[Int-dir] Review of draft-ietf-dmm-mag-multihoming-02

Sheng Jiang <jiangsheng@huawei.com> Thu, 19 January 2017 09:55 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F18A129428; Thu, 19 Jan 2017 01:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level:
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PH3ckRmbBvNF; Thu, 19 Jan 2017 01:55:39 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6682C127ABE; Thu, 19 Jan 2017 01:55:38 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CZC76325; Thu, 19 Jan 2017 09:55:33 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 19 Jan 2017 09:55:14 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Thu, 19 Jan 2017 17:54:35 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "draft-ietf-dmm-mag-multihoming.all@ietf.org" <draft-ietf-dmm-mag-multihoming.all@ietf.org>
Thread-Topic: Review of draft-ietf-dmm-mag-multihoming-02
Thread-Index: AdJyOgI3fI973AFKRYaoXvLu0Irz8w==
Date: Thu, 19 Jan 2017 09:55:11 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B927CC84BA0@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.185.119]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B927CC84BA0NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.58808D16.01DC, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8149c9dd47dfce7734105abefc0723ed
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/FBgHssSf9ykJvzx3TOcynTwGySE>
Cc: "int-dir@ietf.org" <int-dir@ietf.org>
Subject: [Int-dir] Review of draft-ietf-dmm-mag-multihoming-02
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2017 09:55:41 -0000

Reviewer: Sheng Jiang

Review result: Almost Ready



I am an assigned INT directorate reviewer for draft-ietf-dmm-mag-multihoming-02. These comments were written primarily for the benefit of the Internet Area Directors. Document editors and shepherd(s) should treat these comments just like they would treat comments from any other IETF contributors and resolve them along with any other Last Call comments that have been received. For more details on the INT Directorate, see http://www.ietf.org/iesg/directorate.html.



Review Date:2017-1-19

Review Type : Early Review

IESG Telechat date:



Summary: This draft is almost ready for publication as a standard track RFC.


Major issues:



Minor issues:



The figure 2 seems imply a consecutive order of these steps, while some steps could and should be parallel, such as establishing the two connectivities, and the IP address assignment and data flow could and should start if one connectivity has established, but another is still in process. I guess authors have the same understanding. If so, adding some clarification text could address this issue.



The abstract seems to contain references, such as[RFC3963], etc., which it shouldn't. These references should be replaced by straight textual mentions of the documents.





The IANA consideration seems not in normal format. However, the required actions for IANA are described clearly.



Nits:



In abstract, "multiple Care-of Addresses  (CoAs) capabilities of Mobile IP an Network Mobility (NEMO)..."



an // and



In section 1, "In the continuation of [RFC4908], a Proxy Mobile IPv6 [RFC5213] based

   multihomed achitecture."



achitecture // architecture



also in section 1, "using GRE as mobile tuneling"



Tuneling//tunneling



Regards,



Sheng