[OPSAWG]Re: [neotec] Re: Feedback Wanted: Is Attachment Circuit YANG Sufficient for Neotec Use Case?
Wei Wang <weiwang94@foxmail.com> Tue, 22 April 2025 08:34 UTC
Return-Path: <weiwang94@foxmail.com>
X-Original-To: opsawg@mail2.ietf.org
Delivered-To: opsawg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F057A1F3D870; Tue, 22 Apr 2025 01:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 1.088
X-Spam-Level: *
X-Spam-Status: No, score=1.088 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id llz9sgZcHXMq; Tue, 22 Apr 2025 01:34:08 -0700 (PDT)
Received: from out203-205-221-242.mail.qq.com (out203-205-221-242.mail.qq.com [203.205.221.242]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D32601F3D857; Tue, 22 Apr 2025 01:34:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1745310842; bh=HDCDt+VqmNQsLjHlhah7VYgX/NTgAvXfL/EJtdAs36Y=; h=From:To:Cc:Subject:Date:References:In-Reply-To; b=NuqLFcTf9gZaepNCJ3kU3ZVO3TJ0voq8U49gdgzZ8k97a3g/fFMxId/yInszsO8sN S+2CHEh1rU/A7N73GneXrYcbreqqH6oETGFRF/2ckicvmUKt86APzmQ0l9hxBuMmRl NU6gSVSo6rl0DgKFvbq8hEnFxQ7jb/77Uhws/rrQ=
X-QQ-XMRINFO: Mp0Kj//9VHAxr69bL5MkOOs=
X-QQ-XMAILINFO: NIviiJN9XgXANIMaKmY/UUhz6R+G0U3XHzMIhbUuXIw0hnN0mkt4oAT9oUg7t6 e/IZD/Kc9LV90IpyUuOvRfAH8eccMtBZYkbvaypXHh649CnLa+ngFTGTbVVsuE7ghQrhX5w/IUh+A nvzo+c0awNYDS2Y+LzAVQ+YXSn/qLarCqtN1nyYa0RS5c3vBAht4EOfSk7bEo6WpCRuHZaHJmi2SW 9l+/WuPo8Vi7zj/3hlt+SQeTfEncYKswgjxXCflX5Xw8FhoU/MSgyQFoGuN3LOnghczkAnOuHEkDe H1G0Es22IdruH8nhpJN1fsyFs2lPa9q9cJ7Y4nfG3t6S0EE+hgprtOUP3drnpCB2tESDSlps7X3TA lMivlukgPdAd2yFOWnzqWJ4mWjBhpuTY7uWCsKDYI+9piOfncNmLut9WCU8JIPzfCEUd7kinDsIH2 GMSpr2FaRYhamrLBMDjPXoqPhsPStRANIVR38rkE2kGmfyYQg6bjKVTesRqhLHrr6NDjyHw9q2e9P x11sfmNBzh3mbK4G27Psw6/SvSZEbODah01avdUU9FlQ4Ymlfgae7sT1FnJAxFM8aiJ79O2JIDFa3 /Q4k/fOY9o+vI96xc0hbGgiv0wjh2gBFL9zIIt6FH/TCTbdwMMmA3Z+kCre76gmolVj6Z/FEQHs4O mFBbyugvx1PkqzMMCUcoVO6fWmNIChtuF8fvJ64ABLcDmoJXlQcUdcNoPL7SlPnUGPYbthARlkk+8 /KZO8Ig8COQfFCY3YqoDvkYlXI/UnMApDSgoMe+7IiHERWhtcQG2hpyX8SCIxbWaDb7bb6Tmg/xQE rmM86/of+SaMjgg56rtEHGZ2HBmBIkTw74SvSV1CAWqpDdk2Xt5i4c3LkX8Ak134MRXtE0TTXX0qm A10oAnFs87F+9PdjZaSGKIE0reyZIR10jQ040a14rFvn44ylXYpYEVwE+9+S4kFvgMRwEcXVnMWPX UfFuPPy2RkGMMs4g16fSJh6nMTF42PS1zb/Be1V7rRAU/4UzFVOlb6YeiKK+lNx3EOT9RpueLJbCY pDZNAMPxyu0YIumSwbkf4EgJMASFECcuyQtQNO73mzuW77dfIYJVGXLyc0aAjjCJdEspHnUsb2Sjg 7YJER3drZApNyPpf2Ma/ezAkc2jgt9Mm9MAr5eGvIuM2gw==
From: Wei Wang <weiwang94@foxmail.com>
To: Linda Dunbar <dunbar.ll@gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_68075461_3F196260_553365AD"
Content-Transfer-Encoding: 8bit
Date: Tue, 22 Apr 2025 16:33:37 +0800
X-Priority: 3
Message-ID: <tencent_7FA6EDA55D542F72AE68FE862D3DD32E8A05@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
References: <CO1PR13MB492071A7A0E5C893E4C2A85A85BF2@CO1PR13MB4920.namprd13.prod.outlook.com> <tencent_066DEE6CDE840D27D33A2AA60DB8BD428F05@qq.com> <CAP_bo1YkCgFw=diFgLPx8vUzUhEH4AyBWSUjRR-_VMRszDKT_w@mail.gmail.com>
In-Reply-To: <CAP_bo1YkCgFw=diFgLPx8vUzUhEH4AyBWSUjRR-_VMRszDKT_w@mail.gmail.com>
X-QQ-mid: xmseza31-0t1745310817twaeuh4q3
Message-ID-Hash: WUMF6DMXAO4EJ4W5EP4DR4IKK6EK2QUN
X-Message-ID-Hash: WUMF6DMXAO4EJ4W5EP4DR4IKK6EK2QUN
X-MailFrom: weiwang94@foxmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-opsawg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "neotec@ietf.org" <neotec@ietf.org>, opsawg <opsawg@ietf.org>, Joel Halpern Direct <jmh.direct@joelhalpern.com>, Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OPSAWG]Re: [neotec] Re: Feedback Wanted: Is Attachment Circuit YANG Sufficient for Neotec Use Case?
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/l4MUYTZCXP9OAEWpjm036FKFW6g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Owner: <mailto:opsawg-owner@ietf.org>
List-Post: <mailto:opsawg@ietf.org>
List-Subscribe: <mailto:opsawg-join@ietf.org>
List-Unsubscribe: <mailto:opsawg-leave@ietf.org>
Hi Linda,
Thank you for your feedback to me.
I also agree with Neotec's API framework of opening up the YANG model to the cloud through API. IETF has defined many YANG models, but the fact is that the proportion in practical applications is not high. The idea of opening up the YANG model to the cloud through API may be an effective way to improve its usage,it also meets the cloud and network collaboration needs of our operators.
I also agree with Chongfeng's suggestion that "Clous Service ID" should be introduced, this will make the role of policy more focused. I also have one suggestion, in figure 8, "source-sites" and "dest-sites" may be too coarse to identify a service instance, so I propose to add an attribute of "Cloud Service ID" in this policy, based on this ID, the policies for specific service traffic can be issued to the network controller, and traffic that crosses different paths can also be easily associated based on this ID.
Best regards,
Wei
原始邮件
发件人:Linda Dunbar <dunbar.ll@gmail.com>
发件时间:2025年4月22日 00:48
收件人:Wei Wang <weiwang94@foxmail.com>
抄送:Linda Dunbar <linda.dunbar@futurewei.com>, neotec@ietf.org <neotec@ietf.org>, opsawg <opsawg@ietf.org>, mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>, Joel Halpern Direct <jmh.direct@joelhalpern.com>, Mahesh Jethanandani <mjethanandani@gmail.com>
主题:[neotec] Re: [OPSAWG]Feedback Wanted: Is Attachment Circuit YANG Sufficient for Neotec Use Case?
Wei,
Thank you very much for the review and a very good question.
Please see below for the detailed answer:
On Fri, Apr 18, 2025 at 5:48 PM Wei Wang <weiwang94@foxmail.com> wrote:
HI Linda,
The case in this draft is very typical in the illustration of network operation for telecom cloud, thank for your effort. I have one question regarding the model: What if the network between the access point and edge cloud data center is typical Internet network, which is not TE based, what model can be used?
[Linda] That is a very good question. By the way, we have updated the draft with SRv6 and TE underlay added: https://datatracker.ietf.org/doc/draft-dunbar-neotec-ac-te-applicability/
To address your question, we might need to add some study of Non-TE-Based or Internet-Backed PE-PE Networks:
In Non-TE-Based or Internet-Backed PE-PE Networks, basic connectivity and performance data may still be obtained using existing IETF YANG models such as:
- RFC 8343 (YANG Data Model for Interface Management) and RFC 8344 ( YANG Data Model for IP Management) for interface and IP layer status
- ietf-routing [RFC8349] to understand basic forwarding paths and
route preferences
- Operational telemetry models for real-time monitoring of metrics like:
* Interface utilization
* Packet loss
* Round-trip time (RTT)
* Jitter (if measured using active probes or synthetic monitoring)
In these cases, instead of path-level traffic engineering, the
orchestrator or Cloud Manager can query and interpret per-hop or
per-segment interface metrics, or use active measurements (e.g., IP SLA-like probes) to estimate end-to-end path characteristics. These inputs can inform workload placement decisions, albeit without the
deterministic path selection and enforcement that TE-based architectures allow.
Neotec’s API framework can abstract these differences by returning
consistent metrics (e.g., latency, bandwidth availability), regardless
of whether they are derived from TE topology models or measured
heuristically in best-effort environments.
Linda
Thanks
Wei
---Original---
From: "Linda Dunbar"<linda.dunbar@futurewei.com>
Date: Fri, Apr 18, 2025 10:32 AM
To: "neotec@ietf.org"<neotec@ietf.org>;"'opsawg'"<opsawg@ietf.org>;"mohamed.boucadair@orange.com"<mohamed.boucadair@orange.com>;
Cc: "Joel Halpern Direct"<jmh.direct@joelhalpern.com>;"Mahesh Jethanandani"<mjethanandani@gmail.com>;
Subject: [OPSAWG]Feedback Wanted: Is Attachment Circuit YANG Sufficient for Neotec Use Case?
Med,
Following your suggestion during IETF 122 for us to take a simple Neotec use case and "do our homework" by applying existing IETF YANG models—specifically the Attachment Circuit model— we’ve completed an initial exercise and documented it in the following draft:
"Applicability of Attachment Circuit and TE YANG Models to a Neotec Use Case"
https://datatracker.ietf.org/doc/draft-dunbar-neotec-ac-te-applicability/
Our goal with this draft is to evaluate whether the AC and TE YANG models are sufficient to support the selected use case, and to identify any potential modeling or architectural gaps. This is intended as an exploratory step to evaluate whether there is substantive, standards-relevant work that could justify a Neotec WG.
We would greatly appreciate your feedback: Does this exercise align with what you envisioned? Are we on the right track? Any guidance or suggestions on how to refine the framing would be greatly appreciated.
Cc'ing the opsawg mailing list here in case others would like to help us evaluate the approach and share perspectives on the usefulness of this line of inquiry.
Best regards,
Linda
_______________________________________________
neotec mailing list -- neotec@ietf.org
To unsubscribe send an email to neotec-leave@ietf.org
- [OPSAWG]Feedback Wanted: Is Attachment Circuit YA… Linda Dunbar
- [OPSAWG]Re: [neotec] Feedback Wanted: Is Attachme… Fan Zhang
- [OPSAWG]Re: [neotec] Re: Feedback Wanted: Is Atta… Linda Dunbar
- [OPSAWG]Re: [neotec] Re: Feedback Wanted: Is Atta… Fan Zhang
- [OPSAWG]Re: Feedback Wanted: Is Attachment Circui… Wei Wang
- [OPSAWG]Re: [neotec] Re: Feedback Wanted: Is Atta… Linda Dunbar
- [OPSAWG]Re: [neotec] Re: Feedback Wanted: Is Atta… Wei Wang
- [OPSAWG]Re: [neotec] Feedback Wanted: Is Attachme… Chongfeng Xie
- [OPSAWG]Re: [neotec] Re: Feedback Wanted: Is Atta… Linda Dunbar
- [OPSAWG]Re: Feedback Wanted: Is Attachment Circui… mohamed.boucadair
- [OPSAWG]Resolutions to your suggestions and comme… Linda Dunbar