The ENUM Branch Location Record
draft-ietf-enum-branch-location-record-03
| Document | Type |
Expired Internet-Draft
(enum WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Otmar Lendl | ||
| Last updated | 2015-10-14 (Latest revision 2007-06-12) | ||
| Replaces | draft-lendl-enum-branch-location-record | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Experimental | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Jon Peterson | ||
| 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 documents defines an extension to the E.164 Number Mapping (ENUM) algorithm by adding a mapping step which indicates where the ENUM tree for a specific ENUM application is located. A new DNS record (IEBL, the Infrastructure ENUM Branch Location record) is defined which provides an interim solution for the Infrastructure ENUM tree location.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)