Re: [MEXT] Subject: Multiple CoA draft 10 -- two proposals and some comments

Conny Larsson <conny.larsson@ericsson.com> Fri, 12 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 6580F3A6AB9; Thu, 11 Dec 2008 21:59:54 -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 2BF843A6AB9 for <mext@core3.amsl.com>; Thu, 11 Dec 2008 21:59:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 C+XLxGO+5Ycg for <mext@core3.amsl.com>; Thu, 11 Dec 2008 21:59:51 -0800 (PST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id C30A73A6AA6 for <mext@ietf.org>; Thu, 11 Dec 2008 21:59:51 -0800 (PST)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 6F0AC20E8F; Fri, 12 Dec 2008 06:59:44 +0100 (CET)
X-AuditID: c1b4fb3c-ae75fbb00000304c-70-4941fdd0d72b
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 5BD7420E33; Fri, 12 Dec 2008 06:59:44 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Dec 2008 06:59:44 +0100
Received: from [127.0.0.1] ([147.214.130.137]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Dec 2008 06:59:44 +0100
Message-ID: <4941FDCE.9050609@ericsson.com>
Date: Fri, 12 Dec 2008 06:59:42 +0100
From: Conny Larsson <conny.larsson@ericsson.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Christian.Kaas-Petersen@tieto.com
References: <D3CFEF84287B46408A7F0405EE7C545701969E24@corvette.eu.tieto.com>
In-Reply-To: <D3CFEF84287B46408A7F0405EE7C545701969E24@corvette.eu.tieto.com>
X-OriginalArrivalTime: 12 Dec 2008 05:59:44.0165 (UTC) FILETIME=[D48E7550:01C95C1E]
X-Brightmail-Tracker: AAAAAA==
Cc: mext@ietf.org
Subject: Re: [MEXT] Subject: Multiple CoA draft 10 -- two proposals and some comments
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

Hi Christian,

Christian.Kaas-Petersen@tieto.com wrote:
> Assume a mobile node with home address HoA has two interfaces,
> both attached to foreign links.  After exchange of binding update
> and binding acknowledgement, the home agent's binding cache (at
> least the snip of it related to HoA) will look like this
>
>     HoA, BID= 7, CoA1, other parameters like period of validity...
>     HoA, BID=10, CoA2, other parameters ...
>
> The draft uses HoA=2001:db8::EUI.
>
> Draft 10, section 5.1 states, that a BID value must be unique for a
> home address and care-of address pair.  This is satisfied above, but
> it means, that the mobile station is not allowed to change the
> second entry such that it also uses CoA1 as care-of address.
>
> Proposal:  I think it has merit to be able to allow more than
> one BID value per pair of home address and care-of address.  Consider
> flow bindings (defined in draft-ietf-mext-flow-binding) where
> a flow may refer to a BID, and thus there is a simple way to move
> flows between interfaces: only updating the binding cache.
>   
I agree with Gerardo. When reading the draft I did not catch this one 
but I agree that the behaviour should be as you have described it above.

Regards
Conny

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