Re: [MEXT] Removing bindings for IPv4 only - please comment

Hesham Soliman <hesham@elevatemobile.com> Fri, 12 December 2008 12:37 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: monami6-archive@megatron.ietf.org
Delivered-To: ietfarch-monami6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 125563A696A; Fri, 12 Dec 2008 04:37:06 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 934233A696A for <mext@core3.amsl.com>; Fri, 12 Dec 2008 04:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level:
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=-0.305, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLItSEdaop6G for <mext@core3.amsl.com>; Fri, 12 Dec 2008 04:37:03 -0800 (PST)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id A77F03A67D4 for <mext@ietf.org>; Fri, 12 Dec 2008 04:37:02 -0800 (PST)
Received: from [124.190.106.160] (helo=[192.168.0.187]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1 (Debian)) id 1LB7GH-0000vg-BY; Fri, 12 Dec 2008 23:36:53 +1100
User-Agent: Microsoft-Entourage/12.14.0.081024
Date: Fri, 12 Dec 2008 23:36:47 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: <Christian.Kaas-Petersen@tieto.com>, <mext@ietf.org>
Message-ID: <C568A60F.AAF3%hesham@elevatemobile.com>
Thread-Topic: [MEXT] Removing bindings for IPv4 only - please comment
Thread-Index: AclcIrfbppqowVDjTEy3HFmjbORgHQAC7YeQAAn3hrs=
In-Reply-To: <D3CFEF84287B46408A7F0405EE7C545701969F72@corvette.eu.tieto.com>
Mime-version: 1.0
Cc: julien.laganier.ietf@googlemail.com, jari.arkko@piuha.net
Subject: Re: [MEXT] Removing bindings for IPv4 only - please comment
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

> Fine with the addition.  The original suggestion of Karen, now
> described in draft-premec-mext-extended-home-link, is something
> different, namely maintaining both IPv4 and IPv6 home addresses
> on a home link which gives native support for either IPv4 or IPv6.
> Suppose the home link supports only IPv4.  The home agent will
> remove the entry for the v4HoA address, retaining the entry
> for the v6HoA, and this entry will indicate packets for v6HoA
> will have to be IP-in-IP tunneled to v4HoA.

=> Right, but this is what the text I sent does. It removes the v4 binding
and keeps the IPv6 binding. If the link is IPv4 only then it will bind the
v6 HoA to that IPv4 address.

Hesham

> 
> Christian
> 
>> -----Original Message-----
>> From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On
>> Behalf Of Hesham Soliman
>> Sent: 12. december 2008 07:28
>> To: mext@ietf.org
>> Cc: Jari Arkko; Julien Laganier
>> Subject: [MEXT] Removing bindings for IPv4 only - please comment
>> 
>> 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@ietf.org
>> https://www.ietf.org/mailman/listinfo/mext
>> 


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