IETF Logo Mail Archive

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

"Premec, Domagoj" <domagoj.premec@siemens.com> Fri, 22 February 2008 12:31 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: ietfarch-mext-archive@core3.amsl.com
Delivered-To: ietfarch-mext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E41228C355; Fri, 22 Feb 2008 04:31:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.674
X-Spam-Level:
X-Spam-Status: No, score=-0.674 tagged_above=-999 required=5 tests=[AWL=-0.237, 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 LLE83rsGLq3e; Fri, 22 Feb 2008 04:31:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62EB628C327; Fri, 22 Feb 2008 04:31:07 -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 4A73728C32E for <mext@core3.amsl.com>; Fri, 22 Feb 2008 04:31:06 -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 UQeXG5h6BaaG for <mext@core3.amsl.com>; Fri, 22 Feb 2008 04:31:05 -0800 (PST)
Received: from mxs2.siemens.at (mxs2.siemens.at [194.138.12.133]) by core3.amsl.com (Postfix) with ESMTP id 33DD728C327 for <mext@ietf.org>; Fri, 22 Feb 2008 04:31:05 -0800 (PST)
Received: from vies1kbx.sie.siemens.at ([158.226.129.82]) by mxs2.siemens.at with ESMTP id m1MCV5kG000486; Fri, 22 Feb 2008 13:31:05 +0100
Received: from nets139a.ww300.siemens.net ([158.226.129.97]) by vies1kbx.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id m1MCUq2I024100; Fri, 22 Feb 2008 13:30:58 +0100
Received: from zagh223a.ww300.siemens.net ([141.29.124.9]) by nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 22 Feb 2008 13:30:43 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 22 Feb 2008 13:30:43 +0100
Message-ID: <3C31CDD06342EA4A8137716247B1CD6803750856@zagh223a.ww300.siemens.net>
In-Reply-To: <47BE71E4.6040703@nomadiclab.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] draft-arkko-mext-rfc3775-altcoa-check-00.txt
Thread-Index: Ach1IJCw79HLTCrwS96MAkVxAME6bgAK7EGg
References: <20080218193001.F28C43A6899@core3.amsl.com><47B9E6E6.3020901@piuha.net> <654FF284-3A57-4FEB-8435-DB4C940C15C3@lsiit.u-strasbg.fr><B0E7E3680CE6D34D9143AAA76046453802708924@de01exm71.ds.mot.com> <47BE71E4.6040703@nomadiclab.com>
From: "Premec, Domagoj" <domagoj.premec@siemens.com>
To: Heikki Mahkonen <heikki@nomadiclab.com>, mext@ietf.org
X-OriginalArrivalTime: 22 Feb 2008 12:30:43.0986 (UTC) FILETIME=[BE408F20:01C8754E]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 149917::080222133105-0AEA1BB0-078BBC92/0-0/0-15
X-purgate-size: 2444/999999
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 Heikki,

> 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)...

By using the same address for CP and UP the CP messages would arrive at the user plane blade which is not able to deal with them. 

In addition, if the LMA would send unsolicited messages to the MAG (like Binding Revocation), the LMA needs to save two different CoAs in the BCE: one for signalling (source IP) and another for data plane (alt-CoA).

regards
domagoj

 

> -----Original Message-----
> From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On 
> Behalf Of Heikki Mahkonen
> Sent: 22. veljaca 2008 07:56
> To: mext@ietf.org
> Subject: Re: [MEXT] draft-arkko-mext-rfc3775-altcoa-check-00.txt
> 
> 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
> 
> 
_______________________________________________
MEXT mailing list
MEXT@ietf.org
http://www.ietf.org/mailman/listinfo/mext

v2.23.0 | Report a Bug | By Email