Location Source Parameter for the SIP Geolocation Header Field
draft-winterbottom-dispatch-locparam-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | James Winterbottom , Laura Liess , Bruno Chatras , Andrew Hutton , Roland Jesske | ||
| Last updated | 2017-07-03 (Latest revision 2016-12-30) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
Laura Liess
Bruno Chatras
Andrew Hutton
Roland Jesske
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)