1 / 8

draft-ietf-mip6-nemo-v4traversal-02 hesham@qualcomm

draft-ietf-mip6-nemo-v4traversal-02 hesham@qualcomm.com. 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. Issues resolved in this revision.

rangle
Download Presentation

draft-ietf-mip6-nemo-v4traversal-02 hesham@qualcomm

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ietf-mip6-nemo-v4traversal-02hesham@qualcomm.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 in this revision • Assignment of an IPv4 prefix to the MR • Several Editorials • Clarifying the packet formats for normal traffic • Movement detection for IPv4

  4. Outstanding issues • 5 issues outstanding • Discussion will be done on the mip6 alias • Lightweight Keepalives (issue 60) • Dynamic detection of a NAT present in the HA’s domain • Alt-CoA should not be used in BU when located in IPv4 domains. • Use of mapped addresses • Number of authors on the draft

  5. Issue 60 - keepalives • The current keepalive mechanism relies on the BU, in the absence of traffic. • The BU is an expensive mechanism for small mobile devices. • Need a lightweight, ping-like mechanism over UDP.

  6. Dynamic detection of NAT in the HA’s 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 MN’s domain. • To detect a NAT in the HA’s 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

  7. Issue 76: Alt-CoA should not be used in BU • Objection to use of alt-CoA because it makes it harder to detect the presence of NAT. • RFC 3775 requires the use of alt-CoA when ESP is used. When AH is used alt-CoA is needed. • Possible alternatives: • Accept (only use AH) • Accept (relax 3775) • Reject.

  8. 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 it’s 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.

More Related