Re: [6lo] Tsvart last call review of draft-ietf-6lo-plc-05

"Liubing (Remy)" <remy.liubing@huawei.com> Fri, 05 March 2021 04:13 UTC

Return-Path: <remy.liubing@huawei.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A57C13A1D57; Thu, 4 Mar 2021 20:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 X9L8d-LdIZs7; Thu, 4 Mar 2021 20:13:46 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87ED83A1D56; Thu, 4 Mar 2021 20:13:46 -0800 (PST)
Received: from fraeml706-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DsDgB32FSz67vTS; Fri, 5 Mar 2021 12:05:58 +0800 (CST)
Received: from fraeml706-chm.china.huawei.com (10.206.15.55) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Fri, 5 Mar 2021 05:13:44 +0100
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.2106.2 via Frontend Transport; Fri, 5 Mar 2021 05:13:44 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.62]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0509.000; Fri, 5 Mar 2021 12:13:41 +0800
From: "Liubing (Remy)" <remy.liubing@huawei.com>
To: Joseph Touch <touch@strayalpha.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
CC: "6lo@ietf.org" <6lo@ietf.org>, "draft-ietf-6lo-plc.all@ietf.org" <draft-ietf-6lo-plc.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Tsvart last call review of draft-ietf-6lo-plc-05
Thread-Index: AdcRdcjATeEoE3AqS3yLsT/ezrYjMg==
Date: Fri, 5 Mar 2021 04:13:41 +0000
Message-ID: <BB09947B5326FE42BA3918FA28765C2E014F4FF0@DGGEMM506-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.242.194]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/a-S8iJ4b6-KyDZ7Qv_iKzko4l08>
Subject: Re: [6lo] Tsvart last call review of draft-ietf-6lo-plc-05
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2021 04:13:49 -0000

Hello Joseph,

Thank you very much for your comments. Please see my reply below.

Best regards,
Remy

-----邮件原件-----
发件人: Joseph Touch via Datatracker [mailto:noreply@ietf.org] 
发送时间: 2021年2月20日 9:15
收件人: tsv-art@ietf.org
抄送: 6lo@ietf.org; draft-ietf-6lo-plc.all@ietf.org; last-call@ietf.org
主题: Tsvart last call review of draft-ietf-6lo-plc-05

Reviewer: Joseph Touch
Review result: Ready with Issues

This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information.

When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-art@ietf.org if you reply to or forward this review.

---

The only significant transport issue in this doc is the issue of MTU support.
Secs 3.3 and 4.6 refers to underlying frag/reassembly per RFC4944. First, these sections seem redundant; normative requirements should appear in only one section if both are retained.
[Remy]Thanks for indicating this redundancy. We will remove the reference of RFC4944 in the section 3.3.

More notably, the use of a 16-bit tag in that spec is already known to be problematic for IPv4 fragmentation and could cause problems here as well, e.g., per RFC4963. This issue should be addressed, notably if there is a reason why a 16-bit tag is considered sufficient for this use it should be stated or some other shim layer should be proposed with a more robust tag (e.g., 32 bits).
[Remy]I think this question has already been discussed when RFC4944 was defined. The situation shown in RFC 4963 "a host sending 1500-byte packets with a 30-second maximum packet lifetime could send at only about 26 Mbps before exceeding 65535 packets per packet lifetime" cannot be reached by the constrained PLC networks discussed in this draft. Because the constrained PLC networks are used for metering and other IOT use cases, in which the packet is not that big, and the data rate is much lower, when compared to the "high data rates networks" discussed in RFC4963.

Some minor additional suggestions follow:

The intro refers to “6lo”; this term should be defined before being used. The scenarios should include a citation if available. Similarly, LLN should be defined. Work that did not receive consensus might be mentioned elsewhere or even omitted completely, but seems premature in the intro. Also, “the previous work” in the last sentence is ambiguous; it would be useful to refer to the RFCs, the draft, or whatever else to which it refers.
[Remy]We will extend the term, add citations to the scenarios in the intro, and remove the reference to the work did not receive consensus. The previous work refers to the [RFC4944], [RFC6282], [RFC6775] and [RFC8505]. We will update it to a more specific description.

Sec 3 includes “Moreover, recently a new …”, which seems redundant; it might be just “A new…”. Again, this section (and later ones too) refers to “6lo” as a category of sorts, which needs to be defined (and included in the acronym/terminology list).
[Remy]We will update it in the next version.