|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5969 (2010)
|
|
Title:
|
IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC
|
|
3.
|
Justification for the specific reference:
|
|
|
None.
|
|
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=5969
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standards Track RFC approved August 2010.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards Track RFC approved August 2010.Errata Exist.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Supersedes none.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G.,/
and E. Lear, "Address Allocation for Private/
Internets", BCP 5, RFC 1918, February 1996./
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP/
Vendor Extensions", RFC 2132, March 1997./
[RFC2491] Armitage, G., Schulter, P., Jork, M., and G. Harter,/
"IPv6 over Non-Broadcast Multiple Access (NBMA)/
networks", RFC 2491, January 1999./
[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6/
Domains via IPv4 Clouds", RFC 3056, February 2001./
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The/
Addition of Explicit Congestion Notification (ECN) to/
IP", RFC 3168, September 2001./
[RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition/
Mechanisms for IPv6 Hosts and Routers", RFC 4213,/
October 2005./
[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./
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J./
Schoenwaelder, Ed., "Structure of Management/
Information Version 2 (SMIv2)", STD 58, RFC 2578,/
April 1999./
[RFC2983] Black, D., "Differentiated Services and Tunnels",/
RFC 2983, October 2000./
[RFC3068] Huitema, C., "An Anycast Prefix for 6to4 Relay/
Routers", RFC 3068, June 2001./
[RFC3484] Draves, R., "Default Address Selection for Internet/
Protocol version 6 (IPv6)", RFC 3484, February 2003./
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for/
Dynamic Host Configuration Protocol (DHCP) version 6",/
RFC 3633, December 2003./
[RFC3964] Savola, P. and C. Patel, "Security Considerations for/
6to4", RFC 3964, December 2004./
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing/
(CIDR): The Internet Address Assignment and/
Aggregation Plan", BCP 122, RFC 4632, August 2006./
[RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site/
Automatic Tunnel Addressing Protocol (ISATAP)",/
RFC 5214, March 2008./
[RFC5569] Despres, R., "IPv6 Rapid Deployment on IPv4/
Infrastructures (6rd)", RFC 5569, January 2010./
[RoutingLoop] Nakibly and Arov, "Routing Loop Attacks using IPv6/
Tunnels", August 2009, http://www.usenix.org/event//
woot09/tech/full_papers/nakibly.pdf./
[TR069] "TR-069, CPE WAN Management Protocol v1.1, Version:/
Issue 1 Amendment 2", December 2007./
[V6OPS-LOOPS] Nakibly, G. and F. Templin, "Routing Loop Attack using/
IPv6 Automatic Tunnels: Problem Statement and Proposed/
Mitigations", Work in Progress, May 2010./
|
|
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
|
|
