Re: [CCAMP] Fw: I-D Action: draft-ietf-ccamp-otn-tunnel-model-04.txt

tom petch <ietfc@btconnect.com> Fri, 24 August 2018 08:54 UTC

Return-Path: <ietfc@btconnect.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 020F4130D7A for <ccamp@ietfa.amsl.com>; Fri, 24 Aug 2018 01:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.187
X-Spam-Level: ***
X-Spam-Status: No, score=3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RATWARE_OUTLOOK_NONAME=2.95, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 6iCjok5X0q_C for <ccamp@ietfa.amsl.com>; Fri, 24 Aug 2018 01:54:55 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20112.outbound.protection.outlook.com [40.107.2.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34E90130DF6 for <ccamp@ietf.org>; Fri, 24 Aug 2018 01:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8q/cZ1lWIVvqm2IywhAxwiMI9AqfShtlN1sOcNbW0KY=; b=dBGj7CFY149yQjo3XtB2xA6HjkJacOQYNnhhE59g0hPQH/Me9pbtbIDyipVQ2Bwzyq/RSL/GsUDa/zo4iqVRagfadnNBxkabOceCdAkpAF96LYGKwbnki2fTrXpd7roAsh4qBeYvxCOg5h524oF6ZS6spGWtMB6Gslhoj3kP/FA=
Received: from VI1PR07MB0831.eurprd07.prod.outlook.com (10.161.107.154) by VI1PR07MB3343.eurprd07.prod.outlook.com (10.175.244.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1101.5; Fri, 24 Aug 2018 08:54:52 +0000
Received: from VI1PR07MB0831.eurprd07.prod.outlook.com ([fe80::715f:f4a2:caef:d939]) by VI1PR07MB0831.eurprd07.prod.outlook.com ([fe80::715f:f4a2:caef:d939%2]) with mapi id 15.20.1080.010; Fri, 24 Aug 2018 08:54:52 +0000
From: tom petch <ietfc@btconnect.com>
To: "Zhenghaomian (Zhenghaomian, Optical &Microwave Technology Research Dept)" <zhenghaomian@huawei.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: [CCAMP] Fw: I-D Action: draft-ietf-ccamp-otn-tunnel-model-04.txt
Thread-Index: AQHUO4gfnbkmSZUhsEi4QFO+u+uNZQ==
Date: Fri, 24 Aug 2018 08:54:52 +0000
Message-ID: <019801d43b87$a1f070a0$4001a8c0@gateway.2wire.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: AM4P190CA0018.EURP190.PROD.OUTLOOK.COM (2603:10a6:200:56::28) To VI1PR07MB0831.eurprd07.prod.outlook.com (2a01:111:e400:508e::26)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [81.131.229.47]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB3343; 6:FnuUjiWWG9CeOD7MN2Zt1wiHZ0l41mhBHaNjTh3eBgpt1b2kRDvAQ9JfFZa6+r1lVPOiEWOq2qj08RQNmDhYY+p8BnwU50WR6ihoh92KjVwEay32TlT2SoG5niiuJ1TGEWnnrLdUu6v35IYns0DVR6Ya+sit7XIw9WXVlHbW/ilG8QZTV8UZ1WbzXXg0kf4+TBahaa5X5TFx5sTdMX4gF7Zy/p2H9KyaWQ78coGOk3l1iaK8EbONJEYsVnLKASUiMNd4YAOq9hD1eBWLAZedJU7c7rByDRLYxjpB12WvX9K8C1CABLQBkJg5etsSXpbpEoy+QT4iQ5OhDFHvlI1B4lbQJcqh/Bg+/CC6rk/+9nmmOiYHfyQa6Ly6g0G//pv8hMLZIUteubnXhLkqS0WGe2A7CMRVwKcU0oP2Qf4+GfSGE2UDMgmk4Ofzg+8hlGnVivTZTEycyi0+dqrcCe0ckg==; 5:CM3rlU+WFftjLvuLqAR3cClK/7VEeYu8CafzuLEcukLY3gF7alnp3M/MnY1mJ97aohZrpEH7wuQ4EfVdzyQqSJYMpSaQC3mwo2GmBXkvVf2VMmbIdxlvtYEmZgD7cNi7aXu74z98frraMY2c26Tl4yFjMQZd3IZ+ekjrWFSYZls=; 7:LPmUEocVm4dzaCLRq1N9TPSUm9Y6RBT8rqaj2h1vKq3DKSL4+BFBBXKIIpJi8H1P8raBAyBot36+YZm9ONdgD22l4esG0Zg8VWMtbuNLXpqSaUeS48rqsq97szJi5gD5ed87GHhsVCgbb8gTvAIDrAPHGciv4EGb+vAzKo4JaDxBgJydIw3j/nReU5vEK+KEkt1NpJDgwTNazh+47syKxWEX0iRIQC5dDz/5+AbDXU9wPBCP2UY8Ba1sXlJSl5Y6
x-ms-office365-filtering-correlation-id: 5e7e1530-35cd-4f96-9515-08d6099f4155
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7193020); SRVR:VI1PR07MB3343;
x-ms-traffictypediagnostic: VI1PR07MB3343:
x-microsoft-antispam-prvs: <VI1PR07MB33433507B7772B5DC7B42BA1A0360@VI1PR07MB3343.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(178726229863574)(120809045254105)(50582790962513)(219612443155931);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231311)(944501410)(52105095)(10201501046)(93006095)(93001095)(3002001)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(201708071742011)(7699016); SRVR:VI1PR07MB3343; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB3343;
x-forefront-prvs: 07749F8C42
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(396003)(376002)(346002)(136003)(199004)(189003)(13464003)(386003)(66066001)(97736004)(99286004)(6506007)(102836004)(106356001)(105586002)(186003)(26005)(478600001)(14496001)(966005)(1556002)(84392002)(14454004)(86362001)(2906002)(68736007)(7736002)(81166006)(6246003)(305945005)(8676002)(81156014)(2900100001)(52116002)(6116002)(3846002)(5250100002)(25786009)(33896004)(5660300001)(8936002)(2501003)(256004)(476003)(53936002)(6486002)(316002)(229853002)(44736005)(486006)(6306002)(9686003)(6436002)(86152003)(14444005)(110136005)(6512007); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB3343; H:VI1PR07MB0831.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: egyIMzNFI+oV8sZNKCcV+yPdImQna9DbRwxn4gFzaCmBIXnH3omRESOxCYDYulHOGsolYao2nwkEb3aaX9jvBgkXPldTcYoo8cP5kA61avOrmABQakbNAbinF12HkxXgme4RTC/40Hi6PFiT7SH/XaCNUBVaJ87JPV+UVtGRG0lb3BvAisfS5IB4GiwKVPYdNMDmyQt9kEt4iJ11xq9EgbJjZhGtsSna3oY+liURwZa6a3mAfY2SWJpLDPAHGEJpsJ3bQ0YDwvvCNFRZj9/7GZpVazIb5dPGIplHmTzX64wX/TKg11X+3bOcID65OqF5PR4TUOm5f6Q1PrjYINSWP/fmqEUfWs9Rvo2U8wHKw98=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="gb2312"
Content-ID: <42172D2257418F40A13F26B022DA66B5@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5e7e1530-35cd-4f96-9515-08d6099f4155
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Aug 2018 08:54:52.7187 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3343
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/hXI4oC963smxW20TxUxK-S6L6hk>
Subject: Re: [CCAMP] Fw: I-D Action: draft-ietf-ccamp-otn-tunnel-model-04.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 24 Aug 2018 08:54:58 -0000

