|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC2671 deals with EDNS0 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=2671
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
It is a mature document which is based on extensive previous experience as listed in the reference list below.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 1035 has a status of STANDARD and was published in August 1999. Since then it has been widely implemented and became one of the major components of Internet.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
The following file is maintained by ISOC/IETF and has all the requested information: http://www.ietf.org/iesg/1rfc_index.txt .
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Mockapetris, P., "Domain Names - Implementation and Specification", STD 13, RFC 1035, November 1987.
|
|
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):
|
|
|
If the Study Group decides to make the reference to the RFC, the reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic".
|
