A Geopriv Registry for Location-based Error Response Codes
draft-polk-geopriv-location-based-error-registry-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James Polk | ||
| Last updated | 2006-10-17 | ||
| 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
This document IANA registers a list of GEOPRIV location-specific error response indications, to be used by signaling protocols describing a location-based error experienced by an intermediary or recipient endsystem. For example, the registered values here can be placed in a SIP Reason header contained within a 424 (Bad Location Information) response, or in a Location-to-Service Translation (LoST) query failure, giving specific meaning to the reason for the error. This additional information is to provide the location transmitter more granular information about what was wrong with the supplied location in the original request message.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)