RFC 5105 on ENUM Validation Token Format Definition

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5105

        Title:      ENUM Validation Token Format Definition 
        Author:     O. Lendl
        Status:     Standards Track
        Date:       December 2007
        Mailbox:    [email protected]
        Pages:      17
        Characters: 33057
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-enum-validation-token-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5105.txt

An ENUM domain name is tightly coupled with the underlying E.164
number.  The process of verifying whether 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 a
signed XML data format -- the Validation Token -- with which
Validation Entities can convey successful completion of a validation
procedure in a secure fashion.  [STANDARDS TRACK]

This document is a product of the Telephone Number Mapping
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email protected]
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...