draft-ietf-mip6-nemo-v4traversal-03 [e-mail]

1
draft-ietf-mip6-nemo-v4traversal-03hesham_at_qualco
mm.com
2
Objectives in a Nutshell

• Allow a mobile node to bind a care-of address to
  a home address independently of the address
  family of either address.
• Support for NAT detection and traversal

3
Issues resolved

• Issue 66 Setting up forwarding for the IPv4 HoA
• Issue 60 Lightweight keepalive mechanism
• Issue 76 Alt-CoA should not be used when the MN
  is in an IPv4 network
• Issue 75 Authors on the front page

4
Outstanding issues

• 3 issues outstanding
• Discussion will be done on the mip6 alias
• Issue 71 Dynamic Discovery of NAT
• So far no clear consensus achieved 4 people
  against and 3 people for it.
• New issue Maintaining integrity for the CoA when
  the alt-CoA is not present.
• Some discussion but consensus not yet requested.
  To be finalised.
• Use of mapped addresses
• Not yet discussed on list.

5
Dynamic detection of NAT in the HAs domain

• Current draft assumes that the HA is configured
  with the presence of a NAT in its domain.
• Draft handles dynamic detection of the NAT in
  the MNs domain.
• To detect a NAT in the HAs domain we need to
  include original src and dst port numbers in the
  BU.
• There may be IPR on the solution to this problem.

IPv4
DS-MIPv6
NAT
IPv4/v6
DS-HA
DS-MIPv6
DS-MIPv6
IPv6
6
Issue 73 Use of mapped address

• Mapped addresses are used to represent an IPv4
  CoA in IPv6 format (in src address)
• Mapped addresses are not used for routing or
  exposed on the wire
• Some DT members object to the use of mapped
  addresses because its an implicit indication of
  the existence of an IPv4 address or because it
  adds another address to the interface.
• Need to resolve this issue on the list. Text will
  be sent for both sides of the problem for the WG
  to decide.