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

Document Type Active Internet-Draft (opsawg WG)
Last updated 2019-11-17
Replaces draft-aguado-opsawg-l3sm-l3nm
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Yang Validation 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-l3vpn-ntw@2019-11-17.yang
- Yang impact analysis for draft-ietf-opsawg-l3sm-l3nm
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
OPSAWG                                                         A. Aguado
Internet-Draft                                                     Nokia
Intended status: Standards Track                O. Gonzalez de Dios, Ed.
Expires: May 20, 2020                                           V. Lopez
                                                              Telefonica
                                                                D. Voyer
                                                             Bell Canada
                                                                L. Munoz
                                                                Vodafone
                                                       November 17, 2019

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

Abstract

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

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

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

Editorial Note (To be removed by RFC Editor)

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

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

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

   o  reference: RFC XXXX

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

Aguado, et al.            Expires May 20, 2020                  [Page 1]
Internet-Draft                    l3nm                     November 2019

Status of This Memo

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

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

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

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

Copyright Notice

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

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   5
   2.  Reference Architecture  . . . . . . . . . . . . . . . . . . .   6
   3.  Description of the L3NM YANG Module . . . . . . . . . . . . .   8
     3.1.  Structure of the Module . . . . . . . . . . . . . . . . .   9
     3.2.  Modeling a L3 VPN Service . . . . . . . . . . . . . . . .   9
       3.2.1.  VPN node  . . . . . . . . . . . . . . . . . . . . . .  10
         3.2.1.1.  VPN Network Access  . . . . . . . . . . . . . . .  11
           3.2.1.1.1.  Connection  . . . . . . . . . . . . . . . . .  11
           3.2.1.1.2.  IP Connection . . . . . . . . . . . . . . . .  13
           3.2.1.1.3.  Routing Protocols . . . . . . . . . . . . . .  14
       3.2.2.  Concept of Import/Export Profiles . . . . . . . . . .  15
       3.2.3.  Multicast . . . . . . . . . . . . . . . . . . . . . .  16

Aguado, et al.            Expires May 20, 2020                  [Page 2]
Internet-Draft                    l3nm                     November 2019

     3.3.  VPN profiles  . . . . . . . . . . . . . . . . . . . . . .  16
     3.4.  Model tree  . . . . . . . . . . . . . . . . . . . . . . .  17
   4.  Use of the Data Model . . . . . . . . . . . . . . . . . . . .  23
     4.1.  Multi-Domain Resource Management  . . . . . . . . . . . .  23
   5.  Relation with other Yang Models . . . . . . . . . . . . . . .  23
     5.1.  Relation with L3SM  . . . . . . . . . . . . . . . . . . .  23
     5.2.  Relation with Network Topology  . . . . . . . . . . . . .  24
     5.3.  Relation with Device Models . . . . . . . . . . . . . . .  24
   6.  L3VPN  Examples . . . . . . . . . . . . . . . . . . . . . . .  24
     6.1.  4G VPN Provissioning Example  . . . . . . . . . . . . . .  24
   7.  Yang Module . . . . . . . . . . . . . . . . . . . . . . . . .  26
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  89
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  90
   10. Implementation Status . . . . . . . . . . . . . . . . . . . .  91
     10.1.  Nokia Implementation . . . . . . . . . . . . . . . . . .  91
     10.2.  Huawei Implementation  . . . . . . . . . . . . . . . . .  92
     10.3.  Infinera Implementation  . . . . . . . . . . . . . . . .  96
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  96
   12. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  96
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  97
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  97
     13.2.  Informative References . . . . . . . . . . . . . . . . .  98
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  99

1.  Introduction

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

   The YANG data model defined in this document is called L3VPN Network
   Model (L3NM).  The L3NM module is aimed at providing a network-
   centric view of L3 VPN Services.  The data model can be used to
   facilitate communication between the service orchestrator (or a
   network operator) and the network controller/orchestrator by allowing
   for more network-centric information to be included.  It enables
   further capabilities, such as resource management or to serve as a
   multi-domain orchestration interface, where logical resources (such
   as route targets or route distinguishers) must be synchronized.

   This document does not obsolete, but uses, the definitions in
   [RFC8299].  These two modules are used for similar objectives but
   with differents scopes and views.

Aguado, et al.            Expires May 20, 2020                  [Page 3]
Internet-Draft                    l3nm                     November 2019

   The L3NM YANG module is initially built with a prune and extend
   approach, taking as a starting points the YANG module described in
   [RFC8299].  Nevertheless, this module is not defined as an augment to
   L3SM because a specific structure is required to meet network-
   oriented L3 needs.

   Some of the information captured in the L3SM can be passed by the
   Orchestrator in the L3NM (e.g., customer) or be used to fed some of
   the L3NM attribute (e.g., actual forwarding policies).  Some of the
   information captured in L3SM may be maintained locally within the
   Orchestrator; which is supposed to maintain a "glue" between a
   Customer view and its network instantiation.

   The L3NM module does not attempt to address all deployment cases
   especially those where the L3VPN connectivity is supported through
   the coordination of different VPNs in different underlying networks.
   More complex deployment scenarios involving the coordination of
   different VPN instances and different technologies to provide end-to-
   end VPN connectivity are addressed by a complementary YANG model
   defined in [I-D.evenwu-opsawg-yang-composed-vpn].

1.1.  Terminology

   This document assumes that the reader is familiar with the contents
   of [RFC6241], [RFC7950], [RFC8299], [RFC8309], and [RFC8453] and uses
   the terminology defined in those documents.

   The meaning of the symbols in tree diagrams is defined in in
   [RFC8340].

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

   This document makes use of the following terms:

   o  L3 VPN Customer Service Model (L3SM): Describes the requirements
      of a L3 VPN that interconnects a set of sites from the point of
      view of the customer.  The customer service model does not provide
      details on the Service Provider Network.  The L3 VPN Customer
      Service model is defined in [RFC8299].

   o  L3 VPN Service Network Model (L3NM): A YANG module that describes
      a VPN Service in the Service Provider Network.  It containts
      information of the Service Provider network and might include
      allocated resources.  It can be used by network controllers to
      manage and control the VPN Service configuration in the Service

Aguado, et al.            Expires May 20, 2020                  [Page 4]
Internet-Draft                    l3nm                     November 2019

      Provider network.  The YANG module can be consumed by a Service
      Orchestrator to request a VPN Service to a Network controller.

   o  Service Orchestrator: A functional entity that interacts with the
      customer of a L3 VPN.  The Service Orchestrator interacts with the
      customer using L3SM.  The Service Orchestrator is responsible of
      the CE-PE attachment circuits, the PE selection, and requesting
      the VPN service to the network controller.

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

   o  VPN node (vpn-node): An abstraction that represents a set of
      policies applied to a PE and that belong to a single VPN service
      (vpn-service).  A vpn-service involves one or more vpn-nodes.  As
      it is an abstraction, the network controller will take on how to
      implement a vpn-node.  For example, typically, in a BGP-based VPN,
      a vpn-node could be mapped into a VRF.

   o  VPN network access (vpn-network-access): An abstraction that
      represents the network interfaces that are associated to a given
      vpn-node.  Traffic coming from the vpn-network-access belongs to
      the VPN.  The attachment circuits (bearers) between CEs and PEs
      are terminated in the vpn-network-access.  A reference to the
      bearer is maintained to allow keeping the link between L3SM and
      L3NM.

   o  VPN Site (vpn-site): A VPN customer's location that is connected
      to the Service Provider network via a CE-PE link, which can access
      at least one VPN [RFC4176].

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

   o  Service Provider (SP) Network: A network able to provide VPN-
      related services.

1.2.  Requirements Language

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

Aguado, et al.            Expires May 20, 2020                  [Page 5]
Internet-Draft                    l3nm                     November 2019

2.  Reference Architecture

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

   Although some deployments may choose to construct a monolithic
   orchestration component (covering both service and network matters),
   this document advocates for a clear separation between service and
   network orchestration components for the sake of better flexibility.
   Such design adheres to the L3VPN reference architecture defined in
   Section 1.3 of [RFC4176].  The above separation relies upon a
   dediciated communication interface between these components and
   appropriate YANG module that reflect network-related information
   (that is hidden to customers).

   The intelligence for translating customer-facing information into
   network-centric one is implementation-specific.

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

Aguado, et al.            Expires May 20, 2020                  [Page 6]
Internet-Draft                    l3nm                     November 2019

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

                          Figure 1: L3SM and L3NM

   The L3SM and L3NM modules may also be set in the context of the ACTN
   architecture [RFC8453].  Figure 2 shows the Customer Network
   Controller (CNC), the Multi-Domain Service Coordinator (MDSC), and
   the Provisioning Network Controller (PNC).  It also shows the
   interfaces between these functional blocks: the CNC-MDSC Interface
   (CMI), the MDSC-PNC Interface (MPI), and the Southbound Interface
   (SBI).

Aguado, et al.            Expires May 20, 2020                  [Page 7]
Internet-Draft                    l3nm                     November 2019

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

              Figure 2: L3SM and L3NM in the Context of ACTN

3.  Description of the L3NM YANG Module

   The L3NM module ('ietf-l3vpn-ntw') is meant to manage L3 VPNs in a
   service provider network.  In particular, the 'ietf-l3vpn-ntw' module
   can be used to create, modify, and retrieve L3VPN Services of a
   network.

Aguado, et al.            Expires May 20, 2020                  [Page 8]
Internet-Draft                    l3nm                     November 2019

3.1.  Structure of the Module

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

   The 'vpn-profiles' container allows the provider to maintain a set of
   commmon VPN profiles that apply to several VPN Services.

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

                                 Figure 3

3.2.  Modeling a L3 VPN Service

   The 'vpn-service' is the data structure that abstracts a VPN Service
   in the Service Provider Network.  Every 'vpn-service' has a unique
   identifier: vpn-id.  Such vpn-id is only meaningful locally within
   the Network controller.  In order to facilitate the recognition of
   the service, a 'customer-name' and a 'description' may be included.
   The topology of the VPN service is expressed in the 'vpn-service-
   topology' leaf.

   A VPN Service is built by adding instances of 'vpn-node' to the 'vpn-
   nodes' container.  The 'vpn-node' is an abstractions that represent a
   set of policies applied to a network node and that belong to a single
   'vpn-service'.  A 'vpn-node' contains 'vpn_network_accesses', which
   are the interfaces involved in the creation of the VPN.  The customer
   sites are connected to the 'vpn_network_accesses'.  Note that, as
   this is a network data model, the information about customers site is
   not needed.  Such information, is relevant in the L3SM model.

Aguado, et al.            Expires May 20, 2020                  [Page 9]
Internet-Draft                    l3nm                     November 2019

        +--rw vpn-service* [vpn-id]
              +--rw vpn-id                  svc-id
              +--rw customer-name?          string
              +--rw vpn-service-topology?   identityref
              +--rw description?            string
              +--rw ie-profiles
              |  ...
              +--rw vpn-nodes
              |   ...
              +--rw multicast

                                 Figure 4

3.2.1.  VPN node

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 10]
Internet-Draft                    l3nm                     November 2019

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

                                 Figure 5

3.2.1.1.  VPN Network Access

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

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

3.2.1.1.1.  Connection

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 11]
Internet-Draft                    l3nm                     November 2019

3.2.1.1.1.1.  Encapsulation options

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

                     +--rw connection
                       +--rw encapsulation-type?   identityref
                         +--rw tagged-interface
                            +--rw type?                identityref
                            +--rw dot1q-vlan-tagged {dot1q}?
                            |  +--rw tag-type?   identityref
                            |  +--rw cvlan-id?   uint16
                            +--rw priority-tagged
                            |  +--rw tag-type?   identityref
                            +--rw qinq {qinq}?
                            |  +--rw tag-type?   identityref
                            |  +--rw svlan-id    uint16
                            |  +--rw cvlan-id    uint16
                            +--rw qinany {qinany}?
                            |  +--rw tag-type?   identityref
                            |  +--rw svlan-id    uint16
                            +--rw vxlan {vxlan}?
                               +--rw vni-id       uint32
                               +--rw peer-mode?   identityref
                               +--rw peer-list* [peer-ip]
                                  +--rw peer-ip    inet:ip-address

                                 Figure 6

3.2.1.1.1.2.  Remote Far End Configuration

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

