datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
draft-ietf-geopriv-held-identity-extensions-06

RFC
Document Stream: IETF
Last updated: 2010-11-14
Replaces: draft-winterbottom-geopriv-held-identity-extensions
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6155
IANA Action State: RFC-Ed-Ack 
Responsible AD: Robert Sparks
Send notices to: geopriv-chairs@tools.ietf.org, draft-ietf-geopriv-held-identity-extensions@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-geopriv-held-identity-extensions.

Abstract:
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.

Authors:
Martin Thomson <martin.thomson@andrew.com>
Richard Barnes <rbarnes@bbn.com>
James Winterbottom <james.winterbottom@andrew.com>
Hannes Tschofenig <Hannes.Tschofenig@gmx.net>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)