RFC 5687: GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
In plain English — editorial summary, not part of the RFC
This document provides a problem statement, lists requirements, and captures design aspects for a GEOPRIV Layer 7 (L7) Location Configuration Protocol (LCP). This protocol aims to allow an end host to obtain location information, by value or by reference, from a Location Information Server (LIS) that is located in the access network. The obtained location information can then be used for a variety of different protocols and purposes. For example, it can be used as input to the Location-to-Service Translation (LoST) Protocol or to convey location within the Session Initiation Protocol (SIP) to other entities. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5687
- Published
- March 2010
- Authors
- H. Tschofenig; H. Schulzrinne
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5580Carrying Location Objects in RADIUS and DiameterUpdated
August 2009
- RFC 6444Location Hiding: Problem Statement and RequirementsCurrent
January 2012
- RFC 5686RTP Payload Format for mU-law EMbedded Codec for Low-delay IP Communication (UEMCLIP) Speech CodecCurrent
October 2009
- RFC 5691RTP Payload Format for Elementary Streams with MPEG Surround Multi-Channel AudioCurrent
October 2009
- RFC 5669The SEED Cipher Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current
August 2010
- RFC 5658Addressing Record-Route Issues in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5725Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)Current
February 2010
- RFC 5630The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)Current
October 2009
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?