Skip to main content

Location Source Parameter for the SIP Geolocation Header Field
RFC 8787

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed metadata: changed keywords to '['Emergency', 'Call', 'Location']' from '[]'
2026-05-20
(System) Metadata update from RFC Editor
2026-05-20
(System) Changed author "A. Hutton": changed name from "Andrew Hutton" to "A. Hutton", cleared country (was "UK"), changed order from "3" to "4"
2026-05-20
(System) Changed author "B. Chatras": changed name from "Bruno Chatras" to "B. Chatras", cleared country (was "France"), changed order from "2" to "3"
2026-05-20
(System) Changed author "R. Jesske": changed name from "Roland Jesske" to "R. Jesske", cleared country (was "Germany"), changed order from "1" to "2"
2026-05-20
(System) Changed author "J. Winterbottom": changed name from "James Winterbottom" to "J. Winterbottom", cleared country (was "AU"), changed order from "0" to "1"
2026-05-20
(System) Metadata update from RFC Editor
2020-05-31
(System)
Received changes through RFC Editor sync (created alias RFC 8787, changed abstract to 'There are some circumstances where a Geolocation header field may contain …
Received changes through RFC Editor sync (created alias RFC 8787, changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-05-31, changed IESG state to RFC Published, created updates relation between draft-ietf-sipcore-locparam and RFC 6442)
2020-05-31
(System) RFC published