Location Source Parameter for the SIP Geolocation Header Field

Document Type Replaced Internet-Draft (individual)
Authors James Winterbottom  , Roland Jesske  , Bruno Chatras  , Andrew Hutton 
Last updated 2018-05-29
Replaced by RFC 8787
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sipcore-locparam
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


There are some circumstances where a geolocation header field may contain more than one location value. Knowing the identity of the node adding the location value allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the location values.


James Winterbottom (a.james.winterbottom@gmail.com)
Roland Jesske (r.jesske@telekom.de)
Bruno Chatras (bruno.chatras@orange.com)
Andrew Hutton (andrew.hutton@unify.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)