80 likes | 203 Views
This document outlines the applicability of SIIT (RFC 2765) and NAT-PT (RFC 2766) in facilitating the transition from IPv4 to IPv6 networks. It discusses the limitations of SIIT, including issues with IPv4-mapped addresses, ICMP error message handling, multicast, and IPsec support. The document also examines the challenges faced by NAT-PT, such as application-level gateways (ALG) and DNS-ALG issues. The report is crucial for understanding how these protocols can assist legacy systems, especially in special-purpose networks like 3GPP, particularly for IMS applications needing communication across different IP versions.
E N D
NAT-PT Applicability V6OPS WG IETF 58, Minneapolis
Design Team Members • Peter Barany • Karim El-Malki • Howard H. Wang • Rob Austein • Satomi Okazaki • Senthil Sivakumar • Suresh Satapati
Goals To document the applicability of • SIIT (RFC 2765) • NAT-PT (RFC 2766)
SIIT Limitations • Usage of IPv4-mapped addresses • Translation Semantics – ICMP error messages (embedded headers), parameter problem • Multicast will not work • Limited support for IPsec ESP Transport mode (doesn’t support ICMP) • IPsec ESP tunnel mode, AH doesn’t work
NAT-PT Limitations • Difficult to cope up with ALG model to support applications • All SIIT limitations + IPsec ESP transport mode doesn’t work • DNS-ALG • Failure modes for AAAA queries in IPv6->IPv4 direction
Applicability • SIIT • header conversion algorithm is useful • IPv6 hosts are *really* not IPv6-only • RSIP style
Applicability (contd.) • NAT-PT • Legacy v4 nodes • Special purpose networks – 3gpp • 3GPP hosts, running SIP-based IMS applications over IPv6, must be able to communicate with IPv4 SIP hosts • For IMS media translation • a proxy supplies the mapping as opposed to SIP-ALG
Next steps • WG item ?