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

"James M. Polk" <jmpolk@cisco.com> Wed, 07 December 2005 23:28 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 1Ek8iG-0000ni-GN; Wed, 07 Dec 2005 18:28:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ek8iF-0000nc-6H for sip@megatron.ietf.org; Wed, 07 Dec 2005 18:28:39 -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 SAA16300 for <sip@ietf.org>; Wed, 7 Dec 2005 18:27:47 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ek941-0005XU-EK for sip@ietf.org; Wed, 07 Dec 2005 18:51:10 -0500
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 07 Dec 2005 15:28:29 -0800
X-IronPort-AV: i="3.99,227,1131350400"; d="scan'208"; a="682548923:sNHT30791032"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id jB7NS1Qg011206; Wed, 7 Dec 2005 15:28:27 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Dec 2005 15:28:22 -0800
Received: from jmpolk-wxp.cisco.com ([10.21.88.254]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Dec 2005 15:28:22 -0800
Message-Id: <4.3.2.7.2.20051207171954.02adf928@email.cisco.com>
X-Sender: jmpolk@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 07 Dec 2005 17:28:21 -0600
To: MonicaIngudam@aol.com
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <21d.4f3c202.30c8c453@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-OriginalArrivalTime: 07 Dec 2005 23:28:22.0339 (UTC) FILETIME=[E9E72930:01C5FB85]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: sip@ietf.org
Subject: [Sip] Re: Info required for transporting LK (Location Key)
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

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