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

Ben Campbell <ben@nostrum.com> Mon, 09 February 2015 23:27 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 47C951A8A74 for <stox@ietfa.amsl.com>; Mon, 9 Feb 2015 15:27:15 -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 GqloqGGtdmB6 for <stox@ietfa.amsl.com>; Mon, 9 Feb 2015 15:27:11 -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 8A6211A8A7D for <stox@ietf.org>; Mon, 9 Feb 2015 15:27:11 -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 t19NR88b014526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Feb 2015 17:27:08 -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=_B182F6B1-78D7-4916-8DD0-39A4CE5FA503"; 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>
Date: Mon, 09 Feb 2015 17:27:08 -0600
X-Mao-Original-Outgoing-Id: 445217227.83926-be0cd1ebfaff7a680f13c6e51544a9db
Message-Id: <E77F1000-DD04-44E7-9636-348DA463E6E8@nostrum.com>
To: draft-ietf-stox-im.all@tools.ietf.org
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/stox/x2B5ZhqAwTX6gjRVqNEQNaba95w>
Cc: stox@ietf.org, Alissa Cooper <alissa@cooperw.in>
Subject: [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: Mon, 09 Feb 2015 23:27:15 -0000

(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.)

-- Example 3:

This example reverses the From and To in the SIP response (similar to the same issue for stox-chat.)

--section 4, text right above table 1:

The text references stox-chat for additional mappings. But stox-chat references this draft for the same reasons. I realize it's not really a circular reference, but I think it might confuse the reader.

-- Security considerations

I'm a little uncomfortable non-normatively saying we "prefer" the use of RFC3862. My strictly individual opinion is that we should make a normative recommendation, or merely point out the possibility of using 3862. (I realize we do this a lot with the "ought to" construct, but it seems like things like end-to-end crypto could benefit from a less vague approach.)