Re: [MEXT] draft-arkko-mext-rfc3775-altcoa-check-00.txt

Heikki Mahkonen <heikki@nomadiclab.com> Fri, 22 February 2008 06:56 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: ietfarch-mip6-archive@core3.amsl.com
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D300E28C1B7; Thu, 21 Feb 2008 22:56:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.557
X-Spam-Level:
X-Spam-Status: No, score=-0.557 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 FuFZ+RHUgbcq; Thu, 21 Feb 2008 22:56:17 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D50E53A6808; Thu, 21 Feb 2008 22:56:17 -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 8131B3A692D for <mext@core3.amsl.com>; Thu, 21 Feb 2008 22:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 kw+grZFegepG for <mext@core3.amsl.com>; Thu, 21 Feb 2008 22:56:16 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 9AD6F3A6808 for <mext@ietf.org>; Thu, 21 Feb 2008 22:56:16 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 386331EF12D for <mext@ietf.org>; Fri, 22 Feb 2008 08:56:12 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:20e:7fff:fef8:6a7b] (unknown [IPv6:2001:14b8:400:101:20e:7fff:fef8:6a7b]) by n2.nomadiclab.com (Postfix) with ESMTP id 04B981EF11B for <mext@ietf.org>; Fri, 22 Feb 2008 08:56:12 +0200 (EET)
Message-ID: <47BE71E4.6040703@nomadiclab.com>
Date: Fri, 22 Feb 2008 08:55:32 +0200
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.9 (X11/20071212)
MIME-Version: 1.0
To: mext@ietf.org
References: <20080218193001.F28C43A6899@core3.amsl.com><47B9E6E6.3020901@piuha.net> <654FF284-3A57-4FEB-8435-DB4C940C15C3@lsiit.u-strasbg.fr> <B0E7E3680CE6D34D9143AAA76046453802708924@de01exm71.ds.mot.com>
In-Reply-To: <B0E7E3680CE6D34D9143AAA76046453802708924@de01exm71.ds.mot.com>
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [MEXT] draft-arkko-mext-rfc3775-altcoa-check-00.txt
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <http://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: <http://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

Hi,

Singh Ajoy-ASINGH1 wrote:
> Hi, Jari / All. 
> 
> Sorry for delayed response. I also think there is an use case for
> alt-CoA in PMIPv6 context. 
> So, I support the idea of keeping this in current MIPv6 spec. 
>  
==> In PMIP case there might be use for Alt. CoA option (at least when
using HW that has separated CPs and UPs). The use of Alt. CoA option is
also described in the PMIPV6 draft. However, PMIPv6 uses Proxy Binding
Updates and Acknowledgments so the new checking in the new draft doesn't
need to be applied for PMIPv6, rigtht? I mean the draft says that "When
an Alternate Care-of Address option is present in a Binding Update
message, perform the following additional test:".

If this new check is also needed for the PMIPv6, then I think PMIPv6
requires a new option to carry the CoA used for signaling (address of
the CP) inside the ESP protected part of the message. Then the Alt. CoA
option can be used to carry the address for the PMIPv6 tunnel endpoint
(address of the UP). Never the less, I think that the CP needs to know
the address of the UP to add it into the Alt. CoA option, so I guess it
would be doable to use the same UP address also for signaling (as a
source address of the PBU)...

BR,

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