[rfc-dist] RFC 4759 on The ENUM Dip Indicator Parameter for the "tel" URI

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon Dec 11 13:57:48 PST 2006


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

        
        RFC 4759

        Title:      The ENUM Dip Indicator Parameter 
                    for the "tel" URI 
        Author:     R. Stastny, R. Shockey,
                    L. Conroy
        Status:     Standards Track
        Date:       December 2006
        Mailbox:    Richard.stastny at oefeg.at, 
                    richard.shockey at neustar.biz, 
                    lconroy at insensate.co.uk
        Pages:      8
        Characters: 15062
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-iptel-tel-enumdi-05.txt

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

This document defines a new parameter "enumdi" for the "tel" Uniform
Resource Identifier (URI) to support the handling of ENUM queries in
Voice over Internet Protocol (VoIP) network elements.  A VoIP network
element may receive a URI containing an E.164 number, where that URI
contains an "enumdi" parameter.  The presence of the "enumdi"
parameter indicates that an ENUM query has already been performed on
the E.164 number by a previous VoIP network element.  Equally, if a
VoIP network element sends such a URI, it asserts that an ENUM query
has been carried out on this number.  [STANDARDS TRACK]

This document is a product of the IP Telephony
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