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

Dhruv Dhody <dhruv.ietf@gmail.com> Mon, 13 July 2020 18:54 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 4714E3A172A; Mon, 13 Jul 2020 11:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=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 SlllwJqW7lXj; Mon, 13 Jul 2020 11:54:24 -0700 (PDT)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 932CD3A1743; Mon, 13 Jul 2020 11:54:24 -0700 (PDT)
Received: by mail-il1-x12a.google.com with SMTP id x9so12130719ila.3; Mon, 13 Jul 2020 11:54:24 -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; bh=dW2AW2ooXytOgRUNThYri1Q9zxxRtD3uS+XeineHgj0=; b=OlR9ZA1fjW0skzNvt/9wHVr4abD9Q7AiK4mVP0bgP5IcNm/mF4tSSh+cU4/Z5ix3gj zWq68ZBcY8B1oybRpxxPszU+DNVf31E0DwLs6HwO6BML4KAQQhqk9RY3xx7tHcZX1G3h i7p2Hq/YwKiTNKfFALb4+vQRoF6D+PXjXq3nlk6ynpaP+RrEELTYheV3SIFNUfqHtpwH SxzpY551xx0NpQxeN73vgQczBQyA+Ry+jnMYwuw8OrEyl85L6sfBm5Ndw/wub7qUmXAN UMiSV03UdbA62u2/RNz6ezmLElkkFH5C6IsaKJVqu68/ZVP8MgNKyKMJtkBaJ+b/9300 g8dw==
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; bh=dW2AW2ooXytOgRUNThYri1Q9zxxRtD3uS+XeineHgj0=; b=GcZYbggb/3KNy24xcZtZQbQ/aNfHuSCyYImejfU66g8sBuBDW/vUYKar7Hdd0fkfQ7 OPYIgSpkk+F10OHavMS3NaM/HtsxJuGzqxTxkXhalB6Cuo9zfSVzy3umIIQT29wWS+bR s4HPm+M6WjyPEa1bZVmGp+UZj8g9XeMWxacz/WfC2cuwG9Et8VB8H3/n5wIupkdGVW3H gGJAdf/nukIqgOcjPFZtdSjWEzlDNoWQl30JYbk4wpTj0ZoTQUjV+yGw1zT8WSzjJNMG vz/BFMXfH2CHf2jbQQvJdChL/X9WRM3QrWrC4UM1nL+akiGMcDwKRf/WbFVZTj6JIqrc kbbg==
X-Gm-Message-State: AOAM531QEIy3I7v99uzz57sNYGkXAa7X5GJLmHGk342njXeYHbUMKHo8 QR6isGtbFsi9XEvG2ORK3dn+Fv/GQInpCirTNBM=
X-Google-Smtp-Source: ABdhPJwWQoktgVVkwdjSezhUFH8+K5reHZMCjZdxBA7EPpvAMFklx8JBAZ0rOam24Crs5YLeSK/D5uW8cwjxyfl7H48=
X-Received: by 2002:a92:300a:: with SMTP id x10mr1116407ile.124.1594666462759; Mon, 13 Jul 2020 11:54:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn78kAB3e2q+MNLtdskV9dmuBYP4iUhsHMJ_gQCq0AOXYA@mail.gmail.com> <DB7PR07MB5340595C88AD8395C582E9AEA2D00@DB7PR07MB5340.eurprd07.prod.outlook.com>
In-Reply-To: <DB7PR07MB5340595C88AD8395C582E9AEA2D00@DB7PR07MB5340.eurprd07.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 14 Jul 2020 00:23:46 +0530
Message-ID: <CAB75xn7tieFKUW87CCHa7+_V1GxRFSC3qrxg77ri5fLHxxbskA@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: multipart/alternative; boundary="0000000000000c701905aa5738c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/maJua2IRSbRfq6iNVpY5gYJ5A-o>
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: Mon, 13 Jul 2020 18:54:26 -0000

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/

Thanks!
Dhruv

On Fri, Apr 24, 2020 at 4:03 PM tom petch <ietfa@btconnect.com> wrote:

> From: Teas <teas-bounces@ietf.org> on behalf of Dhruv Dhody <
> dhruv.ietf@gmail.com>
> Sent: 22 April 2020 07:37
> To: TEAS WG Chairs; TEAS WG (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
> https://www.ietf.org/mailman/listinfo/teas
>