IPv6 Address Prefixes Reserved for Documentation
Resumo
RFC3849 specified an IPv6 prefix to be used in documentation, in order to reduce the likelihood of conflict and confusion when relating examples of deployed systems. This prefix was reserved to be used in examples in RFCs, books, documentation, and the like. It became widely accepted and used. Although the IPv6 documentation prefix proved to be very useful, a /32 prefix is not enough to be used to document some kinds of IPv6 deployments, such as large ISP deployments, transition techniques, and other useful examples that require longer prefixes. This document defines the allocation of a new global unicast (GUA) block and a new unique local (ULA) block, to expand the range of documentation blocks. It also updates RFC3849.
Referências
IETF RFC1918 (1996). Address Allocation for Private Internets. http://tools.ietf.org/html/rfc1918, March, 2014.
IETF RFC2606 (1999). Reserved Top Level DNS Names. http://tools.ietf.org/html/rfc2606, March, 2014.
IETF RFC3849 (2004). IPv6 Address Prex Reserved for Documentation. http://tools.ietf.org/html/rfc3849, March, 2014.
IETF RFC5737 (2010). IPv4 Address Blocks Reserved for Documentation. http://tools.ietf.org/html/rfc5737, March, 2014.
IETF RFC5969 (2010). IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) Protocol Specication. http://tools.ietf.org/html/rfc5969, March, 2014.
IETF RFC6052 (2010). http://tools.ietf.org/html/rfc6052, March, 2014. IPv6 Addressing of IPv4/IPv6 Translators.
IETF RFC6877 (2013). 464XLAT: Combination of Stateful and Stateless Translation. http://tools.ietf.org/html/rfc6877, March, 2014.
IETF RFC6996 (2014). Autonomous System (AS) Reservation for Private Use. http://tools.ietf.org/html/rfc6996, March, 2014.