Re: [Teas] I-D Action: draft-ietf-teas-te-service-mapping-yang-06.txt

Dhruv Dhody <dhruv.ietf@gmail.com> Mon, 22 February 2021 05:58 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 F044B3A0ACB for <teas@ietfa.amsl.com>; Sun, 21 Feb 2021 21:58:36 -0800 (PST)
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 5i3_stvXoLHW for <teas@ietfa.amsl.com>; Sun, 21 Feb 2021 21:58:34 -0800 (PST)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 876543A0AD1 for <teas@ietf.org>; Sun, 21 Feb 2021 21:58:34 -0800 (PST)
Received: by mail-io1-xd2e.google.com with SMTP id q77so12057641iod.2 for <teas@ietf.org>; Sun, 21 Feb 2021 21:58:34 -0800 (PST)
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=QW0LJzjtQwgN0Gu1SvlxWG8+S0qzlUQBC1TjPsCyh5A=; b=NsiCulqC5ZbwTD3AJ2pZqsmXqya8swkvGdGcZWpnsCzBjMlMoqMHYGpFl+AJlzKdod UncK8YNwk7skav3UUG1KlRUZLKEjVjl+IoGzERW08kAj3pV8+WExNSoMUKzD68Egel+2 +IX4Q8q2kpI7wOHSWDf7LnZnJLd3RQQJCiwSa3PC4dWqSfef4ivBF08ZZihe/FM5+UrV nZvSLm3uRX7NtGqC6Q0RyJvLBM8qTpPZE2iPkJX0660hiNfekXJkHPrN7nhUOYN3s8JQ Rzxd9HhO3UICSk4YDMER8W8DP/NfJuUBANSAEIUmRl1T5QQHtnSZsXjEsCIqcDFQueCp rdtg==
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=QW0LJzjtQwgN0Gu1SvlxWG8+S0qzlUQBC1TjPsCyh5A=; b=ayMHq6ymBSU9eLgJ8df9BpXe+8C0LK2AuUJ9uvHxNPUeEm1bM01hv5Ae5QLnVtMCvu BW7nROPOJ8xzX4Wfq8lujtWTMwB6yqCfze4AT/92GZrQib/dvyJprmgzC87ns5BIy0UW qhZu4USxyminLzhJoWM8yyBDqfOOkk8wcX4HXHio9NvUcA8J34BoQ+6N3oUZzmF9YJVr ofyaBVdHukB5PIyPpCNWtrGg9BCnlrF1qTA5/xc0DDzWc7GI79RX9GVE3VfcohY4ZRWQ hGiYT5W6uR1JUV4Wh4KZ+ihIKrN98NL5zRIDozQdrDuG0+SSPFlUAFRzmonCaJEx1IJ0 AaTw==
X-Gm-Message-State: AOAM533qlMdOpSYy4/GkHcd4iJPqNkTN0ZhYlWbPSN2glKPzL0G2Ol8w V8U5RIhfPyHVbk9MWm0wshPc76o3xJ2EeyAuvVsTV0OmRRU=
X-Google-Smtp-Source: ABdhPJxHpLO/wG1AvK70QAdLsf2qYfAg62SUKH+zuhM+KC1P9oICT5IAgSnfC5knI+TFUAv+/b0STZVECJWhQD+lQFQ=
X-Received: by 2002:a02:c552:: with SMTP id g18mr4171416jaj.76.1613973513396; Sun, 21 Feb 2021 21:58:33 -0800 (PST)
MIME-Version: 1.0
References: <161382661374.28499.18406186700218024423@ietfa.amsl.com> <TY2PR01MB35621346BDF493F16DA03C7F90829@TY2PR01MB3562.jpnprd01.prod.outlook.com>
In-Reply-To: <TY2PR01MB35621346BDF493F16DA03C7F90829@TY2PR01MB3562.jpnprd01.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 22 Feb 2021 11:27:57 +0530
Message-ID: <CAB75xn6T0yumygFbbziyqN2d74MML4LQpH4UbmPhsysDQ8VvNg@mail.gmail.com>
To: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
Cc: "teas@ietf.org" <teas@ietf.org>, "ta-miyasaka@kddi.com" <ta-miyasaka@kddi.com>, "ry-fukui@kddi.com" <ry-fukui@kddi.com>
Content-Type: multipart/alternative; boundary="000000000000f1656205bbe67de5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Ds08k38N_2t_yZgP4vdAyLdcoCw>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-te-service-mapping-yang-06.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: Mon, 22 Feb 2021 05:58:37 -0000

