A YANG Data Model for L2VPN Service Delivery
draft-wen-l2sm-l2vpn-service-model-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Bin Wen  , Giuseppe Fioccola  , Chongfeng Xie  , Luay Jalil 
Last updated 2016-09-02
Replaced by RFC 8466, RFC 8466
Stream (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
L2SM Working Group                                                B. Wen
Internet-Draft                                                   Comcast
Intended status: Standards Track                             G. Fioccola
Expires: March 5, 2017                                    Telecom Italia
                                                                  C. Xie
                                                           China Telecom
                                                                L. Jalil
                                                                 Verizon
                                                       September 1, 2016

              A YANG Data Model for L2VPN Service Delivery
                 draft-wen-l2sm-l2vpn-service-model-00

Abstract

   This document defines a YANG data model that can be used to deliver a
   Layer 2 Provider Provisioned VPN service.

   This model is intended to be instantiated at management system to
   deliver the overall service.  This model is not a configuration model
   to be used directly on network elements, but provides an abstracted
   view of the Layer 2 VPN service configuration components.  It is up
   to a management system to take this as an input and use specific
   configurations models to configure the different network elements to
   deliver the service.  How configuration of network elements is done
   is out of scope of the document.

   The data model in this document includes support for point-to-point
   Virtual Private Wire Services (VPWS) and multipoint Virtual Private
   LAN services (VPLS) that use Pseudowires sgnaled using the Label
   Distrbution Protocol (LDP) and the Border Gateway Protocol (BGP) as
   described in RFC4761 and RFC6624.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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

Wen, et al.               Expires March 5, 2017                 [Page 1]
Internet-Draft             L2VPN Sevice Model             September 2016

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://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 March 5, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Tree diagram  . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  The Layer 2 VPN Service Model . . . . . . . . . . . . . . . .   5
     3.1.  Applicability of the Layer 2 VPN Service Model  . . . . .   5
     3.2.  Layer 2 VPN Service Types . . . . . . . . . . . . . . . .   6
     3.3.  Layer 2 VPN Service Network Topology  . . . . . . . . . .   7
     3.4.  Layer 2 VPN Ethernet Virtual Circuit Construct  . . . . .   8
   4.  Service Data Model Usage  . . . . . . . . . . . . . . . . . .  11
   5.  Design of the Data Model  . . . . . . . . . . . . . . . . . .  12
     5.1.  Overview of Main Components of the Model  . . . . . . . .  22
       5.1.1.  Customer Information  . . . . . . . . . . . . . . . .  22
       5.1.2.  VPN Service Overview  . . . . . . . . . . . . . . . .  23
         5.1.2.1.  Service Type  . . . . . . . . . . . . . . . . . .  23
         5.1.2.2.  ethernet-svc-type . . . . . . . . . . . . . . . .  24
         5.1.2.3.  Metro Network Partition . . . . . . . . . . . . .  24
         5.1.2.4.  vpn-signaling-option  . . . . . . . . . . . . . .  24
         5.1.2.5.  Load Balance Option . . . . . . . . . . . . . . .  27
         5.1.2.6.  SVLAN ID Ethernet Tag . . . . . . . . . . . . . .  28
         5.1.2.7.  CVLAN ID To EVC MAP . . . . . . . . . . . . . . .  28

Wen, et al.               Expires March 5, 2017                 [Page 2]
Internet-Draft             L2VPN Sevice Model             September 2016

         5.1.2.8.  Service Level MAC Limit . . . . . . . . . . . . .  29
         5.1.2.9.  Service Protection  . . . . . . . . . . . . . . .  29
       5.1.3.  site  . . . . . . . . . . . . . . . . . . . . . . . .  29
         5.1.3.1.  uni-site  . . . . . . . . . . . . . . . . . . . .  30
         5.1.3.2.  enni-site . . . . . . . . . . . . . . . . . . . .  30
   6.  Service Model Usage Example . . . . . . . . . . . . . . . . .  31
   7.  Interaction with Other YANG Modules . . . . . . . . . . . . .  31
   8.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .  32
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  69
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  70
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  70
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  70
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  70
     12.2.  Informative References . . . . . . . . . . . . . . . . .  71
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  72

1.  Introduction

   This document defines a YANG data model for Layer 2 VPN service
   configuration.

1.1.  Terminology

   The following terms are defined in [RFC6241] and are not redefined
   here:

   o  client

   o  configuration data

   o  server

   o  state data

   The following terms are defined in [RFC6020] and are not redefined
   here:

   o  augment

   o  data model

   o  data node

   The terminology for describing YANG data models is found in
   [RFC6020].

Wen, et al.               Expires March 5, 2017                 [Page 3]
Internet-Draft             L2VPN Sevice Model             September 2016

1.2.  Tree diagram

   A simplified graphical representation of the data model is presented
   in Section 5.

   The meaning of the symbols in these diagrams is as follows:

   o  Brackets "[" and "]" enclose list keys.

   o  Curly braces "{" and "}" contain names of optional features that
      make the corresponding node conditional.

   o  Abbreviations before data node names: "rw" means configuration
      (read-write), and "ro" state data (read-only).

   o  Symbols after data node names: "?" means an optional node and "*"
      denotes a "list" or "leaf-list".

   o  Parentheses enclose choice and case nodes, and case nodes are also
      marked with a colon (":").

   o  Ellipsis ("...") stands for contents of subtrees that are not
      shown.

2.  Definitions

   This document uses the following terms:

   Service Provder (SP):  The organization (usually a commercial
      undertaking) responsible for operating the network that offers VPN
      services to clients and customers.

   Customer Edge (CE) Device:  Equipment that is dedicated to a
      particular customer and is directly connected to one or more PE
      devices via attachment circuits.  A CE is usually located at the
      customer premises, and is usually dedicated to a single VPN,
      although it may support multiple VPNs if each one has separate
      attachment circuits.  The CE devices can be routers, bridges,
      switches, or hosts.

   Provider Edge (PE) Device:  Equipment managed by the SP that can
      support multiple VPNs for different customers, and is directly
      connected to one or more CE devices via attachment circuits.  A PE
      is usually located at an SP point of presence (PoP) and is managed
      by the SP.

   Virtual Private LAN Service (VPLS):  A VPLS is a provider service
      that emulates the full functionality of a traditional Local Area

Wen, et al.               Expires March 5, 2017                 [Page 4]
Internet-Draft             L2VPN Sevice Model             September 2016

      Network (LAN).  A VPLS makes it possible to interconnect several
      LAN segments over a packet switched network (PSN) and makes the
      remote LAN segments behave as one single LAN.

   Virtual Private Wire Service (VPWS):  A VPWS is a point-to-point
      circuit (i.e., link) connecting two CE devices.  The link is
      established as a logical through a packet switched network.  The
      CE in the customer network is connected to a PE in the provider
      network via an Attachment Circuit (AC); the AC is either a
      physical or a logical circuit.  A VPWS differs from a VPLS in that
      the VPLS is point-to-multipoint, while the VPWS is point-to-point.
      In some implementations, a set of VPWSs is used to create a multi-
      site L2VPN network.

3.  The Layer 2 VPN Service Model

   A Layer 2 VPN service is a collection of sites that are authorized to
   exchange traffic between each other over a shared infrastructure of a
   common technology.  This Layer 2 VPN service model (L2SM) provides a
   common understanding of how the corresponding Layer 2 VPN service is
   to be deployed over the shared infrastructure.

   This document presents the L2SM using the YANG data modeling language
   [RFC6020] as a formal language that is both human-readable and
   parsable by software for use with protocols such as NETCONF [RFC6241]
   and RESTCONF [I-D.ietf-netconf-restconf].

   This service model is limited to VPWS and VPLS based VPNs as
   described in [RFC4761] and [RFC6624].

3.1.  Applicability of the Layer 2 VPN Service Model

   The L2SM defined in this document applies to both point-to-point
   (E-Line) and multipoint-to-multipoint (E-LAN) carrier Ethernet
   services.

   Over the past decade, Metro Ethernet Forum (MEF) has published a
   series of technical specifications of Ethernet virtual circuit
   service attributes and implementation agreements between providers.
   Many Ethernet VPN service providers worldwide have adopted these MEF
   standards and developed backoffice tools accordingly.

   Rather than introducing a new set of terminologies, the L2SM will
   align with existing MEF attributes when it's applicable.  Therefore,
   service providers can easily integrate any new application that
   leverages the L2SM data, Service Orchestrator for example, with
   existing BSS/OSS toolsets.  Service providers also have the option to

Wen, et al.               Expires March 5, 2017                 [Page 5]
Internet-Draft             L2VPN Sevice Model             September 2016

   generate L2SM data for current L2VPN customer circuits already
   deployed in the network.

3.2.  Layer 2 VPN Service Types

   A Layer 2 VPN circuit can be port-based; in which case any service
   frames received from subscriber within contractual bandwidth will be
   delivered to the corresponding remote site, regardless of customer
   Vlan value (C-tag) of the incoming frame.  The service frames can
   also be native Ethernet frames without C-tag.  In this scenario, only
   one Ethernet Virtual Circuit (EVC) is allowed on a single provider to
   subscriber link.

   Contrary to the above use case, incoming customer service frames may
   be split into multiple EVCs based on pre-arrangement between the
   service provider and customer.  Typically, C-tag of the incoming
   frames will serve as the service delimiter for EVC multiplexing over
   the same provider to subscriber interconnection.

   Combining the service-multiplexing attribute with point-to-point
   verses multipoint-to-multipoint connection type, a Layer 2 VPN
   circuit may fall under one of the following service types:

   o  E-Line services: Point-to-Point Layer 2 connections.

      EPL:  In its simplest form, a port-based Ethernet Private Line
         (EPL) service provides a high degree of transparency delivering
         all customer service frames between UNI-to-UNI interfaces using
         All-to-One Bundling.  All unicast/broadcast/multicast packets
         are delivered unconditionally over the EVC.  No service
         multiplexing is allowed on an EPL UNI interface.

      EVPL:  On the other hand, Ethernet Virtual Private Line (EVPL)
         service supports multiplexing more than one Point-to-Point, or
         even other virtual private services, on the same UNI interface.
         Ingress service frames are conditionally transmitted through
         one of the EVCs based upon pre-agreed C-tag to EVC mapping.
         EVPL supports multiple C-tags to one EVC bundling.

   o  E-LAN services: Multipoint-to-Multipoint Layer 2 connections.

      EP-LAN:  Ethernet Private LAN Service (EP-LAN) transparently
         connects multiple subscriber sites together with All-to-One
         Bundling.  No service multiplexing is allowed on an EP-LAN UNI
         interface.

      EVP-LAN:  Some subscriber may desire more sophisticated control of
         data access between multiple sites.  Ethernet Virtual Private

Wen, et al.               Expires March 5, 2017                 [Page 6]
Internet-Draft             L2VPN Sevice Model             September 2016

         LAN Service (EVP-LAN) allows connecting to multiple EVCs from
         one or more of the UNI interfaces.  Services frame disposition
         is based on C-tag to EVC mapping.  EVP-LAN supports multiple
         C-tags to one EVC bundling.

3.3.  Layer 2 VPN Service Network Topology

   Figure 1depicts a typical service provider's physical network
   topology.  Most service providers have deployed an IP, MPLS, or
   Segment Routing (SR) multi-service core infrastructure.  Customer
   Edge (CE) devices are placed at customer premises as demarcation
   points to backhaul in profile service frames from the subscriber over
   the access network to the Provider Edge (PE) equipment.  The actual
   transport technology or physical topology between CE and PE is
   outside the scope of the L2SM model.

    ---     ----                                                ---
   |   |   |    |                                              |   |
   | C +---+ CE |                                              | C |
   |   |   |    |              ---------                       |   |
    ---     ----\             (         )                      /---
                 \  ----     (           )     ----     ----  /
                  \|    |   (             )   |    |   |    |/
                   | PE +---+ IP/MPLS/SR  +---+ PE +---+ CE |
                  /|    |   (  Network    )   |    |   |    |\
                 /  ----     (           )     ----     ----  \
    ---     ----/             (         )                      \---
   |   |   |    |              ----+----                       |   |
   | C +---+ CE |                  |                           | C |
   |   |   |    |                --+--                         |   |
    ---     ----                | PE  |                         ---
                                 --+--
                                   |
                                 --+--
                                | CE  |
                                 --+--
                                   |
                                 --+--
                                |  C  |
                                 -----

    Figure 1: Reference Network for the Use of the L2VPN Service Model

Wen, et al.               Expires March 5, 2017                 [Page 7]
Internet-Draft             L2VPN Sevice Model             September 2016

   From the subscriber perspective, however, all the edge networks
   devices are connected over a simulated LAN environment as shown in
   Figure 2.  Broadcast and multicast packets are sent to all
   participants in the same bridge domain.

                     C---+----+---+---C
                         |    |   |
                         |    |   |
                         |    |   |
                     C---+    C   +---C

                   Figure 2: Customer View of the L2VPN

3.4.  Layer 2 VPN Ethernet Virtual Circuit Construct

   The base model of EVC is shown in Figure 3.

   Subscriber edge network device (C) connects to the service provider's
   CE equipment.  The link between C and CE devices is referred as User
   Network Interface (UNI).  For clarification, this is called UNI-C on
   subscriber side and UNI-N on provider side.

   The service provider is obligated to deliver the original service
   frame across the network to the remote UNI-C.  All Ethernet and IP
   header information, including (but not limit to) source and
   destination MAC addresses, EtherType, Vlan (C-tag), Class-of-Service
   marking (802.1p or DSCP), etc.

   In coming service frames are first examined at UNI-N based on C-tag,
   Class-of-Services identifier, EtherType value.  Conforming packets
   are then metered against the contractual service bandwidth.  In-
   profile packets will be delivered to the remote UNI via the Ethernet
   Virtual Circuit (EVC), which spans between UNI-N to UNI-N.

   When both CEs are located in the same provider's network, a single
   operator maintains the EVC.  In this case, the EVC consists only one
   Operator Virtual Circuit (OVC).

   Typically, the CE device at customer premises is a layer 2 Ethernet
   switch or NID.  Service provider may choose to impose an outer Vlan
   tag (S-tag) into the received subscriber traffic following 802.1ad
   Q-in-Q standard, especially when Layer 2 aggregation devices exist
   between CE and PE.

Wen, et al.               Expires March 5, 2017                 [Page 8]
Internet-Draft             L2VPN Sevice Model             September 2016

   The uplink from CE to PE is referred as Internal Network-to-Network
   Interface (I-NNI).  When 802.1ad Q-in-Q is implemented, Ethernet
   frames from CE to PE are double tagged with both provider and
   subscriber VLANs (S-tag, C-tag).

   Most service providers have deployed MPLS or SR multi-service core
   infrastructure.  Ingress service frames will be mapped to either
   Ethernet Pseudowire (PWE) or VxLAN tunnel PE-to-PE.  The details of
   these tunneling mechanism are at the provider's discretion and not
   part of the L2SM.

   Service provider may also choose Seamless MPLS approach to expand the
   PWE or VxLAN tunnel between UNI-N to UNI-N.

   Service provider may leverage multi-protocol BGP to auto discover and
   signal the PWE or VxLAN tunnel end points.

Wen, et al.               Expires March 5, 2017                 [Page 9]
Internet-Draft             L2VPN Sevice Model             September 2016

                                   EVC
             :<-------------------------------------------->:
             :                                              :
             :                                              :
             :                OVC (Optional)                :
             :<-------------------------------------------->:
             :                                              :
             :                                              :
             :                  PW / VXLAN                  :
             :        :<-------------------------->:        :
             :        :                            :        :
             :        :                            :        :
             :        :          --------          :        :
             :        :         (        )         :        :
     ---     ----     ----     (          )     ----     ----     ---
    |   |   |    |   |    |   (            )   |    |   |    |   |   |
    | C +---+ CE +---+ PE +---+ IP/MPLS/SR +---+ PE +---+ CE +---+ C |
    |   |   |    |   |    |   (  Network   )   |    |   |    |   |   |
     ---     ----     ----     (          )     ----     ----     ---
      ^      ^        :         (        )         :        :
      :      :        :          --------          :        :
    UNI-C  UNI-N      :                            :        :
             :        :                            :        :
             :<------>:<-------------------------->:<------>:
              802.1ad      IP/MPLS/SR Domain        802.1ad
              q-in-q                                q-in-q

        Figure 3: Architectural Model for EVC over a Single Network

   Nevertheless, the remote site may be outside of the provider's
   service territory.  In this case, the provider may partner with the
   operator of another metro netork to provider service to the off-net
   location as shown in Figure 4.

   The first provider owns the customer relationship, thus the end-to-
   end EVC.  The EVC is comprised of two or more OVCs.  Partially of the
   EVC is an OVC from local UNI-C to the inter-provider interface.  The
   provider will purchase an Ethernet Access (E-Access) OVC from the
   second operator to deliver p acket to the remote UNI-C.

   The inter-connect between the two operators edge gateway (EG) devices
   is defined as the External Network-to-Network Interface (E-NNI).

Wen, et al.               Expires March 5, 2017                [Page 10]
Internet-Draft             L2VPN Sevice Model             September 2016

                            EVC
         :<---------------------------------------------------->:
         :                                                      :
         :                                                      :
         :       OVC (Optional)                                 :
         :<----------------------->:                            :
         :                         :                            :
         :                         :                            :
         :           PW / VXLAN    :                            :
         :    :<------------------>:                            :
         :    :                    :                            :
         :    :                    :                            :
         :    :      -----         :            -----           :
         :    :     (     )        :           (     )          :
     -   --   --   (  IP/  )   ----    ----   (  IP/  )   --   --   -
    |C+-+CE+-+PE+--+ MPLS/ +--+Edge+--+Edge+--+ MPLS/ +--+PE+-+CE+-+C|
     -   --   --   (  SR   )  |G/W |  |G/W |  (  SR   )   --   --   -
     ^    ^   :     (     )    ----    ----    (     )              ^
     :    :   :      -----         ^   ^        -----               :
    UNI  UNI  :                 ENNI   ENNI                         :
     C    N   :                    :   :                            :
          :   :                    :   :                       Remote
          :<->:<------------------>:<->:                     Customer
         802.1ad    IP/MPLS/SR    802.1ad                        Site
          q-in-q      Domain       q-in-q

       Figure 4: Architectural Model for EVC over Multiple Networks

4.  Service Data Model Usage

   The L2VPN service model provides an abstracted interface to request,
   configure and manage the components of a L2VPN service.  The model is
   used by a customer who purchases connectivity and other services from
   an SP to communicate with that SP.

   A typical usage is for this model to be an input for an orchestration
   layer that is responsible for translating it into configuration
   commands for the network elements that deliver/enable the service.
   The network elements may be routers, but also servers (like AAA)
   necessary within the network.

   The configuration of network elements may be done usiing the Command
   Line Interface (CLI), or any other configuration (or "southbound")
   interface such as NETCONF [RFC6241] in combination with device-
   specific and protocol-specific YANG models.

Wen, et al.               Expires March 5, 2017                [Page 11]
Internet-Draft             L2VPN Sevice Model             September 2016

   This way of using the service model is illustrated in Figure 5 and
   described in more detail in [I-D.wu-opsawg-service-model-explained].
   The usage of this service model is not limited to this example: it
   can be used by any component of the management system, but not
   directly by network elements.

   The usage and structure of this model should be compared to the Layer
   3 VPN service model defned in [I-D.ietf-l3sm-l3vpn-service-model].

          ---------------------------
         | Customer Servce Requester |
          ---------------------------
              |
      L2VPN   |
      Service |
      Model   |
              |
            -----------------------
           | Service Orchestration |
            -----------------------
              |
              |     Service             +-------------+
              |     Delivery    +------>| Application |
              |     Model       |       |   BSS/OSS   |
              |                 V       +-------------+
            -----------------------
           | Network Orchestration |
            -----------------------
              |            |
      +----------------+   |
      | Config manager |   |
      +----------------+   |  Device
              |            |  Models
              |            |
   --------------------------------------------
                     Network

     Figure 5: Reference Architecture for the Use of the L2VPN Service
                                   Model

5.  Design of the Data Model

   The YANG module is divided in three main containers : customer-info,
   vpn-services, and sites.

   The customer-info defines global parameters for a specific customer.

Wen, et al.               Expires March 5, 2017                [Page 12]
Internet-Draft             L2VPN Sevice Model             September 2016

   The vpn-svc container under vpn-services defines global parameters
   for the VPN service for a specific customer.

   A site is composed of at least one uni-site or one enni-site.

   Authorization of traffic exchange is done through what we call a VPN
   policy or VPN topology defining routing exchange rules between sites.

   The figure below describe the overall structure of the YANG module:

   module: ietf-l2svc

   +--rw l2vpn-svc
      +--rw customer-info
      |  +--rw customer-info* [customer-account-number customer-name]
      |     +--rw customer-account-number      string
      |     +--rw customer-name                string
      |     +--rw customer-operation-center
      |        +--rw customer-noc-street-address?   string
      |        +--rw customer-noc-phone-number
      |           +--rw main-phone-num?      uint32
      |           +--rw extension-options?   uint32
      +--rw vpn-services
      |  +--rw vpn-svc* [svc-id]
      |     +--rw svc-id                     string
      |     +--rw svc-type
      |     |  +--rw evc
      |     |  |  +--rw evc-id?   boolean
      |     |  +--rw ovc
      |     |     +--rw on-net-ovc-id?   boolean
      |     |     +--rw off-net-ov-id?   boolean
      |     +--rw ethernet-svc-type
      |     |  +--rw (ethernet-svc-type)?
      |     |     +--:(e-line)
      |     |     |  +--rw epl?           boolean
      |     |     |  +--rw evpl?          boolean
      |     |     +--:(e-lan)
      |     |     |  +--rw ep-lan?        boolean
      |     |     |  +--rw evp-lan?       boolean
      |     |     +--:(e-access)
      |     |        +--rw access-epl?    boolean
      |     |        +--rw access-evpl?   boolean
      |     +--rw metro-network-id
      |     |  +--rw inter-mkt-service?   boolean
      |     |  +--rw intra-mkt* [metro-mkt-id mkt-name]
      |     |     +--rw metro-mkt-id    uint32
      |     |     +--rw mkt-name        string
      |     +--rw signaling-option

Wen, et al.               Expires March 5, 2017                [Page 13]
Internet-Draft             L2VPN Sevice Model             September 2016

      |     |  +--rw signaling-option* [name type]
      |     |     +--rw name                      string
      |     |     +--rw type                      identityref
      |     |     +--rw mp-bgp-l2vpn
      |     |     |  +--rw vpn-id?   string
      |     |     |  +--rw type?     identityref
      |     |     +--rw mp-bgp-evpn
      |     |     |  +--rw vpn-id?   string
      |     |     |  +--rw type?     identityref
      |     |     +--rw t-ldp-pwe
      |     |     |  +--rw PE-EG-list* [service-ip-lo-addr vc-id]
      |     |     |     +--rw service-ip-lo-addr    inet:ip-address
      |     |     |     +--rw vc-id                 string
      |     |     +--rw pwe-encapsulation-type
      |     |     |  +--rw ethernet?   boolean
      |     |     |  +--rw vlan?       boolean
      |     |     +--rw pwe-mtu
      |     |     |  +--rw allow-mtu-mismatch?   boolean
      |     |     +--rw control-word
      |     +--rw load-balance-option
      |     |  +--rw fat-pw?          boolean
      |     |  +--rw entropy-label?   boolean
      |     +--rw svlan-id-ethernet-tag?     string
      |     +--rw cvlan-id-to-evc-map* [map-id]
      |     |  +--rw map-id    string
      |     +--rw service-level-mac-limit?   string
      |     +--rw service-protection
      |        +--rw protection-model
      |        +--rw peer-evc-id
      +--rw site
         +--rw uni-sites
         |  +--rw uni-site* [site-id]
         |     +--rw site-id                string
         |     +--rw management
         |     |  +--rw site-name?              string
         |     |  +--rw address?                inet:ip-address
         |     |  +--rw ce-device-info?         string
         |     |  +--rw type?                   identityref
         |     |  +--rw management-transport?   identityref
         |     +--rw location
         |     |  +--rw address?        string
         |     |  +--rw zip-code?       string
         |     |  +--rw state?          string
         |     |  +--rw city?           string
         |     |  +--rw country-code?   string
         |     +--rw site-diversity {site-diversity}?
         |     |  +--rw groups
         |     |     +--rw group* [group-id]

Wen, et al.               Expires March 5, 2017                [Page 14]
Internet-Draft             L2VPN Sevice Model             September 2016

         |     |        +--rw group-id    string
         |     +--rw security
         |     |  +--rw authentication
         |     |  +--rw encryption {encryption}?
         |     |     +--rw enabled?              boolean
         |     |     +--rw layer?                enumeration
         |     |     +--rw encryption-profile
         |     |        +--rw (profile)?
         |     |           +--:(provider-profile)
         |     |           |  +--rw profile-name?    string
         |     |           +--:(customer-profile)
         |     |              +--rw algorithm?       string
         |     |              +--rw (key-type)?
         |     |                 +--:(psk)
         |     |                 |  +--rw preshared-key?   string
         |     |                 +--:(pki)
         |     +--rw signaling-option
         |     |  +--rw signaling-option* [name type]
         |     |     +--rw name                      string
         |     |     +--rw type                      identityref
         |     |     +--rw mp-bgp-l2vpn
         |     |     |  +--rw vpn-id?   string
         |     |     |  +--rw type?     identityref
         |     |     +--rw mp-bgp-evpn
         |     |     |  +--rw vpn-id?   string
         |     |     |  +--rw type?     identityref
         |     |     +--rw t-ldp-pwe
         |     |     |  +--rw PE-EG-list* [service-ip-lo-addr vc-id]
         |     |     |     +--rw service-ip-lo-addr    inet:ip-address
         |     |     |     +--rw vc-id                 string
         |     |     +--rw pwe-encapsulation-type
         |     |     |  +--rw ethernet?   boolean
         |     |     |  +--rw vlan?       boolean
         |     |     +--rw pwe-mtu
         |     |     |  +--rw allow-mtu-mismatch?   boolean
         |     |     +--rw control-word
         |     +--rw load-balance-option
         |     |  +--rw fat-pw?          boolean
         |     |  +--rw entropy-label?   boolean
         |     +--rw uni-ports
         |        +--rw uni-port* [uni-id]
         |           +--rw uni-id                  string
         |           +--rw bearer
         |           |  +--rw phy-interface
         |           |  |  +--rw port-number?           uint32
         |           |  |  +--rw port-speed?            uint32
         |           |  |  +--rw auto-neg?              string
         |           |  |  +--rw phy-mtu?               uint32

Wen, et al.               Expires March 5, 2017                [Page 15]
Internet-Draft             L2VPN Sevice Model             September 2016

         |           |  |  +--rw flow-control?          string
         |           |  |  +--rw encapsulation-type?    enumeration
         |           |  |  +--rw ethertype?             string
         |           |  |  +--rw lldp?                  string
         |           |  |  +--rw oam-802.3AH-link?      string
         |           |  |  +--rw uni-loop-prevention?   boolean
         |           |  +--rw LAG-interface
         |           |  |  +--rw LAG-interface* [LAG-interface-number]
         |           |  |     +--rw LAG-interface-number    uint32
         |           |  |     +--rw LACP
         |           |  |        +--rw LACP-on-off?          enumeration
         |           |  |        +--rw LACP-mode?            enumeration
         |           |  |        +--rw LACP-speed?           enumeration
         |           |  |        +--rw mini-link?            uint32
         |           |  |        +--rw system-priority?      uint32
         |           |  |        +--rw Micro-BFD
         |           |  |        |  +--rw Micro-BFD-on-off?  enumeration
         |           |  |        |  +--rw bfd-interval?      uint32
         |           |  |        |  +--rw bfd-hold-timer?    uint32
         |           |  |        +--rw Member-link-list
         |           |  |        |  +--rw member-link* [name]
         |           |  |        |     +--rw name                string
         |           |  |        |     +--rw port-speed?         uint32
         |           |  |        |     +--rw auto-neg?           string
         |           |  |        |     +--rw mtu?                uint32
         |           |  |        |     +--rw oam-802.3AH-link?   string
         |           |  |        +--rw flow-control?         string
         |           |  |        +--rw encapsulation-type?   enumeration
         |           |  |        +--rw ethertype?            string
         |           |  |        +--rw lldp?                 string
         |           |  +--rw interface-description?   string
         |           |  +--rw sub-if-id?               uint32
         |           +--rw ethernet-connection
         |           |  +--rw vlan
         |           |  |  +--rw svlan-id-ethernet-tag?   string
         |           |  |  +--rw cvlan-id-to-evc-map* [map-id]
         |           |  |     +--rw map-id    string
         |           |  +--rw oam
         |           |     +--rw MD-name?    string
         |           |     +--rw MD-level?   uint8
         |           +--rw evc-mtu?                uint32
         |           +--rw mac-addr-limit
         |           |  +--rw exceeding-option?   uint32
         |           +--rw S-vlan
         |           |  +--rw c-vlan2evc-mapping?   string
         |           +--rw multihoming
         |           |  +--rw multihoming* [ESI]
         |           |     +--rw ESI              string

Wen, et al.               Expires March 5, 2017                [Page 16]
Internet-Draft             L2VPN Sevice Model             September 2016

         |           |     +--rw (redundancy-mode)?
         |           |        +--:(single-active)
         |           |        |  +--rw single-active?   boolean
         |           |        +--:(all-active)
         |           |           +--rw all-active?      boolean
         |           +--rw L2CP-control
         |           |  +--rw stp-rstp-mstp?           control-mode
         |           |  +--rw pause?                   control-mode
         |           |  +--rw lacp-lamp?               control-mode
         |           |  +--rw link-oam?                control-mode
         |           |  +--rw esmc?                    control-mode
         |           |  +--rw l2cp-802.1x?             control-mode
         |           |  +--rw e-lmi?                   control-mode
         |           |  +--rw lldp?                    control-mode
         |           |  +--rw ptp-peer-delay?          control-mode
         |           |  +--rw garp-mrp?                control-mode
         |           |  +--rw provider-bridge-group?   yang:mac-address
         |           |  +--rw provider-bridge-mvrp?    yang:mac-address
         |           +--rw service
         |           |  +--rw svlan-id-ethernet-tag?     string
         |           |  +--rw cvlan-id-to-evc-map* [map-id]
         |           |  |  +--rw map-id    string
         |           |  +--rw service-level-mac-limit?   string
         |           |  +--rw service-level
         |           |     +--rw cos-identifier?                  string
         |           |     +--rw color-identifier?                string
         |           |     +--rw ingress-bw-profile-per-evc?      string
         |           |     +--rw ingress-bw-profile-per-cos-id?   string
         |           |     +--rw egress-bw-profile-per-evc?       string
         |           |     +--rw egress-bw-profile-per-cos-id?    string
         |           |     +--rw byte-offset?                     uint16
         |           |     +--rw COS?                             uint32
         |           +--rw B-U-M-strom-control
         |           +--rw mac-loop-prevention
         |           +--rw Ethernet-Service-OAM
         |           |  +--rw cfm-802.1-ag
         |           |  |  +--rw uni-n2uni-c* [MAID]
         |           |  |  |  +--rw MAID                     string
         |           |  |  |  +--rw mep-level?               uint32
         |           |  |  |  +--rw mep-up-down?             enumeration
         |           |  |  |  +--rw remote-mep-id?           uint32
         |           |  |  |  +--rw cos-for-cfm-pdus?        uint32
         |           |  |  |  +--rw ccm-interval?            uint32
         |           |  |  |  +--rw ccm-holdtime?            uint32
         |           |  |  |  +--rw alarm-priority-defect?   identityref
         |           |  |  +--rw uni-n2-uni-n* [MAID]
         |           |  |     +--rw MAID                     string
         |           |  |     +--rw mep-level?               uint32

Wen, et al.               Expires March 5, 2017                [Page 17]
Internet-Draft             L2VPN Sevice Model             September 2016

         |           |  |     +--rw mep-up-down?             enumeration
         |           |  |     +--rw remote-mep-id?           uint32
         |           |  |     +--rw cos-for-cfm-pdus?        uint32
         |           |  |     +--rw ccm-interval?            uint32
         |           |  |     +--rw ccm-holdtime?            uint32
         |           |  |     +--rw alarm-priority-defect?   identityref
         |           |  +--rw y-1731* [MAID]
         |           |     +--rw MAID                    string
         |           |     +--rw type?                   identityref
         |           |     +--rw remote-mep-id?          uint32
         |           |     +--rw measurement-interval?   uint32
         |           |     +--rw cos?                    uint32
         |           |     +--rw frame-size?             uint32
         |           +--rw security
         |              +--rw security
         |                 +--rw authentication
         |                 +--rw encryption {encryption}?
         |                    +--rw enabled?              boolean
         |                    +--rw layer?                enumeration
         |                    +--rw encryption-profile
         |                       +--rw (profile)?
         |                          +--:(provider-profile)
         |                          |  +--rw profile-name?    string
         |                          +--:(customer-profile)
         |                             +--rw algorithm?       string
         |                             +--rw (key-type)?
         |                                +--:(psk)
         |                                |  +--rw preshared-key? string
         |                                +--:(pki)
         +--rw enni-sites
            +--rw enni-site* [site-id]
               +--rw site-id                string
               +--rw location
               |  +--rw address?        string
               |  +--rw zip-code?       string
               |  +--rw state?          string
               |  +--rw city?           string
               |  +--rw country-code?   string
               +--rw site-diversity {site-diversity}?
               |  +--rw groups
               |     +--rw group* [group-id]
               |        +--rw group-id    string
               +--rw management
               |  +--rw site-name?                  string
               |  +--rw address?                    inet:ip-address
               |  +--rw Edge-Gateway-Device-Info?   string
               |  +--rw type?                       identityref
               |  +--rw management-transport?       identityref

Wen, et al.               Expires March 5, 2017                [Page 18]
Internet-Draft             L2VPN Sevice Model             September 2016

               +--rw security
               |  +--rw authentication
               |  +--rw encryption {encryption}?
               |     +--rw enabled?              boolean
               |     +--rw layer?                enumeration
               |     +--rw encryption-profile
               |        +--rw (profile)?
               |           +--:(provider-profile)
               |           |  +--rw profile-name?    string
               |           +--:(customer-profile)
               |              +--rw algorithm?       string
               |              +--rw (key-type)?
               |                 +--:(psk)
               |                 |  +--rw preshared-key?   string
               |                 +--:(pki)
               +--rw service-protection
               |  +--rw protection-model
               |  +--rw peer-evc-id
               +--rw signaling-option
               |  +--rw signaling-option* [name type]
               |     +--rw name                      string
               |     +--rw type                      identityref
               |     +--rw mp-bgp-l2vpn
               |     |  +--rw vpn-id?   string
               |     |  +--rw type?     identityref
               |     +--rw mp-bgp-evpn
               |     |  +--rw vpn-id?   string
               |     |  +--rw type?     identityref
               |     +--rw t-ldp-pwe
               |     |  +--rw PE-EG-list* [service-ip-lo-addr vc-id]
               |     |     +--rw service-ip-lo-addr    inet:ip-address
               |     |     +--rw vc-id                 string
               |     +--rw pwe-encapsulation-type
               |     |  +--rw ethernet?   boolean
               |     |  +--rw vlan?       boolean
               |     +--rw pwe-mtu
               |     |  +--rw allow-mtu-mismatch?   boolean
               |     +--rw control-word
               +--rw load-balance-option
               |  +--rw fat-pw?          boolean
               |  +--rw entropy-label?   boolean
               +--rw enni-ports
                  +--rw enni-port* [enni-id]
                     +--rw enni-id                 string
                     +--rw remote-carrier-name?    string
                     +--rw bearer
                     |  +--rw phy-interface
                     |  |  +--rw port-number?           uint32

Wen, et al.               Expires March 5, 2017                [Page 19]
Internet-Draft             L2VPN Sevice Model             September 2016

                     |  |  +--rw port-speed?            uint32
                     |  |  +--rw auto-neg?              string
                     |  |  +--rw phy-mtu?               uint32
                     |  |  +--rw flow-control?          string
                     |  |  +--rw encapsulation-type?    enumeration
                     |  |  +--rw ethertype?             string
                     |  |  +--rw lldp?                  string
                     |  |  +--rw oam-802.3AH-link?      string
                     |  |  +--rw uni-loop-prevention?   boolean
                     |  +--rw LAG-interface
                     |  |  +--rw LAG-interface* [LAG-interface-number]
                     |  |     +--rw LAG-interface-number    uint32
                     |  |     +--rw LACP
                     |  |        +--rw LACP-on-off?          enumeration
                     |  |        +--rw LACP-mode?            enumeration
                     |  |        +--rw LACP-speed?           enumeration
                     |  |        +--rw mini-link?            uint32
                     |  |        +--rw system-priority?      uint32
                     |  |        +--rw Micro-BFD
                     |  |        |  +--rw Micro-BFD-on-off?  enumeration
                     |  |        |  +--rw bfd-interval?      uint32
                     |  |        |  +--rw bfd-hold-timer?    uint32
                     |  |        +--rw Member-link-list
                     |  |        |  +--rw member-link* [name]
                     |  |        |     +--rw name                string
                     |  |        |     +--rw port-speed?         uint32
                     |  |        |     +--rw auto-neg?           string
                     |  |        |     +--rw mtu?                uint32
                     |  |        |     +--rw oam-802.3AH-link?   string
                     |  |        +--rw flow-control?         string
                     |  |        +--rw encapsulation-type?   enumeration
                     |  |        +--rw ethertype?            string
                     |  |        +--rw lldp?                 string
                     |  +--rw interface-description?   string
                     |  +--rw sub-if-id?               uint32
                     +--rw ethernet-connection
                     |  +--rw vlan
                     |  |  +--rw svlan-id-ethernet-tag?   string
                     |  |  +--rw cvlan-id-to-evc-map* [map-id]
                     |  |     +--rw map-id    string
                     |  +--rw oam
                     |     +--rw MD-name?    string
                     |     +--rw MD-level?   uint8
                     +--rw evc-mtu?                uint32
                     +--rw mac-addr-limit
                     |  +--rw exceeding-option?   uint32
                     +--rw S-vlan
                     |  +--rw c-vlan2evc-mapping?   string

Wen, et al.               Expires March 5, 2017                [Page 20]
Internet-Draft             L2VPN Sevice Model             September 2016

                     +--rw multihoming
                     |  +--rw multihoming* [ESI]
                     |     +--rw ESI              string
                     |     +--rw (redundancy-mode)?
                     |        +--:(single-active)
                     |        |  +--rw single-active?   boolean
                     |        +--:(all-active)
                     |           +--rw all-active?      boolean
                     +--rw L2CP-control
                     |  +--rw stp-rstp-mstp?           control-mode
                     |  +--rw pause?                   control-mode
                     |  +--rw lacp-lamp?               control-mode
                     |  +--rw link-oam?                control-mode
                     |  +--rw esmc?                    control-mode
                     |  +--rw l2cp-802.1x?             control-mode
                     |  +--rw e-lmi?                   control-mode
                     |  +--rw lldp?                    control-mode
                     |  +--rw ptp-peer-delay?          control-mode
                     |  +--rw garp-mrp?                control-mode
                     |  +--rw provider-bridge-group?   yang:mac-address
                     |  +--rw provider-bridge-mvrp?    yang:mac-address
                     +--rw service
                     |  +--rw svlan-id-ethernet-tag?     string
                     |  +--rw cvlan-id-to-evc-map* [map-id]
                     |  |  +--rw map-id    string
                     |  +--rw service-level-mac-limit?   string
                     |  +--rw service-level
                     |     +--rw cos-identifier?                  string
                     |     +--rw color-identifier?                string
                     |     +--rw ingress-bw-profile-per-evc?      string
                     |     +--rw ingress-bw-profile-per-cos-id?   string
                     |     +--rw egress-bw-profile-per-evc?       string
                     |     +--rw egress-bw-profile-per-cos-id?    string
                     |     +--rw byte-offset?                     uint16
                     |     +--rw COS?                             uint32
                     +--rw B-U-M-strom-control
                     +--rw mac-loop-prevention
                     +--rw Ethernet-Service-OAM
                     |  +--rw cfm-802.1-ag
                     |  |  +--rw uni-n2uni-c* [MAID]
                     |  |  |  +--rw MAID                     string
                     |  |  |  +--rw mep-level?               uint32
                     |  |  |  +--rw mep-up-down?             enumeration
                     |  |  |  +--rw remote-mep-id?           uint32
                     |  |  |  +--rw cos-for-cfm-pdus?        uint32
                     |  |  |  +--rw ccm-interval?            uint32
                     |  |  |  +--rw ccm-holdtime?            uint32
                     |  |  |  +--rw alarm-priority-defect?   identityref

Wen, et al.               Expires March 5, 2017                [Page 21]
Internet-Draft             L2VPN Sevice Model             September 2016

                     |  |  +--rw uni-n2-uni-n* [MAID]
                     |  |     +--rw MAID                     string
                     |  |     +--rw mep-level?               uint32
                     |  |     +--rw mep-up-down?             enumeration
                     |  |     +--rw remote-mep-id?           uint32
                     |  |     +--rw cos-for-cfm-pdus?        uint32
                     |  |     +--rw ccm-interval?            uint32
                     |  |     +--rw ccm-holdtime?            uint32
                     |  |     +--rw alarm-priority-defect?   identityref
                     |  +--rw y-1731* [MAID]
                     |     +--rw MAID                    string
                     |     +--rw type?                   identityref
                     |     +--rw remote-mep-id?          uint32
                     |     +--rw measurement-interval?   uint32
                     |     +--rw cos?                    uint32
                     |     +--rw frame-size?             uint32
                     +--rw security
                        +--rw security
                           +--rw authentication
                           +--rw encryption {encryption}?
                              +--rw enabled?              boolean
                              +--rw layer?                enumeration
                              +--rw encryption-profile
                                 +--rw (profile)?
                                    +--:(provider-profile)
                                    |  +--rw profile-name?    string
                                    +--:(customer-profile)
                                       +--rw algorithm?       string
                                       +--rw (key-type)?
                                          +--:(psk)
                                          |  +--rw preshared-key? string
                                          +--:(pki)

                                 Figure 6

5.1.  Overview of Main Components of the Model

   The L2SM model is structured in a way that allows the provider to
   list multiple circuits of various service types for the same
   subscriber.

5.1.1.  Customer Information

   The "customer-info" container contains essential information to
   identify the subscriber.

Wen, et al.               Expires March 5, 2017                [Page 22]
Internet-Draft             L2VPN Sevice Model             September 2016

   "customer-account-number" is an internal alphanumerical number
   assigned by the service provider to identify the subscriber.  It MUST
   be unique within the service provider?s OSS/BSS system.  The actual
   format depends on the system tool the provider uses. "customer-name"
   is in more readable form.

   Subscriber operation center and main contact number are also listed
   here for reference purpose.

5.1.2.  VPN Service Overview

   The "svc-type" container contains two optional leaves: one for EVC
   (Ethernet Virtual Connection) and the other one for OVC (Operator
   Virtual Connection).  These two parameters are not mutually
   exclusive.  Depending on the service-type, a Layer 2 VPN service may
   be identified by EVC-ID, OVC-ID, or both.

   E-Line and E-LAN provider shall have EVC-ID assigned to the UNI-to-
   UNI circuit.  If the service has remote UNIs in off-net partner's
   network, there will be one OVC-ID for the on-net segment between
   local UNI to the E-NNI interconnect, and one OVC-ID for each off-net
   segment from E-NNI to the remote UNI.  E-Access, on the other hand,
   is OVC-based service.  The E-Access service provider will assign OVC-
   ID for the circuit between UNI to E-NNI.

   The "svc-type" container can be augmented in the future to support
   other new technologies.  Note that the "svc-id" should be
   corresponding to the "svc-type".

5.1.2.1.  Service Type

   The "svc-type" container contains two cases, one for EVC (Ethernet
   Virtual Connection), the other for OVC (Operator Virtual Connection).
   It can be used to indicate the type of service pipe type.  The model
   user also can augment the "svc-type" container with other cases to
   support future technologies.  Notes that the "svc-id" should be
   corresponding to the "svc-type".

5.1.2.1.1.  EVC

   The "evc"case contains an "evc-id" leaf with boolean type.  The "evc-
   id" leaf will be marked TRUE for E-Line and E-LAN service types.  And
   the "svc-id" will be associated with the "evc-id".  Only one "evc-id"
   is allowed for each "svc-id".

   The EVC ID is intended to be a structured string.  Each service
   provider can decide the nomenclature in its network.  For example,
   many carriers in North American have implemented the COMMON LANGUAGE?

Wen, et al.               Expires March 5, 2017                [Page 23]
Internet-Draft             L2VPN Sevice Model             September 2016

   Special Service Circuit Codes (CLCI S/S Codes) - Serial Number
   Format, which is defined in defined in ANSI ATIS-0300097.

5.1.2.1.2.  OVC

   The "ovc" case contains two boolean subcases: "on-net-ovc" and "off-
   net-ovc".

   For E-Access or services with off-net UNIs, the "on-net-ovc" leaf
   MUST be marked TRUE.  And the "on-net-ovc-id" will be specified.

   In case of E-Access, the "svc-id" will be associated with the "on-
   net-ovc-id".  Only one "on-net-ovc-id" is allowed for each "svc-id".

   If the service is E-Line or E-LAN with remote UNIs, there will be
   one, and only one, "on-net-ovc-id" and a list of "off-net-ovc-id"s
   for the remote UNIs.  However, the "svc-id" is still associated with
   the "evc-id".  Only one "evc-id" is allowed for each "svc-id".  New
   ovc type could be added by augmentation.

5.1.2.2.  ethernet-svc-type

   The "ethernet-svc-type" group contains all supported Ethernet service
   types.  One, and only one, "ethernet-svc-type" must be selected for
   each "svc-id".

   The current supported Ethernet service types are listed in section
   3.2.  New service types can be added in the future.

5.1.2.3.  Metro Network Partition

   Some servicer providers may divide their network into multiple
   administrative domains.  And a Layer 2 VPN service may span across
   more than one metro network of the same service provider.  The
   optional "metro-network-id" container is intended be used by these
   multi-domain providers to differentiate intra-market vs.  inter-
   market service.

   When the "inter-mkt-service" leaf is marked TRUE, multiple associated
   "metro-mkt-id"s will be listed.  Otherwise, the service is intra-
   domain and only one "metro-mkt-id" is allowed.

5.1.2.4.  vpn-signaling-option

   The "signaling-option" container captures service-wide attributes of
   the L2VPN instance.

Wen, et al.               Expires March 5, 2017                [Page 24]
Internet-Draft             L2VPN Sevice Model             September 2016

   Although topology discovery or network device configurations is
   purposely out-scoped from the L2SM model, certain VPN parameters are
   listed here nevertheless.  The information here can then be passed to
   other elements in the whole automation eco-system, such as the
   configuration engine, which will handle the actual service
   provisioning function.

   The "signaling-option" list uses "name" and "type" combination as the
   key.  The "name" leaf is a freeform string of the VPN instance name.
   The "type" leaf is for the signaling protocol: BGP-L2VPN, BGP-EVPN,
   or T-LDP.

5.1.2.4.1.  BGP L2VPN

   [RFC4761] and [RFC6624] describe the mechanism to auto-discover L2VPN
   VPLS/VPWS end points (CE-ID or VE-ID) and signal the label base and
   offset at the same time to allow remote PE to derive the VPN label to
   be used when sending packets to the advertising router.

   Due to the auto-discovery natural, PEs that have at least one
   attachment circuit associated with a particular VPN service do not
   need to be specified explicitly.

   In the L2SM model, only the target community (or communities) will be
   listed at the service level.

   The "type" leaf under "mp-bgp-l2vpn" is an identityref to specify
   "vpws" or "vpls" sub-types.

5.1.2.4.2.  BGP EVPN

   Defined in [RFC7432], EVPN is a new promising L2VPN technology based
   upon BGP MAC routing.  It's considered the next generation L2VPN
   solution that provides similar functionality of BGP VPWS/VPLS with
   improvement around redundancy, multicast optimization, provisioning
   and simplicity.

   Due to the auto-discovery natural, PEs that have at least one
   attachment circuit associated with a particular VPN service do not
   need to be specified explicitly.

   In the L2SM model, only the target community (or communities) will be
   listed at the service level.

   The "type" leaf under "mp-bgp-evpn" is an identityref to specify
   "vpws" or "vpls" sub-types.

Wen, et al.               Expires March 5, 2017                [Page 25]
Internet-Draft             L2VPN Sevice Model             September 2016

5.1.2.4.3.  LDP Pseudowires

   [RFC4762] specified the method of using targeted LDP sessions between
   PEs to exchange VC label information.  This requires a manually
   define a full mesh of targeted LDP sessions between all PEs.

   As multiple attachment circuits may terminate on a single PE, this
   PE-to-PE mesh is not a per site attribute.  All PEs related to the
   L2VPN service will be listed in the "t-ldp-pwe" with associated "vc-
   id".

5.1.2.4.4.  PWE Encapsulation Type

   Based on [RFC4448], there are two types of Ethernet services: "Port-
   to-Port Ethernet PW emulation" and "Vlan-to-Vlan Ethernet PW
   emulation", commonly referred to as Type 5 and Type 4 respectively.
   This concept applies to both BGP L2VPN VPWS/VPLS and T-LDP signaled
   PWE implementions.

   The "pwe-encapsulation-type" container contains two Boolean type
   leaves: "ethernet" and "ethernet-vlan", only one should be marked
   TRUE if "signaling-option" is "mp-bgp-l2vpn" or "t-ldp-pwe".

5.1.2.4.5.  PWE MTU

   During the signaling process of BGP-l2vpn or T-LDP pseudowire, the
   pwe-mtu value is exchanged and must match on both ends.  By default,
   the pwe-mtu is derived from physical interface MTU of the attachment
   circuit minus the EoMPLS transport header.  In some cases, however,
   the physical interface on both ends of the circuits may not have
   identical MTU settings.  For example, due to 802.1ad q-in-q
   operation, I-NNI interface will need extra four bytes to accommodate
   the S-tag.  The inter-carrier E-NNI link may also have a different
   MTU size then the internal network interfaces.

   [RFC4448] requires same MTU size on physical interface on both end of
   the pseudowire.  In actual implementations, many router vendors have
   provided the knob to explicitly specify the pwe-mtu, which can then
   be decoupled from the physical interface MTU.

   When there's a mismatch between the physical interface MTU and
   configured pwe-mtu, "allow-mtu-mismatch" knob is also required in
   many cases.

   The optional "pwe-mtu" container is for this purpose.

Wen, et al.               Expires March 5, 2017                [Page 26]
Internet-Draft             L2VPN Sevice Model             September 2016

5.1.2.4.6.  Control Word

   A control word is an optional 4-byte field located between the MPLS
   label stack and the Layer 2 payload in the pseudowire packet.  It
   plays a vital role in Any Transport over MPLS (AToM).  The 32-bit
   field carries generic and Layer 2 payload-specific information,
   including a C-bit which indicates whether the control word will
   present in the Ethernet over MPLS (EoMPLS) packets.  If the C-bit is
   set to 1, the advertising PE expects the control word to be present
   in every pseudowire packet on the pseudowire that is being signaled.
   If the C-bit is set to 0, no control word is expected to be present.

   Whether to include control word in the pseudowire packets MUST match
   on PEs at both ends of the pseudowire and it's non-negotiable during
   the signaling process.

   Control-word applies to both BGP L2VPN VPWS/VPLS and T-LDP signaled
   PWE implementions.  It is a routing-instance level configuration in
   many cases.

   The optional "control-word" leaf is a Boolean field in the L2SM model
   for the provider to explicitly specify whether control-word will be
   signaled for the service instance.

5.1.2.5.  Load Balance Option

   As the subscribers start to deploy more 10G or 100G Ethernet
   equipment in their network, the demand for high bandwidth Ethernet
   services increases.  Along with the great revenue opportunities,
   these high bandwidth service requests also pose challenges on
   capacity planning and service delivery in the provider's network.
   Especially when the contractual bandwidth is at, or close to, the
   speed of physical link of the service provider's core network.
   Because of the encapsulation overhead, the provider can not deliver
   the throughput in the service level agreement over a single link.
   Although there may be bundled Nx10G or Nx100G aggregation links
   between core network elements, or Equal Cost Multiple Paths (ECMP) in
   the network, an EoMPLS PWE or VxLAN circuit is considered a single
   flow to a router or switch which uses the five tuples in the hashing
   algorithm.

   Without burdening the core routers with additional processing of deep
   inspection into the payload, the service provider now have the option
   of inserting flow or entropy label into the EoMPLS frames, or using
   different source UDP ports in case of VxLAN/EVPN, at ingress PE to
   facility load-balancing on the subsequent nodes along the path.  The
   ingress PE is in a unique position to see the actual unencapsulated

Wen, et al.               Expires March 5, 2017                [Page 27]
Internet-Draft             L2VPN Sevice Model             September 2016

   service frames and identify data flows based on the original Ethernet
   and IP header.

   On the other hand, not all Layer 2 Ethernet VPNs is suited for load-
   balancing across diverse ECMP paths.  For example, a Layer 2 Ethernet
   service transported over a single RSVP signaled LSP will not take
   multiple ECMP paths.  Or if the subscriber is concerned about
   latency/jitter then diverse path load-balance can be undesirable.

   The optional "load-balance-option" container is intended to capture
   the load-balance agreement between the subscriber and provider.  If
   the "load-balance" Boolean leaf is marked TRUE, then one of the
   following load-balance methods can be selected: "fat-pw", "entropy-
   label", or "vxland-source-udp-port".

5.1.2.6.  SVLAN ID Ethernet Tag

   Service providers have the option of inserting an outer Vlan tag (the
   S-tag) into the service frames from the subscriber to improve service
   scalability and customer Vlan transparency.

   Ideally, all external interfaces (UNI and E-NNI) associated with a
   given service will have the same S-tag assigned.  However, this may
   not always be the case.  Traffic with all attachments using different
   S-tags will need to be "normalized" to a single service S-tag.  (One
   example of this is a multipoint service involves multiple off-net
   OVCs terminating on the same E-NNI interface.  Each of these off-net
   OVCs will have a distinct S-tag, which can be different from the
   S-tag used in the on-net part of the service.)

   The purpose of the optional "svlan-id-ethernet-tag" leaf is to
   identify the service-wide "normalized S-tag".

5.1.2.7.  CVLAN ID To EVC MAP

   When more than one services are multiplexed on the same UNI
   interface, ingress service frames are conditionally transmitted
   through one of the EVC/OVCs based upon pre-arranged customer VLAN to
   EVC mapping.  Multiple customer VLANs can be bundled across the same
   EVC.

   "cvlan-id-to-evc-map", when applicable, contains the list of customer
   vlans to the service mapping in a freeform format.  In most cases,
   this will be the vlan access-list for the inner 802.1q tags (the
   C-tag).

Wen, et al.               Expires March 5, 2017                [Page 28]
Internet-Draft             L2VPN Sevice Model             September 2016

5.1.2.8.  Service Level MAC Limit

   When multiple services are provided on the same network element, MAC
   address table, and RIB space for MAC-routes in case of EVPN, are
   shared common resource.  Service providers may impose a maximum
   number of MAC learned from the subscriber for a single service
   instance, and specify the action when the upper limit is violated:
   drop the packet, flood the packet, or simply send a warning log
   message.

   For point-to-point services, if MAC learning is disabled then MAC
   limit is not necessary in this kind of implementation.

   The optional "service-level-mac-limit" container contains the
   subscriber MAC address limit and exceeding action information.

5.1.2.9.  Service Protection

   Sometimes the subscriber may desire end-to-end protection at the
   service level for applications with high availability requirements.
   There are two protection schemes to offer redundant services:

   o  1+1 protection: In this scheme, the primary EVC or OVC will be
      protected by a backup EVC or OVC, typically meet certain
      diversified path/fiber/site/node criteria.  Both primary and
      protection circuits are provisioning to be in forwarding state.
      Subscriber may choose to send the same service frames across both
      circuits simultaneously.

   o  1:1 protection: In this scheme, a backup circuit can be
      provisioning to the primary circuits.  Depending on the
      implementation agreement, the protection circuits may either
      always be in forwarding state, or only become active when
      detecting a faulty state or the primary circuit.

   The optional "service-protection" container hereby is to capature the
   desired service protection agreement between subscriber and provider.

   An "peer-evc-id" should be specified when the "protection-model" has
   value.

5.1.3.  site

   A site represents a connection of a customer location to one or more
   VPN services.  In l2 vpn service model, we present two kinds of site:
   UNI (User network interfaces) site and ENNI (External Network to
   Network Interface) site.

Wen, et al.               Expires March 5, 2017                [Page 29]
Internet-Draft             L2VPN Sevice Model             September 2016

5.1.3.1.  uni-site

5.1.3.1.1.  Site Management

5.1.3.1.2.  Site Location

5.1.3.1.3.  Site Diversity

5.1.3.1.4.  Site Service

5.1.3.1.5.  Site Protection

5.1.3.1.6.  Site Signaling Option

5.1.3.1.7.  UNI Ports

5.1.3.1.7.1.  Bearer

5.1.3.1.7.2.  UNI Multihoming

5.1.3.1.7.3.  UNI L2CP-Control

5.1.3.1.7.4.  UNI Service

5.1.3.1.7.5.  UNI Ethernet Service OAM

5.1.3.1.7.6.  UNI Security

5.1.3.2.  enni-site

5.1.3.2.1.  Site Management

5.1.3.2.2.  Site Location

5.1.3.2.3.  Site Diversity

5.1.3.2.4.  Site Security

5.1.3.2.5.  Site Service

5.1.3.2.6.  Site Protection

5.1.3.2.7.  ENNI Signaling Options

Wen, et al.               Expires March 5, 2017                [Page 30]
Internet-Draft             L2VPN Sevice Model             September 2016

5.1.3.2.8.  ENNI Port

5.1.3.2.8.1.  ENNI Bearer

5.1.3.2.8.2.  ENNI Multihoming

5.1.3.2.8.3.  ENNI L2CP Control

5.1.3.2.8.4.  ENNI Ethernet Service OAM

5.1.3.2.8.5.  ENNI Security

6.  Service Model Usage Example

7.  Interaction with Other YANG Modules

   As expressed in Section 4, this service module is not intended to
   configure the network element, but is instantiated in a management
   system.

   The management system might follow modular design and comprise at
   least two different components:

   a.  The component instantiating the service model (let's call it the
       service component)

   b.  The component responsible for network element configuration
       (let's call it the configuration component)

   In some cases when the split is needed between the behavior and
   functions that a customer requests and the technology that the
   network operator has available to deliver the service [I-D.wu-opsawg-
   service-model-explained].  A new component can be separated out of
   the service component (let's call it the control component).  This
   component is responsible for network-centric operation and is aware
   of many features such as topology, technology, and operator policy.
   As an optional component, it can use service model as input and is
   not required if the control component delegates its control
   operations to the configuration component.

   In the previous sections, we provided some example of translation of
   service provisioning request to router configuration lines as an
   illustration.  In the NETCONF/YANG ecosystem, it is expected that
   NETCONF and YANG will be used between the configuration component and
   network elements to configure the requested service on those
   elements.

Wen, et al.               Expires March 5, 2017                [Page 31]
Internet-Draft             L2VPN Sevice Model             September 2016

   In this framework, it is expected that YANG models will be used for
   configuring service components on network elements.  There will be a
   strong relationship between the abstracted view provided by this
   service model and the detailed configuration view that will be
   provided by specific configuration models for network elements.
   Service components needing configuration on network elements in
   support of the service model defined in this document include:

   o  VRF definition including VPN policy expression.

   o  Physical interface.

   o  Ethernet layer (VLAN ID).

   o  QoS : classification, profiles, etc.

   o  Routing protocols : support of configuration of all protocols
      listed in the document, as well as routing policies associated
      with these protocols.

   o  Multicast Support.

   o  Ethernet Service OAM Support.

8.  YANG Module

   <CODE BEGINS> file "ietf-l2vpn-svc@2016-08-19.yang"
   module ietf-l2svc {

      namespace "urn:ietf:params:xml:ns:yang:ietf-l2svc";
      prefix "l2svc";

      import ietf-inet-types {
        prefix inet;
      }
      import ietf-yang-types {
           prefix yang;
      }
      organization
        "IETF L2SM Working Group.";

      contact
        "WG List:
         Editor: ";

      description
        "The YANG module defines a generic service configuration

Wen, et al.               Expires March 5, 2017                [Page 32]
Internet-Draft             L2VPN Sevice Model             September 2016

        model for Layer 2 VPN common across all of the vendor
        implementations.";

      revision 2016-08-30{
        description
          "Initial revision.";
        reference
          "draft-XXXX
           A YANG Data Model for layer 2 VPN.";
      }

      /* Feature*/

      feature carrierscarrier {
        description
        "Enables support of carrier&apos;s carrier";
      }

      feature site-diversity {
        description
          "Enables support of site diversity constraints";
      }

        feature encryption {
          description
            "Enables support of encryption";
        }

      /* Typedefs*/

      typedef control-mode {
        type enumeration{
          enum peer{
            description
              "peer mode";
        }
        enum tunnel {
          description
            "tunnel mode";
        }
        enum discard {
          description
            "discard mode";
        }
       }

       description
         "defining a type of the control mode";

Wen, et al.               Expires March 5, 2017                [Page 33]
Internet-Draft             L2VPN Sevice Model             September 2016

      }

      /* identity */
      identity vpn-signaling-type {
        description
          "identity of vpn signaling types";
      }

      identity vrf {
        base vpn-signaling-type;
        description
          "Virtual routing and forwarding (VRF).";
      }

      identity vfi {
        base vpn-signaling-type;
        description
          "Virtual forwarder interface";
      }

      identity evi {
        base vpn-signaling-type;
        description
          "ehternet virtual interconnect.";
      }

      identity l2vpn-type {
        description
          "layer 2 vpn types";
      }

      identity vpws {
        base l2vpn-type;
        description
          "Virtual Private Wire Service";
      }

      identity vpls {
        base l2vpn-type;
        description
          "Virtual Private LAN Service";
      }

      identity evpn {
        base l2vpn-type;
        description
          "Ethernet VPN";

Wen, et al.               Expires March 5, 2017                [Page 34]
Internet-Draft             L2VPN Sevice Model             September 2016

      }

      identity management {
        description
          "Base identity for site management scheme.";
      }
      identity co-managed {
        base management;
        description
          "Base identity for comanaged site.";
      }

      identity customer-managed {
        base management;
        description
          "Base identity for customer managed site.";
      }

      identity provider-managed {
        base management;
        description
          "Base identity for provider managed site.";
      }

      identity address-family {
        description
          "Base identity for an address family.";
      }

      identity ipv4 {
        base address-family;
        description
          "Identity for IPv4 address family.";
      }

      identity ipv6 {
        base address-family;
        description
          "Identity for IPv6 address family.";
      }

      identity vpn-topology {
        description
          "Base identity for VPN topology.";
      }

Wen, et al.               Expires March 5, 2017                [Page 35]
Internet-Draft             L2VPN Sevice Model             September 2016

      identity any-to-any {
        base vpn-topology;
        description
          "Identity for any to any VPN topology.";
      }

      identity hub-spoke {
        base vpn-topology;
        description
          "Identity for Hub&apos;n&apos;Spoke VPN topology.";
      }

      identity hub-spoke-disjoint {
        base vpn-topology;
        description
          "Identity for Hub&apos;n&apos;Spoke VPN topology
           where Hubs cannot talk between each other.";
      }

      identity site-role {
        description
          "Base identity for site type.";
      }

      identity any-to-any-role {
        base site-role;

        description
          "Site in a any to any IPVPN.";
      }

      identity spoke-role {
        base site-role;
        description
          "Spoke Site in a Hub &amp; Spoke IPVPN.";
      }

      identity hub-role {
        base site-role;
        description
          "Hub Site in a Hub &amp; Spoke IPVPN.";
      }

      identity pm-type{
       description
           "performance monitor type";

Wen, et al.               Expires March 5, 2017                [Page 36]
Internet-Draft             L2VPN Sevice Model             September 2016

      }

      identity loss {
       base pm-type;
           description
           "loss measurement";
      }

      identity delay {
       base pm-type;
           description
           "delay measurement";
      }

       identity fault-alarm-defect-type {
        description
            "indicating the alarm priority defect";
       }
         identity remote-rdi {
             base fault-alarm-defect-type;
         description
             "Indicates the aggregate health of the remote MEPs.";
         }
         identity remote-mac-error {
         base fault-alarm-defect-type;
             description
             "Indicates that one or more of the remote MEPs is
         reporting a failure in its Port Status TLV or
         Interface Status TLV.";
         }
         identity remote-invalid-ccm {
         base fault-alarm-defect-type;
             description
             "Indicates that at least one of the Remote MEP
         state machines is not receiving valid CCMs
         from its remote MEP.";
         }
         identity invalid-ccm {
         base fault-alarm-defect-type;
             description
             "Indicates that one or more invalid CCMs has been
         received and that 3.5 times that CCMs transmission
         interval has not yet expired.";
         }
         identity cross-connect-ccm {
         base fault-alarm-defect-type;
             description

Wen, et al.               Expires March 5, 2017                [Page 37]
Internet-Draft             L2VPN Sevice Model             September 2016

             "Indicates that one or more cross connect CCMs has been
          received and that 3.5 times of at least one of those
          CCMs transmission interval has not yet expired.";
         }

      /*groupings*/

      grouping customer-info-grouping {
        list customer-info {
          key "customer-account-number customer-name";
          leaf customer-account-number {
            type string;
            description
              "customer account number";
          }
          leaf customer-name {
            type string;
            description
              "customer name";
          }
          container customer-operation-center {
            leaf customer-noc-street-address {
              type string;
              description
                "customer NOC street Address.";
            }
            container customer-noc-phone-number {
              leaf main-phone-num {
                type uint32;
                description
                  "main phone number.";
              }
              leaf extension-options {
                type uint32;
                description
                  "extension or options";
              }

              description
                "configuration of customer noc phone number";
            }
            description
              "configuration of customer operation center";
          }
          description
            "list of customer information";

Wen, et al.               Expires March 5, 2017                [Page 38]
Internet-Draft             L2VPN Sevice Model             September 2016

        }
        description
          "grouping for customer information";
      }

      grouping topology-grouping{
        leaf topology {
           type identityref {
             base vpn-topology;
           }
           default "any-to-any";
           description
             "VPN topology.";
        }
        description
          "grouping for topology parameters";
      }

      grouping vpn-service-mpls {
        leaf carrierscarrier {
          if-feature carrierscarrier;
          type boolean;
          default false;
          description
            "The VPN is using Carrier&apos;s Carrier,
             and so MPLS is required.";
        }
        description
          "grouping for mpls CsC definition";
      }

      grouping site-management {
        container management {
          leaf site-name {
            type string;
            description
              "site name";
          }
          leaf address {
            type inet:ip-address;

            description
            "address";
          }
          leaf ce-device-info {
            type string;
            description

Wen, et al.               Expires March 5, 2017                [Page 39]
Internet-Draft             L2VPN Sevice Model             September 2016

              "CE device info";
          }
          leaf type {
            type identityref {
              base management;
            }
            description
              "Management type of the connection.";
          }
          leaf management-transport {
            type identityref {
              base address-family;
            }
            description
              "Transport protocol used for management.";
          }
          description
            "Management configuration";
        }
        description
          "Management parameters for the site.";
      }

      grouping customer-location-info {
        container location {
          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.";

Wen, et al.               Expires March 5, 2017                [Page 40]
Internet-Draft             L2VPN Sevice Model             September 2016

          }
          leaf country-code {
            type string;
            description
              "Country of the site.";
          }
          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{

           leaf svlan-id-ethernet-tag {
                     type string;
             description
               "SVLAN-ID/Ethernet Tag configurations";
           }

Wen, et al.               Expires March 5, 2017                [Page 41]
Internet-Draft             L2VPN Sevice Model             September 2016

           list cvlan-id-to-evc-map {
                     key map-id;
               leaf map-id {
                 type string;
                 description
                   "Group-id the site is belonging to";
                 }
             description
               "List of CVLAN-ID to EVC Map configurations";
           }
           leaf service-level-mac-limit {
                   type string;
             description
               "Service-level MAC-limit (E-LAN only)";
           }
          /* container service-level {
             leaf cos-identifier {
               type string;
               description
                 "COS Identifier [ EVC | EVC + PCP ]";
             }
             leaf color-identifier {
               type string;
               description
                 "Color Identifier [ EVC | EVC + CVLAN ]";
             }
             leaf ingress-bw-profile-per-evc {
               type string;
               description
                 "Ingress Bandwidth Profile per EVC";
             }
             leaf ingress-bw-profile-per-cos-id {
               type string;
               description
                 "Ingress Bandwidth Profile per COS Identifier";
             }
             leaf egress-bw-profile-per-evc {
               type string;
               description
                 "Egress Bandwidth Profile per EVC";
             }
             leaf egress-bw-profile-per-cos-id {
               type string;
               description
                 "Egress Bandwidth Profile per COS Identifier";
             }
                     leaf byte-offset{
                       type uint16;

Wen, et al.               Expires March 5, 2017                [Page 42]
Internet-Draft             L2VPN Sevice Model             September 2016

                           description
                           "For not including extra VLAN tags in
                            the QoS calculation";
                     }
             leaf COS{
               type uint32;
               description
                 "Class of Service";
             }
             description
               "Container of service level configurations.";

           } */

         description
           "This grouping defines site service parameters";
       }

       grouping service-protection{
         container service-protection {
           container protection-model {
             description
               "Container of protection model configurations";
           }
           container peer-evc-id {
             description
               "Container of peer evc id configurations";
           }
           description
             "Container of End-to-end Service Protection
             configurations";
         }
         description
           "Grouping for service protection";
       }

       grouping ethernet-service-type {
         choice ethernet-svc-type {
           case e-line {
             leaf epl {
               type boolean;
               description
                 "Ethernet private line";
             }
             leaf evpl {
               type boolean;

Wen, et al.               Expires March 5, 2017                [Page 43]
Internet-Draft             L2VPN Sevice Model             September 2016

               description
                 "Ethernet virtual private line";
             }
             description
               "Case of e-line";
           }
           case e-lan {
             leaf ep-lan {
               type boolean;
               description
                 "Ethernet private LAN";
             }
             leaf evp-lan {

               type boolean;
               description
                 "Ethernet virtual private lan";
             }
             description
               "Case of e-lan";
           }
           case e-access {
             leaf access-epl {
               type boolean;
               description
                 "Access ethernet virtual private line";
             }
             leaf access-evpl {
               type boolean;
               description
                 "Access ethernet virtual private line";
             }
             description
               "Case of e-access.";
           }
           description
             "Choice of ethernet service type";
         }
         description
           "Grouping for ethernet service type.";
       }

       grouping signaling-option-grouping {
         list signaling-option {
           key "name type";
           leaf name {

Wen, et al.               Expires March 5, 2017                [Page 44]
Internet-Draft             L2VPN Sevice Model             September 2016

             type string;
             description
               "VRF/VFI/EVI Name";
           }
           leaf type {
             type identityref {
               base vpn-signaling-type;
             }
             description
               "VPN signaling types";
           }
           container mp-bgp-l2vpn {
               leaf vpn-id {
                 type string;
                 description
                   "Identifies the target VPN";
               }
               leaf type {
                 type identityref {
                   base l2vpn-type;
                 }
                 description
                   "L2VPN types";
               }
             description
             "Container for mp bgp l2vpn";
           }

           container mp-bgp-evpn {
               leaf vpn-id {
                 type string;
                 description
                   "Identifies the target VPN";
               }
               leaf type {
                 type identityref {
                   base l2vpn-type;
                 }
                 description
                   "L2VPN types";
               }
             description
             "Container for mp bgp l2vpn";
           }

           container t-ldp-pwe {
             list PE-EG-list {
               key "service-ip-lo-addr vc-id";

Wen, et al.               Expires March 5, 2017                [Page 45]
Internet-Draft             L2VPN Sevice Model             September 2016

               leaf service-ip-lo-addr {
                 type inet:ip-address;
                 description
                   "Service ip lo address";
               }
               leaf vc-id {
                 type string;
                 description
                 "VC id";
               }
               description
                 "List of PE/EG";
             }
             description
               "Container of T-LDP PWE configurations";

           }
                   container pwe-encapsulation-type {
               leaf ethernet {
                 type boolean;
                 description
                   "Ethernet";
               }
               leaf vlan {
                 type boolean;
                 description
                   "VLAN";
               }
               description
               "Container of PWE Encapsulation Type configurations";
             }
            container pwe-mtu {
               leaf allow-mtu-mismatch {
                 type boolean;
                 description
                   "Allow MTU mismatch";
               }
               description
               "Container of PWE MTU configurations";
             }
                   container control-word {
               description
                 "Container of control word configurations";
             }
           description
             "List of VPN Signaling Option.";
         }
         description

Wen, et al.               Expires March 5, 2017                [Page 46]
Internet-Draft             L2VPN Sevice Model             September 2016

           "Grouping for signaling option";
       }

               grouping load-balance-grouping{
             container load-balance-option {
               leaf fat-pw {
                 type boolean;
                 description
                   "Fat label is applied to Pseudowires
                    across MPLS network";
               }
               leaf entropy-label {
                 type boolean;
                 description
                   "Entropy label is applied to IP forwarding,
                    L2VPN or L3VPN across MPLS network";
               }
               description
                 "Container of load balance option";
             }
                     description
                     "grouping for load balance ";
           }

      grouping intra-mkt-grouping {
        list intra-mkt {
          key "metro-mkt-id mkt-name";
          leaf metro-mkt-id {
            type uint32;
            description
              "Metro MKT ID";
          }
          leaf mkt-name {
            type string;
            description
              "MKT Name";
          }
          description
            "List of intra-MKT";
        }
        description
          "Grouping for intra-MKT";
      }

      grouping oam-service{
             container Ethernet-Service-OAM {
            list uni-n2-uni-n {
              key "MD-name MD-level";

Wen, et al.               Expires March 5, 2017                [Page 47]
Internet-Draft             L2VPN Sevice Model             September 2016

              leaf MD-name{
                       type string;
                           description
                           "Maintenance domain name";
                      }
                      leaf MD-level {
                       type uint8;
                           description
                           "Maintenance domain level";
                      }

                       leaf alarm-priority-defect {
                type identityref{
                            base fault-alarm-defect-type;
                            }
                description
                "The lowest priority defect that is
                            allowed to generate a Fault Alarm.
                            The non-existence of this leaf means
                            that no defects are to be reported";
                           }

              description
               "List of UNI-N to UNI-N";
            }
          description
            "Container for ehternet service oam";
        }
            description
            "grouping for oam service.";
      }
      grouping inter-mkt-service {
        leaf inter-mkt-service{
             type boolean;
             description
             "indicate whether service is inter market service.";
            }
        description
          "Grouping for inter-MKT service";
      }

      grouping evc-id-grouping {
        leaf evc-id {
          type boolean;
          description
            "Ethernet Virtual Connection identifier";
        }
        description

Wen, et al.               Expires March 5, 2017                [Page 48]
Internet-Draft             L2VPN Sevice Model             September 2016

          "Grouping for EVC-ID";
      }

      grouping svc-type-grouping {
        container svc-type {
          container evc {
            leaf evc-id {
              type boolean;
              description
                "Indicate whether the Ethernet virtual connection
                 id support.";
            }
            description
              "container for ethernet virtual connection";
          }
          container ovc {
                leaf on-net-ovc-id {
                  type boolean;
                  description
                    "Indicate whether the on net ovc id support.";
                }

                leaf off-net-ov-id {
                  type boolean;
                  description
                    "Indicate whether the off net ovc id support.";
                }
                            description
                            "container for ovc";
              }
              description
          "Container for servic types";
          }
        description
          "Grouping of service types.";
        }

      grouping cfm-802-grouping {
        leaf MAID {
          type string;
          description
            "MA ID";
        }
        leaf mep-level {
          type uint32;
          description
            "MEP level";
        }

Wen, et al.               Expires March 5, 2017                [Page 49]
Internet-Draft             L2VPN Sevice Model             September 2016

        leaf mep-up-down {
          type enumeration {
            enum up {
              description
                "MEP up";
            }
            enum down {
              description
                "MEP down";
            }
          }
          description
            "MEP up/down";
        }
        leaf remote-mep-id {
          type uint32;
          description
            "Remote mep id";
        }
        leaf cos-for-cfm-pdus {
          type uint32;
          description
            "COS for CFM PDUs";
        }
        leaf ccm-interval {
          type uint32;
          description
            "CCM interval";
        }
        leaf ccm-holdtime {
          type uint32;
          description
            "CCM hold time";
        }
            leaf alarm-priority-defect {
          type identityref{
               base fault-alarm-defect-type;
              }
          description
          "The lowest priority defect that is
           allowed to generate a Fault Alarm.
               The non-existence of this leaf means
               that no defects are to be reported";
            }
        description
          "Grouping for 802.1ag CFM attribute";
      }

Wen, et al.               Expires March 5, 2017                [Page 50]
Internet-Draft             L2VPN Sevice Model             September 2016

      grouping enni-site-info-grouping {
        container site-info {
          leaf site-name {
            type string;
            description
              "Site name";
          }
          leaf address {
            type inet:ip-address;
            description
              "Address";
          }
          leaf Edge-Gateway-Device-Info {
            type string;
            description
              "Edge Gateway Device Info ";
          }
          description
            "Container of site info configurations";
        }
        description
          "Grouping for site information";
      }

      grouping site-security-authentication {
        container authentication {
          description
            "Authentication parameters";
        }
        description
          "This grouping defines authentication parameters
           for a site";
      }

      grouping site-security-encryption {
        container encryption {
          if-feature encryption;
          leaf enabled {
            type boolean;
            description
              "If true, access encryption is required.";
          }
          leaf layer {
            type enumeration {

              enum layer2 {
                description
                  "Encryption will occur at layer2.";

Wen, et al.               Expires March 5, 2017                [Page 51]
Internet-Draft             L2VPN Sevice Model             September 2016

              }
              enum layer3 {
                description
                  "IPSec is requested.";
              }
            }
            description
              "Layer on which encryption is applied.";
          }
          container encryption-profile {
            choice profile {
              case provider-profile {
                leaf profile-name {
                  type string;
                  description
                    "Name of the SP profile to be applied.";
                }
              }
              case customer-profile {
                leaf algorithm {
                  type string;
                  description
                    "Encryption algorithm to be used.";
                }
                choice key-type {
                  case psk {
                    leaf preshared-key {
                      type string;
                      description
                        "Key coming from customer.";
                    }
                  }
                  case pki {
                  }
                  description
                    "Type of keys to be used.";
                }
              }
              description
                "Choice of profile.";
            }
            description
              "Profile of encryption to be applied.";
          }
          description

            "Encryption parameters.";
        }

Wen, et al.               Expires March 5, 2017                [Page 52]
Internet-Draft             L2VPN Sevice Model             September 2016

        description
          "This grouping defines encryption parameters
           for a site";
      }

      grouping site-security {
        container security {
          uses site-security-authentication;
          uses site-security-encryption;
          description
            "Site specific security parameters.";
        }
        description
          "Grouping for security parameters.";
      }

      grouping port-info-grouping {
        container bearer {
          container phy-interface {
            leaf port-number {
              type uint32;
              description
                "Port number";
            }
            leaf port-speed {
              type uint32;
              description
                "Port speed";
            }
            leaf auto-neg {
              type string;
              description
                "Auto neg";
            }
            leaf phy-mtu {
              type uint32;
              description
               "PHY MTU";
            }
            leaf flow-control {
              type string;
              description
                "Flow control";
            }
            leaf encapsulation-type {
              type enumeration {
                enum VLAN {
                  description

Wen, et al.               Expires March 5, 2017                [Page 53]
Internet-Draft             L2VPN Sevice Model             September 2016

                    "VLAN";
                }
                enum Ethernet {
                  description
                    "Ethernet";
                }
              }
              description
                "Encapsulation-type";
            }
            leaf ethertype {
              type string;
              description
                "Ethertype";
            }
            leaf lldp {
              type string;
              description
                "LLDP";
            }
            leaf oam-802.3AH-link {
              type string;
              description
                "802.3AH-link-OAM";
            }
                    leaf uni-loop-prevention{
                      type boolean;
                      description
                      "if this leaf set to truth that
                      the port automatically goes down when
                      a physical loopback is detect.";
                    }
            description
              "Container of PHY Interface Attributes configurations";
          }
          container LAG-interface {
            list LAG-interface {
              key "LAG-interface-number";
              leaf LAG-interface-number {
                type uint32;
                description
                  "LAG interface number";
              }
              container LACP {
                leaf LACP-on-off {
                  type enumeration {
                    enum on{
                      description

Wen, et al.               Expires March 5, 2017                [Page 54]
Internet-Draft             L2VPN Sevice Model             September 2016

                       "LACP ON";
                    }
                    enum off{
                      description
                       "LACP OFF";
                    }
                  }
                  description
                    "LACP on/off";
                }
                leaf LACP-mode {
                  type enumeration {
                    enum active {
                    description
                      "Active mode";
                  }
                  enum passive {
                    description
                      "Passive mode";
                  }
                }
                description
                  "LACP mode";
              }
              leaf LACP-speed {
                type enumeration {
                  enum fast {
                    description
                      "Fast";
                  }
                  enum slow {
                    description
                      "Slow";
                  }
                }
                description
                  "LACP speed";
              }
              leaf mini-link {
                type uint32;
                description
                  "Mini link";
              }
                      leaf system-priority{
                       type uint32;
                           description
                           "indicates the LACP priority for the system.
                           The range is from 0 to 65535.

Wen, et al.               Expires March 5, 2017                [Page 55]
Internet-Draft             L2VPN Sevice Model             September 2016

                           The default is 32768.";
                      }
              container Micro-BFD {
                leaf Micro-BFD-on-off {
                  type enumeration {
                    enum on {
                      description
                        "Micro-bfd on";
                    }
                    enum off {
                      description
                        "Micro-bfd off";
                    }
                  }
                  description
                    "Micro BFD ON/OFF";
                }
                leaf bfd-interval {
                  type uint32;
                  description
                    "BFD interval";
                }
                leaf bfd-hold-timer {
                  type uint32;
                  description
                  "BFD hold timer";
                }
                description
                "Container of Micro-BFD configurations";
              }
              container Member-link-list {
                list member-link {
                  key "name";
                  leaf name {
                    type string;
                    description
                      "Member link name";
                  }
                  leaf port-speed {
                    type uint32;
                    description
                      "Port speed";
                  }
                  leaf auto-neg {
                    type string;
                    description
                      "Auto neg";
                  }

Wen, et al.               Expires March 5, 2017                [Page 56]
Internet-Draft             L2VPN Sevice Model             September 2016

                  leaf mtu {
                    type uint32;
                    description
                      "MTU";
                  }
                  leaf oam-802.3AH-link {
                    type string;
                    description
                      "802.3AH-link-OAM";
                  }
                  description
                    "Member link";
                }
                description
                  "Container of Member link list";
              }
              leaf flow-control {
                type string;
                description
                  "Flow control";
              }
              leaf encapsulation-type {
                type enumeration {
                  enum VLAN {
                    description
                      "VLAN";
                  }
                  enum ether {
                    description
                      "Ether";
                  }
                }
                description
                  "Encapsulation type";
              }
              leaf ethertype {
                type string;
                description
                  "Ether type";
              }
              leaf lldp {
                type string;
                description
                  "LLDP";
              }
              description
                "LACP";
            }

Wen, et al.               Expires March 5, 2017                [Page 57]
Internet-Draft             L2VPN Sevice Model             September 2016

            description
              "List of LAG interfaces";
          }
          description
            "Container of LAG interface attributes configuration";
        }
        leaf interface-description {
          type string;
          description
            "Interface description";
        }
        leaf sub-if-id {
          type uint32;
          description
            "Sub-if id";
        }

        description
          "Container for bearer";
      }
      container ethernet-connection {
          container vlan {
                leaf svlan-id-ethernet-tag {
                     type string;
             description
               "SVLAN-ID/Ethernet Tag configurations";
           }
           list cvlan-id-to-evc-map {
                     key map-id;
               leaf map-id {
                 type string;
                 description
                   "Group-id the site is belonging to";
                 }
             description
               "List of CVLAN-ID to EVC Map configurations";
           }
            description
              "Abstract container for vlan";
          }
          container oam {
                  leaf MD-name{
                       type string;
                           description
                           "Maintenance domain name";
                      }
                      leaf MD-level {
                       type uint8;

Wen, et al.               Expires March 5, 2017                [Page 58]
Internet-Draft             L2VPN Sevice Model             September 2016

                           description
                           "Maintenance domain level";
                      }
            description
              "Abstract container for oam";
          }
          description
            "Container for ethernet connection";
      }
      leaf evc-mtu {
        type uint32;
        description
          "EVC MTU";
      }
      container mac-addr-limit {
        leaf exceeding-option {
          type uint32;
          description
            "Exceeding option";
        }
        description
          "Container of MAC-Addr limit configurations";
      }
      container S-vlan {
        leaf c-vlan2evc-mapping {
          type string;
          description
            "C-VLAN to EVC mapping";
        }
        description
          "Container of S-VLAN configurations";
      }
      container multihoming {
        list multihoming {
          key "ESI";
          leaf ESI{
            type string;
            description
              "Ethernet segment id";
          }
          choice redundancy-mode {
            case single-active {
              leaf single-active {
                type boolean;
                description
                  "Single active";
              }
              description

Wen, et al.               Expires March 5, 2017                [Page 59]
Internet-Draft             L2VPN Sevice Model             September 2016

                "Single active case";
            }
            case all-active {
              leaf all-active {
                type boolean;
                description
                  "All active";
              }
              description
                "All active case";
            }
            description
              "Redundancy mode";
          }
          description
            "List of multihomings";
        }
        description
          "Container of multihoming optional configurations";
      }
      container L2CP-control {
        leaf stp-rstp-mstp {
          type control-mode;
          description
            "STP/RSTP/MSTP";
        }
        leaf pause {
          type control-mode;
          description
            "Pause";
        }
        leaf lacp-lamp {
          type control-mode;
          description
            "LACP/LAMP";
        }
        leaf link-oam {
          type control-mode;
          description
            "Link OAM";
        }
        leaf esmc {
          type control-mode;
          description
            "ESMC";
        }
        leaf l2cp-802.1x {
          type control-mode;

Wen, et al.               Expires March 5, 2017                [Page 60]
Internet-Draft             L2VPN Sevice Model             September 2016

          description
            "802.x";
        }
        leaf e-lmi {
          type control-mode;
          description
            "E-LMI";
        }
        leaf lldp {
          type control-mode;
          description
            "LLDP";
        }
        leaf ptp-peer-delay {
          type control-mode;
          description
            "PTP peer delay";
        }
        leaf garp-mrp {
          type control-mode;
          description
            "GARP/MARP";
        }
            leaf provider-bridge-group{
              type yang:mac-address;
              description
              "provider bridge group reserved MAC address
              01-80-C2-00-00-08";
            }
            leaf provider-bridge-mvrp{
              type yang:mac-address;
              description
              "provider bridge mvrp reserved MAC address
              01-80-C2-00-00-0D";
            }
        description
          "Container of L2CP control configurations";
      }
      container service{
      uses site-service;
      description
      "container for site service.";
                     container service-level {
             leaf cos-identifier {
               type string;
               description
                 "COS Identifier [ EVC | EVC + PCP ]";
             }

Wen, et al.               Expires March 5, 2017                [Page 61]
Internet-Draft             L2VPN Sevice Model             September 2016

             leaf color-identifier {
               type string;
               description
                 "Color Identifier [ EVC | EVC + CVLAN ]";
             }
             leaf ingress-bw-profile-per-evc {
               type string;
               description
                 "Ingress Bandwidth Profile per EVC";
             }
             leaf ingress-bw-profile-per-cos-id {
               type string;
               description
                 "Ingress Bandwidth Profile per COS Identifier";
             }
             leaf egress-bw-profile-per-evc {
               type string;
               description
                 "Egress Bandwidth Profile per EVC";
             }
             leaf egress-bw-profile-per-cos-id {
               type string;
               description
                 "Egress Bandwidth Profile per COS Identifier";
             }
                     leaf byte-offset{
                       type uint16;
                           description
                           "For not including extra VLAN tags in
                            the QoS calculation";
                     }

             leaf COS{
               type uint32;
               description
                 "Class of Service";
             }
             description
               "Container of service level configurations.";
           }
      }
      container B-U-M-strom-control {
        description
          "Container of B-U-M-strom-control configurations";
      }
      container mac-loop-prevention{
       description
           "container of mac loop prevention.";

Wen, et al.               Expires March 5, 2017                [Page 62]
Internet-Draft             L2VPN Sevice Model             September 2016

      }
        container Ethernet-Service-OAM {
          container cfm-802.1-ag {
            list uni-n2uni-c {
              key "MAID";
              uses cfm-802-grouping;
              description
                "List of NUI-N to NUI-C";
            }
            list uni-n2-uni-n {

              key "MAID";
              uses cfm-802-grouping;
              description
               "List of UNI-N to UNI-N";
            }
            description
              "Container of 802.1ag CFM configurations";
          }
          list y-1731 {
            key MAID;
            leaf MAID {
              type string;
              description
                "MA ID ";
            }
                    leaf type {
                     type identityref{
                      base pm-type;
                     }
                     description
                     "performance monitor types";
                    }
                    leaf remote-mep-id {
                     type uint32;
                     description
                     "remote mep identifier";
                    }
                    leaf measurement-interval{
                     type uint32;
                     description
                     "measurement interval";
                    }
                    leaf cos {
                     type uint32;
                     description
                     "class of service";
                    }

Wen, et al.               Expires March 5, 2017                [Page 63]
Internet-Draft             L2VPN Sevice Model             September 2016

                    leaf frame-size{
                     type uint32;
                     description
                     "frame size";
                    }
            description
              "List for y-1731.";
          }
          description
            "Container for ehternet service oam";
        }
        container security {
          uses site-security;
          description
            "Container of security configurations";
        }
        //uses site-attachment-availability;
        description
          "Grouping for port info";
      }

    /*  grouping site-attachment-availability {
        container availability {
          leaf access-priority {
            type uint32;
            default 1;
            description
              "Defines the priority for the access. The highest the
               priority value is, the highest the preference of the
               access is.";
          }
          description
            "Availability parameters (used for multihoming)";
        }
        description
          "Defines site availability parameters.";
      }*/

      /* MAIN L2VPN SERVICE */
      container l2vpn-svc {

        /* CUSTOMER */
        container customer-info {
          uses customer-info-grouping;
          description
            "Container of customer information configurations";
        }

Wen, et al.               Expires March 5, 2017                [Page 64]
Internet-Draft             L2VPN Sevice Model             September 2016

        /* SERVICE */
        container vpn-services {
          list vpn-svc {
            key "svc-id";
            leaf svc-id {
              type string;
              description
                "Defining a service id.";
            }
            uses svc-type-grouping;
               /* list uni{
                key uni-id;
                leaf uni-id{
                 type leafref{
                  path "/l2vpn-svc/site/uni-sites/uni-site/site-id";
                 }
                 description
                 "uni id";
                }
                description
                "list of uni";
               } */

            container ethernet-svc-type {
              uses ethernet-service-type;
              description
                "Container of ethernet service type";
            }
            container metro-network-id {
                      uses inter-mkt-service;
              uses intra-mkt-grouping;
              description
                "Container of Metro-Network ID configurations";
            }
                    container signaling-option {
              uses signaling-option-grouping;
              description
              "Container for signaling option";
            }
                    uses load-balance-grouping;
                    uses site-service;
            /* container Ethernet-Service-OAM {
            list uni-n2-uni-n {
              key "MD-name MD-level";
              leaf MD-name{
                       type string;
                           description
                           "Maintenance domain name";

Wen, et al.               Expires March 5, 2017                [Page 65]
Internet-Draft             L2VPN Sevice Model             September 2016

                      }
                      leaf MD-level {
                       type uint8;
                           description
                           "Maintenance domain level";
                      }
              description
               "List of UNI-N to UNI-N";
            }
          description
            "Container for ehternet service oam";
        } */
                uses service-protection;
            //uses topology-grouping;
            //uses vpn-service-mpls;
            description
              "List of vpn-svc";
          }
          description
            "Container of vpn-services configurations";
        }

        /* SITE */
        container site {
          container uni-sites {
            list uni-site {
              key "site-id";
              leaf site-id {
                type string;
                description
                  "Container of site id";
              }
              uses site-management;
              uses customer-location-info;
              uses site-diversity;

              uses site-security;

                      /*container service{
              uses site-service;

                       description
                           "container for site service.";
                           uses oam-service;
                      } */
              //uses service-protection;
              container signaling-option {
                uses signaling-option-grouping;

Wen, et al.               Expires March 5, 2017                [Page 66]
Internet-Draft             L2VPN Sevice Model             September 2016

                description
                  "Container for signaling option";
              }
                      uses load-balance-grouping;
              container uni-ports {
                list uni-port {
                  key "uni-id";
                  leaf uni-id {
                    type string;
                    description
                      "UNI id";
                  }
                  uses port-info-grouping;
                  description
                    "List of uni ports";
                }
                description
                  "Container of uni port configurations";
              }
              description
                "List of uni sites";
            }
            description
              "Container of uni site configurations";
          }
          container enni-sites {
            list enni-site {
              key "site-id";
              leaf site-id {
                type string;
                description
                  "Container of site id";
              }
              uses customer-location-info;
              uses site-diversity;
              container management {
                leaf site-name {
                  type string;
                  description
                    "Site name";
                }
                leaf address {
                  type inet:ip-address;
                  description
                    "Address";
                }
                leaf Edge-Gateway-Device-Info {
                  type string;

Wen, et al.               Expires March 5, 2017                [Page 67]
Internet-Draft             L2VPN Sevice Model             September 2016

                  description
                    "Edge Gateway Device Information";
                }
                leaf type {
                  type identityref {
                    base management;
                  }
                  description
                    "Management type of the connection.";
                }
                leaf management-transport {
                  type identityref {
                    base address-family;
                  }
                  description
                    "Transport protocol used for management.";
                }
                description
                  "Management configuration";
              }

                uses site-security;
              uses service-protection;
              container signaling-option {
                uses signaling-option-grouping;
                description
                  "Container for signaling option";
              }
                      uses load-balance-grouping;
              container enni-ports {
                list enni-port {
                  key "enni-id";
                  leaf enni-id {
                    type string;
                    description
                    "ENNI id";
                  }
                              leaf remote-carrier-name{
                               type string;
                                   description
                                   "remote carrier name";
                              }
                  uses port-info-grouping;
                  description
                    "List of enni ports";
                }
                description
                  "Container of ENNI port configurations";

Wen, et al.               Expires March 5, 2017                [Page 68]
Internet-Draft             L2VPN Sevice Model             September 2016

              }
              description
                "List of ENNI sites";
            }
            description
              "Container of ENNI site configurations";
          }
          description
           "Container for site configurations";
        }
        description
          "Container of l2vpn-svc configurations";
      }
      }
   <CODE ENDS>

9.  Security Considerations

   The YANG modules defined in this document MAY be accessed via the
   RESTCONF protocol [I-D.ietf-netconf-restconf] or NETCONF protocol
   ([RFC6241].  The lowest RESTCONF or NETCONF layer requires that the
   transport-layer protocol provides both data integrity and
   confidentiality, see Section 2 in [I-D.ietf-netconf-restconf] and
   [RFC6241].  The client MUST carefully examine the certificate
   presented by the server to determine if it meets the client's
   expectations, and the server MUST authenticate client access to any
   protected resource.  The client identity derived from the
   authentication mechanism used is subject to the NETCONF Access
   Control Module (NACM) ([RFC6536]).  Other protocols to access this
   YANG module are also required to support the similar mechanism.

   The data nodes defined in the "ietf-l2vpn-svc" YANG module MUST be
   carefully created/read/updated/deleted.  The entries in the lists
   below include customer proprietary or confidential information,
   therefore only authorized clients MUST access the information and the
   other clients MUST NOT be able to access to the information.

   o  /l2vpn-svc/vpn-services/vpn-svc

   o  /l2vpn-svc/sites/uni-site

   o  /l2vpn-svc/sites/enni-site

Wen, et al.               Expires March 5, 2017                [Page 69]
Internet-Draft             L2VPN Sevice Model             September 2016

10.  Acknowledgements

   Thanks to Qin Wu and Adrian Farrel for facilitating work on the
   initial revision of this document.

   This document has drawn on the work of the L3SM Workng Group
   expressed in [I-D.ietf-l3sm-l3vpn-service-model].

11.  IANA Considerations

   IANA is requested to assign a new URI from the IETF XML registry
   ([RFC3688]).  The following URI is suggested:

       URI: urn:ietf:params:xml:ns:yang:ietf-l2vpn-svc
       Registrant Contact: L2SM WG
       XML: N/A, the requested URI is an XML namespace

   This document also requests a new YANG module name in the YANG Module
   Names registry ([RFC6020]) with the following suggestion:

       name: ietf-l2vpn-svc
       namespace: urn:ietf:params:xml:ns:yang:ietf-l2vpn-svc
       prefix: l2vpn-svc
       reference: RFC XXXX

12.  References

12.1.  Normative References

   [I-D.ietf-netconf-restconf]
              Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", draft-ietf-netconf-restconf-16 (work in
              progress), August 2016.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", March 1997.

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

Wen, et al.               Expires March 5, 2017                [Page 70]
Internet-Draft             L2VPN Sevice Model             September 2016

   [RFC4448]  Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron,
              "Encapsulation Methods for Transport of Ethernet over MPLS
              Networks", RFC 4448, DOI 10.17487/RFC4448, April 2006,
              <http://www.rfc-editor.org/info/rfc4448>.

   [RFC4761]  Kompella, K., Ed. and Y. Rekhter, Ed., "Virtual Private
              LAN Service (VPLS) Using BGP for Auto-Discovery and
              Signaling", RFC 4761, DOI 10.17487/RFC4761, January 2007,
              <http://www.rfc-editor.org/info/rfc4761>.

   [RFC4762]  Lasserre, M., Ed. and V. Kompella, Ed., "Virtual Private
              LAN Service (VPLS) Using Label Distribution Protocol (LDP)
              Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007,
              <http://www.rfc-editor.org/info/rfc4762>.

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

   [RFC6536]  Bierman, A. and M. Bjorklund, "Network Configuration
              Protocol (NETCONF) Access Control Model", RFC 6536,
              DOI 10.17487/RFC6536, March 2012,
              <http://www.rfc-editor.org/info/rfc6536>.

   [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, <http://www.rfc-editor.org/info/rfc7432>.

12.2.  Informative References

   [I-D.ietf-l3sm-l3vpn-service-model]
              Litkowski, S., Shakir, R., Tomotaki, L., Ogaki, K., and K.
              D'Souza, "YANG Data Model for L3VPN service delivery",
              draft-ietf-l3sm-l3vpn-service-model-12 (work in progress),
              July 2016.

   [I-D.wu-opsawg-service-model-explained]
              Wu, Q., (Will), S., and A. Farrel, "Service Models
              Explained", draft-wu-opsawg-service-model-explained-01
              (work in progress), July 2016.

Wen, et al.               Expires March 5, 2017                [Page 71]
Internet-Draft             L2VPN Sevice Model             September 2016

   [RFC6624]  Kompella, K., Kothari, B., and R. Cherukuri, "Layer 2
              Virtual Private Networks Using BGP for Auto-Discovery and
              Signaling", RFC 6624, DOI 10.17487/RFC6624, May 2012,
              <http://www.rfc-editor.org/info/rfc6624>.

Authors' Addresses

   Bin Wen
   Comcast

   Email: Bin_Wen@comcast.com

   Giuseppe Fioccola
   Telecom Italia

   Email: giuseppe.fioccola@telecomitalia.it

   Chongfeng Xie
   China Telecom

   Email: xiechf@ctbri.com.cn

   Luay Jalil
   Verizon

   Email: luay.jalil@verizon.com

Wen, et al.               Expires March 5, 2017                [Page 72]