Administrative Requirements for Deployment of ENUM in North America
draft-pfautz-na-enum-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Penn Pfautz | ||
| Last updated | 2000-09-11 | ||
| 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 discusses a number of the administrative issues that must be resolved before effective deployment of ENUM[2,3] services in complex environments with number portability and multiple providers for using DNS for translation of E.164 (telephone) numbers. North America is examined critically because its environment may be more complex than most and because current deregulation trends may drive other countries/regions in similar directions. In particular the current mechanisms for number administration and number portability in North America will require establishment of a new administrative function for managing the domain name entries for ported numbers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)