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

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Sun, 29 April 2007 07:16 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 1Hi3dk-0006bM-So; Sun, 29 Apr 2007 03:16:12 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hi3dj-0006bG-E7 for sip-confirm+ok@megatron.ietf.org; Sun, 29 Apr 2007 03:16:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hi3dg-0006aq-3j for sip@ietf.org; Sun, 29 Apr 2007 03:16:08 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hi3df-0003Qk-Gh for sip@ietf.org; Sun, 29 Apr 2007 03:16:08 -0400
Received: (qmail 32711 invoked by uid 0); 29 Apr 2007 07:16:06 -0000
Received: from 90.186.63.85 by www100.gmx.net with HTTP; Sun, 29 Apr 2007 09:16:06 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 29 Apr 2007 09:16:06 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
In-Reply-To: <E51D5B15BFDEFD448F90BDD17D41CFF102D1B35C@AHQEX1.andrew.com>
Message-ID: <20070429071606.224850@gmx.net>
MIME-Version: 1.0
References: <E51D5B15BFDEFD448F90BDD17D41CFF102D1B35C@AHQEX1.andrew.com>
Subject: Re: RE: [Sip] Location-conveyance: ISSUE #3 - multiple locations
To: "Winterbottom, James" <James.Winterbottom@andrew.com>, sip@ietf.org, drage@alcatel-lucent.com
X-Authenticated: #29516787
X-Flags: 0001
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
X-Priority: 3
X-Provags-ID: V01U2FsdGVkX1/n1a5WDXTn9ckT4M0ydXWyohZ0bJxE64cL4VqL6H 8qITZYwMRm76++/COpuC5tLiPPe7vIGl3QeQ==
Content-Transfer-Encoding: 7bit
X-GMX-UID: WTNddZgZeWUkW4EFq25n1KYjL0tsZo2r
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc:
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

Hi Keith, 

I also suggested to make use of the PIDF-LO profile document for this purpose in the past. See, for example, http://www1.ietf.org/mail-archive/web/sip/current/msg15002.html

Ciao
Hannes

-------- Original-Nachricht --------
Datum: Sat, 28 Apr 2007 19:24:35 -0500
Von: "Winterbottom, James" <James.Winterbottom@andrew.com>
An: "Drage, Keith \\(Keith\\)" <drage@alcatel-lucent.com>, "IETF SIP List" <sip@ietf.org>
Betreff: RE: [Sip] Location-conveyance: ISSUE #3 - multiple locations

> Hi Keith,
> 
> The GEOPRIV PIDF-LO profile document makes suggestions about including
> and interpreting multiple locations. This may be the right document to
> reference with regards to this topic.
> 
> Cheers
> James
> 
> 
> > -----Original Message-----
> > From: Drage, Keith (Keith) [mailto:drage@alcatel-lucent.com]
> > Sent: Sunday, 29 April 2007 6:00 AM
> > To: IETF SIP List
> > Subject: [Sip] Location-conveyance: ISSUE #3 - multiple locations
> > 
> > (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
> 
> ------------------------------------------------------------------------------------------------
> This message is for the designated recipient only and may
> contain privileged, proprietary, or otherwise private information.  
> If you have received it in error, please notify the sender
> immediately and delete the original.  Any unauthorized use of
> this email is prohibited.
> ------------------------------------------------------------------------------------------------
> [mf2]
> 
> 
> 
> _______________________________________________
> 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


_______________________________________________
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