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

"Liubing (Remy)" <remy.liubing@huawei.com> Fri, 05 March 2021 03:53 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 C32F33A1CFD; Thu, 4 Mar 2021 19:53:09 -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 tBCkvvZcU8de; Thu, 4 Mar 2021 19:53:08 -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 143C93A1CF5; Thu, 4 Mar 2021 19:53:08 -0800 (PST)
Received: from fraeml714-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DsDCN072Yz67vgR; Fri, 5 Mar 2021 11:45:20 +0800 (CST)
Received: from fraeml798-chm.china.huawei.com (10.206.15.19) by fraeml714-chm.china.huawei.com (10.206.15.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 5 Mar 2021 04:53:06 +0100
Received: from fraeml798-chm.china.huawei.com (10.206.15.19) by fraeml798-chm.china.huawei.com (10.206.15.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 5 Mar 2021 04:53:06 +0100
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by fraeml798-chm.china.huawei.com (10.206.15.19) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Fri, 5 Mar 2021 04:53:06 +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 11:53:01 +0800
From: "Liubing (Remy)" <remy.liubing@huawei.com>
To: Dan Romascanu <dromasca@gmail.com>, "ops-dir@ietf.org" <ops-dir@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: Opsdir last call review of draft-ietf-6lo-plc-05
Thread-Index: AdcRcp6rXK4AdR34STWtiM/pfDa+tQ==
Date: Fri, 5 Mar 2021 03:53:01 +0000
Message-ID: <BB09947B5326FE42BA3918FA28765C2E014F4FD8@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/q0SrNjU0gSEhuGPKXEdNiefwFXw>
Subject: Re: [6lo] Opsdir 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 03:53:10 -0000

Hello Dan,

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

Best regards,
Remy

-----邮件原件-----
发件人: Dan Romascanu via Datatracker [mailto:noreply@ietf.org] 
发送时间: 2021年2月12日 18:01
收件人: ops-dir@ietf.org
抄送: 6lo@ietf.org; draft-ietf-6lo-plc.all@ietf.org; last-call@ietf.org; dromasca@gmail.com
主题: Opsdir last call review of draft-ietf-6lo-plc-05

Reviewer: Dan Romascanu
Review result: Has Issues

This document describes how IPv6 packets are transported over constrained Power Line Communication (PLC) networks. It is a clear and well-written document and its content is relevant for all operators that will have such networks under their administration. I have however one concern that I would suggest the OPS AD to clarify before approving this document. There is no mention in the document of the operational and manageability aspects. How will these networks be managed, monitored, troubleshooted?  Which existing OAM protocols and procedures apply and will extensions be needed? Are there / will there be any new new interface types ("ifType" values) required as per RFC 8892? Maybe other documents exist in the IEEE or ITU-T that document these aspects - if so it would be useful to reference them. If other documents are in planning in the IETF on this respect - please clarify.

[Remy]That's a very good question. The constrained PLC networks are not managed in the same way as the enterprise network or carrier network. The constrained PLC networks as the other IoT networks, are designed to be self-organized and self-managed. The software or firmware is flushed into the devices before deployment by the vendor or operator. And during the deployment process, no extra configuration is needed to get the device connected to each other. Once a device becomes offline, it will go back to the bootstrapping stage and tries to rejoin the network. The onboard status of the devices and the topology of the PLC network can be visualized via the gateway. The recently-formed iotops WG in IETF is aming to design more features for  the management of IOT networks.