Re: [CCAMP] hi!  two I-Ds about FlexE posted.   Suggestions and comments are welcome. Thanks!

<niu.xiaobing@zte.com.cn> Wed, 27 March 2019 07:45 UTC

Return-Path: <niu.xiaobing@zte.com.cn>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10C3C120274 for <ccamp@ietfa.amsl.com>; Wed, 27 Mar 2019 00:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 kz9Y3jpXCPmQ for <ccamp@ietfa.amsl.com>; Wed, 27 Mar 2019 00:45:50 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 6E1A412026B for <ccamp@ietf.org>; Wed, 27 Mar 2019 00:45:49 -0700 (PDT)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Forcepoint Email with ESMTPS id 0DB6BCBCEC2341610D57; Wed, 27 Mar 2019 15:45:48 +0800 (CST)
Received: (from root@localhost) by mse01.zte.com.cn id x2R7jk2C024041; Wed, 27 Mar 2019 15:45:46 +0800 (GMT-8) (envelope-from niu.xiaobing@zte.com.cn)
Message-Id: <201903270745.x2R7jk2C024041@mse01.zte.com.cn>
Received: from kjyxapp02.zte.com.cn ([10.30.12.201]) by mse01.zte.com.cn with SMTP id x2P21Td1015666; Mon, 25 Mar 2019 10:01:29 +0800 (GMT-8) (envelope-from niu.xiaobing@zte.com.cn)
Received: from mapi (kjyxapp03[null]) by mapi (Zmail) with MAPI id mid17; Mon, 25 Mar 2019 10:01:30 +0800 (CST)
Date: Mon, 25 Mar 2019 10:01:30 +0800
X-Zmail-TransId: 2b055c98367a592d5ac6
X-Mailer: Zmail v1.0
In-Reply-To: <036101d4e0ad$861564a0$4001a8c0@gateway.2wire.net>
References: 201903220553.x2M5rGqN054270@mse02.zte.com.cn, 036101d4e0ad$861564a0$4001a8c0@gateway.2wire.net
Mime-Version: 1.0
From: niu.xiaobing@zte.com.cn
To: ietfc@btconnect.com
Cc: ccamp@ietf.org, xuyunbin@caict.ac.cn
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse01.zte.com.cn x2R7jk2C024041
X-MSS: AUDITRELEASE@mse01.zte.com.cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/IS1WQZ67xgHHCh25CNGYqxHHPD4>
Subject: Re: [CCAMP] hi!  two I-Ds about FlexE posted.   Suggestions and comments are welcome. Thanks!
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2019 07:45:54 -0000

Hi Tom,


Thanks a lot for your suggestions! I'll revise the file accordingly.


BRs,




牛小兵     Xiaobing NIU



E: niu.xiaobing@zte.com.cn


www.zte.com.cn







原始邮件



发件人:tompetch <ietfc@btconnect.com>
收件人:牛小兵10019881;ccamp@ietf.org <ccamp@ietf.org>;
抄送人:xuyunbin@caict.ac.cn <xuyunbin@caict.ac.cn>;
日 期 :2019年03月22日 20:50
主 题 :Re: [CCAMP] hi!  two I-Ds about FlexE posted.   Suggestions and comments are welcome. Thanks!


---- Original Message -----
From: <niu.xiaobing@zte.com.cn>
Sent: Friday, March 22, 2019 2:21 AM

> hi,
>
> We've posted two I-Ds about FlexE, shown in following links.
>
> draft-wang-ccamp-flexe-control-analysis
>
> draft-xiaobn-ccamp-flexe-yang-mod
>
> Suggestions and comments are welcome.

I notice that you also published, in the run up to the last IETF,
 draft-xiaobn-flexe-yang-mod-00
which looks rather similar, down to the same points that need fixing in
a YANG module, such as:

NMDA support or lack thereof needs mentioning up front

Requirements language needs to refer to RFC8174

The tree diagram should have an Informative Reference to RFC8340 rather
than RYO

Several lines are too long for an RFC making them awkward to read

YANG modules version is 1 while the Introduction references 1.1

YANG modules import statements lack description clauses

YANG modules lack copyright statements

YANG modules lack references e.g. to the FlexE documents

Security considerations is out of date - you need to reference RESTCONF
and TLS 1.3

IANA Considerations needs to specfy prefix

Terminology covers the FlexE terminology but not the YANG terminology
which readers may, or may not, be familiar with.

HTH

Tom Petch

> Thanks!
>
> BRs,
>
> 牛小兵     Xiaobing NIU
>
>
> E: niu.xiaobing@zte.com.cn
>
> www.zte.com.cn


> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>