RFC 4119: A Presence-based GEOPRIV Location Object Format
In plain English — editorial summary, not part of the RFC
This document describes an object format for carrying geographical information on the Internet. This location object extends the Presence Information Data Format (PIDF), which was designed for communicating privacy-sensitive presence information and which has similar properties. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4119
- Published
- December 2005
- Authors
- J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 24
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 5139Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)Current
February 2008
- RFC 5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsUpdated
March 2009
- RFC 7459Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO)Current
February 2015
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5263Session Initiation Protocol (SIP) Extension for Partial Notification of Presence InformationUpdated
September 2008
- RFC 6910Completion of Calls for the Session Initiation Protocol (SIP)Current
April 2013
- RFC 4482CIPID: Contact Information for the Presence Information Data FormatCurrent
July 2006
- RFC 4827An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document ContentsCurrent
May 2007
- RFC 4117Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)Current
June 2005
- RFC 4114E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)Current
June 2005
- RFC 4129Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA ProtocolCurrent
September 2005
- RFC 4103RTP Payload for Text ConversationUpdated
June 2005
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?