Analyzing ECRIT Mapping of a Location to an Emergency URI for Emergency Calling
draft-polk-ecrit-mapping-events-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James Polk | ||
| Last updated | 2006-02-28 | ||
| 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
Emergency calling is a localized event, requiring a caller to place an specially identified local emergency call to a Public Safety Answering Point (PSAP), while including the location of the caller in that signaling. The function of routing the set-up messaging to the appropriate PSAP is performed by a mapping function that binds a given location with one or more PSAP SIP(S)-URIs. This function is done by the ECRIT mapping protocol. This document analyzes when the ECRIT mapping protocol function can occur, and what general components are involved in that mapping.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)