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

Peter McCann <> Mon, 26 November 2012 15:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9145C21F85C7; Mon, 26 Nov 2012 07:54:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hl3wJgtq2aVq; Mon, 26 Nov 2012 07:54:25 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 53AC721F85A6; Mon, 26 Nov 2012 07:54:17 -0800 (PST)
Received: from (EHLO ([]) by (MOS 4.3.5-GA FastPath queued) with ESMTP id AND82885; Mon, 26 Nov 2012 15:54:15 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 26 Nov 2012 15:54:10 +0000
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 26 Nov 2012 15:54:14 +0000
Received: from ([]) by ([]) with mapi id 14.01.0323.003; Mon, 26 Nov 2012 07:54:08 -0800
From: Peter McCann <>
To: jouni korhonen <>
Thread-Topic: [netext] Chair review of I-D: draft-ietf-netext-pd-pmip (05)
Thread-Index: AQHNxz3DQQQBC3W/sU+JRgVtIyAvCpfy7olggAC+hYD//3xY0IAAjCcA//97uoCAAJVJgP//ejdQABOHHoAABSeKoAAWNosAAAesqeAAJAylgAC4CjtwABlJU4AACu3TkA==
Date: Mon, 26 Nov 2012 15:54:07 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "" <>, "" <>, Basavaraj Patil <>, "" <>
Subject: Re: [netext] Chair review of I-D: draft-ietf-netext-pd-pmip (05)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Nov 2012 15:54:26 -0000

Hi, Jouni,

jouni korhonen wrote:
> Pete,
> On Nov 26, 2012, at 10:57 AM, Peter McCann wrote:
>> Hi, Jouni,
>> jouni korhonen wrote:
>>> Pete,
>>> I hope we start getting closer to convergence.. this thread is getting
>>> longish..
>> Yes and sorry about the delay responding.  We had the Thanksgiving
>> holiday here in the US and I was out of touch.
>>> On Nov 21, 2012, at 6:34 PM, Peter McCann wrote:
>>>> Hi, Jouni,
>>>> jouni korhonen wrote:
>>>>>> I guess if you sent a DHCP Renew every time you detected a link
>>>>>> flap (handover to new MAG) that would do the trick.  It seems
>>>>>> somewhat expensive, though.
>>>>> It is what RFC3315 says.. client sends a confirm request.
>>>> Right, I am just pointing out that the link may flap even when the
>>>> same LMA is reachable.  Seems like overhead.  You seem to be
>>>> requiring that the link doesn't flap when the PMIP session continues
>>>> after a MAG to MAG handover under the same LMA.
>>> I would say it it does not flap. The MR (at will) will still see it as
>>> a change of access point or something equivalent at the L2. If that
>>> event then gets delivered to the IP level somehow is out of my
>>> control. I have no control how the DHCPv6-PD client gets implemented
>>> in the MR or whether the network driver delivers proper events to
>>> upper layers.
>>> This is getting to the original reason why we wrote the draft.
>>> Depending on how the MR figures out "whether the link changed" it may
>>> or may not bother sending the Confirm Request. And if it does not,
>>> then the MAG does not know about the delegated prefixes -> forwarding
>>> fails. On the network side I cannot really trust the MR DHCPv6-PD
>>> client to do the right thing all the time.
>> Ok, so can we summarize the recommendation for PMIP deployments:
>> (1) When handing off between two MAGs under the same LMA, the change of
>> link SHOULD NOT be propagated to the IP stack (the link flap should not
>> be visible to IP).
> Should not is OKish. Cannot guarantee that though.

Right.  I think that many links will flap on every handover, whether
LMA changes or not.

>> (2) When handing off between two MAGs where the second MAG cannot or
>> does not connect back to the previous LMA, the change of link MUST be
>> propagated up the IP stack.
> Yep.

Ok, good.

>> I think that (1) is a SHOULD NOT because violation of this SHOULD NOT
>> only leads to some extra traffic on the link from re-confirmation. In
>> contrast, (2) is a MUST because the absence of a link down/up event
>> could lead to a hung session where the MN thinks it has a routable
>> prefix but actually does not.
>> Have either of these two requirements been codified in 5213 or
>> elsewhere?
> RFC5213 is prepared to handle 1) independent whether the event is
> sent or not, ref the DNA text and link-local address MO.

Ok, I see that text now.

Should we document (2) somewhere?

