[L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery
rfc-editor@rfc-editor.org Thu, 23 February 2017 00:25 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D203129BDF; Wed, 22 Feb 2017 16:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 eJ4kWz1hxBvx; Wed, 22 Feb 2017 16:25:50 -0800 (PST)
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 B23B812943E; Wed, 22 Feb 2017 16:25:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A9449B812DF; Wed, 22 Feb 2017 16:25:50 -0800 (PST)
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
Message-Id: <20170223002550.A9449B812DF@rfc-editor.org>
Date: Wed, 22 Feb 2017 16:25:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/qH15Q_UbeDPBR2C-fnsVDDxF42s>
Cc: l3sm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 00:25:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8049
Title: YANG Data Model for L3VPN
Service Delivery
Author: S. Litkowski, L. Tomotaki, K. Ogaki
Status: Standards Track
Stream: IETF
Date: February 2017
Mailbox: stephane.litkowski@orange.com,
luis.tomotaki@verizon.com,
ke-oogaki@kddi.com
Pages: 157
Characters: 272974
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l3sm-l3vpn-service-model-19.txt
URL: https://www.rfc-editor.org/info/rfc8049
DOI: 10.17487/RFC8049
This document defines a YANG data model that can be used for
communication between customers and network operators and to deliver
a Layer 3 provider-provisioned VPN service. This document is limited
to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364. This
model is intended to be instantiated at the management system to
deliver the overall service. It is not a configuration model to be
used directly on network elements. This model provides an abstracted
view of the Layer 3 IP VPN service configuration components. It will
be up to the management system to take this model as input and use
specific configuration models to configure the different network
elements to deliver the service. How the configuration of network
elements is done is out of scope for this document.
This document is a product of the L3VPN 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
- [L3sm] RFC 8049 on YANG Data Model for L3VPN Serv… rfc-editor
- [L3sm] Fwd: RFC 8049 on YANG Data Model for L3VPN… Benoit Claise