A YANG Data Model for Augmenting VPN Service and Network Models with Attachment Circuits
draft-ietf-opsawg-ac-lxsm-lxnm-glue-14

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, bill.wu@huawei.com, draft-ietf-opsawg-ac-lxsm-lxnm-glue@ietf.org, mjethanandani@gmail.com, opsawg-chairs@ietf.org, opsawg@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'A YANG Data Model for Augmenting VPN Service and Network Models with Attachment Circuits' to Proposed Standard (draft-ietf-opsawg-ac-lxsm-lxnm-glue-14.txt)

The IESG has approved the following document:
- 'A YANG Data Model for Augmenting VPN Service and Network Models with
   Attachment Circuits'
  (draft-ietf-opsawg-ac-lxsm-lxnm-glue-14.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-ac-lxsm-lxnm-glue/

Ballot Text

Technical Summary

   The document specifies a module that updates existing service (i.e.,
   the Layer 2 Service Model (L2SM) and the Layer 3 Service Model
   (L3SM)) and network (i.e., the Layer 2 Network Model (L2NM) and the
   Layer 3 Network Model (L3NM)) Virtual Private Network (VPN) modules
   with the required information to bind specific VPN services to
   Attachment Circuits (ACs) that are created using the AC service
   ("ietf-ac-svc") and network ("ietf-ac-ntw") models.

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? 

   This draft was last called together with other three companion drafts, i.e.,
   https://datatracker.ietf.org/doc/draft-ietf-opsawg-teas-common-ac/
   https://datatracker.ietf.org/doc/draft-ietf-opsawg-ntw-attachment-circuit/
   https://datatracker.ietf.org/doc/draft-ietf-opsawg-teas-attachment-circuit/
   The WGLC started on April 19 and was run for 3 weeks due to cross-area
   collaboration with TEAS WG. Note that attachment circuit series drafts had
   been presented and broadly discussed in both TEAS WG and opsawg WG session.
   In addition, this draft has received reviews and inputs from RTWG DIR and
   YANG Doctor. These reviews and inputs on both the TEAS WG mailing list and
   opsawg WG mailing list helped resolve
   the remaining issues associated with this draft.

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?

   It was reported some operators have already considered implementing this
   draft for a network-slicing automation solution. In addition, the IETF network
   slice NBI YANG model work in TEAS WG referenced attachment circuit work and
   discussed usage of attachment circuit for IETF network slice service. 3GPP
   R18 also referenced the attachment circuit draft for the 3GPP end-to-end network
   slice.

Personnel

   The Document Shepherd for this document is Qin Wu. The Responsible Area
   Director is Mahesh Jethanandani.

IANA Note

  All expert reviews have been completed with no blocking issues

RFC Editor Note