Location Source Parameter for the SIP Geolocation Header Field
draft-winterbottom-sipcore-locparam-02
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Last updated | 2018-04-21 (latest revision 2017-10-18) | ||
| Replaced by | draft-ietf-sipcore-locparam | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-winterbottom-sipcore-locparam-02.txt
Abstract
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.
Authors
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.)