[rfc-dist] RFC 4415 on IANA Registration for Enumservice Voice

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon Feb 27 13:00:46 PST 2006


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

        
        RFC 4415

        Title:      IANA Registration for Enumservice Voice 
        Author:     R. Brandner, L. Conroy, 
                    R. Stastny
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    rudolf.brandner at siemens.com, 
                    lwc at roke.co.uk, 
                    Richard.stastny at oefeg.at
        Pages:      8
        Characters: 15956
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-enum-voice-01.txt

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

This document registers the Enumservice \"voice\" (which has a defined
subtype \"tel\"), as per the IANA registration process defined in the
ENUM specification RFC 3761.  This service indicates that the contact
held in the generated Uniform Resource Identifier (URI) can be used
to initiate an interactive voice (audio) call.  [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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list