Protocol Action: 'YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service (ACaaS)' to Proposed Standard (draft-ietf-opsawg-teas-attachment-circuit-20.txt)
The IESG <iesg-secretary@ietf.org> Thu, 06 February 2025 20:56 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from mail.ietf.org (ietfa.amsl.com [50.223.129.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id E5F96C16941B; Thu, 6 Feb 2025 12:56:57 -0800 (PST)
Received: from [10.244.8.212] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 4B431C137367; Thu, 6 Feb 2025 12:56:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service (ACaaS)' to Proposed Standard (draft-ietf-opsawg-teas-attachment-circuit-20.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.35.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <173887541695.454.8369450165320121897@dt-datatracker-75c44cbbdf-pxnd6>
Date: Thu, 06 Feb 2025 12:56:56 -0800
Message-ID-Hash: ADKR62UPG6RBBICBKMKUELGOZ7UPHKJU
X-Message-ID-Hash: ADKR62UPG6RBBICBKMKUELGOZ7UPHKJU
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, draft-ietf-opsawg-teas-attachment-circuit@ietf.org, mjethanandani@gmail.com, opsawg-chairs@ietf.org, opsawg@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-270V-8Kj0NSPxPMzMf8COr-zPQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The IESG has approved the following document: - 'YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service (ACaaS)' (draft-ietf-opsawg-teas-attachment-circuit-20.txt) as Proposed Standard This document is the product of the Operations and Management Area Working Group. The IESG contact persons are Warren Kumari and Mahesh Jethanandani. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-opsawg-teas-attachment-circuit/ Technical Summary This document specifies a YANG service data model for Attachment Circuits (ACs). This model can be used for the provisioning of ACs before or during service provisioning (e.g., Network Slice Service). The document also specifies a service model for managing bearers over which ACs are established. Working Group Summary Was there anything in the WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? The WG's last call on the set of documents dealing with the attachment circuits work was launched to both OPSAWG and TEAS mailing lists. Few WG members responded expressing support for the last call (one of them being authors/contributors), all providing positive feedback. There was no objection to publication. Document Quality Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type, or other Expert Review, what was its course (briefly)? In the case of a Media Type Review, on what date was the request posted? The document describes a YANG data model. No specific implementations have been reported. Personnel The Document Shepherd for this document is Luis M. Contreras. The Responsible Area Director is Mahesh Jethanandani. IANA Note All expert reviews have been completed with no blocking issues