Re: [Teas] FW: New Version Notification for draft-lee-teas-actn-pm-telemetry-autonomics-12.txt

tom petch <ietfa@btconnect.com> Fri, 12 April 2019 16:38 UTC

Return-Path: <ietfa@btconnect.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 808B71202FD; Fri, 12 Apr 2019 09:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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: 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 qCz-di77wfiZ; Fri, 12 Apr 2019 09:38:06 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-db3eur04on0724.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0c::724]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DD24120160; Fri, 12 Apr 2019 09:38:05 -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=d2IhQRigYCRQSo2DjgcygcR/Mwn8w3JKLYnd9vqRNIo=; b=LIAke3mXtl5tNYxlF9wiRfN0PkfhQNWezgtSluqu9EMn4AeEkguP5QwqMkJC2WLGBCKRlbW/KlcGgkoXrLOeMB9lkNZdq3iDJsORlQZQSekW8QF7h8XshcB1ap1wAG6oYU09wrR1kQTQGjTadS2KvlbvA1qwK/GmEk97WN3sU9k=
Received: from DB7PR07MB4475.eurprd07.prod.outlook.com (52.135.140.145) by DB7PR07MB5978.eurprd07.prod.outlook.com (20.178.106.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.15; Fri, 12 Apr 2019 16:38:02 +0000
Received: from DB7PR07MB4475.eurprd07.prod.outlook.com ([fe80::90c3:886b:5217:9313]) by DB7PR07MB4475.eurprd07.prod.outlook.com ([fe80::90c3:886b:5217:9313%3]) with mapi id 15.20.1792.009; Fri, 12 Apr 2019 16:38:02 +0000
From: tom petch <ietfa@btconnect.com>
To: Leeyoung <leeyoung@huawei.com>, TEAS WG Chairs <teas-chairs@ietf.org>
CC: TEAS WG <teas@ietf.org>
Thread-Topic: [Teas] FW: New Version Notification for draft-lee-teas-actn-pm-telemetry-autonomics-12.txt
Thread-Index: AQHU68+zAcAe/LKeDku7nRayD8o/+A==
Date: Fri, 12 Apr 2019 16:38:02 +0000
Message-ID: <016001d4f14d$ad0a5ba0$4001a8c0@gateway.2wire.net>
References: <155424135956.6387.1551126859534085567.idtracker@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173D10E13C@sjceml521-mbx.china.huawei.com> <00f701d4ebcf$4e409540$4001a8c0@gateway.2wire.net> <7AEB3D6833318045B4AE71C2C87E8E173D1117C3@sjceml521-mbx.china.huawei.com> <011b01d4efbb$4060de40$4001a8c0@gateway.2wire.net> <7AEB3D6833318045B4AE71C2C87E8E173D111C67@sjceml521-mbx.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0381.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a3::33) To DB7PR07MB4475.eurprd07.prod.outlook.com (2603:10a6:5:3a::17)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfa@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 814ecd27-b79b-4f07-3d43-08d6bf653b14
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:DB7PR07MB5978;
x-ms-traffictypediagnostic: DB7PR07MB5978:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DB7PR07MB59784FA0A20C568859E0BBECA2280@DB7PR07MB5978.eurprd07.prod.outlook.com>
x-forefront-prvs: 0005B05917
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(136003)(366004)(39860400002)(376002)(189003)(13464003)(199004)(51914003)(51444003)(14454004)(6246003)(52116002)(1556002)(256004)(476003)(6486002)(6436002)(6512007)(229853002)(86152003)(14496001)(99286004)(5024004)(14444005)(4326008)(5660300002)(53936002)(61296003)(9686003)(4720700003)(105586002)(6306002)(316002)(68736007)(25786009)(71200400001)(71190400001)(93886005)(44736005)(62236002)(106356001)(44716002)(8676002)(66574012)(66066001)(84392002)(81166006)(3846002)(86362001)(81816011)(6116002)(81686011)(2906002)(110136005)(15650500001)(81156014)(50226002)(446003)(486006)(186003)(478600001)(386003)(8936002)(97736004)(966005)(76176011)(102836004)(7736002)(6506007)(53546011)(305945005)(26005)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB5978; H:DB7PR07MB4475.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: JhcrOIq8b4h4DzhSAJogiRmLZqoActv6/J0I5irnpuwTbbO9CqJs+yqXCT+msqArG23q/21E54mHUXKFgVVPpjg7OgLBhi7aUr/6L80kRxW3kx6ES56p+jLqzGPMt5KPpMZ/c9sppfVyJPxw72nVAChrLUWKa8zzrVnZkJG2fO7IPSMHm4b2Bz2L4jiu9jEqTO/Asm4tp5dmEsLpwbUFCJ+R9DbidL+vJlzZfyPzxj+FeJaUQWCqQ+Vp3Zhrl4aIzH28K1b/afyfh/mfdjF4eY6c5vLXybGB4F5es0DqPKufXCpiWv4N4991rjPtHZrsr4GaKspLV9ZaJxlUY6Y882HjPpEKD5UiJfc0d2Ph6zPAsM/aO2lqehfT3DOKyPzM67PhnaBeDF87ZzwKwOERbbTT9Rxv8QtE8v2f1+ErPbA=
Content-Type: text/plain; charset="utf-8"
Content-ID: <F5EB7910FDEE2C4E882B7ED4915DBCF0@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 814ecd27-b79b-4f07-3d43-08d6bf653b14
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2019 16:38:02.7841 (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: DB7PR07MB5978
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/xN0SiGigsFI50fMt-RX28tM0gkA>
Subject: Re: [Teas] FW: New Version Notification for draft-lee-teas-actn-pm-telemetry-autonomics-12.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2019 16:38:10 -0000

Young

I am less confused:-)

