1. Click to edit Master title style Click to add subtitle © 2008 Wichorus Inc. All rights reserved. CONFIDENTIAL - DO NOT DISTRIBUTE rfc3775bis Issues March 24, 2009 charliep@wichorus.com

2. Click to edit Master title style Existing and new issues Recent revision includes updates for all previous issues  They are already closed or will be closed soon Four new issues identified during discussion following IETF 73 Need to discuss whether to accept these issues for further revision of rfc3775bis, and if accepted to get text.

3. Click to edit Master title style Four issues identified 1. BU de-registration race condition 2. Malicious RA ==> mobile node deregistration on foreign network 3. Additional specification about saving source address of packets containing the Alt-CoA option. 4. Relaxing the mandate on the use of IPsec (given RFC 4285)

4. Click to edit Master title style BU de-registration race condition MN returns home and sends a BU de-registration HA deletes the BCE What if MN’s previous BU was delayed? HA might well accept the delayed BU as a brand new registration, not checking sequence # Accept as issue?

5. Click to edit Master title style Malicious RA ==> mobile node deregistration If a malicious router advertises the mobile node’s home prefix, the mobile node can be fooled into thinking it is back home It issues a deregistration BU. This is bad enough, but the BA will not arrive. The malicious router could snoop the BU, and relay it via another interface to the home network. Then the mobile node is truly deregistered Solutions aren’t easy (personal opinion)

6. Click to edit Master title style More specification about Alt-COA Does the home agent have to save more information about the source address of the packet? Strong disagreement about whether anything is needed; current draft could be considered sufficient, but not everyone is convinced

7. Click to edit Master title style Discussion about IPsec vs. Mobile IPv6 Proposal: to relax the mandate This really is a complicated subject Any resolution is likely to introduce significant changes to the design of Mobile IPv6 Suggested disposition for this issue: do not accept for rfc3775bis However, see later presentation