ENUM Validation Architecture
draft-mayrhofer-enum-validation-arch-00

Document Type Replaced Internet-Draft (individual)
Last updated 2010-04-09 (latest revision 2005-07-11)
Replaced by draft-ietf-enum-validation-arch
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-validation-arch
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-mayrhofer-enum-validation-arch-00.txt

Abstract

An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether or not the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes validation requirements and a high level architecture for an ENUM validation infrastructure.

Authors

Alex Mayrhofer (axelm@nic.at)
Bernie Hoeneisen (hoeneisen@switch.ch)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)