ENUM Implementation Issues and Experiences
draft-conroy-enum-experiences-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2010-04-09 (latest revision 2004-02-12) | ||
| Replaced by | draft-ietf-enum-experiences | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-enum-experiences | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-conroy-enum-experiences-01.txt
https://www.ietf.org/archive/id/draft-conroy-enum-experiences-01.txt
Abstract
This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is informational only, and produced as a help to others in reporting what is 'out there' and the potential pitfalls in interpreting the set of documents that specify the protocol.
Authors
Lawrence Conroy (lconroy@insensate.co.uk)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)