Protocol Action: 'A Network YANG Data Model for Attachment Circuits' to Proposed Standard (draft-ietf-opsawg-ntw-attachment-circuit-16.txt)
The IESG <iesg-secretary@ietf.org> Thu, 06 February 2025 20:55 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 A5EC9C1D5307; Thu, 6 Feb 2025 12:55:06 -0800 (PST)
Received: from [10.244.8.212] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 09DEAC234FDF; Thu, 6 Feb 2025 12:55:05 -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: 'A Network YANG Data Model for Attachment Circuits' to Proposed Standard (draft-ietf-opsawg-ntw-attachment-circuit-16.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: <173887530569.258.10773553048952461134@dt-datatracker-75c44cbbdf-pxnd6>
Date: Thu, 06 Feb 2025 12:55:05 -0800
Message-ID-Hash: X6WCIXKCU4P3FHZEVCO2PJSJG2NPTASG
X-Message-ID-Hash: X6WCIXKCU4P3FHZEVCO2PJSJG2NPTASG
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-ntw-attachment-circuit@ietf.org, kszarkowicz@juniper.net, 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/1vta4_VhouoJKquVArAAArPuOJU>
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: - 'A Network YANG Data Model for Attachment Circuits' (draft-ietf-opsawg-ntw-attachment-circuit-16.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-ntw-attachment-circuit/ Technical Summary This document specifies a network model for attachment circuits. The model can be used for the provisioning of attachment circuits prior or during service provisioning (e.g., VPN, Network Slice Service). A companion service model is specified in the YANG Data Models for Bearers and 'Attachment Circuits'-as-a-Service (ACaaS) (I-D.ietf- opsawg-teas-attachment-circuit). The module augments the base network ('ietf-network') and the Service Attachment Point (SAP) models with the detailed information for the provisioning of attachment circuits in Provider Edges (PEs). 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? Feedback in the WG mailing list for this draft is positive, and there is a broad agreement for support of this draft, without strong controversy or extreme discontent. 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? One of the normative references [IEEE802.1Qcp] might not be freely available to anyone. However, typically, the community has sufficient access to review this reference. Two other normative references are IETF drafts. However, undergoing WG LC at the same time as this draft. Personnel The Document Shepherd for this document is Krzysztof Grzegorz Szarkowicz. The Responsible Area Director is Mahesh Jethanandani. IANA Note All expert reviews have been completed with no blocking issues