Re: [netext] Review of I-D: draft-ietf-netext-pd-pmip-01

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 10 November 2011 22:46 UTC

Return-Path: <sarikaya2012@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 4658F21F8880 for <netext@ietfa.amsl.com>; Thu, 10 Nov 2011 14:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.439
X-Spam-Level:
X-Spam-Status: No, score=-3.439 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icXzBpVPRJ+S for <netext@ietfa.amsl.com>; Thu, 10 Nov 2011 14:46:29 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5D06321F861E for <netext@ietf.org>; Thu, 10 Nov 2011 14:46:29 -0800 (PST)
Received: by ywt34 with SMTP id 34so1550817ywt.31 for <netext@ietf.org>; Thu, 10 Nov 2011 14:46:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=fep87PkYoD/gTvuT3U/x1A1haS5puQ5oQ5unDVGUIMA=; b=l4fSuBt4noG8Ea+LutjTWGwZdPNpFEtpOQUXgnpv/AWUlL1Tc6A1SsHGgcKCvBW91m a0GUgGzLyukE6g1nl2LnwoVeQh6n3uKuuL8hH2WgMERgIYsBsGxShwJaeZNxoJjr4+YW mJpxpnxreUeUeuNZLTM4p7dNmWqL+yZ+tvyZQ=
MIME-Version: 1.0
Received: by 10.146.159.5 with SMTP id h5mr4085032yae.1.1320965188926; Thu, 10 Nov 2011 14:46:28 -0800 (PST)
Received: by 10.236.95.9 with HTTP; Thu, 10 Nov 2011 14:46:28 -0800 (PST)
In-Reply-To: <CADD9916.1535F%basavaraj.patil@nokia.com>
References: <CADD9916.1535F%basavaraj.patil@nokia.com>
Date: Thu, 10 Nov 2011 16:46:28 -0600
Message-ID: <CAC8QAceKDtSbdz+F3rnVwQbsAGUT6Gzp_M+20vrnP-B+14R9RA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Basavaraj.Patil@nokia.com
Content-Type: multipart/alternative; boundary=000e0cd29e52d8bbc704b1692c5b
Cc: netext@ietf.org, draft-ietf-netext-pd-pmip@tools.ietf.org
Subject: Re: [netext] Review of I-D: draft-ietf-netext-pd-pmip-01
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
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, 10 Nov 2011 22:46:30 -0000

Hi Basavaraj,

I have a question:

Can we at Netext work on specs that require modifying MN?

Reading the charter:

The work in this charter is entirely internal to the network and does
  not affect host IP stack operation in any way (except perhaps through
  impacting packet forwarding capacity visible to the hosts).


It seems to me the answer is no?

Regards,

Behcet
On Mon, Nov 7, 2011 at 2:17 PM, <Basavaraj.Patil@nokia.com> wrote:

>
> A few quick comments:
>
> 1. Abstract should have no references. And the description can be
>   improved. It really is hard to understand what this I-D is trying
>   to accomplish.
>
> 2. The introduction section can be improved. Maybe you should include
>   a problem statement section to indicate what is lacking in PMIP6 as
>   per RFC5213.
>
> 3. In Sec 3.1 it states:
> "
>   o  The MR (as a RR) MUST either obtain the Home Network Prefix (HNP)
>      before initiating the DHCPv6-PD procedure or in case of stateful
>      address configuration simultaneously while configuring the Mobile
>      Node Home Address (MN-HoA).
> "
>
>   So does this imply that the MR (PMIP6 MN) obtains an HNP as per
>   RFC5213 for its own use prior to the MR requesting via DHCPv6
>   another set of prefixes to be used for delegating to downstream
>   nodes?
>
> 4. If the prefixes (delegated) are provided by a DHCP server (and not
>   the LMA), how does the LMA get informed about these? In the PBU?
>   How do you ensure that
>   "All the mobile network prefixes managed in the DR MUST be
>   reachable via local mobility anchor (LMA)" when they are not
>   assigned by the LMA?
>
> 5. Sec 3.1 also states:
>   "The delegating router (DR) can be located either at LMA or some
>      other device in the PMIPv6 domain"
>
>    What is this some other device?
>
> 6.  In Sec 3.2 the I-D states that the profile needs to indicate
>    whether an MN can be assigned prefixes for delegation. Does the
>    profile indicate whether the host is a mobile router? Is this
>    needed? Any MN should be able to act as an MR.
>
> 7. In Fig 1, you have a DR shown there. How does the DR indicate the
>   assigned prefixes to the LMA?
>   - Step 5 seems disconnected from the rest of the process. Maybe it
>   is better to split that aspect and show it in another figure.
>
> 8. Does the lifetime of the delegated prefix (assigned by a DR) the
>   same as the lifetime assigned by the LMA?
>   Why not have Sec 3.3.3 to describe how a prefix is revoked or
>   deleted? Text is currently in 3.3.2.
>
> 9. In sec 3.4.2:
>   "Other considerations from Section 6.10.5 or [RFC5213]"
>
>   Sec 6.10.5 of this I-D? There is none.
>
> 10. Sec 3.5.2 states:
>    "In order to receive
>      those packets, the LMA MUST advertise a connected route into the
>      routing infrastructure for the MR's MNP(s)."
>
>    - Is it enough from a specification standpoint to state that the
>      routes need to be injected into the routing infra?
>      Handwaving????
>
> 11. Are there any new threats or security issues that arise from
>    assigning prefixes to be delegated downstream in the case of
>    PMIP6? Security section seems pretty light.
>
>
> -Raj
>
> _______________________________________________
> netext mailing list
> netext@ietf.org
> https://www.ietf.org/mailman/listinfo/netext
>