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

tom petch <ietfa@btconnect.com> Wed, 10 April 2019 16:37 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 DDECB12037D; Wed, 10 Apr 2019 09:37:25 -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 73S_18PWqAui; Wed, 10 Apr 2019 09:37:23 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40104.outbound.protection.outlook.com [40.107.4.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD1391203FA; Wed, 10 Apr 2019 09:37:21 -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=mVSPT7uuSJTfMrnSRg5WXdGC7/oLP76u9iWSbsPJn0E=; b=K39EKfkv92+xY34Sjz6x4sU0smmDCAmWrbczjplTfWu6y46C5PunkL3YHFGP2CvTcLxCxO5YeJwujVcjfrJzHQw8iHuJ7cvM+iMOGU4w+bYA67lAfIf/Ac9aojHdzfDqMrjCsj3zLuDF/X1wsX96xblfQ5egkJJpAf/qQjrHPZk=
Received: from VI1PR07MB4480.eurprd07.prod.outlook.com (20.177.57.76) by VI1PR07MB4813.eurprd07.prod.outlook.com (20.178.8.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.7; Wed, 10 Apr 2019 16:37:19 +0000
Received: from VI1PR07MB4480.eurprd07.prod.outlook.com ([fe80::e171:25b9:50b7:f8d3]) by VI1PR07MB4480.eurprd07.prod.outlook.com ([fe80::e171:25b9:50b7:f8d3%2]) with mapi id 15.20.1792.007; Wed, 10 Apr 2019 16:37:19 +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: Wed, 10 Apr 2019 16:37:18 +0000
Message-ID: <011b01d4efbb$4060de40$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>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0228.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:b::24) To VI1PR07MB4480.eurprd07.prod.outlook.com (2603:10a6:803:75::12)
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: d828f21f-73a2-4bec-28ee-08d6bdd2cc34
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB4813;
x-ms-traffictypediagnostic: VI1PR07MB4813:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <VI1PR07MB4813EE52DF531837C1802EC9A22E0@VI1PR07MB4813.eurprd07.prod.outlook.com>
x-forefront-prvs: 00032065B2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(376002)(136003)(366004)(346002)(396003)(51914003)(189003)(199004)(13464003)(51444003)(68736007)(4720700003)(62236002)(71200400001)(44716002)(81686011)(99286004)(1556002)(316002)(229853002)(76176011)(52116002)(6116002)(6436002)(6486002)(81816011)(8936002)(93886005)(86362001)(86152003)(53936002)(6246003)(3846002)(106356001)(305945005)(44736005)(105586002)(81156014)(9686003)(7736002)(6512007)(81166006)(50226002)(8676002)(6306002)(61296003)(4326008)(6506007)(71190400001)(53546011)(26005)(110136005)(5660300002)(102836004)(966005)(25786009)(478600001)(186003)(446003)(486006)(476003)(84392002)(14454004)(386003)(66574012)(15650500001)(66066001)(2906002)(14496001)(97736004)(256004)(14444005)(5024004)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4813; H:VI1PR07MB4480.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: /E/qlJWGfBZmBO0LqLci4wXoWZTPbHe5PPIUY6XRYZIoGdfBzWxAhEY7Bx0ao0xAY/3ewKN7gwU3q8wofKs/Rzg6LZvSkW9Qf9nfmLDovdhWRyY/9X3Dd/PcpqSCOGwLIIKo2yWBpuY2fuo7sWavxsUzc5MrdJe/B4+TBJVPotP7Tojr1VZpMi/4CNhyB2vRNZK+zXhsjFTZqtOkD0Bkt0ADBMsnm6+BlR+aDQPAfMipBjpNPG9Eg7G4N5VP85iPq0f/P98IOY6CxWzYtpe3jdU104sGkhGxGgZODYjntzgDBJ8WubtQn2qdsXVpyMewnKQykkxYSzkZ43xjXW672XK5kTyEgJc8nPpHcNZBJ0qGC8keOuH1D57ZhQGqbY8P4yZv2FQhF99PTobDBYZ0t2GY2Jqo3bfojWjRVEUFqjE=
Content-Type: text/plain; charset="utf-8"
Content-ID: <A234B9B53D947D49A376CDB3CBA87C7F@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d828f21f-73a2-4bec-28ee-08d6bdd2cc34
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Apr 2019 16:37:19.0569 (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: VI1PR07MB4813
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/flPOJmqG-xrtbW8s_7Q1QF47-po>
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: Wed, 10 Apr 2019 16:37:26 -0000

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]      |

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;

IANA Considerations

   URI: urn:ietf:params:xml:ns:yang:ietf-te-kpi-telemetry
   URI: urn:ietf:params:xml:ns:yang:ietf-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

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
>
> >
>
> >
>
> > A new version of I-D,
>
> draft-lee-teas-actn-pm-telemetry-autonomics-12.txt
>
> > has been successfully submitted by Young Lee and posted to the IETF
>
> repository.
>
> >
>
> > Name: draft-lee-teas-actn-pm-telemetry-autonomics
>
> > Revision: 12
>
> > Title: YANG models for VN & TE Performance Monitoring Telemetry and
>
> Scaling Intent Autonomics
>
> > Document date: 2019-04-02
>
> > Group: Individual Submission
>
> > Pages: 25
>
> > URL:
>
>
https://www.ietf.org/internet-drafts/draft-lee-teas-actn-pm-telemetry-au
>
> tonomics-12.txt
>
> > Status:
>
>
https://datatracker.ietf.org/doc/draft-lee-teas-actn-pm-telemetry-autono
>
> mics/
>
> > Htmlized:
>
>
https://tools.ietf.org/html/draft-lee-teas-actn-pm-telemetry-autonomics-
>
> 12
>
> > Htmlized:
>
>
https://datatracker.ietf.org/doc/html/draft-lee-teas-actn-pm-telemetry-a
>
> utonomics
>
> > Diff:
>
>
https://www.ietf.org/rfcdiff?url2=draft-lee-teas-actn-pm-telemetry-auton
>
> omics-12
>
> >
>
> > Abstract:
>
> >    This document provides YANG data models that describe performance
>
> >    monitoring telemetry and scaling intent mechanism for TE-tunnels
>
> and
>
> >    Virtual Networks (VN).
>
> >
>
> >    The models presented in this draft allow customers to subscribe
and
>
> >    monitor their key performance data of their interest on the level
>
> of
>
> >    TE-tunnel or VN. The models also provide customers with the
ability
>
> >    to program autonomic scaling intent mechanism on the level of TE-
>
> >    tunnel as well as VN.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > 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
>
> >
>
> >
>
>
>
>
>
> ----------------------------------------------------------------------
--
>
> --------
>
>
>
>
>
> > _______________________________________________
>
> > Teas mailing list
>
> > Teas@ietf.org
>
> > https://www.ietf.org/mailman/listinfo/teas
>
> >
>
>
>
>


------------------------------------------------------------------------
--------


> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>