ETS Requirements for Stub Domains
draft-carlberg-ets-req-stub-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ken Carlberg | ||
| Last updated | 2003-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
This document presents a list of requirements in support of Emergency Telecommunications Service (ETS) within a single adminsitrative stub domain. This document is an extension of the General Requirements of [2] and focuses on a more specific set of administrative constraints and scope. Solutions to these requirements are not presented in this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)