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

tom petch <> Sat, 09 March 2019 12:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1AB0C12787D for <>; Sat, 9 Mar 2019 04:51:10 -0800 (PST)
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 Cb-VEBqs78xF for <>; Sat, 9 Mar 2019 04:51:08 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C272F124B0C for <>; Sat, 9 Mar 2019 04:51:07 -0800 (PST)
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=6QlfV9xeYO0zSTnLetqzDmL+22BbKkXZOtkcOwMgpEI=; b=RRmlVz5fqUNiO2CwEtoogCWCmQrsSBy7UsDziPxtDbCbywEvlxCVIUqjKlJHjtECw7n7dOwXwtHHyHy9CtiXFsL3pewTHWUkTgwBfBueCjirax0PGYCQvqCpiJlNJwtjNusqkbmvVwVOBlbWJspLrxPDXCPDjJQEU8S82q93evQ=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.8; Sat, 9 Mar 2019 12:51:05 +0000
Received: from ([fe80::a8c3:4982:8378:9a45]) by ([fe80::a8c3:4982:8378:9a45%3]) with mapi id 15.20.1709.009; Sat, 9 Mar 2019 12:51:05 +0000
From: tom petch <>
To: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <>, "" <>
Thread-Topic: [CCAMP] Fw: New Version Notification for draft-zheng-ccamp-client-signal-yang-05.txt
Thread-Index: AQHU1nbCXX6OmuSvJEGzuL7OKc5DAQ==
Date: Sat, 9 Mar 2019 12:51:05 +0000
Message-ID: <01f801d4d676$75a1a5c0$>
References: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-clientproxiedby: LO2P265CA0152.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9::20) To (2603:10a6:803:76::27)
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: bb07baa5-b410-4f51-8546-08d6a48de4ab
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB4032;
x-ms-traffictypediagnostic: VI1PR07MB4032:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <>
x-forefront-prvs: 0971922F40
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(39860400002)(376002)(136003)(346002)(199004)(13464003)(189003)(3846002)(97736004)(25786009)(1556002)(14496001)(66574012)(15650500001)(5660300002)(86362001)(81686011)(106356001)(105586002)(61296003)(81816011)(76176011)(102836004)(6346003)(386003)(6506007)(52116002)(99286004)(26005)(71200400001)(71190400001)(14444005)(256004)(68736007)(6116002)(6486002)(229853002)(50226002)(8936002)(84392002)(2906002)(7736002)(966005)(305945005)(478600001)(486006)(476003)(9686003)(86152003)(446003)(6512007)(14454004)(6306002)(81156014)(4720700003)(6436002)(44736005)(81166006)(8676002)(6246003)(53936002)(2501003)(316002)(66066001)(186003)(44716002)(62236002)(110136005)(74416001)(7726001)(473944003)(414714003); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4032;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None ( does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is );
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: o1tBVibOcSMkpq5rAXdx+R5d+c9NtCbrw0P9tr+XFgx/GPlufEDA04RdpaNbQ66kk7VhkdtwHDH+DFIAml9vWO2T/vvWq4n5lz+sc+vsax+a4URHVi/niyUOJjhdNYlRkFE7UHCScXU3hBg2aAOFWey13WJ2JSe5RkYCb4N494Z9jH0riseofwRX2vzDU1x0BuIniaY3VQ3MfuqV4i0xGdd/qnrCcQlLrwxTnYT6v9fgto6t7HA106Bk7g8oGfgkc8ei+JDAwRUjSaQ/mDV0uVeZYBM/W44hnwypKphREIKphOQqHoSw1Hn4bCATYtoObWe3/jhswc4Xsr5gPlI+1s/pEM/AXdydoSGfBlmR69ygy+6hEY1x8P7qXQ0qhB9GKZekgvufF8y4CNU03F1fukhF8XWkrI5Y7fK3FZvtEVA=
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bb07baa5-b410-4f51-8546-08d6a48de4ab
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2019 12:51:05.5355 (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: VI1PR07MB4032
Archived-At: <>
Subject: Re: [CCAMP] Fw: New Version Notification for draft-zheng-ccamp-client-signal-yang-05.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: Sat, 09 Mar 2019 12:51:10 -0000

----- Original Message -----
From: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)"
Sent: Friday, March 08, 2019 5:49 AM

> Dear Ccampers,
> We have updated this work. Compared with -03, there are the following
> - Integrating this work with two more experts (Thanks Francesco and
> - Indicating necessity of the models, and specify their relationship
with existing models, in section 3;
> - Update the modules, ietf-trans-client-service, ietf-eth-tran-service
and ietf-eth-tran-types with new attributes, e.g., end-point and PW
> - For the resilience information and pm-config, there is still pending
work to be done, place holders have been put for future work.
> The authors believe this work is stable in working scope and
functionality, and request for a WG adoption. Please feel free to review
and leave your comments to us. Thank you.

Since you ask...

The YANG needs some more work, mostly of an administrative kind.

Abstract/Introduction should say whether or not NMDA is supported.

good practice is to have a section in the body of the I-D which lists
the prefixes used in a module and where they can be found e.g.
   | Prefix  | YANG module                  | Reference       |
   | l1csm   | ietf-l1cms                   | [RFC XXXX]      |
   | yang    | ietf-yang-types              | [RFC6991]       |

good practice is to have a section just before each YANG module listing
the documents that it imports from and references
   This module imports typedefs and modules from [RFC6991], [RFC8343]
   and [RFC7224], and it references [TR102311], [EN302217-1],
   [EN301129], and [G.826].

YANG modules must have a copyright statement

YANG modules must say where they come from e.g.
  reference "RFC XXXX: A YANG Data Model for Transport Network Client

References in a YANG module must appear in the references of the I-D
MEF 10
RFC 2697
RFC 2698
RFC 4115

YANG import statements need a reference e.g.
     import ietf-routing-types {
       prefix "rt-types";
       reference "RFC 8294 - Common YANG Data Types for the
                  Routing Area";     }

'Security Considerations' are not the current text

Some line lengths are too long for an RFC

IANA Considerations !

All of which makes the I-D easier to follow, easier to assess for
adoption (or not:-)

Tom Petch

> BTW, please forget about -04 of this work as the model inside was not
correct (my apologize...).
> Best wishes,
> Haomian (On behalf of all the authors & contributors)
> -----邮件原件-----
> 发件人: []
> 发送时间: 2019年3月8日 13:02
> 收件人: Xufeng Liu <>;; Zhenghaomian
(Zhenghaomian, Optical Technology Research Dept)
<>;; 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-05.txt
> has been successfully submitted by Haomian Zheng and posted to the
IETF repository.
> Name: draft-zheng-ccamp-client-signal-yang
> Revision: 05
> Title: A YANG Data Model for Transport Network Client Signals
> Document date: 2019-03-08
> Group: Individual Submission
> Pages: 46
> 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