HTTP Enabled Location Delivery (HELD)

HTTP Enabled Location Delivery (HELD) draft-winterbottom-http-location-delivery-01 J. Winterbottom, M. Thomson, M. Dawson IETF-63

Rationale • Location information (LI) belongs to a specific IP device (Target) • LI is an access network service • A LS servicing an access network is able to determine LI for an IP device • Serve location information: • directly to the Target • to location recipients using a location URI Location URI IETF-63

Application layer protocol • Preserve PIDF-LO format • Extensions do not affect the HELD payload • Traverses routers and NAT • Reliant only on the presence of IP • Common location request protocol • Type of access network has no effect • Application layer security • TLS with encryption and authentication Location URI IETF-63

Privacy • LI is associated with a device, not a user • Unlinked pseudonyms for the device • LI can be granted without identity information • Target provides a ruleset for LR requests to the LS • Based on common policy – flexible • The target may also specify what rules are included in served PIDF-LO documents Location URI IETF-63

Basic request • HTTP GET to retrieve LI • HTTP POST with parameters • PIDF-LO – provide own location • Ruleset – by-value or by-reference • Specify the type of location or request location by-reference • Set a limit on response time Location URI IETF-63

Location update • Target publishes location update URI • LS serves a request from LR • LS contacts target through update URI, which initiates positioning in cellular network to determine LI Location URI IETF-63

“On Behalf Of” • An entity that requests as if it were the target device • Acknowledgement that not all devices are able to determine or request LI • Enables delivery of services based on location for all devices • Emergency calls • Trust arrangement is either mandated by regulations, or as part of a contract Location URI IETF-63

Discussion

HTTP Enabled Location Delivery (HELD)