[Stox] SIPS URIs and SIP/XMPP gateways - WAS: review: stox-core-04

<Markus.Isomaki@nokia.com> Fri, 27 September 2013 11:54 UTC

Return-Path: <Markus.Isomaki@nokia.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A4721F967F for <stox@ietfa.amsl.com>; Fri, 27 Sep 2013 04:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.089
X-Spam-Level:
X-Spam-Status: No, score=-6.089 tagged_above=-999 required=5 tests=[AWL=-0.360, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xNkzaG+QDFEo for <stox@ietfa.amsl.com>; Fri, 27 Sep 2013 04:54:08 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 98A7121F99E8 for <stox@ietf.org>; Fri, 27 Sep 2013 04:54:04 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.23]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r8RBhF4A015591 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 27 Sep 2013 14:43:15 +0300
Received: from 008-AM1MPN1-042.mgdnok.nokia.com ([169.254.2.224]) by 008-AM1MMR1-007.mgdnok.nokia.com ([65.54.30.23]) with mapi id 14.03.0136.001; Fri, 27 Sep 2013 11:43:15 +0000
From: <Markus.Isomaki@nokia.com>
To: <stpeter@stpeter.im>, <salvatore.loreto@ericsson.com>, <rjsparks@nostrum.com>, <fluffy@cisco.com>
Thread-Topic: SIPS URIs and SIP/XMPP gateways - WAS: review: stox-core-04
Thread-Index: Ac67dlH5EGOYZG19TBikH7B+J+lQvw==
Date: Fri, 27 Sep 2013 11:43:14 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0CE34A@008-AM1MPN1-042.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: 2PrCjJ7f5poVv9TjWbkmknDJpXPw7WE8ChV/db8mkahw5MISpLcagY0XhXESR7pR5DXNxXX9RUkhax3VmNpYXAM5mP/FbyEqTb7Es2OTH/hFo2IYamy+LNWHywEXLMcpZwPvw+44PgJZYPJEns75Dn4Fgz4vpSYBqGg/0h2LBD/wujJSuv2UiAqmTZwLaSeZsvzI55p/8eSc9k4X5PIFpQH1gyVvbk3DDwv3a6nbW9XwUyKtZic+zSBiy0SWhxEd6E56y464JU0/qBa2ixx75w==
x-originating-ip: [172.21.80.66]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Nokia-AV: Clean
Cc: stox@ietf.org
Subject: [Stox] SIPS URIs and SIP/XMPP gateways - WAS: review: stox-core-04
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 27 Sep 2013 11:54:17 -0000

Hi,

There was many years ago a lot confusion and discussion about the semantics of the SIPS URIs.

Robert, Cullen: I recall you were there :-) Would you have guidance to the STOX WG how SIPS URIs should be dealt with when SIP/XMPP gateways are involved. Please check Peter's exact question from below.

Regards,
	Markus


> -----Original Message-----
> From: stox-bounces@ietf.org [mailto:stox-bounces@ietf.org] On Behalf Of
> ext Peter Saint-Andre
> Sent: 24 September, 2013 02:55
> To: Salvatore Loreto
> Cc: stox@ietf.org
> Subject: Re: [Stox] review: stox-core-04
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 9/20/13 3:39 AM, Salvatore Loreto wrote:
> > I have reviewed the core-04 draft, and I think that is almost ready
> > for the WGLC
> >
> > I have one general comment (btw I apologize in advance if this has
> > already been discussed and I have overlooked or forgot it) and it is
> > about the fact that draft does not talk at all about the inter working
> > when secure URIs are involved. I think that at least we should say
> > something about in the Security consideration.
> 
> Good catch. After reading and re-reading Section 26.4.4 of RFC 3261, I have to
> admit that I'm not sure exactly how SIP entities are supposed to handle SIPS
> URIs. Even if we understand those requirements, I'm also not sure how they
> would apply to the XMPP side of the communications path. At the least, it
> seems we'd want to specify that if the To header or Request-URI is a SIPS
> URI, then the SIP-to-XMPP gateway needs to connect to the XMPP server
> over a TLS-protected stream. However, do we also need to stipulate that the
> XMPP server-to-client connection is TLS-protected? If so, how would the
> gateway associated with the XMPP server ensure that? (The gateway might
> be an external component of the XMPP server, without control over how the
> XMPP server communicates with XMPP clients.)
> 
> Peter
> 
> - --
> Peter Saint-Andre
> https://stpeter.im/
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQIcBAEBAgAGBQJSQNS6AAoJEOoGpJErxa2pueYQAJFMEL4C00F37XDdk9uvA
> DsP
> 3MM9Si1gIYTmIdI4bW4HY8A5LfggByoT17SD/fYjDoescHfhxO4nb8EP/ElUq0lY
> uTeUBl9fi+PQUwQweZS4O/inQAucUTWjf6NAk3x4ETN6ct0dUwXgzj1avmu7o
> O9G
> t4STEtxtxSHMMjFUacCyHxTYp0b9fSCExUScsGHeM7RJtS4oUrxI8Rb8QNDH8b
> ZV
> CFo52opkkYBkjZFfIjMGHLzrMNR66G0C9Cbvx+SIy1hhM2iCqWtS50+KMcWBz
> g7c
> Vog96pNL/li27U18ZAR5kXMT7hbNj/eV2Na6WXPw0ITJ1LtcR2TNbyvJ66U//b0
> g
> Ba5R6Dwk7QfBjW1MQ1W79VOZsRga9RYjEuxKtJ+acZeoL/kLSikEZn0o1N+FXtz
> t
> A0sR0Hovx6jyPDodkrP4R62uhdUdDWXIcLgVOiNTtS9Hbu+RPhDOmsvAA/OyF
> t23
> u8nqBLocb57Mxwvk2b9FMGrBa5aQD2dsSiyfEXtMDlOYlxlBYa7vBoVyI8GPLIb
> m
> sTRPDjN0NvAmokzSWlcA8T2PwnXu06N3UOctw7eVZPoFIE6yk0t/kMNhofMx
> q/EV
> 4K+tnU1I3w/irDTYA8g3zRfCpbs+RlmGG9pgpN9iOFdas9AQe1jS1rZp3H8C/TG
> U
> DM4DbC4CrD0Itj2y0pBp
> =VUg1
> -----END PGP SIGNATURE-----
> _______________________________________________
> stox mailing list
> stox@ietf.org
> https://www.ietf.org/mailman/listinfo/stox