[L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-19.txt
internet-drafts@ietf.org Mon, 07 November 2016 17:20 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l3sm@ietf.org
Delivered-To: l3sm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 11321129850; Mon, 7 Nov 2016 09:20:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147853925506.7946.4035104428850760454.idtracker@ietfa.amsl.com>
Date: Mon, 07 Nov 2016 09:20:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/1JnKGSkMiJg7L2-D8q3_oNq0NBg>
Cc: l3sm@ietf.org
Subject: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-19.txt
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 07 Nov 2016 17:20:55 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the L3VPN Service Model of the IETF. Title : YANG Data Model for L3VPN service delivery Authors : Stephane Litkowski Luis Tomotaki Kenichi Ogaki Filename : draft-ietf-l3sm-l3vpn-service-model-19.txt Pages : 161 Date : 2016-11-07 Abstract: 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. The document is limited to the BGP PE-based VPNs as described in [RFC4026], [RFC4110] and [RFC4364]. This model is intended to be instantiated at management system to deliver the overall service. This model is not a configuration model to be used directly on network elements. This model provides an abstracted view of the Layer 3 IPVPN service configuration components. It will be up to a management system to take this as an input and use specific configurations models to configure the different network elements to deliver the service. How configuration of network elements is done is out of scope of the document. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-19 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-model-19 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-… internet-drafts