Location Source Parameter for the SIP Geolocation Header Field
draft-winterbottom-sipcore-locparam-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | James Winterbottom , Roland Jesske , Bruno Chatras , Andrew Hutton | ||
| Last updated | 2018-04-21 (Latest revision 2017-10-18) | ||
| Replaced by | draft-ietf-sipcore-locparam, RFC 8787 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Roland Jesske
Bruno Chatras
Andrew Hutton
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)