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

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 15 July 2020 10:31 UTC

Return-Path: <dhruv.ietf@gmail.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 77D893A09B7; Wed, 15 Jul 2020 03:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 kS3fjwjE7ZeL; Wed, 15 Jul 2020 03:31:46 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 986AE3A09AD; Wed, 15 Jul 2020 03:31:46 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id f23so1664782iof.6; Wed, 15 Jul 2020 03:31:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=oaihU4Sm+fDruFMfUCJWAdKbk/NJ5/4Eao+VGOtuRIU=; b=PCY2/4pIac1f7JYqC/hsy9M0XZrUzJhgbjxN27rA+z2mx1oow2SA/B36UmDZkn1H3M hp7I4GQoVFmGaCH/XJWis3zujcnOsxNuUS40tv2nls/UpUTAZ3U4Ch1/BCxp8KoanZpf Hnc265+GYzL3xkwwI73WZxf1pBCWvGoTnrjHCrksbevWRQogrWQ3OtOZkbg37y7vHXTC J4k8Dy/iA+RLlaUiP4WvnjsWgbJC19Y7s5/Is8K+FB9asMIIzNjLD9T2CFRm0m/34dCi d5L5XoaVGULJwKKCrKSb8y/DAjNioBQsdNwOh1HVWFdPdPh5TVHQzOOJRN5unAoPOfe6 ocGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=oaihU4Sm+fDruFMfUCJWAdKbk/NJ5/4Eao+VGOtuRIU=; b=ie8lqJZLuzTSjsdo5xzz7CVrRpa+J3I/lHmuULyA3G+e9ezselvTwEsHKQ2UFrQxxg 7RrZX5nOCzsyyIEZuyjSOPYlp+BlNwhtNBYHdQyjAL+1OpsBR2FBxH7JDVgvJfS1tS0+ +sX65r/ZyNQbPfxMBVGEEIbikMzy/EnH1BiQ+KIMo8LANuEjyQ7FiLrpJczEwl5UHOjY 57tAKh5IU4lpPwEQ0mBmeyT9ouW5VM4/qpLgUjqLd2JXj57f2zFO7msAI9MxUMPuqeLJ jv3HZMQTnRMl3dplxl0VaV8ZvM0BNX7CQuvpsofjW5FzP/hCiHJdwK7jLEqO/FI8PrPe AG6g==
X-Gm-Message-State: AOAM531/Wvlz+AqiqDwQq/ZAxuOxjEQO7JhQgTU0b3qikhfGwuTb5hD1 g7/CHZWocfu0hWgX/j/c7ek5Gus09zUfzaxWE5E=
X-Google-Smtp-Source: ABdhPJypEsdLH2HkfdLNQ/XQmBrBbvoELQLomHdIWvbO8q+Hc9zubSta1ZaydHi6WO6B4lO5dtg8R1wnTPlkNI4DfLc=
X-Received: by 2002:a05:6638:14c1:: with SMTP id l1mr10630536jak.108.1594809105690; Wed, 15 Jul 2020 03:31:45 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn78kAB3e2q+MNLtdskV9dmuBYP4iUhsHMJ_gQCq0AOXYA@mail.gmail.com> <DB7PR07MB5340595C88AD8395C582E9AEA2D00@DB7PR07MB5340.eurprd07.prod.outlook.com> <CAB75xn7tieFKUW87CCHa7+_V1GxRFSC3qrxg77ri5fLHxxbskA@mail.gmail.com> <DB7PR07MB5340CDA532D6CEE72CE90814A27E0@DB7PR07MB5340.eurprd07.prod.outlook.com>
In-Reply-To: <DB7PR07MB5340CDA532D6CEE72CE90814A27E0@DB7PR07MB5340.eurprd07.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 15 Jul 2020 16:01:09 +0530
Message-ID: <CAB75xn52cYdvZCmkkQKzuPJ0uLDx0kL9ndrdp6Q2A9-vccQyDw@mail.gmail.com>
To: tom petch <ietfa@btconnect.com>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/_6NAZxbKZGQI6GBUUTsqOX8GvJw>
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:31:49 -0000

Hi Tom,

Thanks for keeping us on our toes :)
I will consider these in the next update.

Regarding uri, I was influenced by RFC 8345 and thought it made sense
here as well (with my reading being the datastore to be related to
NMDA). I will get that confirmed.

Thanks!
Dhruv


On Wed, Jul 15, 2020 at 3:32 PM tom petch <ietfa@btconnect.com> wrote:
>
> 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