YANG Data Model for L3VPN Service Delivery

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: The IESG <iesg@ietf.org>, draft-wu-l3sm-rfc8049bis@ietf.org, alissa@cooperw.in, aretana.ietf@gmail.com, adrian@olddog.co.uk, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'YANG Data Model for L3VPN Service Delivery' to Proposed Standard (draft-wu-l3sm-rfc8049bis-11.txt)

The IESG has approved the following document:
- 'YANG Data Model for L3VPN Service Delivery'
  (draft-wu-l3sm-rfc8049bis-11.txt) as Proposed Standard

This document has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG contact person is Alissa Cooper.

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 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.

  If approved, this document obsoletes RFC 8049.  The changes are a
  series of small fixes to the YANG module, and some clarifications to
  the text.

Working Group Summary

  RFC 8049 was the product of the L3SM working group, but that WG has been closed.
  No other WG covers this topic.
  However, the L3SM list remains open: changes and revisions were publicised and discussed there.
  Although some of the discussion involved firmly stated opinions, there was nothing approaching controversy.
  Consensus should be checked through the normal IETF last call process.

Document Quality

  Implementation work on RFC 8049 gave rise to this revision.
  The shepherd knows of two independent efforts to implement.
  Reviews by David Ball and Jan Lindblad have been particularly thorough.
  A YANG Doctor review of the latest revision has NOT been performed at the time of publication request,
    but Jan Lindblad is a YANG Doctor and his review of RFC 8049 was contributory to this work.


  Adrian Farrel <adrian@olddog.co.uk> is the Document Shepherd
  Alissa Cooper is the Responsible Area Director