1.
|
Clear description of the referenced document:
|
|
|
2.
|
Status of approval:
|
|
Normative
|
3.
|
Justification for the specific reference:
|
|
IETF RFC3596 deals with DNS Extensions for IPv6 used in IPTV terminal devices.
|
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=3596
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
Document published in October 2003 (http://www.ietf.org/rfc/rfc3596.txt). The status is Proposed STANDARD.
|
6.
|
The degree of stability or maturity of the document:
|
|
Document published in October 2003 (http://www.ietf.org/rfc/rfc3596.txt). The status is Proposed STANDARD.
|
7.
|
Relationship with other existing or emerging documents:
|
|
Related RFC are picked up in item (8) below.
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
[1] Mockapetris, P., "Domain Names - Concepts and Facilities", STD 13, RFC 1034, November 1987./
[2] Mockapetris, P., "Domain Names - Implementation and Specification", STD 13, RFC 1035, November 1987./
[3] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) Addressing Architecture", RFC 3513, April 2003.
|
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
|