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

jouni korhonen <jouni.nospam@gmail.com> Tue, 20 November 2012 19:56 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 5DC9B21F8803 for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 11:56:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.516
X-Spam-Level:
X-Spam-Status: No, score=-3.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 91sbSIeFZzYw for <netext@ietfa.amsl.com>; Tue, 20 Nov 2012 11:56:28 -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 2DC1321F87F7 for <netext@ietf.org>; Tue, 20 Nov 2012 11:56:27 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so5288867lbk.31 for <netext@ietf.org>; Tue, 20 Nov 2012 11:56:26 -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=0Cl2zfG3ixas7BnkB++9hXJdu+SnJZB8lHNH1mHdfmc=; b=n+9XFC0IIoj4Irt35aiwtorkY11pdRtSYj3ZCsNPZFDFYXW3nttAJNl7DFIP7wXRC8 tP6sFoRpp3+T+XjhrNOJ1jwN+fT4AWdgBH8D9rmDOXEfNP45HlMgeOYY0SMkVQsYhwYb qlnly4B2tUG4HJlsKxMy+YNZxJV/dHIMpn8G7CYFQvq50ylSvIUt9F3uJ0Y/bCPYOgcV Q5VW98llx6j1qVxxDULIa4HCRSMGxvmPVGHrzYSXyOqiT63hERa7pzf+KyausRIJ/zCm dY0BLeIhI6tr041yUE7n2kWf+tmTEdLrPvjzY36QRZUAIvQSizchX8+mU9FWZNcxxAss fOHQ==
Received: by 10.112.9.135 with SMTP id z7mr6670209lba.66.1353441386853; Tue, 20 Nov 2012 11:56:26 -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 ps11sm5228825lab.12.2012.11.20.11.56.20 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Nov 2012 11:56:24 -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: <CAA5F1T1D0q-kN8r9H5PaDAXhqFozZ11FnEQ_4ce3XisFbJT+XQ@mail.gmail.com>
Date: Tue, 20 Nov 2012 21:56:18 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <A14201F5-7609-41F7-8C29-9DE096C30740@gmail.com>
References: <CAA5F1T1D0q-kN8r9H5PaDAXhqFozZ11FnEQ_4ce3XisFbJT+XQ@mail.gmail.com>
To: Basavaraj Patil <bpatil1@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: netext@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 19:56:29 -0000

Raj,

On Nov 20, 2012, at 6:40 PM, Basavaraj Patil wrote:

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

Ok. I would write this as:

   responsible for managing IP mobility on behalf of the host.  However,
   Proxy Mobile IPv6 does not support assigning a prefix to a router and
   managing IP mobility for it and the networks it serves. This document

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

Maybe.. see above.

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

Could you elaborate a bit more?


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

Good point. That needs to be clarified.

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

Section 3.4.2 states it..? I don't quite get what is missing here..


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


Cumulative ACK for the rest.

- Jouni


> 
> 
> 
> -Raj
> 
> _______________________________________________
> netext mailing list
> netext@ietf.org
> https://www.ietf.org/mailman/listinfo/netext