60 likes | 356 Views
Behcet Sarikaya Frank Xia November 2010. NAT64 for DSMIPv6 IETF 79. http:// tools.ietf.org/id/draft-sarikaya-behave-mext-nat64-dsmip-01.txt. Problem Statement. IPv6-only mobile node NAT64 Pref A for IPv4-only server in domain A
E N D
BehcetSarikayaFrank XiaNovember 2010 NAT64 for DSMIPv6IETF 79 http://tools.ietf.org/id/draft-sarikaya-behave-mext-nat64-dsmip-01.txt
Problem Statement IPv6-only mobile node NAT64 Pref A for IPv4-only server in domain A MN moves to domain B where NAT64 Pref B for the same IPv4-only server, MN continues to use the same synthetic IPv6 address so the packet will not get translated Or MN does DNS query locally gets Pref B then IPv6 packets take longer path MN initiates RO, sends HoTI NAT64 drops No multicast support NAT keep-alives drain MN battery
Solution MN mobility is handled by DSMIPv6 DNS64 no change HA keeps NAT64 state linked to the binding cache but NAT64 can be a separate box Handover operations HA instead of MN does keep-alives by sending ICMPv6 Echo Request messages
Why is it relevant to Mext? • IPv6-only MN behaviour is not defined and this draft defines it • DSMIPv6 (RFC 5555) defines IPv4-only MN • DSMIPv6 does not define multicast support • This draft defines multicast support for IPv6-only MN • Based on bidirectional tunneling approach defined in MIPv6 • HA supports IGMP and MLD/IGMP packet translation • Both ASM and SSM are supported
Next Steps Is there interest in WG?