UpdatedINFORMATIONALIETF stream

RFC 3693: Geopriv Requirements

Still current, but amended. Parts of this document are changed or extended by RFC 6280, RFC 7459. Read both.

In plain English — editorial summary, not part of the RFC

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 (such as a user, resource or other entity). There is a need to securely gather and transfer location information for location services, while at the same time protect the privacy of the individuals involved. This document focuses on the authorization, security and privacy requirements for such location-dependent services. Specifically, it describes the requirements for the Geopriv Location Object (LO) and for the protocols that use this Location Object. This LO is envisioned to be the primary data structure used in all Geopriv protocol exchanges to securely transfer location data. This memo provides information for the Internet community.

Document record

Document ID: RFC3693
Published: February 2004
Authors: J. Cuellar; J. Morris; D. Mulligan; J. Peterson; J. Polk
Status: INFORMATIONAL
Stream: IETF
Area: rai
Pages: 30
Also known as: —

Updated by:: RFC 6280, RFC 7459

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on 23 August 2026. RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?