|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2461 (1998)
|
|
Title:
|
T. Narten, E. Nordmark, W. Simpson, Neighbor Discovery for IP Version 6 (IPv6), December 1998
|
|
|
2.
|
Status of approval:
|
|
|
Draft Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC2461 deals with NDP 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=2461
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
At least two independent, interoperable implementations and sufficient successful operational experience exist; if IPR issues are known, then independent implementations must be based on at least two separate exercises of the licensing process; considered mature and final form of specification
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
At least two independent, interoperable implementations and sufficient successful operational experience exist; if IPR issues are known, then independent implementations must be based on at least two separate exercises of the licensing process; considered mature and final form of specification
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
IETF RFC 2461 Obsoletes RFC 1970, Updated by RFC 4311
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ADDRCONF] Thomson, S. and T. Narten, "IPv6 Address/
Autoconfiguration", RFC 2462, December 1998./
/
[ADDR-ARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing/
Architecture", RFC 2373, July 1998./
/
[ANYCST] Partridge, C., Mendez, T. and W. Milliken, "Host/
Anycasting Service", RFC 1546, November 1993./
/
[ARP] Plummer, D., "An Ethernet Address Resolution Protocol",/
STD 37, RFC 826, November 1982./
/
[HR-CL] Braden, R., Editor, "Requirements for Internet Hosts --/
Communication Layers", STD 3, RFC 1122, October 1989./
/
[ICMPv4] Postel, J., "Internet Control Message Protocol", STD 5,/
RFC 792, September 1981./
/
[ICMPv6] Conta, A. and S. Deering, "Internet Control Message/
Protocol (ICMPv6) for the Internet Protocol Version 6/
(IPv6) Specification", RFC 2463, December 1998./
/
[IPv6] Deering, S. and R. Hinden, "Internet Protocol, Version 6/
(IPv6) Specification", RFC 2460, December 1998./
/
[IPv6-ETHER] Crawford, M., "Transmission of IPv6 Packets over/
Ethernet Networks", RFC 2464, December 1998./
/
[IPv6-SA] Kent, S. and R. Atkinson, "Security Architecture for the/
Internet Protocol", RFC 2401, November 1998./
/
[IPv6-AUTH] Kent, S. and R. Atkinson, "IP Authentication Header",/
RFC 2402, November 1998./
/
[IPv6-ESP] Kent, S. and R. Atkinson, "IP Encapsulating Security/
Payload (ESP)", RFC 2406, November 1998./
/
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RDISC] Deering, S., "ICMP Router Discovery Messages", RFC 1256,/
September 1991./
/
[SH-MEDIA] Braden, R., Postel, J. and Y. Rekhter, "Internet/
Architecture Extensions for Shared Media", RFC 1620, May/
1994./
/
[ASSIGNED] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", STD 2,/
RFC 1700, October 1994. See also:/
http://www.iana.org/numbers.html/
/
[SYNC] S. Floyd, V. Jacobson, "The Synchronization of Periodic/
Routing Messages", IEEE/ACM Transactions on Networking,/
April 1994. ftp://ftp.ee.lbl.gov/papers/sync_94.ps.Z
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
