[netext] Review of I-D: draft-ietf-netext-bulk-re-registration

<Basavaraj.Patil@nokia.com> Mon, 17 October 2011 20:48 UTC

Return-Path: <Basavaraj.Patil@nokia.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 F3C1D21F8B7B for <netext@ietfa.amsl.com>; Mon, 17 Oct 2011 13:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.666
X-Spam-Level:
X-Spam-Status: No, score=-102.666 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 7v5vVSNThyZz for <netext@ietfa.amsl.com>; Mon, 17 Oct 2011 13:48:13 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 6893721F8B79 for <netext@ietf.org>; Mon, 17 Oct 2011 13:48:12 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p9HKmAWj023521; Mon, 17 Oct 2011 23:48:11 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 17 Oct 2011 23:48:06 +0300
Received: from 008-AM1MMR1-004.mgdnok.nokia.com (65.54.30.59) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 17 Oct 2011 22:48:05 +0200
Received: from 008-AM1MPN1-053.mgdnok.nokia.com ([169.254.3.208]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.01.0339.002; Mon, 17 Oct 2011 22:48:05 +0200
From: <Basavaraj.Patil@nokia.com>
To: <netext@ietf.org>
Thread-Topic: Review of I-D: draft-ietf-netext-bulk-re-registration
Thread-Index: AQHMjQ4RrdC/zZ4Hw0OiAXKsx+HFaA==
Date: Mon, 17 Oct 2011 20:48:04 +0000
Message-ID: <CAC1FEBD.12329%basavaraj.patil@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.12.0.110505
x-originating-ip: [172.19.59.25]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2785A5B81C7A7240A48BF2E38042E39E@nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Oct 2011 20:48:06.0209 (UTC) FILETIME=[123F2B10:01CC8D0E]
X-Nokia-AV: Clean
Cc: draft-ietf-netext-bulk-re-registration@tools.ietf.org
Subject: [netext] Review of I-D: draft-ietf-netext-bulk-re-registration
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: Mon, 17 Oct 2011 20:48:14 -0000

Review of I-D: draft-ietf-netext-bulk-re-registration-06


s/so to perform/so as to perform

s/so some of relevant protocol operations can be performed on the
entire group/in order to allow relevant protocol operations to be
performed on the entire group.

s/The document/This document

s/will be the amount of /will the amount of

Comment: "A mobile access gateway when sending a Proxy Binding Update
message
   can request the local mobility anchor to assign a group identifier
   for the mobile node's mobility session."

   You might want to clarify that this is done for an MN which is
   performing initial attachment and for which there does not exist any
   mobility session yet.


s/the message confirm /the message conform

Comment: " Any time the local mobility anchor detects that the mobile node
      has roamed and changed its point of attachment to a new mobile
      access gateway, it SHOULD also update the group identifier of the
      mobility session. "

      If the LMA detects that an MN has attached to a different MAG it
      MUST delete the entry from the previous group. And subsequently
      update the GID if one has been assigned as a result of
      attachment to the new MAG.

The security section does not address the threats arising from the
ability to perform bulk operations. Suggest further enhancing the
security considerations section to include concerns about bulk
operations.


-Raj