|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
RFC - Draft Standard (IETF Stream)
|
|
3.
|
Justification for the specific reference:
|
|
|
RFC 4862 is an essntial part of IPv6 Stateless Address Autoconfiguration and is included as normative reference rather than including the full text.
|
|
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=4862
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 4862 was approved in September 2007.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4862 was approved in September 2007.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 4862 is the core specification for autoconfiguration of interfaces in IP version 6. RFC2464, RFC2119, RFC4291, RFC4861 are required to support RFC 4862.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over/
Ethernet Networks", RFC 2464, December 1998./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing/
Architecture", RFC 4291, February 2006./
/
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,/
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,/
September 2007./
/
|
|
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
|
