RE: [Sip] Re: Info required for transporting LK (Location Key)

"Winterbottom, James" <James.Winterbottom@andrew.com> Wed, 07 December 2005 23:34 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ek8nj-0002T5-KT; Wed, 07 Dec 2005 18:34:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ek8ni-0002T0-CD for sip@megatron.ietf.org; Wed, 07 Dec 2005 18:34:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16937 for <sip@ietf.org>; Wed, 7 Dec 2005 18:33:27 -0500 (EST)
Received: from marauder.andrew.com ([198.17.217.129]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ek99U-0005kU-NY for sip@ietf.org; Wed, 07 Dec 2005 18:56:50 -0500
Received: from aopmfilt4.andrew.com ([127.0.0.1]) by marauder.andrew.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Dec 2005 17:33:57 -0600
Received: from Unknown [10.3.20.69] by aopmfilt4.andrew.com - SurfControl E-mail Filter (4.7); Wed, 07 Dec 2005 17:33:56 -0600
Received: from aopex5.andrew.com ([10.3.20.205]) by aopexbh2.andrew.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Dec 2005 17:33:56 -0600
Message-ID: <AF9FCF3C02DB264EAF9872DFB6040FCC10485BC0@aopex5.andrew.com>
From: "Winterbottom, James" <James.Winterbottom@andrew.com>
To: "James M. Polk" <jmpolk@cisco.com>, MonicaIngudam@aol.com
Date: Wed, 07 Dec 2005 17:33:55 -0600
Subject: RE: [Sip] Re: Info required for transporting LK (Location Key)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
X-OriginalArrivalTime: 07 Dec 2005 23:33:56.0105 (UTC) FILETIME=[B0D7CF90:01C5FB86]
X-SEF-16EBA1E9-99E8-4E1D-A1CA-4971F5510AF: 1
Content-class: urn:content-classes:message
Thread-Topic: [Sip] Re: Info required for transporting LK (Location Key)
Thread-Index: AcX7hifQOsrqVssqQKyNHXDusPusQgAAG7GQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable
Cc: sip@ietf.org
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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Just to be clear.
A location-Key (LK) as described in the NENA i2 specification is a
location-by-reference.

Cheers
James

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> James M. Polk
> Sent: Thursday, 8 December 2005 10:28 AM
> To: MonicaIngudam@aol.com
> Cc: sip@ietf.org
> Subject: [Sip] Re: Info required for transporting LK (Location Key)
> 
> Monica
> 
> I've changed WG lists here because this document moved from the
SIPPING WG
> to the SIP WG last winter. The current document is here:
>
http://www.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-
> 01.txt
> 
> and it does not support a location key, per se.
> 
> It proposes conveyance of:
> 
> #1 - Location-by-value (the PIDF-LO message body in the message), and
> 
> #2 - Location-by-Reference (a URI to a record on a server that has the
> PIDF-LO for that UA)
> 
> The next version of the document will not be published until at least
> January 06.
> 
> We have a goal of having this document ready (i.e. done) for IESG
review
> by
> May 06.
> 
> 
> At 06:03 PM 12/7/2005 -0500, MonicaIngudam@aol.com wrote:
> >All,
> >
> >NENA refers to draft-ietf-sipping-location-requirements-02 for
> >transporting the location or location key. This draft seems to refer
> >details on LO. This draft seems to have expired on 25th October 2004.
> >Please refer me to the latest document available. I am interested in
> >transporting LK (Location Key). Is there any specific header or tag
> >defined to carry LK ? Any pointers to this question will be helpful.
> >
> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
> >- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
> >Thanks & Regards
> >Monica Ingudam
> 
> _______________________________________________
> 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