Aguado, et al.            Expires May 20, 2020                 [Page 12]
Internet-Draft                    l3nm                     November 2019

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

                                 Figure 7

3.2.1.1.1.3.  Bearers

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

3.2.1.1.2.  IP Connection

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 13]
Internet-Draft                    l3nm                     November 2019

                 +--rw ip-connection
                   +--rw ipv4 {ipv4}?
                     +--rw address-allocation-type?   identityref
                       +--rw provider-dhcp
                         ...
                       +--rw dhcp-relay
                         ...
                       +--rw static-addresses
                         +--rw primary-address?   leafref
                       +--rw address* [address-id]
                         ...
                   +--rw ipv6 {ipv6}?
                     +--rw address-allocation-type?   identityref
                       +--rw provider-dhcp
                         ...
                       +--rw dhcp-relay
                         ...
                       +--rw static-addresses
                         +--rw primary-address?  leafref
                         +--rw address* [address-id]
                             ...

                                 Figure 8

3.2.1.1.3.  Routing Protocols

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

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

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

   o  A single BGP process with multiple neighbors running.

Aguado, et al.            Expires May 20, 2020                 [Page 14]
Internet-Draft                    l3nm                     November 2019

   o  A combination of both.

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

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

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

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

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

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

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

3.2.2.  Concept of Import/Export Profiles

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

Aguado, et al.            Expires May 20, 2020                 [Page 15]
Internet-Draft                    l3nm                     November 2019

3.2.3.  Multicast

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

   The model supports a single type of tree (ASM, SSM or bidirectional).

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

3.3.  VPN profiles

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

   +--rw vpn-profiles
    |  +--rw valid-provider-identifiers
    |     +--rw cloud-identifier* [id] {cloud-access}?
    |     |  +--rw id    string
    |     +--rw encryption-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw qos-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw bfd-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw routing-profile-identifier* [id]
    |        +--rw id    string

                                 Figure 9

Aguado, et al.            Expires May 20, 2020                 [Page 16]
Internet-Draft                    l3nm                     November 2019

3.4.  Model tree

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

   module: ietf-l3vpn-ntw
   +--rw l3vpn-ntw
    +--rw vpn-profiles
    |  +--rw valid-provider-identifiers
    |     +--rw cloud-identifier* [id] {cloud-access}?
    |     |  +--rw id    string
    |     +--rw encryption-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw qos-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw bfd-profile-identifier* [id]
    |     |  +--rw id    string
    |     +--rw routing-profile-identifier* [id]
    |        +--rw id    string
    +--rw vpn-services
     +--rw vpn-service* [vpn-id]
        +--rw vpn-id                  svc-id
        +--rw customer-name?          string
        +--rw vpn-service-topology?   identityref
        +--rw description?            string
        +--rw ie-profiles
        |  +--rw ie-profile* [ie-profile-id]
        |     +--rw ie-profile-id    string
        |     +--rw rd?
        |     |       rt-types:route-distinguisher
        |     +--rw vpn-targets
        |        +--rw vpn-target* [route-target]
        |           +--rw route-target
        |           |       rt-types:route-target
        |           +--rw route-target-type
        |                   rt-types:route-target-type
        +--rw vpn-nodes
        |  +--rw vpn-node* [vpn-node-id ne-id]
        |     +--rw vpn-node-id             string
        |     +--rw autonomous-system?      uint32
        |     +--rw description?            string
        |     +--rw ne-id                   string
        |     +--rw router-id?              inet:ip-address
        |     +--rw address-family?         address-family
        |     +--rw node-role?              identityref
        |     +--rw rd?
        |     |       rt-types:route-distinguisher
        |     +--rw vpn-targets

Aguado, et al.            Expires May 20, 2020                 [Page 17]
Internet-Draft                    l3nm                     November 2019

        |     |  +--rw vpn-target* [route-target]
        |     |     +--rw route-target
        |     |     |       rt-types:route-target
        |     |     +--rw route-target-type
        |     |             rt-types:route-target-type
        |     +--rw status
        |     |  +--rw admin-enabled?   boolean
        |     |  +--ro oper-status?     operational-type
        |     +--rw vpn-network-accesses
        |     |  +--rw vpn-network-access*
        |     |          [vpn-network-access-id]
        |     |     +--rw vpn-network-access-id      svc-id
        |     |     +--rw description?               string
        |     |     +--rw status
        |     |     |  +--rw admin-enabled?   boolean
        |     |     |  +--ro oper-status?     operational-type
        |     |     +--rw vpn-network-access-type?
        |     |     |       identityref
        |     |     +--rw connection
        |     |     |  +--rw encapsulation-type?   identityref
        |     |     |  +--rw tagged-interface
        |     |     |  |  +--rw type?
        |     |     |  |  |       identityref
        |     |     |  |  +--rw dot1q-vlan-tagged {dot1q}?
        |     |     |  |  |  +--rw tag-type?   identityref
        |     |     |  |  |  +--rw cvlan-id?   uint16
        |     |     |  |  +--rw priority-tagged
        |     |     |  |  |  +--rw tag-type?   identityref
        |     |     |  |  +--rw qinq {qinq}?
        |     |     |  |  |  +--rw tag-type?   identityref
        |     |     |  |  |  +--rw svlan-id    uint16
        |     |     |  |  |  +--rw cvlan-id    uint16
        |     |     |  |  +--rw qinany {qinany}?
        |     |     |  |  |  +--rw tag-type?   identityref
        |     |     |  |  |  +--rw svlan-id    uint16
        |     |     |  |  +--rw vxlan {vxlan}?
        |     |     |  |     +--rw vni-id       uint32
        |     |     |  |     +--rw peer-mode?   identityref
        |     |     |  |     +--rw peer-list* [peer-ip]
        |     |     |  |        +--rw peer-ip
        |     |     |  |                inet:ip-address
        |     |     |  +--rw bearer
        |     |     |     +--rw bearer-reference?   string
        |     |     |     |       {bearer-reference}?
        |     |     |     +--rw pseudowire
        |     |     |        +--rw vcid?   uint32
        |     |     +--rw ip-connection
        |     |     |  +--rw ipv4 {ipv4}?

Aguado, et al.            Expires May 20, 2020                 [Page 18]
Internet-Draft                    l3nm                     November 2019

        |     |     |  |  +--rw address-allocation-type?
        |     |     |  |  |       identityref
        |     |     |  |  +--rw provider-dhcp
        |     |     |  |  |  +--rw provider-address?
        |     |     |  |  |  |       inet:ipv4-address
        |     |     |  |  |  +--rw prefix-length?
        |     |     |  |  |  |       uint8
        |     |     |  |  |  +--rw (address-assign)?
        |     |     |  |  |     +--:(number)
        |     |     |  |  |     |  +--rw number-of-dynamic-address?
        |     |     |  |  |     |          uint16
        |     |     |  |  |     +--:(explicit)
        |     |     |  |  |        +--rw customer-addresses
        |     |     |  |  |           +--rw address-group*
        |     |     |  |  |                   [group-id]
        |     |     |  |  |              +--rw group-id
        |     |     |  |  |              |       string
        |     |     |  |  |              +--rw start-address?
        |     |     |  |  |              |       inet:ipv4-address
        |     |     |  |  |              +--rw end-address?
        |     |     |  |  |                      inet:ipv4-address
        |     |     |  |  +--rw dhcp-relay
        |     |     |  |  |  +--rw provider-address?
        |     |     |  |  |  |       inet:ipv4-address
        |     |     |  |  |  +--rw prefix-length?
        |     |     |  |  |  |       uint8
        |     |     |  |  |  +--rw customer-dhcp-servers
        |     |     |  |  |     +--rw server-ip-address*
        |     |     |  |  |             inet:ipv4-address
        |     |     |  |  +--rw static-addresses
        |     |     |  |     +--rw primary-address?   leafref
        |     |     |  |     +--rw address* [address-id]
        |     |     |  |        +--rw address-id
        |     |     |  |        |       string
        |     |     |  |        +--rw provider-address?
        |     |     |  |        |       inet:ipv4-address
        |     |     |  |        +--rw customer-address?
        |     |     |  |        |       inet:ipv4-address
        |     |     |  |        +--rw prefix-length?
        |     |     |  |                uint8
        |     |     |  +--rw ipv6 {ipv6}?
        |     |     |  |  +--rw address-allocation-type?
        |     |     |  |  |       identityref
        |     |     |  |  +--rw provider-dhcp
        |     |     |  |  |  +--rw provider-address?
        |     |     |  |  |  |       inet:ipv6-address
        |     |     |  |  |  +--rw prefix-length?
        |     |     |  |  |  |       uint8

Aguado, et al.            Expires May 20, 2020                 [Page 19]
Internet-Draft                    l3nm                     November 2019

        |     |     |  |  |  +--rw (address-assign)?
        |     |     |  |  |     +--:(number)
        |     |     |  |  |     |  +--rw number-of-dynamic-address?
        |     |     |  |  |     |          uint16
        |     |     |  |  |     +--:(explicit)
        |     |     |  |  |        +--rw customer-addresses
        |     |     |  |  |           +--rw address-group*
        |     |     |  |  |                   [group-id]
        |     |     |  |  |              +--rw group-id
        |     |     |  |  |              |       string
        |     |     |  |  |              +--rw start-address?
        |     |     |  |  |              |       inet:ipv6-address
        |     |     |  |  |              +--rw end-address?
        |     |     |  |  |                      inet:ipv6-address
        |     |     |  |  +--rw dhcp-relay
        |     |     |  |  |  +--rw provider-address?
        |     |     |  |  |  |       inet:ipv6-address
        |     |     |  |  |  +--rw prefix-length?
        |     |     |  |  |  |       uint8
        |     |     |  |  |  +--rw customer-dhcp-servers
        |     |     |  |  |     +--rw server-ip-address*
        |     |     |  |  |             inet:ipv6-address
        |     |     |  |  +--rw static-addresses
        |     |     |  |     +--rw primary-address?   leafref
        |     |     |  |     +--rw address* [address-id]
        |     |     |  |        +--rw address-id
        |     |     |  |        |       string
        |     |     |  |        +--rw provider-address?
        |     |     |  |        |       inet:ipv6-address
        |     |     |  |        +--rw customer-address?
        |     |     |  |        |       inet:ipv6-address
        |     |     |  |        +--rw prefix-length?
        |     |     |  |                uint8
        |     |     |  +--rw oam
        |     |     |     +--rw bfd {bfd}?
        |     |     |        +--rw enabled?
        |     |     |        |       boolean
        |     |     |        +--rw (holdtime)?
        |     |     |           +--:(fixed)
        |     |     |           |  +--rw fixed-value?
        |     |     |           |          uint32
        |     |     |           +--:(profile)
        |     |     |              +--rw profile-name?   leafref
        |     |     +--rw security
        |     |     |  +--rw authentication
        |     |     |  +--rw encryption {encryption}?
        |     |     |  |  +--rw enabled?   boolean
        |     |     |  |  +--rw layer?     enumeration

Aguado, et al.            Expires May 20, 2020                 [Page 20]
Internet-Draft                    l3nm                     November 2019

        |     |     |  +--rw encryption-profile
        |     |     |     +--rw (profile)?
        |     |     |     |  +--:(provider-profile)
        |     |     |     |  |  +--rw profile-name?    leafref
        |     |     |     |  +--:(customer-profile)
        |     |     |     |     +--rw algorithm?       string
        |     |     |     +--rw (key-type)?
        |     |     |        +--:(psk)
        |     |     |           +--rw preshared-key?   string
        |     |     +--rw routing-protocols
        |     |        +--rw routing-protocol* [id]
        |     |           +--rw id                  string
        |     |           +--rw type?
        |     |           |       identityref
        |     |           +--rw routing-profiles* [id]
        |     |           |  +--rw id      leafref
        |     |           |  +--rw type?   ie-type
        |     |           +--rw ospf {rtg-ospf}?
        |     |           |  +--rw address-family*
        |     |           |  |       address-family
        |     |           |  +--rw area-address
        |     |           |  |       yang:dotted-quad
        |     |           |  +--rw metric?           uint16
        |     |           |  +--rw mtu?              uint16
        |     |           |  +--rw process-id?       uint16
        |     |           |  +--rw security
        |     |           |  |  +--rw auth-key?   string
        |     |           |  +--rw sham-links
        |     |           |          {rtg-ospf-sham-link}?
        |     |           |     +--rw sham-link* [target-site]
        |     |           |        +--rw target-site    svc-id
        |     |           |        +--rw metric?        uint16
        |     |           +--rw bgp {rtg-bgp}?
        |     |           |  +--rw autonomous-system    uint32
        |     |           |  +--rw address-family*
        |     |           |  |       address-family
        |     |           |  +--rw neighbor?
        |     |           |  |       inet:ip-address
        |     |           |  +--rw multihop?            uint8
        |     |           |  +--rw security
        |     |           |     +--rw auth-key?   string
        |     |           +--rw static
        |     |           |  +--rw cascaded-lan-prefixes
        |     |           |     +--rw ipv4-lan-prefixes*
        |     |           |     |       [lan next-hop] {ipv4}?
        |     |           |     |  +--rw lan
        |     |           |     |  |       inet:ipv4-prefix
        |     |           |     |  +--rw lan-tag?    string