Sorry wrong I-D; the comments I posted yesterday in this thread were on
otn-topo.

So looking at otn-tunnel-model-05 (I hope:-)

- RFC have a line length limit which is exceeded in many places by lines
such as
/* Augment label restrictions for the reverse direction of
path-out-segment of reverse primary path */
[mmm sounds familar]

- a reference to
    "module ietf-otn-types in this Document";
will not make any sense when this YANG module is free standing; you need
something like
"RFC XXXX: OTN Tunnel YANG Model";

In passing, the RFC Editor like a Note at the start of the I-D covering
all uses of XXXX rather than having multiple notes scattered through the
I-D (I asked them:-)

- The YANG Module references
  RFC6991: Common YANG Data Types"
which is good but this then needs to appear in the I-D Normative
References; you then need a [RFC6991] reference in the body of the
document which is usually achieved by putting a note at the start of
section 5

'These YANG modules import from RFC6991: Common YANG Data Types" ....
or some such as in, e.g.
draft-ietf-ccamp-mw-yang

- The YANG module references
  G.709/Y.1331, February 2016: Interfaces for the Optical
but I see no matching entry in the I-D Normative References

- IANA Considerations should reference RFC6020 not RFC7950 since RFC7950
does no more than say 'see RFC6020' (something I only just learnt)

