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

tom petch <> Fri, 29 March 2019 17:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B43AA1202D1; Fri, 29 Mar 2019 10:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.247
X-Spam-Status: No, score=0.247 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id F--DZCSwD5c0; Fri, 29 Mar 2019 10:22:24 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 153801202C6; Fri, 29 Mar 2019 10:22:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1BUkj29m7BOpV5KenPow87db49c64OkZOW/eJ8z2Bj0=; b=GoPYy+oAf23glYVGbYOM80nCYupfUG2mdNz7h3G9LElH7p/V1Bj9mmLIMlq1q/cDyWZQ/2nig8mY/Ff6c31k9sf2GwxrGJVsDDW9UCOl6dXIG4PtsfMKiXMSQTvbx6ecVuNvwoDlYANJFhdMEBDmFuVvHqMA+pcM6isYJNhYZwY=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.6; Fri, 29 Mar 2019 17:22:21 +0000
Received: from ([fe80::b5b0:a479:a08:54d9]) by ([fe80::b5b0:a479:a08:54d9%4]) with mapi id 15.20.1750.014; Fri, 29 Mar 2019 17:22:21 +0000
From: tom petch <>
To: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <>, "" <>
CC: "" <>
Thread-Topic: [CCAMP] Fw: New Version Notification for draft-zheng-ccamp-client-signal-yang-07.txt
Thread-Index: AQHU5lP3IB8ZVxU7YU2/tm6bNkbH8Q==
Date: Fri, 29 Mar 2019 17:22:21 +0000
Message-ID: <001201d4e653$9915be00$>
References: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-clientproxiedby: LNXP265CA0019.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5e::31) To (2603:10a6:10:7b::20)
authentication-results: spf=none (sender IP is );
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3af7d3a1-88c3-4255-d239-08d6b46b1a0b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:DB7PR07MB5993;
x-ms-traffictypediagnostic: DB7PR07MB5993:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <>
x-forefront-prvs: 0991CAB7B3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(376002)(346002)(136003)(39860400002)(13464003)(199004)(189003)(9686003)(106356001)(4720700003)(14444005)(15650500001)(966005)(68736007)(66066001)(62236002)(6506007)(102836004)(66574012)(386003)(50226002)(2906002)(256004)(6436002)(1556002)(26005)(44716002)(8936002)(6486002)(81686011)(81166006)(229853002)(186003)(486006)(52116002)(105586002)(6116002)(81816011)(61296003)(81156014)(3846002)(8676002)(476003)(44736005)(2501003)(7736002)(71190400001)(14454004)(14496001)(305945005)(71200400001)(446003)(84392002)(76176011)(86362001)(478600001)(25786009)(5660300002)(6246003)(110136005)(316002)(86152003)(6306002)(99286004)(97736004)(6512007)(53936002)(4326008)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB5993;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: jJXBPm3AuVSd9dskbIaoT06vDNZ7HG1q1WiqGey3YeDN/pWJ30f1CVh9nAkx/Ae3d6rq+uz32P4hMAnLCd4hdo65wfWu6jSfWk4XDWh8WWFJFZqKBNrrdQrjoMn23cWilElW0s11z+8W84U9VmkVnNAIuu9u9xUEq/DuvBrX/txCxd5cGTcfKwWL83PO3w47xR3o1KnTUu4snAPd0IxWZLz7IUBFFT8PmDwytMZs8nXx9+sRSgGb9Q/kBploeSPT8M29DTt440Y1NZB+Ck1JRGN4iu1RYBohwznBCySV/8cN5tO+ZsvPyB3ebw6WM6b4fmXQh6TbsgQ2tkIrkaw/URhd0a+yg0R2LQmTFzWxBZ8f14+6E2XKcsH+JGEtt6a4fW9sshIJDqYZLMQf5ybaahKucbcFArBruBPEkYKSkIg=
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3af7d3a1-88c3-4255-d239-08d6b46b1a0b
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Mar 2019 17:22:21.3498 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5993
Archived-At: <>
Subject: Re: [CCAMP] Fw: New Version Notification for draft-zheng-ccamp-client-signal-yang-07.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion list for the CCAMP working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 29 Mar 2019 17:22:37 -0000


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

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)"
To: <>;
Cc: <>;
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
Thanks again to Mr. Petch for the careful review.
> It is proposed to proceed this version for WG adoption, thank you.
> Best wishes,
> Haomian
> -----邮件原件-----
> 发件人: []
> 发送时间: 2019年3月28日 1:24
> 收件人: Xufeng Liu <>;; Zhenghaomian
(Zhenghaomian, Optical Technology Research Dept)
<>;; Italo Busi <>;; Yunbin Xu
<>;; Francesco Lazzeri <>;;
Anton Snitser <>;; Giuseppe Fioccola
<>;; Aihuaguo (Aihua Guo, CRC)
<>;; Italo Busi <>;; Yang Zhao
> 主题: New Version Notification for
> 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:
> Status:
> Htmlized:
> Htmlized:
> Diff:
> Abstract:
>    A transport network is a server-layer network to provide
>    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
>    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
>    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
> The IETF Secretariat
> _______________________________________________
> CCAMP mailing list