[rfc-dist] RFC 5076 on ENUM Validation Information Mapping for the Extensible Provisioning Protocol

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Dec 12 15:05:12 PST 2007


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

        
        RFC 5076

        Title:      ENUM Validation Information Mapping for 
                    the Extensible Provisioning Protocol 
        Author:     B. Hoeneisen
        Status:     Standards Track
        Date:       December 2007
        Mailbox:    hoeneisen at switch.ch
        Pages:      24
        Characters: 44679
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-enum-validation-epp-06.txt

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

This document describes an Extensible Provisioning Protocol (EPP)
extension framework for mapping information about the validation
process that has been applied for the E.164 number (or number range)
that the E.164 Number Mapping (ENUM) domain name is based on.
Specified in the Extensible Markup Language (XML), this mapping
extends the EPP domain name mapping to provide an additional feature
required for the provisioning of ENUM Domain Names.  [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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list