dIVI Translation
| IPv6 transition mechanisms |
|---|
| Standards Track |
| Experimental |
| Informational |
|
| Drafts |
|
| Deprecated |
|
dIVI Translation refers to a dual stateless IPv4/IPv6 translation technique. dIVI is an extension of 1:1 stateless IPv4/IPv6 translation (
IPv4 address sharing and dual translation. dIVI-PD is a further extension of dIVI to be well used in Wireline (Fiber, DSL, Cable) and Wireless (3G/4G) access environment, where the prefix delegation (/64 or shorter) is preferred. dIVI-PD is now standardized as MAP-T [1]
in the IETF.
dIVI Translation is intended to benefit the network operators (ISPs) to effectively share the public
DNS64 and ALG
in the network, thereby benefiting the network operator to not deal with any NAT logging etc. dIVI maintains end-to-end address transparency and bidirectional-initiated communications.
How it works
Stateless NAT464 building blocks
- Address translation defined in RFC6052IPv4 address in network specific IPv6 prefixand forms IPv4-converted and IPv4-translatable addresses. The IPv4-converted IPv6 addresses are the IPv6 addresses used to represent IPv4 nodes in an IPv6 network. The IPv4-translatable IPv6 addresses are the IPv6 addresses assigned to IPv6 nodes for use with stateless translation.
- Suffix extension enables multiple IPv6 nodes sharing a single public IPv4 address, with each node managing a different range of ports. This is achieved by defining suffix of the address format RFC6052.[2][3]
- Header translation and ICMP translation defined in RFC6145 .
- Dual stateless translation can restore original IPv4 address. The advantage of stateless NAT464 is that the DNS translation DNS64 and application layer gateway ALG are not needed.[5]
- Prefix extension is only applied to dIVI-PD. It constructs different delegated prefixes for each CPE.[6]
Case study
- Considerations for Stateless Translation (IVI/dIVI) in Large SP Network[7]
IETF
- Stateless Translation techniques have been gaining traction at the IETF as well as production networks. IVI is now an IETF informational RFC, where dIVI is being actively discussed. Many operators have recently submitted a motivation document to push the IETF to standardize Stateless 4v6 techniques such as dIVI.
Stateless 4via6 being advantageous
- Stateless 4Via6 Address Sharing[8] demystifies the upsides with any Statelss 4v6 techniques.
- It is worth pointing out that dIVI/dIVI-PD, unlike CGN44, DS-Lite, CGN64 etc., does not require any Stateful NAT, DNS64 and ALG in the network, thereby benefiting the network operator to not deal with any NAT logging etc.
Relation to IVI Translation
- Due to the stateless nature, the dual stateless translation can easily become single stateless translation by removing the second translator, see IVI Translation.
References
- ^ http://tools.ietf.org/html/draft-ietf-softwire-map-t [dead link]
- ^ RFC 6052IPv6 Addressing of IPv4/IPv6 Translators
- ^ draft-bcx-address-fmt-extension Extended IPv6 Addressing for Encoding Port Range (https://datatracker.ietf.org/doc/draft-bcx-address-fmt-extension/)
- RFC 6145IP/ICMP Translation Algorithm
- ^ draft-xli-behave-divi dIVI: Dual-Stateless IPv4/IPv6 Translation (https://datatracker.ietf.org/doc/draft-xli-behave-divi/)
- ^ draft-xli-behave-divi-pd dIVI-pd: Dual-Stateless IPv4/IPv6 Translation with Prefix Delegation (https://datatracker.ietf.org/doc/draft-xli-behave-divi-pd/)
- ^ draft-sunq-v6ops-ivi-sp Considerations for Stateless Translation (IVI/dIVI) in Large SP Network (https://datatracker.ietf.org/doc/draft-sunq-v6ops-ivi-sp/)
- ^ draft-dec-stateless-4v6 Stateless 4Via6 Address Sharing (https://datatracker.ietf.org/doc/draft-dec-stateless-4v6/)
External links
- www.ivi2.org Archived 2011-11-02 at the Wayback Machine