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

Greg Mirsky <gregimirsky@gmail.com> Sun, 19 July 2020 01:52 UTC

Return-Path: <gregimirsky@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 2B40D3A060A; Sat, 18 Jul 2020 18:52:16 -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 OAm3a4bVyvi0; Sat, 18 Jul 2020 18:52:14 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 A996D3A05A0; Sat, 18 Jul 2020 18:52:13 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id j11so16652643ljo.7; Sat, 18 Jul 2020 18:52:13 -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=kmqdAXGRoVyn7gdJQ3ph+haWvi8S4+3NkqJY0Mbqjo4=; b=GBtM1yedFoPpGQeFFh5kUp7zQYpwesBHC7oIisYyfHlgsbdiNkIscbHyOwiTZAALkE pU9G21CypSPrHV40MV209cp2OyRDiTjRw2KwbbhCAv0ZWwyblCcmUj9nw1CBwcZt19XV 4bpfROSdj+VZBRMSk1LTCuahI6G1wI2hBrN0nyza77FmRCNw94gwVwPDGnQH0xQNiSHS oM0MqbjxHRnUgL2pAN05GimQUlZHfHlq7c556SogSno5NuhKPefmWapInaO0OFbwng5T ellSDJWq5/wz+GvMi/kCXKKQDOnuvQ6Aiu40TJvSSJWMpIGJpTO41dm+hE4jcBtpEFj6 aTQw==
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=kmqdAXGRoVyn7gdJQ3ph+haWvi8S4+3NkqJY0Mbqjo4=; b=ugc+dasAECOf55gGXB1RCPuQvmYLtQOhMdph6W3WxVxTxSeTWihQBRfGSwGzzoyput 8aSGIOnaaSMhFyswVaPgae/f4i8KZWoZF04X5A9ovY2Gzs8OrfDIc1c0VuXcrvRy47TJ 7SkLnPcyfu1XV9CCVJhUT1ytUMQLfdiiFIFZCQonl1p97znbYRK4du2Cklv+drbS/+wT 8frqvDq3yVcw2iqKUTLNjVktNCcMVIfjvuwYQglzmUmYUVO99V5bc7RClq/gzvnMzPrW Al1TLccFugNV6xoQjIZ7HoyX14H12XMUoF9wo6+YyUBSB+VF98bBHmnDIXfC7Pv2I78u cn7A==
X-Gm-Message-State: AOAM532IJVHuSl7rXtd2krukMDw5zvTTpgDFHnws/Qny3ADUPND6JGRm YysmAqJVuyrc58tRZ+yY5VVN+7xgas0EQxaR/+A=
X-Google-Smtp-Source: ABdhPJxMqniqyXRPicqhjP4uIxZqnQjgR1oEsmtOW9WTfILEWr6UuqPn6dZSJZkhtMKXmiGOrJTgtj8XMmfvL+2AFz4=
X-Received: by 2002:a2e:7804:: with SMTP id t4mr7405903ljc.8.1595123531944; Sat, 18 Jul 2020 18:52:11 -0700 (PDT)
MIME-Version: 1.0
References: <004d01d656a8$677ae4d0$3670ae70$@kddi.com> <CAB75xn5VTc97_Zyea27Tngq+zsEX5ttTwRvLO_2o1xK5gL_HEQ@mail.gmail.com>
In-Reply-To: <CAB75xn5VTc97_Zyea27Tngq+zsEX5ttTwRvLO_2o1xK5gL_HEQ@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sat, 18 Jul 2020 18:52:02 -0700
Message-ID: <CA+RyBmVeuA_orrDJUBMSQdLi4s7JJ2XRydUa7pfyBG0WFowpNQ@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: "Ogaki, Kenichi" <ke-oogaki@kddi.com>, =?UTF-8?B?5Li55769IOacneS/oQ==?= <to-niwa@kddi.com>, draft-ietf-teas-actn-vn-yang@ietf.org, =?UTF-8?B?5a6u5Z2CIOaLk+S5nw==?= <ta-miyasaka@kddi.com>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007e95ac05aac1a35b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/PgWKFYb9ia3ftAgJWSBVld3AEv4>
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: Sun, 19 Jul 2020 01:52:16 -0000

Hi Druv,
in your response you've mentioned:
"... this model provides the (1) measured telemetry data .."
Does that apply to the performance metrics listed in Use Cases:
     Customer services have various Service Level Agreement (SLA)
      requirements, such as service availability, latency, latency
      jitter, packet loss rate, Bit Error Rate (BER), etc.
If "yes", I would greatly appreciate it if you can reference measurement
methodology for service availability, latency jitter, and packet loss rate.

Regards,
Greg

On Mon, Jul 13, 2020 at 11:52 AM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:

> Hi Kenichi,
>
> Thank you for your comments and insight.
>
> On Fri, Jul 10, 2020 at 4:34 PM Ogaki, Kenichi <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
>>
>>
>>
>>
>>
>> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>