… specification was originally published as [ RFC5766 ] , which was updated by [ RFC6156 ] to add IPv6 support. This document supersedes and obsoletes both [ RFC5766 ] and [ RFC6156 ] . ¶ 2. Terminology The key words " MUST ", " MUST NOT ", " REQUIRED ", " SHALL ", " SHALL NOT ", …
…addressing, then clients 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 …
…k clients. A proxy MAY provide both IPv4 and IPv6 remote addresses to clients [ RFC6156 ]. A client SHOULD request both address families. If both requests are granted, the client SHOULD treat the two addresses as host candidates on a dual-stack virtual interface. 5.7 . Unspecifie…
…addressing, then clients 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 …
…addressing, then clients 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 …