[Sip] Location-conveyance: ISSUE #3 - multiple locations

"Drage, Keith \(Keith\)" <drage@alcatel-lucent.com> Sat, 28 April 2007 20:00 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hht5m-0004Fl-Nl; Sat, 28 Apr 2007 16:00:26 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hht5k-0004FU-F0 for sip-confirm+ok@megatron.ietf.org; Sat, 28 Apr 2007 16:00:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hht5k-0004FM-5O for sip@ietf.org; Sat, 28 Apr 2007 16:00:24 -0400
Received: from ihemail2.lucent.com ([135.245.0.35]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hht5i-0001qG-Sw for sip@ietf.org; Sat, 28 Apr 2007 16:00:24 -0400
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id l3SK0H8f029925 for <sip@ietf.org>; Sat, 28 Apr 2007 15:00:22 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 28 Apr 2007 15:00:18 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.29]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 28 Apr 2007 22:00:15 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: [Sip] Location-conveyance: ISSUE #3 - multiple locations
Date: Sat, 28 Apr 2007 22:00:15 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180010BFC06@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Location-conveyance: ISSUE #3 - multiple locations
Thread-Index: AceJxeRiWYVqzczWSD+GBqRQT3G6eg==
From: "Drage, Keith (Keith)" <drage@alcatel-lucent.com>
To: IETF SIP List <sip@ietf.org>
X-OriginalArrivalTime: 28 Apr 2007 20:00:15.0442 (UTC) FILETIME=[D6912320:01C789CF]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

(As SIP WG chair)

During the review of the WGLC comments, we have identified some issues
where we need consensus calls on the list. These are in one call per
message.

We had a number of comments that it was not clear whether a message
could contain multiple locations, and if they were, what were the
procedures.

On the call we identified what we believe the way forward in this area,
which is summarised by the following statements:

-	location conveyance should support the delivery of multiple
locations;

-	the document will make no recommendations as to how the
recipient chooses 
which location to use. This is regarded as specific to the using
application, 
and therefore beyond the scope of the protocol extension;

-	the recipient should attempt to make use of all the locations
given, and 
should only respond with a 424 response if it is unable to use any of
those 
locations. This includes resolving all and any locations by reference;

-	as a result of the above, any 424 response is a collective
statement about 
all the locations given in the request rather than any specific location
in the 
request.

We will assume that this represents WG consensus unless we hear
otherwise from the WG in 7 calendar days from the posting of this
message. 

Obviously if the WG has an alternative view, some proposal of the
alternative way forward and the expected impact on the text would be
entirely appropriate.

Regards

Keith


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip