|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Best Current Practice RFC approved in April 2013. Also known as STD 75.
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 6891 defines an extension mechanism and data format for enhancing the traditional DNS query with more accurate user's information, which supports the content routing/redirection mechanism defined in H.644.5 (ex H.MCDN-CRRS).
|
|
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=6891
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Best Current Practice RFC approved April 2013. Obsoletes RFC 2671, RFC 2673. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Best Current Practice RFC approved April 2013.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Supersedes none.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
10.1 Normative References/
/
[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./
/
[RFC2671] Vixie, P., "Extension Mechanisms for DNS (EDNS0)",/
RFC 2671, August 1999./
/
[RFC3225] Conrad, D., "Indicating Resolver Support of DNSSEC",/
RFC 3225, December 2001./
/
10.2. Informative References/
/
[RFC2673] Crawford, M., "Binary Labels in the Domain Name System",/
RFC 2673, August 1999./
/
[RFC3363] Bush, R., Durand, A., Fink, B., Gudmundsson, O., and T./
Hain, "Representing Internet Protocol version 6 (IPv6)/
Addresses in the Domain Name System (DNS)", RFC 3363,/
August 2002./
/
[RFC3364] Austein, R., "Tradeoffs in Domain Name System (DNS)/
Support for Internet Protocol version 6 (IPv6)", RFC 3364,/
August 2002./
/
[RFC5625] Bellis, R., "DNS Proxy Implementation Guidelines",/
BCP 152, RFC 5625, August 2009.
|
|
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
|
|