Hi,

We have posted a -07 version that fixes this!

Thanks!
Dhruv

On Sun, Feb 21, 2021 at 8:14 AM Ogaki, Kenichi <ke-oogaki@kddi.com> wrote:

> Hi te-service-mapping-yang authors,
>
> Thanks for accommodating our request!
>
> However, the YANG model a little bit reverted compared with the conclusion
> in the following thread and the attached there.
> https://mailarchive.ietf.org/arch/msg/teas/C5HyR701gynAq8f_mZdl7XOZNew/
> ietf-l3sm-te-service-mapping@2020-11-08.yang
>
> Augmentations are necessary both for l3vpn-svc:site and
> l3vpn-svc:site-network-access.
>
>  augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site"
>               + "/l3vpn-svc:service/l3vpn-svc:qos/l3vpn-svc:qos-profile"
>               + "/l3vpn-svc:qos-profile/l3vpn-svc:custom"
>               + "/l3vpn-svc:classes/l3vpn-svc:class" {
>      description
>          "Augment of class with VNAP reference for the custom qos-profile";
>      uses tsm-types:te-endpoint-ref-vnap;
>  }
>
>  augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site"
>               +
> "/l3vpn-svc:site-network-accesses/l3vpn-svc:site-network-access"
>               + "/l3vpn-svc:service/l3vpn-svc:qos/l3vpn-svc:qos-profile"
>               + "/l3vpn-svc:qos-profile/l3vpn-svc:custom"
>               + "/l3vpn-svc:classes/l3vpn-svc:class" {
>      description
>          "Augment of class with VNAP reference for the custom qos-profile";
>      uses tsm-types:te-endpoint-ref-vnap;
>  }
>
>
> One more comment for the following, although even we can cover that when
> the latter one above is defined, what's the authors' intention to omit the
> mapping of VNAP to l3vpn-svc:site-network-access?
>
>  augment "/l3vpn-svc:l3vpn-svc/l3vpn-svc:sites/l3vpn-svc:site"
>               + "/l3vpn-svc:site-network-accesses"
>               + "/l3vpn-svc:site-network-access" {
>       description
>           "This augment is only valid for TE mapping of L3SM network-access
>             to TE endpoints";
>        uses tsmt:te-endpoint-ref;
>  }
>
> Thanks,
> Kenichi
> ------------------------------
> *From:* Teas <teas-bounces@ietf.org> on behalf of internet-drafts@ietf.org
> <internet-drafts@ietf.org>
> *Sent:* Saturday, February 20, 2021 10:11 PM
> *To:* i-d-announce@ietf.org
> *Cc:* teas@ietf.org
> *Subject:* [Teas] I-D Action:
> draft-ietf-teas-te-service-mapping-yang-06.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Traffic Engineering Architecture and
> Signaling WG of the IETF.
>
>         Title           : Traffic Engineering (TE) and Service Mapping
> Yang Model
>         Authors         : Young Lee
>                           Dhruv Dhody
>                           Giuseppe Fioccola
>                           Qin Wu
>                           Daniele Ceccarelli
>                           Jeff Tantsura
>         Filename        : draft-ietf-teas-te-service-mapping-yang-06.txt
>         Pages           : 51
>         Date            : 2021-02-20
>
> Abstract:
>    This document provides a YANG data model to map customer service
>    models (e.g., the L3VPN Service Model (L3SM)) to Traffic Engineering
>    (TE) models (e.g., the TE Tunnel or the Virtual Network (VN) model).
>    This model is referred to as TE Service Mapping Model and is
>    applicable generically to the operator's need for seamless control
>    and management of their VPN services with TE tunnel support.
>
>    The model is principally used to allow monitoring and diagnostics of
>    the management systems to show how the service requests are mapped
>    onto underlying network resource and TE models.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-teas-te-service-mapping-yang/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-teas-te-service-mapping-yang-06
>
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-te-service-mapping-yang-06
>
> A diff from the previous version is available at:
>
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-te-service-mapping-yang-06
>
>
> 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.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> 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
>