Hello Michael, Sorry for this late reply. Thank you for your review.
Please see my response below. Best regards, Remy -----邮件原件----- 发件人: 6lo [mailto:[email protected]] 代表 Michael Richardson 发送时间: 2020年5月17日 7:39 收件人: [email protected] 抄送: Liubing (Remy) <[email protected]>; Carles Gomez Montenegro <[email protected]>; Liyizhou <[email protected]> 主题: Re: [6lo] FW: I-D Action: draft-ietf-6lo-plc-03.txt Hi, I have reviewed the changes from 02 to 03. I had suggested that the term PLC Device be used consistently, and I see that. At the end of the first paragraph of 3.2, "PANC" is used which surprised me, but I see it in the glossary. I'm not sure if you want to add "JRC" to the list of aliases for PANC. [Remy] I can add the full name in 3.2. "PAN Coordinator" is a term that is inherited form the PLC standards. We wanted to abbreviate it as "PCO", but PCO refer to "proxy coordinator" in IEEE 1901.1. Thus we use PANC instead. Do you have any suggestion on this abbreviation? In term of the functionality during the joining process, JRC is an alias of the PAN coordinator. Thank you for mentioning 6tisch-minimal-security. There is also a BRSKI-like 6tisch mechanism that uses IDevID. [Remy] I think you must be talking about [draft-ietf-6tisch-dtsecurity-zerotouch-join]. The minimal security is considered to be one-touch since the PSK has to be configured a priori. And this document provides a zero-touch method, in which the IDevID (provided by the manufacturer) in 802.1AR is used as the credential for authentication. The authentication is done with the help of the MASA. Am I understanding it correctly? I think the method simplifies the provisioning procedure. However, the PLC standards have not supported 802.1AR yet, thus this zero-touch method couldn't be used in the implementation at this moment. Is it the case that the PLC devices can have no L2 security as an option? I believe that you may wish to outlaw that situation. [Remy] All the PLC standards we mentioned in this document have L2 security mechanisms, such as encryption, data integrity, and anti-replay. Since this document is focused on the adaptation layer and above, the L2 security is considered to be applied by default. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- _______________________________________________ 6lo mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lo
