[Geopriv] RFC 6155 on Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
rfc-editor@rfc-editor.org Sat, 12 March 2011 02:11 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B42F3A6CA1; Fri, 11 Mar 2011 18:11:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.118
X-Spam-Level:
X-Spam-Status: No, score=-102.118 tagged_above=-999 required=5 tests=[AWL=-0.118, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFxRkmdQUoaG; Fri, 11 Mar 2011 18:11:29 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CA8AF3A6C9F; Fri, 11 Mar 2011 18:11:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 202C8E0760; Fri, 11 Mar 2011 18:12:48 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110312021248.202C8E0760@rfc-editor.org>
Date: Fri, 11 Mar 2011 18:12:48 -0800
Cc: geopriv@ietf.org, rfc-editor@rfc-editor.org
Subject: [Geopriv] RFC 6155 on Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Mar 2011 02:11:30 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6155 Title: Use of Device Identity in HTTP-Enabled Location Delivery (HELD) Author: J. Winterbottom, M. Thomson, H. Tschofenig, R. Barnes Status: Standards Track Stream: IETF Date: March 2011 Mailbox: james.winterbottom@andrew.com, martin.thomson@andrew.com, Hannes.Tschofenig@gmx.net, rbarnes@bbn.com Pages: 27 Characters: 58542 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-geopriv-held-identity-extensions-06.txt URL: http://www.rfc-editor.org/rfc/rfc6155.txt When a Location Information Server receives a request for location information (using the locationRequest message), described in the base HTTP-Enabled Location Delivery (HELD) specification, it uses the source IP address of the arriving message as a pointer to the location determination process. This is sufficient in environments where the location of a Device can be determined based on its IP address. Two additional use cases are addressed by this document. In the first, location configuration requires additional or alternative identifiers from the source IP address provided in the request. In the second, an entity other than the Device requests the location of the Device. This document extends the HELD protocol to allow the location request message to carry Device identifiers. Privacy and security considerations describe the conditions where requests containing identifiers are permitted. [STANDARDS-TRACK] This document is a product of the Geographic Location/Privacy Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC