Requirements for Authorized Emergency Communications
Using Elastic Service
draft-carlberg-ieprep-elastic-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ken Carlberg , Ian Brown | ||
| Last updated | 2002-06-20 | ||
| 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
The objective of this draft is to present a set of requirements to address requests by users of authorized emergency communications for better than best effort service for elastic service. We stress the word 'request' versus guarantee, and we do NOT advocate broad sweeping changes to elastic applications. This document provides background information on emergency communications and presents suggested do's and don'ts in addressing the issue of requirements for elastic services. Finally, examples of requirements for specific applications are presented.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)