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

<Christian.Kaas-Petersen@tieto.com> Fri, 12 December 2008 07:59 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 8E8473A6A9C; Thu, 11 Dec 2008 23:59:45 -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 2F3433A6A9C for <mext@core3.amsl.com>; Thu, 11 Dec 2008 23:59:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.244
X-Spam-Level:
X-Spam-Status: No, score=-6.244 tagged_above=-999 required=5 tests=[AWL=-0.245, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 XTRDvluqxN6e for <mext@core3.amsl.com>; Thu, 11 Dec 2008 23:59:43 -0800 (PST)
Received: from tietoe03.tietoenator.com (datnt07.tieto.com [194.110.47.24]) by core3.amsl.com (Postfix) with ESMTP id 1ED3F3A69EC for <mext@ietf.org>; Thu, 11 Dec 2008 23:59:41 -0800 (PST)
X-AuditID: c26e2f18-00001a2400000510-37-49421a181ce2
Received: from stingray.eu.tieto.com ([192.176.143.13]) by tietoe03.tietoenator.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Dec 2008 10:00:24 +0200
Received: from corvette.eu.tieto.com ([192.176.143.143]) by stingray.eu.tieto.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Dec 2008 08:59:34 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 12 Dec 2008 08:59:32 +0100
Message-ID: <D3CFEF84287B46408A7F0405EE7C545701969F72@corvette.eu.tieto.com>
In-Reply-To: <C5684F86.AAE2%hesham@elevatemobile.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] Removing bindings for IPv4 only - please comment
Thread-Index: AclcIrfbppqowVDjTEy3HFmjbORgHQAC7YeQ
References: <C5684F86.AAE2%hesham@elevatemobile.com>
From: <Christian.Kaas-Petersen@tieto.com>
To: <hesham@elevatemobile.com>, <mext@ietf.org>
X-OriginalArrivalTime: 12 Dec 2008 07:59:34.0700 (UTC) FILETIME=[927306C0:01C95C2F]
X-Brightmail-Tracker: AAAAAA==
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.   

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