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

Ryuji Wakikawa <ryuji.wakikawa@gmail.com> Wed, 17 December 2008 05: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 B02383A6AE9; Tue, 16 Dec 2008 21:59:26 -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 2E7823A6AEB for <mext@core3.amsl.com>; Tue, 16 Dec 2008 21:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 einUg-wWt2CO for <mext@core3.amsl.com>; Tue, 16 Dec 2008 21:59:24 -0800 (PST)
Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.231]) by core3.amsl.com (Postfix) with ESMTP id 212D73A6AD0 for <mext@ietf.org>; Tue, 16 Dec 2008 21:59:24 -0800 (PST)
Received: by qb-out-0506.google.com with SMTP id d11so1859317qbd.41 for <mext@ietf.org>; Tue, 16 Dec 2008 21:59:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:message-id:from:to:cc :subject:in-reply-to:references:user-agent:organization:mime-version :content-type; bh=EdxltWT4HAvOYDZ/q8pZki5a1TPTCGxqgB24ajJySEk=; b=GZcKE6Dx00PLzJnpp44BREQVDOb6JO2+8KH0EawpedqTzrrfwmFVLPl7AyKgURVJiE PxGDYgZ5Fp6gugOFbpj+vlz1B4UI6rk830zLptn3/9aT7d3Lof1fzdql6k18X+cNqd8s gtfecO4sRDKN7jU13KwJ0jDwUdYSPLM5TtAek=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:message-id:from:to:cc:subject:in-reply-to:references :user-agent:organization:mime-version:content-type; b=mw5Lvy4iX4UYPcWr/UPRuP4hYTDK3O/H/Lk/fxmw5JjTlJyqCAHZffUHiHnvCA9BCy lXj+dX3rRHTdFViw8J3gKucKlX1boyG2YrNc4pG02pxUbE22/M0atcj98EEbGWQtVOkV jj7kfe6r1eWFho+gH540UFiJMoShhJCAp2Isc=
Received: by 10.142.234.16 with SMTP id g16mr144718wfh.264.1229493555857; Tue, 16 Dec 2008 21:59:15 -0800 (PST)
Received: from ryuji-wakikawa-no-macbook-pro.local.sfc.wide.ad.jp (yamate242.jp.toyota-itc.com [61.200.198.242]) by mx.google.com with ESMTPS id 24sm1856061wff.37.2008.12.16.21.59.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 16 Dec 2008 21:59:15 -0800 (PST)
Date: Wed, 17 Dec 2008 13:58:30 +0900
Message-ID: <m23agn9z49.wl%ryuji.wakikawa@gmail.com>
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
To: Hesham Soliman <hesham@elevatemobile.com>
In-Reply-To: <C56DFBB5.ABBF%hesham@elevatemobile.com>
References: <C56DFBB5.ABBF%hesham@elevatemobile.com>
User-Agent: Wanderlust/2.14.1 (Bad Medicine-pre) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1 (i386-apple-darwin9) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
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

Hesham,

When you use the bulk registration, all bindings share the same lifetime
specified in BU message.  This is what you proposed here.  We also
have specified Overwrite flag to explicitly replace all the bindings
corresponding to the home address.

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.
Removing a binding with zero lifetime is consisitent with MIP6.

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