Tom Petch

----- Original Message -----
From: "t.petch" <ietfc@btconnect.com>
To: "Zhenghaomian (Zhenghaomian, Optical &Microwave Technology Research
Dept)" <zhenghaomian@huawei.com>om>; <ccamp@ietf.org>
Sent: Thursday, August 23, 2018 4:44 PM


> While you are at it
>
> - the YANG module file statement needs a date on it e.g. as in
> draft-ietf-ccamp-mw-yang
>
> - I see G.709 referenced in the YANG module but do not see a reference
> that matches this in the I-D References
>
> - I see
> I-D.ietf-teas-yang-te
> in the YANG module but not in the I-D References
>
> - there is a line length limit in RFC which is exceeded in many places
> in the YANG module by lines such as
> /* Augment egress label restrictions end of connectivity-matrix
> information-source */
>
> - IANA Considerations should reference RFC6020 not RFC7950 since
RFC7950
> does no more than say 'see RFC6020' (something I only just learnt)
>
> Tom Petch
>
> ----- Original Message -----
> From: "Zhenghaomian (Zhenghaomian, Optical &Microwave Technology
> Research Dept)" <zhenghaomian@huawei.com>
> Sent: Thursday, August 23, 2018 9:31 AM
>
>
> > Hi, Tom,
> >
> > Thanks for point this out, we update the draft, with corresponding
> correction.
> >
> > Best wishes,
> > Haomian
> >
> > -----邮件原件-----
> > 发件人: tom petch [mailto:ietfc@btconnect.com]
> > 发送时间: 2018年8月14日 19:50
> > 收件人: Zhenghaomian (Zhenghaomian, Optical &Microwave Technology
> Research Dept) <zhenghaomian@huawei.com>om>; ccamp@ietf.org
> > 主题: Re: [CCAMP] Fw: I-D Action:
> draft-ietf-ccamp-otn-tunnel-model-04.txt
> >
> > Meanwhile, there are my usual red tape issues.
> >  - no copyright in the YANG modules
> >  - no RFC Editor note asking them to update the dates in the modules
> >  - no YANG reference statements for the import YANG statements
> > - YANG Tree diagrams is now an RFC
> >  - no I-D Reference for G.709 as referenced in the module
> >
> > I find the layout of IANA considerations not as clear as it might
be.
> I suggest
> >
> > OLD
> >
> > It is proposed that IANA should assign new URIs from the "IETF XML
> >    Registry" [RFC3688] as follows: URI:
> >    urn:ietf:params:xml:ns:yang:ietf-otn-tunnel Registrant Contact:
The
> >    IESG XML: N/A; the requested URI is an XML namespace.  URI:
> >    urn:ietf:params:xml:ns:yang:ietf-otn-types Registrant Contact:
The
> >    IESG XML: N/A; the requested URI is an XML namespace.  This
> document
> >    registers following YANG modules in the YANG Module Names
registry
> >    [RFC7950].  name: ietf-otn-tunnel namespace:
> >    urn:ietf:params:xml:ns:yang:ietf-otn-tunnel prefix: otn-tunnel
> >    reference: RFC XXXX name: ietf-otn-types namespace:
> >    urn:ietf:params:xml:ns:yang:ietf-otn-types prefix: otn-types
> >    reference: RFC XXXX
> >
> > NEW
> >
> > IANA is asked to assign URIs from the "IETF XML Registry" [RFC3688]
as
> > follows:
> >
> > URI:  urn:ietf:params:xml:ns:yang:ietf-otn-tunnel
> > Registrant Contact: The  IESG
> > XML: N/A; the requested URI is an XML namespace.
> >
> > URI: urn:ietf:params:xml:ns:yang:ietf-otn-types
> > Registrant Contact: The IESG
> > XML: N/A; the requested URI is an XML namespace.
> >
> > IANA is asked to record YANG module names in the "YANG Module Names"
> registry [RFC6020] as follows:
> >
> > name: ietf-otn-tunnel namespace:
> > urn:ietf:params:xml:ns:yang:ietf-otn-tunnel
> > prefix: otn-tunnel
> > reference: RFC XXXX
> >
> > name: ietf-otn-types namespace:
> > urn:ietf:params:xml:ns:yang:ietf-otn-types
> > prefix: otn-types
> > reference: RFC XXXX
> >
> > Just a few more newlines
> >
> > Tom Petch
> >
> > ----- Original Message -----
> > From: "Zhenghaomian (Zhenghaomian, Optical &Microwave Technology
> Research Dept)" <zhenghaomian@huawei.com>
> > To: <ccamp@ietf.org>
> > Sent: Friday, August 10, 2018 8:15 AM
> >
> > > Dear WG,
> > >
> > > We update the draft-ietf-ccamp-otn-tunnel-model, mainly updating
the
> > ietf-otn-types.yang by cleaning the identities. The types model is
> imported in the other draft draft-ietf-ccamp-otn-topo-yang for YANG
> doctor review.
> > >
> > > Thank you.
> > >
> > > Best wishes,
> > > Haomian
> > >
> > > -----邮件原件-----
> > > 发件人: CCAMP [mailto:ccamp-bounces@ietf.org] 代表
> > internet-drafts@ietf.org
> > > 发送时间: 2018年8月10日 15:10
> > > 收件人: i-d-announce@ietf.org
> > > 抄送: ccamp@ietf.org
> > > 主题: [CCAMP] I-D Action: draft-ietf-ccamp-otn-tunnel-model-04.txt
> > >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > > This draft is a work item of the Common Control and Measurement
> Plane
> > WG of the IETF.
> > >
> > >         Title           : OTN Tunnel YANG Model
> > >         Authors         : Haomian Zheng
> > >                           Aihua Guo
> > >                           Italo Busi
> > >                           Anurag Sharma
> > >                           Rajan Rao
> > >                           Sergio Belotti
> > >                           Victor Lopez
> > >                           Yunbo Li
> > >                           Yunbin Xu
> > > Filename        : draft-ietf-ccamp-otn-tunnel-model-04.txt
> > > Pages           : 62
> > > Date            : 2018-08-10
> > >
> > > Abstract:
> > >    This document describes the YANG data model for OTN Tunnels.
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > >
https://datatracker.ietf.org/doc/draft-ietf-ccamp-otn-tunnel-model/
> > >
> > > There are also htmlized versions available at:
> > > https://tools.ietf.org/html/draft-ietf-ccamp-otn-tunnel-model-04
> > >
> >
>
https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-otn-tunnel-model-
> > 04
> > >
> > > A diff from the previous version is available at:
> > >
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-otn-tunnel-model-04
> > >
> > >
> > > 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.
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > _______________________________________________
> > > CCAMP mailing list
> > > CCAMP@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ccamp
> > > _______________________________________________
> > > CCAMP mailing list
> > > CCAMP@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ccamp
> > >
> >
> >
>