Last Call: <draft-ietf-l3sm-l3vpn-service-model-16.txt> (YANG Data Model for L3VPN service delivery) to Proposed Standard

The IESG <> Tue, 27 September 2016 15:45 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 84F0912B253; Tue, 27 Sep 2016 08:45:29 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-l3sm-l3vpn-service-model-16.txt> (YANG Data Model for L3VPN service delivery) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 27 Sep 2016 08:45:29 -0700
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 Sep 2016 15:45:29 -0000

The IESG has received a request from the L3VPN Service Model  WG (l3sm)
to consider the following document:
- 'YANG Data Model for L3VPN service delivery'
  <draft-ietf-l3sm-l3vpn-service-model-16.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-10-11. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc4026: Provider Provisioned Virtual Private Network (VPN) Terminology (Informational - IETF stream)
Note that some of these references may already be listed in the acceptable Downref Registry.