Re: [Teas] WG I-D Status actn-vm

tom petch <ietfa@btconnect.com> Wed, 15 July 2020 10:02 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 1E6FB3A08A9; Wed, 15 Jul 2020 03:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 oI2GHW5n8Hdo; Wed, 15 Jul 2020 03:02:12 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2120.outbound.protection.outlook.com [40.107.20.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91F713A08AC; Wed, 15 Jul 2020 03:02:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EnWqo4WDhxGoQAyFrorMFb6aGkoiA8+Dv83bpNZ8ULMXDkDy+Ch56CfEv1Xg8mHz5NhRvqic1tR3iMuMjga1aoW/CvStBN5/2+j4cpCW4dVXzHlDE/T3GZGunZAYoJRpiWNcHw8buZul5sOPHGc7DO80DIWH6BX4sXynp1kSAmxuOhdZ1f4frWJMPhMwq0Gol3v+IIP2Qew+V/3nhCBK/3UlkKqaPeIT8N5Ck+3tmQthzpnOqPyYnnjEyW2XFWqI10SzoN7LxfsabDTuOtNPO1zgKVbboxIFb+E8laxsnPgMzq9yIrCWt9A+HKwv7Df2fPLIokfb2THjd+NFVd1khA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dFL7he3oZ6ORE1NFtedDvUechhe0yk3zphY8yCV6c6k=; b=UsRk7cVHpdljvZW/9IV2gGchwpHQKfFh0ICUnzCeYKkTeuKmY6b6k4v+2jJorCBCNwqYkN/Ck1FNQlZAmPzpbqnZkyGvb/g4YjJtGcumybyNpMsAvLYxm44PKJ8k+9pRANEbFawMxvLSCPjqp0Z8obA3zZKY/UihcMLamQOp/LJ8jG/wT/vfKlDu52Fphvcx7VZIKKmzu7YuoMEXg5hcEeKhGBUbYbIs+sCKFTJAU9NogkaN49EMRptVdNt0e+/YMik/bH0GdDtoZ/8IK7JhcDY/pecRbx9qg4LeH3Q/Kt3MW64Cp5Ctfot/1FytDdTDIlkZKejn38J0fzBBQ7Ksjg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dFL7he3oZ6ORE1NFtedDvUechhe0yk3zphY8yCV6c6k=; b=abnlUJvT8/cETag7xvw5f/myYPq8x4acqkCV/2R2E6oE0gPrNG+XLEMP6Zzi1oNcYWUsH7Ddb/M5cyGdO1GQDCkPglJDV46twtL1/k20SDVofOWANtx7GY/4QU/1mGz8QkQUJEI/hRn7DbsKR1i5DKvdUNrkX/YLAUixAhFhScI=
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com (2603:10a6:10:69::25) by DB6PR0701MB2472.eurprd07.prod.outlook.com (2603:10a6:4:5a::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3195.9; Wed, 15 Jul 2020 10:02:09 +0000
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::f911:a06:2f4e:a103]) by DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::f911:a06:2f4e:a103%4]) with mapi id 15.20.3195.009; Wed, 15 Jul 2020 10:02:08 +0000
From: tom petch <ietfa@btconnect.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
CC: TEAS WG Chairs <teas-chairs@ietf.org>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>
Thread-Topic: [Teas] WG I-D Status actn-vm
Thread-Index: AQHWWUcHfAKUQwDcXE2dtlUuZ+wl4KkIZD1j
Date: Wed, 15 Jul 2020 10:02:08 +0000
Message-ID: <DB7PR07MB5340CDA532D6CEE72CE90814A27E0@DB7PR07MB5340.eurprd07.prod.outlook.com>
References: <CAB75xn78kAB3e2q+MNLtdskV9dmuBYP4iUhsHMJ_gQCq0AOXYA@mail.gmail.com> <DB7PR07MB5340595C88AD8395C582E9AEA2D00@DB7PR07MB5340.eurprd07.prod.outlook.com>, <CAB75xn7tieFKUW87CCHa7+_V1GxRFSC3qrxg77ri5fLHxxbskA@mail.gmail.com>
In-Reply-To: <CAB75xn7tieFKUW87CCHa7+_V1GxRFSC3qrxg77ri5fLHxxbskA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [81.131.229.35]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6988a6d8-dd9f-472c-aa4a-08d828a62302
x-ms-traffictypediagnostic: DB6PR0701MB2472:
x-microsoft-antispam-prvs: <DB6PR0701MB2472DDFB86B2831C5B5092AFA27E0@DB6PR0701MB2472.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: gDxKvh3qJ2uIWB7lejK8oBBg8nRqFtO6hqUD6Xkn1dNj1vUxF7e5zVquuFMIwzpXUbHX7ARS8wxcKHRQlUnfhitPWy/3dwcAHSg8UBkk4xactVuhgUMAJeaAvOuHPKsP67I27gNbp6UvEWi5A4Ltjpiw3QzR7KHMCQMQy+d/mETuqlkxmSvkp9TIXot0vEuZiIWeMJWZDyYeGc1IcNlxok59tUoUxG3HTrvpaUpkg0bGU0Zww0uh3RiNymMFi+G2uQw3Qbv4HNrX2vHWD3mjbO8Pqj+drQN12sjsN524z90zWuUPHTgGgGEG/zoRE2XsNBUzz5U71VERa5a5ysGNT+bogIXTV9yLr05eMetFxP/EOz2tphHNdCBky5mTGUldFp1BKwEZytSeHwxH3ojG7w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB5340.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(396003)(136003)(366004)(376002)(346002)(39860400002)(7696005)(53546011)(6916009)(91956017)(76116006)(66476007)(5660300002)(4326008)(86362001)(2906002)(8936002)(66946007)(83380400001)(8676002)(478600001)(71200400001)(9686003)(966005)(55016002)(54906003)(6506007)(316002)(52536014)(186003)(33656002)(66556008)(66446008)(26005)(64756008); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: bz4OPyKABSok1pcbpewKbDCngeGEdUeWzLt/Up22yiX7f/4MFZd28IhJniv0EIBgf6LyU/pL4HolCZyAmnIsrIugGF3fM1g49I7amBKF0RFN9s4nWVwXTi99ZzgDWvrZe6LE562sjxtlIGNkX86GZ5IE8jLESG1plgxCE6WIFi8ASDu/LOtjdT+9DR8+E8S6gB+yssSSxze3tKjjctlyYzP5ORGdc0A07Lvc7a8CYQrtjJpKzKx0JUFWGW5TLdg6m+Jq1JVaVYhjA1BkstFIO3QJtdo3GEDtqSjmLC2F4BItjZ2EuGn0RZbbzHqgC++b2jrFVw2uWjbUKl41hbuvQ0o6fOx54aLd3lMq/NF0QQDpbm7GOlViQ09Zztz3DpC5gMIQ9G5OOcuesX8KMzF/OcGKfGJ5rQYIbI6m0hTFyIzlsm63YugJkvNakZfuku3/nSXS85treHFeLOMEbUtqqqzzm661GaIPDM+1Ca1avwI=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB7PR07MB5340.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6988a6d8-dd9f-472c-aa4a-08d828a62302
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2020 10:02:08.8235 (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-CrossTenant-userprincipalname: /fpgM6RKtpooYEXAsjC/zSdJl/o+RIMC4vtfFGlpzOgWCGBLfrtP4SaVxttC+lJJmgSen8g9kR4tmec/M2lwNA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2472
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/hP_mkPDaDfzVE5JO78jG8qYxk8s>
Subject: Re: [Teas] WG I-D Status actn-vm
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, 15 Jul 2020 10:02:14 -0000

From: Dhruv Dhody <dhruv.ietf@gmail.com>
Sent: 13 July 2020 19:53
Hi Tom,

Apologies for the late reply. I have made an update and handled all your pending comments! Please have a look - https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/

<tp>
Getting there.  I had not realised how much this leant on te-topo but now I am more familiar with the latter I find myself in less need of references but suspect that others will find them useful.  I note that there is a -24 for yang-te - I do not know what has changed.

A general comment.  A much used and useful convention is that a list is plural and content singular so rather than 
list vn-ap
uses vn-ap
you could have 
list vn-aps
uses vn-ap
or 
container aps
list ap
container vns
list vn
I realise that other teas I-D use the suffix -list but for me that is clumsier than a simple 's'

s.1.3 has the wrong prefix for te-topo

I find the use of uri for ids interesting; any scheme? any length?  probably worth some advice here given people's predilection for disastrous identifiers:-)
And do you mean datastores, or modules?  I struggle to see how the uri could differ  across datastores.

LTP should be expanded in the YANG even if I do now recognise it.  It has a different meaning in other technologies.

IANA /TDB/TBD/ !

Tom Petch
Thanks!
Dhruv

On Fri, Apr 24, 2020 at 4:03 PM tom petch <ietfa@btconnect.com<mailto:ietfa@btconnect.com>> wrote:
From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> on behalf of Dhruv Dhody <dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>>
Sent: 22 April 2020 07:37
To: TEAS WG Chairs; TEAS WG (teas@ietf.org<mailto:teas@ietf.org>)
Subject: [Teas] WG I-D Status

Hi Chairs, WG,

Please find the status -

==

A Yang Data Model for VN Operation (draft-ietf-teas-actn-vn-yang-08)
Updates:
  Mainly YANG guidelines update
  All earlier issues resolved

<tp>
Looking at -08 I struggle to see a resolution of some of the issues I raised 3Jul2019.

YANG deserves a reference in Introduction


Done!


YANG should be upper case, not yang


Done!


1,3 places te-types in teas-yang-te
The module imports it from teas-yang-te-types


Updated to the RFC 8776


identity  .. computatione-failed


Fixed


disjoint I cannot find in RFC8453 - a reference would be helpful


I use the te-types typedef instead of defining a new one!


ltp likewise


Added


vn-id seems underspecified.  Has it semantics or is it just a number?  Are there restrictions on the range?  Many I-D create a raft of YANG types
which seem to complicate the model - here I wonder if a vn-id  type would help.


Added typedef.

Tom Petch


Next Steps:
  Yang Doctors Review

==

YANG models for VN/TE Performance Monitoring Telemetry and Scaling
Intent Autonomics (draft-ietf-teas-actn-pm-telemetry-autonomics-02)
Updates:
  Mainly YANG guidelines update
Next Step:
  Solicit more reviews

==

Traffic Engineering (TE) and Service Mapping Yang Model
(draft-ietf-teas-te-service-mapping-yang-03)
Updates:
  Mapping to Network Yang Models added (L3NM and L2NM)
  YANG guidelines update
Question to the WG:
  Is this the right place to include mapping to the network model as well?

==

Thanks!
Dhruv

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