Re: [netext] Chair review of I-D: draft-ietf-netext-pd-pmip (05)
Peter McCann <Peter.McCann@huawei.com> Tue, 20 November 2012 16:50 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 4D94321F8756 for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 08:50:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level:
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080, 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 0XnHwcHIH0lC for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 08:50:50 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0E48821F870C for <netext@ietf.org>; Tue, 20 Nov 2012 08:50:49 -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 AMZ21702; Tue, 20 Nov 2012 16:50:48 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 20 Nov 2012 16:50:18 +0000
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 21 Nov 2012 00:50:47 +0800
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 08:50:45 -0800
From: Peter McCann <Peter.McCann@huawei.com>
To: Basavaraj Patil <bpatil1@gmail.com>, "netext@ietf.org" <netext@ietf.org>
Thread-Topic: [netext] Chair review of I-D: draft-ietf-netext-pd-pmip (05)
Thread-Index: AQHNxz3DQQQBC3W/sU+JRgVtIyAvCpfy7olg
Date: Tue, 20 Nov 2012 16:50:45 +0000
Message-ID: <5963DDF1F751474D8DEEFDCDBEE43AE716E587E9@dfweml512-mbx.china.huawei.com>
References: <CAA5F1T1D0q-kN8r9H5PaDAXhqFozZ11FnEQ_4ce3XisFbJT+XQ@mail.gmail.com>
In-Reply-To: <CAA5F1T1D0q-kN8r9H5PaDAXhqFozZ11FnEQ_4ce3XisFbJT+XQ@mail.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: "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 16:50:51 -0000
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 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, RFC 3633 says that the delegated prefix is NOT advertised on the link between the delegating router and the requesting router. 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. -Pete
- [netext] Chair review of I-D: draft-ietf-netext-p… Basavaraj Patil
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… Basavaraj Patil
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… zhou.xingyue
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann
- Re: [netext] Chair review of I-D: draft-ietf-nete… jouni korhonen
- Re: [netext] Chair review of I-D: draft-ietf-nete… Peter McCann