RFC 5526 on The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

        
        RFC 5526

        Title:      The E.164 to Uniform Resource 
                    Identifiers (URI) Dynamic Delegation Discovery System 
                    (DDDS) Application for Infrastructure ENUM 
        Author:     J. Livingood, P. Pfautz, R. Stastny
        Status:     Informational
        Date:       April 2009
        Mailbox:    jason_livingood@cable.comcast.com, 
                    ppfautz@att.com, 
                    richard.stastny@gmail.com
        Pages:      9624
        Characters: 5
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-enum-infrastructure-07.txt

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

This document defines the use case for Infrastructure ENUM and
proposes its implementation as a parallel namespace to "e164.arpa", as
defined in RFC 3761, as the long-term solution to the problem of allowing 
carriers to provision DNS records for telephone numbers independently of those provisioned by end users (number assignees).  This memo provides information for the Internet community.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________

IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux