|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4443 (2006)
|
|
Title:
|
Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification. A. Conta, S. Deering, M. Gupta March 2006.
|
|
|
2.
|
Status of approval:
|
|
|
Standards track, Draft Standard RFC
|
|
3.
|
Justification for the specific reference:
|
|
|
The router discovery mechanism which is part of ICMPv6 can be used for configuration of the gateway of BIP endpoints in IPv6.
|
|
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=4443
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Document published in March 2006 (http://www.ietf.org/rfc/rfc4443.txt). The status is DRAFT STANDARD.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Document published in March 2006 (http://www.ietf.org/rfc/rfc4443.txt). Updated by RFC 4884. Errata Exist. Obsoletes RFC 2463 and updates RFC 2780.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
ICMPv6 is used by all IPv6 systems and referenced by other IPv6 RFC..
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[IPv6] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998./
[IPv6-DISC] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998./
[RFC-792] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, September 1981./
[RFC-2463] Conta, A. and S. Deering, "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", RFC 2463, December 1998./
[RFC-1122] Braden, R., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989./
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC-3978] Bradner, S., "IETF Rights in Contributions", BCP 78, RFC 3978, March 2005./
[RFC-2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers", BCP 37, RFC 2780, March 2000./
[IPv6-ADDR] Hinden, R. and S. Deering, "Intpernet Protocol Version 6 (IPv6) Addressing Architecture", RFC 3513, April 2003./
[PMTU] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery for IP version 6", RFC 1981, August 1996./
[IPv6-SA] Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998./
[IPv6-AUTH] Kent, S., "IP Authentication Header", RFC 4302, December 2005./
[IPv6-ESP] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4203, December 2005./
[SEC-ARCH] Kent, S. and K. Seo, "Security Architecture for the Internet Protocol", RFC 4301, December 2005./
[TCP-attack] Gont, F., "ICMP attacks against TCP", Work in Progress./
|
|
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
|
|
