Network Requirements for Internet Emergency Preparedness Services
draft-beard-ieprep-requirements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Cory Beard | ||
| Last updated | 2002-05-15 | ||
| 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 outlines requirements that need to be met in IP-based networks to enable and support communications for National Security/Emergency Preparedness (NS/EP) operations. It provides a template from which an emergency service can be negotiated and provides a set of requirements that should be met for acceptable emergency communication services. The focus here is on network requirements, rather than requirements for particular applications. The requirements are general and are intended to provide wide latitude in implementation options for service providers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)