Framework for ENUM Neutrality
draft-rutkowski-enum-neutrality-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Anthony Rutkowski | ||
| Last updated | 2001-11-12 | ||
| 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 pursuit by major national Administrations of declared policies of ENUM technical and administrative neutrality among implementations in the marketplace suggest the need for a framework for such neutrality and a focus on interworking among them. [1] [2] This document draws upon the ENUM Working Group archive of discussions as well as public activities in other standards forums and the marketplace to construct an ENUM options framework for facilitating neutrality. This framework includes not only protocol considerations, but also various critical technical and administrative support functions such as authentication and ancillary directory services.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)