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

Basavaraj Patil <bpatil1@gmail.com> Tue, 20 November 2012 16:40 UTC

Return-Path: <bpatil1@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 88F2C21F847F for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 08:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 S03DoqJm2Rka for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 08:40:22 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6611021F8479 for <netext@ietf.org>; Tue, 20 Nov 2012 08:40:22 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so1527384ieb.31 for <netext@ietf.org>; Tue, 20 Nov 2012 08:40:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=Yra3HgmIgjmEs4Z2ezoQqFtIFpctcUc8ZLvXd/GPqz0=; b=unlhoh2nglYbPh2NddXPLrJhczjySSySGfWVOX4NgGhMBMsT0jvAcTGTQL468BTsIo IBLRINPTLm8Fw7NMQjlEZmXNnJ4D4426iK1o85oF52DK+up8LWoTmnLOzfWL4ty/pd/9 ceUJJ4vS69mWgCEveHh296Ynu5HFntnI+/LEf3YLv58GZhhIsn6hvZ46FfmxlMacgTfI 09vynA9LgjW+4JBdb/b5TsgFMO/zTu6X/JAZg5sndRKwcxXqhrYZrLLfpScMw447TeTT /zuPFeqZI/LkmF3xfy79AMV926NPCBjCDWXFVvI9EDqWaDuiung7O8d+jZvNnU8QCjfv QbLA==
MIME-Version: 1.0
Received: by 10.50.46.134 with SMTP id v6mr10751560igm.55.1353429621676; Tue, 20 Nov 2012 08:40:21 -0800 (PST)
Received: by 10.43.101.197 with HTTP; Tue, 20 Nov 2012 08:40:21 -0800 (PST)
Date: Tue, 20 Nov 2012 10:40:21 -0600
Message-ID: <CAA5F1T1D0q-kN8r9H5PaDAXhqFozZ11FnEQ_4ce3XisFbJT+XQ@mail.gmail.com>
From: Basavaraj Patil <bpatil1@gmail.com>
To: netext@ietf.org
Content-Type: multipart/alternative; boundary=14dae9340f53d41a0404ceefe32f
Cc: draft-ietf-netext-pd-pmip@tools.ietf.org
Subject: [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:40:26 -0000

I-D: Prefix Delegation for Proxy Mobile IPv6
<draft-ietf-netext-pd-pmip-05>


Issues:
-------
1. I-D states: "However, Proxy Mobile IPv6 does not support assigning
a prefix to a router and  managing its IP mobility."

PMIP6 specifically mentions that the network based mobility solution
is for a host (as defined in RFC3775). It would be useful to mention
that this I-D is extending network based mobility support to routers
as well.

2. "This document specifies an extension to
   Proxy Mobile IPv6 protocol for supporting network mobility using
   DHCPv6-based Prefix Delegation."

Should it explicitly state that the extension to PMIP6 protocol is for
enabling network mobility for routers?

3. "The mobility elements in the network allow the
   IP host to obtain an IPv4 address and/or a set of IPv6 addresses
   ..."

MAG/LMA assign the host an IPv6 prefix.

4. Would be useful to mention how binding revocation is handled in the
case of delegated prefixes to the MR.

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.


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 agents within
   the network are responsible for managing IP mobility on behalf of
   the host.

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 Proxy Mobile IPv6 support is specifically
   intended for a host. Mobile routers can also benefit from the
   network based mobility solution provided by Proxy Mobile IPv6. This
   document extends Proxy Mobile IPv6 support to Mobile routers as
   well.

s/for its inside networks/for the networks subtending off the MR.

s/just as how that is supported for Home Network prefixes/in a similar
manner that the protocol supports hosts which are assigned home
network prefixes.

s/The mobile router forwards outgoing packets from its
   mobile network/The mobile router forwards outgoing or uplink
   packets from the networks that are subtending off it

s/ and the MAG
   delivers the incoming packets to the mobile network/and the MAG
   delivers the downlink packets to the MR.

s/to be able to intercept the related DHCPv6 message sourced from the
mobile router /in order to intercept the related DHCPv6 message
transmitted by the MR.

s/If the network mobility service needs to be offered to the mobile
   router/If the network mobility service is authorized for the mobile
   router

s/This requires the MAG to send a regular
        PBU to the LMA to register the location of the mobile router and
        set-up the bi-directional tunnel./This requires the MAG to
        send a regular PBU (with flag R set) to the LMA to register the
         mobile router and set-up the bi-directional tunnel.



-Raj