[netext] Comments on draft-zhou-netext-pd-pmip-01.txt

Hidetoshi Yokota <yokota@kddilabs.jp> Thu, 21 July 2011 11:14 UTC

Return-Path: <yokota@kddilabs.jp>
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 A419421F8AF6 for <netext@ietfa.amsl.com>; Thu, 21 Jul 2011 04:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 XNuit-86G-mM for <netext@ietfa.amsl.com>; Thu, 21 Jul 2011 04:14:25 -0700 (PDT)
Received: from mandala.kddilabs.jp (mandala.kddilabs.jp [IPv6:2001:200:601:12::16]) by ietfa.amsl.com (Postfix) with ESMTP id AA6C421F8B0A for <netext@ietf.org>; Thu, 21 Jul 2011 04:14:24 -0700 (PDT)
Received: from localhost (mandala.kddilabs.jp [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id CACF81748163 for <netext@ietf.org>; Thu, 21 Jul 2011 20:14:22 +0900 (JST)
X-Virus-Scanned: amavisd-new at kddilabs.jp
Received: from mandala.kddilabs.jp ([127.0.0.1]) by localhost (mandala.kddilabs.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TyJeFXqSypAs for <netext@ietf.org>; Thu, 21 Jul 2011 20:14:22 +0900 (JST)
Received: from ultra.mip.kddilabs.jp (ultra.mip.kddilabs.jp [172.19.90.145]) by mandala.kddilabs.jp (Postfix) with ESMTP id 908371748147 for <netext@ietf.org>; Thu, 21 Jul 2011 20:14:22 +0900 (JST)
Received: from [127.0.0.1] (unknown [10.8.0.6]) by ultra.mip.kddilabs.jp (Postfix) with ESMTP id 9907D1B866 for <netext@ietf.org>; Thu, 21 Jul 2011 20:13:05 +0900 (JST)
Message-ID: <4E280A08.1020902@kddilabs.jp>
Date: Thu, 21 Jul 2011 20:14:16 +0900
From: Hidetoshi Yokota <yokota@kddilabs.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "netext@ietf.org" <netext@ietf.org>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: [netext] Comments on draft-zhou-netext-pd-pmip-01.txt
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: Thu, 21 Jul 2011 11:14:25 -0000

Hi Carl and Zhou,

I think this is interesting work clarifying how to make the mobile
router work in PMIPv6 domain. I, however, have a couple of comments on
this I-D:

(1) In Section 3.3.1, at step 1, a PMIPv6 tunnel is established before
PBU/PBA at steps 3 and 4. On the other hand, after steps 3 and 4, no
PMIPv6 tunnel appears to be established. In this specification, two
PBU/PBA exchanges happen or only once?

(2) In Section 3.4.1,

  "In order to support this specification, the conceptual Binding Cache
   entry data structure needs to be extended..."

I think it's "Binding Update List entry" not "Binding Cache entry" here

(3) In Section 3.5.2, it is said,

     "In order to receive those packets, the
      mobile access gateway MUST advertise a connected route into the
      Routing Infrastructure for the mobile router's mobile network
      prefix(es)"

I think it's the local mobility anchor not the mobile access gateway to
do this in this context.

Hope my comments will help improve the document.

Regards,
-- 
Hidetoshi