|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2462 (1998)
|
|
Title:
|
IPv6 Stateless Address Autoconfiguration. S. Thomson, T. Narten, December 1998.
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC2462 deals with IPv6 autoconfiguration 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=2462
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Document published in December 1998 (http://www.ietf.org/rfc/rfc2462.txt). The status is DRAFT STANDARD.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Document published in December 1998 (http://www.ietf.org/rfc/rfc2462.txt). The status is DRAFT STANDARD.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 768 is widely used by IPv6 hosts in local area networks.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2402] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402, November 1998./
[IPv6-ETHER] Crawford, M., "A Method for the Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, December 1998./
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC1112] Deering, S., "Host Extensions for IP Multicasting", STD 5, RFC 1112, August 1989./
[ADDR-ARCH] Hinden, R. and S. Deering, "Internet Protocol Version (IPv6) Addressing Architecture", RFC 2373, July 1998/
[DHCPv6] Bound, J. and C. Perkins, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", Work in Progress./
[DISCOVERY] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998./
|
|
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
|
