Re: [Teas] clarification to actn-vn-yang

"Ogaki, Kenichi" <ke-oogaki@kddi.com> Wed, 15 July 2020 00:11 UTC

Return-Path: <ke-oogaki@kddi.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 1B0723A094B; Tue, 14 Jul 2020 17:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 LBopz9N-pawU; Tue, 14 Jul 2020 17:11:24 -0700 (PDT)
Received: from kddi.com (athena4.kddi.com [27.90.165.197]) by ietfa.amsl.com (Postfix) with ESMTP id 9225F3A0940; Tue, 14 Jul 2020 17:11:24 -0700 (PDT)
Received: from LTMC2123.kddi.com (post-send [10.206.2.120]) by kddi.com (KDDI Mail) with ESMTP id 95397120050; Wed, 15 Jul 2020 09:11:23 +0900 (JST)
Received: from LTMC2144.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2123.kddi.com with ESMTP; Wed, 15 Jul 2020 09:11:23 +0900
Received: from LTMC2144.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 74E374C005E; Wed, 15 Jul 2020 09:11:23 +0900 (JST)
Received: from LTMC2154.kddi.com (post-incheck [10.206.0.239]) by LTMC2144.kddi.com (Postfix) with ESMTP id 699B74C005C; Wed, 15 Jul 2020 09:11:23 +0900 (JST)
Received: from LTMC2154.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2154.kddi.com with ESMTP id 06F0BNDa073696; Wed, 15 Jul 2020 09:11:23 +0900
Received: from LTMC2154.kddi.com.mid_87326095 (localhost.localdomain [127.0.0.1]) by LTMC2154.kddi.com with ESMTP id 06F01Ija061856; Wed, 15 Jul 2020 09:01:19 +0900
X-SA-MID: 87326095
Received: from KDDI1801PC1319 ([10.211.4.86] [10.211.4.86]) by post-smtp2.kddi.com with ESMTPA; Wed, 15 Jul 2020 09:01:18 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: "'Dhruv Dhody'" <dhruv.ietf@gmail.com>
Cc: =?utf-8?B?J+S4uee+vSDmnJ3kv6En?= <to-niwa@kddi.com>, <draft-ietf-teas-actn-vn-yang@ietf.org>, =?utf-8?B?J+WuruWdgiDmi5PkuZ8n?= <ta-miyasaka@kddi.com>, "'TEAS WG'" <teas@ietf.org>
References: <004d01d656a8$677ae4d0$3670ae70$@kddi.com> <CAB75xn5VTc97_Zyea27Tngq+zsEX5ttTwRvLO_2o1xK5gL_HEQ@mail.gmail.com> <002e01d659a0$e2a2ae40$a7e80ac0$@kddi.com> <CAB75xn7N--HdKfYvneCP2-jO8hoz=fcWw2p7dv9zrqF5mT-ZdQ@mail.gmail.com>
In-Reply-To: <CAB75xn7N--HdKfYvneCP2-jO8hoz=fcWw2p7dv9zrqF5mT-ZdQ@mail.gmail.com>
Date: Wed, 15 Jul 2020 09:01:18 +0900
Message-ID: <004001d65a3b$10cc40c0$3264c240$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKPNZ6eqrEs8TlLfJjXkrr9i6UxagH0/W+qAXi9jG4CBjDiladqaZCQ
Content-Language: ja
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/kzutAtMFK28E3fGaXVq59njONCY>
Subject: Re: [Teas] clarification to actn-vn-yang
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 00:11:27 -0000

Hi Dhruv,

Thanks you for the prompt reply.

>Please let us know if you have any suggestions to improve it.

Although I may bring up the old discussion again, for the usability purpose from an operator perspective, could you add path-constraints to at least vn-compute/input?

We don't mind using te-topo behind this model, however, as a customer service model, we believe more abstraction to the provider interface (CMI) is desired.
At least, if the consumer of CMI could conduct vn-compute/input without taking care of the detail, i.e. te-topo (connectivity matrix), and get the necessary te-topo as the output, then the consumer only have to refer the output te-topo instance in order to initiate the actual vn.

How do you think?

Thanks,
Kenichi

-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of Dhruv Dhody
Sent: Tuesday, July 14, 2020 4:04 PM
To: Ogaki, Kenichi <ke-oogaki@kddi.com>
Cc: 丹羽 朝信 <to-niwa@kddi.com>om>; draft-ietf-teas-actn-vn-yang@ietf.org; 宮坂 拓也 <ta-miyasaka@kddi.com>om>; TEAS WG <teas@ietf.org>
Subject: Re: [Teas] clarification to actn-vn-yang

Hi Kenichi,

On Tue, Jul 14, 2020 at 11:17 AM Ogaki, Kenichi <ke-oogaki@kddi.com> wrote:
>
> Hi Dhruv,
>
> Thank you for the clarification.
>
> Even though I just looked through the section 7 and doesn't feel intuitive, I understand the situation.
>

Please let us know if you have any suggestions to improve it.

> If we require any performance constraint to VN topology, CNC must post te-topo with a connection matrix along with the constraint, in the case of section 3.1.
> For example, path-metric-bounds should be set to path-constraints of connectivity-matrices instead of bandwidth-generic in section 7.2 example.
> We will check carefully if this meets what we want.
>

