RFC 5808: Requirements for a Location-by-Reference Mechanism
In plain English — editorial summary, not part of the RFC
This document defines terminology and provides requirements relating to the Location-by-Reference approach using a location Uniform Resource Identifier (URI) to handle location information within signaling and other Internet messaging. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5808
- Published
- May 2010
- Authors
- R. Marshall
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5774Considerations for Civic Addresses in the Presence Information Data Format Location Object (PIDF-LO): Guidelines and IANA Registry DefinitionCurrent
March 2010
- RFC 5768Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
- RFC 5850A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol (SIP)Current
May 2010
- RFC 5764Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)Updated
May 2010
- RFC 5763Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)Updated
May 2010
- RFC 5853Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) DeploymentsCurrent
April 2010
- RFC 5761Multiplexing RTP Data and Control Packets on a Single PortUpdated
April 2010
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?