…ranges have been defined in the IETF, including the IPv6 documentation prefix [ RFC3849 ] and example domain names [ RFC2606 ]. Documentation also makes use of the ranges reserved in [ RFC1918 ]. 2 . Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", …
…ranges have been defined in the IETF, including the IPv6 documentation prefix [ RFC3849 ] and example domain names [ RFC2606 ]. Documentation also makes use of the ranges reserved in [ RFC1918 ]. 2 . Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", …
…s been assigned as a NON-ROUTABLE range to be used for documentation purposes [ RFC3849 ]. [ 3 ] 2002::/16 is reserved for use in 6to4 deployments [ RFC3056 ] [ 4 ] 3FFE::/16 is an experimental allocation to the 6BONE [ RFC2471 ]. This prefix will be returned to the unassigned ad…
…]. 2.6. Documentation Prefix The 2001:db8::/32 are the documentation addresses [RFC3849]. They are used for documentation purposes such as user manuals, RFCs, etc. Addresses within this block should not appear on the public Internet. 2.7. 6to4 2002::/16 are the 6to4 addresses [RF…
…----------+ | Address Block | 2001:db8::/32 | | Name | Documentation | | RFC | [RFC3849] | | Allocation Date | July 2004 | | Termination Date | N/A | | Source | False | | Destination | False | | Forwardable | False | | Global | False | | Reserved-by-Protocol | False | +----------…
… DOI 10.17487/RFC3810, June 2004, < http://www.rfc-editor.org/info/rfc3810 >. [ RFC3849 ] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849 , DOI 10.17487/RFC3849, July 2004, < http://www.rfc-editor.org/info/rfc3849 >. [ RFC4302 ] Kent…
… DOI 10.17487/RFC3810, June 2004, < http://www.rfc-editor.org/info/rfc3810 >. [ RFC3849 ] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Reserved for Documentation", RFC 3849 , DOI 10.17487/RFC3849, July 2004, < http://www.rfc-editor.org/info/rfc3849 >. [ RFC4302 ] Kent…
…---------+ | Address Block | 2001:db8::/32 | | Name | Documentation | | RFC | [ RFC3849 ] | | Allocation Date | July 2004 | | Termination Date | N/A | | Source | False | | Destination | False | | Forwardable | False | | Global | False | | Reserved-by-Protocol | False | +---------…
… 2.6 . Documentation Prefix The 2001:db8::/32 are the documentation addresses [ RFC3849 ]. They are used for documentation purposes such as user manuals, RFCs, etc. Addresses within this block should not appear on the public Internet. 2.7 . 6to4 2002::/16 are the 6to4 addresses […
…les in Table 1 are derived from the IPv6 prefix reserved for documentation in [ RFC3849 ]. The IPv4 address 192.0.2.33 is part of the subnet 192.0.2.0/24 reserved for documentation in [ RFC5735 ]. The representation of IPv6 addresses is compatible with [ RFC5952 ]. . Deployment G…
…V6 ; and have no authority over any parts of 10.0.0.0/8 RFC1918 , 2001:db8::/32 RFC3849 , and AS 64512 - 65534 RFC6996 , for example. Since it's not possible to transfer private internet allocations, documentation prefixes, or private use ASNs into an RIR's management, such resou…
…[ RFC9374 ] 2022-12 N/A True True True True False 2001:db8::/32 Documentation [ RFC3849 ] 2004-07 N/A False False False False False 2002::/16 [ 3 ] 6to4 [ RFC3056 ] 2001-02 N/A True True True N/A [ 3 ] False 2620:4f:8000::/48 Direct Delegation AS112 Service [ RFC7534 ] 2011-05 N/…
[ RFC3849 ] introduced the IPv6 address prefix 2001:db8::/32 as a reserved prefix for use in documentation. The rationale for this reservation was to reduce the likelihood of conflict and confusion when relating documented examples to deployed systems. ¶ As the global deployment …
…https://rdap.apnic.net/ ALLOCATED 2001:db8::/32 is reserved for Documentation [ RFC3849 ]. See [ IPv6 Special-Purpose Address Space ] for details. 2001:e00::/23 APNIC 2003-01-01 whois.apnic.net https://rdap.apnic.net/ ALLOCATED 2001:1200::/23 LACNIC 2002-11-01 whois.lacnic.net ht…