[CCAMP] 答复: Fw: New Version Notification for draft-zheng-ccamp-client-signal-yang-07.txt

"Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com> Sun, 31 March 2019 02:18 UTC

Return-Path: <zhenghaomian@huawei.com>
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 137C612001E; Sat, 30 Mar 2019 19:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 BEPtY0JLAKay; Sat, 30 Mar 2019 19:18:21 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 CBA69120019; Sat, 30 Mar 2019 19:18:20 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id DB6A09FB9860F6EF0578; Sun, 31 Mar 2019 03:18:17 +0100 (IST)
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 31 Mar 2019 03:18:17 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.130]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0415.000; Sun, 31 Mar 2019 10:18:14 +0800
From: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com>
To: tom petch <ietfc@btconnect.com>, "ccamp@ietf.org" <ccamp@ietf.org>
CC: "ccamp-chairs@ietf.org" <ccamp-chairs@ietf.org>
Thread-Topic: [CCAMP] Fw: New Version Notification for draft-zheng-ccamp-client-signal-yang-07.txt
Thread-Index: AdTkweaPop2gz05oTaKVGsUt+wGVbQCpd3TA
Date: Sun, 31 Mar 2019 02:18:13 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B7AF7E1@dggeml511-mbx.china.huawei.com>
References: <E0C26CAA2504C84093A49B2CAC3261A43B7A3FBD@dggeml511-mbx.china.huawei.com> <001201d4e653$9915be00$4001a8c0@gateway.2wire.net>
In-Reply-To: <001201d4e653$9915be00$4001a8c0@gateway.2wire.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.142.18]
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/ccamp/F0Zvxy1VGaWEt6T6r8HqP6Ltr1Q>
Subject: [CCAMP] =?utf-8?b?562U5aSNOiAgRnc6IE5ldyBWZXJzaW9uIE5vdGlmaWNh?= =?utf-8?q?tion_for_draft-zheng-ccamp-client-signal-yang-07=2Etxt?=
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: Sun, 31 Mar 2019 02:18:24 -0000

Thank you Tom for the review again. We have left a comment in 'open issues' to check with RFC8407. 

Will also try the best to address the reference/format issue in the next update, I agree with you, it may be better to do after WG adoption. 

Best wishes,
Haomian

-----邮件原件-----
发件人: tom petch [mailto:ietfc@btconnect.com] 
发送时间: 2019年3月30日 1:22
收件人: Zhenghaomian (Zhenghaomian, Optical Technology Research Dept) <zhenghaomian@huawei.com>;; ccamp@ietf.org
抄送: ccamp-chairs@ietf.org
主题: Re: [CCAMP] Fw: New Version Notification for draft-zheng-ccamp-client-signal-yang-07.txt

Zheng

I note that in the YANG module, you reference IEEE 802.1Q but in the list of references you have IEEE 802.1q.  In the IEEE, case matters so one is right and one is wrong (but I have not checked to see which is which).

MEF 10 is a bit limp for a reference; I think you need to expand MEF and give a URL for the document even if RFC6004 is just as limp.

Security Considerations is still not the current text (which references TLS 1.3 and HTTPS); RFC8407 tells you where to find it

Line lengths are ok but the splits are a bit clunky - there is pyang option to format for a chosen line length, I am unsure if that is what you are using.

More technically, I wonder about the choice of prefix; they customarily go from more important to less which ethtsvc does not do for me; thus the prefix for optical transport networks YANG modules start otn...
which seems just right.  If this is also to do with transport networks, and client service, then should they start with tn... or cs..?

Think of what other modules are likely to be sitting alongside this one, and how the prefixes will look alongside each other; I do like my labels to collate so that like sits along like once sorted.

I see no rush to change this - it can all wait until after adoption if that suits you better; the point about prefix would benefit from a wider input from others who know what is, or is about to be, out there.

Tom Petch

----- Original Message -----
From: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)"
<zhenghaomian@huawei.com>;
To: <ccamp@ietf.org>;
Cc: <ccamp-chairs@ietf.org>;
Sent: Wednesday, March 27, 2019 5:29 PM
>
> This work is updated according to the discussion in the working group.
The usage of terminology 'transport' is replaced by 'transport network'.
Some clean-up have been done as well in this version. We tried our best to solve the comments in https://mailarchive.ietf.org/arch/msg/ccamp/GQ4oxkx1QvWFRNyJTlu6L8UjpE4.
Thanks again to Mr. Petch for the careful review.
>
> It is proposed to proceed this version for WG adoption, thank you.
>
> Best wishes,
> Haomian
>
>
> -----邮件原件-----
> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> 发送时间: 2019年3月28日 1:24
> 收件人: Xufeng Liu <xufeng.liu.ietf@gmail.com>;; Zhenghaomian
(Zhenghaomian, Optical Technology Research Dept) <zhenghaomian@huawei.com>;; Italo Busi <Italo.Busi@huawei.com>;; Yunbin Xu <xuyunbin@ritt.cn>;; Francesco Lazzeri <francesco.lazzeri@ericsson.com>;; Anton Snitser <antons@sedonasys.com>;; Giuseppe Fioccola <giuseppe.fioccola@huawei.com>;; Aihuaguo (Aihua Guo, CRC) <aihuaguo@huawei.com>;; Italo Busi <Italo.Busi@huawei.com>;; Yang Zhao <zhaoyangyjy@chinamobile.com>;
> 主题: New Version Notification for
draft-zheng-ccamp-client-signal-yang-07.txt
>
>
> A new version of I-D, draft-zheng-ccamp-client-signal-yang-07.txt
> has been successfully submitted by Haomian Zheng and posted to the
IETF repository.
>
> Name: draft-zheng-ccamp-client-signal-yang
> Revision: 07
> Title: A YANG Data Model for Transport Network Client Signals Document 
> date: 2019-03-27
> Group: Individual Submission
> Pages: 50
> URL:
https://www.ietf.org/internet-drafts/draft-zheng-ccamp-client-signal-yan
g-07.txt
> Status:
https://datatracker.ietf.org/doc/draft-zheng-ccamp-client-signal-yang/
> Htmlized:
https://tools.ietf.org/html/draft-zheng-ccamp-client-signal-yang-07
> Htmlized:
https://datatracker.ietf.org/doc/html/draft-zheng-ccamp-client-signal-ya
ng
> Diff:
https://www.ietf.org/rfcdiff?url2=draft-zheng-ccamp-client-signal-yang-0
7
>
> Abstract:
>    A transport network is a server-layer network to provide
connectivity
>    services to its client.  The topology and tunnel information in the
>    transport layer has already been defined by generic Traffic-
>    engineered models and technology-specific models (e.g., OTN, WSON).
>    However, how the client signals are accessing to the network has
not
>    been described.  These information is necessary to both client and
>    provider.
>
>    This draft describes how the client signals are carried over
>    transport network and defines YANG data models which are required
>    during configuration procedure.  More specifically, several client
>    signal (of transport network) models including ETH, STM-n, FC and
so
>    on, are defined in this draft.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
submission until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>