metasystema.org
CurrentBEST CURRENT PRACTICEIETF streamBCP160

RFC 6280: An Architecture for Location and Location Privacy in Internet Applications

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

Location-based services (such as navigation applications, emergency services, and management of equipment in the field) need geographic location information about Internet hosts, their users, and other related entities. These applications need to securely gather and transfer location information for location services, and at the same time protect the privacy of the individuals involved. This document describes an architecture for privacy-preserving location-based services in the Internet, focusing on authorization, security, and privacy requirements for the data formats and protocols used by these services. This memo documents an Internet Best Current Practice.

Document record

Document ID
RFC6280
Published
July 2011
Authors
R. Barnes; M. Lepinski; A. Cooper; J. Morris; H. Tschofenig; H. Schulzrinne
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
rai
Pages
41
Also known as
BCP160
Updates:
RFC 3693, RFC 3694

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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 . RFCs are never revised after publication; changes are issued as new documents.

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

canonical URL: /rfc/6280-an-architecture-for-location-and-location-privacy-in-internet-applications