…ents SHOULD make use of other techniques, e.g., TURN-IPv6 [ RFC6156 ], Teredo [ RFC4380 ], or SOCKS IPv4-IPv6 gatewaying [ RFC3089 ], for obtaining IPv6 candidates. While implementations SHOULD support as many techniques as feasible, they SHOULD also consider which of them to use…

…ents SHOULD make use of other techniques, e.g., TURN-IPv6 [ RFC6156 ], Teredo [ RFC4380 ], or SOCKS IPv4-IPv6 gatewaying [ RFC3089 ], for obtaining IPv6 candidates. While implementations SHOULD support as many techniques as feasible, they SHOULD also consider which of them to use…

…ents SHOULD make use of other techniques, e.g., TURN-IPv6 [ RFC6156 ], Teredo [ RFC4380 ], or SOCKS IPv4-IPv6 gatewaying [ RFC3089 ], for obtaining IPv6 candidates. While implementations SHOULD support as many techniques as feasible, they SHOULD also consider which of them to use…

…al packets contained in the payload. One example of such a protocol is Teredo [ RFC4380 ]. Tunnels establish virtual links that appear to directly connect locations that are distant in the physical Internet topology and can be used to create virtual (private) networks. Using UDP …

…anged from False to "N/A [2]". The [2] footnote now states: * See Section 5 of [RFC4380] for details. o EID Space for LISP (2001:5::/32) - All footnotes have been incremented by 1. o 6to4 (2002::/16) - All footnotes have been incremented by 1. o Unique-Local (fc00::/7) - The Glob…

…the other. Various proposals take that model, including 6to4 [RFC3056], Teredo [RFC4380], Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) [RFC5214], and Dual-Stack Lite [DS-LITE]. The advantage of doing so is that the new protocol is enabled to work without disturbing th…

… section 5.3.1 of [RFC3964] . 2.8 . Teredo 2001::/32 are the Teredo addresses [ RFC4380 ]. The Teredo addresses may be advertised when the site is running a Teredo relay or offering a Teredo transit service. 2.9 . 6bone 5f00::/8 were the addresses of the first instance of the 6bo…

…S. Deering, "IP Version 6 Addressing Architecture", RFC 4291 , February 2006. [ RFC4380 ] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380 , February 2006. [ RFC4862 ] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Addr…

… in section 5.3.1 of [RFC3964]. 2.8. Teredo 2001::/32 are the Teredo addresses [RFC4380]. The Teredo addresses may be advertised when the site is running a Teredo relay or offering a Teredo transit service. 2.9. 6bone 5f00::/8 were the addresses of the first instance of the 6bone…

…S. Deering, "IP Version 6 Addressing Architecture", RFC 4291 , February 2006. [ RFC4380 ] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380 , February 2006. [ RFC4862 ] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Addr…

…----+----------------+ | Address Block | 2001::/32 | | Name | TEREDO | | RFC | [RFC4380] | | Allocation Date | January 2006 | | Termination Date | N/A | | Source | True | | Destination | True | | Forwardable | True | | Global | False | | Reserved-by-Protocol | False | +----------…

…S. Deering, "IP Version 6 Addressing Architecture", RFC 4291 , February 2006. [ RFC4380 ] Huitema, C., "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)", RFC 4380 , February 2006. [ RFC4862 ] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Addr…

… section 5.3.1 of [RFC3964] . 2.8 . Teredo 2001::/32 are the Teredo addresses [ RFC4380 ]. The Teredo addresses may be advertised when the site is running a Teredo relay or offering a Teredo transit service. 2.9 . 6bone 5f00::/8 were the addresses of the first instance of the 6bo…

…---+----------------+ | Address Block | 2001::/32 | | Name | TEREDO | | RFC | [ RFC4380 ] | | Allocation Date | January 2006 | | Termination Date | N/A | | Source | True | | Destination | True | | Forwardable | True | | Global | False | | Reserved-by-Protocol | False | +---------…

…09 N/A False [ 1 ] False [ 1 ] False [ 1 ] False [ 1 ] False 2001::/32 TEREDO [ RFC4380 ] [ RFC8190 ] 2006-01 N/A True True True N/A [ 2 ] False 2001:1::1/128 Port Control Protocol Anycast [ RFC7723 ] 2015-10 N/A True True True True False 2001:1::2/128 Traversal Using Relays arou…