Sure!

> >My initial feeling was we could get it from the bandwidth at the VN-member level but I think it would be still useful to put it in vnap as well. I have added it now.
>
> The -09 version added max-bandwidth under vn-ap entry, but ro (operational) data. What do you intend this? You mean that we should set vn-member level bandwidth constraints with te-topo as well, and just retrieve the ro data from this model..
>

That is correct!

Thanks!
Dhruv

> Thanks,
> Kenichi
>
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of Dhruv Dhody
> Sent: Tuesday, July 14, 2020 3:52 AM
> To: Ogaki, Kenichi <ke-oogaki@kddi.com>
> Cc: 丹羽 朝信 <to-niwa@kddi.com>om>; draft-ietf-teas-actn-vn-yang@ietf.org; 宮坂 拓也 <ta-miyasaka@kddi.com>om>; TEAS WG (teas@ietf.org) <teas@ietf.org>
> Subject: Re: [Teas] clarification to actn-vn-yang
>
> Hi Kenichi,
>
> Thank you for your comments and insight.
>
> On Fri, Jul 10, 2020 at 4:34 PM Ogaki, Kenichi <ke-oogaki@kddi.com <mailto:ke-oogaki@kddi.com> > wrote:
>
>
>         Hi actn-vn-yang authors,
>
>         Can I clarify the following two questions?
>
>
>         1) consideration of the key network performance constraints
>
>         I'd like to clarify how actn-vn-yang considers key network performance constraints in the sense of RFC8233 Appendix A, latency, delay variation, loss,...?
>
>
>
>
> We rely on the te-topology connectivity matrix for this. Refer the path-metric-bounds and optimization, there based on the metric-types these can be supported. The common te-types in RFC 8776 include some of them and I would guess other modules would augment more types.
>
>
>         As an operator, we at KDDI are internally discussing to adopt actn-vn-yang to compute/setup VN (topology) as NBI consumed by our OSS/BSS corresponding to CNC. Then, we ask you to accommodate the consideration of the key network performance constraints into the model, for example at the same level of vn-level-diversity in both a vn-list entity and vn-compute/input.
>
>
>
>
> This was our approach initially, but the WG did not like that and wanted us to re-use the existing TE topology model, and thus we came up with an approach where a reference to an abstract node (of the TE topology YANG model) is put in VN Yang model and we rely on the connectivity-matrix structure to assign the constraints. See the backup pages in https://datatracker.ietf.org/meeting/105/materials/slides-105-teas-sessb-04-a-yang-data-model-for-vn-operation-00.. I have added some descriptions in the appendix as well in the latest version.
>
>
>
>         As the same context, actn-pm-telemetry-autonomics, some authors overwrap, already considers the key network performance data and compute/setup VN as autonomic scaling intent as follows. In that sense, CMI of ACTN must support this capability and it's natural for actn-vn-yang to do so, too.
>
>         actn-pm-telemetry-autonomics says:
>         2.  Use-Cases
>            o  Customer services have various Service Level Agreement (SLA)
>               requirements, such as service availability, latency, latency
>               jitter, packet loss rate, Bit Error Rate (BER), etc.  The
>               transport network can satisfy service availability and BER
>               requirements by providing different protection and restoration
>               mechanisms.  However, for other performance parameters, there are
>               no such mechanisms.  In order to provide high quality services
>               according to customer SLA, one possible solution is to measure the
>               SLA related performance parameters, and dynamically provision and
>               optimize services based on the performance monitoring results.
>
>         3.2.  VN KPI Telemetry Model
>            This module also allows autonomic traffic engineering scaling intent configuration mechanism on the VN
>            level.
>
>         4.  Autonomic Scaling Intent Mechanism
>            o  performance-type: performance metric type (e.g., one-way-delay,
>               one-way-delay-min, one-way-delay-max, two-way-delay, two-way-
>               delay-min, two-way-delay-max, utilized bandwidth, etc.)
>
>            o  threshold-value: the threshold value for a certain performance-
>               type that triggers scale-in or scale-out.
>
>
>
>
> You are correct to note that this model provides the (1) measured telemetry data and (2) specify threshold based on different metric-type on for scaling purposes. This is a new advanced feature defined in this I-D for the first time.
>
> But, the WG felt that specifying constraints at the time of VN creation can be achieved by the existing connectivity matrix construct and thus we were asked to reuse it.
>
>
>
>         2) VNAP level bandwidth control
>
>         The current model can indicate the max/available bandwidth to Access Point corresponding to (physical) customer's end point. However, we also want to do so at Virtual Network Access Point level, which corresponds to traffic engineering of vn-member level. Is there any problem?
>
>
>
>
> My initial feeling was we could get it from the bandwidth at the VN-member level but I think it would be still useful to put it in vnap as well. I have added it now.
>
> Thanks!
> Dhruv
>
>
>
>         We of course understand augmentations to solve these requirements, but we believe these are general requirements, and then desire to accommodate to the model.
>
>         Thanks in advance,
>         Kenichi
>
>         --
>         Kenichi Ogaki
>         KDDI Corp. | Operation Automation Promotion Dept.
>         +81-(0)80-5945-9138 | www.kddi.com <http://www.kddi.com>
>
>
>
>
>
>
>
>

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