Saturday, May 01, 2004
RFC3761 ENUM finally released
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
RFC3761:
RFC3761 OBSOLETES RFC2916
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.
At the same time the enumservices for h323 (RFC3762) and sip (RFC3764) have been released. Together with the enumservices defined in ETSI TS 102 172 "Minimum Requirements for Interoperability of European ENUM Trials" ENUM commercial implementation can be launched.
ETSI is currently working on Version 2 of TS 102 172 "Minimum Requirements for Interoperability of ENUM Implementations", taking the current developments and also the experiences of the various trials into account.
The last cornerstone missing is now the replacement of the "Interim Procedures" of ITU-TSB for delegations within e164.arpa by an ITU-T Recommendation. This could be done in the May 2003 SG2 Plenary in Geneva by finalizing the draft AENUM.
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
RFC3761:
RFC3761 OBSOLETES RFC2916
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.
At the same time the enumservices for h323 (RFC3762) and sip (RFC3764) have been released. Together with the enumservices defined in ETSI TS 102 172 "Minimum Requirements for Interoperability of European ENUM Trials" ENUM commercial implementation can be launched.
ETSI is currently working on Version 2 of TS 102 172 "Minimum Requirements for Interoperability of ENUM Implementations", taking the current developments and also the experiences of the various trials into account.
The last cornerstone missing is now the replacement of the "Interim Procedures" of ITU-TSB for delegations within e164.arpa by an ITU-T Recommendation. This could be done in the May 2003 SG2 Plenary in Geneva by finalizing the draft AENUM.
Comments:
Post a Comment
