Re: [L2sm] AD review of draft-ietf-l2sm-l2vpn-service-model

Qin Wu <bill.wu@huawei.com> Thu, 22 February 2018 05:57 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16789126FDC; Wed, 21 Feb 2018 21:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level:
X-Spam-Status: No, score=-4.219 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, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01, 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 ytfdPR1PozOo; Wed, 21 Feb 2018 21:57:19 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB61D126D3F; Wed, 21 Feb 2018 21:57:18 -0800 (PST)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E3EAC97A8A33A; Thu, 22 Feb 2018 05:57:14 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 22 Feb 2018 05:57:05 +0000
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.231]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0361.001; Thu, 22 Feb 2018 13:56:57 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "draft-ietf-l2sm-l2vpn-service-model@ietf.org" <draft-ietf-l2sm-l2vpn-service-model@ietf.org>
CC: "l2sm@ietf.org" <l2sm@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: [L2sm] AD review of draft-ietf-l2sm-l2vpn-service-model
Thread-Index: AQHTq4RWHf0G7IVNAkKpE0YPrIvSyaOv6rfQ
Date: Thu, 22 Feb 2018 05:56:56 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AD6486E@nkgeml513-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.67]
Content-Type: multipart/mixed; boundary="_004_B8F9A780D330094D99AF023C5877DABA9AD6486Enkgeml513mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/-oS4o0KF4W3jNCXvpzG3EJWwMFk>
Subject: Re: [L2sm] AD review of draft-ietf-l2sm-l2vpn-service-model
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2018 05:57:21 -0000

Thanks Benoit.
Authors, please take care of AD review’s comments.
It requires some editorial changes to address them.

-Qin
发件人: L2sm [mailto:l2sm-bounces@ietf.org] 代表 Benoit Claise
发送时间: 2018年2月22日 10:25
收件人: l2sm@ietf.org
主题: [L2sm] AD review of draft-ietf-l2sm-l2vpn-service-model

Dear all,

Here is the AD review.

- Section 1.2.
You want to use the YANG tree diagrams in draft-ietf-netmod-yang-tree-diagrams-04<https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-tree-diagrams/>
I advice a section similar to https://tools.ietf.org/html/draft-ietf-netmod-rfc7223bis-03#section-1.3

- The draft is NMDA compliant. It should be mentioned.
Ex: draft-ietf-netmod-rfc7223bis-03, in the abstract and intro

   The YANG model in this document conforms to the Network Management

   Datastore Architecture defined in I-D.ietf-netmod-revised-datastores.


- The references to RFC6020 should be changed to RFC7950, except in the IANA considerations.
The YANG module is YANG 1.1

-

 revision 2018-02-05 {

    description

      "Initial revision -04 version";

    reference

      "draft-ietf-l2sm-l2vpn-service-model-05.txt<https://tools.ietf.org/html/draft-ietf-l2sm-l2vpn-service-model-05.txt>

       A YANG Data Model for L2VPN Service Delivery.";

  }



This should be changed to

 revision 2018-02-05 {

    description

      "Initial revision -04 version";

    reference

      "RFC XXXX: A YANG Data Model for L2VPN Service Delivery.";

  }


- https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
Please doublecheck the template.
The first sentence is:
The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040].


Please publish a new version asap.
Note that those changes doesn't prevent the IETF LC to start now.
Hopefully, we could shoot for the March 8th IESDG telechat.

Regards, Benoit