[netext] Review of I-D: draft-ietf-netext-pmip-lr-04
<Basavaraj.Patil@nokia.com> Wed, 20 July 2011 16:43 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 9D9F421F869E for <netext@ietfa.amsl.com>; Wed, 20 Jul 2011 09:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.723
X-Spam-Level:
X-Spam-Status: No, score=-102.723 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 rtgQEgTWbg3b for <netext@ietfa.amsl.com>; Wed, 20 Jul 2011 09:43:27 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 4259D21F865D for <netext@ietf.org>; Wed, 20 Jul 2011 09:43:23 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p6KGhMgS021531; Wed, 20 Jul 2011 19:43:22 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 20 Jul 2011 19:43:22 +0300
Received: from 008-AM1MMR1-005.mgdnok.nokia.com (65.54.30.60) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 20 Jul 2011 18:43:21 +0200
Received: from 008-AM1MPN1-024.mgdnok.nokia.com ([169.254.4.61]) by 008-AM1MMR1-005.mgdnok.nokia.com ([65.54.30.60]) with mapi id 14.01.0323.002; Wed, 20 Jul 2011 18:43:20 +0200
From: Basavaraj.Patil@nokia.com
To: netext@ietf.org
Thread-Topic: Review of I-D: draft-ietf-netext-pmip-lr-04
Thread-Index: AcxGcYt8Segd5A1bSEOc4ChY6g6NHQ==
Date: Wed, 20 Jul 2011 16:43:21 +0000
Message-ID: <21E7D9BD69CC7241AAE00F4EA183B719083E70@008-AM1MPN1-024.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.74.219.186]
Content-Type: multipart/alternative; boundary="_000_21E7D9BD69CC7241AAE00F4EA183B719083E70008AM1MPN1024mgdn_"
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Jul 2011 16:43:22.0152 (UTC) FILETIME=[231A2280:01CC46FC]
X-Nokia-AV: Clean
Cc: draft-ietf-netext-pmip-lr@tools.ietf.org
Subject: [netext] Review of I-D: draft-ietf-netext-pmip-lr-04
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: Wed, 20 Jul 2011 16:43:28 -0000
Hello, Below is the chair review of this I-D following the completion of WG last call. -Basavaraj 1. s/mobile access gateways to exchange traffic/mobile access gateways to route traffic 2. s/This document proposes initiation, utilization and termination mechanisms for localized routing/This document proposes initiation, utilization and termination mechanisms for localized routing between mobile access gateways within a proxy mobile IPv6 domain. 3. The reference I-D.ietf-netext-pmip6-lr-ps can be updated to RFC6279 4. In the terminology section (3), it would be useful to reference the terminology captured in RFC6279 5. Please number the figures in the I-D 6. Would be good to explain what are the flags Opt1: R=0,S=0, U=0 from a readability standpoint 7. The terms LRI and LRA are used in Sec 4, Scenario A11 without having previously expanded the acronym or for that matter explaining the basic set of new messages that have been defined for the purpose or localized routing. 8. s/The MAG (MAG1) starts by verifying that the two MNs are indeed attached to it./The MAG (MAG1) verifies via the binding cache the existence/attachment status of the two MNs locally. 9. Question: > The MAG (MAG1) starts by verifying that the two MNs are indeed > attached to it. It then verifies if the EnableMAGLocalRouting flag > is set to 1. If it is not, the MAG has not been configured to allow > localized routing and it will reject the LRI and send an LRA with > status code "Localized Routing Not Allowed". This scenario and message flow suggests the usage of LRI/LRA to setup localized routing at the MAG. Does this update the behavior specified in RFC5213? If so, it would be good to state it. 10. Sec 5: > As earlier, the LMA initiates LR as a response to some trigger > mechanism. What trigger mechanism? Can you provide at least some examples? 11. > The tunnel between the MAGs is assumed to be established by means > outside the scope of this document. It would be useful to at least provide some examples of the tunnel establishment between MAGs from a completeness perspective. It looks like handwaving at the moment. 12. > As before, each MAG responds to the LRI with an LRA message. What exactly are you referencing by "As before"? 13. > 6. Scenario A12: Two MNs attached to the same MAG with different > LMAs It would be good to mention that the LMAs in this case are in the scope of the same PMIP6 domain. 14. Explain the flow diagram in section 6. I would recommend numbering the message flows and explaining the sequence. 15. s/Scenario A22: Two MNs attached to the different MAGs with different LMAs/Scenario A22: Two MNs attached to different MAGs with different LMAs You can also state that this case is not covered even if the LMAs are in the same PMIP6 domain. 16. Question: > 8. IPv4 support in Localized Routing Are we supporting LR for IPv4 traffic? I thought that we had agreed to do LR for IPv6 traffic only and avoid the issues related to overlapping IPv4 addresses etc. Can you clarify why this section exists? Maybe it would be useful to state that LR is only for IPv6 traffic. 17. 11. Security Considerations You do not mention anything about the security requirements between MAGs when traffic is routed between MAG1 and MAG2 via some tunnelling mechanism. This should be clearly captured. 18. The IANA considerations section is poorly written and does not provide sufficient information to IANA regarding the actions needed from them. I would recommend revisiting this section.
- [netext] Review of I-D: draft-ietf-netext-pmip-lr… Basavaraj.Patil
- Re: [netext] Review of I-D: draft-ietf-netext-pmi… Suresh Krishnan
- Re: [netext] Review of I-D: draft-ietf-netext-pmi… Basavaraj.Patil
- Re: [netext] Review of I-D: draft-ietf-netext-pmi… Qin Wu
- Re: [netext] Review of I-D: draft-ietf-netext-pmi… Basavaraj.Patil
- Re: [netext] Review of I-D: draft-ietf-netext-pmi… Rajeev Koodli
- Re: [netext] Review of I-D: draft-ietf-netext-pmi… Suresh Krishnan