Re: [Stox] Comments on draft-ietf-stox-im-11

Ben Campbell <ben@nostrum.com> Sat, 14 February 2015 04:52 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55CCE1A0210 for <stox@ietfa.amsl.com>; Fri, 13 Feb 2015 20:52:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eu7mQwI2lg_r for <stox@ietfa.amsl.com>; Fri, 13 Feb 2015 20:51:56 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB8061A0252 for <stox@ietf.org>; Fri, 13 Feb 2015 20:51:56 -0800 (PST)
Received: from [172.16.4.239] (75-146-141-17-NewMexico.hfc.comcastbusiness.net [75.146.141.17]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id t1E4phc1085069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Feb 2015 22:51:45 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 75-146-141-17-NewMexico.hfc.comcastbusiness.net [75.146.141.17] claimed to be [172.16.4.239]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (12B466)
In-Reply-To: <54DE2480.7060501@andyet.net>
Date: Fri, 13 Feb 2015 21:51:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD8943CD-4194-4FA9-9CED-DDE7964812F1@nostrum.com>
References: <E77F1000-DD04-44E7-9636-348DA463E6E8@nostrum.com> <54DC0CE3.8090405@andyet.net> <54DC1441.2090305@andyet.net> <DEC2CB7F-6A39-4E1D-8B6D-82252399F891@nostrum.com> <54DD28F4.7070200@andyet.net> <AD925407-4003-479D-92AF-B60A5EC6594F@nostrum.com> <54DD6CCA.2020605@andyet.net> <5228A173-7B2F-49BA-AA38-F63B70B8DD39@nostrum.com> <54DD7626.40704@andyet.net> <54DE2480.7060501@andyet.net>
To: Peter Saint-Andre - &yet <peter@andyet.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/stox/AKh1vgEK9QbAcK_O5CNHKt-5E88>
Cc: "stox@ietf.org" <stox@ietf.org>, Alissa Cooper <alissa@cooperw.in>, "draft-ietf-stox-im.all@tools.ietf.org" <draft-ietf-stox-im.all@tools.ietf.org>
Subject: Re: [Stox] Comments on draft-ietf-stox-im-11
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Feb 2015 04:52:01 -0000

On Feb 13, 2015, at 9:21 AM, Peter Saint-Andre - &yet <peter@andyet.net> wrote:

>> Proposed text for a new section in stox-chat...
>> 
>> ###
>> 
>> 8.  Message Size
>> 
>>    Unlike page-mode messaging [RFC3428] (which specifies that the size
>>    of a MESSAGE request is not allowed to exceed 1300 bytes), session-
>>    mode messaging [RFC4975] can be used to send larger messages.  MSRP
>>    includes a chunking mechanism such that larger messages can be broken
>>    up into multiple MSRP SEND requests.  Because the MSRP gateway at an
>>    XMPP service acts as an MSRP endpoint, it is responsible for
>>    receiving chunked messages and reconstructing them into a single
>>    message for delivery toward the XMPP recipient.  (Naturally,
>>    implementations need to be careful about accepting very large
>>    messages; see Section 14.5 of [RFC4975].)
>> 
>>    Although there is no hard limit on the size of an XMPP stanza, in
>>    practice most XMPP services (at least on the public Internet) are
>>    configured with a maximum stanza size in order to help prevent denial
>>    of service attacks.  As specified in Section 13.12 of [RFC6120], this
>>    maximum is not allowed to be less than 10,000 bytes.
>> 
>>    The administrators of an XMPP service need to ensure the associated
>>    MSRP gateway is configured with the same or smaller maximum MSRP
>>    message size as the maximum XMPP stanza size; this enables the
>>    gateway to return an appropriate value for the SDP "max-size"
>>    attribute and to properly handle messages larger than the configured
>>    limits.
>> 
>>    If an MSRP-to-XMPP gateway implementation receives an MSRP message
>>    that exceeds its configured limit as just described, it MUST return
>>    an MSRP 413 error (e.g., in response to the first SEND request whose
>>    Byte-Range header field indicates a byte total exceeding the limit).
>> 
>> ###
> 
> Ben, let me know if that text looks OK. It seems that we'll want to add a pointer from the -groupchat document to this section, too, eh?

Yes, and probably. 

> 
> I think this is the last open issue from your reviews, so once you say it's OK I'll submit revised I-Ds for -im, -chat, and -groupchat.

Agreed.