[Enum] FW: RFC 4759 on The ENUM Dip Indicator Parameter for the "tel" URI

FYI

> -----Original Message-----
> From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> Sent: Monday, December 11, 2006 4:58 PM
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: iptel@ietf.org; rfc-editor@rfc-editor.org
> Subject: RFC 4759 on The ENUM Dip Indicator Parameter for the "tel" URI
> 
> 
> 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@oefeg.at,
>                     richard.shockey@neustar.biz,
>                     lconroy@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@IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> 
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> 
> help: ways_to_get_rfcs. For example:
> 
>         To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
> Authors, for further information.
> 
> 
> The RFC Editor Team
> USC/Information Sciences Institute
> 
> ...
> 
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce


_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum