[MEXT] Removing bindings for IPv4 only - please comment

[Hesham Soliman <hesham at elevatemobile.com>]

Hi all, 

Gerardo requested that we consider the issue of removing an IPv4-only
bindings in the spec. We discussed this with the chairs and it seemed like a
simple add-on to the spec. I'm still wondering if this is the same thing
that Karen asked for earlier and we decided to do it separately. If it is,
then I don't understand why we didn't consider the following solution (can't
remember if I suggested it before).

I've added the following text to the draft, please let me know if you have
any comments ASAP. I want to submit this version on the weekend if possible.
All the IESG comments have been included. It's pretty straight forward and
follows standard MIPv6 logic.

<section title="Removing Bindings">
                   
<t>Mobile nodes will remove bindings from the home agent's binding cache
whenever they move to the home link, or simply when mobility support is not
needed.</t>

<t>De-registering the IPv6 home address is described in <xref
target="RFC3775"/>. The same mechanism applies in this specification. Mobile
nodes may remove the binding for the IPv4 home address only, by sending a
binding update that does not include the IPv4 home address option. Upon
receiving this binding update, the home agent will replace the existing
cache entries with the content of the new message. This ensures that the
IPv4 home address binding is removed, while maintining an IPv6 binding.</t>

<t>Note that the mobile node cannot remove the IPv6 home address binding
while maintaining an IPv4 home address binding.</t>
                   
<t>A binding update message with a lifetime of zero, will remove all
bindings for the mobile node.</t>
</section>

Hesham


_______________________________________________
MEXT mailing list
MEXT at ietf.org
https://www.ietf.org/mailman/listinfo/mext