Internet Engineering Task Force                          S. Barguil, Ed.
Internet-Draft                                  O. Gonzalez de Dios, Ed.
Intended status: Standards Track                              Telefonica
Expires: January 3, May 6, 2021                                        M. Boucadair
                                                                  Orange
                                                                L. Munoz
                                                                Vodafone
                                                                L. Jalil
                                                                 Verizon
                                                                   J. Ma
                                                            China Unicom
                                                           July
                                                       November 02, 2020

                    A Layer 2 VPN Network YANG Model
                       draft-ietf-opsawg-l2nm-00
                       draft-ietf-opsawg-l2nm-01

Abstract

   This document defines a YANG Data model (called, L2NM) that can be
   used to manage the provisioning of Layer 2 VPN services within a
   Service Provider Network.  This YANG module provides representation
   of the Layer 2 VPN Service from a network standpoint.  The module is
   meant to be used by a Network Controller to derive the configuration
   information that will be sent to relevant network devices.

   The L2NM YANG Data model complements the Layer 2 Service Model
   (RFC8466) by providing a network-centric view of the service that is
   internal to a Service Provider.

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 January 3, May 6, 2021.

Copyright Notice

   Copyright (c) 2020 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  . . . . . . . . . . . . . . . . . . . . . . . .   2   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Reference architecture  . . . . . . . . . . . . . . . . . . .   4
   3.  Description of the L2NM YANG Module . . . . . . . . . . . . .   7   8
     3.1.  Structure of the Module . . . . . . . . . . . . . . . . .   7   8
     3.2.  VPN Profiles  . . . . . . . . . . . . . . . . . . . . . .   8
     3.3.  L2 VPN Service  . . . . . . . . . . . . . . . . . . . . .   7
       3.2.1.   9
       3.3.1.  L2 VPN Service Types  . . . . . . . . . . . . . . . .   8
       3.2.2.  11
       3.3.2.  Underlying Transport Selection  . . . . . . . . . . .   9
       3.2.3.  Other relevant  11
       3.3.3.  VPN Node  . . . . . . . . . . . . . . . . . . . . . .  11
         3.3.3.1.  Signaling options . . . . . . . . . . . . . . . .  13
         3.3.3.2.  VPN Network Parameters Access  . . . . . . . . . .   9
     3.3.  L2NM Module Tree . . . . .  15
           3.3.3.2.1.  Connection  . . . . . . . . . . . . . . .  10 . .  18
           3.3.3.2.2.  Layer 2 service requirements  . . . . . . . .  19
   4.  Relation with other YANG Models . . . . . . . . . . . . . . .  18  23
     4.1.  Relation with L2SM  . . . . . . . . . . . . . . . . . . .  18  23
     4.2.  Relation with Network Topology  . . . . . . . . . . . . .  18  23
     4.3.  Relation with Device Models . . . . . . . . . . . . . . .  18  23
   5.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .  19  24
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  89  60
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  89  60
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  89  61
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  90  61
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  91  62
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  91  62
     10.2.  Informative References . . . . . . . . . . . . . . . . .  92  63
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  92  64

