Re: [MEXT] De-resgistering bindings in MCoA draft

Hesham Soliman <hesham@elevatemobile.com> Wed, 17 December 2008 07:12 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 861BE3A6AB6; Tue, 16 Dec 2008 23:12:48 -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 5F4AC3A6904 for <mext@core3.amsl.com>; Tue, 16 Dec 2008 23:12:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level:
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599]
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 BJDfqKHAGdPI for <mext@core3.amsl.com>; Tue, 16 Dec 2008 23:12:46 -0800 (PST)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 820CF3A6AB6 for <mext@ietf.org>; Tue, 16 Dec 2008 23:12:46 -0800 (PST)
Received: from [124.190.106.160] (helo=[192.168.0.187]) by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1 (Debian)) id 1LCqaD-0001B9-2f; Wed, 17 Dec 2008 18:12:37 +1100
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Wed, 17 Dec 2008 18:12:32 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
Message-ID: <C56EF190.AC10%hesham@elevatemobile.com>
Thread-Topic: [MEXT] De-resgistering bindings in MCoA draft
Thread-Index: AclgFtQNdz5IUFyjjUi+qBJ9ZOJgpg==
In-Reply-To: <m23agn9z49.wl%ryuji.wakikawa@gmail.com>
Mime-version: 1.0
Cc: "mext@ietf.org" <mext@ietf.org>
Subject: Re: [MEXT] De-resgistering bindings in MCoA draft
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

> When MN does not use the bulk registration, each binding registering
> with BID is treated as a regular binding. Each binding will have
> individual lifetime. It is not the operation of BID removal, but of a binding
> removal.

=> It's the same thing, you won't remove a BID and keep the binding.

> Removing a binding with zero lifetime is consisitent with MIP6.

=> Yes but that's not the issue, the issue here is having multiple bindings
for the same home address that have different lifetimes.

Hesham

> 
> ryuji
> 
> 
> 
> 
> 
> At Wed, 17 Dec 2008 00:43:33 +1100,
> Hesham Soliman wrote:
>> 
>> Hi, 
>> 
>> I have a comment on this aspect of the spec. The removal of BIDs based on
>> zero lifetime is completely inconsistent with the processing of the BU in
>> MIPv6. The lifetime should be for the entire binding cache for the home
>> address. BIDs should be removed by explicitly by requesting a removal
>> operation in the BID fields (or by simply excluding them from the new BU),
>> not by giving them separate lifetimes. I don't see any reason for
>> complicating things this way. This is not how a binding update is supposed
>> to work. The way it works is that one BU replaces the previous one.
>> 
>> 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