Internet Engineering Task Force
OPSAWG                                                         A. Aguado
Internet-Draft                                                     Nokia
Intended status: Standards Track                O. Gonzalez de Dios, Ed.
Expires: April May 20, 2020                                           V. Lopez
                                                              Telefonica
                                                                D. Voyer
                                                             Bell Canada
                                                                L. Munoz
                                                                Vodafone
                                                        October 18,
                                                       November 17, 2019

                    A Layer 3 VPN Network YANG Model
                     draft-ietf-opsawg-l3sm-l3nm-00
                     draft-ietf-opsawg-l3sm-l3nm-01

Abstract

   RFC8299 defines a L3VPN Service YANG data Model (L3SM) that can be
   used for communication between customers and network operators.  Such VPN service providers.
   That data model is adequate for the customer to network operator conversation
   and plays the role of a Customer Service Model, according
   to the terminology defined in RFC8309. RFC8309, and is as such adequate for
   service negotiation and order handling matters.

   There is a need for a more network-centric YANG data model to be used
   in the communication between the entity that interacts directly with
   the customer, the service orchestrator, (either fully automated or a
   human operator) and the entity in charge of network orchestration and
   control (aka (a.k.a., network controller / orchestrator). controller/orchestrator).

   This document proposes specifies a L3VPN Network Yang YANG Model (L3NM) to
   facilitate communication between a service orchestrator and a network
   controller / orchestrator.  The resulting
   controller/orchestrator.  Such data model is called the L3VPN
   Network Model (L3NM) and provides a network-centric
   view of the L3VPN services.  The Yang model proposed is limited to
   BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364.

Editorial Note (To be removed by RFC Editor)

   Please update these statements within the document with the RFC
   number to be assigned to this document:

   o  "This version of this YANG module is part of RFC XXXX;"

   o  "RFC XXXX: Layer 3 VPN Network Model";

   o  reference: RFC XXXX

   Also, please update the "revision" date of the YANG module.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April May 20, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  INTRODUCTION  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  TERMINOLOGY  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3   4
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3   5
   2.  REFERENCE ARCHITECTURE  Reference Architecture  . . . . . . . . . . . . . . . . . . .   4   6
   3.  Description of the L3NM YANG MODEL EXPLANATION Module . . . . . . . . . . . . .   8
     3.1.  Structure of the Module . . . . . .   6
     3.1.  STRUCTURE OF THE MODEL . . . . . . . . . . .   9
     3.2.  Modeling a L3 VPN Service . . . . . .   7
     3.2.  SITE AND BEARERS . . . . . . . . . .   9
       3.2.1.  VPN node  . . . . . . . . . .   7
     3.3.  BEARER AND ETHERNET ENCAPSULATION . . . . . . . . . . . .   7
     3.4.  MULTI-DOMAIN RESOURCE MANAGEMENT  10
         3.2.1.1.  VPN Network Access  . . . . . . . . . . . .   7
     3.5.  REMOTE FAR-END CONFIGURATION . . .  11
           3.2.1.1.1.  Connection  . . . . . . . . . . .   8
     3.6.  PROVIDE EDGE IDENTIFICATION POINT . . . . . .  11
           3.2.1.1.2.  IP Connection . . . . . .   8
   4.  DESING OF THE DATA MODEL . . . . . . . . . .  13
           3.2.1.1.3.  Routing Protocols . . . . . . . .   9
   5.  YANG MODULE . . . . . .  14
       3.2.2.  Concept of Import/Export Profiles . . . . . . . . . .  15
       3.2.3.  Multicast . . . . . . . . .  20
   6.  IANA CONSIDERATIONS . . . . . . . . . . . . .  16

     3.3.  VPN profiles  . . . . . . . .  93
   7.  SECURITY CONSIDERATIONS . . . . . . . . . . . . . .  16
     3.4.  Model tree  . . . . .  93
   8.  IMPLEMENTATION STATUS . . . . . . . . . . . . . . . . . .  17
   4.  Use of the Data Model . .  93
   9.  ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . .  23
     4.1.  Multi-Domain Resource Management  . . . .  94
   10. CONTRIBUTORS . . . . . . . .  23
   5.  Relation with other Yang Models . . . . . . . . . . . . . . .  23
     5.1.  Relation with L3SM  .  94
   11. References . . . . . . . . . . . . . . . . . .  23
     5.2.  Relation with Network Topology  . . . . . . .  94
     11.1.  NORMATIVE REFERENCES . . . . . .  24
     5.3.  Relation with Device Models . . . . . . . . . . . .  94
     11.2.  INFORMATIVE REFERENCES . . .  24
   6.  L3VPN  Examples . . . . . . . . . . . . . .  94
   Authors' Addresses . . . . . . . . .  24
     6.1.  4G VPN Provissioning Example  . . . . . . . . . . . . . .  95

1.  INTRODUCTION

   [RFC8299] defines a L3VPN Service YANG data Model (L3SM) model that
   can be used for communication between customers and network
   operators.  Such model is focused on describing the customer view of
   the services, and provides an abstracted view of the customer's
   requested services.  That aproach limits the usage of the L3SM to the
   role of a Customer Service Model, according to the terminology
   defined in [RFC8309].

   The YANG data model proposed in this document is called the L3VPN
   Network Model (L3NM).  The L3NM model is aimed at providing a
   network-centric view of L3 VPN Services.  The model can be used to
   facilitate communication between the service orchestrator, and the
   network controller / orchestrator.  It enables further capabilities,
   such as resource management or to serve as a multi-domain
   orchestration interface, where transport resources must be
   synchronized.  The YANG module has been built with a prune and extend
   approach, taking as a starting points the YANG model described in
   [RFC8299].

   Hence, this document does not obsolete, but complements, the
   definitions in [RFC8299].  It aims to provide a different scope for
   the L3SM, but does not attempt to address all deployment cases
   especially those where the L3VPN connectivity is supported through
   the coordination of different VPNs in different underlying networks.
   More complex deployment scenarios involving the coordination of
   different VPN instances and different technologies to provide end-to-
   end VPN connectivity are addressed by a complementary YANG model
   defined in [I-D.evenwu-opsawg-yang-composed-vpn].

1.1.  TERMINOLOGY

   This document assumes that the reader is familiar with the contents
   of [RFC6241], [RFC7950], [RFC8299], [RFC8309], and [RFC8453] and uses
   terminology from those documents.  Tree diagrams used in this
   document follow the notation defined in [RFC8340].

1.2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  REFERENCE ARCHITECTURE

   Figure 1 shows where the L3NM is used in a management stack.  The
   figure is an expansion of the architecture presented in Section 5 of
   [RFC8299] and decomposes the box marked "orchestration" in that
   figure into three separate functional components called "Service
   Orchestration", "Network Orchestration", and "Domain Orchestration".

   Note that some implementations may choose to construct a monolithic
   orchestration component, but this document assumes that there are
   many benefits for flexiblity of implementation and deployment to
   separate the functional components, and that separation demands the
   existence of sepearate  24
   7.  Yang Module . . . . . . . . . . . . . . . . . . . . . . . . .  26
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  89
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  90
   10. Implementation Status . . . . . . . . . . . . . . . . . . . .  91
     10.1.  Nokia Implementation . . . . . . . . . . . . . . . . . .  91
     10.2.  Huawei Implementation  . . . . . . . . . . . . . . . . .  92
     10.3.  Infinera Implementation  . . . . . . . . . . . . . . . .  96
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  96
   12. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  96
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  97
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  97
     13.2.  Informative References . . . . . . . . . . . . . . . . .  98
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  99

1.  Introduction

   [RFC8299] defines an L3VPN Service YANG models to data Model (L3SM) that can be
   used for communication between the components.

   At the same time, terminology from [RFC8309] is introduced to show
   the distinction between the "Customer Service Model", the "Service
   Delivery Model", the "Network Configuration Model", and the "Device
   Configuration Model".  In that context, the "Domain Orchestration"
   and "Config Manager" roles may be performed by "Controllers".

                                       +---------------+
                                     |   Customer    |
                                     +---------------+
                     Customer Service Model  |
                            l3vpn-svc        |
                                     +---------------+
                                     |    Service    |
                                     | Orchestration |
                                     +---------------+
                   Service Delivery Model    |
                           l3nm-svc          |
                    (l3vpn-svc + extensions) |
                                     +---------------+
                                     |   Network     |
                                     | Orchestration |
                                     +---------------+
               Network Configuration Model  |
                                  __________|____________
                                 |                       |
                        +---------------+       +---------------+
                        |    Domain     |       |     Domain    |
                        | Orchestration |       | Orchestration |
                        +---------------+       +---------------+
             Device         |        |                   |
             Configuration  |        |                   |
             Model          |        |                   |
                       +---------+   |                   |
                       | Config  |   |                   |
                       | Manager |   |                   |
                       +---------+   |                   |
                            |        |                   |
                            | NETCONF/CLI..................
                            |        |                   |
                     +------------------------------------------------+
                                         Network

                          Figure 1: L3SM and L3NM

   The L3SM customers and L3NM may also be set in network operators.  Such
   model is focused on describing the context customer view of the ACTN
   architecture [RFC8453].  Figure 2 shows the Customer Network
   Controller (CNC), the Multi-Domain Service Coordinator (MDSC), VPN services,
   and provides an abstracted view of the Provisioning Network Controller (PNC).  It also shows the
   interfaces between these functional units: customer's requested services.
   That aproach limits the CNC-MDSC Interface
   (CMI), usage of the MDSC-PNC Interface (MPI), and L3SM module to the Southbound Interface
   (SBI).

                  ----------------------------------
                  | role of a
   Customer                         |
                  |  -----------------------------   |
                  | |             CNC             |  |
                  |  -----------------------------   |
                   ----:-----------------------:-----
                       :                       :
                       : L3SM                  : L3SM
                       :                       :
              ---------:---------     -------------------
             | MDSC    :         |   |       MDSC        |
             |  ---------------  |   |     (parent)      |
             | | Service    | |    -------------------
             | | Orchestration | |             :
             |  ---------------  |             : L3NM
             |         :         |             :
             |         : L3NM    |    -------------------
             |         :         |   |       MDSC        |
             |  ---------------  |   |      (child)      |
             | |    Network    | |    -------------------
             | | Orchestration | |             :
             |  ---------------  |             :
              ---------:---------              :
                       :                       :
                       : Network Configuration :
                       :                       :
           ------------:-------       ---------:------------
          | Domain     :       |     |         : Domain     |
          | Controller :       |     |         : Controller |
          |        ---------   |     |     ---------        |
          |       |   PNC   |  |     |    |   PNC   |       |
          |        ---------   |     |     ---------        |
           ------------:-------       ---------:------------
                       :                       :
                       : Device Configuration  :
                       :                       :
                   --------                --------
                  | Device |              | Device |
                   --------                --------

              Figure 2: L3SM and L3NM in Model, according to the Context of ACTN

3.  YANG MODEL EXPLANATION terminology defined in
   [RFC8309].

   The scenarios covered YANG data model defined in the this document is called L3VPN Network
   Model (L3NM).  The L3NM module is aimed at providing a network-
   centric view of L3 VPN Services.  The data model includes: can be used to
   facilitate communication between the integration of
   Ethernet service orchestrator (or a
   network operator) and encapsulation parameters, the extension network controller/orchestrator by allowing
   for transport more network-centric information to be included.  It enables
   further capabilities, such as resource management or to serve as a
   multi-domain orchestration interface, where logical resources (e.g., Route (such
   as route targets and Route or route distinguishers) to must be
   orchestrated from the management system, far-end configuration of PEs synchronized.

   This document does not managed by the management system and obsolete, but uses, the definition definitions in
   [RFC8299].  These two modules are used for PE
   identification.

3.1.  STRUCTURE OF THE MODEL similar objectives but
   with differents scopes and views.

   The L3NM YANG module is divided into three main containers: "vpn-
   services","sites" initially built with a prune and "vpn-profiles".

3.2.  SITE AND BEARERS

   A site, extend
   approach, taking as per [RFC8299], represents a connection of a customer
   office to one or more VPN services.  As this YANG module, is starting points the
   network view, each site YANG module described in
   [RFC8299].  Nevertheless, this module is associated with not defined as an augment to
   L3SM because a list of bearers.  A
   bearer specific structure is required to meet network-
   oriented L3 needs.

   Some of the layer two connections with information captured in the site.  In L3SM can be passed by the module it
   is assumed that
   Orchestrator in the bearer has been allocated by L3NM (e.g., customer) or be used to fed some of
   the Service Provider L3NM attribute (e.g., by actual forwarding policies).  Some of the service orchestrator).  The bearer
   information captured in L3SM may be maintained locally within the
   Orchestrator; which is associated supposed to maintain a
   network element and a port.  Hence, "glue" between a bearer is
   Customer view and its network instantiation.

   The L3NM module does not just a bearer-
   reference, but also a true reference attempt to a given port in address all deployment cases
   especially those where the service
   provider network.

3.3.  BEARER AND ETHERNET ENCAPSULATION

   The definition of a L3VPN connectivity is commonly specified not only at supported through
   the IP
   layer, but also requires to identify parameters at coordination of different VPNs in different underlying networks.
   More complex deployment scenarios involving the Ethernet
   layer, such as encapsulation type (e.g., VLAN, QinQ, QinAny, VxLAN,
   etc.).  This specification is not supported coordination of
   different VPN instances and different technologies to provide end-to-
   end VPN connectivity are addressed by a complementary YANG model
   defined in [RFC8299], whilst it
   suggests [I-D.evenwu-opsawg-yang-composed-vpn].

1.1.  Terminology

   This document assumes that any extension on this direction shall be implemented
   via augmentation of the bearer container.  The extension defined to
   cope reader is familiar with these parameters uses the connection container inside contents
   of [RFC6241], [RFC7950], [RFC8299], [RFC8309], and [RFC8453] and uses
   the
   site-network-access terminology defined by in those documents.

   The meaning of the [RFC8466].  This container defines
   protocol parameters to enable connectivity symbols in tree diagrams is defined in in
   [RFC8340].

   The document is aimed at Layer 2.  In modeling BGP PE-based VPNs in a Service
   Provider Network, so the
   context terms defined in [RFC4026] and [RFC4076] are
   used.

   This document makes use of L3SM, the augmentation includes only mandatory parameters
   for the service configuration, which are mainly related to following terms:

   o  L3 VPN Customer Service Model (L3SM): Describes the
   interface encapsulation.  Other definitions requirements
      of a L3 VPN that interconnects a set of sites from L2SM connection
   container are left aside.  For example, Link Aggregation (LAG)
   information is not required and it shall be configured prior to the
   service configuration, being the aggregated interface identified in point of
      view of the customer.  The customer service model as does not provide
      details on the bearer-reference, as discussed later in Section 3.4.

3.4.  MULTI-DOMAIN RESOURCE MANAGEMENT Service Provider Network.  The implementation of L3VPN services which span across
   administratively separated domains (i.e., L3 VPN Customer
      Service model is defined in [RFC8299].

   o  L3 VPN Service Network Model (L3NM): A YANG module that are under describes
      a VPN Service in the
   administration Service Provider Network.  It containts
      information of different management systems or controllers)
   requires some the Service Provider network resources to be synchronized between systems.
   Particularly, there are two resources that must be orchestrated and
   manage to avoid asymmetric (non-functional) configuration, or the
   usage of unavailable might include
      allocated resources.  For example, RTs shall  It can be
   synchronized between PEs.  When every PE is controlled used by network controllers to
      manage and control the same
   management system, RT allocation VPN Service configuration in the Service
      Provider network.  The YANG module can be performed consumed by a Service
      Orchestrator to request a VPN Service to a Network controller.

   o  Service Orchestrator: A functional entity that interacts with the system.  In
   cases where
      customer of a L3 VPN.  The Service Orchestrator interacts with the service spans across multiple management systems,
   this task
      customer using L3SM.  The Service Orchestrator is responsible of allocating RTs has to be aligned across
      the domains,
   therefore, CE-PE attachment circuits, the PE selection, and requesting
      the VPN service model must provide a way to specify RTs.  In
   addition, RDs must also be synchronized to avoid collisions in RD
   allocation between separate systems.  An incorrect allocation might
   lead to the same RD and IP prefixes being exported by different PE
   routers.

3.5.  REMOTE FAR-END CONFIGURATION

   Depending on the control plane implementation, different network
   scenarios might require additional information controller.

   o  Network Controller: A functional entity responsible for the L3VPN
      control and management of the service provider network.

   o  VPN node (vpn-node): An abstraction that represents a set of
      policies applied to be configured a PE and active.  For example, an L3VPN Option C service,
   if no reflection of IPv4 that belong to a single VPN routes is configured via ASBR service
      (vpn-service).  A vpn-service involves one or route
   reflector, may require additional configuration (e.g. a new BGP
   neighbor) more vpn-nodes.  As
      it is an abstraction, the network controller will take on how to be coordinated between both management systems.  This
   definition requires for every management system participant
      implement a vpn-node.  For example, typically, in a BGP-based VPN,
      a vpn-node could be mapped into a VRF.

   o  VPN network access (vpn-network-access): An abstraction that
      represents the network interfaces that are associated to a given
      vpn-node.  Traffic coming from the
   VPN vpn-network-access belongs to receive not just their own sites
      the VPN.  The attachment circuits (bearers) between CEs and site-network-accesses,
   but also PEs
      are terminated in the vpn-network-access.  A reference to receive information about external ones, identified as an
   external site-network-access-type.  In addition, this particular
   site-network-access the
      bearer is augmented maintained to include the loopback address of allow keeping the far-end (remote/external) PE router.

3.6.  PROVIDE EDGE IDENTIFICATION POINT

   [RFC8299] states link between L3SM and
      L3NM.

   o  VPN Site (vpn-site): A VPN customer's location that the "bearer-reference" parameter is used in
   cases where connected
      to the customer has already ordered Service Provider network via a CE-PE link, which can access
      at least one VPN [RFC4176].

   o  VPN Service Provider (SP): A Service Provider offers VPN-related
      services [RFC4176].

   o  Service Provider (SP) Network: A network connection able to
   the service provider (SP) apart from the IP VPN site provide VPN-
      related services.

1.2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and wants to
   reuse
   "OPTIONAL" in this connection. document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Reference Architecture

   Figure 1 depices the reference architecture for L3NM.  The string used figure is
   an internal reference from expansion of the SP architecture presented in Section 5 of [RFC8299]
   and describes the already-available connection.  Usually, a
   client interface (either a customer one or an interface used by decomposes the
   SP) is already box marked "orchestration" in place that figure into
   three separate functional components called "Service Orchestration",
   "Network Orchestration", and connected, although it has not being use
   previously.  In "Domain Orchestration".

   Although some other cases (e.g., deployments may choose to construct a monolithic
   orchestration component (covering both service and network matters),
   this document advocates for a clear separation between service and
   network orchestration components for stitching purposes), the
   termination sake of better flexibility.
   Such design adheres to the L3VPN reference architecture defined in
   Section 1.3 of a VPN service is done over logical terminations within
   a PE router. [RFC4176].  The bearer-reference must serve as above separation relies upon a strict unequivocal parameters to
   identify the connection
   dediciated communication interface between a PE these components and a client (CE).  This means
   that, despite the type
   appropriate YANG module that reflect network-related information
   (that is maintained as a string and there hidden to customers).

   The intelligence for translating customer-facing information into
   network-centric one is no
   restriction in the way this data implementation-specific.

   The terminology from [RFC8309] is formed, the bearer-reference must
   serve as the unique way introduced to identify show the PE router and distinction
   between the client
   interface.  This, together with "Customer Service Model", the encapsulation augments proposed
   in Section 3.2, serves as "Service Delivery Model",
   the way to identify "Network Configuration Model", and the client interface "Device Configuration
   Model".  In that context, the "Domain Orchestration" and configure L2 specific parameters.

4.  DESING OF THE DATA MODEL "Config
   Manager" roles may be performed by "Controllers".

                                     +---------------+
                                     |   Customer    |
                                     +---------------+
                     Customer Service Model  |
                            l3vpn-svc        |
                                     +---------------+
                                     |    Service    |
                                     | Orchestration |
                                     +---------------+
                       L3NM Network Model    |
                          l3vpn-ntw          |
                                     +---------------+
                                     |   Network     |
                                     | Orchestration |
                                     +---------------+
               Network Configuration Model  |
                                  __________|____________
                                 |                       |
                        +---------------+       +---------------+
                        |    Domain     |       |     Domain    |
                        | Orchestration |       | Orchestration |
                        +---------------+       +---------------+
             Device         |        |                   |
             Configuration  |        |                   |
             Model          |        |                   |
                       +---------+   |                   |
                       | Config  |   |                   |
                       | Manager |   |                   |
                       +---------+   |                   |
                            |        |                   |
                            | NETCONF/CLI..................
                            |        |                   |
                     +------------------------------------------------+
                                         Network

                          Figure 1: L3SM and L3NM

   The augmentations defined in this document are organised per
   scenario, as defined L3SM and L3NM modules may also be set in Section 3.  The case described Section 3.4
   does not need any further extension the context of the data model ACTN
   architecture [RFC8453].  Figure 2 shows the Customer Network
   Controller (CNC), the Multi-Domain Service Coordinator (MDSC), and only
   requires a more restricted definition on how
   the data model is used
   for PE router Provisioning Network Controller (PNC).  It also shows the
   interfaces between these functional blocks: the CNC-MDSC Interface
   (CMI), the MDSC-PNC Interface (MPI), and client port identification, so no augmentation is
   implemented for this scenario.

   The augmentations implemented are distributed as follows:

   o  An extension including RT the Southbound Interface
   (SBI).

                  +----------------------------------+
                  | Customer                         |
                  | +-----------------------------+  |
                  | |             CNC             |  |
                  | +-----------------------------+  |
                  +----:-----------------------:-----+
                       :                       :
                       : L3SM                  : L3SM
                       :                       :
             +---------:---------+   +-------------------+
             | MDSC    :         |   |       MDSC        |
             | +---------------+ |   |     (parent)      |
             | |    Service    | |   +-------------------+
             | | Orchestration | |             :
             | +---------------+ |             : L3NM
             |         :         |             :
             |         : L3NM    |   +-------------------+
             |         :         |   |       MDSC        |
             | +---------------+ |   |      (child)      |
             | |    Network    | |   +-------------------+
             | | Orchestration | |             :
             | +---------------+ |             :
              ---------:---------              :
                       :                       :
                       : Network Configuration :
                       :                       :
          +------------:-------+     +---------:------------+
          | Domain     :       |     |         : Domain     |
          | Controller :       |     |         : Controller |
          |       +---------+  |     |    +---------+       |
          |       |   PNC   |  |     |    |   PNC   |       |
          |       +---------+  |     |    +---------+       |
          +------------:-------+     +---------:------------+
                       :                       :
                       : Device Configuration  :
                       :                       :
                  +--------+              +--------+
                  | Device |              | Device |
                  +--------+              +--------+

              Figure 2: L3SM and RD definition for L3NM in the L3VPN,
      following Context of ACTN

3.  Description of the L3NM YANG definitions from BESS-L3VPN.  This extension
      was developed creating Module

   The L3NM module ('ietf-l3vpn-ntw') is meant to manage L3 VPNs in a container "ie-profiles" under the VPN
      Service.  All
   service provider network.  In particular, the import-export information 'ietf-l3vpn-ntw' module
   can be created and
      reused for several VPN-Nodes.

      *  If the "ie-profile" is empty the domain controller should
         automatically assing RD used to create, modify, and RTs.  This is not valid for retrieve L3VPN Services of a
         multi-domain scenario

   o  The second augmentation copes with
   network.

3.1.  Structure of the information from a remote
      PE not directly under management system supervision.  This
      augmentation does not follow any previously defined model Module

   The 'ietf-l3vpn-ntw' module uses two main containers: 'vpn-services'
   and
      includes 'vpn-profiles' (see Figure 3).  The 'vpn-services' container
   maintains the loopback IP address set of VPN Services managed in the external router.

   o service provider
   network.  The third augmentation copes with a pseudowire termination under module allows to create a new VPN service.  This termination requires the management service by adding a
   new instance of 'vpn-service'.  The 'vpn-service' is the
      Virtual Circuit Identifier under data
   structure that abstracts the VPN service.

   o  Access-group-id has been added within Service.

   The 'vpn-profiles' container allows the site network access in
      order provider to allow associations between interfaces maintain a set of
   commmon VPN profiles that have similar
      behaviors.  For example, identify two interfaces in dual homing
      distribution.

   o  The last augmentation includes information below layer apply to several VPN Services.

       module: ietf-l3vpn-ntw
       +--rw l3vpn-ntw
        +--rw vpn-profiles
        |     .......
        +--rw vpn-services
            +--rw vpn-service* [vpn-id]
              ........

                                 Figure 3

