Location Source Parameter for the SIP Geolocation Header Field

The information below is for an old version of the document
Document Type Expired Internet-Draft (sipcore WG)
Authors James Winterbottom  , Roland Jesske  , Bruno Chatras  , Andrew Hutton 
Last updated 2019-07-06 (latest revision 2019-01-02)
Replaces draft-winterbottom-sipcore-locparam
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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.)