Numbering Tiers
draft-gallant-e164-tier-defs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Gallant | ||
| Last updated | 2001-07-17 | ||
| 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
Describing numbering tiers has been informal to date. This document proposes a simple recognition principle for tiers in terms of the protocol mapping of an E.164 numbering resource to a DNS domain name, as described for ENUM in RFC 2916. Tier value is a formal attribute of the digit string for an arbitrary E.164 resource, and it applies also to the resulting domain name. No assumptions about assignment, existence, or delegation are involved.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)