3.2.  Modeling a L3 VPN Service

   The 'vpn-service' is the data structure that abstracts a VPN Service
   in the Service Provider Network.  Every 'vpn-service' has a unique
   identifier: vpn-id.  Such vpn-id is
      required for only meaningful locally within
   the service. Network controller.  In particular, we include information
      related order to clients interface encapsulation facilitate the recognition of
   the service, a 'customer-name' and aggregation. a 'description' may be included.
   The high-level model structure defined topology of the VPN service is expressed in the 'vpn-service-
   topology' leaf.

   A VPN Service is built by adding instances of 'vpn-node' to the 'vpn-
   nodes' container.  The 'vpn-node' is an abstractions that represent a
   set of policies applied to a network node and that belong to a single
   'vpn-service'.  A 'vpn-node' contains 'vpn_network_accesses', which
   are the interfaces involved in the creation of the VPN.  The customer
   sites are connected to the 'vpn_network_accesses'.  Note that, as
   this document is as shown
   below:

            |-------------------- EXAMPLE --------------------|

          module: ietf-l3vpn-ntw
            +--rw l3vpn-ntw
               +--rw vpn-profiles
               |  +--rw valid-provider-identifiers
               |     +--rw cloud-identifier* [id] {cloud-access}?
               |     |  +--rw id    string
               |     +--rw encryption-profile-identifier* [id]
               |     |  +--rw id    string
               |     +--rw qos-profile-identifier* [id]
               |     |  +--rw id    string
               |     +--rw bfd-profile-identifier* [id]
               |     |  +--rw id    string
               |     +--rw routing-profile-identifier* [id]
               |        +--rw id    string
               +--rw vpn-services
               | a network data model, the information about customers site is
   not needed.  Such information, is relevant in the L3SM model.

        +--rw vpn-service* [vpn-id]
               |
              +--rw vpn-id                  svc-id
               |
              +--rw customer-name?          string
               |
              +--rw vpn-service-topology?   identityref
               |
              +--rw description?            string
               |
              +--rw ie-profiles
              |     |  +--rw ie-profile* [ie-profile-id]
               |     |     +--rw ie-profile-id    string
               |     |     +--rw rd?              rt-types:route-distinguisher
               |     |     +--rw vpn-targets
               |     |        +--rw vpn-target* [route-target]
               |     |           +--rw route-target         rt-types:route-target
               |     |           +--rw route-target-type    rt-types:route-target-type
               |  ...
              +--rw vpn-nodes
              |     |   ...
              +--rw multicast

                                 Figure 4

3.2.1.  VPN node

   The 'vpn-node' is an abstraction that represents a set of common
   policies applied in a given network node (tipcally a PE) and belong
   to one L3 VPN Service.  In order to indicate the network node where
   the 'vpn-node' applies the the ne-id MUST be facilitated.  The 'vpn-
   node' includes a parameter to indicate in which network node it is
   applied.  In the case that the ne-id points to a specific PE, the
   vpn_node will likely be mapped into a vrf in the node.  However, the
   model also allows to point to an abstract node.  In this case, the
   network controller will decide how to split the vpn_node into vrfs.
   For the cases the logical resources are managed outside the network
   controller, the model allows to explicitely indicate the logical
   resources such as Route targets and Route distinguishers (RT,RD).

   Under the VPN Node container, VPN Network Acesses can be created.
   The VPN Network Acess represents the point to which sites are
   connected.  Note that, unlike in L3SM, the L3NM does not need to
   model the customer site, only the points where the traffic from the
   site are received.  Hence, the VPN Network access contains the
   connectivity information between the provider's Network and the
   customer premises.  The VPN profiles have a set of routing policies
   than can be applied during the service creation.

       +--rw vpn-node* [vpn-node-id ne-id]
               |     |
        +--rw vpn-node-id             string
               |     |
        +--rw description?            string
               |     |
        +--rw ne-id                   string
               |     |
        +--rw router-id?              inet:ip-address
               |     |
        +--rw address-family?    address-family
               |     | address-family?         address-family
        +--rw node-role?              identityref
        +--rw rd?                     rt-types:route-distinguisher
        +--rw vpn-targets
            ....
        +--rw vpn-network-accesses
            ....

                                 Figure 5

3.2.1.1.  VPN Network Access

   A 'vpn-network-access' represents an entry point to a VPN service.
   In other words, this container encloses the parameters that describe
   the access information for the traffic that belongs to a particular
   L3 VPN.  As such, every vpn-network-access belongs to one and only
   one vpn-node.  As an example, a vpn-network-access includes
   information such as the connection on which the access is defined
   (see the section below), the encapsulation of the traffic, policies
   that are applied on the access, etc.

   A provisioning network controller (PNC) [RFC8453] will accept VPN
   requests containing this construct, using the enclosed data to:
   configure the router's interface to include the parameters described
   at the vpn-network-access, include the given interface into a VRF,
   configuring policies or schedulers for the incoming traffic, etc.

3.2.1.1.1.  Connection

   The definition of a L3VPN is commonly specified not only at the IP
   layer, but also requires to identify parameters at the Ethernet
   layer, such as encapsulation type (e.g., VLAN, QinQ, QinAny, VxLAN,
   etc.).  The 'connection' container represents and groups the set of
   L2 connectivity from where the traffic of the L3VPN in a particular
   VPN Network access is coming.

   Additionally, the bearer-reference (Section 3.2.1.1.1.3) and the
   pseudowire termination (Section 3.2.1.1.1.2) is supported.

3.2.1.1.1.1.  Encapsulation options

   Ethernet encapsulation description is not supported in [RFC8299].
   However, this parameters are mandatory to configure the PE
   interfaces.  Thus, In the L3NM, these parameters uses the connection
   container inside the vpn-network-access.  This container defines
   protocols and parameters to enable connectivity at Layer 2.

                     +--rw connection
                       +--rw node-role? encapsulation-type?   identityref
               |     |     +--rw rd?                rt-types:route-distinguisher
               |     |     +--rw vpn-targets
               |     |     |  +--rw vpn-target* [route-target]
               |     |     |     +--rw route-target         rt-types:route-target
               |     |     |     +--rw route-target-type    rt-types:route-target-type
               |     |     +--rw status
               |     |     |  +--rw admin-enabled?   boolean
               |     |     |  +--ro oper-status?     operational-type
               |     |     +--rw maximum-routes
               |     |     |  +--rw address-family* [af]
               |     |     |     +--rw af                address-family
               |     |     |     +--rw maximum-routes?   uint32
               |     |     +--rw node-ie-profile?   -> /l3vpn-ntw/vpn-services/vpn-service/ie-profiles/ie-profile/ie-profile-id
               |     +--rw cloud-accesses {cloud-access}?
               |     |  +--rw cloud-access* [cloud-identifier]
               |     |     +--rw cloud-identifier       -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/cloud-identifier/id
               |     |     +--rw (list-flavor)?
               |     |     |  +--:(permit-any)
               |     |     |  |  +--rw permit-any?      empty
               |     |     |  +--:(deny-any-except)
               |     |     |  |  +--rw permit-site*     -> /l3vpn-ntw/sites/site/site-id
               |     |     |  +--:(permit-any-except)
               |     |     |     +--rw deny-site*       -> /l3vpn-ntw/sites/site/site-id
               |     |     +--rw address-translation
               |     |        +--rw nat44
               |     |           +--rw enabled?                  boolean
               |     |           +--rw nat44-customer-address?   inet:ipv4-address
               |     +--rw multicast {multicast}?
               |     |  +--rw enabled?                 boolean
               |     |
                         +--rw customer-tree-flavors
               |     |  | tagged-interface
                            +--rw tree-flavor* type?                identityref
               |     |  +--rw rp
               |     |
                            +--rw rp-group-mappings
               |     | dot1q-vlan-tagged {dot1q}?
                            |  +--rw rp-group-mapping* [id]
               |     | tag-type?   identityref
                            |  +--rw id cvlan-id?   uint16
               |     |     |
                            +--rw provider-managed
               |     |     |     |  +--rw enabled?                    boolean
               |     |     |     |  +--rw rp-redundancy?              boolean
               |     |     |     |  +--rw optimal-traffic-delivery?   boolean
               |     |     |     +--rw rp-address          inet:ip-address
               |     |     |     +--rw groups
               |     |     |        +--rw group* [id]
               |     |     |           +--rw id                     uint16
               |     | priority-tagged
                            |  +--rw (group-format)
               |     |     |              +--:(singleaddress)
               |     |     |              | tag-type?   identityref
                            +--rw group-address?   inet:ip-address
               | qinq {qinq}?
                            |  +--rw tag-type?   identityref
                            |              +--:(startend)  +--rw svlan-id    uint16
                            |  +--rw cvlan-id    uint16
                            +--rw qinany {qinany}?
                            |  +--rw tag-type?   identityref
                            |  +--rw group-start? svlan-id    uint16
                            +--rw vxlan {vxlan}?
                               +--rw vni-id       uint32
                               +--rw peer-mode?   identityref
                               +--rw peer-list* [peer-ip]
                                  +--rw peer-ip    inet:ip-address
               |     |     |

                                 Figure 6

3.2.1.1.1.2.  Remote Far End Configuration

   Depending on the control plane implementation, different network
   scenarios might require additional information for the L3VPN service
   to be configured and active.  For example, an L3VPN Option C service,
   if no reflection of IPv4 VPN routes is configured via ASBR or route
   reflector, may require additional configuration (e.g. a new BGP
   neighbor) to be coordinated between both management systems.  This
   definition requires for every management system participant in the
   VPN to receive not just their own sites and site-network-accesses,
   but also to receive information about external ones, identified as an
   external site-network-access-type.  In addition, this particular
   site-network-access is augmented to include the loopback address of
   the far-end (remote/external) PE router.

                       +--rw bearer
                         +--rw connection
                           ...
                           +--rw pseudowire
                            +--rw vcid?   uint32

                                 Figure 7

3.2.1.1.1.3.  Bearers

   A site, as per [RFC4176] represents a VPN customer's location that is
   connected to the Service Provider network via a CE-PE link, which can
   access at least one VPN.  The connection from the site to the Service
   Provider network is the bearer.  Every site is associated with a list
   of bearers.  A bearer is the layer two connections with the site.  In
   the module it is assumed that the bearer has been allocated by the
   Service Provider at the service orchestration step.  The bearer is
   associated to a network element and a port.  Hence, a bearer is just
   a bearer-reference to allow the translation between L3SM and L3NM.

3.2.1.1.2.  IP Connection

   IP Connection container has the parameters of the vpn-network-access
   addressing information.  The address allocated in this container
   would represent the PE interface address configuration.  The IP
   Connection container is designed to support dual stack (IPv4/IPv6)
   and three options to set the ip address: Provider DHCP, DHCP relay or
   static addressing.

   In the case of the static addressing the model supports the
   assignation of several IP addresses in the same vpn-network-access.
   To identify which of the addresses is the primary address of the
   connection the "primary-address" reference must be set with the
   corresponding address-id.

                 +--rw group-end?       inet:ip-address
               |     | ip-connection
                   +--rw rp-discovery
               |     | ipv4 {ipv4}?
                     +--rw rp-discovery-type? address-allocation-type?   identityref
               |     |
                       +--rw bsr-candidates
               |     | provider-dhcp
                         ...
                       +--rw bsr-candidate-address*   inet:ip-address
               | dhcp-relay
                         ...
                       +--rw carrierscarrier?        boolean {carrierscarrier}?
               | static-addresses
                         +--rw extranet-vpns {extranet-vpn}?
               | primary-address?   leafref
                       +--rw extranet-vpn* [vpn-id]
               | address* [address-id]
                         ...
                   +--rw vpn-id              svc-id
               | ipv6 {ipv6}?
                     +--rw local-sites-role? address-allocation-type?   identityref
                       +--rw sites
                  +--rw site* [site-id]
                     +--rw site-id                  svc-id
                     +--rw description?             string
                     +--rw requested-site-start?    yang:date-and-time
                     +--rw requested-site-stop?     yang:date-and-time
                     +--rw locations
                     |  +--rw location* [location-id]
                     |     +--rw location-id     svc-id
                     |     +--rw address?        string
                     |     +--rw postal-code?    string
                     |     +--rw state?          string
                     |     +--rw city?           string
                     |     +--rw country-code?   string
                     +--rw devices
                     |  +--rw device* [device-id]
                     | provider-dhcp
                         ...
                       +--rw device-id     svc-id
                     | dhcp-relay
                         ...
                       +--rw location      -> ../../../locations/location/location-id
                     | static-addresses
                         +--rw management
                     | primary-address?  leafref
                         +--rw address-family? address* [address-id]
                             ...

                                 Figure 8

3.2.1.1.3.  Routing Protocols

   The model allows the Network Operator to configure one or more
   routing protocols associated with a particular vpn-network-access.
   This protocol will run between the PE and the CE.  A routing protocol
   instance MUST have a type (e.g. bgp, ospf, etc.) and an identifier.
   The identifier is necessary when multiple instances of the same
   protocol need to be configured.

   The model uses an abstracted view of routing protocols.  When
   configuring multiple instances of the same protocol, this does not
   automatically imply that, from a device configuration perspective,
   there will be parallel instances (multiple processes) running.  It
   will be up to the implementation to use the most appropriate
   deployment model.  As an example, when multiple BGP peers need to be
   implemented, multiple instances of BGP must be configured as part of
   this model.  However from a device configuration point of view, this
   could be implemented as:

   o  Multiple BGP processes with a single neighbor running in each
      process.

   o  A single BGP process with multiple neighbors running.

   o  A combination of both.

   To be aligned with [RFC8299], this model supports the following
   protocols:

   o  vrrp: takes only a list of address-family
                     |        +--rw address           inet:ip-address
                     +--rw site-diversity {site-diversity}?
                     |  +--rw groups
                     |     +--rw group* [group-id]
                     |        +--rw group-id    string
                     +--rw management
                     |  +--rw as parameter.  VRRP
      instance is expected to run on the vpn-network-access interface.

   o  rip: takes only a list of address-family as parameter.  RIP
      instance is expected to run on the vpn-network-access interface.

   o  static: allows user to configure one or more IPv4 and IPv6 static
      routes.

   o  bgp: allows the user to configure a BGP neighbor including
      parameters like authentication using a key.  The authentication
      type will be driven by the implementation but the model supports
      any authentication that uses a key as a parameter.  A BGP neighbor
      can support ipv4, ipv6, or both address-families.  Again, it is up
      to the implementation to drive the device configuration (e.g.
      separate BGP sessions for Dual Stack, single session for Dual
      Stack, etc.).

   o  ospf: allows the user to configure OSPF to run on the vpn-network-
      access interface.  An OSPF instance can run ipv4, ipv6 or both.
      When only ipv4 address-family is requested, it will be up to the
      implementation to drive if OSPFv2 or v3 is used.

   Routing protocol configuration do not have any routing policy
   configuration.  Routing policies are low level device configurations
   that must not be part of an abstracted model.  Service Provider
   internal policies (such as security filters) will be implemented as
   part of the device configuration but does not require any input from
   this model.  Some policies like primary/backup, load-balancing can be
   inferred from access-priority.

3.2.2.  Concept of Import/Export Profiles

   The import and export profiles construct contains a list with
   information related with route target and distinguishers (RTs and
   RDs), grouped and identified by ie-profile-id.  The identifier is
   then referenced in one or multiple vpn-nodes, so the PNC can identify
   RTs and RDs to be configured in the VRF.

3.2.3.  Multicast

   Multicast can be optionally enabled for a particular vpn-network-
   access.

   The model supports a single type    identityref
                     +--rw site-vpn-flavor?         identityref
                     +--rw maximum-routes
                     |  +--rw address-family* [af]
                     |     +--rw af                address-family
                     |     +--rw maximum-routes?   uint32
                     +--rw security
                     | of tree (ASM, SSM or bidirectional).

   When ASM is used, the model supports configuration of rendez-vous
   points.  RP discovery could be static, bsr-rp or auto-rp.  When
   static is used RP to multicast grouping mapping must be configured as
   part of the rp-group-mappings container.  The RP may be a provider
   node or a customer node.  When the RP is a customer node, the RP
   address must be configured using the rp-address leaf otherwise no RP
   address is needed.  The model supports RP redundancy through the rp-
   redundancy leaf.  How the redundancy is achieved is out of scope and
   is up to the implementation.  When a particular VPN using ASM
   requires a more optimal traffic delivery, the leaf optimal-traffic-
   delivery can be used.  When set to true, the implementation must use
   any mechanism to provide a more optimal traffic delivery for the
   customer.  As an example, the implementation can use RP tree to
   Shortest Path tree switchover or simply deploy additional RPs working
   in an anycast mode.

3.3.  VPN profiles

   The vpn-profiles containers allow the network operator to maintain a
   set of commmon VPN Profiles that apply to several VPN Services.
   Through this container these common profiles can be created, modified
   and deleted.

   +--rw authentication vpn-profiles
    |  +--rw encryption {encryption}?
                     | valid-provider-identifiers
    |     +--rw enabled?   boolean
                     | cloud-identifier* [id] {cloud-access}?
    |  +--rw layer?     enumeration     |  +--rw encryption-profile id    string
    |     +--rw (profile)? encryption-profile-identifier* [id]
    |     |  +--:(provider-profile)  +--rw id    string
    |     +--rw qos-profile-identifier* [id]
    |     |  +--rw profile-name?    -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/encryption-profile-identifier/id
                     | id    string
    |  +--:(customer-profile)     +--rw bfd-profile-identifier* [id]
    |     |  +--rw algorithm? id    string
    |     +--rw (key-type)?
                     |        +--:(psk) routing-profile-identifier* [id]
    |        +--rw preshared-key? id    string

                                 Figure 9

