…v4-compatible addresses [ RFC4291 ], IPv4-mapped [ RFC4291 ], IPv4- converted [ RFC6145 ], IPv4-translatable [ RFC6145 ], and 6to4 addresses [ RFC3056 ] contain an embedded IPv4 address. For the purposes of this document, these addresses MUST be treated as having global scope. IP…
…v4-compatible addresses [ RFC4291 ], IPv4-mapped [ RFC4291 ], IPv4- converted [ RFC6145 ], IPv4-translatable [ RFC6145 ], and 6to4 addresses [ RFC3056 ] contain an embedded IPv4 address. For the purposes of this document, these addresses MUST be treated as having global scope. IP…
…Translation June 2016 1 . Introduction and Motivation This document obsoletes [ RFC6145 ]. Readers of this document are expected to have read and understood the framework described in [ RFC6144 ]. Implementations of this IPv4/IPv6 translation specification MUST support one or mor…
…Translation June 2016 1 . Introduction and Motivation This document obsoletes [ RFC6145 ]. Readers of this document are expected to have read and understood the framework described in [ RFC6144 ]. Implementations of this IPv4/IPv6 translation specification MUST support one or mor…
…4 address). The generic IPv4-to-IPv6 header translation procedures outlined in [RFC6145] apply throughout. The resulting IPv6 packets are then passed to regular IPv6 forwarding. Note that the operation of a BR, when forwarding to/from MAP-T domains that are defined without IPv4 a…
…4 address). The generic IPv4-to-IPv6 header translation procedures outlined in [RFC6145] apply throughout. The resulting IPv6 packets are then passed to regular IPv6 forwarding. Note that the operation of a BR, when forwarding to/from MAP-T domains that are defined without IPv4 a…