Aguado, et al.            Expires May 20, 2020                 [Page 21]
Internet-Draft                    l3nm                     November 2019

        |     |           |     |  +--rw next-hop
        |     |           |     |          inet:ipv4-address
        |     |           |     +--rw ipv6-lan-prefixes*
        |     |           |             [lan next-hop] {ipv6}?
        |     |           |        +--rw lan
        |     |           |        |       inet:ipv6-prefix
        |     |           |        +--rw lan-tag?    string
        |     |           |        +--rw next-hop
        |     |           |                inet:ipv6-address
        |     |           +--rw rip {rtg-rip}?
        |     |           |  +--rw address-family*
        |     |           |          address-family
        |     |           +--rw vrrp {rtg-vrrp}?
        |     |              +--rw address-family*
        |     |                      address-family
        |     +--rw maximum-routes
        |     |  +--rw address-family* [af]
        |     |     +--rw af                address-family
        |     |     +--rw maximum-routes?   uint32
        |     +--rw node-ie-profile?        leafref
        +--rw multicast {multicast}?
           +--rw enabled?                 boolean
           +--rw customer-tree-flavors
           |  +--rw tree-flavor*   identityref
           +--rw rp
              +--rw rp-group-mappings
              |  +--rw rp-group-mapping* [id]
              |     +--rw id                  uint16
              |     +--rw provider-managed
              |     |  +--rw enabled?
              |     |  |       boolean
              |     |  +--rw rp-redundancy?
              |     |  |       boolean
              |     |  +--rw optimal-traffic-delivery?
              |     |          boolean
              |     +--rw rp-address          inet:ip-address
              |     +--rw groups
              |        +--rw group* [id]
              |           +--rw id                     uint16
              |           +--rw (group-format)
              |              +--:(singleaddress)
              |              |  +--rw group-address?
              |              |          inet:ip-address
              |              +--:(startend)
              |                 +--rw group-start?
              |                 |       inet:ip-address
              |                 +--rw group-end?
              |                         inet:ip-address

Aguado, et al.            Expires May 20, 2020                 [Page 22]
Internet-Draft                    l3nm                     November 2019

              +--rw rp-discovery
                 +--rw rp-discovery-type?   identityref
                 +--rw bsr-candidates
                    +--rw bsr-candidate-address*
                            inet:ip-address

                                 Figure 10

4.  Use of the Data Model

4.1.  Multi-Domain Resource Management

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

5.  Relation with other Yang Models

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

5.1.  Relation with L3SM

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 23]
Internet-Draft                    l3nm                     November 2019

5.2.  Relation with Network Topology

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

5.3.  Relation with Device Models

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

6.  L3VPN Examples

6.1.  4G VPN Provissioning Example

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

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

                                                        +--------------+
           +------+    +-----+    +-----+    +-----+    |  Platforms   |
           |eNODEB|--/-|  PE |----|  P  |----|  PE |----|  (SGW/MME)   |
           +------+    +-----+    +-----+    +-----+    |     ...      |
                                                        +--------------+

                    Figure 11: Mobile Backhaul Example

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

   Create VPN Service

Aguado, et al.            Expires May 20, 2020                 [Page 24]
Internet-Draft                    l3nm                     November 2019

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

                       Figure 12: Create VPN Service

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

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

                        Figure 13: Create VPN Node

   Create VPN Network Access

Aguado, et al.            Expires May 20, 2020                 [Page 25]
Internet-Draft                    l3nm                     November 2019

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

                   Figure 14: Create VPN Network Access

7.  Yang Module

 <CODE BEGINS> file "ietf-l3vpn-ntw@2019-11-17.yang"
 module ietf-l3vpn-ntw {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw";
  prefix l3vpn-ntw;
  import ietf-inet-types {
   prefix inet;
  }
  import ietf-yang-types {
   prefix yang;
  }
  import ietf-netconf-acm {

Aguado, et al.            Expires May 20, 2020                 [Page 26]
Internet-Draft                    l3nm                     November 2019

   prefix nacm;
  }
  import ietf-routing-types {
     prefix rt-types;
  }
  organization
    "IETF OPSA (Operations and Management Area) Working Group ";
  contact
    "WG Web:   <http://tools.ietf.org/wg/opsawg/>
        WG List:  <mailto:opsawg@ietf.org>
        Editor:    Oscar Gonzalez de Dios
                  <mailto:oscar.gonzalezdedios@telefonica.com>
        Editor:    Alejandro Aguado
                  <mailto:alejandro.aguado_martin@nokia.com>
        Editor:    Victor Lopez
                  <mailto:victor.lopezalvarez@telefonica.com>
        Editor:    Daniel Voyer
                  <mailto:daniel.voyer@bell.ca>
        Editor:    Luis Angel Munoz
                  <mailto:luis-angel.munoz@vodafone.com>
    ";

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

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

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

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

    revision 2019-11-17 {
     description

Aguado, et al.            Expires May 20, 2020                 [Page 27]
Internet-Draft                    l3nm                     November 2019

     "Network centric hierarchy. Customer unused parameters prunned.
     Site removal";
     reference
       "draft-ietf-opsawg-l3sm-l3nm-01";
     }

  revision 2019-09-13 {
   description
   "Initial document. The document as a whole is based on L3SM
   module, defined in RFC 8299, modified to fit the requirements
   of the platforms at the network layer.";
   reference
     "RFC 8049.";
   }
  /* Features */
  feature cloud-access {
   description
   "Allows the VPN to connect to a CSP.";
   }
  feature multicast {
   description
   "Enables multicast capabilities in a VPN.";
  }
  feature ipv4 {
   description
   "Enables IPv4 support in a VPN.";
  }
  feature ipv6 {
   description
   "Enables IPv6 support in a VPN.";
  }
  feature lan-tag {
   description
   "Enables LAN Tag support in a VPN Policy filter.";
  }
  feature carrierscarrier {
   description
   "Enables support of CsC.";
  }
  feature extranet-vpn {
   description
   "Enables support of extranet VPNs.";
  }
  feature encryption {
   description
   "Enables support of encryption.";
  }
  feature qos {

Aguado, et al.            Expires May 20, 2020                 [Page 28]
Internet-Draft                    l3nm                     November 2019

   description
   "Enables support of classes of services.";
  }
  feature qos-custom {
   description
   "Enables support of the custom QoS profile.";
  }
  feature rtg-bgp {
   description
   "Enables support of the BGP routing protocol.";
  }
  feature rtg-rip {
   description
   "Enables support of the RIP routing protocol.";
  }
  feature rtg-ospf {
   description
   "Enables support of the OSPF routing protocol.";
  }
  feature rtg-ospf-sham-link {
   description
   "Enables support of OSPF sham links.";
  }
  feature rtg-vrrp {
   description
   "Enables support of the VRRP routing protocol.";
  }
  feature fast-reroute {
   description
   "Enables support of Fast Reroute.";
  }
  feature bfd {
   description
   "Enables support of BFD.";
  }
  feature bearer-reference {
   description
   "Enables support of the 'bearer-reference' access constraint.";
  }
  feature target-sites {
   description
   "Enables support of the 'target-sites' match flow parameter.";
  }
 feature input-bw {
   description
   "Enables support of the 'input-bw' limit.";
  }
 feature dot1q  {

Aguado, et al.            Expires May 20, 2020                 [Page 29]
Internet-Draft                    l3nm                     November 2019

   description
   "Enables support of the 'dot1q' encapsulation.";
  }
 feature qinq  {
   description
   "Enables support of the 'qinq' encapsulation.";
  }
 feature qinany  {
   description
   "Enables support of the 'qinany' encapsulation.";
  }
  feature vxlan  {
   description
   "Enables support of the 'vxlan' encapsulation.";
  }

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

   typedef ie-type {
    type enumeration {

Aguado, et al.            Expires May 20, 2020                 [Page 30]
Internet-Draft                    l3nm                     November 2019

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

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

  /* Identities */
  identity site-network-access-type {
   description
   "Base identity for site-network-access type.";
  }
  identity point-to-point {
   base site-network-access-type;
   description
   "Identity for point-to-point connection.";
  }

Aguado, et al.            Expires May 20, 2020                 [Page 31]
Internet-Draft                    l3nm                     November 2019

  /* Extension */
  identity pseudowire {
   base site-network-access-type;
   description
   "Identity for pseudowire connection.";
  }
  /* End of Extension */
  identity multipoint {
   base site-network-access-type;
   description
   "Identity for multipoint connection.
   Example: Ethernet broadcast segment.";
  }
  identity customer-application {
   description
   "Base identity for customer application.";
  }
  identity web {
   base customer-application;
   description
   "Identity for Web application (e.g., HTTP, HTTPS).";
  }
  identity mail {
   base customer-application;
   description
   "Identity for mail application.";
  }
  identity file-transfer {
   base customer-application;
   description
   "Identity for file transfer application (e.g., FTP, SFTP).";
  }
  identity database {
   base customer-application;
   description
   "Identity for database application.";
  }
  identity social {
   base customer-application;
   description
   "Identity for social-network application.";
  }
  identity games {
   base customer-application;
   description
   "Identity for gaming application.";
  }
  identity p2p {

Aguado, et al.            Expires May 20, 2020                 [Page 32]
Internet-Draft                    l3nm                     November 2019

   base customer-application;
   description
   "Identity for peer-to-peer application.";
  }
  identity network-management {
   base customer-application;
   description
   "Identity for management application
   (e.g., Telnet, syslog, SNMP).";
  }
  identity voice {
   base customer-application;
   description
   "Identity for voice application.";
  }
  identity video {
   base customer-application;
   description
   "Identity for video conference application.";
  }
  identity embb {
   base customer-application;
   description
   "Identity for an enhanced Mobile Broadband (eMBB)
   application.  Note that an eMBB application demands
   network performance with a wide variety of
   characteristics, such as data rate, latency,
   loss rate, reliability, and many other parameters.";
 }
 identity urllc {
   base customer-application;
   description
   "Identity for an Ultra-Reliable and Low Latency
   Communications (URLLC) application.  Note that a
   URLLC application demands network performance
   with a wide variety of characteristics, such as latency,
   reliability, and many other parameters.";
  }
  identity mmtc {
    base customer-application;
    description
    "Identity for a massive Machine Type
    Communications (mMTC) application.  Note that an
    mMTC application demands network performance
    with a wide variety of characteristics, such as data
    rate, latency, loss rate, reliability, and many
    other parameters.";
  }

Aguado, et al.            Expires May 20, 2020                 [Page 33]
Internet-Draft                    l3nm                     November 2019

  identity address-allocation-type {
   description
   "Base identity for address-allocation-type for PE-CE link.";
  }
  identity provider-dhcp {
   base address-allocation-type;
   description
   "Provider network provides DHCP service to customer.";
  }
  identity provider-dhcp-relay {
   base address-allocation-type;
   description
   "Provider network provides DHCP relay service to customer.";
  }
  identity provider-dhcp-slaac {
   base address-allocation-type;
   description
   "Provider network provides DHCP service to customer,
   as well as SLAAC.";
  }
  identity static-address {
   base address-allocation-type;
   description
   "Provider-to-customer addressing is static.";
  }
  identity slaac {
   base address-allocation-type;
   description
   "Use IPv6 SLAAC.";
  }
  identity site-role {
   description
   "Base identity for site type.";
  }
  identity any-to-any-role {
   base site-role;
   description
   "Site in an any-to-any IP VPN.";
  }
  identity spoke-role {
   base site-role;
   description
   "Spoke site in a Hub-and-Spoke IP VPN.";
  }
  identity hub-role {
   base site-role;
   description
   "Hub site in a Hub-and-Spoke IP VPN.";

Aguado, et al.            Expires May 20, 2020                 [Page 34]
Internet-Draft                    l3nm                     November 2019

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

Aguado, et al.            Expires May 20, 2020                 [Page 35]
Internet-Draft                    l3nm                     November 2019

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

Aguado, et al.            Expires May 20, 2020                 [Page 36]
Internet-Draft                    l3nm                     November 2019

   description
   "Base identity for protocol field type.";
  }
  identity tcp {
   base protocol-type;
   description
   "TCP protocol type.";
  }
  identity udp {
   base protocol-type;
   description
   "UDP protocol type.";
  }

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

Aguado, et al.            Expires May 20, 2020                 [Page 37]
Internet-Draft                    l3nm                     November 2019

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

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 38]
Internet-Draft                    l3nm                     November 2019

  /* Extended Identities */

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

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

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

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

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

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

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

   identity port-id {
     base bearer-inf-type;

Aguado, et al.            Expires May 20, 2020                 [Page 39]
Internet-Draft                    l3nm                     November 2019

     description
       "Identity for the priority-tagged interface.";
   }

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

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

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

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

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

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

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 40]
Internet-Draft                    l3nm                     November 2019

   }

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

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

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

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

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

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

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 41]
Internet-Draft                    l3nm                     November 2019

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

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

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

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

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

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

  /* Groupings */
  grouping multicast-rp-group-cfg {
   choice group-format {
    mandatory true;
    case singleaddress {
     leaf group-address {
      type inet:ip-address;
      description
      "A single multicast group address.";
     }
    }
    case startend {

Aguado, et al.            Expires May 20, 2020                 [Page 42]
Internet-Draft                    l3nm                     November 2019

     leaf group-start {
      type inet:ip-address;
      description
      "The first multicast group address in
      the multicast group address range.";
     }
     leaf group-end {
      type inet:ip-address;
      description
      "The last multicast group address in
      the multicast group address range.";
     }
    }
    description
    "Choice for multicast group format.";
   }
   description
   "This grouping defines multicast group or
   multicast groups for RP-to-group mapping.";
  }
  grouping vpn-service-multicast {
   container multicast {
    if-feature multicast;
    leaf enabled {
     type boolean;
     default false;
     description
     "Enables multicast.";
    }
    container customer-tree-flavors {
     leaf-list tree-flavor {
      type identityref {
       base multicast-tree-type;
      }
      description
       "Type of tree to be used.";
     }
     description
     "Type of trees used by customer.";
    }
    container rp {
     container rp-group-mappings {
      list rp-group-mapping {
       key id;
       leaf id {
        type uint16;
        description
        "Unique identifier for the mapping.";

Aguado, et al.            Expires May 20, 2020                 [Page 43]
Internet-Draft                    l3nm                     November 2019

       }
       container provider-managed {
        leaf enabled {
         type boolean;
         default false;
         description
         "Set to true if the Rendezvous Point (RP)
         must be a provider-managed node.  Set to false
         if it is a customer-managed node.";
        }
        leaf rp-redundancy {
         type boolean;
         default false;
         description
         "If true, a redundancy mechanism for the RP
         is required.";
        }
        leaf optimal-traffic-delivery {
         type boolean;
         default false;
         description
         "If true, the SP must ensure that
         traffic uses an optimal path.  An SP may use
         Anycast RP or RP-tree-to-SPT switchover
         architectures.";
        }
        description
        "Parameters for a provider-managed RP.";
       }
       leaf rp-address {
        when "../provider-managed/enabled = 'false'" {
         description
         "Relevant when the RP is not provider-managed.";
        }
        type inet:ip-address;
          mandatory true;
        description
        "Defines the address of the RP.
        Used if the RP is customer-managed.";
       }
       container groups {
        list group {
         key id;
         leaf id {
          type uint16;
          description
          "Identifier for the group.";
         }

Aguado, et al.            Expires May 20, 2020                 [Page 44]
Internet-Draft                    l3nm                     November 2019

         uses multicast-rp-group-cfg;
         description
         "List of multicast groups.";
        }
        description
        "Multicast groups associated with the RP.";
       }
       description
       "List of RP-to-group mappings.";
      }
      description
      "RP-to-group mappings parameters.";
     }
     container rp-discovery {
      leaf rp-discovery-type {
       type identityref {
        base multicast-rp-discovery-type;
        }
       default static-rp;
       description
       "Type of RP discovery used.";
      }
      container bsr-candidates {
        when "derived-from-or-self(../rp-discovery-type, "+
            "'l3vpn-ntw:bsr-rp')" {
        description
        "Only applicable if discovery type
        is BSR-RP.";
       }
       leaf-list bsr-candidate-address {
        type inet:ip-address;
         description
         "Address of BSR candidate.";
       }
       description
       "Container for List of Customer
       BSR candidate's addresses.";
      }
      description
      "RP discovery parameters.";
     }
     description
     "RP parameters.";
    }
    description
    "Multicast global parameters for the VPN service.";
   }
   description

Aguado, et al.            Expires May 20, 2020                 [Page 45]
Internet-Draft                    l3nm                     November 2019

   "Grouping for multicast VPN definition.";
  }
  grouping vpn-service-mpls {
   leaf carrierscarrier {
    if-feature carrierscarrier;
     type boolean;
     default false;
     description
     "The VPN is using CsC, and so MPLS is required.";
   }
   description
   "Grouping for MPLS CsC definition.";
  }
  grouping operational-requirements {
    leaf requested-site-start {
     type yang:date-and-time;
      description
      "Optional leaf indicating requested date and
      time when the service at a particular site is
      expected to start.";
   }
   leaf requested-site-stop {
     type yang:date-and-time;
      description
      "Optional leaf indicating requested date and
      time when the service at a particular site is
      expected to stop.";
   }
   description
   "This grouping defines some operational
   parameters.";
  }
  grouping operational-requirements-ops {
    leaf actual-site-start {
     type yang:date-and-time;
     config false;
      description
      "Optional leaf indicating actual date and
      time when the service at a particular site
      actually started.";
   }
   leaf actual-site-stop {
    type yang:date-and-time;
    config false;
      description
      "Optional leaf indicating actual date and
      time when the service at a particular site
      actually stopped.";

Aguado, et al.            Expires May 20, 2020                 [Page 46]
Internet-Draft                    l3nm                     November 2019

   }
   description
   "This grouping defines some operational
   parameters.";
  }
  grouping flow-definition {
   container match-flow {
    leaf dscp {
     type inet:dscp;
      description
      "DSCP value.";
    }
    leaf dot1p {
     type uint8 {
      range "0..7";
     }
     description
     "802.1p matching.";
    }
    leaf ipv4-src-prefix {
     type inet:ipv4-prefix;
      description
      "Match on IPv4 src address.";
    }
    leaf ipv6-src-prefix {
     type inet:ipv6-prefix;
      description
      "Match on IPv6 src address.";
    }
    leaf ipv4-dst-prefix {
     type inet:ipv4-prefix;
      description
      "Match on IPv4 dst address.";
    }
    leaf ipv6-dst-prefix {
     type inet:ipv6-prefix;
     description
     "Match on IPv6 dst address.";
    }
    leaf l4-src-port {
     type inet:port-number;
         must "current() < ../l4-src-port-range/lower-port or "+
         "current() > ../l4-src-port-range/upper-port" {
      description
      "If l4-src-port and l4-src-port-range/lower-port and
      upper-port are set at the same time, l4-src-port
      should not overlap with l4-src-port-range.";
      }

Aguado, et al.            Expires May 20, 2020                 [Page 47]
Internet-Draft                    l3nm                     November 2019

      description
      "Match on Layer 4 src port.";
    }
    leaf-list target-sites {
      if-feature target-sites;
      type svc-id;
      description
      "Identify a site as traffic destination.";
    }
    container l4-src-port-range {
      leaf lower-port {
      type inet:port-number;
      description
      "Lower boundary for port.";
     }
     leaf upper-port {
      type inet:port-number;
      must ". >= ../lower-port" {
       description
       "Upper boundary for port.  If it
       exists, the upper boundary must be
       higher than the lower boundary.";
      }
      description
      "Upper boundary for port.";
     }
      description
      "Match on Layer 4 src port range.  When
      only the lower-port is present, it represents
      a single port.  When both the lower-port and
      upper-port are specified, it implies
      a range inclusive of both values.";
    }
    leaf l4-dst-port {
     type inet:port-number;
          must "current() < ../l4-dst-port-range/lower-port or "+
          "current() > ../l4-dst-port-range/upper-port" {
      description
      "If l4-dst-port and l4-dst-port-range/lower-port
      and upper-port are set at the same time,
      l4-dst-port should not overlap with
      l4-src-port-range.";
      }
      description
      "Match on Layer 4 dst port.";
    }
    container l4-dst-port-range {
     leaf lower-port {

Aguado, et al.            Expires May 20, 2020                 [Page 48]
Internet-Draft                    l3nm                     November 2019

      type inet:port-number;
      description
      "Lower boundary for port.";
     }
     leaf upper-port {
      type inet:port-number;
      must ". >= ../lower-port" {
      description
      "Upper boundary must be
      higher than lower boundary.";
      }
      description
      "Upper boundary for port.  If it exists,
      upper boundary must be higher than lower
      boundary.";
     }
     description
     "Match on Layer 4 dst port range.  When only
     lower-port is present, it represents a single
     port.  When both lower-port and upper-port are
     specified, it implies a range inclusive of both
     values.";
    }
    leaf protocol-field {
     type union {
      type uint8;
      type identityref {
       base protocol-type;
      }
     }
     description
     "Match on IPv4 protocol or IPv6 Next Header field.";
    }
    description
    "Describes flow-matching criteria.";
   }
   description
   "Flow definition based on criteria.";
  }
  grouping site-service-basic {
   leaf svc-input-bandwidth {
     type uint64;
     units bps;
     mandatory true;
      description
      "From the customer site's perspective, the service
      input bandwidth of the connection or download
      bandwidth from the SP to the site.";

Aguado, et al.            Expires May 20, 2020                 [Page 49]
Internet-Draft                    l3nm                     November 2019

   }
   leaf svc-output-bandwidth {
    type uint64;
    units bps;
    mandatory true;
      description
      "From the customer site's perspective, the service
      output bandwidth of the connection or upload
      bandwidth from the site to the SP.";
   }
   leaf svc-mtu {
    type uint16;
    units bytes;
    mandatory true;
     description
     "MTU at service level.  If the service is IP,
     it refers to the IP MTU.  If CsC is enabled,
     the requested 'svc-mtu' leaf will refer to the
     MPLS MTU and not to the IP MTU.";
   }
   description
   "Defines basic service parameters for a site.";
  }
  grouping site-protection {
   container traffic-protection {
    if-feature fast-reroute;
    leaf enabled {
     type boolean;
     default false;
      description
      "Enables traffic protection of access link.";
    }
    description
    "Fast Reroute service parameters for the site.";
   }
   description
   "Defines protection service parameters for a site.";
  }
  grouping site-service-mpls {
   container carrierscarrier {
    if-feature carrierscarrier;
    leaf signalling-type {
     type enumeration {
     enum ldp {
      description
      "Use LDP as the signalling protocol
      between the PE and the CE.  In this case,
      an IGP routing protocol must also be activated.";

Aguado, et al.            Expires May 20, 2020                 [Page 50]
Internet-Draft                    l3nm                     November 2019

      }
     enum bgp {
      description
      "Use BGP (as per RFC 8277) as the signalling protocol
      between the PE and the CE.
      In this case, BGP must also be configured as
      the routing protocol.";
      }
     }
     default bgp;
     description
     "MPLS signalling type.";
    }
      description
      "This container is used when the customer provides
      MPLS-based services.  This is only used in the case
      of CsC (i.e., a customer builds an MPLS service using
      an IP VPN to carry its traffic).";
   }
      description
      "Defines MPLS service parameters for a site.";
  }
  grouping site-service-qos-profile {
   container qos {
    if-feature qos;
    container qos-classification-policy {
     list rule {
      key id;
      ordered-by user;
      leaf id {
       type string;
       description
       "A description identifying the
        qos-classification-policy rule.";
      }
      choice match-type {
       default match-flow;
       case match-flow {
       uses flow-definition;
       }
       case match-application {
        leaf match-application {
         type identityref {
          base customer-application;
         }
          description
          "Defines the application to match.";
        }

Aguado, et al.            Expires May 20, 2020                 [Page 51]
Internet-Draft                    l3nm                     November 2019

       }
       description
       "Choice for classification.";
      }
      leaf target-class-id {
       type string;
       description
       "Identification of the class of service.
       This identifier is internal to the administration.";
      }
      description
      "List of marking rules.";
     }
     description
     "Configuration of the traffic classification policy.";
    }
    container qos-profile {
     choice qos-profile {
      description
      "Choice for QoS profile.
      Can be standard profile or customized profile.";
      case standard {
       description
       "Standard QoS profile.";
       leaf profile {
        type leafref {
        path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
            "/qos-profile-identifier/id";
        }
        description
        "QoS profile to be used.";
       }
       leaf direction {
         type identityref {
           base qos-profile-direction;}
             default both;
             description
             "The direction to which the QoS profile
             is applied.";
       }
      }
      case custom {
       description
       "Customized QoS profile.";
        container classes {
         if-feature qos-custom;
         list class {
          key class-id;

Aguado, et al.            Expires May 20, 2020                 [Page 52]
Internet-Draft                    l3nm                     November 2019

          leaf class-id {
          type string;
                   description
                   "Identification of the class of service.
                   This identifier is internal to the
                   administration.";
          }
          leaf direction {
                   type identityref {
                    base qos-profile-direction;
                    }
                   default both;
                    description
                    "The direction to which the QoS profile
                    is applied.";
                 }
                  leaf rate-limit {
                   type decimal64 {
                    fraction-digits 5;
                    range "0..100";
           }
                   units percent;
                    description
                    "To be used if the class must be rate-limited.
                    Expressed as percentage of the service
                    bandwidth.";
         }

         container latency {
          choice flavor {
           case lowest {
            leaf use-lowest-latency {
             type empty;
              description
              "The traffic class should use the path with the
              lowest latency.";
            }
           }
           case boundary {
            leaf jitter-boundary {
             type uint16;
             units msec;
             default 400;
              description
              "The traffic class should use a path with a
              defined maximum latency.";
            }
           }

Aguado, et al.            Expires May 20, 2020                 [Page 53]
Internet-Draft                    l3nm                     November 2019

           description
           "Latency constraint on the traffic class.";
          }
          description
          "Latency constraint on the traffic class.";
         }
         container jitter {
          choice flavor {
           case lowest {
            leaf use-lowest-jitter {
             type empty;
              description
              "The traffic class should use the path with the
              lowest jitter.";
            }
           }
           case boundary {
            leaf latency-boundary {
             type uint32;
             units usec;
             default 40000;
              description
              "The traffic class should use a path with a
              defined maximum jitter.";
            }
           }
           description
           "Jitter constraint on the traffic class.";
          }
          description
          "Jitter constraint on the traffic class.";
         }
         container bandwidth {
          leaf guaranteed-bw-percent {
           type decimal64 {
                   fraction-digits 5;
                   range "0..100";
           }
           units percent;
           mandatory true;
            description
            "To be used to define the guaranteed bandwidth
            as a percentage of the available service bandwidth.";
          }
          leaf end-to-end {
           type empty;
            description
            "Used if the bandwidth reservation

Aguado, et al.            Expires May 20, 2020                 [Page 54]
Internet-Draft                    l3nm                     November 2019

            must be done on the MPLS network too.";
          }
          description
          "Bandwidth constraint on the traffic class.";
         }
         description
         "List of classes of services.";
        }
        description
        "Container for list of classes of services.";
       }
      }
     }
     description
     "QoS profile configuration.";
    }
    description
    "QoS configuration.";
   }
   description
   "This grouping defines QoS parameters for a site.";
  }
  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;
       default false;
       description
       "If true, traffic encryption on the connection is required.";
     }
      leaf layer {
         when "../enabled = 'true'" {
         description
         "Require a value for layer when enabled is true.";
        }
       type enumeration {
         enum layer2 {
         description
         "Encryption will occur at Layer 2.";

Aguado, et al.            Expires May 20, 2020                 [Page 55]
Internet-Draft                    l3nm                     November 2019

         }
         enum layer3 {
         description
         "Encryption will occur at Layer 3.
         For example, IPsec may be used when
         a customer requests Layer 3 encryption.";
        }
       }
     description
     "Layer on which encryption is applied.";
     }
     description
     "";
   }
   container encryption-profile {
     choice profile {
       case provider-profile {
         leaf profile-name {
            type leafref {
             path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
               "/encryption-profile-identifier/id";
            }
            description
            "Name of the SP profile to be applied.";
         }
       }
       case customer-profile {
         leaf algorithm {
           type string;
           description
           "Encryption algorithm to be used.";
         }
       }
     description
     "";
     }
     choice key-type {
       default psk;
       case psk {
         leaf preshared-key {
           type string;
           description
           "Pre-Shared Key (PSK) coming from the customer.";
         }
       }
       description
       "Choice of encryption profile.
       The encryption profile can be the provider profile

Aguado, et al.            Expires May 20, 2020                 [Page 56]
Internet-Draft                    l3nm                     November 2019

       or customer profile.";
     }
     description
     "This grouping defines encryption parameters for a site.";
   }
   description
   "";
  }

  grouping site-routing {
   container routing-protocols {
    list routing-protocol {
     key id;
     leaf id{
     type string;
     description
     "";
     }
     leaf type {
      type identityref {
       base routing-protocol-type;
      }
      description
      "Type of routing protocol.";
     }

     list routing-profiles {
       key "id";

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

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

    description
   "Import or Export profile reference";
     }

Aguado, et al.            Expires May 20, 2020                 [Page 57]
Internet-Draft                    l3nm                     November 2019

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

      /* Extension */

      leaf mtu {
          type uint16;
          description "Maximum transmission unit for a given
          OSPF link.";
      }

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

      /* End of Extension */

Aguado, et al.            Expires May 20, 2020                 [Page 58]
Internet-Draft                    l3nm                     November 2019

      container sham-links {
       if-feature rtg-ospf-sham-link;
       list sham-link {
        key target-site;
        leaf target-site {
         type svc-id;
          description
          "Target site for the sham link connection.
          The site is referred to by its ID.";
        }
        leaf metric {
         type uint16;
         default 1;
          description
          "Metric of the sham link.  It is used in
          the routing state calculation and path
          selection.  The default value is set
          to 1.";
        }
          description
          "Creates a sham link with another site.";
       }
       description
       "List of sham links.";
      }
      description
      "OSPF-specific configuration.";
     }
     container bgp {
      when "derived-from-or-self(../type, 'l3vpn-ntw:bgp')" {
       description
       "Only applies when protocol is BGP.";
      }
      if-feature rtg-bgp;
      leaf autonomous-system {
       type uint32;
       mandatory true;
          description
          "Customer AS number in case the customer
          requests BGP routing.";
      }
      leaf-list address-family {
       type address-family;
           min-elements "1";
          description
          "If BGP is used on this site, this node
          contains a configured value.  This node
          contains at least one address family

Aguado, et al.            Expires May 20, 2020                 [Page 59]
Internet-Draft                    l3nm                     November 2019

          to be activated.";
      }
      /*  Extension  */
      leaf neighbor {
         type inet:ip-address;
          description
          "IP address of the BGP neighbor.";
      }

      leaf multihop {
         type uint8;
          description
          "Describes the number of hops allowed between the
          given BGP neighbor and the PE router.";
      }

      uses security-params;

      description
      "BGP-specific configuration.";
     }
     container static {
      when "derived-from-or-self(../type, 'l3vpn-ntw:static')" {
        description
        "Only applies when protocol is static.
        BGP activation requires the SP to know
        the address of the customer peer.  When
        BGP is enabled, the 'static-address'
        allocation type for the IP connection
        MUST be used.";
      }
      container cascaded-lan-prefixes {
       list ipv4-lan-prefixes {
        if-feature ipv4;
        key "lan next-hop";
        leaf lan {
         type inet:ipv4-prefix;
         description
         "LAN prefixes.";
        }
        leaf lan-tag {
         type string;
          description
          "Internal tag to be used in VPN policies.";
        }
        leaf next-hop {
         type inet:ipv4-address;
          description

Aguado, et al.            Expires May 20, 2020                 [Page 60]
Internet-Draft                    l3nm                     November 2019

          "Next-hop address to use on the customer side.";
        }
        description
        "List of LAN prefixes for the site.";
       }
       list ipv6-lan-prefixes {
        if-feature ipv6;
        key "lan next-hop";
        leaf lan {
         type inet:ipv6-prefix;
          description
          "LAN prefixes.";
        }
        leaf lan-tag {
         type string;
         description
         "Internal tag to be used in VPN policies.";
        }
        leaf next-hop {
         type inet:ipv6-address;
          description
          "Next-hop address to use on the customer side.";
        }
        description
        "List of LAN prefixes for the site.";
       }
       description
       "LAN prefixes from the customer.";
      }
      description
      "Configuration specific to static routing.";
     }
     container rip {
      when "derived-from-or-self(../type, 'l3vpn-ntw:rip')" {
       description
       "Only applies when the protocol is RIP.  For IPv4,
       the model assumes that RIP version 2 is used.";
      }
      if-feature rtg-rip;
      leaf-list address-family {
       type address-family;
           min-elements "1";
          description
          "If RIP is used on this site, this node
          contains a configured value.  This node
          contains at least one address family
          to be activated.";
      }

Aguado, et al.            Expires May 20, 2020                 [Page 61]
Internet-Draft                    l3nm                     November 2019

      description
      "Configuration specific to RIP routing.";
     }
     container vrrp {
      when "derived-from-or-self(../type, 'l3vpn-ntw:vrrp')" {
       description
       "Only applies when protocol is VRRP.";
      }
      if-feature rtg-vrrp;
      leaf-list address-family {
       type address-family;
           min-elements "1";
          description
          "If VRRP is used on this site, this node
          contains a configured value.  This node contains
          at least one address family to be activated.";
      }
      description
      "Configuration specific to VRRP routing.";
     }
     description
     "List of routing protocols used on
     the site.  This list can be augmented.";
    }
    description
    "Defines routing protocols.";
   }
   description
   "Grouping for routing protocols.";
  }
  grouping site-attachment-ip-connection {

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

Aguado, et al.            Expires May 20, 2020                 [Page 62]
Internet-Draft                    l3nm                     November 2019

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

Aguado, et al.            Expires May 20, 2020                 [Page 63]
Internet-Draft                    l3nm                     November 2019

          key "group-id";
          leaf group-id {
          type string;
          description
          "Group-id for the address range from
          start-address to end-address.";
          }
         leaf start-address {
          type inet:ipv4-address;
           description
           "First address.";
          }
         leaf end-address {
          type inet:ipv4-address;
          description
          "Last address.";
          }
          description
          "Describes IP addresses allocated by DHCP.
          When only start-address or only end-address
          is present, it represents a single address.
          When both start-address and end-address are
          specified, it implies a range inclusive of both
          addresses.  If no address is specified, it implies
          customer addresses group is not supported.";
         }
          description
          "Container for customer addresses is allocated by DHCP.";
        }
      }
          description
          "Choice for the way to assign addresses.";
      }
          description
          "DHCP allocated addresses related parameters.";
     }
  container dhcp-relay {
    when "derived-from-or-self(../address-allocation-type, "+
    "'l3vpn-ntw:provider-dhcp-relay')" {
      description
      "Only applies when provider is required to implement
      DHCP relay function.";
   }
  leaf provider-address {
   type inet:ipv4-address;
      description
      "Address of provider side.  If provider-address is not
      specified, then prefix length should not be specified

Aguado, et al.            Expires May 20, 2020                 [Page 64]
Internet-Draft                    l3nm                     November 2019

      either.  It also implies provider-dhcp allocation is
      not enabled.  If provider-address is specified, then
      prefix length may or may not be specified.";
  }
  leaf prefix-length {
   type uint8 {
   range "0..32";
   }
  must "(../provider-address)" {
   error-message
      "If prefix length is specified, provider-address
       must also be specified.";
      description
      "If prefix length is specified, provider-address
      must also be specified.";
 }
      description
      "Subnet prefix length expressed in bits.  If not
      specified, or specified as zero, this means the
      customer leaves the actual prefix length value
      to the provider.";
  }
  container customer-dhcp-servers {
   leaf-list server-ip-address {
   type inet:ipv4-address;
      description
      "IP address of customer DHCP server.";
  }
  description
  "Container for list of customer DHCP servers.";
  }
  description
  "DHCP relay provided by operator.";
 }
  container static-addresses {
    when "derived-from-or-self(../address-allocation-type, "+
    "'l3vpn-ntw:static-address')" {
    description
    "Only applies when protocol allocation type is static.";
     }
     leaf primary-address{
     type leafref {
      path "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/"+
      "vpn-node/vpn-network-accesses/vpn-network-access/"+
      "ip-connection/ipv4/static-addresses/address/address-id";
     }
     description
     "Principal address of the connection.";

Aguado, et al.            Expires May 20, 2020                 [Page 65]
Internet-Draft                    l3nm                     November 2019

     }
     list address{
     key address-id;
      leaf address-id {
      type string;
      description
      "IPv4 Address";
      }
      leaf provider-address {
       type inet:ipv4-address;
          description
          "IPv4 Address List of the provider side.
          When the protocol allocation type is static,
          the provider address must be configured.";
      }
      leaf customer-address {
       type inet:ipv4-address;
          description
          "IPv4 Address of customer side.";
      }
      leaf prefix-length {
       type uint8 {
        range "0..32";
       }
      description
      "Subnet prefix length expressed in bits.
      It is applied to both provider-address
      and customer-address.";
      }
      description
      "Describes IPv4 addresses used.";
     }
     description
     "Describes IPv4 addresses used.";
     }
     description
     "IPv4-specific parameters.";
    }
    container ipv6 {
     if-feature ipv6;
     leaf address-allocation-type {
      type identityref {
       base address-allocation-type;
      }
      description
      "Defines how addresses are allocated.
      If there is no value for the address
      allocation type, then IPv6 is

Aguado, et al.            Expires May 20, 2020                 [Page 66]
Internet-Draft                    l3nm                     November 2019

      not enabled.";
     }

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

Aguado, et al.            Expires May 20, 2020                 [Page 67]
Internet-Draft                    l3nm                     November 2019

           }
          }
          case explicit {
           container customer-addresses {
            list address-group {
                  key "group-id";
                  leaf group-id {
                  type string;
                  description
                  "Group-id for the address range from
                  start-address to end-address.";
              }
                  leaf start-address {
                   type inet:ipv6-address;
                   description
                   "First address.";
                   }
                  leaf end-address {
                   type inet:ipv6-address;
                   description
                   "Last address.";
                   }
                  description
                  "Describes IP addresses allocated by DHCP.  When only
                  start-address or only end-address is present, it
                  represents a single address.  When both start-address
                  and end-address are specified, it implies a range
                  inclusive of both addresses.  If no address is
                  specified, it implies customer addresses group is
                  not supported.";
           }
            description
            "Container for customer addresses allocated by DHCP.";
          }
         }
          description
          "Choice for the way to assign addresses.";
         }
          description
          "DHCP allocated addresses related parameters.";
         }
    container dhcp-relay {
     when "derived-from-or-self(../address-allocation-type, "+
          "'l3vpn-ntw:provider-dhcp-relay')" {
       description
       "Only applies when the provider is required
       to implement DHCP relay function.";
       }

Aguado, et al.            Expires May 20, 2020                 [Page 68]
Internet-Draft                    l3nm                     November 2019

         leaf provider-address {
          type inet:ipv6-address;
           description
           "Address of the provider side.  If provider-address is
           not specified, then prefix length should not be
           specified either.  It also implies provider-dhcp
           allocation is not enabled.  If provider address
           is specified, then prefix length may or may
           not be specified.";
           }
         leaf prefix-length {
          type uint8 {
           range "0..128";
           }
          must "(../provider-address)" {
           error-message
            "If prefix length is specified, provider-address
            must also be specified.";
           description
           "If prefix length is specified, provider-address
           must also be specified.";
            }
          description
          "Subnet prefix length expressed in bits.  If not
          specified, or specified as zero, this means the
          customer leaves the actual prefix length value
          to the provider.";
          }
     container customer-dhcp-servers {
      leaf-list server-ip-address {
       type inet:ipv6-address;
        description
        "This node contains the IP address of
        the customer DHCP server.  If the DHCP relay
        function is implemented by the
        provider, this node contains the
        configured value.";
      }
       description
       "Container for list of customer DHCP servers.";
      }
     description
     "DHCP relay provided by operator.";
     }
     container static-addresses {
       when "derived-from-or-self(../address-allocation-type, "+
       "'l3vpn-ntw:static-address')" {
       description

Aguado, et al.            Expires May 20, 2020                 [Page 69]
Internet-Draft                    l3nm                     November 2019

       "Only applies when protocol allocation type is static.";
        }
        leaf primary-address{
        type leafref {
         path "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/"+
         "vpn-node/vpn-network-accesses/vpn-network-access/"+
         "ip-connection/ipv6/static-addresses/address/address-id";
        }
        description
        "Principal address of the connection";
        }
        list address{
        key address-id;
         leaf address-id {
         type string;
         description
         "IPv4 Address";
         }
     leaf provider-address {
      type inet:ipv6-address;
       description
       "IPv6 Address of the provider side.  When the protocol
       allocation type is static, the provider address
       must be configured.";
      }
     leaf customer-address {
      type inet:ipv6-address;
       description
       "The IPv6 Address of the customer side.";
      }
     leaf prefix-length {
      type uint8 {
       range "0..128";
      }
      description
      "Subnet prefix length expressed in bits.
      It is applied to both provider-address and
      customer-address.";
     }
     description
     "Describes IPv6 addresses used.";
     }
     description
     "IPv6-specific parameters.";
     }
     description
     "IPv6-specific parameters.";
    }

Aguado, et al.            Expires May 20, 2020                 [Page 70]
Internet-Draft                    l3nm                     November 2019

    container oam {
     container bfd {
      if-feature bfd;
      leaf enabled {
       type boolean;
       default false;
       description
       "If true, BFD activation is required.";
      }
      choice holdtime {
       default fixed;
       case fixed {
        leaf fixed-value {
         type uint32;
         units msec;
          description
          "Expected BFD holdtime expressed in msec.  The customer
          may impose some fixed values for the holdtime period
          if the provider allows the customer use this function.
          If the provider doesn't allow the customer to use this
          function, the fixed-value will not be set.";
        }
       }
       case profile {
        leaf profile-name {
         type leafref {
          path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers/"+
                  "bfd-profile-identifier/id";
         }
         description
         "Well-known SP profile name.  The provider can propose
         some profiles to the customer, depending on the service
         level the customer wants to achieve.  Profile names
         must be communicated to the customer.";
        }
        description
        "Well-known SP profile.";
       }
       description
       "Choice for holdtime flavor.";
      }
      description
      "Container for BFD.";
     }
     description
     "Defines the Operations, Administration, and Maintenance (OAM)
     mechanisms used on the connection.  BFD is set as a fault
     detection mechanism, but the 'oam' container can easily

Aguado, et al.            Expires May 20, 2020                 [Page 71]
Internet-Draft                    l3nm                     November 2019

     be augmented by other mechanisms";
    }
    description
    "Defines connection parameters.";
   }
   description
   "This grouping defines IP connection parameters.";
  }
  grouping site-service-multicast {
   container multicast {
    if-feature multicast;
    leaf multicast-site-type {
     type enumeration {
      enum receiver-only {
       description
       "The site only has receivers.";
      }
      enum source-only {
       description
       "The site only has sources.";
      }
      enum source-receiver {
       description
       "The site has both sources and receivers.";
      }
     }
     default source-receiver;
     description
     "Type of multicast site.";
    }
    container multicast-address-family {
     leaf ipv4 {
      if-feature ipv4;
      type boolean;
      default false;
      description
      "Enables IPv4 multicast.";
     }
     leaf ipv6 {
      if-feature ipv6;
      type boolean;
      default false;
      description
      "Enables IPv6 multicast.";
     }
     description
     "Defines protocol to carry multicast.";
     }

Aguado, et al.            Expires May 20, 2020                 [Page 72]
Internet-Draft                    l3nm                     November 2019

    leaf protocol-type {
     type enumeration {
      enum host {
       description
       "Hosts are directly connected to the provider network.
       Host protocols such as IGMP or MLD are required.";
      }
      enum router {
       description
       "Hosts are behind a customer router.
       PIM will be implemented.";
      }
      enum both {
       description
       "Some hosts are behind a customer router, and
       some others are directly connected to the
       provider network.  Both host and routing protocols
       must be used.  Typically, IGMP and PIM will be
       implemented.";
      }
     }
     default "both";
     description
     "Multicast protocol type to be used with the customer site.";
    }
    description
    "Multicast parameters for the site.";
   }
   description
   "Multicast parameters for the site.";
  }
  grouping site-maximum-routes {
   container maximum-routes {
    list address-family {
     key af;
     leaf af {
      type address-family;
      description
      "Address family.";
     }
     leaf maximum-routes {
      type uint32;
      description
      "Maximum prefixes the VRF can accept
      for this address family.";
     }
     description
     "List of address families.";

Aguado, et al.            Expires May 20, 2020                 [Page 73]
Internet-Draft                    l3nm                     November 2019

    }
    description
    "Defines 'maximum-routes' for the VRF.";
   }
   description
   "Defines 'maximum-routes' for the 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 network-access-service {
   container service {
    uses site-service-basic;
    /* Extension */
    /* uses svc-bandwidth-params; */
    /* EoExt */
    uses site-service-qos-profile;
    uses site-service-mpls;
    uses site-service-multicast;
    description
    "Service parameters on the attachment.";
   }
   description
   "Grouping for service parameters.";
  }
  grouping vpn-extranet {
   container extranet-vpns {
    if-feature extranet-vpn;
    list extranet-vpn {
     key vpn-id;
     leaf vpn-id {
      type svc-id;
      description
      "Identifies the target VPN the local VPN want to access.";
     }
     leaf local-sites-role {
      type identityref {
       base site-role;
      }
      default any-to-any-role;
      description

Aguado, et al.            Expires May 20, 2020                 [Page 74]
Internet-Draft                    l3nm                     November 2019

      "This describes the role of the
      local sites in the target VPN topology.  In the any-to-any VPN
      service topology, the local sites must have the same role, which
      will be 'any-to-any-role'.  In the Hub-and-Spoke VPN service
      topology or the Hub-and-Spoke disjoint VPN service topology,
      the local sites must have a Hub role or a Spoke role.";
     }
     description
     "List of extranet VPNs or target VPNs the local VPN is
     attached to.";
    }
    description
    "Container for extranet VPN configuration.";
   }
   description
   "Grouping for extranet VPN configuration.
   This provides an easy way to interconnect
   all sites from two VPNs.";
  }
  grouping vpn-profile-cfg {
   container valid-provider-identifiers {
    list cloud-identifier {
     if-feature cloud-access;
     key id;
     leaf id {
      type string;
      description
      "Identification of cloud service.
      Local administration meaning.";
     }
     description
     "List for Cloud Identifiers.";
    }
    list encryption-profile-identifier {
     key id;
     leaf id {
      type string;
      description
      "Identification of the SP encryption profile
      to be used.  Local administration meaning.";
     }
     description
     "List for encryption profile identifiers.";
    }
    list qos-profile-identifier {
     key id;
     leaf id {
      type string;

Aguado, et al.            Expires May 20, 2020                 [Page 75]
Internet-Draft                    l3nm                     November 2019

      description
      "Identification of the QoS Profile to be used.
      Local administration meaning.";
     }
     description
     "List for QoS Profile Identifiers.";
    }
    list bfd-profile-identifier {
     key id;
     leaf id {
      type string;
      description
      "Identification of the SP BFD Profile to be used.
      Local administration meaning.";
     }
     description
     "List for BFD Profile identifiers.";
    }

    list routing-profile-identifier {
     key id;
     leaf id {
      type string;
      description
      "Identification of the routing Profile to be used
      by the routing-protocols within sites and vpn-
      network-accesses. Local administration meaning.";
     }
     description
     "List for Routing Profile Identifiers.";
    }

      nacm:default-deny-write;
      description
      "Container for Valid Provider Identifies.";
   }

    description
    "Grouping for VPN Profile configuration.";
  }
  grouping vpn-svc-cfg {
   leaf vpn-id {
    type svc-id;
    description
    "VPN identifier.  Local administration meaning.";
   }
   leaf customer-name {
    type string;

Aguado, et al.            Expires May 20, 2020                 [Page 76]
Internet-Draft                    l3nm                     November 2019

    description
    "Name of the customer that actually uses the VPN service.
    In the case that any intermediary (e.g., Tier-2 provider
    or partner) sells the VPN service to their end user
    on behalf of the original service provider (e.g., Tier-1
    provider), the original service provider may require the
    customer name to provide smooth activation/commissioning
    and operation for the service.";
   }
   leaf vpn-service-topology {
    type identityref {
     base vpn-topology;
    }
    default any-to-any;
    description
    "VPN service topology.";
   }

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

   uses ie-profiles-params;
   uses vpn-nodes-params;
   uses vpn-service-multicast;
   /* uses vpn-service-mpls; */
   /* uses vpn-extranet;*/
   description
   "Grouping for VPN service configuration.";
  }
  grouping site-network-access-top-level-cfg {
   uses status-params;
   leaf vpn-network-access-type {
    type identityref {
     base site-network-access-type;
    }
    default point-to-point;
    description
    "Describes the type of connection, e.g.,
    point-to-point or multipoint.";
   }
   uses ethernet-params;
   uses site-attachment-ip-connection;
   uses site-security;
   uses site-routing;
   description

Aguado, et al.            Expires May 20, 2020                 [Page 77]
Internet-Draft                    l3nm                     November 2019

   "Grouping for site network access top-level configuration.";
  }

   /* Bearers in a site */
    grouping site-bearer-params {
     container site-bearers {
       list bearer {
         key "bearer-id";
         leaf bearer-id {
           type string;
           description "";
         }
         leaf BearerType {
         type identityref {
           base bearer-inf-type;
         }
         description
           "Request for an Bearer access type.
           Choose between port or lag connection type.";
         }

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

         leaf port-id {
           type string;
           description
           "Port-id in format slot/ card /port.";
         }
         leaf lag-id {
           type string;
           description
           "lag-id in format id.";
         }
      description
     "Parameters used to identify each bearer";
       }
     description
     "Grouping to reuse the site bearer assigment";
     }
     description
     "Grouping to reuse the site bearer assigment";
    }

    /* UNUSED */

Aguado, et al.            Expires May 20, 2020                 [Page 78]
Internet-Draft                    l3nm                     November 2019

    grouping svc-bandwidth-params {
      container svc-bandwidth {
         if-feature "input-bw";
         list bandwidth {
           key "direction type";
           leaf direction {
             type identityref {
               base bw-direction;
             }
             description
               "Indicates the bandwidth direction.  It can be
                the bandwidth download direction from the SP to
                the site or the bandwidth upload direction from
                the site to the SP.";
           }
           leaf type {
             type identityref {
               base bw-type;
             }
             description
               "Bandwidth type.  By default, the bandwidth type
                is set to 'bw-per-cos'.";
           }
           leaf cos-id {
             when "derived-from-or-self(../type, "
                + "'l3vpn-ntw:bw-per-cos')" {
               description
                 "Relevant when the bandwidth type is set to
                  'bw-per-cos'.";
             }
             type uint8;
             description
               "Identifier of the CoS, indicated by DSCP or a
                CE-VLAN CoS (802.1p) value in the service frame.
                If the bandwidth type is set to 'bw-per-cos',
                the CoS ID MUST also be specified.";
           }
           leaf vpn-id {
             when "derived-from-or-self(../type, "
                + "'l3vpn-ntw:bw-per-svc')" {
               description
                 "Relevant when the bandwidth type is
                  set as bandwidth per VPN service.";
             }
             type svc-id;
             description
               "Identifies the target VPN.  If the bandwidth
                type is set as bandwidth per VPN service, the

Aguado, et al.            Expires May 20, 2020                 [Page 79]
Internet-Draft                    l3nm                     November 2019

                vpn-id MUST be specified.";
           }
           leaf cir {
             type uint64;
             units "bps";
             mandatory true;
             description
               "Committed Information Rate.  The maximum number
                of bits that a port can receive or send over
                an interface in one second.";
           }
           leaf cbs {
             type uint64;
             units "bps";
             mandatory true;
             description
               "Committed Burst Size (CBS).  Controls the bursty
                nature of the traffic.  Traffic that does not
                use the configured Committed Information Rate
                (CIR) accumulates credits until the credits
                reach the configured CBS.";
           }
           leaf eir {
             type uint64;
             units "bps";
             description
               "Excess Information Rate (EIR), i.e., excess frame
                delivery allowed that is not subject to an SLA.
                The traffic rate can be limited by the EIR.";
           }
           leaf ebs {
             type uint64;
             units "bps";
             description
               "Excess Burst Size (EBS).  The bandwidth available
                for burst traffic from the EBS is subject to the
                amount of bandwidth that is accumulated during
                periods when traffic allocated by the EIR
                policy is not used.";
           }
           leaf pir {
             type uint64;
             units "bps";
             description
               "Peak Information Rate, i.e., maximum frame
                delivery allowed.  It is equal to or less
                than the sum of the CIR and the EIR.";
           }

Aguado, et al.            Expires May 20, 2020                 [Page 80]
Internet-Draft                    l3nm                     November 2019

           leaf pbs {
             type uint64;
             units "bps";
             description
               "Peak Burst Size.  It is measured in bytes per
                second.";
           }
           description
             "List of bandwidth values (e.g., per CoS,
              per vpn-id).";
         }
         description
           "From the customer site's perspective, the service
            input/output bandwidth of the connection or
            download/upload bandwidth from the SP/site
            to the site/SP.";
      }
          description
           " ";
    }

   grouping status-params {
     container status {
       leaf admin-enabled {
         type boolean;
         description
         "Administrative Status UP/DOWN";
       }
       leaf oper-status {
         type operational-type;
         config false;
         description
         "Operations status";
       }
       description "";
     }
     description
     "Grouping used to join operational and administrative status
     is re used in the Site Network Acess and in the VPN-Node";
   }

   /* Parameters related to vpn-nodes (VRF config.) */
    grouping vpn-nodes-params {
     container vpn-nodes {
       description "";

Aguado, et al.            Expires May 20, 2020                 [Page 81]
Internet-Draft                    l3nm                     November 2019

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

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

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

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

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

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

         leaf node-role {
           type identityref {
             base site-role;
           }
           default any-to-any-role;
           description
           "Role of the vpn-node in the IP VPN.";
         }
         uses rt-rd;
         uses status-params;
         uses net-acc;

Aguado, et al.            Expires May 20, 2020                 [Page 82]
Internet-Draft                    l3nm                     November 2019

         uses site-maximum-routes;

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

   /* Parameters related to import and export profiles (RTs RDs.) */
    grouping ie-profiles-params {
     container ie-profiles {
       list ie-profile {
         key "ie-profile-id";
         leaf ie-profile-id {
           type string;
         description
            "";
         }
         uses rt-rd;
     description
     "";
       }
     description
     "";
     }
     description
     "Grouping to specify rules for route import and export";
   }

   grouping pseudowire-params {
     container pseudowire {
       /*leaf far-end {*/
       /*  description "IP of the remote peer of the pseudowire.";*/
       /*  type inet:ip-address;*/
       /*}*/
       leaf vcid {
         type uint32;
         description
         "PW or VC identifier.";
       }
     description

Aguado, et al.            Expires May 20, 2020                 [Page 83]
Internet-Draft                    l3nm                     November 2019

     "Pseudowire termination parameters";
     }
      description
     "Grouping pseudowire termination parameters";
   }

   grouping security-params {
     container security {
     leaf auth-key {
         type string;
         description
           "MD5 authentication password for the connection towards the
           customer edge.";
       }
     description
         "Container for aggregating any security parameter for routing
         sessions between a PE and a CE.";
     }
     description
     "Grouping to define security parameters";
   }

 grouping ethernet-params {
   container connection {
     leaf encapsulation-type {
       type identityref {
         base encapsulation-type;
       }
       default "untagged-int";
       description
         "Encapsulation type.  By default, the
          encapsulation type is set to 'untagged'.";
     }
     container tagged-interface {
       leaf type {
         type identityref {
           base tagged-inf-type;
         }
         default "priority-tagged";
         description
           "Tagged interface type.  By default,
            the type of the tagged interface is
            'priority-tagged'.";
       }
       container dot1q-vlan-tagged {
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:dot1q')" {
           description

Aguado, et al.            Expires May 20, 2020                 [Page 84]
Internet-Draft                    l3nm                     November 2019

             "Only applies when the type of the tagged
              interface is 'dot1q'.";
         }
         if-feature "dot1q";
         leaf tag-type {
           type identityref {
             base tag-type;
           }
           default "c-vlan";
           description
             "Tag type.  By default, the tag type is
              'c-vlan'.";
           }
         leaf cvlan-id {
           type uint16;
           description
             "VLAN identifier.";
           }
         description
           "Tagged interface.";
       }
       container priority-tagged {
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:priority-tagged')" {
           description
             "Only applies when the type of the tagged
              interface is 'priority-tagged'.";
         }
         leaf tag-type {
           type identityref {
             base tag-type;
           }
           default "c-vlan";
           description
             "Tag type.  By default, the tag type is
              'c-vlan'.";
         }
         description
           "Priority tagged.";
       }
       container qinq {
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:qinq')" {
           description
             "Only applies when the type of the tagged
              interface is 'qinq'.";
         }
         if-feature "qinq";

Aguado, et al.            Expires May 20, 2020                 [Page 85]
Internet-Draft                    l3nm                     November 2019

         leaf tag-type {
           type identityref {
             base tag-type;
           }
           default "c-s-vlan";
           description
             "Tag type.  By default, the tag type is
              'c-s-vlan'.";
         }
         leaf svlan-id {
           type uint16;
           mandatory true;
           description
             "SVLAN identifier.";
         }
         leaf cvlan-id {
           type uint16;
           mandatory true;
           description
             "CVLAN identifier.";
         }
         description
           "QinQ.";
       }
       container qinany {
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:qinany')" {
           description
             "Only applies when the type of the tagged
              interface is 'qinany'.";
         }
         if-feature "qinany";
         leaf tag-type {
           type identityref {
             base tag-type;
           }
           default "s-vlan";
           description
             "Tag type.  By default, the tag type is
              's-vlan'.";
         }
         leaf svlan-id {
           type uint16;
           mandatory true;
           description
             "Service VLAN ID.";
         }
         description

Aguado, et al.            Expires May 20, 2020                 [Page 86]
Internet-Draft                    l3nm                     November 2019

           "Container for QinAny.";
       }
       container vxlan {
         when "derived-from-or-self(../type, "
            + "'l3vpn-ntw:vxlan')" {
           description
             "Only applies when the type of the tagged
              interface is 'vxlan'.";
         }
         if-feature "vxlan";
         leaf vni-id {
           type uint32;
           mandatory true;
           description
             "VXLAN Network Identifier (VNI).";
         }
         leaf peer-mode {
           type identityref {
             base vxlan-peer-mode;
           }
           default "static-mode";
           description
             "Specifies the VXLAN access mode.  By default,
              the peer mode is set to 'static-mode'.";
         }
         list peer-list {
           key "peer-ip";
           leaf peer-ip {
             type inet:ip-address;
             description
               "Peer IP.";
           }
           description
             "List of peer IP addresses.";
         }
         description
           "QinQ.";
       }
       description
         "Container for tagged interfaces.";
     }
     container bearer {
      leaf bearer-reference {
       if-feature bearer-reference;
       type string;
        description
        "This is an internal reference for the SP.";
      }

Aguado, et al.            Expires May 20, 2020                 [Page 87]
Internet-Draft                    l3nm                     November 2019

        uses pseudowire-params {
          when "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/"+
          "vpn-node/vpn-network-accesses/vpn-network-access/"+
          "vpn-network-access-type ='pseudowire'"
         {
           description "pseudowire specific parameters";
           }
        }
     description
     "Defines physical properties of a site attachment.";
     }
     description
     "Encapsulation types";
   }
     description
     "Grouping to define encapsulation types";
 }

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

 grouping net-acc{
 container vpn-network-accesses {
      list vpn-network-access {
       key vpn-network-access-id;
       leaf vpn-network-access-id {
        type svc-id;
        description
        "Identifier for the access.";
       }
       leaf description {
         type string;
         description
           "Textual description of a VPN service.";
       }
       uses site-network-access-top-level-cfg;

Aguado, et al.            Expires May 20, 2020                 [Page 88]
Internet-Draft                    l3nm                     November 2019

       description
       "List of accesses for a site.";
      }
      description
      "List of accesses for a site.";
      }
      description
      "Main block of the Network Access.";
 }

  /* Main blocks */
  container l3vpn-ntw {
   container vpn-profiles {
    uses vpn-profile-cfg;
     description
     "Container for VPN Profiles.";
   }
   container vpn-services {
    list vpn-service {
     key vpn-id;
     uses vpn-svc-cfg;
     description
     "List of VPN services.";
    }
    description
    "Top-level container for the VPN services.";
   }
   description
   "Main container for L3VPN service configuration.";
  }
 }
 <CODE ENDS>

                                 Figure 15

8.  IANA Considerations

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

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

      Registrant Contact: The IESG.

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

Aguado, et al.            Expires May 20, 2020                 [Page 89]
Internet-Draft                    l3nm                     November 2019

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

      name: ietf-l3vpn-ntw

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

      maintained by IANA: N

      prefix: l3nm

      reference: RFC XXXX

9.  Security Considerations

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

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

   The ietf-l3vpn-ntw module is used to manage L3 VPNs in a service
   provider backbone network.  Hence, the module can be used to request,
   modify, or retrieve L3VPN services.  For example, the creation of a
   vpn-service leaf instance triggers the creation of an L3 VPN Service
   in a Service Provider Network.

   Due to the foreseen use of the YANG module, there are a number of
   data nodes defined in this YANG module that are writable/creatable/
   deletable (i.e., config true, which is the default).  These data
   nodes MAY be considered sensitive or vulnerable in some network
   environments.  Write operations (e.g., edit-config) and delete
   operations to these data nodes without proper protection or
   authentication can have a negative effect on network operations.
   These are the subtrees and data nodes and their sensitivity/
   vulnerability in the ietf-l3vpn-ntw module:

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

Aguado, et al.            Expires May 20, 2020                 [Page 90]
Internet-Draft                    l3nm                     November 2019

      an attacker may modify the attributes of a running service (e.g.,
      QoS, bandwidth, routing protocols), leading to malfunctioning of
      the service and therefore to SLA violations.  In addition, an
      attacker could attempt to create a L3 VPN Service.  Such activity
      can be detected by monitoring and tracking network configuration
      changes.

   o  COMPLETE rest of critical data nodes and subtrees

   Some of the readable data nodes in this YANG module may be considered
   sensitive or vulnerable in some network environments.  It is thus
   important to control read access (e.g., via get, get-config, or
   notification) to these data nodes.  These are the subtrees and data
   nodes and their sensitivity/vulnerability:

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

   Summing up, the foreseen risks of using the l3vpn-ntw module can be
   clasified into:

   o  Malicious clients attempting to delete or modify services

   o  Unauthorized clients attempting to create/modify/delete a service

   o  Unauthorized clients attempting to read service information

