[Enum] RFC 3761 on The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
- Date: Sat, 1 May 2004 10:58:01 +0200
- Priority: Urgent
Finally rfc2916bis made it officially to RFC3761
IMPORTANT NOTE: RFC3761 OBSOLETES RFC2916
In addition also the h323 enumservice is defined in RFC3762 and
the sip enumservice is defined in RFC3764
Von: rfc-editor@localhost [
Gesendet: Sa 01.05.2004 01:59
Cc: rfc-editor@localhost enum@localhost
Betreff: [Enum] RFC 3761 on The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
A new Request for Comments is now available in online RFC libraries.
Title: The E.164 to Uniform Resource Identifiers (URI)
Dynamic Delegation Discovery System (DDDS)
Author(s): P. Faltstrom, M. Mealling
Status: Standards Track
Date: April 2004
Mailbox: paf@localhost, michael@localhost
I-D Tag: draft-ietf-enum-rfc2916bis-07.txt
This document discusses the use of the Domain Name System (DNS) for
storage of E.164 numbers. More specifically, how DNS can be used for
identifying available services connected to one E.164 number. It
specifically obsoletes RFC 2916 to bring it in line with the Dynamic
Delegation Discovery System (DDDS) Application specification found in
the document series specified in RFC 3401. It is very important to
note that it is impossible to read and understand this document
without reading the documents discussed in RFC 3401.
This document is a product of the Telephone Number Mapping Working
Group of the IETF.
This is now a Proposed Standard Working Group.
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@localhost. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@localhost.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@localhost with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@localhost. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@localhost. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.