>>>>> The LMA-LMA hanover, as per current RFC5213, would be visible as a
>>>>> link flap or L2 session termination whatever. At least on those L2
>>>>> technologies that I am aware of.
>>>> In my view, a MAG to MAG handover under the same LMA is equally
>>>> likely to lead to a link flap.  Which really does no harm, it only
>>>> leads to extra DHCP or RS/RA reconfirmation traffic in this case.
>>> LMA-LMA handover based on the existing specs means the end of PMIP
>>> session, which on the point-to-point link technologies I am aware of
>>> also results in the termination of the L2 session. We have not defined
>>> how renumbering would work in this case. In certain L2 technologies
>>> renumbering is not even supported (ref 3GPP).
>> Are you aware of a deployment of PMIP over the 3GPP PDP context link?
>> I am not.  The existing GPRS model is that the GGSN or PGW is the
> first
> I am. This is not an academic exercise.
>> hop router, and traffic is always tunneled directly back to that
>> router. In contrast, PMIP has the MAG as the first hop router.  This is
>> a fundamental difference that IMHO makes it more likely to see a link
>> flap on a MAG to MAG handover, even when the same LMA is reachable from
>> both.
> If the LMA stays the same, the link does not flap. 

I don't see how you can make a blanket statement like this for all
link layers that might be used for PMIP.  In particular, it seems
to require a knowledge, at the L2, of whether the current MAG can
see the same LMA.  This knowledge needs to be propagated across the
link to the client, and used to determine whether the link down/up
event propagates through the IP stack.  Perhaps your particular 
implementation experience involved carrying such a signal but I
cannot imagine that it holds true for every L2, especially if they
were not designed with PMIP in mind.

> One might receive
> an event that the access point (or equivalent) changed. This again
> depends on the client side implementation.

And in many implementations I can imagine this event treated as a link
>> I think you agree with me that a change of MAG that results in a change
>> of LMA should always result in a link down/up event that is visible to
>> the IP stack.
> I repeat what I said earlier. If the LMA changes the L2 session goes
> down, prefixes may change etc. It is a bit more than just link up/down
> because it also involves setting up a new PMIP session & L2 session. (on
> L2 technologies I am concerned with).

You seem to be implying that the L2 technology has a notion of a PMIP
session.  The layered protocol model would seem to discourage this,
and I can imagine that many link layers are designed without PMIP
in mind.

>>>> Yes, that might help, but it seems to run counter to the
>>>> recommendation in RFC 6543.  Also, I am not so sure that it will be
>>>> possible to define
>>> I know and again back to the context of my assertion:
>>> "..(possible by specs but a hack in a way, thus not elaborated in this
>>> I-D)."
>>> And that "specs" dates to original RC5213 which would allow us this.
>>> Even when using RFC6543 I can turn it off by configuration.
>> Agreed, it's possible.
>>>> clean boundaries a priori where different link local addresses would
>>>> be assigned.  There may be some overlap in the LMA coverage areas
>>>> (although
>>> Assuming RFC6543 is not used and we do assign different link-locals,
>>> then it is up to the LMA decide when to use which link-local. Two
>>> examples: each LMA has its own or each PMIP session gets its own
>>> "unique" link-local. Both cases have possibility of address collisions
>>> but are quite unlikely. I do not really care about coverage areas
>>> rather the case when something happened on the emulated home link and
>>> for that case the two examples would be sufficient. Note that I am not
>>> prompting such "solution".
>> Did you mean to say "up to the MAG"?  I am not sure I like the idea of
>> the LMA controlling the MAG's link-local address.
> No.. or lets say my wording was imprecise. Whether this feature is
> enabled depends on the MAG configuration. If MAG allows the LMA to
> generate the link-local, then LMA does it and MAG uses that address. In
> that case the LMA decides when to use which link-local address.

It would still require coordination between the old LMA and the new
LMA, precisely in those situations where no such coordination is possible
(the PMIP domains are distinct and unconnected).

>>>> You may be running a server on the MN which is waiting for inbound
>>>> connections.  The peer correspondent nodes would send traffic to the
>>>> old prefix, and there would be no indication to the MN that the old
>>>> prefix isn't valid anymore.
>>> As said we cannot heal all networking issues by specifications if
>>> people do not implement them properly. If your delegated prefix is
>>> gone from the network point of view and your MR sits there doing
>>> nothing while it should based on e.g. RFC3315, tough luck.
>> If the link down/up event has been hidden from the IP stack, then
>> sitting there doing nothing is exactly what an RFC3315 compliant
>> implementation would do.  Hence my use of MUST in (2) above.
> Sure. Never claimed it to be different. But as said, I cannot control
> the client side implementation. That is the point.

But you seem to be making assumptions about the L2 implementation 
and that, in particular, it knows when a PMIP session is disconnected.

I am sorry to be making a big deal about these issues.  I am raising
them because I think it will be important to get these details right
when it comes to the DMM solution.  There, I think we will have some
set of prefixes assigned to the MN at any given time, and some arbitrary
subset will need to be deprecated and/or torn down proactively upon 
each handover (change of MAG if a PMIP-style solution is used to 
re-route the packets).  However, we can discuss more details on the
DMM list if you prefer (and this may get us a bit into DMM solution
space.  But, I am trying to think ahead).