[xmpp] Does 6122bis need to update 5122?

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Fri, 01 August 2014 16:55 UTC

Return-Path: <jhildebr@cisco.com>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38DB21B2839 for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 09:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 euJ7DVjuBnzR for <xmpp@ietfa.amsl.com>; Fri, 1 Aug 2014 09:55:14 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C74B41B282A for <xmpp@ietf.org>; Fri, 1 Aug 2014 09:55:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=932; q=dns/txt; s=iport; t=1406912114; x=1408121714; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=FDM9QvoFh6+cAAPc5az09i+Wr9GaDSaynTqyODEfxy4=; b=kehSqDSdAyUa62r1d/9Fl3mT8BhNhgf2UsR5JA6I9e5ALYDEPQ/us7Qk qkYmReaEH71oTFF3bAPmSfrcs6w/G3nrZf6TSVwCM37x5jWBtAuQyjueN wWPGS6X72IEDtZ9/Ifc+4RQj1mLY4wCXwt1+YZQdls183HHeytt7eBlbs Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAAvF21OtJA2B/2dsb2JhbABbgw1SVwSCdMkQh25yFneECiMRVwEiAiYCBDAVEgQTiEKic48rl3EXgSyRIIFSBZdAhDqUWoNJbIFF
X-IronPort-AV: E=Sophos;i="5.01,780,1400025600"; d="scan'208";a="65835291"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-2.cisco.com with ESMTP; 01 Aug 2014 16:55:14 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s71GtCIe021530 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <xmpp@ietf.org>; Fri, 1 Aug 2014 16:55:12 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Fri, 1 Aug 2014 11:54:22 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "xmpp@ietf.org" <xmpp@ietf.org>
Thread-Topic: Does 6122bis need to update 5122?
Thread-Index: AQHPralbv4SoRfqF80GhK2/Lv139gg==
Date: Fri, 01 Aug 2014 16:55:11 +0000
Message-ID: <D001223B.57A8E%jhildebr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.129.24.156]
Content-Type: text/plain; charset="utf-8"
Content-ID: <932EBB4D2350B849AB82C6B7BE50797B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/JS4dCOJefPCrNzaSr99s4Yjn5W0
Subject: [xmpp] Does 6122bis need to update 5122?
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Aug 2014 16:55:18 -0000

On 8/1/14, 10:49 AM, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:

>In that case, we'd specify an XMPP URI (RFC 5122).
>
>Thus I might suggest:
>
>    For an XMPP client [RFC6120] using STUN and TURN, the ORIGIN
>    attribute is an XMPP URI [RFC5122] representing the domainpart
>    of the client's Jabber ID (JID) [RFC6122]; for example, if the
>    client's JID is "juliet@im.example.com/balcony" then the ORIGIN
>    attribute would be "xmpp:im.example.com".

This made me wonder if we need to either rev 5122 to point to 6122bis, or
just have 6122 update 5122 (which I think I'd prefer, so we don't open up
a can of IRI worms).

-- 
Joe Hildebrand