Re: [secdir] Secdir telechat review of draft-ietf-6lo-plc-06

"Liubing (Remy)" <remy.liubing@huawei.com> Tue, 27 July 2021 10:00 UTC

Return-Path: <remy.liubing@huawei.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C24B3A1DB9; Tue, 27 Jul 2021 03:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 kq8n4vEitZiU; Tue, 27 Jul 2021 03:00:26 -0700 (PDT)
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 B7DE93A1DB7; Tue, 27 Jul 2021 03:00:25 -0700 (PDT)
Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GYsS05JGjz6L9kJ; Tue, 27 Jul 2021 17:48:32 +0800 (CST)
Received: from dggpeml100010.china.huawei.com (7.185.36.14) by fraeml703-chm.china.huawei.com (10.206.15.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Tue, 27 Jul 2021 12:00:21 +0200
Received: from dggpeml500011.china.huawei.com (7.185.36.84) by dggpeml100010.china.huawei.com (7.185.36.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Tue, 27 Jul 2021 18:00:14 +0800
Received: from dggpeml500011.china.huawei.com ([7.185.36.84]) by dggpeml500011.china.huawei.com ([7.185.36.84]) with mapi id 15.01.2176.012; Tue, 27 Jul 2021 18:00:14 +0800
From: "Liubing (Remy)" <remy.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>, "secdir@ietf.org" <secdir@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: Secdir telechat review of draft-ietf-6lo-plc-06
Thread-Index: AdeCzeG20waqsFskM0iYuCIAoGKJ1w==
Date: Tue, 27 Jul 2021 10:00:14 +0000
Message-ID: <c5d962c21ec442f4afa2d9b6edccf9ee@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.110.9.243]
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/secdir/TDbL77TyRNkwu10nKBomR6d8qts>
Subject: Re: [secdir] Secdir telechat review of draft-ietf-6lo-plc-06
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2021 10:00:31 -0000

Hello Robert,

Thank you for your comments. Please find my response inline.

I will fix the typos you mentioned in another mail.

Best regards,
Remy

-----邮件原件-----
发件人: Robert Sparks via Datatracker [mailto:noreply@ietf.org] 
发送时间: 2021年7月24日 2:42
收件人: secdir@ietf.org
抄送: 6lo@ietf.org; draft-ietf-6lo-plc.all@ietf.org; last-call@ietf.org
主题: Secdir telechat review of draft-ietf-6lo-plc-06

Reviewer: Robert Sparks
Review result: Has Nits

I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments.

This document is basically ready, but has nits that should be addressed before publication as Proposed Standard RFC.

Context for the ADs, from my LC review:

> This document's primary point is to standardize mappings of ipv6 
> identifiers
for using ipv6 over IEEE 1901.1, 1901.2, and IT-T G.9903 networks. > Those standards are not publicy available, and I have not reviewed how these mappings and the security mechanisms in those protocols interact.

My LC review suggested removing section 5 - Remy's response was that he would check with the WG. I don't find any discussion of that on the WG list? I still think it could be removed or moved to a separate document.
[Remy] I've checked with the WG in IETF110. The WG suggests to keep the section. Please verify it in the minutes.

My other comments have been addressed.

This version introduces a few editorial nits that I will send directly to the editors.