RFC 8787: Location Source Parameter for the SIP Geolocation Header Field
In plain English — editorial summary, not part of the RFC
There are some circumstances where a Geolocation header field may contain more than one locationValue. Knowing the identity of the node adding the locationValue allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the locationValues. This document defines the "loc-src" parameter so that the entity adding the locationValue to the Geolocation header field can identify itself using its hostname. This document updates RFC 6442.
Document record
- Document ID
- RFC8787
- Published
- May 2020
- Authors
- J. Winterbottom; R. Jesske; B. Chatras; A. Hutton
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 6442
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
- RFC 8606ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header FieldCurrent
June 2019
- RFC 8148Next-Generation Vehicle-Initiated Emergency CallsCurrent
May 2017
- RFC 8147Next-Generation Pan-European eCallCurrent
May 2017
- RFC 8917The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service TagCurrent
October 2020
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
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?