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

Location-based services (such as navigation applications, emergency services, and management of equipment in the field) need geographic location information…

Read RFC 6280 on the RFC Editor

Outgoing relationships (2 related RFCs)

Updates — RFC 3693: Geopriv Requirements
Updates — RFC 3694: Threat Analysis of the Geopriv Protocol

Incoming relationships (13 related RFCs)

Normatively referenced by — RFC 8060: LISP Canonical Address Format (LCAF)
Normatively referenced by — RFC 6848: Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)
Normatively referenced by — RFC 6397: Multi-Threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) Routing Information Export Format with Geo-Location Extensions
Normatively referenced by — RFC 6447: Filtering Location Notifications in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 7459: Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO)
Informatively referenced by — RFC 6973: Privacy Considerations for Internet Protocols
Informatively referenced by — RFC 6442: Location Conveyance for the Session Initiation Protocol
Informatively referenced by — RFC 6772: Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
Informatively referenced by — RFC 7216: Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNS
Informatively referenced by — RFC 6908: Deployment Considerations for Dual-Stack Lite
Informatively referenced by — RFC 6915: Flow Identity Extension for HTTP-Enabled Location Delivery (HELD)
Informatively referenced by — RFC 6753: A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)
Informatively referenced by — RFC 7105: Using Device-Provided Location-Related Measurements in Location Configuration Protocols