…es, 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 if multiple options are available. Since di…
….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 if multiple options are available. Since d…
….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 if multiple options are available. Since d…
….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 if multiple options are available. Since d…
…de doesn't work well across NATs without extra support such as SOCKS [RFC1928] [RFC3089]. Across NATs, it generally uses passive mode. However, the designers of FTP wrote different and incompatible passive-mode implementations for IPv4 and IPv6 networks. Hence, either they need t…