RFC 5962: Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO)
In plain English — editorial summary, not part of the RFC
The Geopriv Location Object introduced by the Presence Information Data Format - Location Object (PIDF-LO), RFC 4119, defines a basic XML format for carrying geographical information of a presentity. This document defines PIDF-LO extensions to convey information about moving objects. Elements are defined that enable expression of spatial orientation, speed, and heading of the presentity. [STANDARDS TRACK]
Document record
- Document ID
- RFC5962
- Published
- September 2010
- Authors
- H. Schulzrinne; V. Singh; H. Tschofenig; M. Thomson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5964Specifying Holes in Location-to-Service Translation (LoST) Service BoundariesCurrent
August 2010
- RFC 5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsUpdated
March 2009
- RFC 5139Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)Current
February 2008
- RFC 5606Implications of 'retransmission-allowed' for SIP Location ConveyanceCurrent
August 2009
- RFC 6447Filtering Location Notifications in the Session Initiation Protocol (SIP)Current
January 2012
- RFC 6451Location-to-Service Translation (LoST) Protocol ExtensionsCurrent
December 2011
- RFC 6739Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) ProtocolUpdated
October 2012
- RFC 6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)Current
October 2012
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?