1.  Introduction

   [RFC8466] defines a L2VPN Service Model (L2SM) YANG data model that
   can be used for L2VPN service ordering matters between customers and
   Service Providers (SPs).  This document complements the L2SM model by
   creating a network-centric view of the service which can be exposed
   by a Network to a Service Controller within the Service Provider
   Network.  In particular, the model can 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
   (a.k.a., network controller/orchestrator).

   The data model defined in this document is called the L2VPN Network
   Model (L2NM), playing the role of Service Delivery Model (Figure 3 of
   [RFC8466].  The module supports additional capabilities, such as
   exposing operational parameters, transport protocols selection and
   precedence.  It also serves as a multi-domain orchestration
   interface, because this model can transport resources (i.e., VCID)
   between domains.  The data model keeps minimum customer-related
   information.

   The

   This document uses the common VPN YANG module reuses containers and groupings from L2SM [RFC8466]
   for the cases that the requirements from L2SM can be translated
   directly defined in
   [I-D.ietf-opsawg-vpn-common].

   The YANG data model in this document conforms to L2NM. the Network
   Management Datastore Architecture (NMDA) defined in [RFC8342].

1.1.  Terminology

   This document assumes that the reader is familiar with the contents
   of [RFC6241], [RFC7950], [RFC8466], [RFC8309], and [RFC8453] and uses
   terminology from those documents.  The meaning of the symbols in YANG
   tree diagrams is [RFC8340].

   This document makes use of the following terms:

   o  L2 VPN Customer Service Model (L2SM): Describes the service
      characterization (requirements) of a L2 VPN that interconnects a
      set of sites from the perspective of the customer.  The customer
      service model does not provide details on the Service Provider
      Network.  The L2 VPN Customer Service model is defined in
      [RFC8466].

   o  L2 VPN Service Network Model (L2NM): Refers to the YANG module
      that describes a L2 VPN Service with a network-centric view.  It
      contains information of the Service Provider network and might
      include allocated resources.  It can be used by network
      controllers to manage the Layer 2 VPN Service configuration in the
      Service Provider network.  The YANG module can be consumed by a
      Service Orchestrator to request a VPN Service to a Network
      controller or to expose the list of active L2VPN services.

   o  Service Orchestrator: Refers to a functional entity that interacts
      with the customer of a L2 VPN relying upon, e.g.  L2SM.  The
      Service Orchestrator is responsible of the CE-PE attachment
      circuits, the PE selection, and requesting the activation of the
      L2 VPN service to a network controller.

   o  Network Controller: Denotes a functional entity responsible for
      the management of the service provider network.

   o  VPN node (vpn-node): Is an abstraction that represents a set of
      policies applied on a PE and that belong to a single VPN service
      (vpn-service).  A VPN service involves one or more VPN nodes.  The
      VPN node will identify the Service Provider node on which the VPN
      is deployed.

   o  VPN network access (vpn-network-access): Is an abstraction that
      represents the network interfaces that are associated to a given
      VPN node.  Traffic coming from the VPN network access belongs to
      the VPN.  The attachment circuits (bearers) between CEs and PEs
      are terminated in the VPN network access.

   o  VPN Service Provider (SP): Is a Service Provider that offers VPN-
      related services.

   o  Service Provider Network (SP Network): Is a network able to
      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
   "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 illustrates how L2NM is used.  As a reminder, this figure is
   an expansion of the architecture presented in Section 3 of [RFC8466]
   and decomposes the box marked "orchestration" in that figure into
   three separate functional components called "Service Orchestration",
   "Network Orchestration", and "Domain Orchestration".

   The reader may refer to [RFC8309] for the distinction between the
   "Customer Service Model", the "Service Delivery Model", the "Network
   Configuration Model", and the "Device Configuration Model".  The
   "Domain Orchestration" and "Config Manager" roles may be performed by
   "SDN Controllers".

                             +---------------+
                             |   Customer    |
                             +---------------+
             Customer Service Model  |
                    l2vpn-svc        |
                             +---------------+
                             |    Service    |
                             | Orchestration |
                             +---------------+
       Service Delivery Model       |
             L2NM                   |
            (l2vpn-ntw)     |
                             +---------------+
                             |   Network     |
                             | Orchestration |
                             +---------------+
       Network Configuration Model  |
                          __________|____________
                         |                       |
                +---------------+       +---------------+
                |    Domain     |       |     Domain    |
                | Orchestration |       | Orchestration |
                +---------------+       +---------------+
     Device         |        |                   |
     Configuration  |        |                   |
     Model          |        |                   |
               +---------+   |                   |
               | Config  |   |                   |
               | Manager |   |                   |
               +---------+   |                   |
                    |        |                   |
                    | NETCONF/CLI..................
                    |        |                   |
             +------------------------------------------------+
                                 Network

                            +++++++
                            + AAA +
                            +++++++

    ++++++++   Bearer    ++++++++           ++++++++      ++++++++
    + CE A + ----------- + PE A +           + PE B + ---- + CE B +
    ++++++++  Connection ++++++++           ++++++++      ++++++++

               Site A                               Site B

                    Figure 1: L2SM and L2NM Interaction

   Figure 2 shows how L2SM and L2NM may be used in the context of the
   ACTN architecture [RFC8453].  Figure 2 shows the Customer Network
   Controller (CNC), the Multi-Domain Service Coordinator (MDSC), and
   the Provisioning Network Controller (PNC).  It shows the interfaces
   between these functional units: the CNC-MDSC Interface (CMI), the
   MDSC-PNC Interface (MPI), and the Southbound Interface (SBI).

                  ----------------------------------
                  | Customer                         |
                  |  -----------------------------   |
                  | |             CNC             |  |
                  |  -----------------------------   |
                   ----:-----------------------:-----
                       :                       :
                       : L2SM                  : L2SM
                       :                       :
              ---------:---------     -------------------
             | MDSC    :         |   |       MDSC        |
             |  ---------------  |   |     (parent)      |
             | |    Service    | |    -------------------
             | | Orchestration | |             :
             |  ---------------  |             : L2NM
             |         :         |             :
             |         : L2NM    |    -------------------
             |         :         |   |       MDSC        |
             |  ---------------  |   |      (child)      |
             | |    Network    | |    -------------------
             | | Orchestration | |             :
             |  ---------------  |             :
              ---------:---------              :
                       :                       :
                       : Network Configuration :
                       :                       :
           ------------:-------       ---------:------------
          | Domain     :       |     |         : Domain     |
          | Controller :       |     |         : Controller |
          |        ---------   |     |     ---------        |
          |       |   PNC   |  |     |    |   PNC   |       |
          |        ---------   |     |     ---------        |
           ------------:-------       ---------:------------
                       :                       :
                       : Device Configuration  :
                       :                       :
                   --------                --------
                  | Device |              | Device |
                   --------                --------

              Figure 2: L2SM and L2NM in the Context of ACTN

3.  Description of the L2NM YANG Module

   The L2NM module ('ietf-l2vpn-ntw') is meant to manage L2 VPNs within
   a service provider network.  In particular, the 'ietf-l2vpn-ntw'
   module can be used to create, modify, and retrieve L2VPN Services in
   a Network Controller.  The module is not aimed at maintaining
   customer-related information.

   Editor's note: Next version of the document will include the full
   description of the parameters.  When the parameters match with L2SM,
   the exact reference will be done

3.1.  Structure of the Module

   The 'ietf-l2vpn-ntw' module uses two main containers: 'vpn-services'
   and 'vpn-profiles'.  The 'vpn-services' container maintains a set of
   L2 VPN Services managed in the service provider network.  The module
   allows to create a new l2 VPN service by adding a new instance of
   'vpn-service'.  The 'vpn-service' is the data structure that
   abstracts the VPN Service.

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

                 Figure 3: Simplified L2NM Tree Structure

3.2.  L2  VPN Service Profiles

   The 'vpn-service' is the data structure that abstracts a L2 VPN
   Service within the SP Network.  Every 'vpn-service' has a unique
   identifier: vpn-id.  Such vpn-id is only meaningful locally within 'vpn-profiles' container (Figure 4) allows the Network controller.  In order network provider
   to facilitate the recognition of
   the service, a 'customer-name' define and maintain a 'description' may be included.
   The topology set of the common VPN service is expressed in the 'vpn-service-
   topology' leaf.

   A profiles
   [I-D.ietf-opsawg-vpn-common] that apply to one or several VPN Service is built by adding instances
   services.  The exact definition of 'vpn-node' to the 'vpn-
   nodes' container.  The 'vpn-node' profiles is an abstraction that represents a
   set of policies applied local to a each
   network node and that belong to a single
   'vpn-service'.  A 'vpn-node' contains 'vpn-network-accesses', which
   are provider.

   This document does not make any assumption about the interfaces involved exact definition
   of these profiles.  How such profiles are defined is deployment
   specific.  The model only includes an identifier to these profiles to
   ease identifying local policies when building a VPN service.  As
   shown in Figure 4, the creation following identifiers can be included:

   o  'cloud-identifier': This identifier refers to a cloud service.

   o  'encryption-profile-identifier': An encryption profile refers to a
      set of the VPN.  The customer
   sites are connected policies related to the 'vpn_network_accesses'.  Note that, encryption scheme(s) and setup that
      can be applied when building and offering a VPN service.

   o  'qos-profile-identifier': A QoS profile refers to as
   this is set of
      policies such as classification, marking, and actions (e.g.,
      [RFC3644]).

   o  'bfd-profile-identifier': A Bidirectional Forwarding Detection
      (BFD) profile refers to a network data model, set of BFD [RFC5880] policies that can
      be invoked when building a VPN service.

   o  'forwarding-profile-identifier': A forwarding profile refers to
      the information about customers site is
   not needed.  Such information, is only relevant in policies that apply to the L2SM model. forwarding of packets conveyed
      within a VPN.  Such policies may consist at applying Access
      Control Lists (ACLs).

   o  'routing-profile-identifier': A routing profile refers to a set of
      routing policies that will be invoked (e.g., BGP policies).

            +--rw vpn-services l2vpn-ntw
               +--rw vpn-service* [vpn-id] vpn-profiles
               |  +--rw vpn-id                      svc-id valid-provider-identifiers
               |     +--rw vpn-svc-type?               identityref cloud-identifier* [id] {cloud-access}?
               |     |  +--rw customer-name? id    string
              +--rw svc-topo?                   identityref
              +-rw service-status
               |  +-rw admin     +--rw encryption-profile-identifier* [id]
               |     |  +-rw status?      operational-type  +--rw id    string
               |     +--rw qos-profile-identifier* [id]
               |  +-rw timestamp?   yang:date-and-time     |  +-ro ops  +--rw id    string
               |     +-ro status?      operational-type     +--rw bfd-profile-identifier* [id]
               |     +-ro timestamp?   yang:date-and-time     |  ...  +--rw multicast-like {multicast-like}? id    string
               |  ...     +--rw extranet-vpns {extranet-vpn}? forwarding-profile-identifier* [id]
               |  ...     |  +--rw local-sites-role?   identityref
              +--rw svc-mtu?                    uint32
              +--rw ce-vlan-preservation?       boolean
              +--rw ce-vlan-cos-perservation?   boolean id    string
               |     +--rw transport-encapsulation routing-profile-identifier* [id]
               |        +--rw protocol?   protocols-type id    string
               +--rw vpn-nodes vpn-services
                  ...

                 Figure 4

3.2.1. 4: VPN Profiles Subtree Structure

3.3.  L2 VPN Service Types

   The 'vpn-service' is the data structure that abstracts a L2 VPN
   Service types directly matches with within the L2VPN Service
   types defined SP Network.  Every 'vpn-service' has a unique
   identifier: vpn-id.  Such vpn-id is only meaningful locally within
   the Network controller.  In order to facilitate the recognition of
   the service, a 'customer-name' and a 'description' may be included.

   The 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 abstraction that represents a
   set of policies/configurations 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 is a network data model,
   the information about customers site is not needed.  Such
   information, is only relevant in the L2SM model.

        +--rw vpn-services
           +--rw vpn-service* [vpn-id]
              +--rw status
              |  +--rw admin-status
              |  |  +--rw status?         identityref
              |  |  +--rw last-updated?   yang:date-and-time
              |  +--ro oper-status
              |     +--ro status?         identityref
              |     +--ro last-updated?   yang:date-and-time
              +--rw vpn-id                      vpn-id
              +--rw vpn-name?                   string
              +--rw vpn-description?            string
              +--rw customer-name?              string
              +--rw l2sm-vpn-id?                vpn-common:vpn-id
              +--rw vpn-svc-type?               identityref
              +--rw svc-topo?                   identityref
              +--rw multicast-like {vpn-common:multicast}?
              |  +--rw enabled?                 boolean
              |  +--rw customer-tree-flavors
              |     +--rw tree-flavor*   identityref
              +--rw extranet-vpns {vpn-common:extranet-vpn}?
              |  +--rw extranet-vpn* [vpn-id]
              |     +--rw vpn-id              vpn-common:vpn-id
              |     +--rw local-sites-role?   identityref
              +--rw svc-mtu?                    uint32
              +--rw ce-vlan-preservation?       boolean
              +--rw ce-vlan-cos-perservation?   boolean
              +--rw underlay-transport
              |  +--rw type*   identityref
              +--rw vpn-nodes
                      .....

                                 Figure 5

3.3.1.  L2 VPN Service Types

   The L2 VPN Service types directly matches with the L2VPN Service
   types defined in Section 5.1.3 of [RFC8466]:

   o  Point-to-point VPWSs.

   o  Point-to-point or point-to-multipoint VPWSs [RFC8214].

   o  Multipoint VPLSs.

   o  Multipoint VPLSs connecting one or more root sites and a set of
      leaf sites but preventing inter-leaf-site communication.

   o  EVPN services [RFC7432].

   o  EVPN VPWSs between two customer sites or a set of customer sites
      as specified in [RFC8214].

3.2.2.

3.3.2.  Underlying Transport Selection

   The model enables network operators to select the type of transport
   protocol underlay.  Also, in scenarios with multiple domains and NNI
   types, the selection of the transport protocol underlay is required.
   The Service Provider Network might have several underlay
   possibilities available.  If no underlay transport protocol is
   specified, the Network Controller will take care of the transport
   decision.  The following options are supported in the "underlay-
   transport" container:

      LDP: MPLS with LDP (martini encapsulation).

      GRE: A mesh of GRE tunnels is established between vpn-nodes.

      BGP: BGP tunnels (kompella encapsulation) are preferred to route
      traffic between VPN nodes.

      TE: TE tunnels (either RSVP-TE or SR) are prefered.  The mapping
      details will be specified in draft-ietf-te-service-mapping.

      SR: Non-TE SR is preferred to route traffic.

3.2.3.  Other relevant Network Parameters

   This draft

3.3.3.  VPN Node

   The 'vpn-node' is focus in the development of the network centric an abstraction that represents a set of
   parameters policies/
   configurations applied to provision L2VPNs.  Thus, the covered scenarios include
   the augmentation of Virtual Circuit Identifier synchronization in a
   multidomain environment, precedence management (i.e., Primary network node and
   backup coordination), Split Horizon group management.  The parameters that belong to a single
   'vpn-service'.  A 'vpn-node' contains 'vpn-network-accesses', which
   are described by the container associated:

   The set of augmentations done interfaces involved in the VPN service are:

      Status: Request and modify the service status

   The set creation of augmentations done in the Site Network Access are:

      Site Bearer: Reference the NEs and Ports were each site Network
      access belongs.  This may help to preserve the local and farends
      from the Network controller site.

      Precedence: When two L2VPNs VPN.  The customer
   sites are created at the same time, the
      primary secondary option is enabled according connected to the tunnel role
      on the network.

      Lag Interface Support.

      Split Horizon group: Split-horizon group name is extended as part
      of the Site Network Access container.

      Status: Request and modify the interface status.

3.3.  L2NM Module Tree

   The tree structure of the YANG module proposed by this document is
   shown below:

   module: ietf-l2vpn-ntw
     +--rw l2vpn-ntw
        +--rw vpn-profiles
        |  +--rw valid-provider-identifiers
        | 'vpn_network_accesses'.

                      +--rw cloud-identifier*            string {cloud-access}?
        | vpn-nodes
                 +--rw qos-profile-identifier*      string
        | vpn-node* [vpn-node-id ne-id]
                    +--rw bfd-profile-identifier*      string
        | vpn-node-id             vpn-common:vpn-id
                    +--rw remote-carrier-identifier* description?            string
                    +--rw vpn-services
           +--rw vpn-service* [vpn-id]
              +--rw vpn-id                      svc-id
              +--rw vpn-service-type? node-role?              identityref
                    +--rw customer-name? ne-id                   string
                    +--rw svc-topo?                   identityref
              +--rw status?                     operational-type
              +--rw timestamp?                  yang:date-and-time
              +--rw multicast-like {multicast-like}?
              | port-id?                string
                    +--rw enabled?                     boolean status
                    |  +--rw customer-tree-flavors admin-status
                    |  |  +--rw tree-flavor* status?         identityref
                    |  +--rw bum-frame-delivery-modes
              |  |  +--rw bum-frame-delivery* [traffic-type] last-updated?   yang:date-and-time
                    |  +--ro oper-status
                    |     +--rw traffic-type     +--ro status?         identityref
                    |  |     +--ro last-updated?   yang:date-and-time
                    +--rw delivery-mode?   identityref signaling-options* [type]
                    |  +--rw multicast-gp-port-mapping? type         identityref
              +--rw extranet-vpns {extranet-vpn}?
                    |  +--rw extranet-vpn* [vpn-id] l2vpn-bgp
                    |     +--rw vpn-id              svc-id  |  +--rw local-sites-role? pwe-encapsulation-type?   identityref
              +--rw svc-mtu?                    uint32
              +--rw ce-vlan-preservation?       boolean
              +--rw ce-vlan-cos-perservation?   boolean
              +--rw underlay-transport
                    |  +--rw type*   protocol-type
              +--rw vpn-nodes
                 +--rw vpn-node* [vpn-node-id ne-id]
                    +--rw vpn-node-id             string
                    +--rw description?            string
                    +--rw node-role?              identityref
                    +--rw ne-id                   string  |  +--rw vpn-target* [id]
                    |  |  |  +--rw id                   int8
                    |  |  |  +--rw route-targets* [route-target]
                    |  |  |  |  +--rw route-target
                    |  |  |  |          rt-types:route-target
                    |  |  |  +--rw route-target-type
                    |  |  |          rt-types:route-target-type
                    |  |  +--rw vpn-policies
                    |  |  |  +--rw import-policy?   leafref   string
                    |  |  |  +--rw export-policy?   leafref
                    +--rw vpn-network-accesses
                       +--rw vpn-network-access* [network-access-id]
                          +--rw network-access-id
                          |   string
                          +--rw description?
                    |       string
                          +--rw remote-carrier-name?  |       string  +--rw Interface-mtu? pwe-mtu
                    |       uint32
                          +--rw status?  |       operational-type
                          +--rw timestamp?  |       yang:date-and-time  +--rw access-diversity {site-diversity}? allow-mtu-mismatch?   boolean
                    |  |  +--rw groups address-family?
                    |  |          vpn-common:address-family
                    |  +--rw fate-sharing-group-size?   uint16 evpn-bgp
                    |  |  +--rw group-color?               string vpn-id?              leafref
                    |  |  +--rw group* [group-id] type?                identityref
                    |  |  +--rw group-id    string address-family?
                    |  +--rw constraints  |     +--rw constraint* [constraint-type]  |       vpn-common:address-family
                    |  |  +--rw constraint-type mac-learning-mode?   identityref
                    |        +--rw target  |  +--rw (target-flavor)? arp-suppress?        boolean
                    |              +--:(id)  +--rw t-ldp-pwe
                    |  |  +--rw group* [group-id] type?                     identityref
                    |  |  +--rw group-id    string
                          |              +--:(all-accesses) pwe-encapsulation-type?   identityref
                    |  |  +--rw all-other-accesses? pwe-mtu?                  uint16
                    |  |          empty  +--rw ac-pw-list* [peer-addr vc-id]
                    |              +--:(all-groups)  |                 +--rw all-other-groups?  |                         empty  +--rw connection peer-addr      inet:ip-address
                    |  +--rw encapsulation-type?    identityref  |  +--rw eth-inf-type*          identityref  |  +--rw dot1q-interface vc-id          vpn-common:vpn-id
                    |  |  |  +--rw l2-access-type? pw-type?       identityref
                    |  |  +--rw dot1q {dot1q}?  |  +--rw pw-priority?   uint32
                    |  |  +--rw physical-inf?   string
                          | qinq
                    |  |     +--rw c-vlan-id? s-tag?   uint32
                    |  |     +--rw sub-inf {sub-inf}?
                          | c-tag?   uint32
                    |  +--rw l2tp-pwe
                    |     +--rw interface-description? type?                 identityref
                    |     +--rw encapsulation-type?   identityref
                    |     +--rw ac-pw-list* [peer-addr vc-id]
                    |        +--rw peer-addr      inet:ip-address
                    |        +--rw vc-id          string
                    |  |        +--rw pw-priority?   uint32
                    +--rw vpn-network-accesses

                                 Figure 6

3.3.3.1.  Signaling options

   This sub-tree defines the L2VPN service type, according to the
   several signalling options to exchange membership information between
   the PE that is used.  There are some common parameters inside each of
   them (e.g encapsulation type, MTU) but some others are:

      l2vpn-bgp.  The service is a Multipoint VPLSs that use a BGP
      control plane as described in [RFC4761] and [RFC6624].  The VPLS
      members exchange Route Targets with related import/export
      policies.

      evpn-bgp.  The service is a Multipoint VPLSs that use also a BGP
      control plane but also includes the additional features and
      related parameters described in [RFC7432] and [RFC7209].

      t-ldp-pwe.  A Multipoint VPLSs that use a mesh of LDP-signaled
      Pseudowires [RFC6074], including as parameters the list of
      Pseudowires that constitute the mesh, with their details (VC-IDs
      and endpoints).

      L2tp-pwe.  Multipoint VPLSs that use L2TP-signaled Pseudowires
      [RFC6074].

                    +--rw signaling-options* [type]
                      +--rw type         identityref
                      +--rw l2vpn-bgp
                      |  +--rw sub-if-id? pwe-encapsulation-type?   identityref
                      |  +--rw vpn-target* [id]
                      |  |          uint32  +--rw id                   int8
                      |  |  +--rw qinq {qinq}? route-targets* [route-target]
                      |  |  |  +--rw s-vlan-id?   uint32 route-target
                      |  |  |  +--rw c-vlan-id?   uint32          rt-types:route-target
                      |  |  +--rw qinany {qinany}? route-target-type
                      |  |          rt-types:route-target-type
                      |  +--rw s-vlan-id?   uint32 vpn-policies
                      |  |  +--rw atm {atm}? import-policy?   string
                      |  |  +--rw export-policy?   string
                      |  +--rw vpi?   uint32 pwe-mtu
                      |  |  +--rw allow-mtu-mismatch?   boolean
                      |  +--rw vci?   uint32 address-family?
                      |          vpn-common:address-family
                      +--rw evpn-bgp
                      |  +--rw vxlan {vxlan}? vpn-id?              leafref
                      |  +--rw type?                identityref
                      |  +--rw vni-id?      uint32 address-family?
                      |  |       vpn-common:address-family
                      |  +--rw peer-mode? mac-learning-mode?   identityref
                      |  +--rw arp-suppress?        boolean
                      +--rw t-ldp-pwe
                      |  +--rw peer-list* [peer-ip] type?                     identityref
                      |  +--rw pwe-encapsulation-type?   identityref
                      |  +--rw peer-ip    inet:ip-address pwe-mtu?                  uint16
                      |  +--rw phy-interface ac-pw-list* [peer-addr vc-id]
                      |  |  +--rw port-number?           uint32 peer-addr      inet:ip-address
                      |  |  +--rw port-speed?            uint32 vc-id          vpn-common:vpn-id
                      |  |  +--rw mode?                  neg-mode pw-type?       identityref
                      |  |  +--rw phy-mtu? pw-priority?   uint32
                      |  |  +--rw flow-control?          string qinq
                      |     +--rw s-tag?   uint32
                      |     +--rw physical-if? c-tag?   uint32
                      +--rw l2tp-pwe
                         +--rw type?                 identityref
                         +--rw encapsulation-type?   identityref
                         +--rw ac-pw-list* [peer-addr vc-id]
                            +--rw peer-addr      inet:ip-address
                            +--rw vc-id          string
                            +--rw pw-priority?   uint32

                                 Figure 7

3.3.3.2.  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
   L2VPN.  As such, every 'vpn-network-access' MUST belong to one and
   only one 'vpn-node'.

   A 'vpn-network-access' includes information such as the connection on
   which the access is defined , the specific layer 2 service
   requirements, etc.

   The Site Network Access is comprised of:

      id: Identifier of the vpn network access.

      description: Text describing the vpn network access.

      interface-mtu: maximum transmission unit or maximum frame size of
      the interface belonging to the vpn network access.  When a frame
      is larger than the MTU, it is broken down, or fragmented, into
      smaller pieces by the network protocol to accommodate the MTU of
      the network"

      status: Administrative and operational status of the service.

      ethernet-service-oam: Carries information about the service OAM

                            +--rw vpn-network-accesses
                       +--rw vpn-network-access* [id]
                          +--rw id
                          |  |       vpn-common:vpn-id
                          +--rw circuit-id? description?
                          |       string
                          +--rw Interface-mtu?
                          |       uint32
                          +--rw status
                          |  +--rw lldp?                  boolean admin-status
                          |  |  +--rw oam-802.3ah-link {oam-3ah}?
                          | status?         identityref
                          |  |  +--rw enable?   boolean last-updated?   yang:date-and-time
                          |  +--ro oper-status
                          |  +--rw uni-loop-prevention?   boolean     +--ro status?         identityref
                          |     +--ro last-updated?   yang:date-and-time
                          +--rw lag-interface {lag-interface}? access-diversity
                          |       {vpn-common:placement-diversity}?
                          |  +--rw lag-interface* groups
                          |  |          [lag-interface-number]  +--rw fate-sharing-group-size?   uint16
                          |  |  +--rw lag-interface-number    uint32 group-color?               string
                          |  |  +--rw lacp group* [group-id]
                          |  |     +--rw lacp-state?         boolean
                          | group-id    string
                          |  +--rw lacp-mode?          boolean constraints
                          |     +--rw constraint* [constraint-type]
                          |        +--rw lacp-speed?         boolean constraint-type    identityref
                          |        +--rw target
                          |           +--rw mini-link?          uint32 (target-flavor)?
                          |              +--:(id)
                          |              |  +--rw system-priority?    uint16 group* [group-id]
                          |              |     +--rw micro-bfd {micro-bfd}? group-id    string
                          |              +--:(all-accesses)
                          |              |  +--rw micro-bfd-on-off?
                          |  |        | all-other-accesses?
                          |       enumeration              |          empty
                          |              +--:(all-groups)
                          |                 +--rw bfd-interval?
                          |  |        |  |       uint32
                          |  | all-other-groups?
                          |                         empty
                          +--rw bfd-hold-timer?
                          | connection
                          |       ....
                          +--rw availability
                          |  +--rw access-priority?       uint32
                          |  |  +--rw bfd {bfd}? (redundancy-mode)?
                          |     +--:(single-active)
                          |     |  +--rw bfd-enabled?
                          |  |        |  | single-active?   boolean
                          |     +--:(all-active)
                          |        |        +--rw (holdtime)? all-active?      boolean
                          +--rw service
                          |       .....
                          +--rw broadcast-unknown-unicast-multicast
                          |  +--rw multicast-site-type?
                          |     +--:(profile)  |       enumeration
                          |  +--rw multicast-gp-address-mapping* [id]
                          |  |  +--rw profile-name?
                          | id                 uint16
                          |  |  +--rw vlan-id?           uint32
                          |          string  |  +--rw mac-gp-address?
                          |  |     +--:(fixed)  |       yang:mac-address
                          |  |  +--rw fixed-value?
                          |  |        | port-lag-number?   uint32
                          |  |  +--rw member-link-list bum-overall-rate?
                          |          uint32
                          +--rw ethernet-service-oam
                          |  +--rw md-name?        string
                          |  +--rw member-link* [name] md-level?       uint8
                          |  +--rw cfm-802.1-ag
                          |  |  +--rw name
                          | n2-uni-c* [maid]
                          |  |  |  +--rw maid                string
                          |  |  |  +--rw port-speed?
                          | mep-id?             uint32
                          |  |  |  +--rw mep-level?          uint32
                          |  |  |  +--rw mode?
                          | mep-up-down?        enumeration
                          |  |  |       neg-mode  +--rw remote-mep-id?      uint32
                          |  |  |  +--rw link-mtu?
                          | cos-for-cfm-pdus?   uint32
                          |  |  |  +--rw ccm-interval?       uint32
                          |  |  |  +--rw oam-802.3ah-link ccm-holdtime?       uint32
                          |  |  |             {oam-3ah}?  +--rw ccm-p-bits-pri?
                          |  |  |        +--rw enable?   boolean          vpn-common:ccm-priority-type
                          |  |  +--rw flow-control?       string n2-uni-n* [maid]
                          |  |     +--rw lldp?               boolean maid                string
                          |  |     +--rw cvlan-id-to-svc-map* [svc-id] mep-id?             uint32
                          |  |     +--rw svc-id      leafref mep-level?          uint32
                          |  |     +--rw cvlan-id* [vid] mep-up-down?        enumeration
                          |  |     +--rw vid remote-mep-id?      uint32
                          |  |     +--rw split-horizon cos-for-cfm-pdus?   uint32
                          |  |     +--rw group-name?   string ccm-interval?       uint32
                          |  +--rw l2cp-control {L2CP-control}?  |     +--rw stp-rstp-mstp?    control-mode ccm-holdtime?       uint32
                          |     +--rw pause?            control-mode  |     +--rw lacp-lamp?        control-mode ccm-p-bits-pri?
                          |     +--rw link-oam?         control-mode  |     +--rw esmc?             control-mode             vpn-common:ccm-priority-type
                          |  +--rw l2cp-802.1x?      control-mode y-1731* [maid]
                          |     +--rw e-lmi?            control-mode maid
                          |     +--rw lldp?             boolean     |     +--rw ptp-peer-delay?   control-mode       string
                          |     +--rw garp-mrp?         control-mode
                          +--rw availability mep-id?
                          |     |  +--rw access-priority?       uint32
                          |     +--rw (redundancy-mode)? type?
                          |     +--:(single-active)     |       identityref
                          |     +--rw single-active?   boolean remote-mep-id?
                          |     +--:(all-active)     |        +--rw all-active?      boolean
                          +--rw service       uint32
                          |     +--rw svc-input-bandwidth {input-bw}?
                          | message-period?
                          |  +--rw input-bandwidth* [type]     |       uint32
                          |     +--rw type      identityref measurement-interval?
                          |     |       uint32
                          |     +--rw cos-id?   uint8 cos?
                          |     |       uint32
                          |     +--rw vpn-id?   svc-id loss-measurement?
                          |     |       boolean
                          |     +--rw cir?      uint64 synthethic-loss-measurement?
                          |     |       boolean
                          |     +--rw cbs?      uint64 delay-measurement
                          |     |  +--rw eir?      uint64 enable-dm?   boolean
                          |     |  +--rw ebs?      uint64
                          | two-way?     boolean
                          |     +--rw pir?      uint64 frame-size?
                          |     |     +--rw pbs?      uint64       uint32
                          |     +--rw svc-output-bandwidth {output-bw}?
                          | session-type?
                          |             enumeration
                          +--rw output-bandwidth* [type] mac-loop-prevention
                          |  +--rw frequency?         uint32
                          |  +--rw type protection-type?   identityref
                          |  |  +--rw cos-id?   uint8
                          |  | number-retries?    uint32
                          +--rw vpn-id?   svc-id
                          | access-control-list
                          |  +--rw cir?      uint64
                          | mac* [mac-address]
                          |     +--rw cbs?      uint64
                          |  | mac-address    yang:mac-address
                          +--rw eir?      uint64
                          |  | mac-addr-limit
                             +--rw ebs?      uint64 mac-num-limit?   uint16
                             +--rw time-interval?   uint32
                             +--rw action?          identityref

                                 Figure 8

3.3.3.2.1.  Connection

   The connection container is used to configure the relevant properties
   of the interface that is attached to the VPN, for example the
   encapsulation type, the physical interface or creating a lag.

                   +--rw connection
                      +--rw encapsulation-type?    identityref
                      +--rw eth-inf-type*          identityref
                      +--rw dot1q-interface
                      |  +--rw l2-access-type?   identityref
                      |  +--rw pir?      uint64 dot1q {vpn-common:dot1q}?
                      |  |  +--rw pbs?      uint64 physical-inf?   string
                      |  |  +--rw qos {qos}? c-vlan-id?      uint32
                      |  +--rw classification-policy qinq {vpn-common:qinq}?
                      |  |  +--rw rule* [id] s-vlan-id?   uint32
                      |  |  +--rw id
                          | c-vlan-id?   uint32
                      |  +--rw qinany {vpn-common:qinany}?
                      |       string  |  +--rw s-vlan-id?   uint32
                      |  +--rw (match-type)? vxlan {vxlan}?
                      |     +--rw vni-id?      uint32
                      |     +--rw peer-mode?   identityref
                      |  +--:(match-flow)     +--rw peer-list* [peer-ip]
                      |        +--rw peer-ip    inet:ip-address
                      +--rw phy-interface
                      |  +--rw port-number?           uint32
                      |  +--rw port-speed?            uint32
                      |  +--rw match-flow mode?
                      |  |       vpn-common:neg-mode
                      |  +--rw phy-mtu?               uint32
                      |  +--rw dscp? flow-control?          string
                      |  +--rw oam-802.3ah-link {oam-3ah}?
                      |  |  +--rw enable?   boolean
                      |  +--rw uni-loop-prevention?   boolean
                      +--rw lag-interface
                      |       inet:dscp       {vpn-common:lag-interface}?
                      |  +--rw lag-interface*
                      |          [lag-interface-number]
                      |     +--rw lag-interface-number    uint32
                      |     +--rw dot1q? lacp
                      |        +--rw lacp-state?         boolean
                      |        +--rw lacp-mode?          boolean
                      |        +--rw lacp-speed?         boolean
                      |        +--rw mini-link?          uint32
                      |        +--rw system-priority?    uint16
                      |     |     |  |        +--rw pcp? member-link-list
                      |        |  +--rw member-link* [name]
                      |        |     +--rw name
                      |       uint8        |     |       string
                      |        |     +--rw src-mac? port-speed?
                      |        |     |       uint32
                      |        |       yang:mac-address     +--rw mode?
                      |        |     |       vpn-common:neg-mode
                      |        |     +--rw dst-mac? link-mtu?
                      |        |     |       uint32
                      |        |     +--rw oam-802.3ah-link
                      |       yang:mac-address        |             {oam-3ah}?
                      |        |        +--rw enable?   boolean
                      |        +--rw color-type? flow-control?       string
                      |        +--rw lldp?               boolean
                      +--rw cvlan-id-to-svc-map* [svc-id]
                      |  +--rw svc-id      leafref
                      |  +--rw cvlan-id* [vid]
                      |     +--rw vid    uint32
                      +--rw split-horizon
                         +--rw group-name?   string

                                 Figure 9

3.3.3.2.2.  Layer 2 service requirements

   This container is usedd to indicate the details of the ethernet
   service such as bandwidth or qos.

+--rw service
  |       identityref  +--rw svc-input-bandwidth
  |  |       {vpn-common:input-bw}?
  |  |  +--rw target-sites* input-bandwidth* [type]
  |  |     +--rw type      identityref
  |  |     +--rw cos-id?   uint8
  |       svc-id  |     +--rw cir?      uint64
  |  |     +--rw cbs?      uint64
  |  |       {target-sites}?     +--rw eir?      uint64
  |  |     +--rw ebs?      uint64
  |  |     +--rw any? pir?      uint64
  |  |     +--rw pbs?      uint64
  |  +--rw svc-output-bandwidth {output-bw}?
  |  |       empty  +--rw output-bandwidth* [type]
  |  |     +--rw type      identityref
  |  |     +--rw vpn-id? cos-id?   uint8
  |  |     +--rw cir?      uint64
  |  |             svc-id     +--rw cbs?      uint64
  |  |     +--rw eir?      uint64
  |  +--:(match-application)  |     +--rw ebs?      uint64
  |  |     +--rw match-application? pir?      uint64
  |  |     +--rw pbs?      uint64
  |             identityref  +--rw qos {vpn-common:qos}?
  |  |  +--rw target-class-id? qos-classification-policy
  |  |             string  |  +--rw qos-profile rule* [id]
  |  |  |     +--rw (qos-profile)? id
  |           +--:(standard)  |  |  +--rw profile?   leafref     |           +--:(custom)       string
  |              +--rw classes {qos-custom}?  |                 +--rw class* [class-id]  |     +--rw class-id (match-type)?
  |  |       string  |                    +--rw direction?     |  +--:(match-flow)
  |       identityref  |                    +--rw policing?  |     |       identityref  |  +--rw byte-offset? (l3)?
  |  |       uint16  |                    +--rw frame-delay     |  |  +--rw (flavor)?  |  +--:(ipv4)
  |     +--:(lowest)  |  |     |  +--rw use-lowest  |  |  |   -latency? empty  +--rw ipv4
  |  |     +--:(boundary)  |     |        +--rw delay-  |  |           bound? uint16  |     +--rw frame-jitter dscp?
  |  |  +--rw (flavor)?  |     |     +--:(lowest)  |  |  |  +--rw use-lowest     |       inet:dscp
  |  |  |    -jitter? empty     |  |     +--:(boundary)  |  |     +--rw delay- ecn?
  |  |           bound? uint32  |                    +--rw frame-loss     |  |  +--rw rate?  |  |          decimal64     |                    +--rw bandwidth       uint8
  |                       +--rw guaranteed-bw-  |  |    percent decimal64     |                       +--rw end-to-end?  |                               empty
                          +--rw svc-precedence  |  +--rw precedence?   identityref
                          +--rw broadcast-unknown-unicast-multicast  |     +--rw multicast-site-type? length?
  |  |       enumeration  |  +--rw multicast-gp-address-mapping* [id]     |  |  +--rw id                 uint16  |  |  +--rw vlan-id?           uint32     |       uint16
  |  +--rw mac-gp-address?  |  |     |       yang:mac-address  |  |  +--rw port-lag-number?   uint32  |     +--rw bum-overall-rate? ttl?
  |  |  |       uint32     |  +--rw bum-rate-per-type* [type]  |     +--rw type    identityref  |     +--rw rate?   uint32
                          +--rw ethernet-service-oam  |  +--rw md-name?        string     |  +--rw md-level?       uint8
  |  +--rw cfm-802.1-ag  |  |  +--rw n2-uni-c* [maid]     |  |  |  |     +--rw maid protocol?
  |  |  |     |       string  |  |  |  +--rw mep-id?     |       uint8
  |  |  |     |       uint32  |  |  |     +--rw mep-level? ihl?
  |  |  |     |       uint32  |  |  |  +--rw mep-up-down?     |       uint8
  |  |  |     |       enumeration  |  |  |     +--rw remote-mep-id? flags?
  |  |  |     |       uint32  |  |  |  +--rw cos-for-cfm-pdus?     |       bits
  |  |  |     |       uint32  |  |  |     +--rw ccm-interval? offset?
  |  |  |     |       uint32  |  |  |  +--rw ccm-holdtime?     |       uint16
  |  |  |     |       uint32  |  |  |     +--rw alarm-priority-defect? identification?
  |  |  |     |       identityref  |  |  |  +--rw ccm-p-bits-pri?     |       uint16
  |  |  |          ccm-priority-type     |  |  +--rw n2-uni-n* [maid]  |  |     +--rw maid (destination-network)?
  |  |  |       string     |  |     +--rw mep-id?  |  |     |       uint32  +--:(destination-ipv4-network)
  |  |  |     +--rw mep-level?     |  |  |       uint32  |     |     +--rw mep-up-down? destination-ipv4-network?
  |  |  |       enumeration     |  |     +--rw remote-mep-id?  |  |     |       uint32             inet:ipv4-prefix
  |  |     +--rw cos-for-cfm-pdus?  |     |  |       uint32  |  |     +--rw ccm-interval? (source-network)?
  |  |  |       uint32     |  |     +--rw ccm-holdtime?  |  |        +--:(source-ipv4-network)
  |  |  |     |  |       uint32  |  |           +--rw alarm-priority-defect? source-ipv4-network?
  |  |  |       identityref     |  |     +--rw ccm-p-bits-pri?  |  |             ccm-priority-type                   inet:ipv4-prefix
  |  +--rw y-1731* [maid]  |     +--rw maid  |     |       string  |     +--rw mep-id?  |  +--:(ipv6)
  |  |       uint32  |     +--rw type?     |  |       identityref  |     +--rw remote-mep-id? ipv6
  |  |       uint32  |     +--rw message-period?     |  |       uint32  |        +--rw measurement-interval? dscp?
  |  |       uint32  |     +--rw cos?     |  |       uint32  |     +--rw loss-measurement?        |       inet:dscp
  |  |       boolean  |     +--rw synthethic-loss-measurement?     |  |       boolean  |        +--rw delay-measurement ecn?
  |  |  +--rw enable-dm?   boolean  |     |  +--rw two-way?     boolean  |     +--rw frame-size?  |        |       uint32       uint8
  |     +--rw session-type?  |             enumeration
                          +--rw mac-loop-prevention  |  +--rw frequency?         uint32     |  +--rw protection-type?   identityref  |  +--rw number-retries?    uint32
                          +--rw access-control-list  |        +--rw mac* [mac-address] length?
  |  |  |     |  |  |     +--rw mac-address    yang:mac-address
                          +--rw mac-addr-limit        |  +--rw mac-num-limit?       uint16
  |  |  |     |  |  |        +--rw time-interval? ttl?
  |  |  |     |  |  |        |       uint8
  |  |  |     |  |  |        +--rw protocol?
  |  |  |     |  |  |        |       uint8
  |  |  |     |  |  |        +--rw (destination-network)?
  |  |  |     |  |  |        |  +--:(destination-ipv6-network)
  |  |  |     |  |  |        |     +--rw destination-ipv6-network?
  |  |  |     |  |  |        |             inet:ipv6-prefix
  |  |  |     |  |  |        +--rw (source-network)?
  |  |  |     |  |  |        |  +--:(source-ipv6-network)
  |  |  |     |  |  |        |     +--rw source-ipv6-network?
  |  |  |     |  |  |        |             inet:ipv6-prefix
  |  |  |     |  |  |        +--rw flow-label?
  |  |  |     |  |  |                inet:ipv6-flow-label
  |  |  |     |  |  +--rw (l4)?
  |  |  |     |  |     +--:(tcp)
  |  |  |     |  |     |  +--rw tcp
  |  |  |     |  |     |     +--rw sequence-number?
  |  |  |     |  |     |     |       uint32
  |  |  |     |  |     |     +--rw action?          identityref acknowledgement-number?
  |  |  |     |  |     |     |       uint32
  |  |  |     |  |     |     +--rw site-bearers data-offset?
  |  |  |     |  |     |     |       uint8
  |  |  |     |  |     |     +--rw bearer-id?
   string

                                 Figure 5

4.  Relation with other YANG Models

   The L2NM model, aimed at managing the L2VPN Services in a Service
   Provider Network controller/orchestrator has relations with other
   YANG modules.

4.1.  Relation with L2SM

   [RFC8466] defines a L2VPN Service YANG data Model (L2SM) 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, most parts of the model can be
   directly mapped into L2NM.

   o  Service requirements: The service requirements can be directly
      taken from L2SM to L2NM.

   o  Sites: The sites from L2SM are used to select the Service Prodider
      node.  The site information is NOT maintained in L2NM

4.2.  Relation with Network Topology

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

4.3.  Relation with Device Models

   Creating services in the l2vpn-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 L2NM vpn-service container.  Note that L2NM is NOT a device
   model.

5.  YANG Module

<CODE BEGINS>file "ietf-l2vpn-ntw@2020-05-26.yang"
module ietf-l2vpn-ntw {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw";
  prefix l2vpn-ntw;

  import ietf-inet-types {
    prefix inet;
    reference
      "Section 4 of RFC 6991";
  }
  import ietf-yang-types {
    prefix yang;
    reference
      "Section 3 of RFC 6991";
  }
  import ietf-netconf-acm {
    prefix nacm;
    reference
      "RFC 8341: Network Configuration Access Control Model";
  }
  import ietf-l3vpn-ntw {
    prefix l3vpn-ntw;
    reference
      "RFC NNNN: A Layer 3 VPN Network YANG Model";
  }
  import ietf-l2vpn-svc {
    prefix l2vpn-svc;
    reference
      "RFC 8466: YANG Data Model for Layer 2 Virtual Private
        Network (L2VPN) Service Delivery";
  }
  import ietf-packet-fields {
    prefix pf;
    reference
      "RFC 8519 - YANG Data Model for Network Access Control
                  Lists (ACLs).";
  }
  import ietf-routing-types {
    prefix rt-types;
    reference
      "RFC 8294: Common YANG Data Types for the Routing Area";
  }

  organization
    "IETF OPSA (Operations and Management Area) Working Group";

  contact
    "WG Web:   <http://tools.ietf.org/wg/opsawg/>
        WG List:  <mailto:opsawg@ietf.org>
        Editor:    Samier Barguil
                  <mailto:samier.barguilgiraldo.ext@telefonica.com>
        Editor:    Oscar Gonzalez de Dios
                  <mailto:oscar.gonzalezdedios@telefonica.com>
        Author:    Mohamed Boucadair
                  <mailto:mohamed.boucadair@orange.com>
        Author:    Luis Angel Munoz
                  <mailto:luis-angel.munoz@vodafone.com>
        Author:    Luay Jalil
                  <mailto:luay.jalil@verizon.com>
        Author:    Jichun Ma
                  <mailto:majc16@chinaunicom.cn>
    ";
  description
    "The YANG module defines a generic network configuration
     model for Layer 2 VPN services common across all of the
     vendor implementations.

     Copyright (c) 2020 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.";

  revision 2020-05-26 {
    description
      "Third revision -02 version";
    reference
      "RFC XXXX: A Layer 2 VPN Network YANG Model.";
  }

  /* Features */

 feature multicast-like {
    description
      "Indicates the support of multicast-like capabilities
       in a L2VPN.";

  }

  feature extranet-vpn {
    description
      "Indicates the Support of Extranet VPN.";
  }

  feature target-sites {
    description
      "Indicates the support of 'target-sites' match flow
       parameter.";
  }

  feature l2cp-control {
    description
      "Indicates the support of L2CP control.";
  }

  feature input-bw {
    description
      "Indicates the suppport of Input Bandwidth
      in a VPN.";
  }

  feature output-bw {
    description
      "Indicates the support of Output Bandwidth in
       a VPN";
  }

  feature uni-list {
    description
      "Indicates thesupport of UNI list in a VPN.";
  }

  feature cloud-access {
    description
      "Indicates the support of a VPN to connect to a Cloud Service
       provider.";
  }

  feature oam-3ah {
    description
      "Indicates the support of OAM 802.3ah.";
  }

  feature micro-bfd {
    description
      "Indicates the support of Micro-BFD.";
  }

  feature bfd {
    description
      "Indicates the support of BFD.";
  }

  feature signaling-options {
    description
      "Indicates the support of signalling option.";
  }

  feature site-diversity {
    description
      "Indicates the support of site diversity constraints in
       a VPN.";
  }

  feature encryption {
    description
      "Indicates the support of encryption.";
  }

  feature always-on {
    description
      "Indicates the support for always-on access
       constraint.";
  }

  feature requested-type {
    description
      "Indicates the support for requested-type access
       constraint.";
  }

  feature bearer-reference {
    description
      "Indicates the support for bearer-reference access
       constraint.";
  }

  feature qos {
    description
      "Indicates the support of Class of Services.";
  }

  feature lag-interface {
    description
      "Enable lag-interface.";
  }

  feature vlan {
    description
      "Indicates the support of VLAN.";
  }

  feature dot1q {
    description
      "Indicates the support of Dot1Q.";
  }

  feature sub-inf {
    description
      "Indicates the support of Sub Interface.";
  }

  feature qinq {
    description
      "Indicates the support of QinQ.";
  }

  feature qinany {
    description
      "Indicates the support of QinAny.";
  }

  feature atm {
    description
      "Indicates the support of ATM.";
  }

  feature vxlan {
    description
      "Indicates the support of VxLAN.";
  }

  feature ipv4 {
    description
      "Indicates the support in a VPN.";
  }

  feature ipv6 {
    description
      "Indicates the support in a VPN.";
  }
  feature lan-tag {
    description
      "Indicates the LAN Tag support in a VPN.";
  }

  /* Typedefs */

  typedef protocol-type {
    type enumeration {
      enum GRE {
        value 0;
        description
          "Transport based on GRE.";
      }
      enum LDP {
        value 1;
        description
          "Transport based on LDP.";
        reference
          "RFC 5036: LDP Specification";
      }
      enum BGP {
        value 2;
        description
          "Transport based on BGP.";
        reference
          "RFC 4760: Multiprotocol Extensions for BGP-4";
      }
      enum SR {
        value 3;
        description
          "Transport based on Segment Routing";
        reference
         "RFC 8660: Segment Routing with the MPLS Data Plane";
      }
      enum SR-TE {
        value 4;
        description
          "Transport based on Segment Routing for Traffic
           Engineering";
      }
      enum RSVP-TE {
        value 5;
        description
          "Transport based on RSVP-TE signaled tunnels";
        reference
         "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels";
      }

    }
    description
      "This are attributes used to identify underly
       transport protocols used to deliver the service.";
  }

  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 an attribute used to determine the
       operational status of a particular element.";
  }

  typedef svc-id {
    type string;
    description
      "Indicates the type of service component identifier.";
  }

  typedef ccm-priority-type {
    type uint8 {
      range "0..7";
    }
    description
      "A 3 bit priority value to be used in the VLAN tag,
       if present in the transmitted frame.";
  }

  typedef control-mode {
    type enumeration {
      enum peer {
        description
          "Peer mode, i.e., participate in the protocol towards
           the CE. Peering is common for LACP  and E-LMI and
           occasionally for LLDP. For virtual private services
           the Subscriber can also request that the Service
           Provider peer spanning tree.";
      }
      enum tunnel {
        description
          "Tunnel mode,i.e.,pass to the egress or destination site.
           For EPL, the expectation is that L2CP frames are
           tunneled.";
      }
      enum discard {
        description
          "Discard mode,i.e.,discard the frame.";
      }
    }
    description
      "Defining a type of the control mode on L2CP protocols.";
  }

  typedef neg-mode {
    type enumeration {
      enum full-duplex {
        description
          "Defining Full duplex mode";
      }
      enum auto-neg {
        description
          "Defining Auto negotiation mode";
      }
    }
    description
      "Defining a type of the negotiation mode";
  }

  /* Identities */

  identity multicast-tree-type {
    base l2vpn-svc:multicast-tree-type;
    description
      "Base identity for multicast tree type.";
  }

  identity mapping-type {
    base l2vpn-svc:multicast-gp-address-mapping;
    description
      "Identity mapping-type.";

  }

  identity tf-type {
    base l2vpn-svc:tf-type;
    description
      "Identity traffic-type";
  }

  identity pwe-encapsulation-type {
    base l2vpn-svc:encapsulation-type;
    description
      "Identity pwe-encapsulation-type";
  }

  identity l2tp-pw-type {
    description
      "Identity for L2TP PW type";
  }

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

  identity ethernet-type {
    base encapsulation-type;
    description
      "Identity for encapsulation type";
  }

  identity vlan-type {
    base encapsulation-type;
    description
      "Identity for encapsulation type";
  }

  identity protection-mode {
    description
      "Identity of protection mode";
  }

  identity oneplusone {
    base protection-mode;
    description
      "In this scheme, the primary circuit will be
       protected by a backup circuit, typically meeting certain
       diverse path/fiber/site/node criteria.  Both primary and
       protection circuits are provisioned to be in the active
       forward ing state. The subscriber may choose to send the
       same service frames across both circuits simultaneously.";
  }

  identity one-to-one {
    base protection-mode;
    description
      "In this scheme, a backup circuit to the primary
       circuit is provisioned.  Depending on the implementation
       agreement, the protection circuits may either always be
       in active forwarding state, or may only become active when
       a faulty state is detected on the primary circuit.";
  }

  identity eth-inf-type {
    base l2vpn-svc:eth-inf-type;
    description
      "Identity of Ethernet Interface Type";
  }

  identity bw-type {
    base l2vpn-svc:bw-type;
    description
      "Identity of bandwidth";
  }

  identity site-type {
    description
      "Identity of site type.";
  }

  identity uni {
    base site-type;
    description
      "Identity of User Network Interface ";
  }

  identity enni {
    base site-type;
    description
      "Identity of External Network to Network Interface";
  }

  identity service-type {
    base l2vpn-svc:service-type;
    description
      "Base Identity of service type.";
  }
  identity bundling-type {
    base l2vpn-svc:bundling-type;
    description
      "This is base identity for Bundling type. It supports
       multiple CE-VLAN associated with L2VPN service or all
       CE-VLANs associated with L2VPN service.";
  }

  identity color-id {
    base l2vpn-svc:color-id;
    description
      "base identity of color id";
  }

  identity cos-id {
    base l2vpn-svc:cos-id;
    description
      "Identity of class of service id";
  }

  identity color-type {
    base l2vpn-svc:color-type;
    description
      "Identity of color types";
  }

  identity perf-tier-opt {
    description
      "Identity of performance tier option.";
  }

  identity metro {
    base perf-tier-opt;
    description
      "Identity of metro";
  }

  identity regional {
    base perf-tier-opt;
    description
      "Identity of regional";
  }

  identity continental {
    base perf-tier-opt;
    description
      "Identity of continental";
  }
  identity global {
    base perf-tier-opt;
    description
      "Identity of global";
  }

  identity policing {
    description
      "Identity of policing type";
  }

  identity one-rate-two-color {
    base policing;
    description
      "Identity of one-rate, two-color (1R2C)";
  }

  identity two-rate-three-color {
    base policing;
    description
      "Identity of two-rate, three-color (2R3C)";
  }

  identity bum-type {
    base l2vpn-svc:bum-type;
    description
      "Identity of BUM type";
  }

  identity loop-prevention-type {
    base l2vpn-svc:loop-prevention-type;
    description
      "Identity of loop prevention";
  }

  identity lacp-state {
    base l2vpn-svc:lacp-state;
    description
      "Identity of LACP state";
  }

  identity lacp-mode {
  base l2vpn-svc:lacp-mode;
    description
      "Identity of LACP mode";
  }

  identity lacp-speed {
    base l2vpn-svc:lacp-speed;
    description
      "Identity of LACP speed";
  }

  identity vpn-signaling-type {
    description
      "Identity of VPN signaling types";
  }

  identity l2vpn-bgp {
    base vpn-signaling-type;
    description
      "Identity of l2vpn-bgp";
  }

  identity evpn-bgp {
    base vpn-signaling-type;
    description
      "Identity of evpn-bgp";
  }

  identity t-ldp {
    base vpn-signaling-type;
    description
      "Identity of t-ldp.";
  }

  identity h-vpls {
    base vpn-signaling-type;
    description
      "Identity for h-vpls";
  }

  identity l2tp {
    base vpn-signaling-type;
    description
      "Identity of l2tp.";
  }

  identity t-ldp-pwe-type {
    description
      "Identity for t-ldp-pwe-type.";
  }

  identity vpws-type {
    base t-ldp-pwe-type;
    description
      "Identity for VPWS";
  }

  identity vpls-type {
    base t-ldp-pwe-type;
    description
      "Identity for vpls";
  }

  identity hvpls {
    base t-ldp-pwe-type;
    description
      "Identity for h-vpls";
  }

  identity l2vpn-type {
    description
      "Layer 2 VPN types";
  }

  identity l2vpn-vpws {
    base l2vpn-type;
    description
      "VPWS L2VPN type.";
  }

  identity l2vpn-vpls {
    base l2vpn-type;
    description
      "VPLS L2VPN type.";
  }

  identity distribute-vpls {
    base l2vpn-type;
    description
      "distribute VPLS L2VPN type.";
  }

  identity evpn-type {
    description
      "Ethernet VPN types";
  }

  identity evpn-vpws {
    base evpn-type;
    description
      "VPWS support in EVPN.";
  }
  identity evpn-pbb {
    base evpn-type;
    description
      " Provider Backbone Bridging Support in EVPN.";
  }

  identity management {
    base l2vpn-svc:management;
    description
      "Base identity for site management scheme.";
  }

  identity address-family {
    base l2vpn-svc:address-family;
    description
      "Base identity for an address family.";
  }

  identity vpn-topology {
    base l3vpn-ntw:vpn-topology;
    description
      "Base identity for VPN topology.";
  }

  identity site-role {
    base l2vpn-svc:site-role;
    description
      "Base identity for site type.";
  }

  identity any-to-any-role {
    base site-role;
    description
      "Any-to-any-role site type.";
  }

  identity pm-type {
    base l2vpn-svc:pm-type;
    description
      "Performance monitor type";
  }

  identity fault-alarm-defect-type {
    base l2vpn-svc:fault-alarm-defect-type;
    description
      "Indicating the alarm priority defect";
  }
  identity frame-delivery-mode {
   base l2vpn-svc:frame-delivery-mode;
    description
      "Delivery types";
  }

  identity pw-topo-type {
    base l2vpn-svc:site-network-access-type;
    description
      "base identity for pw topology Type";
  }

  identity placement-diversity {
   base l2vpn-svc:placement-diversity;
    description
      "Base identity for site placement
       constraints";
  }

  identity l2-access-type {
    description
      "This identify the access type
       of the vpn acccess interface";
  }

  identity untag {
    base l2-access-type;
    description
      "Untag";
  }

  identity port {
    base l2-access-type;
    description
      "Port";
  }

  identity dot1q {
    base l2-access-type;
    description
      "Qot1q";
  }

  identity qinq {
    base l2-access-type;
    description
      "QinQ";
  }
  identity sub-interface {
    base l2-access-type;
    description
      "Create a default sub-interface and keep vlan.";
  }

  identity atm {
    base l2-access-type;
    description
      "ATM Cell.";
  }

  identity vxlan {
    base l2-access-type;
    description
      "Vxlan access into the vpn";
  }

  identity provision-model {
   base l2vpn-svc:provision-model;
    description
      "base identity for provision model.";
  }

  identity mac-learning-mode {
   base l2vpn-svc:mac-learning-mode;
    description
      "MAC learning mode";
  }

  identity vpn-policy-filter-type {
   base l2vpn-svc:vpn-policy-filter-type;
    description
      "Base identity for filter type.";
  }

  identity mac-action {
   base l2vpn-svc:mac-action;
    description
      "Base identity for MAC action.";
  }

  identity load-balance-method {
    description
      "Base identity for load balance method.";
  }

  identity fat-pw {
    base load-balance-method;
    description
      "Identity for Fat PW. Fat label is
       applied to Pseudowires across MPLS
       network.";
  }

  identity entropy-label {
    base load-balance-method;
    description
      "Identity for entropy label.Entropy label
       is applied to IP forwarding,
       L2VPN or L3VPN across MPLS network";
  }

  identity vxlan-source-port {
    base load-balance-method;
    description
      "Identity for vxlan source port.VxLAN
       Source Port is one load balancing method.";
  }

  identity qos-profile-direction {
   base l2vpn-svc:qos-profile-direction;
    description
      "Base identity for qos profile direction.";
  }

  identity vxlan-peer-mode {
   base l2vpn-svc:vxlan-peer-mode;
    description
      "Base identity for vxlan peer mode.";
  }

  identity customer-application {
   base l2vpn-svc:customer-application;
    description
      "Base identity for customer application.";
  }

  identity precedence-type {
    description
      "Redundancy type. The service can be created
       with active and bakcup signalization.";
  }

  identity primary {
    base precedence-type;
    description
      "Identifies the Main L2VPN.";
  }

  identity backup {
    base precedence-type;
    description
      "Identifies the Backup L2VPN.";
  }

  /* Groupings */

  grouping vpn-route-targets {
    description
      "A grouping that specifies Route Target import-export rules
       used in a BGP-enabled VPN.";
    list vpn-target {
      key "id";
      leaf id {
        type int8;
        description
          "Identifies each VPN Target";
      }
      list route-targets {
        key "route-target";
        leaf route-target {
          type rt-types:route-target;
          description
            "Route Target value";
        }
        description
          "List of Route Targets.";
      }
      leaf route-target-type {
        type rt-types:route-target-type;
        mandatory true;
        description
          "Import/export type of the Route Target.";
      }
      description
        "l3vpn route targets. AND/OR Operations are available
         based on the RTs assigment";
    }
    reference
      "RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs)
       RFC4664: Framework for Layer 2 Virtual Private Networks
       (L2VPNs)";
    container vpn-policies {
      description
        "";
      leaf import-policy {
        type string;
        description
          "Reference to a VRF import policy.";
      }
      leaf export-policy {
        type string;
        description
          "Reference to a VRF export policy.";
      }
    }
  }

  grouping svc-transport-encapsulation {
    container transport-encapsulation {
      leaf-list protocol {
        type protocol-type;
        ordered-by user;
        description
          "Protocols used to support transport";
      }
      description
        "Container for the Transport Underlay.";
    }
    description
      "This grouping defines the type of underlay transport
    for VPN service.";
  }

  grouping split-horizon-group {
    container split-horizon {
      leaf group-name {
        type string;
        description
          "group-name of the Split Horizon";
      }
      description
        "Configuration with split horizon enabled";
    }
    description
      "Configuration with split horizon enabled";
  }

  grouping svc-precedence {
    container svc-precedence {
      leaf precedence {
        type identityref {
          base precedence-type;
        }
        description
          "Defining service redundancy in transport
           network.";
      }
      description
        "Transport netowrk precedence selector
         Primary or Secondary tunnel.";
    }
    description
      "Transport netowrk precedence selector
       Primary or Secondary tunnel.";
  }

  grouping vpn-service-cloud-access {
    container cloud-accesses {
      if-feature "cloud-access";
      list cloud-access {
        key "cloud-identifier";
        leaf cloud-identifier {
          type string;
          description
            "Identification of cloud service. Local
             admin meaning.";
        }
        choice list-flavor {
          case permit-any {
            leaf permit-any {
              type empty;
              description
                "Allow all sites.";
            }
          }
          case deny-any-except {
            leaf-list permit-site {
              type leafref {
                path "/l2vpn-ntw/sites/site/site-id";
              }
              description
                "Site ID to be authorized.";
            }
          }
          case permit-any-except {
            leaf-list deny-site {
              type leafref {
                path "/l2vpn-ntw/sites/site/site-id";
              }
              description
                "Site ID to be denied.";
            }
          }
          description
            "Choice for cloud access policy.";
        }
        container authorized-sites {
          list authorized-site {
            key "site-id";
            leaf site-id {
              type leafref {
                path "/l2vpn-ntw/sites/site/site-id";
              }
              description
                "Site ID.";
            }
            description
              "List of authorized sites.";
          }
          description
            "Configuration of authorized sites.";
        }
        container denied-sites {
          list denied-site {
            key "site-id";
            leaf site-id {
              type leafref {
                path "/l2vpn-ntw/sites/site/site-id";
              }
              description
                "Site ID.";
            }
            description
              "List of denied sites.";
          }
          description
            "Configuration of denied sites.";
        }
        description
          "Cloud access configuration.";
      }
      description
        "Container for cloud access configurations";
    }
    description
      "Grouping for vpn cloud definition";
  }

  grouping site-device {
    container device {
      list devices {
        key "device-id";
        leaf device-id {
          type string;
          description
            "Device ID";
        }
        leaf location {
          type leafref {
            path "/l2vpn-ntw/sites/site/locations/location/" +
                 "location-id";
          }
          description
            "Site name";
        }
        container management {
          leaf address {
            type inet:ip-address;
            description
              "Address";
          }
          leaf management-transport {
            type identityref {
              base address-family;
            }
            description
              "Transport protocol used for management.";
          }
          description
            "Container for management";
        }
        description
          "List of devices";
      }
      description
        "Devices configuration";
    }
    description
      "Device parameters for the site.";
  }

  grouping site-management {
    container management {
      leaf type {
        type identityref {
          base management;
        }
        description
          "Management type of the connection.";
      }
      description
        "Container for management";
    }
    description
      "Grouping for management";
  }

  grouping site-vpn-policy {
    container vpn-policies {
      list vpn-policy {
        key "vpn-policy-id";
        leaf vpn-policy-id {
          type string;
          description
            "Unique identifier for the VPN policy.";
        }
        list entries {
          key "id";
          leaf id {
            type string;
            description
              "Unique identifier for the policy entry.";
          }
          container filters {
            list filter {
              key "type";
              ordered-by user;
              leaf type {
                type identityref {
                  base vpn-policy-filter-type;
                }
                description
                  "Type of VPN Policy filter.";
              }

              description
                "List of filters used on the site. This list can
                 be augmented.";
            }
            description
              "If a more-granular VPN attachment is necessary,
               filtering can be used. If used, it permits the
               splitting of site LANs among multiple VPNs. The
               Site LAN can be split based on either LAN-tag
               or LAN prefix. If no filter is used, all the LANs
               will be part of the same VPNs with the same role.";
          }
          list vpn {
            key "vpn-id";
            leaf vpn-id {
              type leafref {
                path "/l2vpn-ntw/vpn-services/"
                   + "vpn-service/vpn-id";
              }
              mandatory true;
              description
                "Reference to an IP VPN.";
            }
            leaf site-role {
              type identityref {
                base site-role;
              }
              default "any-to-any-role";
              description
                "Role of the site in the IP VPN.";
            }
            description
              "List of VPNs the LAN is associated with.";
          }
          description
            "List of entries for export policy.";
        }
        description
          "List of VPN policies.";
      }
      description
        "VPN policy.";
    }
    description
      "VPN policy parameters for the site.";
  }

  grouping bum-frame-delivery {
    container bum-frame-delivery-modes {
      list bum-frame-delivery {
        key "traffic-type";
        leaf traffic-type {
          type identityref {
            base tf-type;

          }
          description
            "Type of frame delivery. It support unicast
             frame delivery, multicast frame delivery
             and broadcast frame delivery.";
        }
        leaf delivery-mode {
          type identityref {
            base frame-delivery-mode;
          }
          description
            " Define Frame Delivery Mode
             (unconditional[default], conditional, or discard).";
        }
        description
          "List of frame delivery type and mode.";
      }
      description
        "Define frame delivery type and mode.";
    }
    description
      "Grouping for unicast, mulitcast, broadcast frame delivery";
  }

  grouping cvlan-svc-map-grouping {
    list cvlan-id-to-svc-map {
      key "svc-id";
      leaf svc-id {
        type leafref {
          path "/l2vpn-ntw/vpn-services/vpn-service/vpn-id";
        }
        description
          "VPN Service identifier";
      }
      list cvlan-id {
        key "vid";
        leaf vid {
          type uint32;
          description
            "CVLAN ID";
        }
        description
          "List of CVLAN-ID to SVC Map configurations";
      }
      description
        "List for cvlan-id to L2VPn Service map configurations";
    }
    description
      "Grouping for cvlan to L2VPN service mapping";
  }

  grouping customer-location-info {
    container locations {
      list location {
        key "location-id";
        leaf location-id {
          type string;
          description
            "Location ID";
        }
        leaf address {
          type string;
          description
            "Address (number and street) of the site.";
        }
        leaf zip-code {
          type string;
          description
            "ZIP code of the site.";
        }
        leaf state {
          type string;
          description
            "State of the site. This leaf can also be used to
             describe a region for country who does not have
             states.";
        }
        leaf city {
          type string;
          description
            "City of the site.";
        }
        leaf country-code {
          type string;
          description
            "Country of the site.";
        }
        description
          "List for location";
      }
      description
        "Location of the site.";
    }
    description
      "This grouping defines customer location parameters";
  }
  grouping site-diversity {
    container site-diversity {
      if-feature "site-diversity";
      container groups {
        list group {
          key "group-id";
          leaf group-id {
            type string;
            description
              "Group-id the site is belonging to";
          }
          description
            "List of group-id";
        }
        description
          "Groups the site is belonging to.
           All site network accesses will inherit those group
           values.";
      }
      description
        "Diversity constraint type.";
    }
    description
      "This grouping defines site diversity parameters";
  }

  grouping site-service {
    description
      "This grouping defines site service parameters";
  }

  grouping vpn-service-multicast {
    container multicast-like {
      if-feature "multicast-like";
      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.";
      }

      uses bum-frame-delivery;
      leaf multicast-gp-port-mapping {
        type identityref {
          base mapping-type;
        }
        description
          "Describe the way in which each interface is associated
           with the Multicast group";
      }
      description
        "Multicast global parameters for the VPN service.";
    }
    description
      "Grouping for multicast VPN definition.";
  }

  grouping vpn-extranet {
    container extranet-vpns {
      if-feature "extranet-vpn";
      list extranet-vpn {
        key "vpn-id";
        leaf vpn-id {
          type svc-id;
          description
            "Identifies the target VPN.";
        }
        leaf local-sites-role {
          type identityref {
            base site-role;
          }
          default "any-to-any-role";
          description
            "This describes the role of the
             local sites in the target VPN topology.";
        }
        description
          "List of extranet VPNs the local VPN is attached to.";
      }
      description
        "Container for extranet VPN configuration.";
    }
    description
      "Grouping for extranet VPN configuration.
       This provides an easy way to interconnect
       all sites from two VPNs.";
  }

  grouping signaling-options-grouping {
    list signaling-options {
      key "type";
      leaf type {
        type identityref {
          base vpn-signaling-type;
        }
        description
          "VPN signaling types";
      }
      container l2vpn-bgp {
        when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'l2vpn-ntw:l2vpn-bgp'" {
          description
            "Only applies when vpn signaling type is l2vpn
             BGP protocol.";
        }
        leaf vpn-id {
          type leafref {
            path "/l2vpn-ntw/vpn-services/vpn-service/vpn-id";
          }
          description
            "Identifies the target VPN";
        }
        leaf type {
          type identityref {
            base l2vpn-type;
          }
          description
            "L2VPN types";
        }
        leaf pwe-encapsulation-type {
          type identityref {
            base pwe-encapsulation-type;
          }
          description
            "PWE Encapsulation Type";
        }
        uses vpn-route-targets;
        container pwe-mtu {
          leaf allow-mtu-mismatch {
            type boolean;
            description
              "Allow MTU mismatch";
          }
          description
            "Container of PWE MTU configurations";
        }
        leaf address-family {
          type reserved?
  |  |  |     |  |     |     |       uint8
  |  |  |     |  |     |     +--rw flags?
  |  |  |     |  |     |     |       bits
  |  |  |     |  |     |     +--rw window-size?
  |  |  |     |  |     |     |       uint16
  |  |  |     |  |     |     +--rw urgent-pointer?
  |  |  |     |  |     |     |       uint16
  |  |  |     |  |     |     +--rw options?
  |  |  |     |  |     |     |       binary
  |  |  |     |  |     |     +--rw (source-port)?
  |  |  |     |  |     |     |  +--:(source-port-range-or-operator)
  |  |  |     |  |     |     |     +--rw source-port-range-or-operator
  |  |  |     |  |     |     |        +--rw (port-range-or-operator)?
  |  |  |     |  |     |     |           +--:(range)
  |  |  |     |  |     |     |           |  +--rw lower-port
  |  |  |     |  |     |     |           |  |       inet:port-number
  |  |  |     |  |     |     |           |  +--rw upper-port
  |  |  |     |  |     |     |           |          inet:port-number
  |  |  |     |  |     |     |           +--:(operator)
  |  |  |     |  |     |     |              +--rw operator?
  |  |  |     |  |     |     |              |       operator
  |  |  |     |  |     |     |              +--rw port
  |  |  |     |  |     |     |                      inet:port-number
  |  |  |     |  |     |     +--rw (destination-port)?
  |  |  |     |  |     |        +--:(destination-port-range-or-operator)
  |  |  |     |  |     |           +--rw destination-port-range-or-operator
  |  |  |     |  |     |              +--rw (port-range-or-operator)?
  |  |  |     |  |     |                 +--:(range)
  |  |  |     |  |     |    |  +--rw lower-port
  |  |  |     |  |     |    |  |       inet:port-number
  |  |  |     |  |     |    |  +--rw upper-port
  |  |  |     |  |     |    |          inet:port-number
  |  |  |     |  |     |                 +--:(operator)
  |  |  |     |  |     |                    +--rw operator?
  |  |  |     |  |     |       |       operator
  |  |  |     |  |     |                    +--rw port
  |  |  |     |  |     |                            inet:port-number
  |  |  |     |  |     +--:(udp)
  |  |  |     |  |        +--rw udp
  |  |  |     |  |           +--rw length?
  |  |  |     |  |           |       uint16
  |  |  |     |  |           +--rw (source-port)?
  |  |  |     |  |           |  +--:(source-port-range-or-operator)
  |  |  |     |  |           |     +--rw source-port-range-or-operator
  |  |  |     |  |           |        +--rw (port-range-or-operator)?
  |  |  |     |  |           |           +--:(range)
  |  |  |     |  |           |           |  +--rw lower-port
  |  |  |     |  |           |           |  |       inet:port-number
  |  |  |     |  |           |           |  +--rw upper-port
  |  |  |     |  |           |           |          inet:port-number
  |  |  |     |  |           |           +--:(operator)
  |  |  |     |  |           |              +--rw operator?
  |  |  |     |  |           |              |       operator
  |  |  |     |  |           |              +--rw port
  |  |  |     |  |           |                      inet:port-number
  |  |  |     |  |           +--rw (destination-port)?
  |  |  |     |  |              +--:(destination-port-range-or-operator)
  |  |  |     |  |                 +--rw destination-port-range-or-operator
  |  |  |     |  |                    +--rw (port-range-or-operator)?
  |  |  |     |  |                       +--:(range)
  |  |  |     |  |          |  +--rw lower-port
  |  |  |     |  |          |  |       inet:port-number
  |  |  |     |  |          |  +--rw upper-port
  |  |  |     |  |          |          inet:port-number
  |  |  |     |  |                       +--:(operator)
  |  |  |     |  |                          +--rw operator?
  |  |  |     |  |             |       operator
  |  |  |     |  |                          +--rw port
  |  |  |     |  |                                  inet:port-number
  |  |  |     |  +--:(match-application)
  |  |  |     |     +--rw match-application?
  |  |  |     |             identityref {
            base address-family;
          }
          description
            "Address family used for management.";
        }
        description
          "Container for MP BGP L2VPN";
      }
      container evpn-bgp {
        when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'l2vpn-ntw:evpn-bgp'" {
          description
            "Only applies when vpn signaling type is EVPN
             BGP protocol.";
        }
        leaf vpn-id {
          type
  |  |  |     +--rw target-class-id?
  |  |  |             string
  |  |  +--rw qos-profile
  |  |     +--rw qos-profile* [profile]
  |  |        +--rw profile      leafref {
            path "/l2vpn-ntw/vpn-services/vpn-service/vpn-id";
          }
          description
            "Identifies the target EVPN";
        }
        leaf type {
          type
  |  |        +--rw direction?   identityref {
            base evpn-type;
          }
          description
            "L2VPN types";
        }
        leaf address-family {
          type
  |  +--rw precedence
  |     +--rw precedence?   identityref {
            base address-family;
          }
          description
            "Address family

                                 Figure 10

4.  Relation with other YANG Models

   The L2NM model, aimed at managing the L2VPN Services in a Service
   Provider Network controller/orchestrator has relations with other
   YANG modules.

4.1.  Relation with L2SM

   [RFC8466] defines a L2VPN Service YANG data Model (L2SM) that can be
   used for management.";
        }
        leaf mac-learning-mode {
          type identityref {
            base mac-learning-mode;
          }
          description
            "Indicates through which plane MAC addresses communication between customers and VPN service providers.
   Hence, the model provides inputs to the Network Operator to deliver
   such service to the customer.  Hence, most parts of the model can be
   directly mapped into L2NM.

   o  Service requirements: The service requirements can be directly
      taken from L2SM to L2NM.

   o  Sites: The sites from L2SM are
             advertised.";
        }
        leaf arp-suppress {
          type boolean;
          default "false";
          description
            "Indicates whether used to suppress ARP broadcast.";
        }
        description
          "Container for MP BGP L2VPN";
      }
      container t-ldp-pwe {
        when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'l2vpn-ntw:t-ldp'" {
          description
            "Only applies when vpn signaling type select the Service Prodider
      node.  The site information is NOT maintained in L2NM

4.2.  Relation with Network Topology

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

4.3.  Relation with Device Models

   Creating services in the l2vpn-ntw module will will lead at some
   point to the configuration of devices.  Hence, it is Target LDP.";
        }
        leaf type foreseen that
   the data for the device yang modules will be derived partially from
   the L2NM vpn-service container.  Note that L2NM is NOT a device
   model.

