[L2sm] RFC 8466 on A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
rfc-editor@rfc-editor.org Fri, 12 October 2018 20:49 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F70512D4EE; Fri, 12 Oct 2018 13:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 I9o2jU5zdu1p; Fri, 12 Oct 2018 13:49:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 353DC12D4E8; Fri, 12 Oct 2018 13:49:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 14B2CB8159B; Fri, 12 Oct 2018 13:49:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, l2sm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181012204911.14B2CB8159B@rfc-editor.org>
Date: Fri, 12 Oct 2018 13:49:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/BkkoBkohX6E51SSlx0Bkz7QwGo4>
Subject: [L2sm] RFC 8466 on A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2018 20:49:34 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8466
Title: A YANG Data Model for
Layer 2 Virtual Private Network (L2VPN)
Service Delivery
Author: B. Wen,
G. Fioccola, Ed.,
C. Xie,
L. Jalil
Status: Standards Track
Stream: IETF
Date: October 2018
Mailbox: bin_wen@comcast.com,
giuseppe.fioccola@tim.it,
xiechf.bri@chinatelecom.cn,
luay.jalil@verizon.com
Pages: 158
Characters: 315113
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l2sm-l2vpn-service-model-10.txt
URL: https://www.rfc-editor.org/info/rfc8466
DOI: 10.17487/RFC8466
This document defines a YANG data model that can be used to configure
a Layer 2 provider-provisioned VPN service. It is up to a management
system to take this as an input and generate specific configuration
models to configure the different network elements to deliver the
service. How this configuration of network elements is done is out
of scope for this document.
The YANG data model defined in this document includes support for
point-to-point Virtual Private Wire Services (VPWSs) and multipoint
Virtual Private LAN Services (VPLSs) that use Pseudowires signaled
using the Label Distribution Protocol (LDP) and the Border Gateway
Protocol (BGP) as described in RFCs 4761 and 6624.
The YANG data model defined in this document conforms to the Network
Management Datastore Architecture defined in RFC 8342.
This document is a product of the L2VPN Service Model 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