Learning the Initial Location-to-Service Translation (LoST) Uniform Resource Identifier (URI) During Session Initiation Protocol (SIP) Registration
draft-polk-ecrit-lost-server-uri-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | James Polk | ||
| Last updated | 2006-06-19 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-polk-ecrit-lost-server-uri-00.txt
Abstract
A Location-to-Service Translation protocol (LoST) Server is used to resolve or map a given location with an appropriate Public Safety Answering Point (PSAP) Uniform Resource Identifier (URI) for that location. This query is conceivably performed on two occasions: prior to making an emergency call, and during an emergency call. This document specifies a new Session Initiation Protocol (SIP) header, returned in a SIP Registration transaction, indicating to a SIP user agent the appropriate LoST Server's URI to send this query to.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)