The Copyright statements are incomplete; look, for example, at RFC8294
and you lack the final sentence which provides the required link back to
the RFC to be, one of the missing references I referred to earlier.

Recall that the YANG modules will be extracted and widely used with
nothing else to support them, so from 'CODE BEGINS' to 'CODE ENDS' must
be comprehensible standing alone.  Again, look at RFC8294 and you will
see reference clauses in the description, which I think are needed in
each and every YANG module and one per object is not too many.

Thus, within the IETF, IPPM have done much on one-way and two-way delay;
do you mean the same as they do? If not, where do your definitions
thereof come from?  ITU-T (who are also hot on this)?

This makes me note that there are no default values nor guidance as to
what to use; again, references here help, if only to the RFC to be.
Human nature suggests the people will use whatever they can see so that
following s.4 we could see a lot of

Threshold-time: 3600 (sec)
Cooldown-time:  60 (sec)
threshold-value: 300 mile-seconds [milli?]
threshold-value: 300 megabytes

which may, or may not, be suitable values.

Related to this, common practice is to put examples in an Appendix, the
idea being that examples are not Normative and Appendices are not
Normative, whereas the body of the document is, which examples are not.
Examples in the body may be blindly followed.

HTH

Tom Petch


----- Original Message -----
From: "Leeyoung" <leeyoung@huawei.com>
To: "tom petch" <ietfa@btconnect.com>om>; "TEAS WG Chairs"
<teas-chairs@ietf.org>
Cc: "TEAS WG" <teas@ietf.org>
Sent: Wednesday, April 10, 2019 6:06 PM

