metasystema.org
CurrentINFORMATIONALIETF stream

RFC 4725: ENUM Validation Architecture

In plain English — editorial summary, not part of the RFC

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. This memo provides information for the Internet community.

Document record

Document ID
RFC4725
Published
November 2006
Authors
A. Mayrhofer; B. Hoeneisen
Status
INFORMATIONAL
Stream
IETF
Area
rai
Pages
17
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4725-enum-validation-architecture