[OPSAWG] RFC 9181 on A Common YANG Data Model for Layer 2 and Layer 3 VPNs

rfc-editor@rfc-editor.org Wed, 16 February 2022 03:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F261E3A0128; Tue, 15 Feb 2022 19:52:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyGGMhjZvgmZ; Tue, 15 Feb 2022 19:52:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 747413A00E5; Tue, 15 Feb 2022 19:52:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 2299A4C1DA; Tue, 15 Feb 2022 19:52:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, opsawg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220216035223.2299A4C1DA@rfc-editor.org>
Date: Tue, 15 Feb 2022 19:52:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/wicFASgkARCrlnqH5ldvXc2-O24>
Subject: [OPSAWG] RFC 9181 on A Common YANG Data Model for Layer 2 and Layer 3 VPNs
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2022 03:52:29 -0000

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

        
        RFC 9181

        Title:      A Common YANG Data Model 
                    for Layer 2 and Layer 3 VPNs 
        Author:     S. Barguil,
                    O. Gonzalez de Dios, Ed.,
                    M. Boucadair, Ed.,
                    Q. Wu
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2022
        Mailbox:    samier.barguilgiraldo.ext@telefonica.com,
                    oscar.gonzalezdedios@telefonica.com,
                    mohamed.boucadair@orange.com,
                    bill.wu@huawei.com
        Pages:      60
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-vpn-common-12.txt

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

        DOI:        10.17487/RFC9181

This document defines a common YANG module that is meant to be reused
by various VPN-related modules such as Layer 3 VPN and Layer 2 VPN
network models.

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