Non-Interactive Emergency Calls
draft-rosen-stir-emergency-calls-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Brian Rosen | ||
Last updated | 2020-09-10 (Latest revision 2020-03-09) | ||
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 calls from citizens to authorities, and call back of such emergency calls by authorities to citizens need assurances that headers intended to get appropriate priority from the networks they traverse, and in some cases, appropriate routing. Protection of the SIP Resource Priority Header and the SIP Priority header is needed for such calls. This document describes the environment for placing emergency calls and call backs which motivate the need and use of the mechanisms described in other documents
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)