Committed to connecting the world

  •  

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.3405     
  ITU-T A.5 justification information for referenced document IETF RFC 4861 (2007) in draft Q.3405
1. Clear description of the referenced document:
Name: IETF RFC 4861 (2007)
Title: Neighbor Discovery for IP version 6 (IPv6)
2. Status of approval:
Normative
3. Justification for the specific reference:
IETF RFC 4861 (2007) is referenced in Q.3405 (ex. Q.IPv6ProBB).
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=4861
5. Other useful information describing the "Quality" of the document:
RFC 4861 has been in existence since 2007.
6. The degree of stability or maturity of the document:
It is a standards-track document. Current standards status of this document can be found at http://www.rfc-editor.org/rfcxx00.html.
7. Relationship with other existing or emerging documents:
RFC 4861 has been in existence since 2007. It obsoletes RFC 2461 and it is updated by RFC 5942.
8. Any explicit references within that referenced document should also be listed:
[ADDR-ARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing/
Architecture", RFC 4291, February 2006./
/
[ICMPv6] Conta, A., Deering, S., and M. Gupta, Ed., "Internet/
Control Message Protocol (ICMPv6) for the Internet/
Protocol Version 6 (IPv6) Specification", RFC 4443,/
March 2006./
/
[IPv6] Deering, S. and R. Hinden, "Internet Protocol, Version 6/
(IPv6) Specification", RFC 2460, December 1998./
/
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997.
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
Note: This form is based on Recommendation ITU-T A.5