|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6116 (2011)
|
|
Title:
|
The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM), IETF RFC, 2011.
|
|
|
2.
|
Status of approval:
|
|
|
Approved as Proposed Standard in 2011-03.
|
|
3.
|
Justification for the specific reference:
|
|
|
This reference defines the use of the Domain Name System (DNS) for storage of data associated with E.164 numbers, and for resolving those numbers into URIs that can be used (for example) in telephony call setup.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=6116
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
Obsoletes RFC 3761.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References:/
[E.164] ITU-T, "The International Public Telecommunication Number/
Plan", Recommendation E.164, February 2005./
/
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",/
STD 13, RFC 1034, November 1987./
/
[RFC1035] Mockapetris, P., "Domain names - implementation and/
specification", STD 13, RFC 1035, November 1987./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC3402] Mealling, M., "Dynamic Delegation Discovery System (DDDS)/
Part Two: The Algorithm", RFC 3402, October 2002./
/
[RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS)/
Part Three: The Domain Name System (DNS) Database", RFC/
3403, October 2002./
/
[RFC3404] Mealling, M., "Dynamic Delegation Discovery System (DDDS)/
Part Four: The Uniform Resource Identifiers (URI)", RFC/
3404, October 2002./
/
[RFC3492] Costello, A., "Punycode: A Bootstring encoding of Unicode/
for Internationalized Domain Names in Applications (IDNA)",/
RFC 3492, March 2003./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646",/
STD 63, RFC 3629, November 2003./
/
[RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform/
Resource Identifiers (URI) Dynamic Delegation Discovery/
System (DDDS) Application (ENUM)", RFC 3761, April 2004./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66, RFC/
3986, January 2005./
/
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource/
Identifiers (IRIs)", RFC 3987, January 2005./
/
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
Informative References:/
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,/
March 1997./
/
[RFC2136] Vixie, P., Ed., Thomson, S., Rekhter, Y., and J. Bound,/
"Dynamic Updates in the Domain Name System (DNS UPDATE)",/
RFC 2136, April 1997./
/
[RFC2671] Vixie, P., "Extension Mechanisms for DNS (EDNS0)", RFC/
2671, August 1999./
/
[RFC2782] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for/
specifying the location of services (DNS SRV)", RFC 2782,/
February 2000./
/
[RFC2915] Mealling, M. and R. Daniel, "The Naming Authority Pointer/
(NAPTR) DNS Resource Record", RFC 2915, September 2000./
/
[RFC2916] Faltstrom, P., "E.164 number and DNS", RFC 2916, September/
2000./
/
[RFC3245] Klensin, J., Ed., and IAB, "The History and Context of/
Telephone Number Mapping (ENUM) Operational Decisions:/
Informational Documents Contributed to ITU-T Study Group 2/
(SG2)", RFC 3245, March 2002./
/
[RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation/
Protocol (SIP): Locating SIP Servers", RFC 3263, June 2002./
/
[RFC3401] Mealling, M., "Dynamic Delegation Discovery System (DDDS)/
Part One: The Comprehensive DDDS", RFC 3401, October 2002./
/
[RFC3597] Gustafsson, A., "Handling of Unknown DNS Resource Record/
(RR) Types", RFC 3597, September 2003./
/
[RFC3824] Peterson, J., Liu, H., Yu, J., and B. Campbell, "Using/
E.164 numbers with the Session Initiation Protocol (SIP)",/
RFC 3824, June 2004./
/
[RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain/
Name System (DNS)", RFC 3833, August 2004./
/
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S./
Rose, "DNS Security Introduction and Requirements", RFC/
4033, March 2005./
/
[RFC5483] Conroy, L. and K. Fujiwara, "ENUM Implementation Issues and/
Experiences", RFC 5483, March 2009./
/
[RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA/
Registration of Enumservices: Guide, Template, and IANA/
Considerations" RFC 6117, March 2011.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
