Re: [netext] Review of I-D: draft-ietf-netext-pd-pmip6-06

"Sri Gundavelli (sgundave)" <> Mon, 20 May 2013 15:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F110F21F93BC for <>; Mon, 20 May 2013 08:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.449
X-Spam-Status: No, score=-9.449 tagged_above=-999 required=5 tests=[AWL=1.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0s2bt6sItnHM for <>; Mon, 20 May 2013 08:26:21 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E7AAA21F93BD for <>; Mon, 20 May 2013 08:26:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=6665; q=dns/txt; s=iport; t=1369063581; x=1370273181; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=SLmQ2EzgsnOIqhLgEDPWmuFiR7E5l+PyD5Kn+O04U00=; b=IISNboYk3g5jp3YXF1SWpAvJ6j7i/Yp8iQYVRlezVY8TWyLp4ccYp+kD PpUNOPC3gY+EXhC8Qzd4LBRPjFzQkB4jLNw8fj+DmWShS8Z2edXSAP7fs r8AO/eJDWiImeGetESSwuWtPilG6b0Ca5SsDt/01X/2miWqqQrtXAF45T E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuAFAJ8/mlGtJV2Z/2dsb2JhbABagwgwwT+BABZ0gh8BAQEEAQEBZAcGBRIBCBgKSwslAgQBDQUIE4dyDLtSBI5uAjEHgnNhA4hniwCVEYMPgiY
X-IronPort-AV: E=Sophos;i="4.87,707,1363132800"; d="scan'208";a="212667657"
Received: from ([]) by with ESMTP; 20 May 2013 15:26:20 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id r4KFQKkP016333 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 May 2013 15:26:20 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Mon, 20 May 2013 10:26:20 -0500
From: "Sri Gundavelli (sgundave)" <>
To: "" <>, Basavaraj Patil <>
Thread-Topic: [netext] Review of I-D: draft-ietf-netext-pd-pmip6-06
Thread-Index: AQHOVWtVRsvRLCtAEUCu95E5Obm4XJkODlwA
Date: Mon, 20 May 2013 15:26:19 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>, "" <>
Subject: Re: [netext] Review of I-D: draft-ietf-netext-pd-pmip6-06
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, 20 May 2013 15:26:26 -0000

Hi Raj,

Adding to what carlos said. Just one clarification.

On 5/20/13 8:04 AM, "Carlos Jesús Bernardos Cano" <> wrote:

>Hi Raj,
>Some additional responses inline below (as Joy mentioned, we believe
>that everything is clearer in the new version, but just in case).
>On Wed, 2013-04-03 at 12:59 -0500, Basavaraj Patil wrote:
>> Questions:
>> 1. In the terminology section:
>>    "The DMNP is an IPv4 or an IPv6 prefix delegated to a mobile router
>>       and advertised in the mobile network."
>>       What is the mobile network being refered to in this statement?
>>       Is it the PMIP6 domain itself? Or is it the network that the
>>       mobile router is hosting?
>[Carlos] It is the network that the mobile router is hosting.
>> 2. In Sec 4.3.1:
>>    "It is possible that the delegated prefix(es) may
>>        have been assigned to the MAG by the LMA during this procedure
>> of
>>        PMIPv6 tunnel establishment.  That is the MAG may include one
>> (or
>>        more) Delegated Mobile Network Prefix (DMNP) mobility options
>>        which MUST be set to the unspecified IPv6 address "::" in the
>> PBU
>>        to request the delegated prefix(es).  The LMA assigns a new set
>>        of DMNP(s) in PBA message."
>>        Not sure what your assumptions are here. Why does the LMA
>>        assign delegated prefix(es) during normal RFC5213 PMIP6 tunnel
>>        establishment procedures?
>>        What would cause the MAG to include the DMNP option in the PBU
>>        at this stage (Step 2) of the session?
>[Carlos] We have clarified this in the new version.
>> 3. In Sec 4.3.1:
>>    " The mobile router, acting as a "Requesting Router" as described
>>        in [RFC3633], sends a DHCPv6 SOLICIT message including one or
>>        more IA_PD option(s) to the mobile access gateway (which has a
>>        "DHCPv6 Server" function) to acquire the delegated prefix(es)."
>>        Is there an assumption that the MAG is also the DHCPv6 server?
>>        The MAG could be a DHCP relay as well, right?
>[Carlos] Right, two deployment models are considered: one in which the
>MAG acts a DHCPv6 Delegating Router (i.e., server) and another in which
>the MAG acts as DHCPv6 Relay Agent and the LMA as Delegating Router.
>This has been further clarified in the new version.
>> 4. In Sec 4.3.1, step 5:
>>    "The LMA must set
>>        up forwarding for the delegated prefixes as reachable through
>> the
>>        PMIPv6 tunnel."
>>        The LMA may or may not assign these delegated prefixes. The MAG
>>        could be the one assigning the delegated prefixes as per the
>>        description. Are those prefixes routable by the LMA?
>[Carlos] Yes, the prefixes are routable by the LMA.
>> 5. In Sec 4.4.1, step 4:
>>    "If the mobile access
>>         gateway does not know the delegated prefix(es), then the
>>         delegated mobile network prefix in the DMNP option(s) MUST be
>>         set to the unspecified IPv6 address "::", "
>> How would the MAG know the delegated prefix(es)? Unless it is
>> just renewing the assigned prefix(es)?

The prefixes can be statically configured in the policy profile. Typically
mobile networks are statically configured (but registered with the LMA) as
we don't want the prefixes to disappear if the egress link goes down and
that will result in local communication between the hosts to break. So,
the prefixes are statically provisioned in the mobile network. But,
mobility support comes up only when there is active session with LMA
enabling the forwarding.

If the MAG knows the prefixes, it can indicate them in the DMNP option.
If the MAG does not know the prefixes,  it will carry a NULL value.
LMA assigns them based on what is in the BCE state.

This is consistent with how the home address (IPv4 HoA, HNP) options are
carried in PMIP signaling messages.


>[Carlos] This has been further revised and clarified in the new version.
>> 6. Is the assumption that the DHCP server functionality resides either
>>    at the MAG or the LMA in this I-D?
>[Carlos] Yes. It should be now clearer with the updates we have done in
>the text.
>> 7. In Sec 6.2 you state:
>>    "In order to receive these packets, the
>>       local mobility anchor MUST be the topological anchor of the MR's
>>       delegated mobile network prefix(es)."
>>       This should be made clear up front in order to avoid confusion
>>       about how forwarding is accomplished.
>[Carlos] This should be now clear.
>Thanks for your comments!
>> Editorial:
>> s/Proxy Mobile IPv6 enables IP mobility for a host without requiring
>>    its participation in any mobility signaling, being the network
>>    responsible for managing IP mobility on behalf of the host./ Proxy
>>    Mobile IPv6 enables IP mobility for a host without requiring
>>    its participation in any mobility signaling. Mobility elements in
>>    the network are responsible for managing IP mobility on behalf of
>>    the host. 
>> s/However,
>>    Proxy Mobile IPv6 does not support assigning a prefix to a router
>> and
>>    managing its IP mobility./However, Proxy Mobile IPv6 lacks the
>>    ability to assign a prefix to a router and  manage its IP
>>    mobility. 
>> s/and be able to obtain IP mobility support for those IP addresses./
>>    and enable IP mobility support for the assigned IP address or
>>    prefixes. 
>> s/However,
>>    this network-based mobility management support is specific to an IP
>>    host and currently there is no such network-based mobility
>> management
>>    support for a mobile router with a cluster of IP hosts behind
>> it./However,
>>    the Proxy Mobile IPv6 based solution for  network-based mobility
>>    management is specific to IP hosts and does not provide similar
>>    functionality for a mobile router with a cluster of IP hosts behind
>>    it. 
>> -Raj
>> _______________________________________________
>> netext mailing list
>netext mailing list