Re: [netext] Chair review of I-D: draft-ietf-netext-pd-pmip (05)

Peter McCann <Peter.McCann@huawei.com> Tue, 20 November 2012 20:18 UTC

Return-Path: <Peter.McCann@huawei.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C617821F87A4 for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 12:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level:
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id seUnqZ3z6M-s for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 12:18:26 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B0B3021F878F for <netext@ietf.org>; Tue, 20 Nov 2012 12:18:25 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AMZ31291; Tue, 20 Nov 2012 20:18:24 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 20 Nov 2012 20:17:54 +0000
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 20 Nov 2012 20:18:23 +0000
Received: from dfweml512-mbx.china.huawei.com ([169.254.1.159]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.003; Tue, 20 Nov 2012 12:18:20 -0800
From: Peter McCann <Peter.McCann@huawei.com>
To: jouni korhonen <jouni.nospam@gmail.com>
Thread-Topic: [netext] Chair review of I-D: draft-ietf-netext-pd-pmip (05)
Thread-Index: AQHNxz3DQQQBC3W/sU+JRgVtIyAvCpfy7olggAC+hYD//3xY0A==
Date: Tue, 20 Nov 2012 20:18:19 +0000
Message-ID: <5963DDF1F751474D8DEEFDCDBEE43AE716E588CF@dfweml512-mbx.china.huawei.com>
References: <CAA5F1T1D0q-kN8r9H5PaDAXhqFozZ11FnEQ_4ce3XisFbJT+XQ@mail.gmail.com> <5963DDF1F751474D8DEEFDCDBEE43AE716E587E9@dfweml512-mbx.china.huawei.com> <9892BC94-F495-405F-93E9-90A33DAF8C96@gmail.com>
In-Reply-To: <9892BC94-F495-405F-93E9-90A33DAF8C96@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.193.125.187]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "netext@ietf.org" <netext@ietf.org>, Basavaraj Patil <bpatil1@gmail.com>, "draft-ietf-netext-pd-pmip@tools.ietf.org" <draft-ietf-netext-pd-pmip@tools.ietf.org>
Subject: Re: [netext] Chair review of I-D: draft-ietf-netext-pd-pmip (05)
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2012 20:18:26 -0000

Hi, Jouni,

What if the new MAG cannot connect back to the old LMA?  How does the
MR find out that its delegated prefix is no longer routable?

-Pete


jouni korhonen wrote:
> 
> Pete,
> 
> On Nov 20, 2012, at 6:50 PM, Peter McCann wrote:
> 
>> Basavaraj Patil wrote:
>>> 
>>> 5. How does the MAG know that it needs to allow forwarding of packets
>>> via the PMIP6 tunnel for packets with SRC address that are derived
>>> from the delegated prefixes? Its not clear if there is added
>>> functionality needed at the MAG to accomplish this.
>> 
>> I think there are potentially some deeper issues here.
>> 
>> The MN sees the original MAG as its "delegating router".  When the
>> MN changes to a new MAG, there is no good way to tell that the
>> delegated prefixes are still routable to the link.  The delegating
> 
> This is what the I-D is about.. That's we got the new signaling in
> place and the handover case described in Section 3.4.3.
> 
>> router has become unreachable.  The new router may send an RA that
>> advertises the original link prefix, and so the MN can tell that its
>> SLAAC unicast addresses are still valid on the link.  However,
> 
> When the MR (i.e. in RFC5213 terminology the MN) does a handover, the
> prefix used between the MR-MAG stays the same as usually provided by
> PMIP6. Section 3.4.3 the describes what the MAG has to do in order to
> know the existing delegated prefixes and set the forwarding state.
> 
>> RFC 3633 says that the delegated prefix is NOT advertised on the
>> link between the delegating router and the requesting router.
> 
> And they are not. The delegated prefixes are used on the downstream
> interfaces of the MR, not on the MR-MAG link. If the prefix used on
> the MR-MAG link is part of the delegated prefix, then the MR has to
> use RFC6603.
> 
>> Therefore, there is no way for the MR to determine whether it can
>> still use the delegated prefixes, other than perhaps re-running
>> DHCPv6-PD on the new link.
> 
> From MR point of view nothing changed. So what is the issue?
> 
> - Jouni
> 
> 
>> 
>> -Pete
>> 
>> 
>> _______________________________________________
>> netext mailing list
>> netext@ietf.org
>> https://www.ietf.org/mailman/listinfo/netext