Geopriv requirements
draft-cuellar-geopriv-reqs-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Jorge R. Cuellar , Mehmet Ersue , John Morris , Deirdre Mulligan | ||
Last updated | 2002-05-09 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Location-based services, navigation applications, emergency services, management of equipment in the field, and other location-dependent services need geographic location information about a target (user, resource or other entity). There is a need to securely gather and transfer location information for location services, protecting the privacy of the individuals involved. This document describes the requirements for the geopriv Location Object (used to transfer location data and perhaps some other information) and for further IETF protocols that use this Location Object as an embedded protocol. We focus on authorization, integrity and privacy requirements.
Authors
Jorge R. Cuellar
Mehmet Ersue
John Morris
Deirdre Mulligan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)