|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3646 (2003)
|
|
Title:
|
DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (2003/12)
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
ETF RFC3646 deals with DNS options for DHCPv6 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=3646
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred specifications is "approved specification".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred specifications is "approved specification".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced specifications are listed under item (8).
|
|
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./
[2] Bound, J., Carney, M., Perkins, C., Lemon, T., Volz, B. and R. Droms (ed.), "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, May 2003./
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[4] Eastlake, D., "Domain Name System Security Extensions", RFC 2535, March 1999./
[5] Kumar, A., Postel, J., Neuman, C., Danzig, P. and S. Miller,"Common DNS Implementation Errors and Suggested Fixes", RFC 1536, October 1993.
|
|
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
|