> Hi Tom,
>
> Thanks. I think there is still some inconsistency as you pointed out.
Please see inline. This should be it. I uploaded v.14 that incorporated
all your comments. Attached is the new version notification and the
below is the pointer for the diff.
>
>
https://www6.ietf.org/rfcdiff/?url2=draft-lee-teas-actn-pm-telemetry-aut
onomics-14
>
> Please let me know if any further fix is needed.
>
> Best regards,
>
> Young
> -----Original Message-----
>
> From: tom petch [mailto:ietfa@btconnect.com]
> Sent: Wednesday, April 10, 2019 11:37 AM
>
> To: Leeyoung <leeyoung@huawei.com>om>; TEAS WG Chairs
<teas-chairs@ietf.org>
>
> Cc: TEAS WG <teas@ietf.org>
>
> Young (!)
>
> I remain confused.  What I see is
>
> s.1.3
>
>
>
>       | te-kpi  | ietf-te-kpi-telemetry        | [This I-D]      |
>
>       | vn-tel  | ietf-vn-kpi-telemetry        | [This I-D]      |
>
>
>
> YL>> te-kpi should be te-tel
>
>
>
> YANG Modules
>
>
>
>   namespace "urn:ietf:params:xml:ns:yang:ietf-te-kpi-telemetry";
>
>   prefix te-tel;
>
>
>
>   namespace "urn:ietf:params:xml:ns:yang:ietf-vn-kpi-telemetry";
>
>   prefix vn-tel;
>
>
>
> YL>> This is now consistent with s.1.3
>
>
>
>
>
> IANA Considerations
>
>
>
>    URI: urn:ietf:params:xml:ns:yang:ietf-te-kpi-telemetry
>
>    URI: urn:ietf:params:xml:ns:yang:ietf-kpi-telemetry
>
>
>
> YL>> ietf-kpi-temetry should be ietf-vn-kpi-telemetry.
>
>
>
>    namespace:    urn:ietf:params:xml:ns:yang:ietf-te-kpi-telemetry
>
>    namespace:    urn:ietf:params:xml:ns:yang:ietf-vn-kpi-telemetry
>
>
>
> Too many prefix, too many URI.
>
>
>
> And IANA Considerations - which is authoritative so I tend to look at
first - must specify prefix but it does not
>
>
>
> YL>> Added: prefix: te-tel and prefix:vn-tel
>
>    -------------------------------------------------------------------
-
>
>    name:         ietf-te-kpi-telemetry
>
>    namespace:    urn:ietf:params:xml:ns:yang:ietf-te-kpi-telemetry
>
>    prefix:       te-tel
>
>    reference:    RFC XXXX (TDB)
>
>    -------------------------------------------------------------------
-
>
>
>
>    -------------------------------------------------------------------
-
>
>    name:         ietf-vn-kpi-telemetry
>
>    namespace:    urn:ietf:params:xml:ns:yang:ietf-vn-kpi-telemetry
>
>    prefix:       vn-tel
>
>    reference:    RFC XXXX (TDB)
>
>    -------------------------------------------------------------------
-
>
>
>
> Tom Petch
>
>
>
> ----- Original Message -----
>
> From: "Leeyoung" <leeyoung@huawei.com>
>
> To: "tom petch" <ietfa@btconnect.com>om>; "TEAS WG Chairs"
>
> <teas-chairs@ietf.org>
>
> Cc: "TEAS WG" <teas@ietf.org>
>
> Sent: Tuesday, April 09, 2019 6:21 PM
>
>
>
> > Hi Tom,
>
> >
>
> >
>
> >
>
> > Thanks for your interest in this draft and a good review for it. I
>
> really appreciate that. I think most of your comments are valid;
please see inline for my response.
>
> >
>
> > Please see the diff file:
>
>
https://www6.ietf.org/rfcdiff/?url2=draft-lee-teas-actn-pm-telemetry-aut
>
> onomics-13  and let us know if there are still missing items.
>
> >
>
> >
>
> >
>
> > Thanks & Best regards,
>
> >
>
> > Young
>
> >
>
> >
>
> >
>
> > -----Original Message-----
>
> >
>
> > From: tom petch [mailto:ietfa@btconnect.com]
>
> >
>
> > Sent: Friday, April 5, 2019 11:51 AM
>
> >
>
> > To: Leeyoung <leeyoung@huawei.com>om>; TEAS WG Chairs
>
> <teas-chairs@ietf.org>
>
> >
>
> > Cc: TEAS WG <teas@ietf.org>
>
> >
>
> > Subject: Re: [Teas] FW: New Version Notification for
>
> draft-lee-teas-actn-pm-telemetry-autonomics-12.txt
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > ----- Original Message -----
>
> >
>
> > From: "Leeyoung" <leeyoung@huawei.com>
>
> >
>
> > Sent: Tuesday, April 02, 2019 10:56 PM
>
> >
>
> >
>
> >
>
> > > Hi Lou and Pavan,
>
> >
>
> > >
>
> >
>
> > > Following up the discussion from IETF 104 TEAS WG meeting, please
>
> find
>
> >
>
> > the updated version of
draft-lee-teas-actn-pm-telemetry-autonomics-12.
>
> >
>
> > (See the attachment diff file).
>
> >
>
> > >
>
> >
>
> > > To recap:
>
> >
>
> > >
>
> >
>
> > > - The draft is "generalized" to be applicable in generic settings.
>
> >
>
> > (See Abstract/Introduction)
>
> >
>
> > > - Changes of modules: from ietf-actn-te-kpi-telemetry model to
>
> >
>
> > ietf-vn-kpi-telemetry model.
>
> >
>
> > > - Section 4 has been added (v.11) to explain what scaling in/out
>
> >
>
> > mechanism is with illustration and a partial YANG tree.
>
> >
>
> > >
>
> >
>
> > > We believe all pending issues/comments have been incorporated in
v12
>
> >
>
> > and as such the draft is a good basis for WG adoption. Please let me
>
> know if you have any further comments.
>
> >
>
> >
>
> >
>
> > Lee
>
> >
>
> >
>
> >
>
> > I am confused.  I am looking at
>
> >
>
> >   draft-lee-teas-actn-pm-telemetry-autonomics-12
>
> >
>
> >
>
> >
>
> > In IANA Considerations you have
>
> >
>
> >     URI: urn:ietf:params:xml:ns:yang:ietf-kpi-telemetry
>
> >
>
> > when the namespace is
>
> >
>
> >    "urn:ietf:params:xml:ns:yang:ietf-vn-kpi-telemetry";
>
> >
>
> > and the prefix, which must be specified, is missing
>
> >
>
> >
>
> >
>
> > In the list of prefix I see
>
> >
>
> >
>
> >
>
> >       | te-kpi  | ietf-te-kpi-telemetry        | [This I-D]      |
>
> >
>
> >       | vn-tel  | ietf-vn-kpi-telemetry        | [This I-D]      |
>
> >
>
> >
>
> >
>
> > YL>> Thanks for the catch. I Corrected:
>
> >
>
> >
>
> >
>
> > OLD: URI: urn:ietf:params:xml:ns:yang:ietf-kpi-telemetry
>
> >
>
> > NEW: URI: urn:ietf:params:xml:ns:yang:ietf-vn-kpi-telemetry
>
> >
>
> >
>
> >
>
> > 7.1 has
>
> >
>
> >   namespace "urn:ietf:params:xml:ns:yang:ietf-te-kpi-telemetry";
>
> >
>
> > prefix te-tel;
>
> >
>
> >
>
> >
>
> > 7.2 has
>
> >
>
> >   namespace "urn:ietf:params:xml:ns:yang:ietf-vn-kpi-telemetry";
>
> >
>
> >   prefix actn-tel;
>
> >
>
> >
>
> >
>
> > [perm any of 'actn' 'vn' 'te' 'kpi' 'tel' at random!]
>
> >
>
> >
>
> >
>
> > YL>> actn -> vn; ‘te’ is te-tunnel so it is clear; kpi is key
>
> performance index, so it is clear. I would change actn-tel to vn-tel
to be consistent with te-tel.
>
> >
>
> >
>
> >
>
> > I do wonder about the choice of prefix. It seems to me that it is
>
> about KPI for VN and TE in which case, kpi-th- and kpi-vn seem
clearer.
>
> I have yet to see the minutes of the meeting so am not familiar with
the discussion
>
> >
>
> >
>
> >
>
> > YL>> I think te and vn are the base model to which these kpi modules
>
> are extended; thus, I think we would stick to  ietf-te-kpi-telemetry
and ietf-vn-kpi-telemetry.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Also,
>
> >
>
> >
>
> >
>
> > There are a lot of lines that are too long for an RFC
>
> >
>
> >
>
> >
>
> > The YANG Modules lack version statement
>
> >
>
> >
>
> >
>
> > YL>> Added version 1.1
>
> >
>
> >
>
> >
>
> > The YANG modules lack Copyright statement
>
> >
>
> >
>
> >
>
> > YL>> added.
>
> >
>
> >
>
> >
>
> > The YANG module lack reference statements
>
> >
>
> >
>
> >
>
> > YL>> There is no real external reference in this module.
>
> >
>
> >
>
> >
>
> > The import statements lack reference clause
>
> >
>
> >
>
> >
>
> > YL>> Added.
>
> >
>
> >
>
> >
>
> > There is no reference back from the YANG module to the I-D/RFC to
tell
>
> users where it came from where to find out more.
>
> >
>
> >
>
> >
>
> > YL>> Since there is no real reference in the YANG module, there is
no
>
> case for this.
>
> >
>
> >
>
> >
>
> > Several of the Informative References look Normative e.g.
>
> >
>
> > RFC6020 RFC7950 RFC8341RFC8309 RFC8233 RFC7926etc etc
>
> >
>
> >
>
> >
>
> > YL>> Agreed and moved these to Normative except 8233 as it is
already
>
> in the Normative.
>
> >
>
> >
>
> >
>
> > The Security Considerations are out of date lacking RESTCONF, TLS,
>
> HTTPS
>
> >
>
> >
>
> >
>
> > YL>> Added. Please see the section.
>
> >
>
> >
>
> >
>
> > I suggest expanding VN in the Introduction; you do it in the
Abstract
>
> and that is good but I, and some like me, skip straight to the
Introduction.
>
> >
>
> >
>
> >
>
> > YL>> Done.
>
> >
>
> >
>
> >
>
> > Further on, I think that you need to expand SLA, BER - not sure
about
>
> CAPEX/OPEX
>
> >
>
> >
>
> >
>
> > YL>> Will do that in the next revision.
>
> >
>
> >
>
> >
>
> > Tom Petch
>
> >
>
> >
>
> >
>
> > p.s. if in doubt, blame your fellow authors:-)
>
> >
>
> >
>
> >
>
> > > Thanks.
>
> >
>
> > > Young (on behalf of other co-authors and contributors)
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > -----Original Message-----
>
> >
>
> > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>
> >
>
> > > Sent: Tuesday, April 2, 2019 4:43 PM
>
> >
>
> > > To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>om>; Satish
>
> >
>
> > Karunanithi <satish.karunanithi@gmail.com>om>; Leeyoung
>
> <leeyoung@huawei.com>om>; Dhruv Dhody <dhruv.dhody@huawei.com>om>; Daniel
King <d.king@lancaster.ac.uk>uk>; Ricard Vilata <ricard.vilalta@cttc.es>es>;
Ricard Vilalta <ricard.vilalta@cttc.es>
>
> >
>
> > > Subject: New Version Notification for
>
> >
>
> > draft-lee-teas-actn-pm-telemetry-autonomics-12.txt
>