YANG Data Model for L3VPN Service Delivery
RFC 8049

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: l3sm@ietf.org, l3sm-chairs@ietf.org, draft-ietf-l3sm-l3vpn-service-model@ietf.org, "Qin Wu" <bill.wu@huawei.com>, bclaise@cisco.com, "The IESG" <iesg@ietf.org>, bill.wu@huawei.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'YANG Data Model for L3VPN service delivery' to Proposed Standard (draft-ietf-l3sm-l3vpn-service-model-19.txt)

The IESG has approved the following document:
- 'YANG Data Model for L3VPN service delivery'
  (draft-ietf-l3sm-l3vpn-service-model-19.txt) as Proposed Standard

This document is the product of the L3VPN Service Model  Working Group.

The IESG contact persons are Benoit Claise and Joel Jaeggli.

A URL of this Internet Draft is:

Technical Summary

   This document defines a YANG data model that can be used for communication 
   between customers and network operators, and to provide input to automated 
   control and configuration applications used to deliver a Layer 3 Provider 
   Provisioned VPN service.  The document is limited to the BGP PE-based VPNs 
   as described in 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.

Working Group Summary

   Consensus was complete in the working group after one and half year of development.
  A first WGLC was largely silent reflecting (the chairs believe) satisfaction with previous discussions.
  But after solicitation, a number of people from network operators responded that they considered
  the document ready. A few last-minute questions were received and handled.

Document Quality

   The shepherd is aware of a proof-of-concept implementation based on an earlier version of the document.
This document is ready to ship,


   Qin Wu is the Document Shepherd.
   Benoit Claise is the responsible Area Director.

RFC Editor Note

An editor note (which throws a compilation warning):

revision 2016-11-03 {
"Initial document";

revision 2016-11-04 {
"Initial document";