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

jouni korhonen <jouni.nospam@gmail.com> Tue, 20 November 2012 20:38 UTC

Return-Path: <jouni.nospam@gmail.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 4105D21F8810 for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 12:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.53
X-Spam-Level:
X-Spam-Status: No, score=-3.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 qjBtnsKLhXrG for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 12:38:25 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5892021F880B for <netext@ietf.org>; Tue, 20 Nov 2012 12:38:24 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so5316681lbk.31 for <netext@ietf.org>; Tue, 20 Nov 2012 12:38:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=7JcJaHuZE0wtkMb67fhcjaAP8/jopH1aCQCRSlnFVvs=; b=TNu2lO5rz3DzbUmQdKW7ml5LmQ2dJO7Uf2n9aIKGV61DJkSAOQavOxB14CUGidKMJR IRy3XCzv8+2ZyVOynHfl45b/OxaGZx3cOINUAo1W7bqY/CRxjHlckkI3oxmZL2wv5WzF MZnZPwWKNabnNU9j1OeXhXLQv3/VyM2TPJO7IyXV7GPSgpAal6Lx9ZGcu/xuGFGCRHF/ LhQj+uz922vOO4raijQeZlWe3tXgXn88NDBRdZjKu18CDPzyuGbiL1NjkIUQemrqWM8I nv88yHUEsXEW7K0N+L70757PvEaAsw5RLKq8ebkOrC9ScAJ1ZX7eWtjULEl+Z2/EWept tt1w==
Received: by 10.152.132.3 with SMTP id oq3mr15502598lab.18.1353443903763; Tue, 20 Nov 2012 12:38:23 -0800 (PST)
Received: from ?IPv6:2001:1bc8:101:f101:226:bbff:fe18:6e9c? ([2001:1bc8:101:f101:226:bbff:fe18:6e9c]) by mx.google.com with ESMTPS id jk8sm5263285lab.7.2012.11.20.12.38.16 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Nov 2012 12:38:19 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <5963DDF1F751474D8DEEFDCDBEE43AE716E588CF@dfweml512-mbx.china.huawei.com>
Date: Tue, 20 Nov 2012 22:38:14 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <DF31E9C5-2730-4078-95EA-A2A88A4A0CA5@gmail.com>
References: <CAA5F1T1D0q-kN8r9H5PaDAXhqFozZ11FnEQ_4ce3XisFbJT+XQ@mail.gmail.com> <5963DDF1F751474D8DEEFDCDBEE43AE716E587E9@dfweml512-mbx.china.huawei.com> <9892BC94-F495-405F-93E9-90A33DAF8C96@gmail.com> <5963DDF1F751474D8DEEFDCDBEE43AE716E588CF@dfweml512-mbx.china.huawei.com>
To: Peter McCann <Peter.McCann@huawei.com>
X-Mailer: Apple Mail (2.1085)
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:38:26 -0000

Pete,

On Nov 20, 2012, at 10:18 PM, Peter McCann wrote:

> 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?

In that case your PMIP session goes down.. and the MR sees it as a change
of the link. In that case MR does what any DHCP client is supposed to do
i.e. verify whether its prefixes are still valid on the new link using a
confirm/reply exchange.

- JOuni

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