3.4.  Model tree

   The high-level model structure defined by this document is as shown
   below:

   module: ietf-l3vpn-ntw
   +--rw service
                     | l3vpn-ntw
    +--rw qos {qos}?
                     | vpn-profiles
    |  +--rw qos-classification-policy
                     |  | valid-provider-identifiers
    |     +--rw rule* cloud-identifier* [id]
                     | {cloud-access}?
    |     |  +--rw id    string
    |  |  |     +--rw (match-type)?
                     |  |  | encryption-profile-identifier* [id]
    |  +--:(match-flow)     |  +--rw id    string
    |     +--rw qos-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw match-flow bfd-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw routing-profile-identifier* [id]
    |        +--rw id    string
    +--rw vpn-services
     +--rw vpn-service* [vpn-id]
        +--rw vpn-id                  svc-id
        +--rw customer-name?          string
        +--rw vpn-service-topology?   identityref
        +--rw description?            string
        +--rw ie-profiles
        |  +--rw dscp?                inet:dscp ie-profile* [ie-profile-id]
        |     +--rw ie-profile-id    string
        |     +--rw rd?
        |     |       rt-types:route-distinguisher
        |     +--rw dot1p?               uint8 vpn-targets
        |        +--rw vpn-target* [route-target]
        |           +--rw route-target
        |           |       rt-types:route-target
        |           +--rw ipv4-src-prefix?     inet:ipv4-prefix
                     |  | route-target-type
        |                   rt-types:route-target-type
        +--rw vpn-nodes
        |  +--rw vpn-node* [vpn-node-id ne-id]
        |     +--rw ipv6-src-prefix?     inet:ipv6-prefix vpn-node-id             string
        |     +--rw autonomous-system?      uint32
        |     +--rw description?            string
        |     +--rw ne-id                   string
        |     +--rw router-id?              inet:ip-address
        |     +--rw ipv4-dst-prefix?     inet:ipv4-prefix address-family?         address-family
        |     +--rw node-role?              identityref
        |     +--rw rd?
        |     |       rt-types:route-distinguisher
        |     +--rw ipv6-dst-prefix?     inet:ipv6-prefix
                     | vpn-targets
        |     |  +--rw vpn-target* [route-target]
        |     |     +--rw l4-src-port?         inet:port-number route-target
        |     |     |       rt-types:route-target
        |     |     +--rw target-sites*        svc-id {target-sites}? route-target-type
        |     |             rt-types:route-target-type
        |     +--rw status
        |     |  +--rw l4-src-port-range
                     | admin-enabled?   boolean
        |     |  +--ro oper-status?     operational-type
        |     +--rw vpn-network-accesses
        |     |  +--rw lower-port?   inet:port-number vpn-network-access*
        |     |          [vpn-network-access-id]
        |     |     +--rw vpn-network-access-id      svc-id
        |     |     +--rw upper-port?   inet:port-number description?               string
        |     |     +--rw status
        |     |     |  +--rw l4-dst-port?         inet:port-number admin-enabled?   boolean
        |     |     |  +--ro oper-status?     operational-type
        |     |     +--rw l4-dst-port-range
                     | vpn-network-access-type?
        |     |     |       identityref
        |     |     +--rw lower-port?   inet:port-number connection
        |     |     |  +--rw encapsulation-type?   identityref
        |     |     |  +--rw upper-port?   inet:port-number
                     | tagged-interface
        |     |     |  |  +--rw protocol-field?      union
                     |  |  | type?
        |  +--:(match-application)     |     |  |  |     +--rw match-application?       identityref
        |     |     |     +--rw target-class-id?           string
                     |  |  +--rw qos-profile
                     |  |  +--rw (qos-profile)?
                     |  |        +--:(standard)
                     | dot1q-vlan-tagged {dot1q}?
        |     |  +--rw profile?     -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/qos-profile-identifier/id     |  |  |  +--rw direction? tag-type?   identityref
        |     |        +--:(custom)     |  |           +--rw classes {qos-custom}?
                     |  |              +--rw class* [class-id]
                     |  |  +--rw class-id      string cvlan-id?   uint16
        |     |                 +--rw direction?    identityref     |  |  +--rw rate-limit?   decimal64 priority-tagged
        |     |                 +--rw latency     |  |  |  +--rw (flavor)?
                     |  |                 |     +--:(lowest) tag-type?   identityref
        |     |     |  |  +--rw use-lowest-latency?   empty
                     | qinq {qinq}?
        |     |     +--:(boundary)     |  |  |  +--rw latency-boundary?     uint16 tag-type?   identityref
        |     |                 +--rw jitter     |  |  |  +--rw (flavor)?
                     |  | svlan-id    uint16
        |     +--:(lowest)     |     |  |  |  +--rw use-lowest-jitter?   empty
                     |  | cvlan-id    uint16
        |     +--:(boundary)     |     |  |  +--rw latency-boundary?    uint32 qinany {qinany}?
        |     |     |                 +--rw bandwidth  |  |  +--rw guaranteed-bw-percent    decimal64 tag-type?   identityref
        |     |                    +--rw end-to-end?              empty     |  +--rw carrierscarrier {carrierscarrier}?  |  |  +--rw signalling-type?   enumeration svlan-id    uint16
        |     |  +--rw multicast {multicast}?     |     +--rw multicast-site-type?        enumeration  |  +--rw multicast-address-family vxlan {vxlan}?
        |     |  +--rw ipv4?   boolean {ipv4}?     |  |     +--rw ipv6?   boolean {ipv6}? vni-id       uint32
        |     +--rw protocol-type?              enumeration
                     +--rw traffic-protection {fast-reroute}?     |  +--rw enabled?   boolean
                     +--rw routing-protocols     |  +--rw routing-protocol* [type]  |     +--rw type peer-mode?   identityref
        |     +--rw routing-profiles* [id]
                     |     |  +--rw id      -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id     |     |  +--rw type?   ie-type  |     +--rw ospf {rtg-ospf}? peer-list* [peer-ip]
        |     |  +--rw address-family*   address-family     |  |        +--rw area-address      yang:dotted-quad peer-ip
        |     |  +--rw metric?           uint16     |  |  +--rw mtu?              uint16                inet:ip-address
        |     |     |  +--rw security bearer
        |     |     |     +--rw auth-key? bearer-reference?   string
        |     |  +--rw sham-links {rtg-ospf-sham-link}?
                     |     |     +--rw sham-link* [target-site]     |       {bearer-reference}?
        |        +--rw target-site    svc-id     |     |     +--rw metric?        uint16 pseudowire
        |     +--rw bgp {rtg-bgp}?     |     |        +--rw autonomous-system vcid?   uint32
        |     |     +--rw address-family*      address-family
                     | ip-connection
        |  +--rw neighbor?            inet:ip-address     |     |  +--rw multihop?            uint8 ipv4 {ipv4}?
        |     |  +--rw security     |  |  +--rw auth-key?   string address-allocation-type?
        |     +--rw static     |     |  +--rw cascaded-lan-prefixes  |  |     +--rw ipv4-lan-prefixes* [lan next-hop] {ipv4}?       identityref
        |     |     |  +--rw lan         inet:ipv4-prefix  |  +--rw provider-dhcp
        |     |  +--rw lan-tag?    string     |  |  |  +--rw next-hop    inet:ipv4-address provider-address?
        |     |     +--rw ipv6-lan-prefixes* [lan next-hop] {ipv6}?     |  |        +--rw lan         inet:ipv6-prefix  |  |        +--rw lan-tag?    string       inet:ipv4-address
        |     |        +--rw next-hop    inet:ipv6-address     |     +--rw rip {rtg-rip}?  |  |  +--rw address-family*   address-family prefix-length?
        |     +--rw vrrp {rtg-vrrp}?     |        +--rw address-family*   address-family
                     +--ro actual-site-start?       yang:date-and-time
                     +--ro actual-site-stop?        yang:date-and-time
                     +--rw site-bearers     |  +--rw bearer* [bearer-id]  |     +--rw bearer-id     string  |     +--rw BearerType?   identityref  |     +--rw ne-id?        string       uint8
        |     |     +--rw port-id?      string     |     +--rw lag-id?       string
                     +--rw site-network-accesses
                        +--rw site-network-access* [site-network-access-id]
                           +--rw site-network-access-id      svc-id
                           +--rw description?                string
                           +--rw status  |  +--rw admin-enabled?   boolean  |  +--ro oper-status?     operational-type
                           +--rw site-network-access-type?   identityref  +--rw (location-flavor) (address-assign)?
        |  +--:(location)     |     |  +--rw location-reference?   -> ../../../locations/location/location-id  |  +--:(device)  |     +--rw device-reference?     -> ../../../devices/device/device-id
                           +--rw access-diversity {site-diversity}?     +--:(number)
        |  +--rw groups     |     |  +--rw group* [group-id]  |  |     +--rw group-id    string     |  +--rw constraints number-of-dynamic-address?
        |     +--rw constraint* [constraint-type]     |        +--rw constraint-type    identityref     |        +--rw target  |           +--rw (target-flavor)?  |              +--:(id)     |          uint16
        |  +--rw group* [group-id]     |     |     +--rw group-id    string  |              +--:(all-accesses)  |     +--:(explicit)
        |     |  +--rw all-other-accesses?   empty     |              +--:(all-groups)  |                 +--rw all-other-groups?     empty
                           +--rw bearer  |        +--rw requested-type {requested-type}? customer-addresses
        |     |  +--rw requested-type?   string     |  |  +--rw strict?           boolean  |           +--rw always-on?          boolean {always-on}? address-group*
        |  +--rw bearer-reference?   string {bearer-reference}?     |  +--rw connection     |  |  +--rw encapsulation-type?   identityref  |                   [group-id]
        |  +--rw tagged-interface     |     |     +--rw type?                identityref  |  |              +--rw dot1q-vlan-tagged {dot1q}? group-id
        |     |     |  +--rw tag-type?   identityref  |  |              |  +--rw cvlan-id?   uint16       string
        |     |     +--rw priority-tagged     |  |  |              +--rw tag-type?   identityref start-address?
        |     |     +--rw qinq {qinq}?     |  |  |  +--rw tag-type?   identityref              |       inet:ipv4-address
        |     |  +--rw svlan-id    uint16     |  |  |              +--rw cvlan-id    uint16
                           | end-address?
        |     +--rw qinany {qinany}?     |     |  |  +--rw tag-type?   identityref  |                      inet:ipv4-address
        |     |  +--rw svlan-id    uint16     |  |  +--rw vxlan {vxlan}? dhcp-relay
        |     |     |        +--rw vni-id       uint32  |  |  +--rw peer-mode?   identityref provider-address?
        |     |        +--rw peer-list* [peer-ip]     |  |           +--rw peer-ip    inet:ip-address  |  +--rw pseudowire  |     +--rw vcid?   uint32
                           +--rw ip-connection       inet:ipv4-address
        |  +--rw ipv4 {ipv4}?     |     |  +--rw address-allocation-type?   identityref  |  |  +--rw provider-dhcp prefix-length?
        |     |     |  +--rw provider-address?                  inet:ipv4-address  |  |  |  +--rw prefix-length?       uint8
        |     |     |  +--rw (address-assign)?  |  |  +--rw customer-dhcp-servers
        |     +--:(number)     |     |  |  |     +--rw number-of-dynamic-address?   uint16 server-ip-address*
        |     |     |     +--:(explicit)  |  |             inet:ipv4-address
        |        +--rw customer-addresses     |     |  |  +--rw address-group* [group-id] static-addresses
        |     |     |  |     +--rw group-id         string primary-address?   leafref
        |     |     |  |     +--rw start-address?   inet:ipv4-address address* [address-id]
        |     |     |  |        +--rw end-address?     inet:ipv4-address address-id
        |     |     |  +--rw dhcp-relay  |        |       string
        |     |     |  |        +--rw provider-address?        inet:ipv4-address
        |     |     |  +--rw prefix-length?           uint8  |        |       inet:ipv4-address
        |  +--rw customer-dhcp-servers     |     |  |        +--rw server-ip-address*   inet:ipv4-address customer-address?
        |     |     |  +--rw addresses  |        |     +--rw provider-address?       inet:ipv4-address
        |     |     +--rw customer-address?   inet:ipv4-address     |  |        +--rw prefix-length?
        |     |     |  |                uint8
        |     |     |  +--rw ipv6 {ipv6}?
        |     |     |  |  +--rw address-allocation-type?
        |     |     |  |  |       identityref
        |     |     |  |  +--rw provider-dhcp
        |     |     |  |  |  +--rw provider-address?
        |     |     |  |  |  |       inet:ipv6-address
        |     |     |  |  |  +--rw prefix-length?
        |     |     |  |  |  |       uint8
        |     |     |  |  |  +--rw (address-assign)?
        |     |     |  |  |     +--:(number)
        |     |     |  |  |     |  +--rw number-of-dynamic-address?
        |     |     |  |  |     |          uint16
        |     |     |  |  |     +--:(explicit)
        |     |     |  |  |        +--rw customer-addresses
        |     |     |  |  |           +--rw address-group*
        |     |     |  |  |                   [group-id]
        |     |     |  |  |              +--rw group-id
        |     |     |  |  |              |       string
        |     |     |  |  |              +--rw start-address?
        |     |     |  |  |              |       inet:ipv6-address
        |     |     |  |  |              +--rw end-address?
        |     |     |  |  |                      inet:ipv6-address
        |     |     |  |  +--rw dhcp-relay
        |     |     |  |  |  +--rw provider-address?
        |     |     |  |  |  |       inet:ipv6-address
        |     |     |  |  |  +--rw prefix-length?
        |     |     |  |  |  |       uint8
        |     |     |  |  |  +--rw customer-dhcp-servers
        |     |     |  |  |     +--rw server-ip-address*   inet:ipv6-address
        |     |  +--rw addresses     |  |     +--rw provider-address?  |             inet:ipv6-address
        |     |     +--rw customer-address?   inet:ipv6-address     |  |  +--rw prefix-length?      uint8 static-addresses
        |     |  +--rw oam     |     +--rw bfd {bfd}?  |     +--rw enabled?              boolean primary-address?   leafref
        |     |     |  |     +--rw (holdtime)? address* [address-id]
        |     |           +--:(fixed)     |  |        +--rw fixed-value?    uint32 address-id
        |           +--:(profile)     |              +--rw profile-name?   -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/bfd-profile-identifier/id
                           +--rw security     |  +--rw authentication  |  +--rw encryption {encryption}?        |       string
        |     |  +--rw enabled?   boolean     |  |        +--rw layer?     enumeration provider-address?
        |  +--rw encryption-profile     |     +--rw (profile)?     |  |  +--:(provider-profile)        |       inet:ipv6-address
        |     |     |  |        +--rw profile-name?    -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/encryption-profile-identifier/id customer-address?
        |     |  +--:(customer-profile)     |  |     +--rw algorithm?       string        |     +--rw (key-type)?       inet:ipv6-address
        |        +--:(psk)     |           +--rw preshared-key?   string
                           +--rw service     |  +--rw svc-input-bandwidth     uint64  |        +--rw svc-output-bandwidth    uint64 prefix-length?
        |  +--rw svc-mtu                 uint16     |  +--rw qos {qos}?     |  |  +--rw qos-classification-policy                uint8
        |     |     |  +--rw rule* [id] oam
        |     |     |     +--rw id                         string bfd {bfd}?
        |     |     |        +--rw (match-type)? enabled?
        |     |     |        |  +--:(match-flow)       boolean
        |     |     |        +--rw (holdtime)?
        |     |  +--rw match-flow     |           +--:(fixed)
        |     |     |           |  +--rw dscp?                inet:dscp fixed-value?
        |     |     |           |          uint32
        |     +--rw dot1p?               uint8     |     |           +--:(profile)
        |     |     |              +--rw ipv4-src-prefix?     inet:ipv4-prefix profile-name?   leafref
        |     |     +--rw security
        |     |     |  +--rw ipv6-src-prefix?     inet:ipv6-prefix authentication
        |     |     |  +--rw encryption {encryption}?
        |     |     |     +--rw ipv4-dst-prefix?     inet:ipv4-prefix  |  +--rw enabled?   boolean
        |     |     |  |  +--rw ipv6-dst-prefix?     inet:ipv6-prefix layer?     enumeration
        |     |     |  +--rw encryption-profile
        |     |     |     +--rw l4-src-port?         inet:port-number (profile)?
        |     |     |     |  +--:(provider-profile)
        |     |     |     |  |  +--rw target-sites*        svc-id {target-sites}? profile-name?    leafref
        |     |     |     |  +--:(customer-profile)
        |     +--rw l4-src-port-range     |     |     |     +--rw algorithm?       string
        |     |     |     +--rw lower-port?   inet:port-number (key-type)?
        |     |     |        +--:(psk)
        |     |     |           +--rw preshared-key?   string
        |     |     +--rw upper-port?   inet:port-number routing-protocols
        |     |        +--rw routing-protocol* [id]
        |     |           +--rw id                  string
        |     |           +--rw l4-dst-port?         inet:port-number type?
        |     |           |       identityref
        |     |           +--rw l4-dst-port-range routing-profiles* [id]
        |     |           |  +--rw id      leafref
        |     |           |  +--rw lower-port?   inet:port-number
                           | type?   ie-type
        |     |           +--rw ospf {rtg-ospf}?
        |     |           |  +--rw upper-port?   inet:port-number address-family*
        |     |           |  |       address-family
        |     |     +--rw protocol-field?      union           |  +--rw area-address
        |     |           |  +--:(match-application)  |       yang:dotted-quad
        |     |           |  +--rw match-application?   identityref metric?           uint16
        |     |           |  +--rw target-class-id?           string mtu?              uint16
        |     |           |  +--rw qos-profile process-id?       uint16
        |     |     +--rw (qos-profile)?           |  +--rw security
        |        +--:(standard)     |           |  |  +--rw profile?     -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/qos-profile-identifier/id auth-key?   string
        |     |           |  +--rw direction?   identityref sham-links
        |     |        +--:(custom)           |          {rtg-ospf-sham-link}?
        |           +--rw classes {qos-custom}?     |           |     +--rw class* [class-id] sham-link* [target-site]
        |     |           |        +--rw class-id      string target-site    svc-id
        |     |           |        +--rw direction?    identityref metric?        uint16
        |     |           +--rw rate-limit?   decimal64 bgp {rtg-bgp}?
        |     |           |  +--rw latency autonomous-system    uint32
        |     |           |  +--rw (flavor)? address-family*
        |     |           |     +--:(lowest)  |       address-family
        |     |           |  +--rw use-lowest-latency?   empty neighbor?
        |     |           |     +--:(boundary)  |       inet:ip-address
        |     |           |  +--rw latency-boundary?     uint16 multihop?            uint8
        |     |           |  +--rw jitter security
        |     |           |     +--rw (flavor)? auth-key?   string
        |     |           +--rw static
        |     +--:(lowest)     |           |  +--rw cascaded-lan-prefixes
        |     |           |     +--rw use-lowest-jitter?   empty ipv4-lan-prefixes*
        |     |           |     +--:(boundary)     |       [lan next-hop] {ipv4}?
        |     |        +--rw latency-boundary?    uint32           |     |  +--rw bandwidth lan
        |     |                    +--rw guaranteed-bw-percent    decimal64           |     |                    +--rw end-to-end?              empty  |  +--rw carrierscarrier {carrierscarrier}?       inet:ipv4-prefix
        |     |  +--rw signalling-type?   enumeration           |  +--rw multicast {multicast}?     |  +--rw multicast-site-type?        enumeration lan-tag?    string
        |     |     +--rw multicast-address-family           |     |  +--rw ipv4?   boolean {ipv4}? next-hop
        |     |           |     |          inet:ipv4-address
        |     |  +--rw ipv6?   boolean {ipv6}?           |     +--rw protocol-type?              enumeration
                           +--rw routing-protocols ipv6-lan-prefixes*
        |     |           |             [lan next-hop] {ipv6}?
        |  +--rw routing-protocol* [type]     |     +--rw type                identityref           |        +--rw routing-profiles* [id] lan
        |     |  +--rw id      -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id           |        |  +--rw type?   ie-type       inet:ipv6-prefix
        |     +--rw ospf {rtg-ospf}?     |           |        +--rw address-family*   address-family lan-tag?    string
        |     |           |        +--rw area-address      yang:dotted-quad next-hop
        |     |  +--rw metric?           uint16           |                inet:ipv6-address
        |     |           +--rw mtu?              uint16 rip {rtg-rip}?
        |     |           |  +--rw security address-family*
        |     |           |  +--rw auth-key?   string          address-family
        |     |           +--rw sham-links {rtg-ospf-sham-link}? vrrp {rtg-vrrp}?
        |     |              +--rw sham-link* [target-site] address-family*
        |     |                      address-family
        |     +--rw target-site    svc-id maximum-routes
        |     |  +--rw metric?        uint16 address-family* [af]
        |     |     +--rw bgp {rtg-bgp}? af                address-family
        |     |     +--rw autonomous-system maximum-routes?   uint32
        |     |     +--rw address-family*      address-family node-ie-profile?        leafref
        +--rw multicast {multicast}?
           +--rw enabled?                 boolean
           +--rw customer-tree-flavors
           |  +--rw tree-flavor*   identityref
           +--rw rp
              +--rw rp-group-mappings
              |  +--rw neighbor?            inet:ip-address rp-group-mapping* [id]
              |     +--rw id                  uint16
              |     +--rw multihop?            uint8 provider-managed
              |     |  +--rw security enabled?
              |     |     +--rw auth-key?   string  |     +--rw static       boolean
              |     |  +--rw cascaded-lan-prefixes rp-redundancy?
              |     |     +--rw ipv4-lan-prefixes* [lan next-hop] {ipv4}?  |       boolean
              |     |  +--rw lan         inet:ipv4-prefix optimal-traffic-delivery?
              |     |          boolean
              |     +--rw lan-tag?    string
                           | rp-address          inet:ip-address
              |     +--rw groups
              |        +--rw next-hop    inet:ipv4-address group* [id]
              |           +--rw id                     uint16
              |           +--rw ipv6-lan-prefixes* [lan next-hop] {ipv6}? (group-format)
              |              +--:(singleaddress)
              |              |  +--rw lan         inet:ipv6-prefix group-address?
              |              |          inet:ip-address
              |              +--:(startend)
              |                 +--rw lan-tag?    string group-start?
              |                 |       inet:ip-address
              |                 +--rw next-hop    inet:ipv6-address group-end?
              |                         inet:ip-address
              +--rw rip {rtg-rip}? rp-discovery
                 +--rw rp-discovery-type?   identityref
                 +--rw bsr-candidates
                    +--rw bsr-candidate-address*
                            inet:ip-address

                                 Figure 10

4.  Use of the Data Model

4.1.  Multi-Domain Resource Management

   The implementation of L3VPN services which span across
   administratively separated domains (i.e., that are under the
   administration of different management systems or controllers)
   requires some network resources to be synchronized between systems.
   Particularly, there are two resources that must be orchestrated and
   manage to avoid asymmetric (non-functional) configuration, or the
   usage of unavailable resources.  For example, RTs shall be
   synchronized between PEs.  When every PE is controlled by the same
   management system, RT allocation can be performed by the system.  In
   cases where the service spans across multiple management systems,
   this task of allocating RTs has to be aligned across the domains,
   therefore, the service model must provide a way to specify RTs.  In
   addition, RDs must also be synchronized to avoid collisions in RD
   allocation between separate systems.  An incorrect allocation might
   lead to the same RD and IP prefixes being exported by different PE
   routers.

5.  Relation with other Yang Models

   The L3NM model, aimed at managing the L3VPN Services in a Service
   Provider Network controller/orchestrator has relations with other
   Yang modules.

5.1.  Relation with L3SM

   [RFC8299] defines a L3VPN Service YANG data Model (L3SM) that can be
   used for communication between customers and VPN service providers.
   Hence, the model provides inputs to the Network Operator to deliver
   such service to the customer.  Hence, some parts of the model can be
   directly mapped into L3NM.

   o  Routing protocols requested by the client at PE-CE interface.  In
      sake of alignment, the same protocols are supported.

5.2.  Relation with Network Topology

   The L3NM model manages VPN Services running over Service Provider
   Backbone network.  The set of nodes over which it is possible to
   deploy a L3 VPN Service MAY be part of the topology contained in an
   ietf-network module.

5.3.  Relation with Device Models

   Creating services in the l3vpn-ntw module will will lead at some
   point to the configuration of devices.  Hence, it is foreseen that
   the data for the device yang modules will be derived partially from
   the L3NM vpn-service container.  Note that L3NM is NOT a device
   model.

6.  L3VPN Examples

6.1.  4G VPN Provissioning Example

   The L3VPN service defined in this draft provides a multipoint, routed
   service to the customer over an IP/MPLS core.  The L3VPNs are widely
   used to deploy 3G/4G, fixed and enterprise services principally due
   to the fact that several traffic discrimination policies can be
   applied in the network to transport and guarantee the right SLAs to
   the mobile customers.

   As it is shown in the Figure 11, commonly the eNODEB (CE) is directly
   connected to the access routers (DCSG) of the mobile backhaul and
   their logical interfaces (one or many according to the Service type)
   are configured in a VPN that transport the packets to the mobile core
   platforms.

                                                        +--------------+
           +------+    +-----+    +-----+    +-----+    |  Platforms   |  +--rw address-family*   address-family
           |eNODEB|--/-|  PE |----|  P  |----|  PE |----|  (SGW/MME)   |     +--rw vrrp {rtg-vrrp}?
           +------+    +-----+    +-----+    +-----+    |        +--rw address-family*   address-family
                           +--rw availability     ...      |  +--rw access-priority?   uint32
                           +--rw node-id?                    -> /l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn-node-id
                           +--rw service-id?                 -> /l3vpn-ntw/vpn-services/vpn-service/vpn-id
                           +--rw access-group-id?            yang:uuid
                                                        +--------------+

                    Figure 3

5.  YANG MODULE

            |-------------------- EXAMPLE --------------------| 11: Mobile Backhaul Example

   To configure a L3VPN service using the L3NM model the procedure and
   the JSON with the data structure is the following:

   Create VPN Service
   <vpn-services>
       <vpn-service>
         <vpn-id>1</vpn-id>
         <customer-name>4G</customer-name>
         <vpn-service-topology>hub-spoke</vpn-service-topology>
         <description>4G</description>
       </vpn-service>
     </vpn-services>
   </l3vpn-ntw>

                       Figure 12: Create VPN Service

   Create VPN Node: For this type of service the VPN Node is equivalent
   with the VRF configured in the physical device.

   <vpn-nodes>
     <vpn-node>
       <vpn-node-id>1</vpn-node-id>
       <ne-id>10.0.0.1</ne-id>
       <autonomous-system>65000</autonomous-system>
       <description>4G</description>
       <router-id>10.0.0.1</router-id>
       <address-family>ipv4</address-family>
       <node-role>any-to-any-role</node-role>
       <rd>1:1</rd>
     </vpn-node>
   </vpn-nodes>

                        Figure 13: Create VPN Node

   Create VPN Network Access

 <vpn-network-accesses>
 <vpn-network-access>
   <vpn-network-access-id>1/1/1</vpn-network-access-id>
   <description>4G</description>
   <status>
     <admin-enabled>true</admin-enabled>
   </status>
   <vpn-network-access-type>point-to-point</vpn-network-access-type>
   <ip-connection>
     <ipv4>
       <address-allocation-type>static-address</address-allocation-type>
       <static-addresses>
         <primary-address>1</primary-address>
         <address>
           <address-id>1</address-id>
           <provider-address>192.168.0.1</provider-address>
           <customer-address>192.168.0.2</customer-address>
           <prefix-length>30</prefix-length>
         </address>
       </static-addresses>
     </ipv4>
   </ip-connection>
   <routing-protocols>
     <routing-protocol>
       <id>1</id>
       <type>direct</type>
     </routing-protocol>
   </routing-protocols>
 </vpn-network-access>
 </vpn-network-accesses>

                   Figure 14: Create VPN Network Access

