[OPSAWG] RFC 9291 on A YANG Network Data Model for Layer 2 VPNs

A new Request for Comments is now available in online RFC libraries.

        RFC 9291

        Title:      A YANG Network Data Model 
                    for Layer 2 VPNs 
        Author:     M. Boucadair, Ed.,
                    O. Gonzalez de Dios, Ed.,
                    S. Barguil,
                    L. Munoz
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2022
        Mailbox:    mohamed.boucadair@orange.com,
                    oscar.gonzalezdedios@telefonica.com,
                    samier.barguilgiraldo.ext@telefonica.com,
                    luis-angel.munoz@vodafone.com
        Pages:      139
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-l2nm-19.txt

        URL:        https://www.rfc-editor.org/info/rfc9291

        DOI:        10.17487/RFC9291

This document defines an L2VPN Network Model (L2NM) that can be used
to manage the provisioning of Layer 2 Virtual Private Network (L2VPN)
services within a network (e.g., a service provider network). The
L2NM complements the L2VPN Service Model (L2SM) by providing a
network-centric view of the service that is internal to a service
provider. The L2NM is particularly meant to be used by a network
controller to derive the configuration information that will be sent
to relevant network devices.

Also, this document defines a YANG module to manage Ethernet segments
and the initial versions of two IANA-maintained modules that include
a set of identities of BGP Layer 2 encapsulation types and pseudowire
types.

This document is a product of the Operations and Management Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC