draft-ietf-opsawg-l3sm-l3nm-00.txt   draft-ietf-opsawg-l3sm-l3nm-01.txt 
Internet Engineering Task Force A. Aguado OPSAWG A. Aguado
Internet-Draft Nokia Internet-Draft Nokia
Intended status: Standards Track O. Gonzalez de Dios, Ed. Intended status: Standards Track O. Gonzalez de Dios, Ed.
Expires: April 20, 2020 V. Lopez Expires: May 20, 2020 V. Lopez
Telefonica Telefonica
D. Voyer D. Voyer
Bell Canada Bell Canada
L. Munoz L. Munoz
Vodafone Vodafone
October 18, 2019 November 17, 2019
Layer 3 VPN Network Model A Layer 3 VPN Network YANG Model
draft-ietf-opsawg-l3sm-l3nm-00 draft-ietf-opsawg-l3sm-l3nm-01
Abstract Abstract
RFC8299 defines a L3VPN Service YANG data Model (L3SM) that can be RFC8299 defines a L3VPN Service YANG data Model (L3SM) that can be
used for communication between customers and network operators. Such used for communication between customers and VPN service providers.
model is adequate for the customer to network operator conversation That data model plays the role of a Customer Service Model, according
and plays the role of a Customer Service Model, according to the to the terminology defined in RFC8309, and is as such adequate for
terminology defined in RFC8309. service negotiation and order handling matters.
There is a need for a YANG model to be used in the communication There is a need for a more network-centric YANG data model to be used
between the entity that interacts directly with the customer, the in the communication between the entity that interacts directly with
service orchestrator, (either fully automated or a human operator) the customer, the service orchestrator, (either fully automated or a
and the entity in charge of network orchestration and control (aka human operator) and the entity in charge of network orchestration and
network controller / orchestrator). control (a.k.a., network controller/orchestrator).
This document proposes a L3VPN Network Yang Model (L3NM) to This document specifies a L3VPN Network YANG Model (L3NM) to
facilitate communication between a service orchestrator and a network facilitate communication between a service orchestrator and a network
controller / orchestrator. The resulting model is called the L3VPN controller/orchestrator. Such data model provides a network-centric
Network Model (L3NM) and provides a network-centric view of the L3VPN view of the L3VPN services. The Yang model proposed is limited to
services. BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364.
Editorial Note (To be removed by RFC Editor)
Please update these statements within the document with the RFC
number to be assigned to this document:
o "This version of this YANG module is part of RFC XXXX;"
o "RFC XXXX: Layer 3 VPN Network Model";
o reference: RFC XXXX
Also, please update the "revision" date of the YANG module.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 20, 2020. This Internet-Draft will expire on May 20, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. TERMINOLOGY . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 5
2. REFERENCE ARCHITECTURE . . . . . . . . . . . . . . . . . . . 4 2. Reference Architecture . . . . . . . . . . . . . . . . . . . 6
3. YANG MODEL EXPLANATION . . . . . . . . . . . . . . . . . . . 6 3. Description of the L3NM YANG Module . . . . . . . . . . . . . 8
3.1. STRUCTURE OF THE MODEL . . . . . . . . . . . . . . . . . 7 3.1. Structure of the Module . . . . . . . . . . . . . . . . . 9
3.2. SITE AND BEARERS . . . . . . . . . . . . . . . . . . . . 7 3.2. Modeling a L3 VPN Service . . . . . . . . . . . . . . . . 9
3.3. BEARER AND ETHERNET ENCAPSULATION . . . . . . . . . . . . 7 3.2.1. VPN node . . . . . . . . . . . . . . . . . . . . . . 10
3.4. MULTI-DOMAIN RESOURCE MANAGEMENT . . . . . . . . . . . . 7 3.2.1.1. VPN Network Access . . . . . . . . . . . . . . . 11
3.5. REMOTE FAR-END CONFIGURATION . . . . . . . . . . . . . . 8 3.2.1.1.1. Connection . . . . . . . . . . . . . . . . . 11
3.6. PROVIDE EDGE IDENTIFICATION POINT . . . . . . . . . . . . 8 3.2.1.1.2. IP Connection . . . . . . . . . . . . . . . . 13
4. DESING OF THE DATA MODEL . . . . . . . . . . . . . . . . . . 9 3.2.1.1.3. Routing Protocols . . . . . . . . . . . . . . 14
5. YANG MODULE . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.2.2. Concept of Import/Export Profiles . . . . . . . . . . 15
6. IANA CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . . 93 3.2.3. Multicast . . . . . . . . . . . . . . . . . . . . . . 16
7. SECURITY CONSIDERATIONS . . . . . . . . . . . . . . . . . . . 93
8. IMPLEMENTATION STATUS . . . . . . . . . . . . . . . . . . . . 93
9. ACKNOWLEDGEMENTS . . . . . . . . . . . . . . . . . . . . . . 94
10. CONTRIBUTORS . . . . . . . . . . . . . . . . . . . . . . . . 94
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 94
11.1. NORMATIVE REFERENCES . . . . . . . . . . . . . . . . . . 94
11.2. INFORMATIVE REFERENCES . . . . . . . . . . . . . . . . . 94
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 95
1. INTRODUCTION 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
[RFC8299] defines a L3VPN Service YANG data Model (L3SM) model that 1. Introduction
can be used for communication between customers and network
operators. Such model is focused on describing the customer view of
the services, and provides an abstracted view of the customer's
requested services. That aproach limits the usage of the L3SM to the
role of a Customer Service Model, according to the terminology
defined in [RFC8309].
The YANG data model proposed in this document is called the L3VPN [RFC8299] defines an L3VPN Service YANG data Model (L3SM) that can be
Network Model (L3NM). The L3NM model is aimed at providing a used for communication between customers and network operators. Such
network-centric view of L3 VPN Services. The model can be used to model is focused on describing the customer view of the VPN services,
facilitate communication between the service orchestrator, and the and provides an abstracted view of the customer's requested services.
network controller / orchestrator. It enables further capabilities, That aproach limits the usage of the L3SM module to the role of a
such as resource management or to serve as a multi-domain Customer Service Model, according to the terminology defined in
orchestration interface, where transport resources must be [RFC8309].
synchronized. The YANG module has been built with a prune and extend
approach, taking as a starting points the YANG model described in
[RFC8299].
Hence, this document does not obsolete, but complements, the The YANG data model defined in this document is called L3VPN Network
definitions in [RFC8299]. It aims to provide a different scope for Model (L3NM). The L3NM module is aimed at providing a network-
the L3SM, but does not attempt to address all deployment cases 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.
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 especially those where the L3VPN connectivity is supported through
the coordination of different VPNs in different underlying networks. the coordination of different VPNs in different underlying networks.
More complex deployment scenarios involving the coordination of More complex deployment scenarios involving the coordination of
different VPN instances and different technologies to provide end-to- different VPN instances and different technologies to provide end-to-
end VPN connectivity are addressed by a complementary YANG model end VPN connectivity are addressed by a complementary YANG model
defined in [I-D.evenwu-opsawg-yang-composed-vpn]. defined in [I-D.evenwu-opsawg-yang-composed-vpn].
1.1. TERMINOLOGY 1.1. Terminology
This document assumes that the reader is familiar with the contents This document assumes that the reader is familiar with the contents
of [RFC6241], [RFC7950], [RFC8299], [RFC8309], and [RFC8453] and uses of [RFC6241], [RFC7950], [RFC8299], [RFC8309], and [RFC8453] and uses
terminology from those documents. Tree diagrams used in this the terminology defined in those documents.
document follow the notation defined in [RFC8340].
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
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 1.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. REFERENCE ARCHITECTURE 2. Reference Architecture
Figure 1 shows where the L3NM is used in a management stack. The Figure 1 depices the reference architecture for L3NM. The figure is
figure is an expansion of the architecture presented in Section 5 of an expansion of the architecture presented in Section 5 of [RFC8299]
[RFC8299] and decomposes the box marked "orchestration" in that and decomposes the box marked "orchestration" in that figure into
figure into three separate functional components called "Service three separate functional components called "Service Orchestration",
Orchestration", "Network Orchestration", and "Domain Orchestration". "Network Orchestration", and "Domain Orchestration".
Note that some implementations may choose to construct a monolithic Although some deployments may choose to construct a monolithic
orchestration component, but this document assumes that there are orchestration component (covering both service and network matters),
many benefits for flexiblity of implementation and deployment to this document advocates for a clear separation between service and
separate the functional components, and that separation demands the network orchestration components for the sake of better flexibility.
existence of sepearate YANG models to be used between the components. 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).
At the same time, terminology from [RFC8309] is introduced to show The intelligence for translating customer-facing information into
the distinction between the "Customer Service Model", the "Service network-centric one is implementation-specific.
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".
+---------------+ 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".
+---------------+
| Customer | | Customer |
+---------------+ +---------------+
Customer Service Model | Customer Service Model |
l3vpn-svc | l3vpn-svc |
+---------------+ +---------------+
| Service | | Service |
| Orchestration | | Orchestration |
+---------------+ +---------------+
Service Delivery Model | L3NM Network Model |
l3nm-svc | l3vpn-ntw |
(l3vpn-svc + extensions) |
+---------------+ +---------------+
| Network | | Network |
| Orchestration | | Orchestration |
+---------------+ +---------------+
Network Configuration Model | Network Configuration Model |
__________|____________ __________|____________
| | | |
+---------------+ +---------------+ +---------------+ +---------------+
| Domain | | Domain | | Domain | | Domain |
| Orchestration | | Orchestration | | Orchestration | | Orchestration |
skipping to change at page 5, line 43 skipping to change at page 7, line 42
| Manager | | | | Manager | | |
+---------+ | | +---------+ | |
| | | | | |
| NETCONF/CLI.................. | NETCONF/CLI..................
| | | | | |
+------------------------------------------------+ +------------------------------------------------+
Network Network
Figure 1: L3SM and L3NM Figure 1: L3SM and L3NM
The L3SM and L3NM may also be set in the context of the ACTN The L3SM and L3NM modules may also be set in the context of the ACTN
architecture [RFC8453]. Figure 2 shows the Customer Network architecture [RFC8453]. Figure 2 shows the Customer Network
Controller (CNC), the Multi-Domain Service Coordinator (MDSC), and Controller (CNC), the Multi-Domain Service Coordinator (MDSC), and
the Provisioning Network Controller (PNC). It also shows the the Provisioning Network Controller (PNC). It also shows the
interfaces between these functional units: the CNC-MDSC Interface interfaces between these functional blocks: the CNC-MDSC Interface
(CMI), the MDSC-PNC Interface (MPI), and the Southbound Interface (CMI), the MDSC-PNC Interface (MPI), and the Southbound Interface
(SBI). (SBI).
---------------------------------- +----------------------------------+
| Customer | | Customer |
| ----------------------------- | | +-----------------------------+ |
| | CNC | | | | CNC | |
| ----------------------------- | | +-----------------------------+ |
----:-----------------------:----- +----:-----------------------:-----+
: : : :
: L3SM : L3SM : L3SM : L3SM
: : : :
---------:--------- ------------------- +---------:---------+ +-------------------+
| MDSC : | | MDSC | | MDSC : | | MDSC |
| --------------- | | (parent) | | +---------------+ | | (parent) |
| | Service | | ------------------- | | Service | | +-------------------+
| | Orchestration | | : | | Orchestration | | :
| --------------- | : L3NM | +---------------+ | : L3NM
| : | : | : | :
| : L3NM | ------------------- | : L3NM | +-------------------+
| : | | MDSC | | : | | MDSC |
| --------------- | | (child) | | +---------------+ | | (child) |
| | Network | | ------------------- | | Network | | +-------------------+
| | Orchestration | | : | | Orchestration | | :
| --------------- | : | +---------------+ | :
---------:--------- : ---------:--------- :
: : : :
: Network Configuration : : Network Configuration :
: : : :
------------:------- ---------:------------ +------------:-------+ +---------:------------+
| Domain : | | : Domain | | Domain : | | : Domain |
| Controller : | | : Controller | | Controller : | | : Controller |
| --------- | | --------- | | +---------+ | | +---------+ |
| | PNC | | | | PNC | | | | PNC | | | | PNC | |
| --------- | | --------- | | +---------+ | | +---------+ |
------------:------- ---------:------------ +------------:-------+ +---------:------------+
: : : :
: Device Configuration : : Device Configuration :
: : : :
-------- -------- +--------+ +--------+
| Device | | Device | | Device | | Device |
-------- -------- +--------+ +--------+
Figure 2: L3SM and L3NM in the Context of ACTN Figure 2: L3SM and L3NM in the Context of ACTN
3. YANG MODEL EXPLANATION 3. Description of the L3NM YANG Module
The scenarios covered in the L3NM model includes: the integration of The L3NM module ('ietf-l3vpn-ntw') is meant to manage L3 VPNs in a
Ethernet and encapsulation parameters, the extension for transport service provider network. In particular, the 'ietf-l3vpn-ntw' module
resources (e.g., Route targets and Route distinguishers) to be can be used to create, modify, and retrieve L3VPN Services of a
orchestrated from the management system, far-end configuration of PEs network.
not managed by the management system and the definition for PE
identification.
3.1. STRUCTURE OF THE MODEL 3.1. Structure of the Module
The YANG module is divided into three main containers: "vpn- The 'ietf-l3vpn-ntw' module uses two main containers: 'vpn-services'
services","sites" and "vpn-profiles". 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.
3.2. SITE AND BEARERS The 'vpn-profiles' container allows the provider to maintain a set of
commmon VPN profiles that apply to several VPN Services.
A site, as per [RFC8299], represents a connection of a customer module: ietf-l3vpn-ntw
office to one or more VPN services. As this YANG module, is the +--rw l3vpn-ntw
network view, each site is associated with a list of bearers. A +--rw vpn-profiles
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 +--rw vpn-services
(e.g., by the service orchestrator). The bearer is associated to a +--rw vpn-service* [vpn-id]
network element and a port. Hence, a bearer is not just a bearer- ........
reference, but also a true reference to a given port in the service
provider network.
3.3. BEARER AND ETHERNET ENCAPSULATION 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.
+--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.
+--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 The definition of a L3VPN is commonly specified not only at the IP
layer, but also requires to identify parameters at the Ethernet layer, but also requires to identify parameters at the Ethernet
layer, such as encapsulation type (e.g., VLAN, QinQ, QinAny, VxLAN, layer, such as encapsulation type (e.g., VLAN, QinQ, QinAny, VxLAN,
etc.). This specification is not supported in [RFC8299], whilst it etc.). The 'connection' container represents and groups the set of
suggests that any extension on this direction shall be implemented L2 connectivity from where the traffic of the L3VPN in a particular
via augmentation of the bearer container. The extension defined to VPN Network access is coming.
cope with these parameters uses the connection container inside the
site-network-access defined by the [RFC8466]. This container defines
protocol parameters to enable connectivity at Layer 2. In the
context of L3SM, the augmentation includes only mandatory parameters
for the service configuration, which are mainly related to the
interface encapsulation. Other definitions from L2SM connection
container are left aside. For example, Link Aggregation (LAG)
information is not required and it shall be configured prior to the
service configuration, being the aggregated interface identified in
the model as the bearer-reference, as discussed later in Section 3.4.
3.4. MULTI-DOMAIN RESOURCE MANAGEMENT Additionally, the bearer-reference (Section 3.2.1.1.1.3) and the
pseudowire termination (Section 3.2.1.1.1.2) is supported.
3.2.1.1.1.1. Encapsulation options
Ethernet encapsulation description is not supported in [RFC8299].
However, this parameters are mandatory to configure the PE
interfaces. Thus, In the L3NM, these parameters uses the connection
container inside the vpn-network-access. This container defines
protocols and parameters to enable connectivity at Layer 2.
+--rw connection
+--rw 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.
+--rw bearer
+--rw connection
...
+--rw pseudowire
+--rw vcid? uint32
Figure 7
3.2.1.1.1.3. Bearers
A site, as per [RFC4176] represents a VPN customer's location that is
connected to the Service Provider network via a CE-PE link, which can
access at least one VPN. The connection from the site to the Service
Provider network is the bearer. Every site is associated with a list
of bearers. A bearer is the layer two connections with the site. In
the module it is assumed that the bearer has been allocated by the
Service Provider at the service orchestration step. The bearer is
associated to a network element and a port. Hence, a bearer is just
a bearer-reference to allow the translation between L3SM and L3NM.
3.2.1.1.2. IP Connection
IP Connection container has the parameters of the vpn-network-access
addressing information. The address allocated in this container
would represent the PE interface address configuration. The IP
Connection container is designed to support dual stack (IPv4/IPv6)
and three options to set the ip address: Provider DHCP, DHCP relay or
static addressing.
In the case of the static addressing the model supports the
assignation of several IP addresses in the same vpn-network-access.
To identify which of the addresses is the primary address of the
connection the "primary-address" reference must be set with the
corresponding address-id.
+--rw 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.
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.
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
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
| | +--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}?
| | | | +--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
| | | | | +--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
| | | +--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
| | | | +--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
+--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 The implementation of L3VPN services which span across
administratively separated domains (i.e., that are under the administratively separated domains (i.e., that are under the
administration of different management systems or controllers) administration of different management systems or controllers)
requires some network resources to be synchronized between systems. requires some network resources to be synchronized between systems.
Particularly, there are two resources that must be orchestrated and Particularly, there are two resources that must be orchestrated and
manage to avoid asymmetric (non-functional) configuration, or the manage to avoid asymmetric (non-functional) configuration, or the
usage of unavailable resources. For example, RTs shall be usage of unavailable resources. For example, RTs shall be
synchronized between PEs. When every PE is controlled by the same synchronized between PEs. When every PE is controlled by the same
management system, RT allocation can be performed by the system. In management system, RT allocation can be performed by the system. In
cases where the service spans across multiple management systems, cases where the service spans across multiple management systems,
this task of allocating RTs has to be aligned across the domains, this task of allocating RTs has to be aligned across the domains,
therefore, the service model must provide a way to specify RTs. In therefore, the service model must provide a way to specify RTs. In
addition, RDs must also be synchronized to avoid collisions in RD addition, RDs must also be synchronized to avoid collisions in RD
allocation between separate systems. An incorrect allocation might allocation between separate systems. An incorrect allocation might
lead to the same RD and IP prefixes being exported by different PE lead to the same RD and IP prefixes being exported by different PE
routers. routers.
3.5. REMOTE FAR-END CONFIGURATION 5. Relation with other Yang Models
Depending on the control plane implementation, different network The L3NM model, aimed at managing the L3VPN Services in a Service
scenarios might require additional information for the L3VPN service Provider Network controller/orchestrator has relations with other
to be configured and active. For example, an L3VPN Option C service, Yang modules.
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.
3.6. PROVIDE EDGE IDENTIFICATION POINT 5.1. Relation with L3SM
[RFC8299] states that the "bearer-reference" parameter is used in [RFC8299] defines a L3VPN Service YANG data Model (L3SM) that can be
cases where the customer has already ordered a network connection to used for communication between customers and VPN service providers.
the service provider (SP) apart from the IP VPN site and wants to Hence, the model provides inputs to the Network Operator to deliver
reuse this connection. The string used is an internal reference from such service to the customer. Hence, some parts of the model can be
the SP and describes the already-available connection. Usually, a directly mapped into L3NM.
client interface (either a customer one or an interface used by the
SP) is already in place and connected, although it has not being use
previously. In some other cases (e.g., for stitching purposes), the
termination of a VPN service is done over logical terminations within
a PE router.
The bearer-reference must serve as a strict unequivocal parameters to o Routing protocols requested by the client at PE-CE interface. In
identify the connection between a PE and a client (CE). This means sake of alignment, the same protocols are supported.
that, despite the type is maintained as a string and there is no
restriction in the way this data is formed, the bearer-reference must
serve as the unique way to identify the PE router and the client
interface. This, together with the encapsulation augments proposed
in Section 3.2, serves as the way to identify the client interface
and configure L2 specific parameters.
4. DESING OF THE DATA MODEL 5.2. Relation with Network Topology
The augmentations defined in this document are organised per The L3NM model manages VPN Services running over Service Provider
scenario, as defined in Section 3. The case described Section 3.4 Backbone network. The set of nodes over which it is possible to
does not need any further extension of the data model and only deploy a L3 VPN Service MAY be part of the topology contained in an
requires a more restricted definition on how the data model is used ietf-network module.
for PE router and client port identification, so no augmentation is
implemented for this scenario.
The augmentations implemented are distributed as follows: 5.3. Relation with Device Models
o An extension including RT and RD definition for the L3VPN, Creating services in the l3vpn-ntw module will will lead at some
following the YANG definitions from BESS-L3VPN. This extension point to the configuration of devices. Hence, it is foreseen that
was developed creating a container "ie-profiles" under the VPN the data for the device yang modules will be derived partially from
Service. All the import-export information can be created and the L3NM vpn-service container. Note that L3NM is NOT a device
reused for several VPN-Nodes. model.
* If the "ie-profile" is empty the domain controller should 6. L3VPN Examples
automatically assing RD and RTs. This is not valid for a
multi-domain scenario
o The second augmentation copes with the information from a remote 6.1. 4G VPN Provissioning Example
PE not directly under management system supervision. This
augmentation does not follow any previously defined model and
includes the loopback IP address of the external router.
o The third augmentation copes with a pseudowire termination under a The L3VPN service defined in this draft provides a multipoint, routed
VPN service. This termination requires the management of the service to the customer over an IP/MPLS core. The L3VPNs are widely
Virtual Circuit Identifier under the VPN service. 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.
o Access-group-id has been added within the site network access in As it is shown in the Figure 11, commonly the eNODEB (CE) is directly
order to allow associations between interfaces that have similar connected to the access routers (DCSG) of the mobile backhaul and
behaviors. For example, identify two interfaces in dual homing their logical interfaces (one or many according to the Service type)
distribution. are configured in a VPN that transport the packets to the mobile core
platforms.
o The last augmentation includes information below layer 3 that is +--------------+
required for the service. In particular, we include information +------+ +-----+ +-----+ +-----+ | Platforms |
related to clients interface encapsulation and aggregation. |eNODEB|--/-| PE |----| P |----| PE |----| (SGW/MME) |
+------+ +-----+ +-----+ +-----+ | ... |
+--------------+
The high-level model structure defined by this document is as shown Figure 11: Mobile Backhaul Example
below:
|-------------------- EXAMPLE --------------------| To configure a L3VPN service using the L3NM model the procedure and
the JSON with the data structure is the following:
module: ietf-l3vpn-ntw Create VPN Service
+--rw l3vpn-ntw <vpn-services>
+--rw vpn-profiles <vpn-service>
| +--rw valid-provider-identifiers <vpn-id>1</vpn-id>
| +--rw cloud-identifier* [id] {cloud-access}? <customer-name>4G</customer-name>
| | +--rw id string <vpn-service-topology>hub-spoke</vpn-service-topology>
| +--rw encryption-profile-identifier* [id] <description>4G</description>
| | +--rw id string </vpn-service>
| +--rw qos-profile-identifier* [id] </vpn-services>
| | +--rw id string </l3vpn-ntw>
| +--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 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-target* [route-target]
| | | +--rw route-target rt-types:route-target
| | | +--rw route-target-type rt-types:route-target-type
| | +--rw status
| | | +--rw admin-enabled? boolean
| | | +--ro oper-status? operational-type
| | +--rw maximum-routes
| | | +--rw address-family* [af]
| | | +--rw af address-family
| | | +--rw maximum-routes? uint32
| | +--rw node-ie-profile? -> /l3vpn-ntw/vpn-services/vpn-service/ie-profiles/ie-profile/ie-profile-id
| +--rw cloud-accesses {cloud-access}?
| | +--rw cloud-access* [cloud-identifier]
| | +--rw cloud-identifier -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/cloud-identifier/id
| | +--rw (list-flavor)?
| | | +--:(permit-any)
| | | | +--rw permit-any? empty
| | | +--:(deny-any-except)
| | | | +--rw permit-site* -> /l3vpn-ntw/sites/site/site-id
| | | +--:(permit-any-except)
| | | +--rw deny-site* -> /l3vpn-ntw/sites/site/site-id
| | +--rw address-translation
| | +--rw nat44
| | +--rw enabled? boolean
| | +--rw nat44-customer-address? inet:ipv4-address
| +--rw multicast {multicast}?
| | +--rw enabled? boolean
| | +--rw customer-tree-flavors
| | | +--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
| | +--rw rp-discovery
| | +--rw rp-discovery-type? identityref
| | +--rw bsr-candidates
| | +--rw bsr-candidate-address* inet:ip-address
| +--rw carrierscarrier? boolean {carrierscarrier}?
| +--rw extranet-vpns {extranet-vpn}?
| +--rw extranet-vpn* [vpn-id]
| +--rw vpn-id svc-id
| +--rw local-sites-role? identityref
+--rw sites
+--rw site* [site-id]
+--rw site-id svc-id
+--rw description? string
+--rw requested-site-start? yang:date-and-time
+--rw requested-site-stop? yang:date-and-time
+--rw locations
| +--rw location* [location-id]
| +--rw location-id svc-id
| +--rw address? string
| +--rw postal-code? string
| +--rw state? string
| +--rw city? string
| +--rw country-code? string
+--rw devices
| +--rw device* [device-id]
| +--rw device-id svc-id
| +--rw location -> ../../../locations/location/location-id
| +--rw management
| +--rw address-family? address-family
| +--rw address inet:ip-address
+--rw site-diversity {site-diversity}?
| +--rw groups
| +--rw group* [group-id]
| +--rw group-id string
+--rw management
| +--rw type identityref
+--rw site-vpn-flavor? identityref
+--rw maximum-routes
| +--rw address-family* [af]
| +--rw af address-family
| +--rw maximum-routes? uint32
+--rw security
| +--rw authentication
| +--rw encryption {encryption}?
| | +--rw enabled? boolean
| | +--rw layer? enumeration
| +--rw encryption-profile
| +--rw (profile)?
| | +--:(provider-profile)
| | | +--rw profile-name? -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/encryption-profile-identifier/id
| | +--:(customer-profile)
| | +--rw algorithm? string
| +--rw (key-type)?
| +--:(psk)
| +--rw preshared-key? string
+--rw service
| +--rw qos {qos}?
| | +--rw qos-classification-policy
| | | +--rw rule* [id]
| | | +--rw id string
| | | +--rw (match-type)?
| | | | +--:(match-flow)
| | | | | +--rw match-flow
| | | | | +--rw dscp? inet:dscp
| | | | | +--rw dot1p? uint8
| | | | | +--rw ipv4-src-prefix? inet:ipv4-prefix
| | | | | +--rw ipv6-src-prefix? inet:ipv6-prefix
| | | | | +--rw ipv4-dst-prefix? inet:ipv4-prefix
| | | | | +--rw ipv6-dst-prefix? inet:ipv6-prefix
| | | | | +--rw l4-src-port? inet:port-number
| | | | | +--rw target-sites* svc-id {target-sites}?
| | | | | +--rw l4-src-port-range
| | | | | | +--rw lower-port? inet:port-number
| | | | | | +--rw upper-port? inet:port-number
| | | | | +--rw l4-dst-port? inet:port-number
| | | | | +--rw l4-dst-port-range
| | | | | | +--rw lower-port? inet:port-number
| | | | | | +--rw upper-port? inet:port-number
| | | | | +--rw protocol-field? union
| | | | +--:(match-application)
| | | | +--rw match-application? identityref
| | | +--rw target-class-id? string
| | +--rw qos-profile
| | +--rw (qos-profile)?
| | +--:(standard)
| | | +--rw profile? -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/qos-profile-identifier/id
| | | +--rw direction? identityref
| | +--:(custom)
| | +--rw classes {qos-custom}?
| | +--rw class* [class-id]
| | +--rw class-id string
| | +--rw direction? identityref
| | +--rw rate-limit? decimal64
| | +--rw latency
| | | +--rw (flavor)?
| | | +--:(lowest)
| | | | +--rw use-lowest-latency? empty
| | | +--:(boundary)
| | | +--rw latency-boundary? uint16
| | +--rw jitter
| | | +--rw (flavor)?
| | | +--:(lowest)
| | | | +--rw use-lowest-jitter? empty
| | | +--:(boundary)
| | | +--rw latency-boundary? uint32
| | +--rw bandwidth
| | +--rw guaranteed-bw-percent decimal64
| | +--rw end-to-end? empty
| +--rw carrierscarrier {carrierscarrier}?
| | +--rw signalling-type? enumeration
| +--rw multicast {multicast}?
| +--rw multicast-site-type? enumeration
| +--rw multicast-address-family
| | +--rw ipv4? boolean {ipv4}?
| | +--rw ipv6? boolean {ipv6}?
| +--rw protocol-type? enumeration
+--rw traffic-protection {fast-reroute}?
| +--rw enabled? boolean
+--rw routing-protocols
| +--rw routing-protocol* [type]
| +--rw type identityref
| +--rw routing-profiles* [id]
| | +--rw id -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id
| | +--rw type? ie-type
| +--rw ospf {rtg-ospf}?
| | +--rw address-family* address-family
| | +--rw area-address yang:dotted-quad
| | +--rw metric? uint16
| | +--rw mtu? 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
| | | +--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
+--ro actual-site-start? yang:date-and-time
+--ro actual-site-stop? yang:date-and-time
+--rw site-bearers
| +--rw bearer* [bearer-id]
| +--rw bearer-id string
| +--rw BearerType? identityref
| +--rw ne-id? string
| +--rw port-id? string
| +--rw lag-id? string
+--rw site-network-accesses
+--rw site-network-access* [site-network-access-id]
+--rw site-network-access-id svc-id
+--rw description? string
+--rw status
| +--rw admin-enabled? boolean
| +--ro oper-status? operational-type
+--rw site-network-access-type? identityref
+--rw (location-flavor)
| +--:(location)
| | +--rw location-reference? -> ../../../locations/location/location-id
| +--:(device)
| +--rw device-reference? -> ../../../devices/device/device-id
+--rw access-diversity {site-diversity}?
| +--rw groups
| | +--rw group* [group-id]
| | +--rw group-id string
| +--rw constraints
| +--rw constraint* [constraint-type]
| +--rw constraint-type identityref
| +--rw target
| +--rw (target-flavor)?
| +--:(id)
| | +--rw group* [group-id]
| | +--rw group-id string
| +--:(all-accesses)
| | +--rw all-other-accesses? empty
| +--:(all-groups)
| +--rw all-other-groups? empty
+--rw bearer
| +--rw requested-type {requested-type}?
| | +--rw requested-type? string
| | +--rw strict? boolean
| +--rw always-on? boolean {always-on}?
| +--rw bearer-reference? string {bearer-reference}?
| +--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 pseudowire
| +--rw vcid? uint32
+--rw ip-connection
| +--rw ipv4 {ipv4}?
| | +--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 addresses
| | +--rw provider-address? inet:ipv4-address
| | +--rw customer-address? inet:ipv4-address
| | +--rw prefix-length? uint8
| +--rw ipv6 {ipv6}?
| | +--rw address-allocation-type? identityref
| | +--rw provider-dhcp
| | | +--rw provider-address? inet:ipv6-address
| | | +--rw prefix-length? uint8
| | | +--rw (address-assign)?
| | | +--:(number)
| | | | +--rw number-of-dynamic-address? uint16
| | | +--:(explicit)
| | | +--rw customer-addresses
| | | +--rw address-group* [group-id]
| | | +--rw group-id string
| | | +--rw start-address? inet:ipv6-address
| | | +--rw end-address? inet:ipv6-address
| | +--rw dhcp-relay
| | | +--rw provider-address? inet:ipv6-address
| | | +--rw prefix-length? uint8
| | | +--rw customer-dhcp-servers
| | | +--rw server-ip-address* inet:ipv6-address
| | +--rw addresses
| | +--rw provider-address? inet:ipv6-address
| | +--rw customer-address? inet:ipv6-address
| | +--rw prefix-length? uint8
| +--rw oam
| +--rw bfd {bfd}?
| +--rw enabled? boolean
| +--rw (holdtime)?
| +--:(fixed)
| | +--rw fixed-value? uint32
| +--:(profile)
| +--rw profile-name? -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/bfd-profile-identifier/id
+--rw security
| +--rw authentication
| +--rw encryption {encryption}?
| | +--rw enabled? boolean
| | +--rw layer? enumeration
| +--rw encryption-profile
| +--rw (profile)?
| | +--:(provider-profile)
| | | +--rw profile-name? -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/encryption-profile-identifier/id
| | +--:(customer-profile)
| | +--rw algorithm? string
| +--rw (key-type)?
| +--:(psk)
| +--rw preshared-key? string
+--rw service
| +--rw svc-input-bandwidth uint64
| +--rw svc-output-bandwidth uint64
| +--rw svc-mtu uint16
| +--rw qos {qos}?
| | +--rw qos-classification-policy
| | | +--rw rule* [id]
| | | +--rw id string
| | | +--rw (match-type)?
| | | | +--:(match-flow)
| | | | | +--rw match-flow
| | | | | +--rw dscp? inet:dscp
| | | | | +--rw dot1p? uint8
| | | | | +--rw ipv4-src-prefix? inet:ipv4-prefix
| | | | | +--rw ipv6-src-prefix? inet:ipv6-prefix
| | | | | +--rw ipv4-dst-prefix? inet:ipv4-prefix
| | | | | +--rw ipv6-dst-prefix? inet:ipv6-prefix
| | | | | +--rw l4-src-port? inet:port-number
| | | | | +--rw target-sites* svc-id {target-sites}?
| | | | | +--rw l4-src-port-range
| | | | | | +--rw lower-port? inet:port-number
| | | | | | +--rw upper-port? inet:port-number
| | | | | +--rw l4-dst-port? inet:port-number
| | | | | +--rw l4-dst-port-range
| | | | | | +--rw lower-port? inet:port-number
| | | | | | +--rw upper-port? inet:port-number
| | | | | +--rw protocol-field? union
| | | | +--:(match-application)
| | | | +--rw match-application? identityref
| | | +--rw target-class-id? string
| | +--rw qos-profile
| | +--rw (qos-profile)?
| | +--:(standard)
| | | +--rw profile? -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/qos-profile-identifier/id
| | | +--rw direction? identityref
| | +--:(custom)
| | +--rw classes {qos-custom}?
| | +--rw class* [class-id]
| | +--rw class-id string
| | +--rw direction? identityref
| | +--rw rate-limit? decimal64
| | +--rw latency
| | | +--rw (flavor)?
| | | +--:(lowest)
| | | | +--rw use-lowest-latency? empty
| | | +--:(boundary)
| | | +--rw latency-boundary? uint16
| | +--rw jitter
| | | +--rw (flavor)?
| | | +--:(lowest)
| | | | +--rw use-lowest-jitter? empty
| | | +--:(boundary)
| | | +--rw latency-boundary? uint32
| | +--rw bandwidth
| | +--rw guaranteed-bw-percent decimal64
| | +--rw end-to-end? empty
| +--rw carrierscarrier {carrierscarrier}?
| | +--rw signalling-type? enumeration
| +--rw multicast {multicast}?
| +--rw multicast-site-type? enumeration
| +--rw multicast-address-family
| | +--rw ipv4? boolean {ipv4}?
| | +--rw ipv6? boolean {ipv6}?
| +--rw protocol-type? enumeration
+--rw routing-protocols
| +--rw routing-protocol* [type]
| +--rw type identityref
| +--rw routing-profiles* [id]
| | +--rw id -> /l3vpn-ntw/vpn-profiles/valid-provider-identifiers/routing-profile-identifier/id
| | +--rw type? ie-type
| +--rw ospf {rtg-ospf}?
| | +--rw address-family* address-family
| | +--rw area-address yang:dotted-quad
| | +--rw metric? uint16
| | +--rw mtu? 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
| | | +--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 availability
| +--rw access-priority? uint32
+--rw node-id? -> /l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn-node-id
+--rw service-id? -> /l3vpn-ntw/vpn-services/vpn-service/vpn-id
+--rw access-group-id? yang:uuid
Figure 3
5. YANG MODULE Figure 12: Create VPN Service
|-------------------- EXAMPLE --------------------| Create VPN Node: For this type of service the VPN Node is equivalent
with the VRF configured in the physical device.
<CODE BEGINS>file "ietf-l3vpn-ntw@2019-09-13.YANG" <vpn-nodes>
module ietf-l3vpn-ntw { <vpn-node>
yang-version 1.1; <vpn-node-id>1</vpn-node-id>
namespace "urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw"; <ne-id>10.0.0.1</ne-id>
prefix l3vpn-ntw; <autonomous-system>65000</autonomous-system>
import ietf-inet-types { <description>4G</description>
prefix inet; <router-id>10.0.0.1</router-id>
} <address-family>ipv4</address-family>
import ietf-yang-types { <node-role>any-to-any-role</node-role>
prefix yang; <rd>1:1</rd>
} </vpn-node>
import ietf-netconf-acm { </vpn-nodes>
prefix nacm;
}
import ietf-routing-types {
prefix rt-types;
}
organization
"Individual draft";
contact
"Currently discussed in WG List: <mailto:opsawg@ietf.org>
Editor: Oscar Gonzalez de Dios
<mailto:oscar.gonzalezdedios@telefonica.com>";
description Figure 13: Create VPN Node
"This YANG module defines a generic network-oriented model
for the configuration of Layer 3 VPNs.
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 Create VPN Network Access
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 <vpn-network-accesses>
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself <vpn-network-access>
for full legal notices. <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>
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL Figure 14: Create VPN Network Access
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.";
revision 2019-09-24 { 7. Yang Module
description
"Initial document. The document as a whole is based on L3SM <CODE BEGINS> file "ietf-l3vpn-ntw@2019-11-17.yang"
module, defined in RFC 8299, modified to fit the requirements module ietf-l3vpn-ntw {
of the platforms at the network layer."; yang-version 1.1;
reference namespace "urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw";
"RFC 8049."; prefix l3vpn-ntw;
import ietf-inet-types {
prefix inet;
} }
/* Features */ import ietf-yang-types {
feature cloud-access { prefix yang;
description
"Allows the VPN to connect to a CSP.";
}
feature multicast {
description
"Enables multicast capabilities in a VPN.";
}
feature ipv4 {
description
"Enables IPv4 support in a VPN.";
}
feature ipv6 {
description
"Enables IPv6 support in a VPN.";
}
feature lan-tag {
description
"Enables LAN Tag support in a VPN Policy filter.";
}
feature carrierscarrier {
description
"Enables support of CsC.";
}
feature extranet-vpn {
description
"Enables support of extranet VPNs.";
}
feature site-diversity {
description
"Enables support of site diversity constraints.";
}
feature encryption {
description
"Enables support of encryption.";
}
feature qos {
description
"Enables support of classes of services.";
}
feature qos-custom {
description
"Enables support of the custom QoS profile.";
}
feature rtg-bgp {
description
"Enables support of the BGP routing protocol.";
}
feature rtg-rip {
description
"Enables support of the RIP routing protocol.";
}
feature rtg-ospf {
description
"Enables support of the OSPF routing protocol.";
}
feature rtg-ospf-sham-link {
description
"Enables support of OSPF sham links.";
}
feature rtg-vrrp {
description
"Enables support of the VRRP routing protocol.";
}
feature fast-reroute {
description
"Enables support of Fast Reroute.";
}
feature bfd {
description
"Enables support of BFD.";
}
feature always-on {
description
"Enables support of the 'always-on' access constraint.";
}
feature requested-type {
description
"Enables support of the 'requested-type' access constraint.";
}
feature bearer-reference {
description
"Enables support of the 'bearer-reference' access constraint.";
}
feature target-sites {
description
"Enables support of the 'target-sites' match flow parameter.";
}
feature input-bw {
description
"Enables support of the 'input-bw' limit.";
}
feature dot1q {
description
"Enables support of the 'dot1q' encapsulation.";
}
feature qinq {
description
"Enables support of the 'qinq' encapsulation.";
}
feature qinany {
description
"Enables support of the 'qinany' encapsulation.";
}
feature vxlan {
description
"Enables support of the 'vxlan' encapsulation.";
}
/* Typedefs */
typedef svc-id {
type string;
description
"Defines a type of service component identifier.";
}
typedef template-id {
type string;
description
"Defines a type of service template identifier.";
}
typedef address-family {
type enumeration {
enum ipv4 {
description
"IPv4 address family.";
}
enum ipv6 {
description
"IPv6 address family.";
}
} }
description import ietf-netconf-acm {
"Defines a type for the address family."; 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>
";
typedef ie-type { description
type enumeration { "This YANG module defines a generic network-oriented model
enum "import" { for the management of Layer 3 VPNs in a Service Provider
value 0; backbone network.
description "Import routing profile."; Copyright (c) 2019 IETF Trust and the persons identified as
} authors of the code. All rights reserved.
enum "export" {
value 1; Redistribution and use in source and binary forms, with or
description "Export routing profile"; without modification, is permitted pursuant to, and subject to
} the license terms contained in, the Simplified BSD License set
enum "both" { forth in Section 4.c of the IETF Trust's Legal Provisions
value 2; Relating to IETF Documents
description "Import/Export routing profile"; (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
"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.";
} }
description /* Features */
"Defines Import-Export routing profiles. feature cloud-access {
Those are able to be reused between vpn-nodes"; 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 {
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 {
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.";
} }
typedef operational-type { /* 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 { type enumeration {
enum "up" { enum ipv4 {
value 0; description
description "Operational status UP."; "IPv4 address family.";
} }
enum "down" { enum ipv6 {
value 1; description
description "Operational status DOWN"; "IPv6 address family.";
} }
enum "unknown" { enum ipv4/ipv6 {
value 2; description
description "Operational status UNKNOWN"; "IPv4/IPv6 address family.";
} }
} }
description description
"This is a read-only attribute used to determine the "Defines a type for the address family.";
status of a particular element";
} }
/* Identities */ typedef ie-type {
identity site-network-access-type { type enumeration {
description enum "import" {
"Base identity for site-network-access type."; 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 {
identity point-to-point { type enumeration {
base site-network-access-type; enum "up" {
description value 0;
"Identity for point-to-point connection."; description "Operational status UP.";
} }
/* Extension */ enum "down" {
identity pseudowire { value 1;
base site-network-access-type; description "Operational status DOWN";
description }
"Identity for pseudowire connection."; enum "unknown" {
} value 2;
/* End of Extension */ description "Operational status UNKNOWN";
identity multipoint { }
base site-network-access-type; }
description description
"Identity for multipoint connection. "This is a read-only attribute used to determine the
Example: Ethernet broadcast segment."; status of a particular element";
} }
identity placement-diversity {
description
"Base identity for site placement constraints.";
}
identity bearer-diverse {
base placement-diversity;
description
"Identity for bearer diversity.
The bearers should not use common elements.";
}
identity pe-diverse {
base placement-diversity;
description
"Identity for PE diversity.";
}
identity pop-diverse {
base placement-diversity;
description
"Identity for POP diversity.";
}
identity linecard-diverse {
base placement-diversity;
description
"Identity for linecard diversity.";
}
identity same-pe {
base placement-diversity;
description
"Identity for having sites connected on the same PE.";
} /* Identities */
identity same-bearer { identity site-network-access-type {
base placement-diversity; description
description "Base identity for site-network-access type.";
"Identity for having sites connected using the same bearer."; }
} identity point-to-point {
identity customer-application { base site-network-access-type;
description description
"Base identity for customer application."; "Identity for point-to-point connection.";
} }
identity web { /* Extension */
base customer-application; identity pseudowire {
description base site-network-access-type;
"Identity for Web application (e.g., HTTP, HTTPS)."; description
} "Identity for pseudowire connection.";
identity mail { }
base customer-application; /* End of Extension */
description identity multipoint {
"Identity for mail application."; base site-network-access-type;
} description
identity file-transfer { "Identity for multipoint connection.
base customer-application; Example: Ethernet broadcast segment.";
description }
"Identity for file transfer application (e.g., FTP, SFTP)."; identity customer-application {
} description
identity database { "Base identity for customer application.";
base customer-application; }
description identity web {
"Identity for database application.";
}
identity social {
base customer-application;
description
"Identity for social-network application.";
}
identity games {
base customer-application;
description
"Identity for gaming application.";
}
identity p2p {
base customer-application;
description
"Identity for peer-to-peer application.";
}
identity network-management {
base customer-application;
description
"Identity for management application
(e.g., Telnet, syslog, SNMP).";
}
identity voice {
base customer-application;
description
"Identity for voice application.";
}
identity video {
base customer-application;
description
"Identity for video conference application.";
}
identity embb {
base customer-application;
description
"Identity for an enhanced Mobile Broadband (eMBB)
application. Note that an eMBB application demands
network performance with a wide variety of
characteristics, such as data rate, latency,
loss rate, reliability, and many other parameters.";
}
identity urllc {
base customer-application;
description
"Identity for an Ultra-Reliable and Low Latency
Communications (URLLC) application. Note that a
URLLC application demands network performance
with a wide variety of characteristics, such as latency,
reliability, and many other parameters.";
}
identity mmtc {
base customer-application; base customer-application;
description description
"Identity for a massive Machine Type "Identity for Web application (e.g., HTTP, HTTPS).";
Communications (mMTC) application. Note that an }
mMTC application demands network performance identity mail {
with a wide variety of characteristics, such as data base customer-application;
rate, latency, loss rate, reliability, and many
other parameters.";
}
identity site-vpn-flavor {
description
"Base identity for the site VPN service flavor.";
}
identity site-vpn-flavor-single {
base site-vpn-flavor;
description
"Base identity for the site VPN service flavor.
Used when the site belongs to only one VPN.";
}
identity site-vpn-flavor-multi {
base site-vpn-flavor;
description
"Base identity for the site VPN service flavor.
Used when a logical connection of a site
belongs to multiple VPNs.";
}
identity site-vpn-flavor-sub {
base site-vpn-flavor;
description
"Base identity for the site VPN service flavor.
Used when a site has multiple logical connections.
Each connection may belong to different multiple VPNs.";
}
identity site-vpn-flavor-nni {
base site-vpn-flavor;
description
"Base identity for the site VPN service flavor.
Used to describe an NNI option A connection.";
}
identity management {
description
"Base identity for site management scheme.";
}
identity co-managed {
base management;
description
"Base identity for co-managed site.";
}
identity customer-managed {
base management;
description
"Base identity for customer-managed site.";
}
identity provider-managed {
base management;
description
"Base identity for provider-managed site.";
}
identity address-allocation-type {
description
"Base identity for address-allocation-type for PE-CE link.";
}
identity provider-dhcp {
base address-allocation-type;
description
"Provider network provides DHCP service to customer.";
}
identity provider-dhcp-relay {
base address-allocation-type;
description
"Provider network provides DHCP relay service to customer.";
}
identity provider-dhcp-slaac {
base address-allocation-type;
description
"Provider network provides DHCP service to customer,
as well as SLAAC.";
}
identity static-address {
base address-allocation-type;
description
"Provider-to-customer addressing is static.";
}
identity slaac {
base address-allocation-type;
description
"Use IPv6 SLAAC.";
}
identity site-role {
description
"Base identity for site type.";
}
identity any-to-any-role {
base site-role;
description
"Site in an any-to-any IP VPN.";
}
identity spoke-role {
base site-role;
description
"Spoke site in a Hub-and-Spoke IP VPN.";
}
identity hub-role {
base site-role;
description
"Hub site in a Hub-and-Spoke IP VPN.";
}
identity vpn-topology {
description
"Base identity for VPN topology.";
}
identity any-to-any {
base vpn-topology;
description
"Identity for any-to-any VPN topology.";
}
identity hub-spoke {
base vpn-topology;
description
"Identity for Hub-and-Spoke VPN topology.";
}
identity hub-spoke-disjoint {
base vpn-topology;
description
"Identity for Hub-and-Spoke VPN topology
where Hubs cannot communicate with each other.";
}
identity multicast-tree-type {
description
"Base identity for multicast tree type.";
}
identity ssm-tree-type {
base multicast-tree-type;
description
"Identity for SSM tree type.";
}
identity asm-tree-type {
base multicast-tree-type;
description
"Identity for ASM tree type.";
}
identity bidir-tree-type {
base multicast-tree-type;
description
"Identity for bidirectional tree type.";
}
identity multicast-rp-discovery-type {
description
"Base identity for RP discovery type.";
}
identity auto-rp {
base multicast-rp-discovery-type;
description
"Base identity for Auto-RP discovery type.";
}
identity static-rp {
base multicast-rp-discovery-type;
description
"Base identity for static type.";
}
identity bsr-rp {
base multicast-rp-discovery-type;
description
"Base identity for BSR discovery type.";
}
identity routing-protocol-type {
description
"Base identity for routing protocol type.";
}
identity ospf {
base routing-protocol-type;
description
"Identity for OSPF protocol type.";
}
identity bgp {
base routing-protocol-type;
description
"Identity for BGP protocol type.";
}
identity static {
base routing-protocol-type;
description
"Identity for static routing protocol type.";
}
identity rip {
base routing-protocol-type;
description
"Identity for RIP protocol type.";
}
identity vrrp {
base routing-protocol-type;
description
"Identity for VRRP protocol type.
This is to be used when LANs are directly connected
to PE routers.";
}
identity direct {
base routing-protocol-type;
description
"Identity for direct protocol type.";
}
identity protocol-type {
description
"Base identity for protocol field type.";
}
identity tcp {
base protocol-type;
description
"TCP protocol type.";
}
identity udp {
base protocol-type;
description
"UDP protocol type.";
}
identity icmp {
base protocol-type;
description
"ICMP protocol type.";
}
identity icmp6 {
base protocol-type;
description
"ICMPv6 protocol type.";
}
identity gre {
base protocol-type;
description
"GRE protocol type.";
}
identity ipip {
base protocol-type;
description
"IP-in-IP protocol type.";
}
identity hop-by-hop {
base protocol-type;
description
"Hop-by-Hop IPv6 header type.";
}
identity routing {
base protocol-type;
description
"Routing IPv6 header type.";
}
identity esp {
base protocol-type;
description
"ESP header type.";
}
identity ah {
base protocol-type;
description
"AH header type.";
}
identity vpn-policy-filter-type {
description
"Base identity for VPN Policy filter type.";
}
identity ipv4 {
base vpn-policy-filter-type;
description description
"Identity for IPv4 Prefix filter type."; "Identity for mail application.";
} }
identity ipv6 { identity file-transfer {
base vpn-policy-filter-type; base customer-application;
description description
"Identity for IPv6 Prefix filter type."; "Identity for file transfer application (e.g., FTP, SFTP).";
} }
identity lan { identity database {
base vpn-policy-filter-type; base customer-application;
description description
"Identity for LAN Tag filter type."; "Identity for database application.";
} }
identity social {
identity qos-profile-direction { base customer-application;
description
"Base identity for QoS profile direction.";
}
identity site-to-wan {
base qos-profile-direction;
description description
"Identity for Site-to-WAN direction."; "Identity for social-network application.";
} }
identity wan-to-site { identity games {
base qos-profile-direction; base customer-application;
description description
"Identity for WAN-to-Site direction."; "Identity for gaming application.";
} }
identity both { identity p2p {
base qos-profile-direction; base customer-application;
description description
"Identity for both WAN-to-Site direction "Identity for peer-to-peer application.";
and Site-to-WAN direction."; }
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 {
/* Extended Identities */ base customer-application;
description
identity encapsulation-type { "Identity for an Ultra-Reliable and Low Latency
description Communications (URLLC) application. Note that a
"Identity for the encapsulation type."; URLLC application demands network performance
with a wide variety of characteristics, such as latency,
reliability, and many other parameters.";
} }
identity untagged-int { identity mmtc {
base encapsulation-type; base customer-application;
description description
"Identity for Ethernet type."; "Identity for a massive Machine Type
Communications (mMTC) application. Note that an
mMTC application demands network performance
with a wide variety of characteristics, such as data
rate, latency, loss rate, reliability, and many
other parameters.";
} }
identity address-allocation-type {
identity tagged-int { description
base encapsulation-type; "Base identity for address-allocation-type for PE-CE link.";
description
"Identity for the VLAN type.";
} }
identity provider-dhcp {
identity eth-inf-type { base address-allocation-type;
description description
"Identity of the Ethernet interface type."; "Provider network provides DHCP service to customer.";
} }
identity provider-dhcp-relay {
identity tagged { base address-allocation-type;
base eth-inf-type; description
description "Provider network provides DHCP relay service to customer.";
"Identity of the tagged interface type.";
} }
identity provider-dhcp-slaac {
identity untagged { base address-allocation-type;
base eth-inf-type; description
description "Provider network provides DHCP service to customer,
"Identity of the untagged interface type."; as well as SLAAC.";
} }
identity static-address {
identity lag { base address-allocation-type;
base eth-inf-type; description
description "Provider-to-customer addressing is static.";
"Identity of the LAG interface type.";
} }
identity bearer-inf-type { identity slaac {
description base address-allocation-type;
"Identity for the bearer interface type."; description
"Use IPv6 SLAAC.";
} }
identity site-role {
identity port-id { description
base bearer-inf-type; "Base identity for site type.";
description
"Identity for the priority-tagged interface.";
} }
identity any-to-any-role {
identity lag-id { base site-role;
base bearer-inf-type; description
description "Site in an any-to-any IP VPN.";
"Identity for the priority-tagged interface.";
} }
identity spoke-role {
identity tagged-inf-type { base site-role;
description description
"Identity for the tagged interface type."; "Spoke site in a Hub-and-Spoke IP VPN.";
} }
identity hub-role {
base site-role;
description
"Hub site in a Hub-and-Spoke IP VPN.";
identity priority-tagged {
base tagged-inf-type;
description
"Identity for the priority-tagged interface.";
} }
identity vpn-topology {
identity qinq { description
base tagged-inf-type; "Base identity for VPN topology.";
description
"Identity for the QinQ tagged interface.";
} }
identity any-to-any {
identity dot1q { base vpn-topology;
base tagged-inf-type; description
description "Identity for any-to-any VPN topology.";
"Identity for the dot1Q VLAN tagged interface.";
} }
identity hub-spoke {
identity qinany { base vpn-topology;
base tagged-inf-type; description
description "Identity for Hub-and-Spoke VPN topology.";
"Identity for the QinAny tagged interface.";
} }
identity hub-spoke-disjoint {
identity vxlan { base vpn-topology;
base tagged-inf-type; description
description "Identity for Hub-and-Spoke VPN topology
"Identity for the VXLAN tagged interface."; where Hubs cannot communicate with each other.";
} }
identity multicast-tree-type {
identity tag-type { description
description "Base identity for multicast tree type.";
"Base identity from which all tag types are derived.";
} }
identity ssm-tree-type {
identity c-vlan { base multicast-tree-type;
base tag-type; description
description "Identity for SSM tree type.";
"A CVLAN tag, normally using the 0x8100 Ethertype.";
} }
identity s-vlan { identity asm-tree-type {
base tag-type; base multicast-tree-type;
description description
"An SVLAN tag."; "Identity for ASM tree type.";
} }
identity bidir-tree-type {
identity c-s-vlan { base multicast-tree-type;
base tag-type; description
description "Identity for bidirectional tree type.";
"Using both a CVLAN tag and an SVLAN tag.";
} }
identity multicast-rp-discovery-type {
identity vxlan-peer-mode { description
description "Base identity for RP discovery type.";
"Base identity for the VXLAN peer mode.";
} }
identity auto-rp {
base multicast-rp-discovery-type;
description
"Base identity for Auto-RP discovery type.";
identity static-mode {
base vxlan-peer-mode;
description
"Identity for VXLAN access in the static mode.";
} }
identity static-rp {
identity bgp-mode { base multicast-rp-discovery-type;
base vxlan-peer-mode; description
description "Base identity for static type.";
"Identity for VXLAN access by BGP EVPN learning.";
} }
identity bsr-rp {
identity bw-direction { base multicast-rp-discovery-type;
description description
"Identity for the bandwidth direction."; "Base identity for BSR discovery type.";
} }
identity routing-protocol-type {
identity input-bw { description
base bw-direction; "Base identity for routing protocol type.";
description }
"Identity for the input bandwidth."; identity ospf {
base routing-protocol-type;
description
"Identity for OSPF protocol type.";
}
identity bgp {
base routing-protocol-type;
description
"Identity for BGP protocol type.";
}
identity static {
base routing-protocol-type;
description
"Identity for static routing protocol type.";
}
identity rip {
base routing-protocol-type;
description
"Identity for RIP protocol type.";
}
identity vrrp {
base routing-protocol-type;
description
"Identity for VRRP protocol type.
This is to be used when LANs are directly connected
to PE routers.";
}
identity direct {
base routing-protocol-type;
description
"Identity for direct protocol type.";
}
identity protocol-type {
description
"Base identity for protocol field type.";
}
identity tcp {
base protocol-type;
description
"TCP protocol type.";
}
identity udp {
base protocol-type;
description
"UDP protocol type.";
} }
identity output-bw { identity icmp {
base bw-direction; base protocol-type;
description description
"Identity for the output bandwidth."; "ICMP protocol type.";
}
identity icmp6 {
base protocol-type;
description
"ICMPv6 protocol type.";
}
identity gre {
base protocol-type;
description
"GRE protocol type.";
}
identity ipip {
base protocol-type;
description
"IP-in-IP protocol type.";
}
identity hop-by-hop {
base protocol-type;
description
"Hop-by-Hop IPv6 header type.";
}
identity routing {
base protocol-type;
description
"Routing IPv6 header type.";
} }
identity esp {
base protocol-type;
description
"ESP header type.";
identity bw-type { }
identity ah {
base protocol-type;
description
"AH header type.";
}
identity vpn-policy-filter-type {
description
"Base identity for VPN Policy filter type.";
}
identity ipv4 {
base vpn-policy-filter-type;
description description
"Identity of the bandwidth type."; "Identity for IPv4 Prefix filter type.";
} }
identity ipv6 {
identity bw-per-cos { base vpn-policy-filter-type;
base bw-type;
description description
"Bandwidth is per CoS."; "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 bw-per-port { identity site-to-wan {
base bw-type; base qos-profile-direction;
description description
"Bandwidth is per site network access."; "Identity for Site-to-WAN direction.";
} }
identity wan-to-site {
identity bw-per-site { base qos-profile-direction;
base bw-type;
description description
"Bandwidth is per site. It is applicable to "Identity for WAN-to-Site direction.";
all the site network accesses within the site.";
} }
identity both {
identity bw-per-svc { base qos-profile-direction;
base bw-type;
description description
"Bandwidth is per VPN service."; "Identity for both WAN-to-Site direction
and Site-to-WAN direction.";
} }
/* Extended Identities */
/* Groupings */ identity encapsulation-type {
grouping vpn-service-cloud-access {
container cloud-accesses {
if-feature cloud-access;
list cloud-access {
key cloud-identifier;
leaf cloud-identifier {
type leafref {
path "/l3vpn-ntw/vpn-profiles/"+
"valid-provider-identifiers/cloud-identifier/id";
}
description description
"Identification of cloud service. "Identity for the encapsulation type.";
Local administration meaning."; }
}
choice list-flavor { identity untagged-int {
case permit-any { base encapsulation-type;
leaf permit-any {
type empty;
description
"Allows all sites.";
}
}
case deny-any-except {
leaf-list permit-site {
type leafref {
path "/l3vpn-ntw/sites/site/site-id";
}
description
"Site ID to be authorized.";
}
}
case permit-any-except {
leaf-list deny-site {
type leafref {
path "/l3vpn-ntw/sites/site/site-id";
}
description
"Site ID to be denied.";
}
}
description description
"Choice for cloud access policy. By "Identity for Ethernet type.";
default, all sites in the IP VPN MUST }
be authorized to access the cloud.";
}
container address-translation {
container nat44 {
leaf enabled {
type boolean;
default false;
description
"Controls whether or not Network address
translation from IPv4 to IPv4 (NAT44)
[RFC3022] is required.";
}
leaf nat44-customer-address {
type inet:ipv4-address;
description
"Address to be used for network address
translation from IPv4 to IPv4. This is
to be used if the customer is providing
the IPv4 address. If the customer address
is not set, the model assumes that the
provider will allocate the address.";
}
description
"IPv4-to-IPv4 translation.";
} identity tagged-int {
base encapsulation-type;
description description
"Container for NAT."; "Identity for the VLAN type.";
}
description
"Cloud access configuration.";
} }
description
"Container for cloud access configurations."; identity eth-inf-type {
}
description
"Grouping for VPN cloud definition.";
}
grouping multicast-rp-group-cfg {
choice group-format {
mandatory true;
case singleaddress {
leaf group-address {
type inet:ip-address;
description description
"A single multicast group address."; "Identity of the Ethernet interface type.";
}
} }
case startend {
leaf group-start { identity tagged {
type inet:ip-address; base eth-inf-type;
description description
"The first multicast group address in "Identity of the tagged interface type.";
the multicast group address range."; }
}
leaf group-end { identity untagged {
type inet:ip-address; base eth-inf-type;
description description
"The last multicast group address in "Identity of the untagged interface type.";
the multicast group address range.";
}
} }
description
"Choice for multicast group format."; identity lag {
} base eth-inf-type;
description description
"This grouping defines multicast group or "Identity of the LAG interface type.";
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 { identity bearer-inf-type {
leaf-list tree-flavor {
type identityref {
base multicast-tree-type;
}
description description
"Type of tree to be used."; "Identity for the bearer interface type.";
}
description
"Type of trees used by customer.";
} }
container rp {
container rp-group-mappings { identity port-id {
list rp-group-mapping { base bearer-inf-type;
key id;
leaf id {
type uint16;
description
"Unique identifier for the mapping.";
}
container provider-managed {
leaf enabled {
type boolean;
default false;
description
"Set to true if the Rendezvous Point (RP)
must be a provider-managed node. Set to false
if it is a customer-managed node.";
}
leaf rp-redundancy {
type boolean;
default false;
description
"If true, a redundancy mechanism for the RP
is required.";
}
leaf optimal-traffic-delivery {
type boolean;
default false;
description
"If true, the SP must ensure that
traffic uses an optimal path. An SP may use
Anycast RP or RP-tree-to-SPT switchover
architectures.";
}
description
"Parameters for a provider-managed RP.";
}
leaf rp-address {
when "../provider-managed/enabled = 'false'" {
description
"Relevant when the RP is not provider-managed.";
}
type inet:ip-address;
mandatory true;
description
"Defines the address of the RP.
Used if the RP is customer-managed.";
}
container groups {
list group {
key id;
leaf id {
type uint16;
description
"Identifier for the group.";
}
uses multicast-rp-group-cfg;
description
"List of multicast groups.";
}
description
"Multicast groups associated with the RP.";
}
description
"List of RP-to-group mappings.";
}
description description
"RP-to-group mappings parameters."; "Identity for the priority-tagged interface.";
} }
container rp-discovery {
leaf rp-discovery-type { identity lag-id {
type identityref { base bearer-inf-type;
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 description
"RP discovery parameters."; "Identity for the priority-tagged interface.";
}
description
"RP parameters.";
} }
description
"Multicast global parameters for the VPN service."; identity tagged-inf-type {
}
description
"Grouping for multicast VPN definition.";
}
grouping vpn-service-mpls {
leaf carrierscarrier {
if-feature carrierscarrier;
type boolean;
default false;
description
"The VPN is using CsC, and so MPLS is required.";
}
description
"Grouping for MPLS CsC definition.";
}
grouping customer-location-info {
container locations {
list location {
key location-id;
leaf location-id {
type svc-id;
description description
"Identifier for a particular location."; "Identity for the tagged interface type.";
} }
leaf address {
type string; identity priority-tagged {
base tagged-inf-type;
description description
"Address (number and street) of the site."; "Identity for the priority-tagged interface.";
} }
leaf postal-code {
type string; identity qinq {
base tagged-inf-type;
description description
"Postal code of the site."; "Identity for the QinQ tagged interface.";
} }
leaf state {
type string; identity dot1q {
base tagged-inf-type;
description description
"State of the site. This leaf can also be "Identity for the dot1Q VLAN tagged interface.";
used to describe a region for a country that }
does not have states.";
} identity qinany {
leaf city { base tagged-inf-type;
type string;
description description
"City of the site."; "Identity for the QinAny tagged interface.";
}
identity vxlan {
base tagged-inf-type;
description
"Identity for the VXLAN tagged interface.";
}
identity tag-type {
description
"Base identity from which all tag types are derived.";
}
identity c-vlan {
base tag-type;
description
"A CVLAN tag, normally using the 0x8100 Ethertype.";
}
identity s-vlan {
base tag-type;
description
"An SVLAN tag.";
}
identity c-s-vlan {
base tag-type;
description
"Using both a CVLAN tag and an SVLAN tag.";
}
identity vxlan-peer-mode {
description
"Base identity for the VXLAN peer mode.";
}
identity static-mode {
base vxlan-peer-mode;
description
"Identity for VXLAN access in the static mode.";
}
identity bgp-mode {
base vxlan-peer-mode;
description
"Identity for VXLAN access by BGP EVPN learning.";
}
identity bw-direction {
description
"Identity for the bandwidth direction.";
}
identity input-bw {
base bw-direction;
description
"Identity for the input bandwidth.";
}
identity output-bw {
base bw-direction;
description
"Identity for the output bandwidth.";
}
identity bw-type {
description
"Identity of the bandwidth type.";
}
identity bw-per-cos {
base bw-type;
description
"Bandwidth is per CoS.";
}
identity bw-per-port {
base bw-type;
description
"Bandwidth is per site network access.";
}
identity bw-per-site {
base bw-type;
description
"Bandwidth is per site. It is applicable to
all the site network accesses within the site.";
}
identity bw-per-svc {
base bw-type;
description
"Bandwidth is per VPN service.";
}
/* Groupings */
grouping multicast-rp-group-cfg {
choice group-format {
mandatory true;
case singleaddress {
leaf group-address {
type inet:ip-address;
description
"A single multicast group address.";
}
} }
leaf country-code { case startend {
type string { leaf group-start {
pattern '[A-Z]{2}'; 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
"Country of the site.
Expressed as ISO ALPHA-2 code.";
} }
description description
"Location of the site."; "Choice for multicast group format.";
} }
description description
"List of locations for the site."; "This grouping defines multicast group or
multicast groups for RP-to-group mapping.";
} }
description grouping vpn-service-multicast {
"This grouping defines customer location parameters."; container multicast {
} if-feature multicast;
grouping site-group { leaf enabled {
container groups { type boolean;
list group { default false;
key group-id;
leaf group-id {
type string;
description description
"Group-id the site belongs to."; "Enables multicast.";
} }
description container customer-tree-flavors {
"List of group-ids."; leaf-list tree-flavor {
}
description
"Groups the site or site-network-access belongs to.";
}
description
"Grouping definition to assign
group-ids to site or site-network-access.";
}
grouping site-diversity {
container site-diversity {
if-feature site-diversity;
uses site-group;
description
"Diversity constraint type. All
site-network-accesses will inherit
the group values defined here.";
}
description
"This grouping defines site
diversity parameters.";
}
grouping access-diversity {
container access-diversity {
if-feature site-diversity;
uses site-group;
container constraints {
list constraint {
key constraint-type;
leaf constraint-type {
type identityref { type identityref {
base placement-diversity; base multicast-tree-type;
} }
description description
"Diversity constraint type."; "Type of tree to be used.";
} }
container target { description
choice target-flavor { "Type of trees used by customer.";
default id; }
case id { container rp {
container rp-group-mappings {
list rp-group-mapping {
key id;
leaf id {
type uint16;
description
"Unique identifier for the mapping.";
}
container provider-managed {
leaf enabled {
type boolean;
default false;
description
"Set to true if the Rendezvous Point (RP)
must be a provider-managed node. Set to false
if it is a customer-managed node.";
}
leaf rp-redundancy {
type boolean;
default false;
description
"If true, a redundancy mechanism for the RP
is required.";
}
leaf optimal-traffic-delivery {
type boolean;
default false;
description
"If true, the SP must ensure that
traffic uses an optimal path. An SP may use
Anycast RP or RP-tree-to-SPT switchover
architectures.";
}
description
"Parameters for a provider-managed RP.";
}
leaf rp-address {
when "../provider-managed/enabled = 'false'" {
description
"Relevant when the RP is not provider-managed.";
}
type inet:ip-address;
mandatory true;
description
"Defines the address of the RP.
Used if the RP is customer-managed.";
}
container groups {
list group { list group {
key group-id; key id;
leaf group-id { leaf id {
type string; type uint16;
description description
"The constraint will be applied against "Identifier for the group.";
this particular group-id for this site
network access level.";
} }
uses multicast-rp-group-cfg;
description description
"List of group-ids associated with one specific "List of multicast groups.";
constraint for this site network access level.";
} }
description
"Multicast groups associated with the RP.";
} }
case all-accesses { description
leaf all-other-accesses { "List of RP-to-group mappings.";
type empty; }
description description
"The constraint will be applied against "RP-to-group mappings parameters.";
all other site network accesses of this site."; }
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.";
} }
case all-groups { leaf-list bsr-candidate-address {
leaf all-other-groups { type inet:ip-address;
type empty;
description description
"The constraint will be applied against "Address of BSR candidate.";
all other groups managed by the customer.";
}
} }
description description
"Choice for the target flavor definition."; "Container for List of Customer
BSR candidate's addresses.";
} }
description description
"The constraint will be applied against a "RP discovery parameters.";
Specific target, and the target can be a list
of group-ids,all other site network accesses of
this site, or all other groups managed by the
customer.";
} }
description description
"List of constraints."; "RP parameters.";
} }
description description
"Placement constraints for this site network access."; "Multicast global parameters for the VPN service.";
} }
description description
"Diversity parameters."; "Grouping for multicast VPN definition.";
} }
description grouping vpn-service-mpls {
"This grouping defines access diversity parameters."; leaf carrierscarrier {
} if-feature carrierscarrier;
grouping operational-requirements { type boolean;
leaf requested-site-start { default false;
type yang:date-and-time;
description description
"Optional leaf indicating requested date and "The VPN is using CsC, and so MPLS is required.";
time when the service at a particular site is }
expected to start."; description
"Grouping for MPLS CsC definition.";
} }
grouping operational-requirements {
leaf requested-site-stop { leaf requested-site-start {
type yang:date-and-time; type yang:date-and-time;
description description
"Optional leaf indicating requested date and "Optional leaf indicating requested date and
time when the service at a particular site is time when the service at a particular site is
expected to stop."; 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.";
} }
description grouping operational-requirements-ops {
"This grouping defines some operational leaf actual-site-start {
parameters."; type yang:date-and-time;
} config false;
grouping operational-requirements-ops { description
leaf actual-site-start { "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; type yang:date-and-time;
config false; config false;
description description
"Optional leaf indicating actual date and "Optional leaf indicating actual date and
time when the service at a particular site time when the service at a particular site
actually started."; actually stopped.";
}
leaf actual-site-stop {
type yang:date-and-time;
config false;
description
"Optional leaf indicating actual date and
time when the service at a particular site
actually stopped.";
}
description
"This grouping defines some operational
parameters.";
}
grouping flow-definition {
container match-flow {
leaf dscp {
type inet:dscp;
description
"DSCP value.";
} }
leaf dot1p { description
type uint8 { "This grouping defines some operational
range "0..7"; parameters.";
}
grouping flow-definition {
container match-flow {
leaf dscp {
type inet:dscp;
description
"DSCP value.";
} }
description leaf dot1p {
"802.1p matching."; type uint8 {
} range "0..7";
leaf ipv4-src-prefix {
type inet:ipv4-prefix;
description
"Match on IPv4 src address.";
}
leaf ipv6-src-prefix {
type inet:ipv6-prefix;
description
"Match on IPv6 src address.";
}
leaf ipv4-dst-prefix {
type inet:ipv4-prefix;
description
"Match on IPv4 dst address.";
}
leaf ipv6-dst-prefix {
type inet:ipv6-prefix;
description
"Match on IPv6 dst address.";
}
leaf l4-src-port {
type inet:port-number;
must "current() < ../l4-src-port-range/lower-port or "+
"current() > ../l4-src-port-range/upper-port" {
description
"If l4-src-port and l4-src-port-range/lower-port and
upper-port are set at the same time, l4-src-port
should not overlap with l4-src-port-range.";
} }
description description
"Match on Layer 4 src port."; "802.1p matching.";
} }
leaf-list target-sites { leaf ipv4-src-prefix {
if-feature target-sites; type inet:ipv4-prefix;
type svc-id; description
description "Match on IPv4 src address.";
"Identify a site as traffic destination."; }
} leaf ipv6-src-prefix {
container l4-src-port-range { type inet:ipv6-prefix;
leaf lower-port { description
type inet:port-number; "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 description
"Lower boundary for port."; "Match on IPv6 dst address.";
} }
leaf upper-port { leaf l4-src-port {
type inet:port-number; type inet:port-number;
must ". >= ../lower-port" { must "current() < ../l4-src-port-range/lower-port or "+
"current() > ../l4-src-port-range/upper-port" {
description description
"Upper boundary for port. If it "If l4-src-port and l4-src-port-range/lower-port and
exists, the upper boundary must be upper-port are set at the same time, l4-src-port
higher than the lower boundary."; should not overlap with l4-src-port-range.";
} }
description description
"Upper boundary for port."; "Match on Layer 4 src port.";
} }
description leaf-list target-sites {
"Match on Layer 4 src port range. When if-feature target-sites;
only the lower-port is present, it represents type svc-id;
a single port. When both the lower-port and description
upper-port are specified, it implies "Identify a site as traffic destination.";
a range inclusive of both values."; }
} container l4-src-port-range {
leaf l4-dst-port { leaf lower-port {
type inet:port-number; type inet:port-number;
must "current() < ../l4-dst-port-range/lower-port or "+ description
"current() > ../l4-dst-port-range/upper-port" { "Lower boundary for 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 leaf upper-port {
"Match on Layer 4 dst port."; type inet:port-number;
} must ". >= ../lower-port" {
container l4-dst-port-range { description
leaf lower-port { "Upper boundary for port. If it
type inet:port-number; exists, the upper boundary must be
description higher than the lower boundary.";
"Lower boundary for port."; }
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 upper-port { leaf l4-dst-port {
type inet:port-number; type inet:port-number;
must ". >= ../lower-port" { must "current() < ../l4-dst-port-range/lower-port or "+
description "current() > ../l4-dst-port-range/upper-port" {
"Upper boundary must be description
higher than lower boundary."; "If l4-dst-port and l4-dst-port-range/lower-port
and upper-port are set at the same time,
l4-dst-port should not overlap with
l4-src-port-range.";
}
description
"Match on Layer 4 dst port.";
}
container l4-dst-port-range {
leaf lower-port {
type inet:port-number;
description
"Lower boundary for port.";
}
leaf upper-port {
type inet:port-number;
must ". >= ../lower-port" {
description
"Upper boundary must be
higher than lower boundary.";
}
description
"Upper boundary for port. If it exists,
upper boundary must be higher than lower
boundary.";
} }
description description
"Upper boundary for port. If it exists, "Match on Layer 4 dst port range. When only
upper boundary must be higher than lower lower-port is present, it represents a single
boundary."; port. When both lower-port and upper-port are
specified, it implies a range inclusive of both
values.";
} }
description leaf protocol-field {
"Match on Layer 4 dst port range. When only type union {
lower-port is present, it represents a single type uint8;
port. When both lower-port and upper-port are type identityref {
specified, it implies a range inclusive of both base protocol-type;
values."; }
}
leaf protocol-field {
type union {
type uint8;
type identityref {
base protocol-type;
} }
description
"Match on IPv4 protocol or IPv6 Next Header field.";
} }
description description
"Match on IPv4 protocol or IPv6 Next Header field."; "Describes flow-matching criteria.";
} }
description description
"Describes flow-matching criteria."; "Flow definition based on criteria.";
} }
description grouping site-service-basic {
"Flow definition based on criteria."; leaf svc-input-bandwidth {
} type uint64;
grouping site-service-basic { units bps;
leaf svc-input-bandwidth { mandatory true;
description
"From the customer site's perspective, the service
input bandwidth of the connection or download
bandwidth from the SP to the site.";
}
leaf svc-output-bandwidth {
type uint64; type uint64;
units bps; units bps;
mandatory true; 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 description
"From the customer site's perspective, the service "MTU at service level. If the service is IP,
input bandwidth of the connection or download it refers to the IP MTU. If CsC is enabled,
bandwidth from the SP to the site."; the requested 'svc-mtu' leaf will refer to the
} MPLS MTU and not to the IP MTU.";
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 description
"Fast Reroute service parameters for the site."; "Defines basic service parameters for a site.";
} }
description grouping site-protection {
"Defines protection service parameters for a site."; container traffic-protection {
} if-feature fast-reroute;
grouping site-service-mpls { leaf enabled {
container carrierscarrier { type boolean;
if-feature carrierscarrier; default false;
leaf signalling-type { description
type enumeration { "Enables traffic protection of access link.";
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.";
}
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 description
"MPLS signalling type."; "Fast Reroute service parameters for the site.";
} }
description description
"This container is used when the customer provides "Defines protection service parameters for a site.";
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 grouping site-service-mpls {
"Defines MPLS service parameters for a site."; container carrierscarrier {
} if-feature carrierscarrier;
grouping site-service-qos-profile { leaf signalling-type {
container qos { type enumeration {
if-feature qos; enum ldp {
container qos-classification-policy {
list rule {
key id;
ordered-by user;
leaf id {
type string;
description description
"A description identifying the "Use LDP as the signalling protocol
qos-classification-policy rule."; between the PE and the CE. In this case,
} an IGP routing protocol must also be activated.";
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.";
}
} }
enum bgp {
description description
"Choice for classification."; "Use BGP (as per RFC 8277) as the signalling protocol
} between the PE and the CE.
leaf target-class-id { In this case, BGP must also be configured as
type string; the routing protocol.";
description }
"Identification of the class of service.
This identifier is internal to the administration.";
} }
default bgp;
description description
"List of marking rules."; "MPLS signalling type.";
} }
description description
"Configuration of the traffic classification policy."; "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).";
} }
container qos-profile {
choice qos-profile {
description
"Choice for QoS profile.
Can be standard profile or customized profile.";
case standard {
description description
"Standard QoS profile."; "Defines MPLS service parameters for a site.";
leaf profile { }
type leafref { grouping site-service-qos-profile {
path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+ container qos {
"/qos-profile-identifier/id"; 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.";
}
} }
description description
"QoS profile to be used."; "Choice for classification.";
} }
leaf direction { leaf target-class-id {
type identityref { type string;
base qos-profile-direction;} description
default both; "Identification of the class of service.
description This identifier is internal to the administration.";
"The direction to which the QoS profile
is applied.";
} }
description
"List of marking rules.";
} }
case custom { description
"Configuration of the traffic classification policy.";
}
container qos-profile {
choice qos-profile {
description description
"Customized QoS profile."; "Choice for QoS profile.
container classes { Can be standard profile or customized profile.";
if-feature qos-custom; case standard {
list class { description
key class-id; "Standard QoS profile.";
leaf class-id { leaf profile {
type string; type leafref {
description path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
"Identification of the class of service. "/qos-profile-identifier/id";
This identifier is internal to the }
administration."; description
} "QoS profile to be used.";
leaf direction { }
type identityref { leaf direction {
base qos-profile-direction; type identityref {
} base qos-profile-direction;}
default both; 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;
leaf class-id {
type string;
description description
"The direction to which the QoS profile "Identification of the class of service.
is applied."; This identifier is internal to the
} administration.";
leaf rate-limit {
type decimal64 {
fraction-digits 5;
range "0..100";
} }
units percent; leaf direction {
description type identityref {
"To be used if the class must be rate-limited. base qos-profile-direction;
Expressed as percentage of the service }
bandwidth."; 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 { container latency {
choice flavor { choice flavor {
case lowest { case lowest {
leaf use-lowest-latency { leaf use-lowest-latency {
type empty; type empty;
description description
"The traffic class should use the path with the "The traffic class should use the path with the
lowest latency."; lowest latency.";
}
} }
} case boundary {
case boundary { leaf jitter-boundary {
leaf latency-boundary { type uint16;
type uint16; units msec;
units msec; default 400;
default 400; description
description "The traffic class should use a path with a
"The traffic class should use a path with a defined maximum latency.";
defined maximum latency."; }
} }
description
"Latency constraint on the traffic class.";
} }
description description
"Latency constraint on the traffic class."; "Latency constraint on the traffic class.";
} }
description container jitter {
"Latency constraint on the traffic class."; choice flavor {
} case lowest {
container jitter { leaf use-lowest-jitter {
choice flavor { type empty;
case lowest { description
leaf use-lowest-jitter { "The traffic class should use the path with the
type empty; lowest jitter.";
description }
"The traffic class should use the path with the
lowest jitter.";
} }
} case boundary {
case boundary { leaf latency-boundary {
leaf latency-boundary { type uint32;
type uint32; units usec;
units usec; default 40000;
default 40000; description
description "The traffic class should use a path with a
"The traffic class should use a path with a defined maximum jitter.";
defined maximum jitter."; }
} }
description
"Jitter constraint on the traffic class.";
} }
description description
"Jitter constraint on the traffic class."; "Jitter constraint on the traffic class.";
} }
description container bandwidth {
"Jitter constraint on the traffic class."; leaf guaranteed-bw-percent {
} type decimal64 {
container bandwidth { fraction-digits 5;
leaf guaranteed-bw-percent { range "0..100";
type decimal64 { }
fraction-digits 5; units percent;
range "0..100"; mandatory true;
description
"To be used to define the guaranteed bandwidth
as a percentage of the available service bandwidth.";
} }
units percent; leaf end-to-end {
mandatory true; type empty;
description description
"To be used to define the guaranteed bandwidth "Used if the bandwidth reservation
as a percentage of the available service bandwidth."; must be done on the MPLS network too.";
} }
leaf end-to-end { description
type empty; "Bandwidth constraint on the traffic class.";
description
"Used if the bandwidth reservation
must be done on the MPLS network too.";
} }
description description
"Bandwidth constraint on the traffic class."; "List of classes of services.";
} }
description description
"List of classes of services."; "Container for list of classes of services.";
} }
description
"Container for list of classes of services.";
} }
} }
description
"QoS profile configuration.";
} }
description description
"QoS profile configuration."; "QoS configuration.";
} }
description description
"QoS configuration."; "This grouping defines QoS parameters for a site.";
}
description
"This grouping defines QoS parameters for a site.";
}
grouping site-security-authentication {
container authentication {
description
"Authentication parameters.";
} }
description grouping site-security-authentication {
"This grouping defines authentication parameters for a site."; container authentication {
}
grouping site-security-encryption {
container encryption {
if-feature encryption;
leaf enabled {
type boolean;
default false;
description description
"If true, traffic encryption on the connection is required."; "Authentication parameters.";
} }
leaf layer { description
when "../enabled = 'true'" { "This grouping defines authentication parameters for a site.";
description
"Require a value for layer when enabled is true.";
}
type enumeration {
enum layer2 {
description
"Encryption will occur at Layer 2.";
}
enum layer3 {
description
"Encryption will occur at Layer 3.
For example, IPsec may be used when
a customer requests Layer 3 encryption.";
}
}
description
"Layer on which encryption is applied.";
}
description
"";
} }
container encryption-profile { grouping site-security-encryption {
choice profile { container encryption {
case provider-profile { if-feature encryption;
leaf profile-name { leaf enabled {
type leafref { type boolean;
path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+ default false;
"/encryption-profile-identifier/id"; description
} "If true, traffic encryption on the connection is required.";
description }
"Name of the SP profile to be applied."; leaf layer {
} when "../enabled = 'true'" {
} description
case customer-profile { "Require a value for layer when enabled is true.";
leaf algorithm {
type string;
description
"Encryption algorithm to be used.";
} }
} type enumeration {
description enum layer2 {
""; description
} "Encryption will occur at Layer 2.";
choice key-type { }
default psk; enum layer3 {
case psk { description
leaf preshared-key { "Encryption will occur at Layer 3.
type string; For example, IPsec may be used when
description a customer requests Layer 3 encryption.";
"Pre-Shared Key (PSK) coming from the customer.";
} }
} }
description
"Choice of encryption profile.
The encryption profile can be the provider profile
or customer profile.";
}
description
"This grouping defines encryption parameters for a site.";
}
description
"";
}
grouping site-attachment-bearer {
container bearer {
container requested-type {
if-feature requested-type;
leaf requested-type {
type string;
description
"Type of requested bearer: Ethernet, DSL,
Wireless, etc. Operator specific.";
}
leaf strict {
type boolean;
default false;
description description
"Defines whether requested-type is a preference "Layer on which encryption is applied.";
or a strict requirement."; }
}
description description
"Container for requested-type."; "";
} }
leaf always-on { container encryption-profile {
if-feature always-on; choice profile {
type boolean; case provider-profile {
default true; 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 description
"Request for an always-on access type. "";
For example, this could mean no dial access type."; }
} choice key-type {
default psk;
leaf bearer-reference { case psk {
if-feature bearer-reference; leaf preshared-key {
type string; type string;
description
"Pre-Shared Key (PSK) coming from the customer.";
}
}
description
"Choice of encryption profile.
The encryption profile can be the provider profile
or customer profile.";
}
description description
"This is an internal reference for the SP."; "This grouping defines encryption parameters for a site.";
} }
description description
"Bearer-specific parameters. "";
To be augmented."; }
uses ethernet-params;
uses pseudowire-params { grouping site-routing {
when "/l3vpn-ntw/sites/site/site-network-accesses" + container routing-protocols {
"/site-network-access/site-network-access-type ='pseudowire'" list routing-protocol {
{ key id;
description "pseudowire specific parameters"; leaf id{
} type string;
description
"";
} }
leaf type {
} type identityref {
description base routing-protocol-type;
"Defines physical properties of a site attachment."; }
} description
grouping site-routing { "Type of routing protocol.";
container routing-protocols {
list routing-protocol {
key type;
leaf type {
type identityref {
base routing-protocol-type;
} }
description
"Type of routing protocol.";
}
list routing-profiles {
key "id";
leaf id { list routing-profiles {
type leafref { key "id";
path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
"/routing-profile-identifier/id";
}
description
"Routing profile to be used.";
}
leaf type { leaf id {
type ie-type; type leafref {
path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers"+
"/routing-profile-identifier/id";
}
description description
"Import, export or both."; "Routing profile to be used.";
} }
description
"Import or Export profile reference";
}
container ospf { leaf type {
when "derived-from-or-self(../type, 'l3vpn-ntw:ospf')" { type ie-type;
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 description
"Metric of the PE-CE link. It is used "Import, export or both.";
in the routing state calculation and }
path selection.";
}
/* Extension */
leaf mtu { description
type uint16; "Import or Export profile reference";
description "Maximum transmission unit for a given
OSPF link.";
} }
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.";
}
uses security-params; /* Extension */
/* End of Extension */ leaf mtu {
type uint16;
description "Maximum transmission unit for a given
OSPF link.";
}
container sham-links { leaf process-id {
if-feature rtg-ospf-sham-link; type uint16;
list sham-link { description
key target-site; "Process id of the OSPF CE-PE connection.";
leaf target-site { }
type svc-id; uses security-params;
description
"Target site for the sham link connection. /* End of Extension */
The site is referred to by its ID."; container sham-links {
} if-feature rtg-ospf-sham-link;
leaf metric { list sham-link {
type uint16; key target-site;
default 1; leaf target-site {
description type svc-id;
"Metric of the sham link. It is used in description
the routing state calculation and path "Target site for the sham link connection.
selection. The default value is set The site is referred to by its ID.";
to 1."; }
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 description
"Creates a sham link with another site."; "List of sham links.";
} }
description description
"List of sham links."; "OSPF-specific configuration.";
}
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
to be activated.";
}
/* Extension */
leaf neighbor {
type inet:ip-address;
description
"IP address of the BGP neighbor.";
} }
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
to be activated.";
}
/* Extension */
leaf neighbor {
type inet:ip-address;
description
"IP address of the BGP neighbor.";
}
leaf multihop { leaf multihop {
type uint8; type uint8;
description description
"Describes the number of hops allowed between the "Describes the number of hops allowed between the
given BGP neighbor and the PE router."; given BGP neighbor and the PE router.";
} }
uses security-params; uses security-params;
description description
"BGP-specific configuration."; "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 { container static {
list ipv4-lan-prefixes { when "derived-from-or-self(../type, 'l3vpn-ntw:static')" {
if-feature ipv4;
key "lan next-hop";
leaf lan {
type inet:ipv4-prefix;
description description
"LAN prefixes."; "Only applies when protocol is static.
} BGP activation requires the SP to know
leaf lan-tag { the address of the customer peer. When
type string; BGP is enabled, the 'static-address'
description allocation type for the IP connection
"Internal tag to be used in VPN policies."; MUST be used.";
}
leaf next-hop {
type inet:ipv4-address;
description
"Next-hop address to use on the customer side.";
}
description
"List of LAN prefixes for the site.";
} }
list ipv6-lan-prefixes { container cascaded-lan-prefixes {
if-feature ipv6; list ipv4-lan-prefixes {
key "lan next-hop"; if-feature ipv4;
leaf lan { key "lan next-hop";
type inet:ipv6-prefix; leaf lan {
type inet:ipv4-prefix;
description description
"LAN prefixes."; "LAN prefixes.";
} }
leaf lan-tag { leaf lan-tag {
type string; type string;
description
"Internal tag to be used in VPN policies.";
}
leaf next-hop {
type inet:ipv4-address;
description
"Next-hop address to use on the customer side.";
}
description description
"Internal tag to be used in VPN policies."; "List of LAN prefixes for the site.";
} }
leaf next-hop { list ipv6-lan-prefixes {
type inet:ipv6-address; if-feature ipv6;
key "lan next-hop";
leaf lan {
type inet:ipv6-prefix;
description
"LAN prefixes.";
}
leaf lan-tag {
type string;
description description
"Next-hop address to use on the customer side."; "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 description
"List of LAN prefixes for the site."; "LAN prefixes from the customer.";
} }
description description
"LAN prefixes from the customer."; "Configuration specific to static routing.";
} }
description container rip {
"Configuration specific to static routing."; when "derived-from-or-self(../type, 'l3vpn-ntw:rip')" {
} description
container rip { "Only applies when the protocol is RIP. For IPv4,
when "derived-from-or-self(../type, 'l3vpn-ntw:rip')" { 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.";
}
description description
"Only applies when the protocol is RIP. For IPv4, "Configuration specific to RIP routing.";
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.";
} }
description container vrrp {
"Configuration specific to RIP routing."; when "derived-from-or-self(../type, 'l3vpn-ntw:vrrp')" {
} description
container vrrp { "Only applies when protocol is VRRP.";
when "derived-from-or-self(../type, 'l3vpn-ntw: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 description
"Only applies when protocol is VRRP."; "Configuration specific to VRRP routing.";
}
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 description
"Configuration specific to VRRP routing."; "List of routing protocols used on
the site. This list can be augmented.";
} }
description description
"List of routing protocols used on "Defines routing protocols.";
the site. This list can be augmented.";
} }
description description
"Defines routing protocols."; "Grouping for routing protocols.";
} }
description grouping site-attachment-ip-connection {
"Grouping for routing protocols.";
} container ip-connection {
grouping site-attachment-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.";
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 container provider-dhcp {
"Defines how addresses are allocated. when "derived-from-or-self(../address-allocation-type, "+
If there is no value for the address "'l3vpn-ntw:provider-dhcp')" {
allocation type, then IPv4 is not enabled."; description
"Only applies when addresses are allocated by DHCP.";
} }
container provider-dhcp { leaf provider-address {
when "derived-from-or-self(../address-allocation-type, "+ type inet:ipv4-address;
"'l3vpn-ntw:provider-dhcp')" { description
description "Address of provider side. If provider-address is not
"Only applies when addresses are allocated by DHCP."; specified, then prefix length should not be specified
} either. It also implies provider-dhcp allocation is
leaf provider-address { not enabled. If provider-address is specified, then
type inet:ipv4-address; the prefix length may or may not be specified.";
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)" { leaf prefix-length {
error-message type uint8 {
"If the prefix length is specified, provider-address range "0..32";
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.";
} }
} must "(../provider-address)" {
case explicit { error-message
container customer-addresses { "If the prefix length is specified, provider-address
list address-group { must also be specified.";
key "group-id"; description
leaf group-id { "If the prefix length is specified, provider-address
type string; must also be specified.";
description
"Group-id for the address range from
start-address to end-address.";
} }
leaf start-address { description
type inet:ipv4-address; "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 description
"First address."; "Describes the number of IP addresses
} the customer requires.";
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.";
} }
case explicit {
container customer-addresses {
list address-group {
key "group-id";
leaf group-id {
type string;
description
"Group-id for the address range from
start-address to end-address.";
}
leaf start-address {
type inet:ipv4-address;
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.";
} }
description container dhcp-relay {
"Choice for the way to assign addresses."; when "derived-from-or-self(../address-allocation-type, "+
} "'l3vpn-ntw:provider-dhcp-relay')" {
description description
"DHCP allocated addresses related parameters."; "Only applies when provider is required to implement
} DHCP relay function.";
container dhcp-relay { }
when "derived-from-or-self(../address-allocation-type, "+ leaf provider-address {
"'l3vpn-ntw:provider-dhcp-relay')" { type inet:ipv4-address;
description description
"Only applies when provider is required to implement "Address of provider side. If provider-address is not
DHCP relay function."; specified, then prefix length should not be specified
} either. It also implies provider-dhcp allocation is
leaf provider-address { not enabled. If provider-address is specified, then
type inet:ipv4-address; prefix length may or may not be specified.";
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
prefix length may or may not be specified.";
}
leaf prefix-length {
type uint8 {
range "0..32";
} }
must "(../provider-address)" { leaf prefix-length {
error-message type uint8 {
"If prefix length is specified, provider-address 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."; 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 description
"Container for list of customer DHCP servers."; "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.";
} }
description container static-addresses {
"DHCP relay provided by operator."; when "derived-from-or-self(../address-allocation-type, "+
} "'l3vpn-ntw:static-address')" {
container addresses { description
when "derived-from-or-self(../address-allocation-type, "+ "Only applies when protocol allocation type is static.";
"'l3vpn-ntw:static-address')" {
description
"Only applies when protocol allocation type is static.";
}
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 { leaf primary-address{
type inet:ipv4-address; type leafref {
description path "/l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/"+
"IPv4 Address of customer side."; "vpn-node/vpn-network-accesses/vpn-network-access/"+
"ip-connection/ipv4/static-addresses/address/address-id";
} }
leaf prefix-length {
type uint8 {
range "0..32";
}
description description
"Subnet prefix length expressed in bits. "Principal address of the connection.";
It is applied to both provider-address }
and customer-address."; 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 description
"Describes IPv4 addresses used."; "Describes IPv4 addresses used.";
}
description
"IPv4-specific parameters.";
}
container ipv6 {
if-feature ipv6;
leaf address-allocation-type {
type identityref {
base address-allocation-type;
} }
description description
"Defines how addresses are allocated. "IPv4-specific parameters.";
If there is no value for the address
allocation type, then IPv6 is
not enabled.";
} }
container ipv6 {
container provider-dhcp { if-feature ipv6;
when "derived-from-or-self(../address-allocation-type, "+ leaf address-allocation-type {
"'l3vpn-ntw:provider-dhcp') "+ type identityref {
"or derived-from-or-self(../address-allocation-type, "+ base address-allocation-type;
"'l3vpn-ntw:provider-dhcp-slaac')" { }
description description
"Only applies when addresses are allocated by DHCP."; "Defines how addresses are allocated.
} If there is no value for the address
leaf provider-address { allocation type, then IPv6 is
type inet:ipv6-address; not enabled.";
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; container provider-dhcp {
case number { when "derived-from-or-self(../address-allocation-type, "+
leaf number-of-dynamic-address { "'l3vpn-ntw:provider-dhcp') "+
type uint16; "or derived-from-or-self(../address-allocation-type, "+
default 1; "'l3vpn-ntw:provider-dhcp-slaac')" {
description description
"Describes the number of IP addresses the customer "Only applies when addresses are allocated by DHCP.";
requires."; }
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 {
case explicit { type uint8 {
container customer-addresses { range "0..128";
list address-group { }
key "group-id"; must "(../provider-address)" {
leaf group-id { error-message
type string; "If prefix length is specified, provider-address
description must also be specified.";
"Group-id for the address range from description
start-address to end-address."; "If prefix length is specified, provider-address
must also be specified.";
} }
leaf start-address { description
type inet:ipv6-address; "Subnet prefix length expressed in bits. If not
specified, or specified as zero, this means the
customer leaves the actual prefix length value
to the provider.";
}
choice address-assign {
default number;
case number {
leaf number-of-dynamic-address {
type uint16;
default 1;
description
"Describes the number of IP addresses the customer
requires.";
}
}
case explicit {
container customer-addresses {
list address-group {
key "group-id";
leaf group-id {
type string;
description description
"First address."; "Group-id for the address range from
} start-address to end-address.";
leaf end-address { }
type inet:ipv6-address; leaf start-address {
type inet:ipv6-address;
description
"First address.";
}
leaf end-address {
type inet:ipv6-address;
description
"Last address.";
}
description description
"Last address."; "Describes IP addresses allocated by DHCP. When only
} start-address or only end-address is present, it
description represents a single address. When both start-address
"Describes IP addresses allocated by DHCP. When only and end-address are specified, it implies a range
start-address or only end-address is present, it inclusive of both addresses. If no address is
represents a single address. When both start-address specified, it implies customer addresses group is
and end-address are specified, it implies a range not supported.";
inclusive of both addresses. If no address is }
specified, it implies customer addresses group is description
not supported."; "Container for customer addresses allocated by DHCP.";
} }
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.";
}
leaf provider-address {
type inet:ipv6-address;
description description
"Address of the provider side. If provider-address is "Choice for the way to assign addresses.";
not specified, then prefix length should not be }
specified either. It also implies provider-dhcp description
allocation is not enabled. If provider address "DHCP allocated addresses related parameters.";
is specified, then prefix length may or may }
not be specified."; container dhcp-relay {
} when "derived-from-or-self(../address-allocation-type, "+
leaf prefix-length { "'l3vpn-ntw:provider-dhcp-relay')" {
type uint8 { description
range "0..128"; "Only applies when the provider is required
} to implement DHCP relay function.";
must "(../provider-address)" { }
error-message 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 "If prefix length is specified, provider-address
must also be specified."; must also be specified.";
}
description description
"If prefix length is specified, provider-address "Subnet prefix length expressed in bits. If not
must also be specified."; 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
"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 description
"Subnet prefix length expressed in bits. If not "IPv4 Address";
specified, or specified as zero, this means the
customer leaves the actual prefix length value
to the provider.";
} }
container customer-dhcp-servers { leaf provider-address {
leaf-list server-ip-address {
type inet:ipv6-address; type inet:ipv6-address;
description description
"This node contains the IP address of "IPv6 Address of the provider side. When the protocol
the customer DHCP server. If the DHCP relay allocation type is static, the provider address
function is implemented by the must be configured.";
provider, this node contains the }
configured value."; leaf customer-address {
} type inet:ipv6-address;
description
"The IPv6 Address of the customer side.";
}
leaf prefix-length {
type uint8 {
range "0..128";
}
description description
"Container for list of customer DHCP servers."; "Subnet prefix length expressed in bits.
It is applied to both provider-address and
customer-address.";
} }
description
"DHCP relay provided by operator.";
}
container addresses {
when "derived-from-or-self(../address-allocation-type, "+
"'l3vpn-ntw:static-address')" {
description description
"Only applies when protocol allocation type is static."; "Describes IPv6 addresses used.";
}
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 { description
type uint8 { "IPv6-specific parameters.";
range "0..128";
} }
description description
"Subnet prefix length expressed in bits. "IPv6-specific parameters.";
It is applied to both provider-address and
customer-address.";
}
description
"Describes IPv6 addresses used.";
} }
description container oam {
"IPv6-specific parameters."; container bfd {
} if-feature bfd;
container oam { leaf enabled {
container bfd { type boolean;
if-feature bfd; default false;
leaf enabled { description
type boolean; "If true, BFD activation is required.";
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 { choice holdtime {
leaf profile-name { default fixed;
type leafref { case fixed {
path "/l3vpn-ntw/vpn-profiles/valid-provider-identifiers/"+ leaf fixed-value {
"bfd-profile-identifier/id"; 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 description
"Well-known SP profile name. The provider can propose "Well-known SP profile.";
some profiles to the customer, depending on the service
level the customer wants to achieve. Profile names
must be communicated to the customer.";
} }
description description
"Well-known SP profile."; "Choice for holdtime flavor.";
} }
description description
"Choice for holdtime flavor."; "Container for BFD.";
} }
description description
"Container for BFD."; "Defines the Operations, Administration, and Maintenance (OAM)
mechanisms used on the connection. BFD is set as a fault
detection mechanism, but the 'oam' container can easily
be augmented by other mechanisms";
} }
description description
"Defines the Operations, Administration, and Maintenance (OAM) "Defines connection parameters.";
mechanisms used on the connection. BFD is set as a fault
detection mechanism, but the 'oam' container can easily
be augmented by other mechanisms";
} }
description description
"Defines connection parameters."; "This grouping defines IP connection parameters.";
} }
description grouping site-service-multicast {
"This grouping defines IP connection parameters."; container multicast {
} if-feature multicast;
grouping site-service-multicast { leaf multicast-site-type {
container multicast { type enumeration {
if-feature multicast; enum receiver-only {
leaf multicast-site-type { description
type enumeration { "The site only has receivers.";
enum receiver-only { }
description enum source-only {
"The site only has receivers."; description
"The site only has sources.";
}
enum source-receiver {
description
"The site has both sources and receivers.";
}
} }
enum source-only { default source-receiver;
description
"Type of multicast site.";
}
container multicast-address-family {
leaf ipv4 {
if-feature ipv4;
type boolean;
default false;
description description
"The site only has sources."; "Enables IPv4 multicast.";
} }
enum source-receiver { leaf ipv6 {
if-feature ipv6;
type boolean;
default false;
description description
"The site has both sources and receivers."; "Enables IPv6 multicast.";
} }
}
default source-receiver;
description
"Type of multicast site.";
}
container multicast-address-family {
leaf ipv4 {
if-feature ipv4;
type boolean;
default false;
description description
"Enables IPv4 multicast."; "Defines protocol to carry multicast.";
} }
leaf ipv6 {
if-feature ipv6; leaf protocol-type {
type boolean; type enumeration {
default false; 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 description
"Enables IPv6 multicast."; "Multicast protocol type to be used with the customer site.";
} }
description description
"Defines protocol to carry multicast."; "Multicast parameters for the site.";
} }
leaf protocol-type { description
type enumeration { "Multicast parameters for the site.";
enum host { }
description grouping site-maximum-routes {
"Hosts are directly connected to the provider network. container maximum-routes {
Host protocols such as IGMP or MLD are required."; list address-family {
} key af;
enum router { leaf af {
type address-family;
description description
"Hosts are behind a customer router. "Address family.";
PIM will be implemented.";
} }
enum both { leaf maximum-routes {
type uint32;
description description
"Some hosts are behind a customer router, and "Maximum prefixes the VRF can accept
some others are directly connected to the for this address family.";
provider network. Both host and routing protocols
must be used. Typically, IGMP and PIM will be
implemented.";
} }
description
"List of address families.";
} }
default "both";
description description
"Multicast protocol type to be used with the customer site."; "Defines 'maximum-routes' for the VRF.";
} }
description description
"Multicast parameters for the site."; "Defines 'maximum-routes' for the site.";
} }
description grouping site-security {
"Multicast parameters for the site."; container security {
} uses site-security-authentication;
grouping site-management { uses site-security-encryption;
container management {
leaf type {
type identityref {
base management;
}
mandatory true;
description description
"Management type of the connection."; "Site-specific security parameters.";
} }
description description
"Management configuration."; "Grouping for security parameters.";
}
description
"Management parameters for the site.";
}
grouping site-devices {
container devices {
when "derived-from-or-self(../management/type, "+
"'l3vpn-ntw:provider-managed') or "+
"derived-from-or-self(../management/type, 'l3vpn-ntw:co-managed')" {
description
"Applicable only for provider-managed or
co-managed device.";
} }
list device { grouping network-access-service {
key device-id; container service {
leaf device-id { uses site-service-basic;
type svc-id; /* Extension */
/* uses svc-bandwidth-params; */
/* EoExt */
uses site-service-qos-profile;
uses site-service-mpls;
uses site-service-multicast;
description description
"