7.  Yang Module

 <CODE BEGINS>file "ietf-l3vpn-ntw@2019-09-13.YANG" BEGINS> file "ietf-l3vpn-ntw@2019-11-17.yang"
 module ietf-l3vpn-ntw {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw";
  prefix l3vpn-ntw;
  import ietf-inet-types {
   prefix inet;
  }
  import ietf-yang-types {
   prefix yang;
  }
  import ietf-netconf-acm {
   prefix nacm;
  }
  import ietf-routing-types {
     prefix rt-types;
  }
  organization
  "Individual draft";
    "IETF OPSA (Operations and Management Area) Working Group ";
  contact
  "Currently discussed in
    "WG Web:   <http://tools.ietf.org/wg/opsawg/>
        WG List:  <mailto:opsawg@ietf.org>
        Editor:    Oscar Gonzalez de Dios
    <mailto:oscar.gonzalezdedios@telefonica.com>";
                  <mailto:oscar.gonzalezdedios@telefonica.com>
        Editor:    Alejandro Aguado
                  <mailto:alejandro.aguado_martin@nokia.com>
        Editor:    Victor Lopez
                  <mailto:victor.lopezalvarez@telefonica.com>
        Editor:    Daniel Voyer
                  <mailto:daniel.voyer@bell.ca>
        Editor:    Luis Angel Munoz
                  <mailto:luis-angel.munoz@vodafone.com>
    ";

    description
    "This YANG module defines a generic network-oriented model
    for the configuration management of Layer 3 VPNs. VPNs in a Service Provider
    backbone network.
    Copyright (c) 2019 IETF Trust and the persons identified as
    authors of the code.  All rights reserved.

    Redistribution and use in source and binary forms, with or
    without modification, is permitted pursuant to, and subject to
    the license terms contained in, the Simplified BSD License set
    forth in Section 4.c of the IETF Trust's Legal Provisions
    Relating to IETF Documents
    (https://trustee.ietf.org/license-info).

    This version of this YANG module is part of RFC XXXX
    (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
    for full legal notices.

    The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
    NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
    'MAY', and 'OPTIONAL' in this document are to be interpreted as
    described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
    they appear in all capitals, as shown here.";

    revision 2019-09-24 2019-11-17 {
     description
     "Network centric hierarchy. Customer unused parameters prunned.
     Site removal";
     reference
       "draft-ietf-opsawg-l3sm-l3nm-01";
     }

  revision 2019-09-13 {
   description
   "Initial document. The document as a whole is based on L3SM
   module, defined in RFC 8299, modified to fit the requirements
   of the platforms at the network layer.";
   reference
     "RFC 8049.";
   }
  /* Features */
  feature cloud-access {
   description
   "Allows the VPN to connect to a CSP.";
   }
  feature multicast {
   description
   "Enables multicast capabilities in a VPN.";
  }
  feature ipv4 {
   description
   "Enables IPv4 support in a VPN.";
  }
  feature ipv6 {
   description
   "Enables IPv6 support in a VPN.";
  }
  feature lan-tag {
   description
   "Enables LAN Tag support in a VPN Policy filter.";
  }
  feature carrierscarrier {
   description
   "Enables support of CsC.";
  }
  feature extranet-vpn {
   description
   "Enables support of extranet VPNs.";
  }
  feature site-diversity {
  description
  "Enables support of site diversity constraints.";
 }
 feature encryption {
   description
   "Enables support of encryption.";
  }
  feature qos {
   description
   "Enables support of classes of services.";
  }
  feature qos-custom {
   description
   "Enables support of the custom QoS profile.";
  }
  feature rtg-bgp {
   description
   "Enables support of the BGP routing protocol.";
  }
  feature rtg-rip {
   description
   "Enables support of the RIP routing protocol.";
  }
  feature rtg-ospf {
   description
   "Enables support of the OSPF routing protocol.";
  }
  feature rtg-ospf-sham-link {
   description
   "Enables support of OSPF sham links.";
  }
  feature rtg-vrrp {
   description
   "Enables support of the VRRP routing protocol.";
  }
  feature fast-reroute {
   description
   "Enables support of Fast Reroute.";
  }
  feature bfd {
   description
   "Enables support of BFD.";
  }
  feature always-on {
  description
  "Enables support of the 'always-on' access constraint.";
 }
 feature requested-type {
  description
  "Enables support of the 'requested-type' access constraint.";
 }
 feature bearer-reference {
   description
   "Enables support of the 'bearer-reference' access constraint.";
  }
  feature target-sites {
   description
   "Enables support of the 'target-sites' match flow parameter.";
  }
 feature input-bw {
   description
   "Enables support of the 'input-bw' limit.";
  }
 feature dot1q  {
   description
   "Enables support of the 'dot1q' encapsulation.";
  }
 feature qinq  {
   description
   "Enables support of the 'qinq' encapsulation.";
  }
 feature qinany  {
   description
   "Enables support of the 'qinany' encapsulation.";
  }
  feature vxlan  {
   description
   "Enables support of the 'vxlan' encapsulation.";
  }

  /* Typedefs */
  typedef svc-id {
   type string;
   description
   "Defines a type of service component identifier.";
  }
  typedef template-id {
   type string;
   description
   "Defines a type of service template identifier.";
  }
  typedef address-family {
   type enumeration {
    enum ipv4 {
     description
     "IPv4 address family.";
    }
    enum ipv6 {
     description
     "IPv6 address family.";
    }
    enum ipv4/ipv6 {
     description
     "IPv4/IPv6 address family.";
    }
   }
   description
   "Defines a type for the address family.";
  }

   typedef ie-type {
    type enumeration {
      enum "import" {
        value 0;
        description "Import routing profile.";
      }
      enum "export" {
       value 1;
       description "Export routing profile";
      }
      enum "both" {
       value 2;
       description "Import/Export routing profile";
      }
    }
   description
   "Defines Import-Export routing profiles.
   Those are able to be reused between vpn-nodes";
   }

   typedef operational-type {
    type enumeration {
      enum "up" {
        value 0;
        description "Operational status UP.";
      }
      enum "down" {
       value 1;
       description "Operational status DOWN";
      }
      enum "unknown" {
       value 2;
       description "Operational status UNKNOWN";
      }
    }
    description
   "This is a read-only attribute used to determine the
   status of a particular element";
  }

 /* Identities */
 identity site-network-access-type {
  description
  "Base identity for site-network-access type.";

 }
 identity point-to-point {
  base site-network-access-type;
  description
  "Identity for point-to-point connection.";
 }
 /* Extension */
 identity pseudowire {
  base site-network-access-type;
  description
  "Identity for pseudowire connection.";
 }
 /* End of Extension */
 identity multipoint {
  base site-network-access-type;
  description
  "Identity for multipoint connection.
  Example: Ethernet broadcast segment.";
 }
 identity placement-diversity {
  description
  "Base identity for site placement constraints.";
 }
 identity bearer-diverse {
  base placement-diversity;
  description
  "Identity for bearer diversity.
  The bearers should not use common elements."; a particular element";
   }

  /* Identities */
  identity pe-diverse site-network-access-type {
  base placement-diversity;
   description
  "Identity for PE diversity.";
 }
   "Base identity pop-diverse {
  base placement-diversity;
  description
  "Identity for POP diversity."; site-network-access type.";
  }
  identity linecard-diverse point-to-point {
   base placement-diversity; site-network-access-type;
   description
   "Identity for linecard diversity."; point-to-point connection.";
  }
  /* Extension */
  identity same-pe pseudowire {
   base placement-diversity; site-network-access-type;
   description
   "Identity for having sites connected on the same PE."; pseudowire connection.";
  }
  /* End of Extension */
  identity same-bearer multipoint {
   base placement-diversity; site-network-access-type;
   description
   "Identity for having sites connected using the same bearer."; multipoint connection.
   Example: Ethernet broadcast segment.";
  }
  identity customer-application {
   description
   "Base identity for customer application.";
  }
  identity web {
   base customer-application;
   description
   "Identity for Web application (e.g., HTTP, HTTPS).";
  }
  identity mail {
   base customer-application;
   description
   "Identity for mail application.";
  }
  identity file-transfer {
   base customer-application;
   description
   "Identity for file transfer application (e.g., FTP, SFTP).";
  }
  identity database {
   base customer-application;
   description
   "Identity for database application.";
  }
  identity social {
   base customer-application;
   description
   "Identity for social-network application.";
  }
  identity games {
   base customer-application;
   description
   "Identity for gaming application.";
  }
  identity p2p {
   base customer-application;
   description
   "Identity for peer-to-peer application.";
  }
  identity network-management {
   base customer-application;
   description
   "Identity for management application
   (e.g., Telnet, syslog, SNMP).";
  }
  identity voice {
   base customer-application;
   description
   "Identity for voice application.";
  }
  identity video {
   base customer-application;
   description
   "Identity for video conference application.";
  }
  identity embb {
   base customer-application;
   description
   "Identity for an enhanced Mobile Broadband (eMBB)
   application.  Note that an eMBB application demands
   network performance with a wide variety of
   characteristics, such as data rate, latency,
   loss rate, reliability, and many other parameters.";
 }
 identity urllc {
   base customer-application;
   description
   "Identity for an Ultra-Reliable and Low Latency
  Communications (URLLC) application.  Note that a
  URLLC application demands network performance
  with a wide variety of characteristics, such as latency,
  reliability, and many other parameters.";
 }
 identity mmtc {
   base customer-application;
   description
   "Identity for a massive Machine Type
   Communications (mMTC) application.  Note that an
   mMTC application demands network performance
   with a wide variety of characteristics, such as data
   rate, latency, loss rate, reliability, and many
   other parameters.";
 }
 identity site-vpn-flavor {
  description
  "Base identity for the site VPN service flavor.";
 }
 identity site-vpn-flavor-single {
  base site-vpn-flavor;
  description
  "Base identity for the site VPN service flavor.
  Used when the site belongs to only one VPN.";
 }
 identity site-vpn-flavor-multi {
  base site-vpn-flavor;
  description
  "Base identity for the site VPN service flavor.
  Used when a logical connection of a site
  belongs to multiple VPNs.";
 }
 identity site-vpn-flavor-sub {
  base site-vpn-flavor;
  description
  "Base identity for the site VPN service flavor.
  Used when a site has multiple logical connections.
  Each connection may belong to different multiple VPNs.";
 }
 identity site-vpn-flavor-nni {
  base site-vpn-flavor;
  description
  "Base identity for the site VPN service flavor.
  Used to describe an NNI option A connection.";
 }
 identity management {
  description
  "Base identity for site management scheme.";
 }
 identity co-managed {
  base management;
  description
  "Base identity for co-managed site.";
 }
 identity customer-managed {
  base management;
  description
  "Base identity for customer-managed site."; an Ultra-Reliable and Low Latency
   Communications (URLLC) application.  Note that a
   URLLC application demands network performance
   with a wide variety of characteristics, such as latency,
   reliability, and many other parameters.";
  }
  identity provider-managed mmtc {
    base management; customer-application;
    description
  "Base identity
    "Identity for provider-managed site."; a massive Machine Type
    Communications (mMTC) application.  Note that an
    mMTC application demands network performance
    with a wide variety of characteristics, such as data
    rate, latency, loss rate, reliability, and many
    other parameters.";
  }
  identity address-allocation-type {
   description
   "Base identity for address-allocation-type for PE-CE link.";
  }
  identity provider-dhcp {
   base address-allocation-type;
   description
   "Provider network provides DHCP service to customer.";
  }
  identity provider-dhcp-relay {
   base address-allocation-type;
   description
   "Provider network provides DHCP relay service to customer.";
  }
  identity provider-dhcp-slaac {
   base address-allocation-type;
   description
   "Provider network provides DHCP service to customer,
   as well as SLAAC.";
  }
  identity static-address {
   base address-allocation-type;
   description
   "Provider-to-customer addressing is static.";
  }
  identity slaac {
   base address-allocation-type;
   description
   "Use IPv6 SLAAC.";
  }
  identity site-role {
   description
   "Base identity for site type.";
  }
  identity any-to-any-role {
   base site-role;
   description
   "Site in an any-to-any IP VPN.";
  }
  identity spoke-role {
   base site-role;
   description
   "Spoke site in a Hub-and-Spoke IP VPN.";
  }
  identity hub-role {
   base site-role;
   description
   "Hub site in a Hub-and-Spoke IP VPN.";

  }
  identity vpn-topology {
   description
   "Base identity for VPN topology.";
  }
  identity any-to-any {
   base vpn-topology;
   description
   "Identity for any-to-any VPN topology.";
  }
  identity hub-spoke {
   base vpn-topology;
   description
   "Identity for Hub-and-Spoke VPN topology.";
  }
  identity hub-spoke-disjoint {
   base vpn-topology;
   description
   "Identity for Hub-and-Spoke VPN topology
   where Hubs cannot communicate with each other.";
  }
  identity multicast-tree-type {
   description
   "Base identity for multicast tree type.";
  }
  identity ssm-tree-type {
   base multicast-tree-type;
   description
   "Identity for SSM tree type.";
  }
  identity asm-tree-type {
   base multicast-tree-type;
   description
   "Identity for ASM tree type.";
  }
  identity bidir-tree-type {
   base multicast-tree-type;
   description
   "Identity for bidirectional tree type.";
  }
  identity multicast-rp-discovery-type {
   description
   "Base identity for RP discovery type.";
  }
  identity auto-rp {
   base multicast-rp-discovery-type;
   description
   "Base identity for Auto-RP discovery type.";

  }
  identity static-rp {
   base multicast-rp-discovery-type;
   description
   "Base identity for static type.";
  }
  identity bsr-rp {
   base multicast-rp-discovery-type;
   description
   "Base identity for BSR discovery type.";
  }
  identity routing-protocol-type {
   description
   "Base identity for routing protocol type.";
  }
  identity ospf {
   base routing-protocol-type;
   description
   "Identity for OSPF protocol type.";
  }
  identity bgp {
   base routing-protocol-type;
   description
   "Identity for BGP protocol type.";
  }
  identity static {
   base routing-protocol-type;
   description
   "Identity for static routing protocol type.";
  }
  identity rip {
   base routing-protocol-type;
   description
   "Identity for RIP protocol type.";
  }
  identity vrrp {
   base routing-protocol-type;
   description
   "Identity for VRRP protocol type.
   This is to be used when LANs are directly connected
   to PE routers.";
  }
  identity direct {
   base routing-protocol-type;
   description
   "Identity for direct protocol type.";
  }
  identity protocol-type {
   description
   "Base identity for protocol field type.";
  }
  identity tcp {
   base protocol-type;
   description
   "TCP protocol type.";
  }
  identity udp {
   base protocol-type;
   description
   "UDP protocol type.";
  }

  identity icmp {
   base protocol-type;
   description
   "ICMP protocol type.";
  }
  identity icmp6 {
   base protocol-type;
   description
   "ICMPv6 protocol type.";
  }
  identity gre {
   base protocol-type;
   description
   "GRE protocol type.";
  }
  identity ipip {
   base protocol-type;
   description
   "IP-in-IP protocol type.";
  }
  identity hop-by-hop {
   base protocol-type;
   description
   "Hop-by-Hop IPv6 header type.";
  }
  identity routing {
   base protocol-type;
   description
   "Routing IPv6 header type.";
  }
  identity esp {
   base protocol-type;
   description
   "ESP header type.";

  }
  identity ah {
   base protocol-type;
   description
   "AH header type.";
  }
  identity vpn-policy-filter-type {
   description
   "Base identity for VPN Policy filter type.";
  }
  identity ipv4 {
    base vpn-policy-filter-type;
    description
    "Identity for IPv4 Prefix filter type.";
  }
  identity ipv6 {
    base vpn-policy-filter-type;
    description
    "Identity for IPv6 Prefix filter type.";
 }
  identity lan {
    base vpn-policy-filter-type;
    description
    "Identity for LAN Tag filter type.";
 }

  identity qos-profile-direction {
   description
   "Base identity for QoS profile direction.";
  }

  identity site-to-wan {
    base qos-profile-direction;
    description
    "Identity for Site-to-WAN direction.";
  }
  identity wan-to-site {
    base qos-profile-direction;
    description
    "Identity for WAN-to-Site direction.";
  }
  identity both {
    base qos-profile-direction;
    description
    "Identity for both WAN-to-Site direction
    and Site-to-WAN direction.";
  }
  /* Extended Identities */

  identity encapsulation-type {
     description
       "Identity for the encapsulation type.";
   }

   identity untagged-int {
     base encapsulation-type;
     description
       "Identity for Ethernet type.";
   }

   identity tagged-int {
     base encapsulation-type;
     description
       "Identity for the VLAN type.";
   }

   identity eth-inf-type {
     description
       "Identity of the Ethernet interface type.";
   }

   identity tagged {
     base eth-inf-type;
     description
       "Identity of the tagged interface type.";
   }

   identity untagged {
     base eth-inf-type;
     description
       "Identity of the untagged interface type.";
   }

   identity lag {
     base eth-inf-type;
     description
       "Identity of the LAG interface type.";
   }
   identity bearer-inf-type {
     description
       "Identity for the bearer interface type.";
   }

   identity port-id {
     base bearer-inf-type;
     description
       "Identity for the priority-tagged interface.";
   }

   identity lag-id {
     base bearer-inf-type;
     description
       "Identity for the priority-tagged interface.";
   }

   identity tagged-inf-type {
     description
       "Identity for the tagged interface type.";
   }

   identity priority-tagged {
     base tagged-inf-type;
     description
       "Identity for the priority-tagged interface.";
   }

   identity qinq {
     base tagged-inf-type;
     description
       "Identity for the QinQ tagged interface.";
   }

   identity dot1q {
     base tagged-inf-type;
     description
       "Identity for the dot1Q VLAN tagged interface.";
   }

   identity qinany {
     base tagged-inf-type;
     description
       "Identity for the QinAny tagged interface.";
   }

   identity vxlan {
     base tagged-inf-type;
     description
       "Identity for the VXLAN tagged interface.";
   }

   identity tag-type {
     description
       "Base identity from which all tag types are derived.";

   }

   identity c-vlan {
     base tag-type;
     description
       "A CVLAN tag, normally using the 0x8100 Ethertype.";
   }

   identity s-vlan {
     base tag-type;
     description
       "An SVLAN tag.";
   }

   identity c-s-vlan {
     base tag-type;
     description
       "Using both a CVLAN tag and an SVLAN tag.";
   }

   identity vxlan-peer-mode {
     description
       "Base identity for the VXLAN peer mode.";
   }

   identity static-mode {
     base vxlan-peer-mode;
     description
       "Identity for VXLAN access in the static mode.";
   }

   identity bgp-mode {
     base vxlan-peer-mode;
     description
       "Identity for VXLAN access by BGP EVPN learning.";
   }

   identity bw-direction {
     description
       "Identity for the bandwidth direction.";
   }

   identity input-bw {
     base bw-direction;
     description
       "Identity for the input bandwidth.";
   }
   identity output-bw {
     base bw-direction;
     description
       "Identity for the output bandwidth.";
   }

   identity bw-type {
     description
       "Identity of the bandwidth type.";
   }

   identity bw-per-cos {
     base bw-type;
     description
       "Bandwidth is per CoS.";
   }

   identity bw-per-port {
     base bw-type;
     description
       "Bandwidth is per site network access.";
   }

   identity bw-per-site {
     base bw-type;
     description
       "Bandwidth is per site.  It is applicable to
        all the site network accesses within the site.";
   }

   identity bw-per-svc {
     base bw-type;
     description
       "Bandwidth is per VPN service.";
   }

  /* Groupings */
 grouping vpn-service-cloud-access {
  container cloud-accesses {
   if-feature cloud-access;
   list cloud-access {
    key cloud-identifier;
    leaf cloud-identifier {
     type leafref {
      path "/l3vpn-ntw/vpn-profiles/"+
      "valid-provider-identifiers/cloud-identifier/id";
     }
     description
     "Identification of cloud service.
     Local administration meaning.";
    }
    choice list-flavor {
     case permit-any {
      leaf permit-any {
       type empty;
       description
       "Allows all sites.";
      }
     }
     case deny-any-except {
      leaf-list permit-site {
       type leafref {
        path "/l3vpn-ntw/sites/site/site-id";
       }
       description
       "Site ID to be authorized.";
      }
     }
     case permit-any-except {
      leaf-list deny-site {
       type leafref {
       path "/l3vpn-ntw/sites/site/site-id";
      }
      description
      "Site ID to be denied.";
      }
     }
     description
     "Choice for cloud access policy.  By
     default, all sites in the IP VPN MUST
     be authorized to access the cloud.";
    }
    container address-translation {
     container nat44 {
      leaf enabled {
       type boolean;
        default false;
        description
        "Controls whether or not Network address
        translation from IPv4 to IPv4 (NAT44)
        [RFC3022] is required.";
      }
      leaf nat44-customer-address {
       type inet:ipv4-address;
        description
        "Address to be used for network address
        translation from IPv4 to IPv4.  This is
        to be used if the customer is providing
        the IPv4 address.  If the customer address
        is not set, the model assumes that the
        provider will allocate the address.";
      }
      description
      "IPv4-to-IPv4 translation.";

     }
     description
     "Container for NAT.";
    }
    description
    "Cloud access configuration.";
   }
   description
   "Container for cloud access configurations.";
  }
  description
  "Grouping for VPN cloud definition.";
 } Groupings */
  grouping multicast-rp-group-cfg {
   choice group-format {
    mandatory true;
    case singleaddress {
     leaf group-address {
      type inet:ip-address;
      description
      "A single multicast group address.";
     }
    }
    case startend {
     leaf group-start {
      type inet:ip-address;
      description
      "The first multicast group address in
      the multicast group address range.";
     }
     leaf group-end {
      type inet:ip-address;
      description
      "The last multicast group address in
      the multicast group address range.";
     }
    }
    description
    "Choice for multicast group format.";
   }
   description
   "This grouping defines multicast group or
   multicast groups for RP-to-group mapping.";
  }
  grouping vpn-service-multicast {
   container multicast {
    if-feature multicast;
    leaf enabled {
     type boolean;
     default false;
     description
     "Enables multicast.";
    }
    container customer-tree-flavors {
     leaf-list tree-flavor {
      type identityref {
       base multicast-tree-type;
      }
      description
       "Type of tree to be used.";
     }
     description
     "Type of trees used by customer.";
    }
    container rp {
     container rp-group-mappings {
      list rp-group-mapping {
       key id;
       leaf id {
        type uint16;
        description
        "Unique identifier for the mapping.";

       }
       container provider-managed {
        leaf enabled {
         type boolean;
         default false;
         description
         "Set to true if the Rendezvous Point (RP)
         must be a provider-managed node.  Set to false
         if it is a customer-managed node.";
        }
        leaf rp-redundancy {
         type boolean;
         default false;
         description
         "If true, a redundancy mechanism for the RP
         is required.";
        }
        leaf optimal-traffic-delivery {
         type boolean;
         default false;
         description
         "If true, the SP must ensure that
         traffic uses an optimal path.  An SP may use
         Anycast RP or RP-tree-to-SPT switchover
         architectures.";
        }
        description
        "Parameters for a provider-managed RP.";
       }
       leaf rp-address {
        when "../provider-managed/enabled = 'false'" {
         description
         "Relevant when the RP is not provider-managed.";
        }
        type inet:ip-address;
         mandatory true;
       description
       "Defines the address of the RP.
       Used if the RP is customer-managed.";
      }
      container groups {
       list group {
        key id;
        leaf id {
         type uint16;
         description
         "Identifier for the group.";
        }
        uses multicast-rp-group-cfg;
        description
        "List of multicast groups.";
       }
       description
       "Multicast groups associated with the RP.";
      }
      description
      "List of RP-to-group mappings.";
     }
     description
     "RP-to-group mappings parameters.";
    }
    container rp-discovery {
     leaf rp-discovery-type {
      type identityref {
       base multicast-rp-discovery-type;
       }
      default static-rp;
      description
      "Type of RP discovery used.";
     }
     container bsr-candidates {
       when "derived-from-or-self(../rp-discovery-type, "+
           "'l3vpn-ntw:bsr-rp')" {
       description
       "Only applicable if discovery type
       is BSR-RP.";
      }
      leaf-list bsr-candidate-address {
       type inet:ip-address;
        description
        "Address of BSR candidate.";
      }
      description
      "Container for List of Customer
      BSR candidate's addresses.";
     }
     description
     "RP discovery parameters.";
    }
    description
    "RP parameters.";
   }
   description
   "Multicast global parameters for the VPN service.";
  }
  description
  "Grouping for multicast VPN definition.";
 }
 grouping vpn-service-mpls {
  leaf carrierscarrier {
   if-feature carrierscarrier;
    type boolean;
    default false;
    description
    "The VPN is using CsC, and so MPLS is required.";
  }
  description
  "Grouping for MPLS CsC definition.";
 }
 grouping customer-location-info {
  container locations {
   list location {
    key location-id;
    leaf location-id {
     type svc-id;
     description
     "Identifier for a particular location.";
    }
    leaf address {
     type string;
     description
     "Address (number and street) of the site.";
    }
    leaf postal-code {
     type string;
     description
     "Postal code of the site.";
    }
    leaf state {
     type string;
     description
     "State of the site.  This leaf can also be
     used to describe a region for a country that
     does not have states.";
    }
    leaf city {
     type string;
     description
     "City of the site.";
    }
    leaf country-code {
     type string {
      pattern '[A-Z]{2}';
     } inet:ip-address;
          mandatory true;
        description
     "Country of
        "Defines the site.
     Expressed as ISO ALPHA-2 code.";
    }
    description
    "Location address of the site.";
   }
   description
   "List of locations for RP.
        Used if the site.";
  }
  description
  "This grouping defines customer location parameters."; RP is customer-managed.";
       }
 grouping site-group {
       container groups {
        list group {
         key group-id; id;
         leaf group-id id {
          type string; uint16;
          description
     "Group-id
          "Identifier for the site belongs to."; group.";
         }
         uses multicast-rp-group-cfg;
         description
         "List of group-ids."; multicast groups.";
        }
        description
   "Groups
        "Multicast groups associated with the site or site-network-access belongs to.";
  }
  description
  "Grouping definition to assign
  group-ids to site or site-network-access."; RP.";
       }
 grouping site-diversity {
  container site-diversity {
   if-feature site-diversity;
   uses site-group;
       description
   "Diversity constraint type.  All
   site-network-accesses will inherit
   the group values defined here.";
       "List of RP-to-group mappings.";
      }
      description
  "This grouping defines site
  diversity
      "RP-to-group mappings parameters.";
     }
 grouping access-diversity {
  container access-diversity {
   if-feature site-diversity;
   uses site-group;
     container constraints {
    list constraint rp-discovery {
     key constraint-type;
      leaf constraint-type rp-discovery-type {
       type identityref {
        base placement-diversity;
      }
      description
      "Diversity constraint type."; multicast-rp-discovery-type;
        }
     container target {
      choice target-flavor {
       default id;
       case id {
        list group {
         key group-id;
         leaf group-id {
          type string;
          description
          "The constraint will be applied against
          this particular group-id for this site
          network access level.";
         } static-rp;
       description
         "List
       "Type of group-ids associated with one specific
         constraint for this site network access level.";
        } RP discovery used.";
      }
       case all-accesses
      container bsr-candidates {
        leaf all-other-accesses
        when "derived-from-or-self(../rp-discovery-type, "+
            "'l3vpn-ntw:bsr-rp')" {
         type empty;
        description
         "The constraint will be applied against
         all other site network accesses of this site.";
        }
       }
       case all-groups {
        leaf all-other-groups {
        "Only applicable if discovery type empty;
         description
         "The constraint will be applied against
         all other groups managed by the customer.";
        }
       }
       description
       "Choice for the target flavor definition.";
      }
      description
      "The constraint will be applied against a
      Specific target, and the target can be a list
      of group-ids,all other site network accesses of
      this site, or all other groups managed by the
      customer.";
        is BSR-RP.";
       }
       leaf-list bsr-candidate-address {
        type inet:ip-address;
         description
     "List
         "Address of constraints."; BSR candidate.";
       }
       description
    "Placement constraints
       "Container for this site network access."; List of Customer
       BSR candidate's addresses.";
      }
      description
   "Diversity
      "RP discovery parameters.";
     }
     description
  "This grouping defines access diversity
     "RP parameters.";
    }
    description
    "Multicast global parameters for the VPN service.";
   }
   description
   "Grouping for multicast VPN definition.";
  }
  grouping vpn-service-mpls {
   leaf carrierscarrier {
    if-feature carrierscarrier;
     type boolean;
     default false;
     description
     "The VPN is using CsC, and so MPLS is required.";
   }
   description
   "Grouping for MPLS CsC definition.";
  }
  grouping operational-requirements {
    leaf requested-site-start {
     type yang:date-and-time;
      description
      "Optional leaf indicating requested date and
      time when the service at a particular site is
      expected to start.";
   }
   leaf requested-site-stop {
     type yang:date-and-time;
      description
      "Optional leaf indicating requested date and
      time when the service at a particular site is
      expected to stop.";
   }
   description
   "This grouping defines some operational
   parameters.";
  }
  grouping operational-requirements-ops {
    leaf actual-site-start {
     type yang:date-and-time;
     config false;
      description
      "Optional leaf indicating actual date and
      time when the service at a particular site
      actually started.";
   }
   leaf actual-site-stop {
    type yang:date-and-time;
    config false;
      description
      "Optional leaf indicating actual date and
      time when the service at a particular site
      actually stopped.";

   }
   description
   "This grouping defines some operational
   parameters.";
  }
  grouping flow-definition {
   container match-flow {
    leaf dscp {
     type inet:dscp;
      description
      "DSCP value.";
    }
    leaf dot1p {
     type uint8 {
      range "0..7";
     }
     description
     "802.1p matching.";
    }
    leaf ipv4-src-prefix {
     type inet:ipv4-prefix;
      description
      "Match on IPv4 src address.";
    }
    leaf ipv6-src-prefix {
     type inet:ipv6-prefix;
      description
      "Match on IPv6 src address.";
    }
    leaf ipv4-dst-prefix {
     type inet:ipv4-prefix;
      description
      "Match on IPv4 dst address.";
    }
    leaf ipv6-dst-prefix {
     type inet:ipv6-prefix;
     description
     "Match on IPv6 dst address.";
    }
    leaf l4-src-port {
     type inet:port-number;
         must "current() < ../l4-src-port-range/lower-port or "+
         "current() > ../l4-src-port-range/upper-port" {
      description
      "If l4-src-port and l4-src-port-range/lower-port and
      upper-port are set at the same time, l4-src-port
      should not overlap with l4-src-port-range.";
      }
      description
      "Match on Layer 4 src port.";
    }
    leaf-list target-sites {
      if-feature target-sites;
      type svc-id;
      description
      "Identify a site as traffic destination.";
    }
    container l4-src-port-range {
      leaf lower-port {
      type inet:port-number;
      description
      "Lower boundary for port.";
     }
     leaf upper-port {
      type inet:port-number;
      must ". >= ../lower-port" {
       description
       "Upper boundary for port.  If it
       exists, the upper boundary must be
       higher than the lower boundary.";
      }
      description
      "Upper boundary for port.";
     }
      description
      "Match on Layer 4 src port range.  When
      only the lower-port is present, it represents
      a single port.  When both the lower-port and
      upper-port are specified, it implies
      a range inclusive of both values.";
    }
    leaf l4-dst-port {
     type inet:port-number;
          must "current() < ../l4-dst-port-range/lower-port or "+
          "current() > ../l4-dst-port-range/upper-port" {
      description
      "If l4-dst-port and l4-dst-port-range/lower-port
      and upper-port are set at the same time,
      l4-dst-port should not overlap with
      l4-src-port-range.";
      }
      description
      "Match on Layer 4 dst port.";
    }
    container l4-dst-port-range {
     leaf lower-port {
      type inet:port-number;
      description
      "Lower boundary for port.";
     }
     leaf upper-port {
      type inet:port-number;
      must ". >= ../lower-port" {
      description
      "Upper boundary must be
      higher than lower boundary.";
      }
      description
      "Upper boundary for port.  If it exists,
      upper boundary must be higher than lower
      boundary.";
     }
     description
     "Match on Layer 4 dst port range.  When only
     lower-port is present, it represents a single
     port.  When both lower-port and upper-port are
     specified, it implies a range inclusive of both
    values."; both
     values.";
    }
    leaf protocol-field {
     type union {
      type uint8;
      type identityref {
       base protocol-type;
      }
     }
     description
     "Match on IPv4 protocol or IPv6 Next Header field.";
    }
    description
    "Describes flow-matching criteria.";
   }
   description
   "Flow definition based on criteria.";
  }
  grouping site-service-basic {
   leaf svc-input-bandwidth {
     type uint64;
     units bps;
     mandatory true;
      description
      "From the customer site's perspective, the service
      input bandwidth of the connection or download
      bandwidth from the SP to the site.";

   }
   leaf svc-output-bandwidth {
    type uint64;
    units bps;
    mandatory true;
      description
      "From the customer site's perspective, the service
      output bandwidth of the connection or upload
      bandwidth from the site to the SP.";
   }
   leaf svc-mtu {
    type uint16;
    units bytes;
    mandatory true;
     description
     "MTU at service level.  If the service is IP,
     it refers to the IP MTU.  If CsC is enabled,
     the requested 'svc-mtu' leaf will refer to the
     MPLS MTU and not to the IP MTU.";
   }
   description
   "Defines basic service parameters for a site.";
  }
  grouping site-protection {
   container traffic-protection {
    if-feature fast-reroute;
    leaf enabled {
     type boolean;
     default false;
      description
      "Enables traffic protection of access link.";
    }
    description
    "Fast Reroute service parameters for the site.";
   }
   description
   "Defines protection service parameters for a site.";
  }
  grouping site-service-mpls {
   container carrierscarrier {
    if-feature carrierscarrier;
    leaf protocol-field signalling-type {
     type union enumeration {
     type uint8;
     type identityref
     enum ldp {
      base protocol-type;
     }
    }
      description
    "Match on IPv4
      "Use LDP as the signalling protocol or IPv6 Next Header field.";
      between the PE and the CE.  In this case,
      an IGP routing protocol must also be activated.";
      }
     enum bgp {
      description
   "Describes flow-matching criteria.";
      "Use BGP (as per RFC 8277) as the signalling protocol
      between the PE and the CE.
      In this case, BGP must also be configured as
      the routing protocol.";
      }
     }
     default bgp;
     description
  "Flow definition based on criteria.";
     "MPLS signalling type.";
    }
 grouping site-service-basic {
  leaf svc-input-bandwidth {
    type uint64;
    units bps;
    mandatory true;
      description
     "From
      "This container is used when the customer site's perspective, provides
      MPLS-based services.  This is only used in the service
     input bandwidth case
      of the connection or download
     bandwidth from the SP CsC (i.e., a customer builds an MPLS service using
      an IP VPN to the carry its traffic).";
   }
      description
      "Defines MPLS service parameters for a site.";
  }
  grouping site-service-qos-profile {
   container qos {
    if-feature qos;
    container qos-classification-policy {
     list rule {
      key id;
      ordered-by user;
      leaf svc-output-bandwidth id {
       type uint64;
   units bps;
   mandatory true; string;
       description
     "From the customer site's perspective, the service
     output bandwidth of
       "A description identifying the connection or upload
     bandwidth from
        qos-classification-policy rule.";
      }
      choice match-type {
       default match-flow;
       case match-flow {
       uses flow-definition;
       }
       case match-application {
        leaf match-application {
         type identityref {
          base customer-application;
         }
          description
          "Defines the site application to the SP."; match.";
        }

       }
       description
       "Choice for classification.";
      }
      leaf svc-mtu target-class-id {
       type uint16;
   units bytes;
   mandatory true; string;
       description
    "MTU at service level.  If the service is IP,
    it refers to
       "Identification of the IP MTU.  If CsC class of service.
       This identifier is enabled,
    the requested 'svc-mtu' leaf will refer to the
    MPLS MTU and not internal to the IP MTU."; administration.";
      }
      description
  "Defines basic service parameters for a site.";
      "List of marking rules.";
     }
     description
     "Configuration of the traffic classification policy.";
    }
 grouping site-protection {
    container traffic-protection qos-profile {
   if-feature fast-reroute;
     choice qos-profile {
      description
      "Choice for QoS profile.
      Can be standard profile or customized profile.";
      case standard {
       description
       "Standard QoS profile.";
       leaf enabled profile {
        type boolean;
    default false; leafref {
        path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
            "/qos-profile-identifier/id";
        }
        description
     "Enables traffic protection of access link.";
        "QoS profile to be used.";
       }
       leaf direction {
         type identityref {
           base qos-profile-direction;}
             default both;
             description
   "Fast Reroute service parameters for
             "The direction to which the site."; QoS profile
             is applied.";
       }
  description
  "Defines protection service parameters for a site.";
      }
 grouping site-service-mpls
      case custom {
       description
       "Customized QoS profile.";
        container carrierscarrier classes {
         if-feature carrierscarrier; qos-custom;
         list class {
          key class-id;
          leaf signalling-type class-id {
          type enumeration {
    enum ldp { string;
                   description
     "Use LDP as the signalling protocol
     between
                   "Identification of the PE and class of service.
                   This identifier is internal to the CE.  In this case,
     an IGP routing protocol must also be activated.";
                   administration.";
          }
    enum bgp
          leaf direction {
                   type identityref {
                    base qos-profile-direction;
                    }
                   default both;
                    description
     "Use BGP (as per RFC 8277) as the signalling protocol
     between
                    "The direction to which the PE and QoS profile
                    is applied.";
                 }
                  leaf rate-limit {
                   type decimal64 {
                    fraction-digits 5;
                    range "0..100";
           }
                   units percent;
                    description
                    "To be used if the CE.
     In this case, BGP class must also be configured rate-limited.
                    Expressed as percentage of the routing protocol."; service
                    bandwidth.";
         }

         container latency {
          choice flavor {
           case lowest {
            leaf use-lowest-latency {
             type empty;
              description
              "The traffic class should use the path with the
              lowest latency.";
            }
           }
           case boundary {
            leaf jitter-boundary {
             type uint16;
             units msec;
             default bgp; 400;
              description
    "MPLS signalling type.";
              "The traffic class should use a path with a
              defined maximum latency.";
            }
           }
           description
     "This container is used when the customer provides
     MPLS-based services.  This is only used in
           "Latency constraint on the case
     of CsC (i.e., a customer builds an MPLS service using
     an IP VPN to carry its traffic)."; traffic class.";
          }
          description
     "Defines MPLS service parameters for a site.";
          "Latency constraint on the traffic class.";
         }
 grouping site-service-qos-profile {
         container qos jitter {
   if-feature qos;
   container qos-classification-policy
          choice flavor {
    list rule
           case lowest {
     key id;
     ordered-by user;
            leaf id use-lowest-jitter {
             type string;
      description
      "A empty;
              description identifying
              "The traffic class should use the
       qos-classification-policy rule."; path with the
              lowest jitter.";
            }
     choice match-type {
      default match-flow;
      case match-flow {
      uses flow-definition;
           }
           case match-application boundary {
            leaf match-application latency-boundary {
             type identityref {
         base customer-application; uint32;
             units usec;
             default 40000;
              description
              "The traffic class should use a path with a
              defined maximum jitter.";
            }
           }
           description
         "Defines
           "Jitter constraint on the application to match."; traffic class.";
          }
          description
          "Jitter constraint on the traffic class.";
         }
         container bandwidth {
          leaf guaranteed-bw-percent {
           type decimal64 {
                   fraction-digits 5;
                   range "0..100";
           }
           units percent;
           mandatory true;
            description
      "Choice for classification.";
            "To be used to define the guaranteed bandwidth
            as a percentage of the available service bandwidth.";
          }
          leaf target-class-id end-to-end {
           type string; empty;
            description
      "Identification of
            "Used if the class of service.
      This identifier is internal to bandwidth reservation
            must be done on the administration."; MPLS network too.";
          }
          description
     "List of marking rules.";
          "Bandwidth constraint on the traffic class.";
         }
         description
    "Configuration
         "List of the traffic classification policy."; classes of services.";
        }
   container qos-profile {
    choice qos-profile {
        description
     "Choice
        "Container for QoS profile.
     Can be standard profile or customized profile.";
     case standard { list of classes of services.";
       }
      }
     }
     description
      "Standard QoS profile.";
      leaf
     "QoS profile {
       type leafref {
       path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
           "/qos-profile-identifier/id"; configuration.";
    }
    description
    "QoS profile to be used."; configuration.";
   }
      leaf direction
   description
   "This grouping defines QoS parameters for a site.";
  }
  grouping site-security-authentication {
        type identityref
   container authentication {
          base qos-profile-direction;}
            default both;
      description
            "The direction to which the QoS profile
            is applied.";
      "Authentication parameters.";
   }
   description
   "This grouping defines authentication parameters for a site.";
  }
     case custom
  grouping site-security-encryption {
      description
      "Customized QoS profile.";
   container classes encryption {
     if-feature qos-custom;
        list class {
         key class-id; encryption;
     leaf class-id enabled {
       type string; boolean;
       default false;
       description
                  "Identification of
       "If true, traffic encryption on the class of service.
                  This identifier connection is internal to the
                  administration."; required.";
     }
      leaf direction layer {
                  type identityref
         when "../enabled = 'true'" {
                   base qos-profile-direction;
                   }
                  default both;
         description
                   "The direction to which the QoS profile
         "Require a value for layer when enabled is applied."; true.";
        }
                 leaf rate-limit {
       type decimal64 enumeration {
                   fraction-digits 5;
                   range "0..100";
         enum layer2 {
         description
         "Encryption will occur at Layer 2.";
         }
         enum layer3 {
         description
         "Encryption will occur at Layer 3.
         For example, IPsec may be used when
         a customer requests Layer 3 encryption.";
        }
       }
     description
     "Layer on which encryption is applied.";
     }
                  units percent;
     description
                   "To be used if the class must be rate-limited.
                   Expressed as percentage of the service
                   bandwidth.";
     "";
   }
   container latency encryption-profile {
     choice flavor profile {
       case lowest provider-profile {
         leaf use-lowest-latency profile-name {
            type empty;
             description
             "The traffic class should use the leafref {
             path with "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
               "/encryption-profile-identifier/id";
            }
            description
            "Name of the
             lowest latency."; SP profile to be applied.";
         }
       }
       case boundary customer-profile {
         leaf latency-boundary algorithm {
           type uint16;
            units msec;
            default 400; string;
           description
             "The traffic class should use a path with a
             defined maximum latency.";
           }
           "Encryption algorithm to be used.";
         }
          description
          "Latency constraint on the traffic class.";
       }
     description
         "Latency constraint on the traffic class.";
     "";
     }
        container jitter {
     choice flavor key-type {
       default psk;
       case lowest psk {
         leaf use-lowest-jitter preshared-key {
           type empty; string;
           description
             "The traffic class should use the path with
           "Pre-Shared Key (PSK) coming from the
             lowest jitter."; customer.";
         }
       }
          case boundary {
           leaf latency-boundary {
            type uint32;
            units usec;
            default 40000;
       description
             "The traffic class should use a path with a
             defined maximum jitter.";
           }
       "Choice of encryption profile.
       The encryption profile can be the provider profile
       or customer profile.";
     }
     description
          "Jitter constraint on the traffic class.";
     "This grouping defines encryption parameters for a site.";
   }
   description
         "Jitter constraint on the traffic class.";
   "";
  }

  grouping site-routing {
   container bandwidth routing-protocols {
         leaf guaranteed-bw-percent
    list routing-protocol {
     key id;
     leaf id{
     type decimal64 {
                  fraction-digits 5;
                  range "0..100";
          }
          units percent;
          mandatory true; string;
     description
           "To be used to define the guaranteed bandwidth
           as a percentage of the available service bandwidth.";
     "";
     }
     leaf end-to-end { type empty;
           description
           "Used if the bandwidth reservation
           must be done on the MPLS network too.";
         }
         description
         "Bandwidth constraint on the traffic class."; {
      type identityref {
       base routing-protocol-type;
      }
      description
        "List of classes
      "Type of services."; routing protocol.";
     }
       description
       "Container for

     list of classes of services."; routing-profiles {
       key "id";

       leaf id {
        type leafref {
         path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
              "/routing-profile-identifier/id";
        }
        description
        "Routing profile to be used.";
       }

       leaf type {
         type ie-type;
         description
         "Import, export or both.";
       }

    description
    "QoS
   "Import or Export profile configuration."; reference";
     }
     container ospf {
      when "derived-from-or-self(../type, 'l3vpn-ntw:ospf')" {
      description
   "QoS configuration.";
      "Only applies when protocol is OSPF.";
      }
      if-feature rtg-ospf;
      leaf-list address-family {
       type address-family;
           min-elements "1";
          description
  "This grouping defines QoS parameters for
          "If OSPF is used on this site, this node
          contains a site."; configured value.  This node
          contains at least one address family
          to be activated.";
      }
 grouping site-security-authentication
      leaf area-address {
  container authentication
       type yang:dotted-quad;
       mandatory true;
          description
          "Area address.";
      }
      leaf metric {
       type uint16;
       default 1;
          description
     "Authentication parameters.";
          "Metric of the PE-CE link.  It is used
          in the routing state calculation and
          path selection.";
      }

      /* Extension */

      leaf mtu {
          type uint16;
          description
  "This grouping defines authentication parameters "Maximum transmission unit for a site."; given
          OSPF link.";
      }
 grouping site-security-encryption

      leaf process-id {
          type uint16;
          description
          "Process id of the OSPF CE-PE connection.";
      }
      uses security-params;

      /* End of Extension */
      container encryption sham-links {
       if-feature encryption; rtg-ospf-sham-link;
       list sham-link {
        key target-site;
        leaf enabled target-site {
         type boolean;
      default false; svc-id;
          description
      "If true, traffic encryption on
          "Target site for the connection sham link connection.
          The site is required."; referred to by its ID.";
        }
        leaf layer {
        when "../enabled = 'true'" metric {
         type uint16;
         default 1;
          description
        "Require a value for layer when enabled
          "Metric of the sham link.  It is used in
          the routing state calculation and path
          selection.  The default value is true.";
       }
      type enumeration {
        enum layer2 {
        description
        "Encryption will occur at Layer 2."; set
          to 1.";
        }
        enum layer3 {
          description
        "Encryption will occur at Layer 3.
        For example, IPsec may be used when
          "Creates a customer requests Layer 3 encryption.";
       } sham link with another site.";
       }
       description
    "Layer on which encryption is applied.";
       "List of sham links.";
      }
      description
    "";
      "OSPF-specific configuration.";
     }
     container encryption-profile {
    choice profile bgp {
      case provider-profile
      when "derived-from-or-self(../type, 'l3vpn-ntw:bgp')" {
       description
       "Only applies when protocol is BGP.";
      }
      if-feature rtg-bgp;
      leaf profile-name autonomous-system {
       type leafref {
            path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
              "/encryption-profile-identifier/id";
           } uint32;
       mandatory true;
          description
           "Name of
          "Customer AS number in case the SP profile to be applied.";
        } customer
          requests BGP routing.";
      }
      case customer-profile {
        leaf algorithm
      leaf-list address-family {
       type string; address-family;
           min-elements "1";
          description
          "Encryption algorithm
          "If BGP is used on this site, this node
          contains a configured value.  This node
          contains at least one address family
          to be used.";
        } activated.";
      }
      /*  Extension  */
      leaf neighbor {
         type inet:ip-address;
          description
    "";
          "IP address of the BGP neighbor.";
      }
    choice key-type {
      default psk;
      case psk {

      leaf preshared-key multihop {
         type string; uint8;
          description
          "Pre-Shared Key (PSK) coming from
          "Describes the customer."; number of hops allowed between the
          given BGP neighbor and the PE router.";
      }

      uses security-params;

      description
      "BGP-specific configuration.";
     }
     container static {
      when "derived-from-or-self(../type, 'l3vpn-ntw:static')" {
        description
      "Choice
        "Only applies when protocol is static.
        BGP activation requires the SP to know
        the address of encryption profile.
      The encryption profile can be the provider profile
      or customer profile.";
    }
    description
    "This grouping defines encryption parameters peer.  When
        BGP is enabled, the 'static-address'
        allocation type for a site.";
  }
  description
  ""; the IP connection
        MUST be used.";
      }
 grouping site-attachment-bearer {
      container bearer cascaded-lan-prefixes {
   container requested-type
       list ipv4-lan-prefixes {
        if-feature requested-type; ipv4;
        key "lan next-hop";
        leaf lan {
         type inet:ipv4-prefix;
         description
         "LAN prefixes.";
        }
        leaf requested-type lan-tag {
         type string;
          description
     "Type of requested bearer: Ethernet, DSL,
     Wireless, etc. Operator specific.";
          "Internal tag to be used in VPN policies.";
        }
        leaf strict next-hop {
         type boolean;
     default false; inet:ipv4-address;
          description
     "Defines whether requested-type is a preference
     or a strict requirement.";
          "Next-hop address to use on the customer side.";
        }
        description
     "Container
        "List of LAN prefixes for requested-type."; the site.";
       }
   leaf always-on
       list ipv6-lan-prefixes {
        if-feature always-on; ipv6;
        key "lan next-hop";
        leaf lan {
         type boolean;
    default true; inet:ipv6-prefix;
          description
     "Request for an always-on access type.
     For example, this could mean no dial access type.";
          "LAN prefixes.";
        }
        leaf bearer-reference lan-tag {
    if-feature bearer-reference;
         type string;
         description
     "This is an internal reference for the SP.";
   }
     description
     "Bearer-specific parameters.
     To
         "Internal tag to be augmented.";

     uses ethernet-params;

     uses pseudowire-params {
      when "/l3vpn-ntw/sites/site/site-network-accesses" +
            "/site-network-access/site-network-access-type ='pseudowire'" used in VPN policies.";
        }
        leaf next-hop {
         type inet:ipv6-address;
          description "pseudowire specific parameters";
        }
     }
          "Next-hop address to use on the customer side.";
        }
        description
  "Defines physical properties
        "List of a site attachment."; LAN prefixes for the site.";
       }
 grouping site-routing {
  container routing-protocols {
   list routing-protocol {
    key type;
    leaf type {
     type identityref {
      base routing-protocol-type;
       description
       "LAN prefixes from the customer.";
      }
      description
     "Type of routing protocol.";
      "Configuration specific to static routing.";
     }

    list routing-profiles {
      key "id";

      leaf id
     container rip {
       type leafref
      when "derived-from-or-self(../type, 'l3vpn-ntw:rip')" {
        path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
             "/routing-profile-identifier/id";
       }
       description
       "Routing profile to be
       "Only applies when the protocol is RIP.  For IPv4,
       the model assumes that RIP version 2 is used.";
      }

      leaf type
      if-feature rtg-rip;
      leaf-list address-family {
       type ie-type; address-family;
           min-elements "1";
          description
        "Import, export or both.";
          "If RIP is used on this site, this node
          contains a configured value.  This node
          contains at least one address family
          to be activated.";
      }
      description
  "Import or Export profile reference";
      "Configuration specific to RIP routing.";
     }
     container ospf vrrp {
      when "derived-from-or-self(../type, 'l3vpn-ntw:ospf')" 'l3vpn-ntw:vrrp')" {
       description
       "Only applies when protocol is OSPF."; VRRP.";
      }
      if-feature rtg-ospf; rtg-vrrp;
      leaf-list address-family {
       type address-family;
           min-elements "1";
          description
          "If OSPF VRRP is used on this site, this node
          contains a configured value.  This node contains
          at least one address family to be activated.";
      }
     leaf area-address {
      type yang:dotted-quad;
      mandatory true;
      description
         "Area address.";
      "Configuration specific to VRRP routing.";
     }
     leaf metric {
      type uint16;
      default 1;
     description
         "Metric
     "List of the PE-CE link.  It is routing protocols used
         in on
     the site.  This list can be augmented.";
    }
    description
    "Defines routing state calculation and
         path selection."; protocols.";
   }

     /* Extension */
   description
   "Grouping for routing protocols.";
  }
  grouping site-attachment-ip-connection {

    container ip-connection {
      container ipv4 {
      if-feature ipv4;
       leaf mtu address-allocation-type {
       type uint16; identityref {
        base address-allocation-type;
      }
      must "not(derived-from-or-self(current(), 'l3vpn-ntw:slaac') or "+
          "derived-from-or-self(current(), "+
          "'l3vpn-ntw:provider-dhcp-slaac'))" {
      error-message "SLAAC is only applicable to IPv6";
      }
      description "Maximum transmission unit
      "Defines how addresses are allocated.
      If there is no value for a given
         OSPF link."; the address
      allocation type, then IPv4 is not enabled.";

     }

     uses security-params;

     /* End of Extension */
    container sham-links provider-dhcp {
      if-feature rtg-ospf-sham-link;
      list sham-link
      when "derived-from-or-self(../address-allocation-type, "+
      "'l3vpn-ntw:provider-dhcp')" {
       key target-site;
      description
      "Only applies when addresses are allocated by DHCP.";
    }
      leaf target-site provider-address {
       type svc-id; inet:ipv4-address;
          description
         "Target site for
          "Address of provider side.  If provider-address is not
          specified, then prefix length should not be specified
          either.  It also implies provider-dhcp allocation is
          not enabled.  If provider-address is specified, then
          the prefix length may or may not be specified.";
      }
      leaf prefix-length {
       type uint8 {
       range "0..32";
       }
          must "(../provider-address)" {
           error-message
           "If the prefix length is specified, provider-address
           must also be specified.";
              description
              "If the prefix length is specified, provider-address
              must also be specified.";
         }
      description
      "Subnet prefix length expressed in bits.
      If not specified, or specified as zero,
      this means the sham link connection.
         The site is referred customer leaves the actual
      prefix length value to by its ID."; the provider.";
      }
      choice address-assign {
       default number;
       case number {
        leaf metric number-of-dynamic-address {
         type uint16;
         default 1;
          description
         "Metric of the sham link.  It is used in
          "Describes the routing state calculation and path
         selection.  The default value is set
         to 1.";
       }
         description
         "Creates a sham link with another site.";
      }
      description
      "List number of sham links."; IP addresses
          the customer requires.";
        }
     description
     "OSPF-specific configuration.";
       }
       case explicit {
        container bgp customer-addresses {
     when "derived-from-or-self(../type, 'l3vpn-ntw:bgp')"
         list address-group {
      description
      "Only applies when protocol is BGP.";
     }
     if-feature rtg-bgp;
          key "group-id";
          leaf autonomous-system group-id {
          type uint32;
      mandatory true; string;
          description
         "Customer AS number in case
          "Group-id for the customer
         requests BGP routing.";
     }
     leaf-list address-family {
      type address-family;
          min-elements "1";
         description
         "If BGP is used on this site, this node
         contains a configured value.  This node
         contains at least one address family range from
          start-address to be activated."; end-address.";
          }
     /*  Extension  */
         leaf neighbor start-address {
          type inet:ip-address; inet:ipv4-address;
           description
         "IP address of the BGP neighbor.";
           "First address.";
          }
         leaf multihop end-address {
          type uint8; inet:ipv4-address;
          description
          "Last address.";
          }
          description
          "Describes the number of hops allowed between the
         given BGP neighbor IP addresses allocated by DHCP.
          When only start-address or only end-address
          is present, it represents a single address.
          When both start-address and end-address are
          specified, it implies a range inclusive of both
          addresses.  If no address is specified, it implies
          customer addresses group is not supported.";
         }
          description
          "Container for customer addresses is allocated by DHCP.";
        }
      }
          description
          "Choice for the PE router."; way to assign addresses.";
      }

     uses security-params;
          description
     "BGP-specific configuration.";
          "DHCP allocated addresses related parameters.";
     }
  container static dhcp-relay {
    when "derived-from-or-self(../type, 'l3vpn-ntw:static')" "derived-from-or-self(../address-allocation-type, "+
    "'l3vpn-ntw:provider-dhcp-relay')" {
      description
      "Only applies when protocol provider is static.
       BGP activation requires the SP required to know
       the address implement
      DHCP relay function.";
   }
  leaf provider-address {
   type inet:ipv4-address;
      description
      "Address of the customer peer.  When
       BGP provider side.  If provider-address is enabled, the 'static-address' not
      specified, then prefix length should not be specified
      either.  It also implies provider-dhcp allocation type for the IP connection
       MUST is
      not enabled.  If provider-address is specified, then
      prefix length may or may not be used."; specified.";
  }
     container cascaded-lan-prefixes {
      list ipv4-lan-prefixes {
       if-feature ipv4;
       key "lan next-hop";
  leaf lan prefix-length {
   type inet:ipv4-prefix;
        description
        "LAN prefixes."; uint8 {
   range "0..32";
   }
       leaf lan-tag
  must "(../provider-address)" {
        type string;
   error-message
      "If prefix length is specified, provider-address
       must also be specified.";
      description
         "Internal tag to
      "If prefix length is specified, provider-address
      must also be used in VPN policies."; specified.";
 }
       leaf next-hop {
        type inet:ipv4-address;
      description
         "Next-hop address to use on
      "Subnet prefix length expressed in bits.  If not
      specified, or specified as zero, this means the
      customer side.";
       }
       description
       "List of LAN prefixes for leaves the site.";
      }
      list ipv6-lan-prefixes {
       if-feature ipv6;
       key "lan next-hop";
       leaf lan {
        type inet:ipv6-prefix;
         description
         "LAN prefixes.";
       }
       leaf lan-tag {
        type string;
        description
        "Internal tag actual prefix length value
      to be used in VPN policies."; the provider.";
  }
       leaf next-hop
  container customer-dhcp-servers {
   leaf-list server-ip-address {
   type inet:ipv6-address; inet:ipv4-address;
      description
         "Next-hop
      "IP address to use on the customer side.";
       }
       description
       "List of LAN prefixes for the site."; customer DHCP server.";
  }
  description
      "LAN prefixes from the customer.";
  "Container for list of customer DHCP servers.";
  }
  description
     "Configuration specific to static routing.";
  "DHCP relay provided by operator.";
 }
  container rip static-addresses {
    when "derived-from-or-self(../type, 'l3vpn-ntw:rip')" "derived-from-or-self(../address-allocation-type, "+
    "'l3vpn-ntw:static-address')" {
    description
    "Only applies when the protocol allocation type is RIP.  For IPv4,
      the model assumes that RIP version 2 is used."; static.";
     }
     if-feature rtg-rip;
     leaf-list address-family {
     leaf primary-address{
     type address-family;
          min-elements "1"; leafref {
      path "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/"+
      "vpn-node/vpn-network-accesses/vpn-network-access/"+
      "ip-connection/ipv4/static-addresses/address/address-id";
     }
     description
         "If RIP is used on this site, this node
         contains a configured value.  This node
         contains at least one
     "Principal address family
         to be activated."; of the connection.";
     }
     list address{
     key address-id;
      leaf address-id {
      type string;
      description
     "Configuration specific to RIP routing.";
      "IPv4 Address";
      }
    container vrrp {
     when "derived-from-or-self(../type, 'l3vpn-ntw:vrrp')"
      leaf provider-address {
       type inet:ipv4-address;
          description
      "Only applies when
          "IPv4 Address List of the provider side.
          When the protocol allocation type is VRRP."; static,
          the provider address must be configured.";
      }
     if-feature rtg-vrrp;
     leaf-list address-family
      leaf customer-address {
       type address-family;
          min-elements "1"; inet:ipv4-address;
          description
         "If VRRP is used on this site, this node
         contains a configured value.  This node contains
         at least one address family to be activated.";
          "IPv4 Address of customer side.";
      }
      leaf prefix-length {
       type uint8 {
        range "0..32";
       }
      description
     "Configuration specific
      "Subnet prefix length expressed in bits.
      It is applied to VRRP routing."; both provider-address
      and customer-address.";
      }
      description
    "List of routing protocols used on
    the site.  This list can be augmented.";
      "Describes IPv4 addresses used.";
     }
     description
   "Defines routing protocols.";
     "Describes IPv4 addresses used.";
     }
     description
  "Grouping for routing protocols.";
     "IPv4-specific parameters.";
    }
 grouping site-attachment-ip-connection {

   container ip-connection {
    container ipv4 ipv6 {
     if-feature ipv4; ipv6;
     leaf address-allocation-type {
      type identityref {
       base address-allocation-type;
      }
     must "not(derived-from-or-self(current(), 'l3vpn-ntw:slaac') or "+
         "derived-from-or-self(current(), "+
         "'l3vpn-ntw:provider-dhcp-slaac'))" {
     error-message "SLAAC is only applicable to IPv6";
     }
      description
      "Defines how addresses are allocated.
      If there is no value for the address
      allocation type, then IPv4 IPv6 is
      not enabled.";
     }

    container provider-dhcp {
       when "derived-from-or-self(../address-allocation-type, "+
     "'l3vpn-ntw:provider-dhcp')"
       "'l3vpn-ntw:provider-dhcp') "+
       "or derived-from-or-self(../address-allocation-type, "+
       "'l3vpn-ntw:provider-dhcp-slaac')" {
       description
       "Only applies when addresses are allocated by DHCP.";
        }
           leaf provider-address {
            type inet:ipv4-address; inet:ipv6-address;
            description
            "Address of the provider side.  If provider-address
            is not specified, then prefix length should not be
            specified either.  It also implies provider-dhcp
            allocation is not enabled.  If provider-address is
            specified, then
         the prefix length may or may
            not be specified.";
          }
       leaf prefix-length {
        type uint8 {
        range "0..32"; "0..128";
        }
            must "(../provider-address)" {
              error-message
              "If the prefix length is specified, provider-address
              must also be specified.";
              description
              "If the prefix length is specified, provider-address
              must also be specified.";
             }
        description
        "Subnet prefix length expressed in bits.  If not
        specified, or specified as zero, this means the
        customer leaves the actual prefix length value
        to the provider.";
      }
         choice address-assign {
          default number;
          case number {
           leaf number-of-dynamic-address {
            type uint16;
            default 1;
            description
            "Describes the number of IP addresses the customer
            requires.";

           }
          }
          case explicit {
           container customer-addresses {
            list address-group {
                  key "group-id";
                  leaf group-id {
                  type string;
                  description
                  "Group-id for the address range from
                  start-address to end-address.";
              }
                  leaf start-address {
                   type inet:ipv4-address; inet:ipv6-address;
                   description
                   "First address.";
                   }
                  leaf end-address {
                   type inet:ipv4-address; inet:ipv6-address;
                   description
                   "Last address.";
                   }
                  description
                  "Describes IP addresses allocated by DHCP.  When only
                  start-address or only end-address is present, it
                  represents a single address.  When both start-address
                  and end-address are specified, it implies a range
                  inclusive of both addresses.  If no address is
                  specified, it implies customer addresses group is
                  not supported.";
           }
            description
            "Container for customer addresses is allocated by DHCP.";
          }
         }
          description
          "Choice for the way to assign addresses.";
         }
          description
          "DHCP allocated addresses related parameters.";
         }
    container dhcp-relay {
     when "derived-from-or-self(../address-allocation-type, "+
          "'l3vpn-ntw:provider-dhcp-relay')" {
       description
       "Only applies when the provider is required
       to implement DHCP relay function.";
       }
         leaf provider-address {
          type inet:ipv4-address; inet:ipv6-address;
           description
           "Address of the provider side.  If provider-address is
           not specified, then prefix length should not be
           specified either.  It also implies provider-dhcp
           allocation is not enabled.  If provider-address provider address
           is specified, then prefix length may or may
           not be specified.";
           }
         leaf prefix-length {
          type uint8 {
           range "0..32"; "0..128";
           }
          must "(../provider-address)" {
           error-message
            "If prefix length is specified, provider-address
            must also be specified.";
           description
           "If prefix length is specified, provider-address
           must also be specified.";
            }
          description
          "Subnet prefix length expressed in bits.  If not
          specified, or specified as zero, this means the
          customer leaves leaves the actual prefix length value
          to the provider.";
          }
     container customer-dhcp-servers {
      leaf-list server-ip-address {
       type inet:ipv6-address;
        description
        "This node contains the IP address of
        the customer DHCP server.  If the DHCP relay
        function is implemented by the
        provider, this node contains the
        configured value.";
      }
       description
       "Container for list of customer DHCP servers.";
      }
     description
     "DHCP relay provided by operator.";
     }
     container static-addresses {
       when "derived-from-or-self(../address-allocation-type, "+
       "'l3vpn-ntw:static-address')" {
       description
       "Only applies when protocol allocation type is static.";
        }
        leaf primary-address{
        type leafref {
         path "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/"+
         "vpn-node/vpn-network-accesses/vpn-network-access/"+
         "ip-connection/ipv6/static-addresses/address/address-id";
        }
        description
        "Principal address of the connection";
        }
        list address{
        key address-id;
         leaf address-id {
         type string;
         description
         "IPv4 Address";
         }
     leaf provider-address {
      type inet:ipv6-address;
       description
       "IPv6 Address of the provider side.  When the protocol
       allocation type is static, the provider address
       must be configured.";
      }
     leaf customer-address {
      type inet:ipv6-address;
       description
       "The IPv6 Address of the customer side.";
      }
     leaf prefix-length {
      type uint8 {
       range "0..128";
      }
      description
      "Subnet prefix length expressed in bits.
      It is applied to both provider-address and
      customer-address.";
     }
     description
     "Describes IPv6 addresses used.";
     }
     description
     "IPv6-specific parameters.";
     }
     description
     "IPv6-specific parameters.";
    }
    container oam {
     container bfd {
      if-feature bfd;
      leaf enabled {
       type boolean;
       default false;
       description
       "If true, BFD activation is required.";
      }
      choice holdtime {
       default fixed;
       case fixed {
        leaf fixed-value {
         type uint32;
         units msec;
          description
          "Expected BFD holdtime expressed in msec.  The customer
          may impose some fixed values for the holdtime period
          if the provider allows the customer use this function.
          If the actual prefix length value provider doesn't allow the customer to use this
          function, the provider."; fixed-value will not be set.";
        }
 container customer-dhcp-servers
       }
       case profile {
  leaf-list server-ip-address
        leaf profile-name {
         type inet:ipv4-address; leafref {
          path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers/"+
                  "bfd-profile-identifier/id";
         }
         description
     "IP address of
         "Well-known SP profile name.  The provider can propose
         some profiles to the customer, depending on the service
         level the customer DHCP server."; wants to achieve.  Profile names
         must be communicated to the customer.";
        }
        description
 "Container for list of customer DHCP servers.";
        "Well-known SP profile.";
       }
       description
 "DHCP relay provided by operator.";
       "Choice for holdtime flavor.";
      }
 container addresses {
   when "derived-from-or-self(../address-allocation-type, "+
   "'l3vpn-ntw:static-address')" {
      description
   "Only applies when protocol allocation type is static.";
      "Container for BFD.";
     }
     leaf provider-address {
      type inet:ipv4-address;
     description
         "IPv4 Address List of
     "Defines the provider side.
         When Operations, Administration, and Maintenance (OAM)
     mechanisms used on the protocol allocation type connection.  BFD is static, set as a fault
     detection mechanism, but the provider address must 'oam' container can easily
     be configured."; augmented by other mechanisms";
    }
     leaf customer-address {
      type inet:ipv4-address;
    description
         "IPv4 Address of customer side.";
    "Defines connection parameters.";
   }
   description
   "This grouping defines IP connection parameters.";
  }
  grouping site-service-multicast {
   container multicast {
    if-feature multicast;
    leaf prefix-length multicast-site-type {
     type uint8 enumeration {
       range "0..32";
      enum receiver-only {
       description
       "The site only has receivers.";
      }
      enum source-only {
       description
     "Subnet prefix length expressed in bits.
     It is applied to
       "The site only has sources.";
      }
      enum source-receiver {
       description
       "The site has both provider-address sources and customer-address."; receivers.";
      }
     }
     default source-receiver;
     description
     "Type of multicast site.";
    }
    container multicast-address-family {
     leaf ipv4 {
      if-feature ipv4;
      type boolean;
      default false;
      description
     "Describes
      "Enables IPv4 addresses used.";
    }
    description
    "IPv4-specific parameters."; multicast.";
     }
   container
     leaf ipv6 {
      if-feature ipv6;
    leaf address-allocation-type {
      type identityref {
      base address-allocation-type;
     } boolean;
      default false;
      description
     "Defines how addresses are allocated.
     If there is no value for the address
     allocation type, then
      "Enables IPv6 is
     not enabled."; multicast.";
     }

   container provider-dhcp {
      when "derived-from-or-self(../address-allocation-type, "+
      "'l3vpn-ntw:provider-dhcp') "+
      "or derived-from-or-self(../address-allocation-type, "+
      "'l3vpn-ntw:provider-dhcp-slaac')" {
     description
      "Only applies when addresses are allocated by DHCP.";
     "Defines protocol to carry multicast.";
     }

    leaf provider-address protocol-type {
     type inet:ipv6-address; enumeration {
      enum host {
       description
           "Address of
       "Hosts are directly connected to the provider side.  If provider-address
           is not specified, then prefix length should not be
           specified either.  It also implies provider-dhcp
           allocation is not enabled.  If provider-address is
           specified, then prefix length may network.
       Host protocols such as IGMP or may
           not be specified.";
         }
      leaf prefix-length {
       type uint8 {
       range "0..128"; MLD are required.";
      }
           must "(../provider-address)"
      enum router {
             error-message
             "If prefix length is specified, provider-address
             must also be specified.";
       description
             "If prefix length is specified, provider-address
             must also
       "Hosts are behind a customer router.
       PIM will be specified."; implemented.";
      }
      enum both {
       description
       "Subnet prefix length expressed in bits.  If not
       specified, or specified as zero, this means the
       "Some hosts are behind a customer leaves the actual prefix length value router, and
       some others are directly connected to the provider.";
       provider network.  Both host and routing protocols
       must be used.  Typically, IGMP and PIM will be
       implemented.";
      }
     }
        choice address-assign {
         default number;
         case number {
          leaf number-of-dynamic-address {
           type uint16;
     default 1; "both";
     description
           "Describes
     "Multicast protocol type to be used with the number of IP addresses customer site.";
    }
    description
    "Multicast parameters for the customer
           requires."; site.";
   }
   description
   "Multicast parameters for the site.";
  }
         case explicit
  grouping site-maximum-routes {
   container customer-addresses maximum-routes {
    list address-group address-family {
     key "group-id";
                 leaf group-id {
                 type string;
                 description
                 "Group-id for the address range from
                 start-address to end-address.";
             } af;
     leaf start-address af {
      type inet:ipv6-address; address-family;
      description
                  "First address.";
      "Address family.";
     }
     leaf end-address maximum-routes {
      type inet:ipv6-address; uint32;
      description
                  "Last address.";
      "Maximum prefixes the VRF can accept
      for this address family.";
     }
     description
                 "Describes IP addresses allocated by DHCP.  When only
                 start-address or only end-address is present, it
                 represents a single address.  When both start-address
                 and end-address are specified, it implies a range
                 inclusive
     "List of both addresses.  If no address is
                 specified, it implies customer addresses group is
                 not supported."; families.";

    }
    description
           "Container
    "Defines 'maximum-routes' for customer addresses allocated by DHCP.";
         } the VRF.";
   }
   description
         "Choice
   "Defines 'maximum-routes' for the way to assign addresses."; site.";
  }
  grouping site-security {
   container security {
    uses site-security-authentication;
    uses site-security-encryption;
    description
         "DHCP allocated addresses related
    "Site-specific security parameters.";
   }
   container dhcp-relay
   description
   "Grouping for security parameters.";
  }
  grouping network-access-service {
    when "derived-from-or-self(../address-allocation-type, "+
         "'l3vpn-ntw:provider-dhcp-relay')"
   container service {
    uses site-service-basic;
    /* Extension */
    /* uses svc-bandwidth-params; */
    /* EoExt */
    uses site-service-qos-profile;
    uses site-service-mpls;
    uses site-service-multicast;
    description
      "Only applies when
    "Service parameters on the provider is required
      to implement DHCP relay function."; attachment.";
   }
   description
   "Grouping for service parameters.";
  }
  grouping vpn-extranet {
   container extranet-vpns {
    if-feature extranet-vpn;
    list extranet-vpn {
     key vpn-id;
     leaf provider-address vpn-id {
      type inet:ipv6-address; svc-id;
      description
          "Address of
      "Identifies the provider side.  If provider-address is
          not specified, then prefix length should not be
          specified either.  It also implies provider-dhcp
          allocation is not enabled.  If provider address
          is specified, then prefix length may or may
          not be specified."; target VPN the local VPN want to access.";
     }
     leaf prefix-length local-sites-role {
      type uint8 identityref {
          range "0..128";
       base site-role;
      }
         must "(../provider-address)" {
          error-message
           "If prefix length is specified, provider-address
           must also be specified.";
      default any-to-any-role;
      description
          "If prefix length is specified, provider-address
      "This describes the role of the
      local sites in the target VPN topology.  In the any-to-any VPN
      service topology, the local sites must also have the same role, which
      will be specified.";
           }
         description
         "Subnet prefix length expressed in bits.  If not
         specified, or specified as zero, this means 'any-to-any-role'.  In the
         customer leaves Hub-and-Spoke VPN service
      topology or the actual prefix length value
         to Hub-and-Spoke disjoint VPN service topology,
      the provider."; local sites must have a Hub role or a Spoke role.";
     }
    container customer-dhcp-servers {
     leaf-list server-ip-address {
      type inet:ipv6-address;
     description
       "This node contains the IP address
     "List of extranet VPNs or target VPNs the customer DHCP server.  If the DHCP relay
       function local VPN is implemented by the
       provider, this node contains the
       configured value.";
     attached to.";
    }
    description
    "Container for list of customer DHCP servers."; extranet VPN configuration.";
   }
   description
    "DHCP relay provided by operator.";
   "Grouping for extranet VPN configuration.
   This provides an easy way to interconnect
   all sites from two VPNs.";
  }
  grouping vpn-profile-cfg {
   container addresses valid-provider-identifiers {
    when "derived-from-or-self(../address-allocation-type, "+
        "'l3vpn-ntw:static-address')"
    list cloud-identifier {
     if-feature cloud-access;
     key id;
     leaf id {
      type string;
      description
     "Only applies when protocol allocation
      "Identification of cloud service.
      Local administration meaning.";
     }
     description
     "List for Cloud Identifiers.";
    }
    list encryption-profile-identifier {
     key id;
     leaf id {
      type is static."; string;
      description
      "Identification of the SP encryption profile
      to be used.  Local administration meaning.";
     }
     description
     "List for encryption profile identifiers.";
    }
    list qos-profile-identifier {
     key id;
     leaf provider-address id {
      type inet:ipv6-address; string;
      description
      "IPv6 Address
      "Identification of the provider side.  When the protocol
      allocation type is static, the provider address
      must QoS Profile to be configured."; used.
      Local administration meaning.";
     }
     description
     "List for QoS Profile Identifiers.";
    }
    list bfd-profile-identifier {
     key id;
     leaf customer-address id {
      type inet:ipv6-address; string;
      description
      "The IPv6 Address
      "Identification of the customer side."; SP BFD Profile to be used.
      Local administration meaning.";
     }
     description
     "List for BFD Profile identifiers.";
    }

    list routing-profile-identifier {
     key id;
     leaf prefix-length id {
      type uint8 {
      range "0..128";
     } string;
      description
     "Subnet prefix length expressed in bits.
     It is applied
      "Identification of the routing Profile to both provider-address be used
      by the routing-protocols within sites and
     customer-address."; vpn-
      network-accesses. Local administration meaning.";
     }
     description
    "Describes IPv6 addresses used.";
     "List for Routing Profile Identifiers.";
    }

      nacm:default-deny-write;
      description
    "IPv6-specific parameters.";
      "Container for Valid Provider Identifies.";
   }
   container oam {
    container bfd

    description
    "Grouping for VPN Profile configuration.";
  }
  grouping vpn-svc-cfg {
     if-feature bfd;
   leaf enabled vpn-id {
    type boolean;
      default false; svc-id;
    description
      "If true, BFD activation is required.";
    "VPN identifier.  Local administration meaning.";
   }
     choice holdtime {
      default fixed;
      case fixed {
   leaf fixed-value customer-name {
    type uint32;
        units msec; string;
    description
         "Expected BFD holdtime expressed in msec.  The customer
         may impose some fixed values for the holdtime period
         if the provider allows
    "Name of the customer use this function.
         If the provider doesn't allow that actually uses the customer to use this
         function, VPN service.
    In the fixed-value will not be set.";
       }
      } case profile {
       leaf profile-name {
        type leafref {
         path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers/"+
                 "bfd-profile-identifier/id";
        }
        description
        "Well-known SP profile name.  The that any intermediary (e.g., Tier-2 provider can propose
        some profiles to
    or partner) sells the customer, depending VPN service to their end user
    on behalf of the original service
        level provider (e.g., Tier-1
    provider), the original service provider may require the
    customer wants to achieve.  Profile names
        must be communicated name to provide smooth activation/commissioning
    and operation for the customer."; service.";
   }
       description
       "Well-known SP profile.";
   leaf vpn-service-topology {
    type identityref {
     base vpn-topology;
    }
    default any-to-any;
    description
      "Choice for holdtime flavor.";
    "VPN service topology.";
   }

   leaf description
     "Container for BFD.";
    } {
     type string;
     description
    "Defines the Operations, Administration, and Maintenance (OAM)
    mechanisms used on the connection.  BFD is set as a fault
    detection mechanism, but the 'oam' container can easily
    be augmented by other mechanisms";
   }
       "Textual description
   "Defines connection parameters."; of a VPN service.";
   }

   uses ie-profiles-params;
   uses vpn-nodes-params;
   uses vpn-service-multicast;
   /* uses vpn-service-mpls; */
   /* uses vpn-extranet;*/
   description
  "This grouping defines IP connection parameters.";
   "Grouping for VPN service configuration.";
  }
  grouping site-service-multicast {
  container multicast site-network-access-top-level-cfg {
   if-feature multicast;
   uses status-params;
   leaf multicast-site-type vpn-network-access-type {
    type enumeration {
     enum receiver-only identityref {
      description
      "The site only has receivers.";
     base site-network-access-type;
    }
     enum source-only {
    default point-to-point;
    description
      "The site only has sources.";
    "Describes the type of connection, e.g.,
    point-to-point or multipoint.";
   }
     enum source-receiver {
   uses ethernet-params;
   uses site-attachment-ip-connection;
   uses site-security;
   uses site-routing;
   description
      "The
   "Grouping for site has both sources and receivers.";
     }
    }
    default source-receiver;
    description
    "Type of multicast site."; network access top-level configuration.";
  }

   /* Bearers in a site */
    grouping site-bearer-params {
     container multicast-address-family site-bearers {
       list bearer {
         key "bearer-id";
         leaf ipv4 bearer-id {
     if-feature ipv4;
           type boolean;
     default false; string;
           description
     "Enables IPv4 multicast."; "";
         }
         leaf BearerType {
         type identityref {
           base bearer-inf-type;
         }
         description
           "Request for an Bearer access type.
           Choose between port or lag connection type.";
         }

         leaf ipv6 ne-id {
     if-feature ipv6;
           type boolean;
     default false;
     description
     "Enables IPv6 multicast.";
    } string;
         description
    "Defines protocol to carry multicast.";
           "NE-id reference.";
         }

         leaf protocol-type port-id {
           type enumeration {
     enum host { string;
           description
      "Hosts are directly connected to the provider network.
      Host protocols such as IGMP or MLD are required.";
           "Port-id in format slot/ card /port.";
         }
     enum router
         leaf lag-id {
           type string;
           description
      "Hosts are behind a customer router.
      PIM will be implemented.";
           "lag-id in format id.";
         }
     enum both {
      description
      "Some hosts are behind a customer router, and
      some others are directly connected
     "Parameters used to the
      provider network.  Both host and routing protocols
      must be used.  Typically, IGMP and PIM will be
      implemented.";
     } identify each bearer";
       }
    default "both";
     description
    "Multicast protocol type
     "Grouping to be used with the customer site.";
   }
   description
   "Multicast parameters for reuse the site."; site bearer assigment";
     }
     description
  "Multicast parameters for
     "Grouping to reuse the site."; site bearer assigment";
    }

    /* UNUSED */
    grouping site-management svc-bandwidth-params {
      container management svc-bandwidth {
         if-feature "input-bw";
         list bandwidth {
           key "direction type";
           leaf type direction {
             type identityref {
               base management; bw-direction;
             }
    mandatory true;
             description
    "Management
               "Indicates the bandwidth direction.  It can be
                the bandwidth download direction from the SP to
                the site or the bandwidth upload direction from
                the site to the SP.";
           }
           leaf type of {
             type identityref {
               base bw-type;
             }
             description
               "Bandwidth type.  By default, the connection."; bandwidth type
                is set to 'bw-per-cos'.";
           }
           leaf cos-id {
             when "derived-from-or-self(../type, "
                + "'l3vpn-ntw:bw-per-cos')" {
               description
   "Management configuration.";
                 "Relevant when the bandwidth type is set to
                  'bw-per-cos'.";
             }
             type uint8;
             description
  "Management parameters for
               "Identifier of the CoS, indicated by DSCP or a
                CE-VLAN CoS (802.1p) value in the service frame.
                If the bandwidth type is set to 'bw-per-cos',
                the site."; CoS ID MUST also be specified.";
           }
 grouping site-devices {
  container devices
           leaf vpn-id {
             when "derived-from-or-self(../management/type, "+
   "'l3vpn-ntw:provider-managed') or "+
   "derived-from-or-self(../management/type, 'l3vpn-ntw:co-managed')" "derived-from-or-self(../type, "
                + "'l3vpn-ntw:bw-per-svc')" {
               description
   "Applicable only for provider-managed or
   co-managed device.";
                 "Relevant when the bandwidth type is
                  set as bandwidth per VPN service.";
             }
  list device {
   key device-id;
   leaf device-id {
             type svc-id;
             description
    "Identifier for
               "Identifies the target VPN.  If the bandwidth
                type is set as bandwidth per VPN service, the device.";
                vpn-id MUST be specified.";
           }
           leaf location cir {
             type leafref {
     path "../../../locations/"+
     "location/location-id";
    } uint64;
             units "bps";
             mandatory true;
             description
     "Location
               "Committed Information Rate.  The maximum number
                of the device.";
    }
   container management {
    when "derived-from-or-self(../../../management/type,"+
      "'l3vpn-ntw:co-managed')" {
      description
       "Applicable only for co-managed device."; bits that a port can receive or send over
                an interface in one second.";
           }
           leaf address-family cbs {
             type address-family; uint64;
             units "bps";
             mandatory true;
             description
     "Address family used for management.";
               "Committed Burst Size (CBS).  Controls the bursty
                nature of the traffic.  Traffic that does not
                use the configured Committed Information Rate
                (CIR) accumulates credits until the credits
                reach the configured CBS.";
           }
           leaf address {
         when "(../address-family)" eir {
             type uint64;
             units "bps";
             description
           "If address-family is specified, then address should
           also be specified.  If address-family
               "Excess Information Rate (EIR), i.e., excess frame
                delivery allowed that is not specified,
           then address should also not subject to an SLA.
                The traffic rate can be specified."; limited by the EIR.";
           }
           leaf ebs {
             type inet:ip-address;
         mandatory true;
     description
     "Management address.";
     } uint64;
             units "bps";
             description
     "Management configuration.  Applicable only
               "Excess Burst Size (EBS).  The bandwidth available
                for
      co-managed device.";
    }
    description
    "List burst traffic from the EBS is subject to the
                amount of devices requested bandwidth that is accumulated during
                periods when traffic allocated by customer.";
   }
   description
   "Device configuration.";
  }
  description
  "Grouping for device allocation."; the EIR
                policy is not used.";
           }
 grouping site-vpn-flavor {
           leaf site-vpn-flavor pir {
             type identityref {
    base site-vpn-flavor;
   }
   default site-vpn-flavor-single; uint64;
             units "bps";
             description
   "Defines the way the VPN multiplexing
               "Peak Information Rate, i.e., maximum frame
                delivery allowed.  It is done, e.g., whether
   the site belongs equal to a single VPN site or a multiVPN; or, in the case
   of a multiVPN, whether less
                than the logical accesses sum of the sites belong
   to CIR and the same set of VPNs or each logical access maps to
   different VPNs.";
  }
  description
  "Grouping for site VPN flavor.";
 }
 grouping site-maximum-routes {
  container maximum-routes {
   list address-family {
    key af;
    leaf af {
     type address-family;
     description
     "Address family."; EIR.";
           }
           leaf maximum-routes pbs {
             type uint32; uint64;
             units "bps";
             description
     "Maximum prefixes the VRF can accept
     for this address family.";
               "Peak Burst Size.  It is measured in bytes per
                second.";
           }
           description
             "List of address families."; bandwidth values (e.g., per CoS,
              per vpn-id).";
         }
         description
   "Defines 'maximum-routes' for
           "From the VRF.";
  }
  description
  "Defines 'maximum-routes' for customer site's perspective, the site.";
 }
 grouping site-security {
  container security {
   uses site-security-authentication;
   uses site-security-encryption;
   description
   "Site-specific security parameters."; service
            input/output bandwidth of the connection or
            download/upload bandwidth from the SP/site
            to the site/SP.";
      }
          description
  "Grouping for security parameters.";
           " ";
    }

   grouping site-service status-params {
     container service status {
   uses site-service-qos-profile;
   uses site-service-mpls;
   uses site-service-multicast;
       leaf admin-enabled {
         type boolean;
         description
   "Service parameters on the attachment.";
         "Administrative Status UP/DOWN";
       }
       leaf oper-status {
         type operational-type;
         config false;
         description
  "Grouping for service parameters.";
         "Operations status";
       }
 grouping site-network-access-service {
  container service {
   uses site-service-basic;
   /* Extension */
   /* uses svc-bandwidth-params; */
   /* EoExt */
   uses site-service-qos-profile;
   uses site-service-mpls;
   uses site-service-multicast;
       description
   "Service parameters on the attachment."; "";
     }
     description
     "Grouping for service parameters."; used to join operational and administrative status
     is re used in the Site Network Acess and in the VPN-Node";
   }

   /* Parameters related to vpn-nodes (VRF config.) */
    grouping vpn-extranet vpn-nodes-params {
     container extranet-vpns vpn-nodes {
   if-feature extranet-vpn;
       description "";
       list extranet-vpn vpn-node {
         key vpn-id; "vpn-node-id ne-id";

         leaf vpn-id vpn-node-id {
           type svc-id; string;
           description
     "Identifies the target VPN "";
         }

         leaf autonomous-system {
          type uint32;
             description
             "Provider AS number in case the local customer
             requests BGP routing.";
         }

         leaf description {
           type string;
           description
             "Textual description of a VPN want to access."; node.";
         }
         leaf local-sites-role ne-id {
           type string;
           description "";
         }

         leaf router-id {
           type inet:ip-address;
           description
           "router-id information can be ipv4/6 addresses";
         }

         leaf address-family {
          type address-family;
          description
          "Address family used for router-id information.";
         }

         leaf node-role {
           type identityref {
             base site-role;
           }
           default any-to-any-role;
           description
     "This describes the role
           "Role of the
     local sites vpn-node in the target VPN topology.  In the any-to-any VPN
     service topology, the local sites must have the same role, which
     will be 'any-to-any-role'.  In the Hub-and-Spoke VPN service
     topology or the Hub-and-Spoke disjoint VPN service topology,
     the local sites must have a Hub role or a Spoke role."; IP VPN.";
         }
         uses rt-rd;
         uses status-params;
         uses net-acc;
         uses site-maximum-routes;

         leaf node-ie-profile {
           type leafref {
             path "/l3vpn-ntw/vpn-services/"+
                  "vpn-service/ie-profiles/ie-profile/ie-profile-id";
           }
           description
    "List of extranet VPNs or target VPNs the local VPN is
    attached to."; "";
         }
       description
   "Container for extranet VPN "";
       }
     }
     description "Grouping to define VRF-specific configuration.";
    }

   /* Parameters related to import and export profiles (RTs RDs.) */
    grouping ie-profiles-params {
     container ie-profiles {
       list ie-profile {
         key "ie-profile-id";
         leaf ie-profile-id {
           type string;
         description
            "";
         }
         uses rt-rd;
     description
     "";
       }
     description
     "";
     }
     description
     "Grouping for extranet VPN configuration.
  This provides an easy way to interconnect
  all sites from two VPNs."; specify rules for route import and export";
   }

   grouping site-attachment-availability pseudowire-params {
     container availability pseudowire {
       /*leaf far-end {*/
       /*  description "IP of the remote peer of the pseudowire.";*/
       /*  type inet:ip-address;*/
       /*}*/
       leaf access-priority vcid {
         type uint32;
    default 100;
         description
    "Defines the priority for the access.
    The higher the access-priority value,
    the higher the preference of the
    access will be.";
         "PW or VC identifier.";
       }
     description
   "Availability parameters (used for multihoming).";
     "Pseudowire termination parameters";
     }
      description
  "Defines availability parameters for a site.";
     "Grouping pseudowire termination parameters";
   }

   grouping vpn-profile-cfg security-params {
     container valid-provider-identifiers {
   list cloud-identifier security {
    if-feature cloud-access;
    key id;
     leaf id auth-key {
         type string;
         description
     "Identification of cloud service.
     Local administration meaning.";
           "MD5 authentication password for the connection towards the
           customer edge.";
       }
     description
    "List
         "Container for Cloud Identifiers."; aggregating any security parameter for routing
         sessions between a PE and a CE.";
     }
   list encryption-profile-identifier {
    key id;
    leaf id {
     type string;
     description
     "Identification of the SP encryption profile
     "Grouping to be used.  Local administration meaning.";
    }
    description
    "List for encryption profile identifiers."; define security parameters";
   }
   list qos-profile-identifier

 grouping ethernet-params {
   container connection {
    key id;
     leaf id encapsulation-type {
       type string; identityref {
         base encapsulation-type;
       }
       default "untagged-int";
       description
     "Identification of
         "Encapsulation type.  By default, the QoS Profile
          encapsulation type is set to be used.
     Local administration meaning.";
    }
    description
    "List for QoS Profile Identifiers."; 'untagged'.";
     }
   list bfd-profile-identifier
     container tagged-interface {
    key id;
       leaf id type {
         type string; identityref {
           base tagged-inf-type;
         }
         default "priority-tagged";
         description
     "Identification
           "Tagged interface type.  By default,
            the type of the SP BFD Profile to be used.
     Local administration meaning.";
    }
    description
    "List for BFD Profile identifiers."; tagged interface is
            'priority-tagged'.";
       }

   list routing-profile-identifier
       container dot1q-vlan-tagged {
    key id;
    leaf id
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:dot1q')" {
     type string;
           description
     "Identification of
             "Only applies when the routing Profile to be used
     by type of the routing-protocols within sites and site-
     network-accesses. Local administration meaning."; tagged
              interface is 'dot1q'.";
         }
         if-feature "dot1q";
         leaf tag-type {
           type identityref {
             base tag-type;
           }
           default "c-vlan";
           description
    "List for Routing Profile Identifiers.";
             "Tag type.  By default, the tag type is
              'c-vlan'.";
           }

     nacm:default-deny-write;
         leaf cvlan-id {
           type uint16;
           description
     "Container for Valid Provider Identifies.";
             "VLAN identifier.";
           }
         description
   "Grouping for VPN Profile configuration.";
           "Tagged interface.";
       }
 grouping vpn-svc-cfg
       container priority-tagged {
  leaf vpn-id
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:priority-tagged')" {
   type svc-id;
           description
   "VPN identifier.  Local administration meaning.";
             "Only applies when the type of the tagged
              interface is 'priority-tagged'.";
         }
         leaf customer-name tag-type {
           type string; identityref {
             base tag-type;
           }
           default "c-vlan";
           description
   "Name of the customer that actually uses the VPN service.
   In
             "Tag type.  By default, the case that any intermediary (e.g., Tier-2 provider
   or partner) sells tag type is
              'c-vlan'.";
         }
         description
           "Priority tagged.";
       }
       container qinq {
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:qinq')" {
           description
             "Only applies when the VPN service to their end user
   on behalf type of the original service provider (e.g., Tier-1
   provider), the original service provider may require the
   customer name to provide smooth activation/commissioning
   and operation for the service."; tagged
              interface is 'qinq'.";
         }
         if-feature "qinq";
         leaf vpn-service-topology tag-type {
           type identityref {
             base vpn-topology; tag-type;
           }
           default any-to-any; "c-s-vlan";
           description
   "VPN service topology.";
             "Tag type.  By default, the tag type is
              'c-s-vlan'.";
         }
         leaf description svlan-id {
           type string;
    description
      "Textual description of a VPN service.";
  }

  uses ie-profiles-params;
  uses vpn-nodes-params;
  uses vpn-service-cloud-access;
  uses vpn-service-multicast;
  uses vpn-service-mpls;
  uses vpn-extranet; uint16;
           mandatory true;
           description
  "Grouping for VPN service configuration.";
             "SVLAN identifier.";
         }
 grouping site-top-level-cfg
         leaf cvlan-id {
  uses operational-requirements;
  uses customer-location-info;
  uses site-devices;
  uses site-diversity;
  uses site-management;
  uses site-vpn-flavor;
  uses site-maximum-routes;
  uses site-security;
  uses site-service;
  uses site-protection;
  uses site-routing;
           type uint16;
           mandatory true;
           description
             "CVLAN identifier.";
         }
         description
  "Grouping for site top-level configuration.";
           "QinQ.";
       }
 grouping site-network-access-top-level-cfg
       container qinany {

  /* Extension */

  uses status-params;

  /* End
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:qinany')" {
           description
             "Only applies when the type of Extension */ the tagged
              interface is 'qinany'.";
         }
         if-feature "qinany";
         leaf site-network-access-type tag-type {
           type identityref {
             base site-network-access-type; tag-type;
           }
           default point-to-point; "s-vlan";
           description
   "Describes
             "Tag type.  By default, the tag type of connection, e.g.,
   point-to-point or multipoint."; is
              's-vlan'.";
         }
  choice location-flavor {
   case location {
    when "derived-from-or-self(../../management/type, "+
     "'l3vpn-ntw:customer-managed')"
         leaf svlan-id {
           type uint16;
           mandatory true;
           description
     "Applicable only
             "Service VLAN ID.";
         }
         description
           "Container for customer-managed device."; QinAny.";
       }
    leaf location-reference
       container vxlan {
     type leafref
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:vxlan')" {
      path "../../../locations/location/location-id";
     }
           description
     "Location
             "Only applies when the type of the site-network-access.";
    } tagged
              interface is 'vxlan'.";
         }
   case device {
    when "derived-from-or-self(../../management/type, "+
     "'l3vpn-ntw:provider-managed') or "+
     "derived-from-or-self(../../management/type, "+
     "'l3vpn-ntw:co-managed')"
         if-feature "vxlan";
         leaf vni-id {
           type uint32;
           mandatory true;
           description
     "Applicable only for provider-managed or co-managed device.";
             "VXLAN Network Identifier (VNI).";
         }
         leaf device-reference peer-mode {
           type leafref identityref {
      path "../../../devices/device/device-id";
             base vxlan-peer-mode;
           }
           default "static-mode";
           description
     "Identifier of CE
             "Specifies the VXLAN access mode.  By default,
              the peer mode is set to use."; 'static-mode'.";
         }
         list peer-list {
           key "peer-ip";
           leaf peer-ip {
             type inet:ip-address;
             description
               "Peer IP.";
           }
   mandatory true;
           description
   "Choice
             "List of how to describe the site's location."; peer IP addresses.";
         }
  uses access-diversity;
  uses site-attachment-bearer;
  uses site-attachment-ip-connection;
  uses site-security;
  uses site-network-access-service;
  uses site-routing;
  uses site-attachment-availability;
         description
  "Grouping
           "QinQ.";
       }
       description
         "Container for site network access top-level configuration."; tagged interfaces.";
     }

 /* Extensions */

  /* Bearers in a site */
   grouping site-bearer-params {
     container site-bearers {
      list bearer {
        key "bearer-id";
      leaf bearer-id bearer-reference {
       if-feature bearer-reference;
       type string;
        description "";
        "This is an internal reference for the SP.";
      }

        leaf BearerType
        uses pseudowire-params {
        type identityref
          when "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/"+
          "vpn-node/vpn-network-accesses/vpn-network-access/"+
          "vpn-network-access-type ='pseudowire'"
         {
          base bearer-inf-type;
           description "pseudowire specific parameters";
           }
        }
     description
          "Request for an Bearer access type.

          Choose between port or lag connection type.";
     "Defines physical properties of a site attachment.";
     }

        leaf ne-id {
          type string;
     description
          "NE-id reference.";
     "Encapsulation types";
   }

        leaf port-id {
          type string;
     description
          "Port-id in format slot/ card /port.";
     "Grouping to define encapsulation types";
 }

 grouping rt-rd {
   leaf lag-id rd {
     type string;
          description
          "lag-id in format id.";
        } rt-types:route-distinguisher;
     description
    "Parameters used to identify each bearer";
     "";
     }
     container vpn-targets {
     description
    "Grouping
     "Set of route-targets to reuse the site bearer assigment"; match for import and export routes
      to/from VRF";
      uses rt-types:vpn-route-targets;
      }
   description
    "Grouping to reuse the site bearer assigment";
   "";
 }

   /* UNUSED */

 grouping svc-bandwidth-params { net-acc{
 container svc-bandwidth vpn-network-accesses {
        if-feature "input-bw";
      list bandwidth vpn-network-access {
       key "direction type"; vpn-network-access-id;
       leaf direction vpn-network-access-id {
        type identityref {
              base bw-direction;
            } svc-id;
        description
              "Indicates the bandwidth direction.  It can be
               the bandwidth download direction from the SP to
               the site or the bandwidth upload direction from
               the site to
        "Identifier for the SP."; access.";
       }
       leaf type description {
         type identityref {
              base bw-type;
            } string;
         description
              "Bandwidth type.  By default, the bandwidth type
               is set to 'bw-per-cos'.";
           "Textual description of a VPN service.";
       }
          leaf cos-id {
            when "derived-from-or-self(../type, "
               + "'l3vpn-ntw:bw-per-cos')" {
       uses site-network-access-top-level-cfg;
       description
                "Relevant when the bandwidth type is set to
                 'bw-per-cos'.";
       "List of accesses for a site.";
      }
            type uint8;
      description
              "Identifier
      "List of the CoS, indicated by DSCP or accesses for a
               CE-VLAN CoS (802.1p) value in the service frame.
               If the bandwidth type is set to 'bw-per-cos', site.";
      }
      description
      "Main block of the CoS ID MUST also be specified."; Network Access.";
 }
          leaf vpn-id

  /* Main blocks */
  container l3vpn-ntw {
            when "derived-from-or-self(../type, "
               + "'l3vpn-ntw:bw-per-svc')"
   container vpn-profiles {
    uses vpn-profile-cfg;
     description
     "Container for VPN Profiles.";
   }
   container vpn-services {
    list vpn-service {
     key vpn-id;
     uses vpn-svc-cfg;
     description
     "List of VPN services.";
    }
    description
                "Relevant when
    "Top-level container for the bandwidth type is
                 set as bandwidth per VPN service."; services.";
   }
            type svc-id;
   description
              "Identifies
   "Main container for L3VPN service configuration.";
  }
 }
 <CODE ENDS>

                                 Figure 15

8.  IANA Considerations

   This document requests IANA to register the target VPN.  If following URI in the bandwidth
               type is set as bandwidth per VPN service, "ns"
   subregistry within the
               vpn-id MUST be specified.";
          }
          leaf cir {
            type uint64;
            units "bps";
            mandatory true;
            description
              "Committed Information Rate. "IETF XML Registry" [RFC3688]:

      URI: urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw

      Registrant Contact: The maximum number
               of bits that a port can receive or send over IESG.

      XML: N/A; the requested URI is an interface XML namespace.

   This document requests IANA to register the following YANG module in one second.";
          }
          leaf cbs {
            type uint64;
            units "bps";
            mandatory true;
            description
              "Committed Burst Size (CBS).  Controls
   the bursty
               nature of "YANG Module Names" subregistry [RFC6020] within the traffic.  Traffic "YANG
   Parameters" registry.

      name: ietf-l3vpn-ntw

      namespace: urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw

      maintained by IANA: N

      prefix: l3nm

      reference: RFC XXXX

9.  Security Considerations

   The YANG module specified in this document defines a schema for data
   that does not
               use is designed to be accessed via network management protocols such
   as NETCONF [RFC6241] or RESTCONF [RFC8040] .  The lowest NETCONF
   layer is the configured Committed Information Rate
               (CIR) accumulates credits until secure transport layer, and the credits
               reach mandatory-to-implement
   secure transport is Secure Shell (SSH) [RFC6242].  The lowest
   RESTCONF layer is HTTPS, and the configured CBS.";
          }
          leaf eir {
            type uint64;
            units "bps";
            description
              "Excess Information Rate (EIR), i.e., excess frame
               delivery allowed that mandatory-to-implement secure
   transport is not subject TLS [RFC8466].

   The Network Configuration Access Control Model (NACM) [RFC8341]
   provides the means to an SLA. restrict access for particular NETCONF or
   RESTCONF users to a preconfigured subset of all available NETCONF or
   RESTCONF protocol operations and content.

   The traffic rate ietf-l3vpn-ntw module is used to manage L3 VPNs in a service
   provider backbone network.  Hence, the module can be limited by used to request,
   modify, or retrieve L3VPN services.  For example, the EIR.";
          } creation of a
   vpn-service leaf ebs {
            type uint64;
            units "bps";
            description
              "Excess Burst Size (EBS).  The bandwidth available
               for burst traffic from instance triggers the EBS is subject creation of an L3 VPN Service
   in a Service Provider Network.

   Due to the
               amount foreseen use of bandwidth the YANG module, there are a number of
   data nodes defined in this YANG module that are writable/creatable/
   deletable (i.e., config true, which is accumulated during
               periods when traffic allocated by the EIR
               policy is not used.";
          }
          leaf pir {
            type uint64;
            units "bps";
            description
              "Peak Information Rate, i.e., maximum frame
               delivery allowed.  It is equal default).  These data
   nodes MAY be considered sensitive or vulnerable in some network
   environments.  Write operations (e.g., edit-config) and delete
   operations to these data nodes without proper protection or less
               than the sum of
   authentication can have a negative effect on network operations.
   These are the CIR subtrees and data nodes and their sensitivity/
   vulnerability in the EIR.";
          }
          leaf pbs {
            type uint64;
            units "bps";
            description
              "Peak Burst Size.  It ietf-l3vpn-ntw module:

   o  vpn-service: An attacker who is measured in bytes per
               second.";
          }
          description
            "List of bandwidth values (e.g., per CoS,
             per vpn-id).";
        }
        description
          "From able to access network nodes can
      undertake various attacks, such as deleting a running L3 VPN
      Service, interrupting all the customer site's perspective, traffic of a client.  In addition,
      an attacker may modify the attributes of a running service
           input/output bandwidth (e.g.,
      QoS, bandwidth, routing protocols), leading to malfunctioning of
      the connection or
           download/upload bandwidth from the SP/site service and therefore to the site/SP.";
     }
         description
          " ";
   }

  grouping status-params {
    container status {
      leaf admin-enabled {
        type boolean;
        description
        "Administrative Status UP/DOWN";
      }
      leaf oper-status {
        type operational-type;
        config false;
        description
        "Operations status";
      }
      description "";
    }
    description
    "Grouping used SLA violations.  In addition, an
      attacker could attempt to join operational and administrative status
    is re used in the Site Network Acess create a L3 VPN Service.  Such activity
      can be detected by monitoring and tracking network configuration
      changes.

   o  COMPLETE rest of critical data nodes and subtrees

   Some of the readable data nodes in this YANG module may be considered
   sensitive or vulnerable in some network environments.  It is thus
   important to control read access (e.g., via get, get-config, or
   notification) to these data nodes.  These are the VPN-Node";
  }

  /* Parameters subtrees and data
   nodes and their sensitivity/vulnerability:

   o  customer-name and ip-connection: An attacker can retrieve privacy-
      related to vpn-nodes (VRF config.) */
   grouping vpn-nodes-params {
    container vpn-nodes {
      description "";

      list vpn-node {
        key "vpn-node-id ne-id";

        leaf vpn-node-id {
          type string;
          description "";
        }

        leaf description {
          type string;
          description
            "Textual description of a VPN node.";
        }

        leaf ne-id {
          type string;
          description "";

        }

        leaf router-id {
          type inet:ip-address;
          description
          "router-id information which can be ipv4/6 addresses";
        }

        leaf address-family {
         type address-family;
         description
         "Address family used for router-id information.";
        }

        leaf node-role {
          type identityref {
            base site-role;
          }
          default any-to-any-role;
          description
          "Role to track a customer.
      Disclosing such information may be considered as a violation of
      the vpn-node in the IP VPN.";
        }
        uses rt-rd;
        uses status-params;

        /* Here we use customer-provider trust relationship.

   Summing up, the name given to foreseen risks of using the existing structure in sites */
        uses site-maximum-routes;

        leaf node-ie-profile {
          type leafref {
            path "/l3vpn-ntw/vpn-services/"+
                 "vpn-service/ie-profiles/ie-profile/ie-profile-id";
          }
          description "";
        }
      description "";
      }
    }
    description "Grouping to define VRF-specific configuration.";
   }

  /* Parameters related l3vpn-ntw module can be
   clasified into:

   o  Malicious clients attempting to import and export profiles (RTs RDs.) */
   grouping ie-profiles-params {
    container ie-profiles {
      list ie-profile {
        key "ie-profile-id";
        leaf ie-profile-id {
          type string;

        description
           "";
        }
        uses rt-rd;
    description
    "";
      }
    description
    "";
    }
    description
    "Grouping delete or modify services

   o  Unauthorized clients attempting to specify rules for route import and export";
  }

  grouping pseudowire-params {
    container pseudowire {
      /*leaf far-end {*/
      /*  description "IP create/modify/delete a service

   o  Unauthorized clients attempting to read service information

10.  Implementation Status

10.1.  Nokia Implementation

   Nokia has a draft implementation of the remote peer IETF L3NM model.

   The implementation is a prototype and is currently being planned for
   production.

   Nokia NSP (Network Services Platform) supports integration of
   standard models with the pseudowire.";*/
      /*  type inet:ip-address;*/
      /*}*/
      leaf vcid {
        type uint32;
        description
        "PW Intent Manager framework.  NSP platform
   provides hot pluggable model definitions and implementations which
   would enable defining models where standardization is in progress or VC identifier.";
      }
    description
    "Pseudowire termination parameters";
    }
     description
    "Grouping pseudowire termination parameters";
  }

  grouping security-params {
    container security {
    leaf auth-key {
        type string;
        description
          "MD5 authentication password for the connection towards the
          customer edge.";
      }
    description
        "Container for aggregating any security parameter
   non-existent.  With pluggable architecture for routing
        sessions between a PE model and
   implementation injections, NSP also serves as a CE.";
    }
    description
    "Grouping Multi-Layer, Multi-
   Domain controller.

   The Nokia implementation of L3NM covers, the following
   a) RESTConf support

   b) Configuration of L3 IP VPN Services.  Create/Get/Query/Delete
   supported on the following operations.

   * Site

   * Site-Bearer

   * VpnService

   * IEProfile

   * VpnNode

   * Site Network Access

   * Site Attachments

   c) Supports translations to define security parameters";
  }

grouping ethernet-params {
  container connection {
    leaf encapsulation-type {
      type identityref {
        base encapsulation-type;
      }
      default "untagged-int";
      description
        "Encapsulation type.  By default, the
         encapsulation type Device Model (Standard /
   Properietary)

   draft-ietf-opsawg-l3sm-l3nm-00

   The current implementation is set proprietary, so under no terms the
   current implementation can be used.

   Contact information: Sriram Krishnamurthy
   (sriram.krishnamurthy@nokia.com)

10.2.  Huawei Implementation

   The organization responsible for the implementation, if any.

   Huawei Technologies Co.,Ltd.

   The implementation's name and/or a link to 'untagged'.";
    }
    container tagged-interface {
      leaf type {
        type identityref {
          base tagged-inf-type;
        }
        default "priority-tagged";
        description
          "Tagged interface type.  By default, a web page where the type
   implementation or a description of the tagged interface it can be found.

   NCE V1R19C00

   A brief general description.

   This section provides an implementation report summary for Layer 3
   VPN Network Model.  Layer 3 VPN Network Model is
           'priority-tagged'.";
      }
      container dot1q-vlan-tagged {
        when "derived-from-or-self(../type, "
           + "'l3vpn-ntw:dot1q')" {
          description
            "Only applies when the type available at:
   https://tools.ietf.org/html/draft-ietf-opsawg-l3sm-l3nm-00
   The implementation's level of maturity: research, prototype, alpha,
   beta, production, widely used, etc.

   Right now, the tagged
             interface data model is 'dot1q'.";
        }
        if-feature "dot1q";
        leaf tag-type {
          type identityref {
            base tag-type;
          }
          default "c-vlan";
          description
            "Tag type.  By default, the tag type still subject to change, therefore it is
             'c-vlan'.";
          }
        leaf cvlan-id {
          type uint16;
          description
            "VLAN identifier.";
          }
        description
          "Tagged interface.";
      }
      container priority-tagged {
        when "derived-from-or-self(../type, "
           + "'l3vpn-ntw:priority-tagged')" {
          description
            "Only applies when the type
   still a Prototype, not put into production yet.

   Coverage: which parts of the tagged
             interface is 'priority-tagged'.";
        }
        leaf tag-type {
          type protocol specification are implemented.

   We have implemented pruned L3NM model with the following parameters

   module: ietf-l3vpn-ntw
   +--rw l3vpn-ntw
      +--rw vpn-profiles
      |  +--rw valid-provider-identifiers
      |     +--rw qos-profile-identifier* [id]
      |     |  +--rw id    string
      +--rw vpn-services
      |  +--rw vpn-service* [vpn-id]
      |     +--rw vpn-id                  svc-id
      |     +--rw vpn-service-topology?   identityref
      |     +--rw description?            string
      |     +--rw vpn-nodes
      |     |  +--rw vpn-node* [vpn-node-id ne-id]
      |     |     +--rw vpn-node-id        string
      |     |     +--rw description?       string
      |     |     +--rw ne-id              string
      |     |     +--rw node-role?         identityref
      |     |     +--rw rd?                rt-types:route-distinguisher
      |     |     +--rw vpn-targets
      |     |     +--rw maximum-routes
      |     |     |  +--rw address-family* [af]
      |     |     |     +--rw af                address-family
      |     |     |     +--rw maximum-routes?   uint32
      +--rw sites
         +--rw site* [site-id]
            +--rw site-id                  svc-id
            +--rw locations
            |  +--rw location* [location-id]
            |     +--rw location-id     svc-id
            +--rw site-bearers
            |  +--rw bearer* [bearer-id]
            |     +--rw bearer-id    string
            |     +--rw ne-id?       string
            |     +--rw port-id?     string
            +--rw site-network-accesses
               +--rw site-network-access* [site-network-access-id]
                  +--rw site-network-access-id      svc-id
                  +--rw site-network-access-type?   ref
                  +--rw bearer
                  |  +--rw bearer-reference?   {bearer-reference}?
                  |  +--rw connection
                  |  |  +--rw encapsulation-type?   identityref {
            base tag-type;
          }
          default "c-vlan";
          description
            "Tag type.  By default, the tag type is
             'c-vlan'.";
        }
        description
          "Priority tagged.";
      }
      container qinq {
        when "derived-from-or-self(../type, "
           + "'l3vpn-ntw:qinq')" {
          description
            "Only applies when the type of the tagged
             interface is 'qinq'.";
        }
        if-feature "qinq";
        leaf tag-type {
          type
                  |  |  +--rw tagged-interface
                  |  |     +--rw type?                identityref {
            base tag-type;
          }
          default "c-s-vlan";
          description
            "Tag type.  By default, the tag type is
             'c-s-vlan'.";
        }
        leaf svlan-id {
          type uint16;
          mandatory true;
          description
            "SVLAN identifier.";
        }
        leaf
                  |  |     +--rw dot1q-vlan-tagged {dot1q}?
                  |  |     |  +--rw cvlan-id {
          type uint16;
          mandatory true;
          description
            "CVLAN identifier.";
        }
        description
          "QinQ.";
      }
      container qinany {
        when "derived-from-or-self(../type, "
           + "'l3vpn-ntw:qinany')" {
          description
            "Only applies when the type of the tagged
             interface is 'qinany'.";
        }
        if-feature "qinany";
        leaf tag-type {
          type identityref {
            base tag-type;
          }
          default "s-vlan";
          description
            "Tag type.  By default, the tag type is
             's-vlan'.";
        }
        leaf    uint16
                  |  |     +--rw qinq {qinq}?
                  |  |     |  +--rw svlan-id {
          type uint16;
          mandatory true;
          description
            "Service VLAN ID.";
        }
        description
          "Container for QinAny.";
      }
      container vxlan {
        when "derived-from-or-self(../type, "
           + "'l3vpn-ntw:vxlan')" {
          description
            "Only applies when the type of the tagged
             interface is 'vxlan'.";
        }
        if-feature "vxlan";
        leaf vni-id {
          type uint32;
          mandatory true;
          description
            "VXLAN Network Identifier (VNI).";
        }
        leaf peer-mode {    uint16
                  |  |     |  +--rw cvlan-id    uint16
                  +--rw ip-connection
                  |  +--rw ipv4 {ipv4}?
                  |  |  +--rw dhcp-relay
                  |  |  |  +--rw customer-dhcp-servers
                  |  |  |     +--rw server-ip-address*   inet
                  |  |  +--rw addresses
                  |  |     +--rw provider-address?   inet:ipv4-address
                  |  |     +--rw customer-address?   inet:ipv4-address
                  |  |     +--rw prefix-length?      uint8
                  +--rw service
                  |  +--rw qos {qos}?
                  |  |  +--rw qos-profile
                  |  |     +--rw (qos-profile)?
                  |  |        +--:(standard)
                  |  |        |  +--rw profile?   leafreaf
                  +--rw routing-protocols
                  |  +--rw routing-protocol* [type]
                  |     +--rw type                identityref {
            base vxlan-peer-mode;
          }
          default "static-mode";
          description
            "Specifies the VXLAN access mode.  By default,
             the peer mode is set to 'static-mode'.";
        }
        list peer-list {
          key "peer-ip";
          leaf peer-ip {
            type inet:ip-address;
            description
              "Peer IP.";
          }
          description
            "List of peer IP addresses.";
        }
        description
          "QinQ.";
      }
      description
        "Container for tagged interfaces.";
    }
    description
    "Encapsulation types";
  }
    description
    "Grouping to define encapsulation types";
}

grouping rt-rd {
  leaf rd {
    type rt-types:route-distinguisher;
    description
    "";
    }
    container vpn-targets {
    description
    "Set of route-targets to match for import and export routes
     to/from VRF";
     uses rt-types:vpn-route-targets;
     }
  description
  "";
}

 /* Main blocks */
 container l3vpn-ntw {
  container vpn-profiles {
   uses vpn-profile-cfg;
    description
    "Container for VPN Profiles.";

  }
  container vpn-services {
   list vpn-service {
    key vpn-id;
    uses vpn-svc-cfg;
    description
    "List of
                  |     +--rw ospf {rtg-ospf}?
                  |     |  +--rw address-family*   address-family
                  |     |  +--rw area-address      yang:dotted-quad
                  |     |  +--rw metric?           uint16
                  |     |  +--rw security
                  |     |  |  +--rw auth-key?   string
                  |     +--rw bgp {rtg-bgp}?
                  |     |  +--rw autonomous-system    uint32
                  |     |  +--rw address-family*      address-family
                  |     |  +--rw neighbor?            inet:ip-address
                  |     |  +--rw multihop?            uint8
                  |     |  +--rw security
                  |     |     +--rw auth-key?   string
                  |     +--rw static
                  |     |  +--rw cascaded-lan-prefixes
                  |     |     +--rw ipv4-lan-prefixes*  {ipv4}?
                  |     |     |  +--rw lan         inet:ipv4-prefix
                  |     |     |  +--rw lan-tag?    string
                  |     |     |  +--rw next-hop    inet:ipv4-address
                  +--rw node-id?                    leafreaf
                  +--rw service-id?                 leafreaf
                  +--rw access-group-id?            yang:uuid

                                 Figure 16

   Use Cases we have implemented include:

   (a).Create VPN services.";
   }
   description
   "Top-level container for the

   (b).Create Site

   (c).Create/add bearers to an existing Site

   (d).Create/Include Site Network Access into VPN services.";
  }
  container sites {
   list site {
    key site-id;
    leaf site-id {
     type svc-id;
     description
     "Identifier of the site.";
    }
    leaf description {
      type string;
      description
        "Textual description of a site.";
    }
    uses site-top-level-cfg;
    uses operational-requirements-ops;
    uses site-bearer-params;
    container site-network-accesses {
     list site-network-access {
      key site-network-access-id;
      leaf site-network-access-id {
       type svc-id;
       description
       "Identifier for the access.";
      }
      leaf description {
        type string;
        description
          "Textual description nodes.

   Version compatibility: what version/versions of a VPN service.";
      }
      uses site-network-access-top-level-cfg;
      leaf node-id {
        type leafref{
          path "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn-node-id";
            }
          description
          "Reference the VPN node id";
          }

      leaf service-id {
        type leafref{
          path "/l3vpn-ntw/vpn-services/vpn-service/vpn-id";
          }
        description
        "Reference Internet-Draft
   are known to be implemented.

   draft-ietf-opsawg-l3sm-l3nm-00

   Licensing: the VPN node id";
        }
      leaf access-group-id {
          type yang:uuid;
          description
          "Reference terms under which the Access Goup ID.
          It is used implementation can be used.  For
   example: proprietary, royalty licensing, freely distributable with
   acknowledgement (BSD style), freely distributable with requirement to group
   redistribute source (General Public License (GPL) style), and identify SNA other
   (specify).

   Not available yet.

   Implementation experience: any useful information the implementers
   want to share with common behavior
          such as dual-homming";
        }
      description
      "List of accesses for the community.

   Contact information: ideally a site.";
     }
     description
     "List of accesses person's name and email address, but
   possibly just a URL or mailing list.

   Qin Wu (bill.wu@huawei.com)

   The date when information about this particular implementation was
   last updated.

   2019-09-30

   List other implementations that have been tested for
   interoperability.

   Nokia

10.3.  Infinera Implementation

   Infinera has a site.";
    }
    description
    "List draft implementation of sites.";
   }
   description
   "Container for sites.";
  }
  description
  "Main container for L3VPN service configuration.";
   }
  }

                                 Figure 4

6.  IANA CONSIDERATIONS

   This memo includes no request to IANA.

7.  SECURITY CONSIDERATIONS

   All the security considerations of [RFC8299] apply to this document.
   Subsequent versions will provide additional security considerations.

8.  IMPLEMENTATION STATUS

   This section will be used to track IETF L3NM model.  The
   implementation is in beta state and is currently being tested and
   integrated with other suppliers controllers supporting this same
   model.  Infinera is supporting the status L3NM model in its Transcend
   Maestro Multi-layer, Multi-domain Controller.

   The Infinera implementation of the implementations L3NM covers discovery and
   configuration of IP VPN services, and is supporting both North-Bound
   (server) and South-Bound (client) functionality.  Versions 01 and 02
   of the model.  It model are supported.

   The current implementation is aimed at being removed if proprietary, so under no terms the document becomes
   RFC.

9.  ACKNOWLEDGEMENTS
   current implementation can be used.

   Contact information: Janne Karvonen (JKarvonen@infinera.com)

   26 October is the date when information about this particular
   implementation was last updated.

11.  Acknowledgements

   Thanks to Adrian Farrel and Miguel Cros for the suggestions on the
   document.  Thanks to Stephane Litowski and Philip Eardlay for the review.  Lots of thanks
   for the discussions on opsawg mailing list and at IETF meeting.  Some of the comments have already been
   incorported and the other part of the comments will be addressed in
   the next versions.

   This work was supported in part by the European Commission funded
   H2020-ICT-2016-2 METRO-HAUL project (G.A. 761727).

10.  CONTRIBUTORS

12.  Contributors

   Samier Barguil
   Telefonica
   Email: samier.barguilgiraldo.ext@telefonica.com

   Daniel King
   Old Dog Consulting
   Email: daniel@olddog.co.uk

   Samier Barguil
   Telefonica
   Email: samier.barguilgiraldo.ext@telefonica.com

   Luay Jalil
   Verizon
   Email: luay.jalil@verizon.com

   Qin Wu
   Huawei
   Email: bill.wu@huawei.com>

11.
   Mohamed Boucadair
   Orange
   Email: mohamed.boucadair@orange.com>

   Stephane Litkowski
   Cisco
   Email: slitkows@cisco.com>

13.  References

13.1.  Normative References

11.1.  NORMATIVE REFERENCES

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

11.2.  INFORMATIVE REFERENCES

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <https://www.rfc-editor.org/info/rfc6020>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <https://www.rfc-editor.org/info/rfc6241>.

   [RFC6242]  Wasserman, M., "Using the NETCONF Protocol over Secure
              Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
              <https://www.rfc-editor.org/info/rfc6242>.

   [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
              RFC 7950, DOI 10.17487/RFC7950, August 2016,
              <https://www.rfc-editor.org/info/rfc7950>.

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8341]  Bierman, A. and M. Bjorklund, "Network Configuration
              Access Control Model", STD 91, RFC 8341,
              DOI 10.17487/RFC8341, March 2018,
              <https://www.rfc-editor.org/info/rfc8341>.

   [RFC8466]  Wen, B., Fioccola, G., Ed., Xie, C., and L. Jalil, "A YANG
              Data Model for Layer 2 Virtual Private Network (L2VPN)
              Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October
              2018, <https://www.rfc-editor.org/info/rfc8466>.

13.2.  Informative References

   [RFC4026]  Andersson, L. and T. Madsen, "Provider Provisioned Virtual
              Private Network (VPN) Terminology", RFC 4026,
              DOI 10.17487/RFC4026, March 2005,
              <https://www.rfc-editor.org/info/rfc4026>.

   [RFC4076]  Chown, T., Venaas, S., and A. Vijayabhaskar, "Renumbering
              Requirements for Stateless Dynamic Host Configuration
              Protocol for IPv6 (DHCPv6)", RFC 4076,
              DOI 10.17487/RFC4076, May 2005,
              <https://www.rfc-editor.org/info/rfc4076>.

   [RFC4176]  El Mghazli, Y., Ed., Nadeau, T., Boucadair, M., Chan, K.,
              and A. Gonguet, "Framework for Layer 3 Virtual Private
              Networks (L3VPN) Operations and Management", RFC 4176,
              DOI 10.17487/RFC4176, October 2005,
              <https://www.rfc-editor.org/info/rfc4176>.

   [RFC8299]  Wu, Q., Ed., Litkowski, S., Tomotaki, L., and K. Ogaki,
              "YANG Data Model for L3VPN Service Delivery", RFC 8299,
              DOI 10.17487/RFC8299, January 2018,
              <https://www.rfc-editor.org/info/rfc8299>.

   [RFC8309]  Wu, Q., Liu, W., and A. Farrel, "Service Models
              Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018,
              <https://www.rfc-editor.org/info/rfc8309>.

   [RFC8340]  Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
              BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
              <https://www.rfc-editor.org/info/rfc8340>.

   [RFC8453]  Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for
              Abstraction and Control of TE Networks (ACTN)", RFC 8453,
              DOI 10.17487/RFC8453, August 2018,
              <https://www.rfc-editor.org/info/rfc8453>.

   [RFC8466]  Wen, B., Fioccola, G., Ed., Xie, C., and L. Jalil, "A YANG
              Data Model for Layer 2 Virtual Private Network (L2VPN)
              Service Delivery", RFC 8466, DOI 10.17487/RFC8466, October
              2018, <https://www.rfc-editor.org/info/rfc8466>.

Authors' Addresses

   Alejandro Aguado
   Nokia
   Madrid
   ES

   Email: alejandro.aguado_martin@nokia.com

   Oscar Gonzalez de Dios (editor)
   Telefonica
   Madrid
   ES

   Email: oscar.gonzalezdedios@telefonica.com

   Victor Lopez
   Telefonica
   Madrid
   ES

   Email: victor.lopezalvarez@telefonica.com

   Daniel Voyer
   Bell Canada
   CA

   Email: daniel.voyer@bell.ca

   Luis Angel Munoz
   Vodafone
   ES

   Email: luis-angel.munoz@vodafone.com