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

Ben Campbell <ben@nostrum.com> Thu, 12 February 2015 03:07 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 C98B21A8A5A for <stox@ietfa.amsl.com>; Wed, 11 Feb 2015 19:07:41 -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 t3EyAzhv9veZ for <stox@ietfa.amsl.com>; Wed, 11 Feb 2015 19:07:28 -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 2F4CD1A8A65 for <stox@ietf.org>; Wed, 11 Feb 2015 19:07:28 -0800 (PST)
Received: from [10.0.1.23] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id t1C37IAD049458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Feb 2015 21:07:19 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.23]
Content-Type: multipart/signed; boundary="Apple-Mail=_8F5408B1-ABDC-490A-9BC9-96C0B81797C6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Pgp-Agent: GPGMail 2.5b5
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <54DC1441.2090305@andyet.net>
Date: Wed, 11 Feb 2015 21:07:18 -0600
X-Mao-Original-Outgoing-Id: 445403238.179771-fe93bc60406d74cccedf271dfb60759c
Message-Id: <DEC2CB7F-6A39-4E1D-8B6D-82252399F891@nostrum.com>
References: <E77F1000-DD04-44E7-9636-348DA463E6E8@nostrum.com> <54DC0CE3.8090405@andyet.net> <54DC1441.2090305@andyet.net>
To: Peter Saint-Andre - &yet <peter@andyet.net>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/stox/lgct4wRZfZ1r2FBYYd-dZrCMDLk>
Cc: stox@ietf.org, Alissa Cooper <alissa@cooperw.in>, 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: Thu, 12 Feb 2015 03:07:42 -0000

> On Feb 11, 2015, at 8:47 PM, Peter Saint-Andre - &yet <peter@andyet.net> wrote:
> 
> On 2/11/15 7:16 PM, Peter Saint-Andre - &yet wrote:
>> On 2/9/15 4:27 PM, Ben Campbell wrote:
>>> (No hats)
>>> 
>>> Hi,
>>> 
>>> (I apologize that these comments are late in the process. Please feel
>>> free to defer them to last call.)
>>> 
>>> This version mostly looks good, but there are a few minor issues:
>>> 
>>> -- Message Size
>>> 
>>> It might be worth a discussion on message size limits (e.g. the SIP
>>> MESSAGE method limits the size to 1300 octets except under some
>>> pretty narrow circumstances.)
>> 
>> Thank you for pointing this out. I had glossed over it in my reading of
>> RFC 3428. I think it deserves a section of its own in the -im document.
> 
> I propose the following text:
> 
>   [RFC3428] specifies that (outside of a media session) the size of a
>   MESSAGE request is not allowed to exceed 1300 bytes.  Although in
>   practice XMPP instant messages do not often exceed that size, neither
>   [RFC6120] nor [RFC6121] sets an upper limit on the size of XMPP
>   stanzas.  However, XMPP server deployments usually do limit the size
>   of stanzas in order to help prevent denial of service attacks, and
>   [RFC6120] states that if a server sets a maximum stanza size then the
>   limit is not allowed to be less than 10,000 bytes.  Because of this
>   mismatch, an XMPP-to-SIP gateway MUST return a <policy-violation/>
>   stanza error if an XMPP user attempts to send an XMPP message stanza
>   that would result in a SIP MESSAGE greater than 1300 bytes.
> 

That just stepped in a bit of discomfort on my part, in that I'm not sure how a gateway that happened to support both stox-im and stox-chat decides which to invoke. I'm mostly willing to ignore that particular elephant, but would it be reasonable for an implementation to decide that larger messages would get promoted to MSRP (assuming support at the other end)? If so, the MUST return a <policy-violation/> seems to forbid it.

(While I'm still standing in it--what happens in stox-chat if the MSRP side sends a message larger than the largest allowed? Apologies if the draft talks about that--I don't have it in front of me.)


> Peter
> 
> --
> Peter Saint-Andre
> https://andyet.com/