5.  YANG Module

<CODE BEGINS>file "ietf-l2vpn-ntw@2020-11-02.yang"
module ietf-l2vpn-ntw {
          type identityref
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw";
  prefix l2vpn-ntw;

  import ietf-inet-types {
            base t-ldp-pwe-type;
          }
          description
            "T-LDP PWE type";
    prefix inet;
    reference
      "Section 4 of RFC 6991";
  }
        leaf pwe-encapsulation-type {
          type identityref
  import ietf-yang-types {
            base pwe-encapsulation-type;
          }
          description
            "PWE Encapsulation Type.";
    prefix yang;
    reference
      "Section 3 of RFC 6991";
  }
        leaf control-word
  import ietf-vpn-common {
          type boolean;
          description
            "Control word configurations";
    prefix vpn-common;
    reference
      "RFC CCCC: A Layer 2/3 VPN Common YANG Model";
  }
        container pwe-mtu {
          leaf allow-mtu-mismatch

  organization
    "IETF OPSA (Operations and Management Area) Working Group";
  contact
    "WG Web:   <http://tools.ietf.org/wg/opsawg/>
     WG List:  <mailto:opsawg@ietf.org>

     Editor:    Samier Barguil
               <mailto:samier.barguilgiraldo.ext@telefonica.com>
     Editor:    Oscar Gonzalez de Dios
               <mailto:oscar.gonzalezdedios@telefonica.com>
     Author:    Mohamed Boucadair
               <mailto:mohamed.boucadair@orange.com>
     Author:    Luis Angel Munoz
                <mailto:luis-angel.munoz@vodafone.com>
     Author:    Luay Jalil
                <mailto:luay.jalil@verizon.com>
     Author:    Jichun Ma
                <mailto:majc16@chinaunicom.cn>
    ";
  description
    "The YANG module defines a generic network configuration
     model for Layer 2 VPN services common across all of the
     vendor implementations.

     Copyright (c) 2020 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.";

  revision 2020-11-02 {
            type boolean;
            description
              "Allow MTU mismatch";
          }
    description
            "Container of PWE MTU configurations";
      "Initial version.";
    reference
      "RFC XXXX: A Layer 2 VPN Network YANG Model.";
  }
        leaf provision-mode {
          type identityref

  /* Features */

  feature multicast-like {
            base provision-model;
          }
    description
            "provision-models. It
      "Indicates the support Double-Sided Provisioning
             model or single-side provisioning model.";

        }
        list ac-pw-list {
          key "peer-addr vc-id";
          leaf peer-addr {
            type inet:ip-address;
            description
              "Peer IP address."; of multicast-like capabilities
       in a L2VPN.";
  }
          leaf vc-id

  feature target-sites {
            type string;
    description
              "VC lable used to identify PW.";
      "Indicates the support of 'target-sites' match flow
       parameter.";
  }
          leaf pw-type {
            type identityref

  feature l2cp-control {
              base pw-topo-type;
            }
    description
              "PW topology type";
      "Indicates the support of L2CP control.";
  }
          leaf pw-priority

  feature output-bw {
            type uint32;
    description
              "Defines the priority for the PW.
               The higher the pw-priority value,
               the higher
      "Indicates the preference support of the PW will be."; Output Bandwidth in
       a VPN";
  }
  feature uni-list {
    description
            "List
      "Indicates thesupport of AC and PW bindings."; UNI list in a VPN.";
  }
        container qinq {
          when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'l2vpn-ntw:h-vpls'"

  feature oam-3ah {
    description
              "Only applies when t-ldp pwe type is h-vpls.";
      "Indicates the support of OAM 802.3ah.";
  }
          leaf s-tag

  feature micro-bfd {
            type uint32;
    description
              "S-TAG";
      "Indicates the support of Micro-BFD.";
  }
          leaf c-tag

  feature signaling-options {
            type uint32;
            description
              "C-TAG";
          }
          description
            "Container for QinQ";
        }
    description
          "Container
      "Indicates the support of T-LDP PWE configurations"; signalling option.";
  }
      container l2tp-pwe {
        when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'l2vpn-ntw:l2tp'"

  feature always-on {
    description
            "Applies when vpn signaling type is L2TP protocol.";
      "Indicates the support for always-on access
       constraint.";
  }
        leaf type {
          type identityref

  feature requested-type {
            base t-ldp-pwe-type;
          }
    description
            "T-LDP PWE type";
      "Indicates the support for requested-type access
       constraint.";
  }
        leaf encapsulation-type {
          type identityref

  feature vlan {
            base encapsulation-type;
          }
    description
            "Encapsulation type";
      "Indicates the support of VLAN.";
  }
        leaf control-word

  feature sub-inf {
          type boolean;
    description
            "Control word configurations";
      "Indicates the support of Sub Interface.";
  }
        list ac-pw-list {
          key "peer-addr vc-id";
          leaf peer-addr

  feature atm {
            type inet:ip-address;
    description
              "Peer IP address.";
      "Indicates the support of ATM.";
  }
          leaf vc-id

  feature vxlan {
            type string;
    description
              "VC lable used to identify PW.";
      "Indicates the support of VxLAN.";
  }

          leaf pw-type {
            type identityref

  feature lan-tag {
              base pw-topo-type;
            }
    description
              "PW topology type";
      "Indicates the LAN Tag support in a VPN.";
  }
          leaf pw-priority

  /* Typedefs */
  /* Identities */

  identity mapping-type {
            type uint32;
    base vpn-common:multicast-gp-address-mapping;
    description
              "PW priority";
      "Identity mapping-type.";
  }

  identity protection-mode {
    description
            "List
      "Identity of AC and PW bindings.";
        }
        description
          "Container for l2tp pw"; protection mode";
  }

  identity oneplusone {
    base protection-mode;
    description
        "List of VPN Signaling Option.";
      "In this scheme, the primary circuit will be
       protected by a backup circuit, typically meeting certain
       diverse path/fiber/site/node criteria.  Both primary and
       protection circuits are provisioned to be in the active
       forward ing state. The subscriber may choose to send the
       same service frames across both circuits simultaneously.";
  }

  identity one-to-one {
    base protection-mode;
    description
      "Grouping for signaling option";
      "In this scheme, a backup circuit to the primary
       circuit is provisioned.  Depending on the implementation
       agreement, the protection circuits may either always be
       in active forwarding state, or may only become active when
       a faulty state is detected on the primary circuit.";
  }

  grouping operational-requirements-ops {
    leaf actual-site-start

  identity bundling-type {
      type yang:date-and-time;
      config false;
    description
        "Optional leaf indicating actual date
         and time when
      "The base identity for the bundling type.  It supports
       multiple CE-VLANs associated with an L2VPN service or
       all CE-VLANs associated with an L2VPN service.";
  }

  identity multi-svc-bundling {
    base bundling-type;
    description
      "Identity for multi-service bundling, i.e.,
       multiple CE-VLAN IDs can be associated with an
       L2VPN service at a particular
         site actually started"; site.";
  }
    leaf actual-site-stop

  identity one2one-bundling {
      type yang:date-and-time;
      config false;
    base bundling-type;
    description
        "Optional leaf indicating actual date
         and time when the
      "Identity for one-to-one service bundling, i.e.,
       each L2VPN can be associated with only one CE-VLAN ID
       at a particular
         site actually stopped"; site.";
  }
    leaf bundling-type {
      type identityref

  identity all2one-bundling {
    base bundling-type;
    description
      "Identity for all-to-one bundling, i.e., all CE-VLAN IDs
       are mapped to one L2VPN service.";
  }

  identity color-id {
    description
        "Bundling type";
      "Base identity of the color ID.";
  }
    leaf default-ce-vlan-id

  identity color-id-cvlan {
      type uint32;
    base color-id;
    description
        "Default CE VLAN
      "Identity of the color ID set at site level."; based on a CVLAN.";
  }

  identity color-type {
    description
      "This grouping defines some operational parameters
       parameters";
      "Identity of color types.";
  }

  grouping cfm-802-grouping {
    leaf maid

  identity green {
      type string;
    base color-type;
    description
        "MA ID";
      "Identity of the 'green' color type.";
  }
    leaf mep-id
  identity yellow {
      type uint32;
    base color-type;
    description
        "Local MEP ID";
      "Identity of the 'yellow' color type.";
  }
    leaf mep-level

  identity red {
      type uint32;
    base color-type;
    description
        "MEP level";
      "Identity of the 'red' color type.";
  }
    leaf mep-up-down {
      type enumeration {
        enum up

  identity perf-tier-opt {
    description
            "MEP up";
      "Identity of performance tier option.";
  }
        enum down

  identity metro {
    base perf-tier-opt;
    description
            "MEP down";
      "Identity of metro";
  }

  identity regional {
    base perf-tier-opt;
    description
      "Identity of regional";
  }

  identity continental {
    base perf-tier-opt;
    description
        "MEP up/down";
      "Identity of continental";
  }
    leaf remote-mep-id

  identity global {
      type uint32;
    base perf-tier-opt;
    description
        "Remote MEP ID";
      "Identity of global";
  }
    leaf cos-for-cfm-pdus

  identity policing {
      type uint32;
    description
        "COS for CFM PDUs";
      "Identity of policing type";
  }
    leaf ccm-interval

  identity one-rate-two-color {
      type uint32;
    base policing;
    description
        "CCM interval";
      "Identity of one-rate, two-color (1R2C)";
  }
    leaf ccm-holdtime

  identity two-rate-three-color {
      type uint32;
    base policing;
    description
        "CCM hold time";
      "Identity of two-rate, three-color (2R3C)";
  }
    leaf alarm-priority-defect {
      type identityref

  identity loop-prevention-type {
        base fault-alarm-defect-type;
      }
    description
        "The lowest priority defect that is
         allowed to generate a Fault Alarm.
         The non-existence
      "Identity of this leaf means
         that no defects are to be reported"; loop prevention.";
  }
    leaf ccm-p-bits-pri

  identity shut {
      type ccm-priority-type;
    base loop-prevention-type;
    description
        "The priority parameter for CCMs transmitted by the MEP";
      "Identity of shut protection.";
  }

  identity trap {
    base loop-prevention-type;
    description
      "Grouping for 802.1ag CFM attribute";
      "Identity of trap protection.";
  }

  grouping y-1731 {
    list y-1731 {
      key "maid";
      leaf maid

  identity t-ldp-pwe-type {
        type string;
    description
          "MA ID ";
      "Identity for t-ldp-pwe-type.";
  }
      leaf mep-id

  identity vpws-type {
        type uint32;
    base t-ldp-pwe-type;
    description
          "Local MEP ID";
      "Identity for VPWS";
  }
      leaf type {
        type identityref

  identity vpls-type {
    base pm-type;
        } t-ldp-pwe-type;
    description
          "Performance monitor types";
      "Identity for vpls";
  }
      leaf remote-mep-id

  identity hvpls {
        type uint32;
    base t-ldp-pwe-type;
    description
          "Remote MEP ID";
      "Identity for h-vpls";

  }
      leaf message-period

  identity l2vpn-type {
        type uint32;
    description
          "Defines the interval between OAM messages. The message
           period is expressed in milliseconds";
      "Layer 2 VPN types";
  }
      leaf measurement-interval

  identity l2vpn-vpws {
        type uint32;
    base l2vpn-type;
    description
          "Specifies the measurement interval for statistics. The
           measurement interval is expressed in seconds";
      "VPWS L2VPN type.";
  }
      leaf cos

  identity l2vpn-vpls {
        type uint32;
    base l2vpn-type;
    description
          "Class of service";
      "VPLS L2VPN type.";
  }
      leaf loss-measurement

  identity distribute-vpls {
        type boolean;
    base l2vpn-type;
    description
          "Whether enable loss measurement";
      "distribute VPLS L2VPN type.";
  }
      leaf synthethic-loss-measurement

  identity evpn-type {
        type boolean;
    description
          "Indicate whether enable synthetic loss measurement";
      "Ethernet VPN types";
  }
      container delay-measurement {
        leaf enable-dm

  identity evpn-vpws {
          type boolean;
    base evpn-type;
    description
            "Whether to enable delay measurement";
      "VPWS support in EVPN.";
  }
        leaf two-way

  identity evpn-pbb {
          type boolean;
    base evpn-type;
    description
            "Whether delay measurement is two-way (true) of one-
             way (false)";
      " Provider Backbone Bridging Support in EVPN.";
  }

  identity pm-type {
    description
          "Container for delay measurement";
      "Performance-monitoring type.";
  }
      leaf frame-size

  identity loss {
        type uint32;
    base pm-type;
    description
          "Frame size";
      "Loss measurement.";
  }
      leaf session-type {
        type enumeration {
          enum proactive

  identity delay {
    base pm-type;
    description
              "Proactive mode";
      "Delay measurement.";
  }
          enum on-demand

  identity mac-learning-mode {
    description
              "On demand mode";
          }
      "MAC learning mode.";
  }

  identity data-plane {
    base mac-learning-mode;
    description
          "Session type";
      "User MAC addresses are learned through ARP broadcast.";
  }

  identity control-plane {
    base mac-learning-mode;
    description
        "List for y-1731.";
      "User MAC addresses are advertised through EVPN-BGP.";
  }

  identity mac-action {
    description
      "Grouping
      "Base identity for y.1731"; a MAC action.";
  }

  grouping enni-site-info-grouping {
    container site-info {
      leaf site-name

  identity drop {
        type string;
    base mac-action;
    description
          "Site name";
      "Identity for dropping a packet.";
  }
      leaf address

  identity flood {
        type inet:ip-address;
    base mac-action;
    description
          "Address";
      "Identity for packet flooding.";
  }
      leaf Edge-Gateway-Device-Info

  identity warning {
        type string;
        description
          "Edge Gateway Device Info ";
      }
    base mac-action;
    description
        "Container of site info configurations";
      "Identity for sending a warning log message.";
  }

  identity load-balance-method {
    description
      "Grouping
      "Base identity for site information"; load balance method.";
  }

  grouping acl-grouping {
    container access-control-list {
      list mac {
        key "mac-address";
        leaf mac-address

  identity fat-pw {
          type yang:mac-address;
    base load-balance-method;
    description
            "MAC address.";
      "Identity for Fat PW. Fat label is
       applied to Pseudowires across MPLS
       network.";
  }

  identity entropy-label {
    base load-balance-method;
    description
          "List
      "Identity for MAC."; entropy label.Entropy label
       is applied to IP forwarding,
       L2VPN or L3VPN across MPLS network";
  }

  identity vxlan-source-port {
    base load-balance-method;
    description
        "Container
      "Identity for access control List."; vxlan source port.VxLAN
       Source Port is one load balancing method.";
  }

  identity precedence-type {
    description
      "This grouping defines Access Control List.";
      "Redundancy type. The service can be created
       with active and bakcup signalization.";
  }

  grouping lacp-grouping {
    container lacp {
      leaf lacp-state

  identity primary {
        type boolean;
    base precedence-type;
    description
          "LACP on/off";
      "Identifies the Main L2VPN.";
  }
      leaf lacp-mode {
        type boolean;

  identity backup {
    base precedence-type;
    description
          "LACP mode";
      "Identifies the Backup L2VPN.";
  }
  /* Groupings */

  grouping cfm-802-grouping {
    leaf lacp-speed maid {
      type boolean; string;
      description
          "LACP speed";
        "MA ID";
    }
    leaf mini-link mep-id {
      type uint32;
      description
          "The minimum aggregate bandwidth for a LAG";
        "Local MEP ID";
    }
    leaf system-priority mep-level {
      type uint16; uint32;
      description
          "Indicates the LACP priority for the system.
           The range is from 0 to 65535.
           The default is 32768.";
        "MEP level";
    }
      container micro-bfd {
        if-feature "micro-bfd";
    leaf micro-bfd-on-off mep-up-down {
      type enumeration {
        enum on up {
          description
                "Micro-bfd on";
            "MEP up";
        }
        enum off down {
          description
                "Micro-bfd off";
            "MEP down";
        }
      }
      description
            "Micro BFD ON/OFF";
        "MEP up/down";
    }
    leaf bfd-interval remote-mep-id {
      type uint32;
      description
            "BFD interval";
        "Remote MEP ID";
    }
    leaf bfd-hold-timer cos-for-cfm-pdus {
      type uint32;
      description
            "BFD hold timer";
        "COS for CFM PDUs";
    }
    leaf ccm-interval {
      type uint32;
      description
          "Container of Micro-BFD configurations";
        "CCM interval";
    }
      container bfd
    leaf ccm-holdtime {
        if-feature "bfd";
      type uint32;
      description
        "CCM hold time";
    }
    leaf bfd-enabled ccm-p-bits-pri {
      type boolean; vpn-common:ccm-priority-type;
      description
        "The priority parameter for CCMs transmitted by the MEP";
    }
    description
            "BFD activation";
      "Grouping for 802.1ag CFM attribute";
  }
        choice holdtime

  grouping y-1731 {
          case profile
    list y-1731 {
      key "maid";
      leaf profile-name maid {
        type string;
        description
                "Service provider well known profile.";
          "MA ID ";
      }
      leaf mep-id {
        type uint32;
        description
              "Service provider well known profile.";
          "Local MEP ID";
      }
          case fixed
      leaf type {
        type identityref {
          base pm-type;
        }
        description
          "Performance monitor types";
      }
      leaf fixed-value remote-mep-id {
        type uint32;
              units "msec";
        description
                "Expected hold time expressed in msec.";
            }
          "Remote MEP ID";
      }
      leaf message-period {
        type uint32;
        description
            "Choice for hold time flavor.";
          "Defines the interval between OAM messages. The message
           period is expressed in milliseconds";
      }
      leaf measurement-interval {
        type uint32;
        description
          "Container
          "Specifies the measurement interval for BFD."; statistics. The
           measurement interval is expressed in seconds";
      }
      container member-link-list {
        list member-link {
          key "name";
      leaf name cos {
        type string; uint32;
        description
              "Member link name";
          "Class of service";
      }
      leaf port-speed loss-measurement {
        type uint32; boolean;
        description
              "Port speed";
          "Whether enable loss measurement";
      }
      leaf mode synthethic-loss-measurement {
        type neg-mode; boolean;
        description
              "Negotiation mode";
          "Indicate whether enable synthetic loss measurement";
      }
      container delay-measurement {
        leaf link-mtu enable-dm {
          type uint32; boolean;
          description
              "Link MTU size.";
            "Whether to enable delay measurement";
        }
          container oam-802.3ah-link {
            if-feature "oam-3ah";
        leaf enable two-way {
          type boolean;
          description
                "Indicate whether support oam 802.3 ah link";
            "Whether delay measurement is two-way (true) of one-
             way (false)";
        }
        description
          "Container for oam 802.3 ah link.";
          }
          description
            "Member link";
        }
        description
          "Container of Member link list"; delay measurement";
      }
      leaf flow-control frame-size {
        type string; uint32;
        description
          "Flow control";
          "Frame size";
      }
      leaf lldp session-type {
        type boolean; enumeration {
          enum proactive {
            description
          "LLDP";
              "Proactive mode";
          }
          enum on-demand {
            description
        "LACP";
              "On demand mode";
          }
        }
        description
          "Session type";
      }
      description
        "List for y-1731.";
    }
    description
      "Grouping for lacp"; y.1731";
  }

  grouping phy-interface-grouping {

  /* MAIN L2VPN SERVICE */

  container phy-interface l2vpn-ntw {
      leaf port-number
    container vpn-profiles {
        type uint32;
      uses vpn-common:vpn-profile-cfg;
      description
          "Port number";
        "Container for VPN Profiles.";
    }
    container vpn-services {
      list vpn-service {
        key "vpn-id";
        uses vpn-common:service-status;
        uses vpn-common:vpn-description;
        leaf port-speed l2sm-vpn-id {
          type uint32; vpn-common:vpn-id;
          description
          "Port speed";
            "Pointer to the L2SM service.";
        }
        leaf mode vpn-svc-type {
          type neg-mode; identityref {
            base vpn-common:vpn-signaling-type;
          }
          description
          "Negotiation mode";
            "Service type";
        }
        leaf phy-mtu svc-topo {
          type uint32; identityref {
            base vpn-common:vpn-topology;
          }
          description
          "PHY MTU";
            "Defining service topology, such as
             any-to-any, hub-spoke, etc.";
        }
        container multicast-like {
          if-feature "vpn-common:multicast";
          leaf flow-control enabled {
            type string; boolean;
            default "false";
            description
          "Flow control";
              "Enables multicast.";
          }
      leaf physical-if
          container customer-tree-flavors {
            leaf-list tree-flavor {
              type string; identityref {
                base vpn-common:multicast-tree-type;
              }
              description
          "Physical interface";
                "Type of tree to be used.";
            }
            description
              "Type of trees used by customer.";
          }
          description
            "Multicast like container";
        }
        container extranet-vpns {
          if-feature "vpn-common:extranet-vpn";
          list extranet-vpn {
            key "vpn-id";
            leaf circuit-id vpn-id {
              type string; vpn-common:vpn-id;
              description
          "Circuit ID";
                "Identifies the target VPN.";
            }
            leaf lldp local-sites-role {
              type boolean; identityref {
                base vpn-common:role;
              }
              default "vpn-common:any-to-any-role";
              description
          "LLDP";
                "This describes the role of the
                 local sites in the target VPN topology.";
            }
            description
              "List of extranet VPNs the local VPN is attached to.";
          }
          description
            "Container for extranet VPN configuration.";
        }
      container oam-802.3ah-link {
        if-feature "oam-3ah";
        leaf enable svc-mtu {
          type boolean;
          description
            "Indicate whether support oam 802.3 ah link";
        } uint32;
          description
          "Container for oam 802.3 ah link.";
            "SVC MTU, it is also known as the maximum transmission unit
             or maximum frame size,When a frame is larger than the MTU,
             it is broken down, or fragmented, into smaller pieces by the
             network protocol to accommodate the MTU of the network";

        }
        leaf uni-loop-prevention ce-vlan-preservation {
          type boolean;
          description
          "If this leaf set
            "Preserve the CE-VLAN ID from ingress to truth that egress,i.e.,
             CE-VLAN tag of the port automatically
           goes down when egress frame are identical to
             those of the ingress frame that yielded this egress
             service frame. If All-to-One bundling within a physical loopback site
             is detect."; Enabled, then preservation applies to all Ingress
             service frames. If All-to-One bundling is Disabled,
             then preservation applies to tagged Ingress service
             frames having CE-VLAN ID 1 through 4094.";
        }
        leaf ce-vlan-cos-perservation {
          type boolean;
          description
        "Container
            "CE vlan CoS preservation. PCP bits in the CE-VLAN tag
             of PHY Interface Attributes configurations";
    }
    description
      "Grouping for phy interface."; the egress frame are identical to those of the ingress
             frame that yielded this egress service frame.";
        }

  grouping lag-interface-grouping {
        uses vpn-common:svc-transport-encapsulation;
        container lag-interface vpn-nodes {
      if-feature "lag-interface";
          list lag-interface vpn-node {
            key "lag-interface-number"; "vpn-node-id ne-id";
            leaf lag-interface-number vpn-node-id {
              type uint32; vpn-common:vpn-id;
              description
            "LAG interface number";
                "";
            }
        uses lacp-grouping;
            leaf description
          "List of LAG interfaces";
      } {
              type string;
              description
        "Container of LAG interface attributes configuration";
    }
                "Textual description
      "Grouping for LAG interface"; of a VPN node.";
            }

  grouping dot1q-interface-grouping {
    container dot1q-interface {
            leaf l2-access-type node-role {
              type identityref {
                base l2-access-type; vpn-common:role;
              }
              default "vpn-common:any-to-any-role";
              description
          "L2 Access Encapsulation Type";
      }
      container dot1q {
        when "'../l2-access-type'='dot1q'";
        if-feature "dot1q";
                "Role of the vpn-node in the IP VPN.";
            }
            leaf physical-inf ne-id {
              type string;
              description
            "Physical Interface";
                "NE IP address";
            }
            leaf c-vlan-id port-id {
              type uint32;
          description
            "VLAN identifier";
        } string;
              description
          "Qot1q";
                "NE Port-id";
            }
      container sub-inf
            uses vpn-common:service-status;
            list signaling-options {
        when "'../l2-access-type'='sub-interface'";
        if-feature "sub-inf";
              key "type";
              leaf interface-description { type string;
          description
            "Interface description";
        }
        leaf sub-if-id {
                type uint32;
          description
            "Sub interface ID"; identityref {
                  base vpn-common:vpn-signaling-type;
                }
                description
          "sub interface";
                  "VPN signaling types";
              }
              container qinq l2vpn-bgp {
                when "'../l2-access-type'='qinq'";
        if-feature "qinq"; "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:l2vpn-bgp'" {
                  description
                    "Only applies when vpn signaling type is l2vpn
                     BGP protocol.";
                }
                leaf s-vlan-id pwe-encapsulation-type {
                  type uint32; identityref {
                    base vpn-common:encapsulation-type;
                  }
                  description
            "S-VLAN Identifier";
                    "PWE Encapsulation Type";
                }
                uses vpn-common:vpn-route-targets;
                container pwe-mtu {
                  leaf c-vlan-id allow-mtu-mismatch {
                    type uint32; boolean;
                    description
            "C-VLAN Identifier";
                      "Allow MTU mismatch";
                  }
                  description
          "QinQ";
                    "Container of PWE MTU configurations";
                }
      container qinany {
        if-feature "qinany";
                leaf s-vlan-id address-family {
                  type uint32; vpn-common:address-family;
                  description
            "S-Vlan ID";
                    "Address family used for router-id information.";
                }
                description
                  "Container for Q in Any"; MP BGP L2VPN";
              }
              container atm evpn-bgp {
                when "'../l2-access-type'='atm'";
        if-feature "atm"; "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:evpn-bgp'" {
                  description
                    "Only applies when vpn signaling type is EVPN
                     BGP protocol.";
                }
                leaf vpi vpn-id {
                  type uint32; leafref {
                    path "/l2vpn-ntw/vpn-services/vpn-service/vpn-id";
                  }
                  description
            "VPI Identifier";
                    "Identifies the target EVPN";
                }
                leaf vci type {
                  type uint32;
          description
            "VCI Identifier"; identityref {
                    base evpn-type;
                  }
                  description
          "ATM Cell.";
                    "L2VPN types";
                }
      container vxlan {
        when "'../l2-access-type'='vxlan'";
        if-feature "vxlan";
                leaf vni-id address-family {
                  type uint32; vpn-common:address-family;
                  description
            "VNI Identifier";
                    "Address family used for router-id information.";
                }
                leaf peer-mode mac-learning-mode {
                  type identityref {
                    base vxlan-peer-mode; mac-learning-mode;
                  }
                  description
            "specify the vxlan access mode";
                    "Indicates through which plane MAC addresses are
                     advertised.";
                }
        list peer-list {
          key "peer-ip";
                leaf peer-ip arp-suppress {
                  type inet:ip-address;
            description
              "Peer IP";
          }
          description
            "List for peer IP";
        } boolean;
                  default "false";
                  description
          "QinQ";
                    "Indicates whether to suppress ARP broadcast.";
                }
                description
                  "Container for dot1Q Interface";
    }
    description
      "Grouping for Layer2 access"; MP BGP L2VPN";
              }

  grouping ethernet-connection-grouping {
              container connection t-ldp-pwe {
      leaf port-id
                when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:t-ldp'" {
          type string;
                  description
            "Reference to the Port-id.
             The semantic of the Port-Id depends on the vendor's
             semantic. i.e ge-X/Y/Z , xe-X/Y/Z , et-X/Y/Z,AeXXX.YYY,
             aeXXX,GigabitEthernetX/Y/Z";
                    "Only applies when vpn signaling type is Target LDP.";
                }
                leaf encapsulation-type type {
                  type identityref {
                    base encapsulation-type; t-ldp-pwe-type;
                  }
                  description
          "Encapsulation Type";
                    "T-LDP PWE type";
                }
      leaf-list eth-inf-type
                leaf pwe-encapsulation-type {
                  type identityref {
                    base eth-inf-type;
        }
        description
          "Ethernet Interface Type"; vpn-common:encapsulation-type;
                  }
      uses dot1q-interface-grouping;
      uses phy-interface-grouping;
      uses lag-interface-grouping;
      uses cvlan-svc-map-grouping;
      uses split-horizon-group;
      uses l2cp-grouping;
                  description
        "Container for bearer";
                    "PWE Encapsulation Type.";
                }
                leaf pwe-mtu {
                  type uint16;
                  description
      "Grouping for bearer.";
                    "Allow MTU mismatch";
                }

  grouping svc-mtu-grouping
                list ac-pw-list {
                  key "peer-addr vc-id";
                  leaf svc-mtu peer-addr {
                    type uint32; inet:ip-address;
                    description
        "SVC MTU, it is also known as the maximum transmission unit
         or maximum frame size,When a frame is larger than the MTU,
         it is broken down, or fragmented, into smaller pieces by the
         network protocol to accommodate the MTU of the network";
                      "Peer IP address.";
                  }
                  leaf vc-id {
                    type vpn-common:vpn-id;
                    description
      "Grouping for service mtu.";
                      "VC lable used to identify PW.";
                  }

  grouping svc-preservation-grouping {
                  leaf ce-vlan-preservation pw-type {
                    type boolean; identityref {
                      base vpn-common:vpn-topology;
                    }
                    description
        "Preserve the CE-VLAN ID from ingress to egress,i.e.,
         CE-VLAN tag of the egress frame are identical to
         those of the ingress frame that yielded this egress
         service frame. If All-to-One bundling within a site
         is Enabled, then preservation applies to all Ingress
         service frames. If All-to-One bundling is Disabled,
         then preservation applies to tagged Ingress service
         frames having CE-VLAN ID 1 through 4094.";
                      "PW topology type";
                  }
                  leaf ce-vlan-cos-perservation pw-priority {
                    type boolean; uint32;
                    description
        "CE vlan CoS preservation. PCP bits in
                      "Defines the CE-VLAN tag
         of priority for the egress frame are identical to those PW.
                       The higher the pw-priority value,
                       the higher the preference of the ingress
         frame that yielded this egress service frame."; PW will be.";
                  }
                  description
      "Grouping for service preservation.";
                    "List of AC and PW bindings.";
                }

  grouping mac-addr-limit-grouping {
                container mac-addr-limit qinq {
      leaf mac-num-limit
                  when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:h-vpls'" {
        type uint16;
                    description
          "maximum number of MAC addresses learned from
           the subscriber for a single service instance.";
                      "Only applies when t-ldp pwe type is h-vpls.";

                  }
                  leaf time-interval s-tag {
                    type uint32;
        units "milliseconds";
                    description
          "The aging time of the mac address.";
                      "S-TAG";
                  }
                  leaf action c-tag {
                    type identityref {
          base mac-action; uint32;
                    description
                      "C-TAG";
                  }
                  description
          "specify the action when the upper limit is
           exceeded: drop the packet, flood the
           packet, or simply send a warning log message.";
                    "Container for QinQ";
                }
                description
                  "Container of MAC-Addr limit T-LDP PWE configurations";
              }
    description
      "Grouping for mac address limit";
  }

  grouping availability-grouping {
              container availability l2tp-pwe {
      leaf access-priority
                when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:l2tp'" {
        type uint32;
                  description
          "Access priority";
                    "Applies when vpn signaling type is L2TP protocol.";
                }
      choice redundancy-mode
                leaf type {
        case single-active
                  type identityref {
                    base t-ldp-pwe-type;
                  }
                  description
                    "T-LDP PWE type";
                }
                leaf single-active encapsulation-type {
                  type boolean;
            description
              "Single active"; identityref {
                    base vpn-common:encapsulation-type;
                  }
                  description
            "Single active case";
                    "Encapsulation type";
                }
        case all-active
                list ac-pw-list {
                  key "peer-addr vc-id";
                  leaf all-active peer-addr {
                    type boolean; inet:ip-address;
                    description
              "All active";
                      "Peer IP address.";
                  }
                  leaf vc-id {
                    type string;
                    description
            "All active case";
                      "VC lable used to identify PW.";
                  }
                  leaf pw-priority {
                    type uint32;
                    description
          "Redundancy mode choice";
                      "PW priority";
                  }
                  description
        "Container
                    "List of availability optional configurations"; AC and PW bindings.";
                }
                description
      "Grouping
                  "Container for availability"; l2tp pw";
              }
              description
                "List of VPN Signaling Option.";
            }

  grouping l2cp-grouping {
            container l2cp-control vpn-network-accesses {
      if-feature "l2cp-control";
              list vpn-network-access {
                key "id";
                leaf stp-rstp-mstp id {
                  type control-mode; vpn-common:vpn-id;
                  description
          "STP/RSTP/MSTP protocol type applicable to all UNIs";
                    "Identifier of network access";
                }
                leaf pause description {
                  type control-mode; string;
                  description
          "Pause protocol type applicable
                    "String to all UNIs"; describe the element.";
                }
                leaf lacp-lamp Interface-mtu {
                  type control-mode; uint32;
                  description
          "LACP/LAMP  ";
                    "Interface MTU, it is also known as the maximum
                     transmission unit or maximum frame size. When a
                     frame is larger than the MTU, it is broken down,
                     or fragmented, into smaller pieces by the
                     network protocol to accommodate the MTU of the
                     network";
                }
                uses vpn-common:service-status;
                container access-diversity {
                  if-feature "vpn-common:placement-diversity";
                  container groups {
                    leaf link-oam fate-sharing-group-size {
                      type control-mode; uint16;
                      description
          "Link OAM";
                        "Fate sharing group size.";
                    }
                    leaf esmc group-color {
                      type control-mode; string;
                      description
          "ESMC";
                        "Group color associated with a particular VPN.";
                    }
                    list group {
                      key "group-id";
                      leaf l2cp-802.1x group-id {
                        type control-mode; string;
                        description
          "802.x";
                          "Group-id the site network access
                           is belonging to";
                      }
      leaf e-lmi {
        type control-mode;
                      description
          "E-LMI";
                        "List of group-id";
                    }
      leaf lldp {
        type boolean;
                    description
          "LLDP protocol type applicable to all UNIs";
                      "Groups the fate sharing group member
                       is belonging to";
                  }
                  container constraints {
                    list constraint {
                      key "constraint-type";
                      leaf ptp-peer-delay constraint-type {
                        type control-mode; identityref {
                          base vpn-common:placement-diversity;
                        }
                        description
          "PTP peer delay";
                          "Diversity constraint type.";
                      }
                      container target {
                        choice target-flavor {
                          case id {
                            list group {
                              key "group-id";
                              leaf garp-mrp group-id {
                                type control-mode; string;
                                description
          "GARP/MRP";
                                  "The constraint will apply
                                   against this particular
                                   group-id";
                              }
                              description
        "Container
                                "List of L2CP control configurations"; groups";
                            }
    description
      "Grouping for l2cp control";
                          }

  grouping B-U-M-grouping {
    container broadcast-unknown-unicast-multicast
                          case all-accesses {
                            leaf multicast-site-type all-other-accesses {
                              type enumeration {
          enum receiver-only { empty;
                              description
                                "The constraint will apply
                                 against all other site only has receivers."; network
                                 access of this site";
                            }
          enum source-only {
            description
              "The site only has sources.";
                          }
          enum source-receiver
                          case all-groups {
                            leaf all-other-groups {
                              type empty;
                              description
                                "The site has both sources and receivers.";
          } constraint will apply
                                 against all other groups the
                                 customer is managing";
                            }
        default "source-receiver";
        description
          "Type of multicast site.";
                          }
      list multicast-gp-address-mapping {
        key "id";
        leaf id {
          type uint16;
                          description
            "Unique identifier
                            "Choice for the mapping."; group definition";
                        }
        leaf vlan-id {
          type uint32;
                        description
            "the VLAN ID
                          "The constraint will apply against
                           this list of the Multicast group"; groups";
                      }
        leaf mac-gp-address {
          type yang:mac-address;
                      description
            "the MAC address
                        "List of the Multicast group"; constraints";
                    }
                    description
                      "Constraints for placing this site
                        network access";
                  }
                  description
                    "Diversity parameters.";
                }
                container connection {
                  leaf port-lag-number encapsulation-type {
                    type uint32;
          description
            "the ports/LAGs belonging to the Multicast group"; identityref {
                      base vpn-common:encapsulation-type;
                    }
                    description
          "List of Port to group mappings.";
                      "Encapsulation Type";
                  }
      leaf bum-overall-rate
                  leaf-list eth-inf-type {
                    type uint32; identityref {
                      base vpn-common:encapsulation-type;
                    }
                    description
          "overall rate for BUM";
                      "Ethernet Interface Type";
                  }
      list bum-rate-per-type
                  container dot1q-interface {
        key "type";
                    leaf type l2-access-type {
                      type identityref {
                        base bum-type; vpn-common:encapsulation-type;
                      }
                      description
            "BUM type";
                        "L2 Access Encapsulation Type";
                    }
                    container dot1q {
                      when "../l2-access-type='vpn-common:dot1q'";
                      if-feature "vpn-common:dot1q";
                      leaf rate physical-inf {
                        type uint32;
          description
            "rate for BUM";
        } string;
                        description
          "List of rate per type";
                          "Physical Interface";
                      }
                      leaf c-vlan-id {
                        type uint32;
                        description
        "Container of broadcast, unknown unicast, and multicast
         configurations";
                          "VLAN identifier";
                      }
                      description
      "Grouping for broadcast, unknown unicast, and multicast ";
                        "Qot1q";
                    }

  grouping mac-loop-prevention-grouping {
                    container mac-loop-prevention qinq {
                      when "../l2-access-type='vpn-common:qinq'";
                      if-feature "vpn-common:qinq";
                      leaf frequency s-vlan-id {
                        type uint32;
                        description
          "Frequency";
                          "S-VLAN Identifier";
                      }
                      leaf protection-type c-vlan-id {
                        type identityref {
          base loop-prevention-type; uint32;
                        description
                          "C-VLAN Identifier";
                      }
                      description
          "Protection type";
                        "QinQ";
                    }
                    container qinany {
                      if-feature "vpn-common:qinany";
                      leaf number-retries s-vlan-id {
                        type uint32;
                        description
          "Number of retries";
                          "S-Vlan ID";
                      }
                      description
                        "Container of MAC loop prevention.";
    }
    description
      "Grouping for MAC loop prevention"; Q in Any";
                    }

  grouping ethernet-svc-oam-grouping {
                    container ethernet-service-oam vxlan {
                      when "../l2-access-type='vpn-common:vxlan'";
                      if-feature "vxlan";
                      leaf md-name vni-id {
                        type string; uint32;
                        description
          "Maintenance domain name";
                          "VNI Identifier";
                      }
                      leaf md-level peer-mode {
                        type uint8; identityref {
                          base vpn-common:vxlan-peer-mode;
                        }
                        description
          "Maintenance domain level";
                          "specify the vxlan access mode";
                      }
      container cfm-802.1-ag {
                      list n2-uni-c peer-list {
                        key "maid";
          uses cfm-802-grouping; "peer-ip";
                        leaf peer-ip {
                          type inet:ip-address;
                          description
            "List of UNI-N to UNI-C";
                            "Peer IP";
                        }
        list n2-uni-n {
          key "maid";
          uses cfm-802-grouping;
                        description
                          "List of UNI-N to UNI-N"; for peer IP";
                      }
                      description
          "Container of 802.1ag CFM configurations.";
                        "QinQ";
                    }
      uses y-1731;
                    description
                      "Container for Ethernet service OAM.";
    }
    description
      "Grouping for Ethernet service OAM."; dot1Q Interface";
                  }

  grouping fate-sharing-group {
                  container groups phy-interface {
                    leaf fate-sharing-group-size port-number {
                      type uint16; uint32;
                      description
          "Fate sharing group size.";
                        "Port number";
                    }
                    leaf group-color port-speed {
                      type string; uint32;
                      description
          "Group color associated with a particular VPN.";
                        "Port speed";
                    }
      list group {
        key "group-id";
                    leaf group-id mode {
                      type string;
          description
            "Group-id the site network access
             is belonging to";
        }
        description
          "List of group-id";
      } vpn-common:neg-mode;
                      description
        "Groups the fate sharing group member
         is belonging to";
                        "Negotiation mode";
                    }
                    leaf phy-mtu {
                      type uint32;
                      description
      "Grouping for Fate sharing group.";
                        "PHY MTU";
                    }

  grouping site-group
                    leaf flow-control {
                      type string;
                      description
                        "Flow control";
                    }
                    container groups {
      list group oam-802.3ah-link {
        key "group-id";
                      if-feature "oam-3ah";
                      leaf group-id enable {
                        type string; boolean;
                        description
            "Group-id the site is belonging to";
                          "Indicate whether support oam 802.3 ah link";
                      }
                      description
          "List of group-id";
                        "Container for oam 802.3 ah link.";
                    }
                    leaf uni-loop-prevention {
                      type boolean;
                      description
        "Groups
                        "If this leaf set to truth that the site or vpn-network-access port automatically
                         goes down when a physical loopback is belonging to."; detect.";
                    }
                    description
      "Grouping definition to assign
       group-ids to site or vpn-network-access";
                      "Container of PHY Interface Attributes configurations";
                  }

  grouping access-diversity {
                  container access-diversity lag-interface {
                    if-feature "site-diversity";
      uses fate-sharing-group;
      container constraints { "vpn-common:lag-interface";
                    list constraint lag-interface {
                      key "constraint-type"; "lag-interface-number";
                      leaf constraint-type lag-interface-number {
                        type identityref {
              base placement-diversity;
            } uint32;
                        description
              "Diversity constraint type.";
                          "LAG interface number";
                      }
                      container target {
            choice target-flavor {
              case id {
                list group lacp {
                  key "group-id";
                        leaf group-id lacp-state {
                          type string;
                    description
                      "The constraint will apply
                       against this particular
                       group-id";
                  } boolean;
                          description
                    "List of groups";
                }
                            "LACP on/off";
                        }
              case all-accesses {
                        leaf all-other-accesses lacp-mode {
                          type empty; boolean;
                          description
                    "The constraint will apply
                     against all other site network
                     access of this site";
                }
                            "LACP mode";
                        }
              case all-groups {
                        leaf all-other-groups lacp-speed {
                          type empty;
                  description
                    "The constraint will apply
                     against all other groups the
                     customer is managing";
                }
              } boolean;
                          description
                "Choice for the group definition";
                            "LACP speed";
                        }
                        leaf mini-link {
                          type uint32;
                          description
                            "The constraint will apply against
               this list of groups";
          }
          description
            "List of constraints";
        }
        description
          "Constraints minimum aggregate bandwidth for placing this site
            network access";
      }
      description
        "Diversity parameters."; a LAG";
                        }
                        leaf system-priority {
                          type uint16;
                          description
      "This grouping defines access diversity
       parameters";
                            "Indicates the LACP priority for the system.
                             The range is from 0 to 65535.
                             The default is 32768.";
                        }

  grouping request-type-profile-grouping {
                        container request-type-profile {
      choice request-type-choice {
        case dot1q-case member-link-list {
          container dot1q
                          list member-link {
                            key "name";
                            leaf physical-if name {
                              type string;
                              description
                "Physical interface";
                                "Member link name";
                            }
                            leaf vlan-id port-speed {
                              type uint16;
              description
                "VLAN ID";
            }
            description
              "Container for dot1q.";
          } uint32;
                              description
            "Case for dot1q";
                                "Port speed";
                            }
        case physical-case {
                            leaf physical-if mode {
                              type string; vpn-common:neg-mode;
                              description
              "Physical interface";
                                "Negotiation mode";
                            }
                            leaf circuit-id link-mtu {
                              type string; uint32;
                              description
              "Circuit ID";
                                "Link MTU size.";
                            }
                            container oam-802.3ah-link {
                              if-feature "oam-3ah";
                              leaf enable {
                                type boolean;
                                description
            "Physical case";
                                  "Indicate whether support oam 802.3 ah link";
                              }
                              description
          "Choice
                                "Container for request type"; oam 802.3 ah link.";
                            }
                            description
        "Container for request type profile.";
                              "Member link";
                          }
                          description
      "Grouping for request type profile";
                            "Container of Member link list";
                        }

  grouping site-attachment-bearer {
    container bearer {
      container requested-type {
        if-feature "requested-type";
                        leaf requested-type flow-control {
                          type string;
                          description
            "Type of requested bearer Ethernet, ATM, Frame
             Relay, IP Layer 2 Transport, Frame Relay DLCI,
             SONET/SDH,PPP.";
                            "Flow control";
                        }
                        leaf strict lldp {
                          type boolean;
          default "false";
                          description
            "Define if the requested-type is a preference
             or a strict requirement.";
                            "LLDP";
                        }
                        description
                          "LACP";
                      }
                      description
                        "List of LAG interfaces";
                    }
                    description
                      "Container for requested type."; of LAG interface attributes configuration";
                  }
                  list cvlan-id-to-svc-map {
                    key "svc-id";
                    leaf always-on svc-id {
        if-feature "always-on";
                      type boolean;
        default "true"; leafref {
                        path "/l2vpn-ntw/vpn-services/vpn-service/vpn-id";
                      }
                      description
          "Request for an always on access type.
           This means no Dial access type for
           example.";
                        "VPN Service identifier";
                    }
                    list cvlan-id {
                      key "vid";
                      leaf bearer-reference vid {
        if-feature "bearer-reference";
                        type string; uint32;
                        description
          "This is an internal reference for the
           service provider.";
                          "CVLAN ID";
                      }
                      description
        "Bearer specific parameters.
         To be augmented.";
                        "List of CVLAN-ID to SVC Map configurations";
                    }
                    description
      "Grouping
                      "List for cvlan-id to define physical properties of
       a site attachment."; L2VPn Service map configurations";

                  }

  grouping vpn-attachment-grouping {
                  container vpn-attachment split-horizon {
                    leaf device-id group-name {
                      type string;
                      description
          "Device ID";
                        "group-name of the Split Horizon";
                    }
      container management {
        leaf address-family {
          type identityref {
            base address-family;
                    description
                      "Configuration with split horizon enabled";
                  }
                  description
            "Address family used
                    "Container for management."; bearer";
                }
                container availability {
                  leaf address access-priority {
                    type inet:ip-address;
          description
            "Management address";
        } uint32;
                    description
          "Management configuration..";
                      "Access priority";
                  }
                  choice attachment-flavor redundancy-mode {
                    case vpn-flavor {
          list vpn-flavor {
            key "vpn-id";
            leaf vpn-id {
              type leafref single-active {
                path "/l2vpn-ntw/vpn-services"
                   + "/vpn-service/vpn-id";
              }
              description
                "Reference to a VPN.";
            }
                      leaf site-role single-active {
                        type identityref {
                base site-role;
              }
              default "any-to-any-role"; boolean;
                        description
                "Role of the site in the IPVPN.";
                          "Single active";
                      }
                      description
              "List of IPVPNs attached by the Site Network Access";
          }
                        "Single active case";
                    }
                    case vpn-policy-id all-active {
                      leaf vpn-policy-id all-active {
                        type leafref {
              path "/l2vpn-ntw/sites/site/vpn-policies/vpn-policy/"+
              "vpn-policy-id";
            } boolean;
                        description
              "Reference to a vpn policy";
          }
                          "All active";
                      }
        mandatory true;
                      description
          "Choice for VPN attachment flavor.";
                        "All active case";
                    }
                    description
        "Defines VPN attachment of a site.";
                      "Redundancy mode choice";
                  }
                  description
      "Grouping for access attachment";
                    "Container of availability optional configurations";
                }

  grouping site-service-basic
                container service {
                  container svc-input-bandwidth {
                    if-feature "input-bw"; "vpn-common:input-bw";
                    list input-bandwidth {
                      key "type";
                      leaf type {
                        type identityref {
                          base bw-type; vpn-common:bw-type;
                        }
                        description
                          "Bandwidth Type";
                      }
                      leaf cos-id {
                        type uint8;
                        description
                          "Identifier of Class of Service
                           , indicated by DSCP or a CE-CLAN
                           CoS(802.1p)value in the service frame.";
                      }
                      leaf vpn-id {
          type svc-id;
          description
            "Identifies the target VPN.";

        }
        leaf cir {
                        type uint64;
                        description
                          "Committed Information Rate. The maximum number of
                           bits that a port can receive or send during
                           one-second over an interface.";
                      }
                      leaf cbs {
                        type uint64;
                        description
                          "Committed Burst Size.CBS controls the bursty nature
                           of the traffic. Traffic that does not use the
                           configured CIR accumulates credits until the credits
                           reach the configured CBS.";
                      }
                      leaf eir {
                        type uint64;
                        description
                          "Excess Information Rate,i.e.,Excess frame delivery
                           allowed not subject to SLA.The traffic rate can be
                           limited by eir.";
                      }
                      leaf ebs {
                        type uint64;
                        description
                          "Excess Burst Size. The bandwidth available for burst
                           traffic from the EBS is subject to the amount of
                           bandwidth that is accumulated during periods when
                           traffic allocated by the EIR policy is not used.";
                      }
                      leaf pir {
                        type uint64;
                        description
                          "Peak Information Rate, i.e., maixmum frame delivery
                           allowed. It is equal to or less than sum of cir and
                           eir.";
                      }
                      leaf pbs {
                        type uint64;
                        description
                          "Peak Burst Size. It is measured in bytes per second.";
                      }
                      description
                        "List for input bandwidth";
                    }
                    description
                      "From the PE perspective, the service input
                       bandwidth of the connection.";
                  }
                  container svc-output-bandwidth {
                    if-feature "output-bw";
                    list output-bandwidth {
                      key "type";
                      leaf type {
                        type identityref {
                          base bw-type; vpn-common:bw-type;
                        }
                        description
                          "Bandwidth Type";
                      }
                      leaf cos-id {
                        type uint8;
                        description
                          "Identifier of Class of Service
                           , indicated by DSCP or a CE-CLAN
                           CoS(802.1p)value in the service frame.";
                      }
                      leaf vpn-id {
          type svc-id;
          description
            "Identifies the target VPN.";
        }
        leaf cir {
                        type uint64;
                        description
                          "Committed Information Rate. The maximum number of
                           bits that a port can receive or send during
                           one-second over an interface.";
                      }
                      leaf cbs {
                        type uint64;
                        description
                          "Committed Burst Size.CBS controls the bursty nature
                           of the traffic. Traffic that does not use the
                           configured CIR accumulates credits until the credits
                           reach the configured CBS.";

                      }
                      leaf eir {
                        type uint64;
                        description
                          "Excess Information Rate,i.e.,Excess frame delivery
                           allowed not subject to SLA.The traffic rate can be
                           limited by eir.";
                      }
                      leaf ebs {
                        type uint64;
                        description
                          "Excess Burst Size. The bandwidth available for burst
                           traffic from the EBS is subject to the amount of
                           bandwidth that is accumulated during periods when
                           traffic allocated by the EIR policy is not used.";
                      }
                      leaf pir {
          type uint64;
          description
            "Peak Information Rate, i.e., maixmum frame delivery
             allowed. It is equal to or less than sum of cir and
             eir.";
        }
        leaf pbs {
          type uint64;
          description
            "Peak Burst Size. It is measured in bytes per second.";
        }
        description
          "List for output bandwidth";
      }
      description
        "From the PE perspective, the service output
         bandwidth of the connection.";
    }
    description
      "Grouping for site service";
  }

  grouping flow-definition {
    container match-flow {
      leaf dscp {
        type inet:dscp;
        description
          "DSCP value.";
      }
      leaf dot1q {
        type uint32;
        description
          "802.1q matching. It is VLAN Tag added into frame.";
      }
      leaf pcp {
        type uint8 {
          range "0 .. 7";
        }
        description
          "PCP value";

      }

      uses pf:acl-eth-header-fields;
      leaf color-type {
        type identityref {
          base color-type;
        }
        description
          "Color Types";
      }
      leaf-list target-sites {
        type svc-id;
        description
          "Identify a site as traffic destination.";
      }
      leaf any {
        type empty;
        description
          "Allow all.";
      }
      leaf vpn-id pir {
                        type svc-id; uint64;
                        description
          "Reference
                          "Peak Information Rate, i.e., maixmum frame delivery
                           allowed. It is equal to the target VPN.";
      }
      description
        "Describe flow matching criteria.";
    }
    description
      "Flow definition based on criteria."; or less than sum of cir and
                           eir.";
                      }

  grouping services-grouping {
    container service
                      leaf pbs {
      uses site-service-qos-profile;
      description
        "Container for service";
    }
                        type uint64;
                        description
      "Grouping for Services";
                          "Peak Burst Size. It is measured in bytes per second.";
                      }

  grouping service-grouping {
    container service {
      uses site-service-basic;
      uses site-service-qos-profile;
      uses svc-precedence;
                      description
        "Container
                        "List for service"; output bandwidth";
                    }
                    description
      "Grouping for service.";
                      "From the PE perspective, the service output
                       bandwidth of the connection.";
                  }

  grouping site-service-qos-profile {
                  container qos {
                    if-feature "qos"; "vpn-common:qos";
                    container classification-policy qos-classification-policy {
        list rule {
          key "id";
          ordered-by user;
          leaf id {
            type string;
            description
              "A
                      uses vpn-common:qos-classification-policy;
                      description identifying qos
                        "Configuration of the traffic classification
               policy rule.";
                         policy.";
                    }
          choice match-type {
            default "match-flow";
            case match-flow {
                    container match-flow {
                leaf dscp qos-profile {
                  type inet:dscp;
                  description
                    "DSCP value.";
                }
                leaf dot1q
                      list qos-profile {
                  type uint16;
                        key "profile";
                        description
                    "802.1q matching. It is VLAN Tag added into
                     frame.";
                }
                          "QoS profile.

                           Can be standard profile or customized
                           profile.";
                        leaf pcp profile {
                          type uint8 leafref {
                    range "0 .. 7";
                            path "/l2vpn-ntw/vpn-profiles"
                               + "/valid-provider-identifiers"
                               + "/qos-profile-identifier/id";
                          }
                          description
                    "PCP value.";
                            "QoS profile to be used.";
                        }
                uses pf:acl-eth-header-fields;
                        leaf color-type direction {
                          type identityref {
                            base color-type;
                  }
                  description
                    "Color Types.";

                }
                leaf-list target-sites {
                  if-feature "target-sites";
                  type svc-id;
                  description
                    "Identify a site as traffic destination.";
                }
                leaf any {
                  type empty;
                  description
                    "Allow all."; vpn-common:qos-profile-direction;
                          }
                leaf vpn-id {
                  type svc-id;
                          default "vpn-common:both";
                          description
                    "Reference
                            "The direction to which the target VPN."; QoS profile
                             is applied.";
                        }
                      }
                      description
                  "Describe flow matching criteria.";
                        "QoS profile configuration.";
                    }
                    description
                      "QoS configuration.";
                  }
            case match-application
                  container precedence {
                    leaf match-application precedence {
                      type identityref {
                        base customer-application;
                }
                description
                  "Defines the application to match.";
              }
            }
            description
              "Choice for classification"; precedence-type;
                      }
          leaf target-class-id {
            type string;
                      description
              "Identification of the class of service.
               This identifier is internal to the
               administration.";
                        "Defining service redundancy in transport
                         network.";
                    }
                    description
            "List of marking rules.";
                      "Transport netowrk precedence selector
                       Primary or Secondary tunnel.";
                  }
                  description
          "Configuration of the traffic classification policy.";
                    "Container for service";
                }
                container qos-profile broadcast-unknown-unicast-multicast {
                  leaf profile multicast-site-type {
                    type leafref enumeration {
                      enum receiver-only {
            path "/l2vpn-ntw/vpn-profiles/"
               + "valid-provider-identifiers"
               + "/qos-profile-identifier";
          }
                        description
            "QoS profile configuration.";
                          "The site only has receivers.";
                      }
                      enum source-only {
                        description
          "QoS profile configuration.";
                          "The site only has sources.";
                      }
                      enum source-receiver {
                        description
        "QoS configuration.";
                          "The site has both sources and receivers.";
                      }
                    }
                    default "source-receiver";
                    description
      "This grouping defines QoS parameters
       for a site";
                      "Type of multicast site.";
                  }

  /* MAIN L2VPN SERVICE */

  container l2vpn-ntw {
    container vpn-profiles {
      container valid-provider-identifiers
                  list multicast-gp-address-mapping {
        leaf-list cloud-identifier
                    key "id";
                    leaf id {
          if-feature "cloud-access";
                      type string; uint16;
                      description
            "Identification of public cloud service
             or internet service. Local administration
             meaning.";
                        "Unique identifier for the mapping.";
                    }
        leaf-list qos-profile-identifier
                    leaf vlan-id {
                      type string; uint32;
                      description
            "Identification
                        "The VLAN ID of the QoS Profile to be used.
             Local administration meaning."; Multicast group.";
                    }
        leaf-list bfd-profile-identifier
                    leaf mac-gp-address {
                      type string; yang:mac-address;
                      description
            "Identification
                        "The MAC address of the SP BFD Profile to be used.
             Local administration meaning."; Multicast group.";
                    }
        leaf-list remote-carrier-identifier
                    leaf port-lag-number {
                      type string; uint32;
                      description
            "Identification of
                        "The ports/LAGs belonging to the remote carrier name Multicast group.";
                    }
                    description
                      "List of Port to be used.

             It can be L2VPN partner, Data center service provider
             or private cloud service provider. Local administration
             meaning."; group mappings.";
                  }
        nacm:default-deny-write;
                  leaf bum-overall-rate {
                    type uint32;
                    description
          "Container
                      "overall rate for Valid Provider Identifies."; BUM";
                  }
                  description
                    "Container for VPN Profiles."; of broadcast, unknown unicast, and multicast
                     configurations";

                }
                container vpn-services {
      list vpn-service ethernet-service-oam {
        key "vpn-id";
                  leaf vpn-id md-name {
                    type svc-id; string;
                    description
            "Refers to unique identifier for the L2NM.";
                      "Maintenance domain name";
                  }
                  leaf l2sm-vpn-id md-level {
                    type svc-id; uint8;
                    description
            "Pointer to the L2SM service.";
                      "Maintenance domain level";
                  }
        leaf vpn-svc-type
                  container cfm-802.1-ag {
          type identityref
                    list n2-uni-c {
            base service-type;
          }
                      key "maid";
                      uses cfm-802-grouping;
                      description
            "Service type";
                        "List of UNI-N to UNI-C";
                    }
        leaf customer-name
                    list n2-uni-n {
          type string;
                      key "maid";
                      uses cfm-802-grouping;
                      description
            "Customer name";
                        "List of UNI-N to UNI-N";
                    }
        leaf svc-topo {
          type identityref {
            base vpn-topology;
                    description
                      "Container of 802.1ag CFM configurations.";
                  }
                  uses y-1731;
                  description
            "Defining
                    "Container for Ethernet service topology, such as
             any-to-any,hub-spoke, etc."; OAM.";
                }
        uses l3vpn-ntw:service-status;
        uses site-service;
        uses vpn-service-multicast;
        uses vpn-extranet;
        uses svc-mtu-grouping;
        uses svc-preservation-grouping;
        uses l3vpn-ntw:svc-transport-encapsulation;
                container vpn-nodes {
          list vpn-node {
            key "vpn-node-id ne-id";
            leaf vpn-node-id mac-loop-prevention {
              type string;
              description
                "";
            }
                  leaf description frequency {
                    type string;
              description
                "Textual uint32;
                    description of a VPN node.";
                      "Frequency";
                  }
                  leaf node-role protection-type {
                    type identityref {
                      base site-role; loop-prevention-type;
                    }
              default "any-to-any-role";
                    description
                "Role of the vpn-node in the IP VPN.";
                      "Protection type";
                  }
                  leaf ne-id number-retries {
                    type string; uint32;
                    description
                "NE IP address";
                      "Number of retries";
                  }
            leaf port-id {
              type string;
                  description
                "NE Port-id";
                    "Container of MAC loop prevention.";
                }
            uses signaling-options-grouping;
                container vpn-network-accesses access-control-list {
                  list vpn-network-access mac {
                    key "network-access-id"; "mac-address";
                    leaf network-access-id mac-address {
                      type string; yang:mac-address;
                      description
                    "Identifier of network access";
                        "MAC address.";
                    }
                    description
                      "List for MAC.";
                  }
                leaf
                  description
                    "Container for access control List.";
                }
                container mac-addr-limit {
                  leaf mac-num-limit {
                    type string; uint16;
                    description
                    "String to describe
                      "maximum number of MAC addresses learned from
                       the element."; subscriber for a single service instance.";
                  }
                  leaf remote-carrier-name {
                  when "'../site-type' = 'enni'" time-interval {
                    description
                      "Site type = enni";
                  }
                    type string; uint32;
                    units "milliseconds";
                    description
                    "Remote carrier name";
                      "The aging time of the mac address.";
                  }
                  leaf Interface-mtu action {
                    type uint32; identityref {
                      base mac-action;
                    }
                    description
                    "Interface MTU, it is also known as
                      "specify the maximum
                     transmission unit or maximum frame size. When a
                     frame is larger than action when the MTU, it upper limit is broken down,
                     or fragmented, into smaller pieces by
                       exceeded: drop the
                     network protocol to accommodate packet, flood the MTU
                       packet, or simply send a warning log message.";
                  }
                  description
                    "Container of the
                     network"; MAC-Addr limit configurations";
                }
                uses l3vpn-ntw:service-status;
                uses access-diversity;
                uses ethernet-connection-grouping;
                uses availability-grouping;
                uses service-grouping;
                uses B-U-M-grouping;
                uses ethernet-svc-oam-grouping;
                uses mac-loop-prevention-grouping;
                uses acl-grouping;
                uses mac-addr-limit-grouping;
                description
                  "List of VPN Network Accesses.";
              }
              description
                "List of VPN Nodes.";
            }
            description
              "Container of VPN Nodes.";
          }
          description
            "List of vpn-svc";
        }
        description
          "Container of port configurations";
      }
      description
        "Container for L2VPN service";
    }
    description
      "Container for VPN services.";
  }
}

<CODE ENDS>

                                 Figure 6 11

6.  Acknowledgements

   The authors would like to thank Tom Petch for the comments to improve
   the document.

7.  Contributors

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

   Victor Lopez
   Telefonica
   Email: victor.lopezalvarez@telefonica.com

   Zhang Guiyu
   China Unicom
   Email: zhanggy113@chinaunicom.cn

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

8.  IANA Considerations

   This document requests IANA to register the following URI in the "ns"
   subregistry within the "IETF XML Registry" [RFC3688]:

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

      Registrant Contact: The IESG.

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

   This document requests IANA to register the following YANG module in
   the "YANG Module Names" subregistry [RFC6020] within the "YANG
   Parameters" registry.

      name: ietf-l2vpn-ntw

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

      maintained by IANA: N

      prefix: l2vpn-ntw

      reference: RFC XXXX

9.  Security Considerations

   The YANG module specified in this document defines a schema for data
   that is designed to be accessed via network management protocols such
   as NETCONF [RFC6241] or RESTCONF [RFC8040] .  The lowest NETCONF
   layer is the secure transport layer, and the mandatory-to-implement
   secure transport is Secure Shell (SSH) [RFC6242].  The lowest
   RESTCONF layer is HTTPS, and the mandatory-to-implement secure
   transport is TLS [RFC8466].

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

   The ietf-l2vpn-ntw module is used to manage L2 VPNs in a service
   provider backbone network.  Hence, the module can be used to request,
   modify, or retrieve L2VPN services.  There are a number of data nodes
   defined in this YANG module that are writable/creatable/deletable
   (i.e., config true, which is the 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 authentication can have a
   negative effect on network operations.  These are the subtrees and
   data nodes and their sensitivity/vulnerability in the ietf-l2vpn-ntw
   module:

   o  vpn-service: An attacker who is able to access network nodes can
      undertake various attacks, such as deleting a running L2 VPN
      Service, interrupting all the traffic of a client.

   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 subtrees and data
   nodes and their sensitivity/vulnerability:

   o  customer-name: An attacker can retrieve privacy-related
      information which can be used to track a customer.  Disclosing
      such information may be considered as a violation of the customer-
      provider trust relationship.

10.  References

10.1.  Normative References

   [I-D.ietf-opsawg-vpn-common]
              barguil, s., Dios, O., Boucadair, M., and Q. WU, "A Layer
              2/3 VPN Common YANG Model", draft-ietf-opsawg-vpn-
              common-02 (work in progress), October 2020.

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

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

   [RFC7432]  Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
              Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
              Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
              2015, <https://www.rfc-editor.org/info/rfc7432>.

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

   [RFC8214]  Boutros, S., Sajassi, A., Salam, S., Drake, J., and J.
              Rabadan, "Virtual Private Wire Service Support in Ethernet
              VPN", RFC 8214, DOI 10.17487/RFC8214, August 2017,
              <https://www.rfc-editor.org/info/rfc8214>.

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

   [RFC8342]  Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
              and R. Wilton, "Network Management Datastore Architecture
              (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
              <https://www.rfc-editor.org/info/rfc8342>.

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

10.2.  Informative References

   [RFC3644]  Snir, Y., Ramberg, Y., Strassner, J., Cohen, R., and B.
              Moore, "Policy Quality of Service (QoS) Information
              Model", RFC 3644, DOI 10.17487/RFC3644, November 2003,
              <https://www.rfc-editor.org/info/rfc3644>.

   [RFC5880]  Katz, D. and D. Ward, "Bidirectional Forwarding Detection
              (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
              <https://www.rfc-editor.org/info/rfc5880>.

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

Authors' Addresses

   Samier Barguil (editor)
   Telefonica
   Madrid
   ES

   Email: samier.barguilgiraldo.ext@telefonica.com

   Oscar Gonzalez de Dios (editor)
   Telefonica
   Madrid
   ES

   Email: oscar.gonzalezdedios@telefonica.com

   Mohamed Boucadair
   Orange
   France

   Email: "mohamed.boucadair@orange.com

   Luis Angel Munoz
   Vodafone
   ES

   Email: luis-angel.munoz@vodafone.com
   Luay Jalil
   Verizon
   USA

   Email: luay.jalil@verizon.com

   Jichun Ma
   China Unicom
   China

   Email: majc16@chinaunicom.cn