IVI Translation

IVI Translation refers to a stateless IPv4/IPv6 translation technique.[1] It allows hosts in different address families (IPv4 and IPv6) communicate with each other and keeps the end-to-end address transparency.[2]

Stateless NAT64 (IVI)
IPv6 transition mechanisms
Standards Track
Experimental
Informational
Drafts
Deprecated
  • NAT-PT
  • NAPT-PT

Stateless NAT64 can be used in 4 different scenarios:[3]

  • An IPv6 network to the IPv4 Internet
  • The IPv4 Internet to an IPv6 network
  • An IPv6 network to an IPv4 network
  • An IPv4 network to an IPv6 network

Stateless NAT64 is a replacement of SIIT (RFC 6145).

How it works

Stateless NAT64 building blocks
  • Address translation defined in RFC 6052 [4] is a stateless mapping scheme, which embeds IPv4 address in network specific IPv6 prefix and 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.
  • Header translation and ICMP translation defined in RFC 6145 [5] are algorithms to perform header translation between IPv4 and IPv6, as well as between ICMP and ICMPv6.
  • DNS record translation (DNS64) defined in RFC 6147 [6] describes mapping from A record to AAAA record defined in RFC 6052.[4]

Stateless NAT64 extensions
  • Address sharing stateless NAT64 enables multiple IPv6 nodes sharing a single public IPv4 address, with each node managing a different range of ports. This can be achieved by defining suffix of the address format RFC 6052.[4][7]
  • Dual stateless translation is also called dIVI Translation. Due to the stateless nature, after the second translation, the original IPv4 address can be restored. The advantage of stateless NAT464 is that the DNS64 and application-level gateway (ALG) are not needed.

Case study
  • RFC 6219: China Education and Research Network (CERNET)'s IVI translation design and deployment for the IPv4/IPv6 coexistence and transition.[2]
  • RFC 7599: MAP-T is being used on the IPv6-only "CERNET2", expanding on the work done with CERNET. [8]

Relation to Stateful NAT64
  • The stateless NAT64 also forms the basic building blocks for stateful NAT64. Additional building block is the maintaining of the translation states defined in RFC 6146.[9]

Relation to Stateless NAT464 (dIVI, dIVI-PD)
  • Due to stateless nature, the second stateless translator can be introduced to translate the IPv4-translatable IPv6 address back to IPv4. In this case, the DNS64 and ALG are not required. See dIVI Translation
gollark: Uninterceptable except via actual internet meddling.
gollark: Or a dedicated websockets server.
gollark: .
gollark: You need to run an encryption layer over skynet or modem
gollark: Isn't secure.

References
  1. http://www.ivi2.org/
  2. RFC 6219 China Education and Research Network (CERNET)'s IVI translation design and deployment for the IPv4/IPv6 coexistence and transition
  3. RFC 6144 Framework for IPv4/IPv6 Translation
  4. RFC 6052 IPv6 Addressing of IPv4/IPv6 Translators
  5. RFC 6145 IP/ICMP Translation Algorithm
  6. RFC 6147 DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
  7. draft-bcx-address-fmt-extension Extended IPv6 Addressing for Encoding Port Range (https://datatracker.ietf.org/doc/draft-bcx-address-fmt-extension/)
  8. https://blog.apnic.net/2017/01/31/chinas-first-ipv6-backbone-network-connect-1200-campuses/
  9. RFC 6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.