10.  Implementation Status

10.1.  Nokia Implementation

   Nokia has a draft implementation of the IETF L3NM model.

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

   Nokia NSP (Network Services Platform) supports integration of
   standard models with the Intent Manager framework.  NSP platform
   provides hot pluggable model definitions and implementations which
   would enable defining models where standardization is in progress or
   non-existent.  With pluggable architecture for model and
   implementation injections, NSP also serves as a Multi-Layer, Multi-
   Domain controller.

   The Nokia implementation of L3NM covers, the following

Aguado, et al.            Expires May 20, 2020                 [Page 91]
Internet-Draft                    l3nm                     November 2019

   a) RESTConf support

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

   * Site

   * Site-Bearer

   * VpnService

   * IEProfile

   * VpnNode

   * Site Network Access

   * Site Attachments

   c) Supports translations to the Device Model (Standard /
   Properietary)

   draft-ietf-opsawg-l3sm-l3nm-00

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

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

10.2.  Huawei Implementation

   The organization responsible for the implementation, if any.

   Huawei Technologies Co.,Ltd.

   The implementation's name and/or a link to a web page where the
   implementation or a description of it can be found.

   NCE V1R19C00

   A brief general description.

   This section provides an implementation report summary for Layer 3
   VPN Network Model.  Layer 3 VPN Network Model is available at:
   https://tools.ietf.org/html/draft-ietf-opsawg-l3sm-l3nm-00

Aguado, et al.            Expires May 20, 2020                 [Page 92]
Internet-Draft                    l3nm                     November 2019

   The implementation's level of maturity: research, prototype, alpha,
   beta, production, widely used, etc.

   Right now, the data model is still subject to change, therefore it is
   still a Prototype, not put into production yet.

   Coverage: which parts of the protocol specification are implemented.

   We have implemented pruned L3NM model with the following parameters

   module: ietf-l3vpn-ntw
   +--rw l3vpn-ntw
      +--rw vpn-profiles
      |  +--rw valid-provider-identifiers
      |     +--rw qos-profile-identifier* [id]
      |     |  +--rw id    string
      +--rw vpn-services
      |  +--rw vpn-service* [vpn-id]
      |     +--rw vpn-id                  svc-id
      |     +--rw vpn-service-topology?   identityref
      |     +--rw description?            string
      |     +--rw vpn-nodes
      |     |  +--rw vpn-node* [vpn-node-id ne-id]
      |     |     +--rw vpn-node-id        string
      |     |     +--rw description?       string
      |     |     +--rw ne-id              string
      |     |     +--rw node-role?         identityref
      |     |     +--rw rd?                rt-types:route-distinguisher
      |     |     +--rw vpn-targets
      |     |     +--rw maximum-routes
      |     |     |  +--rw address-family* [af]
      |     |     |     +--rw af                address-family
      |     |     |     +--rw maximum-routes?   uint32
      +--rw sites
         +--rw site* [site-id]
            +--rw site-id                  svc-id
            +--rw locations
            |  +--rw location* [location-id]
            |     +--rw location-id     svc-id
            +--rw site-bearers
            |  +--rw bearer* [bearer-id]
            |     +--rw bearer-id    string
            |     +--rw ne-id?       string
            |     +--rw port-id?     string
            +--rw site-network-accesses
               +--rw site-network-access* [site-network-access-id]
                  +--rw site-network-access-id      svc-id
                  +--rw site-network-access-type?   ref

Aguado, et al.            Expires May 20, 2020                 [Page 93]
Internet-Draft                    l3nm                     November 2019

                  +--rw bearer
                  |  +--rw bearer-reference?   {bearer-reference}?
                  |  +--rw connection
                  |  |  +--rw encapsulation-type?   identityref
                  |  |  +--rw tagged-interface
                  |  |     +--rw type?                identityref
                  |  |     +--rw dot1q-vlan-tagged {dot1q}?
                  |  |     |  +--rw cvlan-id    uint16
                  |  |     +--rw qinq {qinq}?
                  |  |     |  +--rw svlan-id    uint16
                  |  |     |  +--rw cvlan-id    uint16
                  +--rw ip-connection
                  |  +--rw ipv4 {ipv4}?
                  |  |  +--rw dhcp-relay
                  |  |  |  +--rw customer-dhcp-servers
                  |  |  |     +--rw server-ip-address*   inet
                  |  |  +--rw addresses
                  |  |     +--rw provider-address?   inet:ipv4-address
                  |  |     +--rw customer-address?   inet:ipv4-address
                  |  |     +--rw prefix-length?      uint8
                  +--rw service
                  |  +--rw qos {qos}?
                  |  |  +--rw qos-profile
                  |  |     +--rw (qos-profile)?
                  |  |        +--:(standard)
                  |  |        |  +--rw profile?   leafreaf
                  +--rw routing-protocols
                  |  +--rw routing-protocol* [type]
                  |     +--rw type                identityref
                  |     +--rw ospf {rtg-ospf}?
                  |     |  +--rw address-family*   address-family
                  |     |  +--rw area-address      yang:dotted-quad
                  |     |  +--rw metric?           uint16
                  |     |  +--rw security
                  |     |  |  +--rw auth-key?   string
                  |     +--rw bgp {rtg-bgp}?
                  |     |  +--rw autonomous-system    uint32
                  |     |  +--rw address-family*      address-family
                  |     |  +--rw neighbor?            inet:ip-address
                  |     |  +--rw multihop?            uint8
                  |     |  +--rw security
                  |     |     +--rw auth-key?   string
                  |     +--rw static
                  |     |  +--rw cascaded-lan-prefixes
                  |     |     +--rw ipv4-lan-prefixes*  {ipv4}?
                  |     |     |  +--rw lan         inet:ipv4-prefix
                  |     |     |  +--rw lan-tag?    string
                  |     |     |  +--rw next-hop    inet:ipv4-address

Aguado, et al.            Expires May 20, 2020                 [Page 94]
Internet-Draft                    l3nm                     November 2019

                  +--rw node-id?                    leafreaf
                  +--rw service-id?                 leafreaf
                  +--rw access-group-id?            yang:uuid

                                 Figure 16

   Use Cases we have implemented include:

   (a).Create VPN

   (b).Create Site

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

   (d).Create/Include Site Network Access into VPN nodes.

   Version compatibility: what version/versions of the Internet-Draft
   are known to be implemented.

   draft-ietf-opsawg-l3sm-l3nm-00

   Licensing: the terms under which the implementation can be used.  For
   example: proprietary, royalty licensing, freely distributable with
   acknowledgement (BSD style), freely distributable with requirement to
   redistribute source (General Public License (GPL) style), and other
   (specify).

   Not available yet.

   Implementation experience: any useful information the implementers
   want to share with the community.

   Contact information: ideally a person's name and email address, but
   possibly just a URL or mailing list.

   Qin Wu (bill.wu@huawei.com)

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

   2019-09-30

   List other implementations that have been tested for
   interoperability.

   Nokia

Aguado, et al.            Expires May 20, 2020                 [Page 95]
Internet-Draft                    l3nm                     November 2019

10.3.  Infinera Implementation

   Infinera has a draft implementation of the IETF L3NM model.  The
   implementation is in beta state and is currently being tested and
   integrated with other suppliers controllers supporting this same
   model.  Infinera is supporting the L3NM model in its Transcend
   Maestro Multi-layer, Multi-domain Controller.

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

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

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

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

11.  Acknowledgements

   Thanks to Adrian Farrel and Miguel Cros for the suggestions on the
   document.  Thanks to Philip Eardlay for the review.  Lots of thanks
   for the discussions on opsawg mailing list and at IETF meeting.

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

12.  Contributors

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

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

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 96]
Internet-Draft                    l3nm                     November 2019

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

   Stephane Litkowski
   Cisco
   Email: slitkows@cisco.com>

13.  References

13.1.  Normative References

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

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

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

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

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

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

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 97]
Internet-Draft                    l3nm                     November 2019

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

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

13.2.  Informative References

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

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

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

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

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

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

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

Aguado, et al.            Expires May 20, 2020                 [Page 98]
Internet-Draft                    l3nm                     November 2019

Authors' Addresses

   Alejandro Aguado
   Nokia
   Madrid
   ES

   Email: alejandro.aguado_martin@nokia.com

   Oscar Gonzalez de Dios (editor)
   Telefonica
   Madrid
   ES

   Email: oscar.gonzalezdedios@telefonica.com

   Victor Lopez
   Telefonica
   Madrid
   ES

   Email: victor.lopezalvarez@telefonica.com

   Daniel Voyer
   Bell Canada
   CA

   Email: daniel.voyer@bell.ca

   Luis Angel Munoz
   Vodafone
   ES

   Email: luis-angel.munoz@vodafone.com

Aguado, et al.            Expires May 20, 2020                 [Page 99]