| L2SM Working Group | B. Wen |
| Internet-Draft | Comcast |
| Intended status: Standards Track | G. Fioccola |
| Expires: August 19, 2017 | Telecom Italia |
| C. Xie | |
| China Telecom | |
| L. Jalil | |
| Verizon | |
| February 15, 2017 |
A YANG Data Model for L2VPN Service Delivery
draft-wen-l2sm-l2vpn-service-model-04
This document defines a YANG data model that can be used to configure a Layer 2 Provider Provisioned VPN service.
This model is intended to be instantiated at management system to deliver the overall service. This model is not a configuration model to be used directly on network elements, but provides an abstracted view of the Layer 2 VPN service configuration components. It is up to a management system to take this as an input and use specific configurations models to configure the different network elements to deliver the service. How configuration of network elements is done is out of scope of the document.
The data model in this document includes support for point-to-point Virtual Private Wire Services (VPWS) and multipoint Virtual Private LAN services (VPLS) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFC4761 and RFC6624.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 19, 2017.
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This document defines a YANG data model for Layer 2 VPN (L2VPN) service configuration. This model is intended to be instantiated at management system to allow a user (a customer or an application) to request the service from a service provider. This model is not a configuration model to be used directly on network elements, but provides an abstracted view of the L2VPN service configuration components. It is up to a management system to take this as an input and use specific configurations models to configure the different network elements to deliver the service. How configuration of network elements is done is out of scope of the document.
The data model in this document includes support for point-to-point Virtual Private Wire Services (VPWS) and multipoint Virtual Private LAN services (VPLS) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in [RFC4761] and [RFC6624].
Further discussion of the way that services are modelled in YANG and of the relationship between "customer service models" like the one described in this document and configuration models can be found in [I-D.wu-opsawg-service-model-explained]. Section 4 and Section 6 also provide more information of how this service model could be used and how it fits into the overall modelling architecture.
The following terms are defined in [RFC6241] and are not redefined here:
The following terms are defined in [RFC6020] and are not redefined here:
The terminology for describing YANG data models is found in [RFC6020].
A simplified graphical representation of the data model is presented in Section 5.
The meaning of the symbols in these diagrams is as follows:
This document uses the following terms:
This document uses the following abbreviations:
A Layer 2 VPN service is a collection of sites that are authorized to exchange traffic between each other over a shared infrastructure of a common technology. This Layer 2 VPN service model (L2SM) provides a common understanding of how the corresponding Layer 2 VPN service is to be deployed over the shared infrastructure.
This document presents the L2SM using the YANG data modeling language [RFC6020] as a formal language that is both human-readable and parsable by software for use with protocols such as NETCONF [RFC6241] and RESTCONF [RFC8040].
This service model is limited to VPWS and VPLS based VPNs as described in [RFC4761] and [RFC6624].
The L2SM defined in this document applies to both point-to-point (E-Line) and multipoint-to-multipoint (E-LAN) carrier Ethernet services.
Over the past decade, The MEF Forum (MEF) has published a series of technical specifications of Ethernet virtual circuit service attributes and implementation agreements between providers. Many Ethernet VPN service providers worldwide have adopted these MEF standards and developed backoffice tools accordingly.
Rather than introducing a new set of terminologies, the L2SM will align with existing MEF attributes when it's applicable. Therefore, service providers can easily integrate any new application that leverages the L2SM data (for example, a Service Orchestrator), with existing BSS/OSS toolsets. Service providers also have the option to generate L2SM data for current L2VPN customer circuits already deployed in the network.
A Layer 2 VPN circuit can be port-based, in which case any service frames received from a subscriber within the contracted bandwidth will be delivered to the corresponding remote site, regardless of the customer VLAN value (C-tag) of the incoming frame. The service frames can also be native Ethernet frames without a C-tag: in this scenario, only one Ethernet Virtual Circuit (EVC) is allowed on a single provider to subscriber link.
Contrary to the above use case, incoming customer service frames may be split into multiple EVCs based on pre-arrangement between the service provider and customer. Typically, C-tag of the incoming frames will serve as the service delimiter for EVC multiplexing over the same provider to subscriber interconnection.
Combining the service-multiplexing attribute with the connection type (point-to-point or multipoint-to-multipoint), a Layer 2 VPN circuit may fall into one of the following service types:
Figure 1depicts a typical service provider's physical network topology. Most service providers have deployed an IP, MPLS, or Segment Routing (SR) multi-service core infrastructure. Customer Edge (CE) devices are placed at customer premises as demarcation points that backhaul in-profile service frames from the subscriber over the access network to the Provider Edge (PE) equipment. The actual transport technology or physical topology between CE and PE is outside the scope of the L2SM model.
--- ---- ---
| | | | | |
| C +---+ CE | | C |
| | | | --------- | |
--- ----\ ( ) /---
\ ---- ( ) ---- ---- /
\| | ( ) | | | |/
| PE +---+ IP/MPLS/SR +---+ PE +---+ CE |
/| | ( Network ) | | | |\
/ ---- ( ) ---- ---- \
--- ----/ ( ) \---
| | | | ----+---- | |
| C +---+ CE | | | C |
| | | | --+-- | |
--- ---- | PE | ---
--+--
|
--+--
| CE |
--+--
|
--+--
| C |
-----
Figure 1: Reference Network for the Use of the L2VPN Service Model
From the subscriber perspective, however, all the edge networks devices are connected over a simulated LAN environment as shown in Figure 2. Broadcast and multicast packets are sent to all participants in the same bridge domain.
C---+----+---+---C
| | |
| | |
| | |
C---+ C +---C
Figure 2: Customer View of the L2VPN
The base model of EVC is shown in Figure 3.
Subscriber edge network device (C) connects to the service provider's CE equipment. The link between C and CE devices is referred as the User Network Interface (UNI). For clarification, this is called the UNI-C on the subscriber side and UNI-N on the provider side.
The service provider is obligated to deliver the original service frame across the network to the remote UNI-C. All Ethernet and IP header information, including (but not limit to) source and destination MAC addresses, EtherType, VLAN (C-tag), Class-of-Service marking (802.1p or DSCP), etc.
In coming service frames are first examined at UNI-N based on C-tag, Class-of-Services identifier, EtherType value. Conforming packets are then metered against the contractual service bandwidth. In-profile packets will be delivered to the remote UNI via the Ethernet Virtual Circuit (EVC), which spans between UNI-N and UNI-N.
When both CEs are located in the same provider's network, a single operator maintains the EVC. In this case, the EVC consists only one Operator Virtual Circuit (OVC).
Typically, the CE device at customer premises is a layer 2 Ethernet switch or NID. A service provider may choose to impose an outer VLAN tag (S-tag) into the received subscriber traffic following 802.1ad Q-in-Q standard, especially when Layer 2 aggregation devices exist between CE and PE.
The uplink from CE to PE is referred as an Internal Network-to-Network Interface (I-NNI). When 802.1ad Q-in-Q is implemented, Ethernet frames from CE to PE are double tagged with both provider and subscriber VLANs (S-tag, C-tag).
Most service providers have deployed MPLS or SR multi-service core infrastructure. Ingress service frames will be mapped to either Ethernet Pseudowire (PWE) or VxLAN tunnel PE-to-PE. The details of these tunneling mechanism are at the provider's discretion and not part of the L2SM.
The service provider may also choose a Seamless MPLS approach to expand the PWE or VxLAN tunnel between UNI-N to UNI-N.
The service provider may leverage multi-protocol BGP to auto-discover and signal the PWE or VxLAN tunnel end points.
EVC
:<-------------------------------------------->:
: :
: :
: OVC (Optional) :
:<-------------------------------------------->:
: :
: :
: PW / VXLAN :
: :<-------------------------->: :
: : : :
: : : :
: : -------- : :
: : ( ) : :
--- ---- ---- ( ) ---- ---- ---
| | | | | | ( ) | | | | | |
| C +---+ CE +---+ PE +---+ IP/MPLS/SR +---+ PE +---+ CE +---+ C |
| | | | | | ( Network ) | | | | | |
--- ---- ---- ( ) ---- ---- ---
^ ^ : ( ) : :
: : : -------- : :
UNI-C UNI-N : : :
: : : :
:<------>:<-------------------------->:<------>:
802.1ad IP/MPLS/SR Domain 802.1ad
q-in-q q-in-q
Figure 3: Architectural Model for EVC over a Single Network
Nevertheless, the remote site may be outside of the provider's service territory. In this case, the provider may partner with the operator of another metro network to provide service to the off-net location as shown in Figure 4.
The first provider owns the customer relationship, thus the end-to-end EVC. The EVC is comprised of two or more OVCs. The EVC is partially composed of an OVC from local the UNI-C to the inter-provider interface. The provider will purchase an Ethernet Access (E-Access) OVC from the second operator to deliver packet to the remote UNI-C.
The inter-connect between the two operators edge gateway (EG) devices is defined as the External Network-to-Network Interface (E-NNI).
EVC
:<---------------------------------------------------->:
: :
: :
: OVC (Optional) :
:<----------------------->: :
: : :
: : :
: PW / VXLAN : :
: :<------------------>: :
: : : :
: : : :
: : ----- : ----- :
: : ( ) : ( ) :
- -- -- ( IP/ ) ---- ---- ( IP/ ) -- -- -
|C+-+CE+-+PE+--+ MPLS/ +--+Edge+--+Edge+--+ MPLS/ +--+PE+-+CE+-+C|
- -- -- ( SR ) |G/W | |G/W | ( SR ) -- -- -
^ ^ : ( ) ---- ---- ( ) ^
: : : ----- ^ ^ ----- :
UNI UNI : ENNI ENNI :
C N : : : :
: : : : Remote
:<->:<------------------>:<->: Customer
802.1ad IP/MPLS/SR 802.1ad Site
q-in-q Domain q-in-q
Figure 4: Architectural Model for EVC over Multiple Networks
The L2VPN service model provides an abstracted interface to request, configure, and manage the components of a L2VPN service. The model is used by a customer who purchases connectivity and other services from an SP to communicate with that SP.
A typical usage for this model is to be an input to an orchestration layer that is responsible for translating it into configuration commands for the network elements that deliver/enable the service. The network elements may be routers, but also servers (like AAA) that are necessary within the network.
The configuration of network elements may be done using the Command Line Interface (CLI), or any other configuration (or "southbound") interface such as NETCONF [RFC6241] in combination with device-specific and protocol-specific YANG models.
This way of using the service model is illustrated in Figure 5 and described in more detail in [I-D.wu-opsawg-service-model-explained]. The usage of this service model is not limited to this example: it can be used by any component of the management system, but not directly by network elements.
The usage and structure of this model should be compared to the Layer 3 VPN service model defined in [I-D.ietf-l3sm-l3vpn-service-model].
----------------------------
| Customer Service Requester |
----------------------------
|
L2VPN |
Service |
Model |
|
-----------------------
| Service Orchestration |
-----------------------
|
| Service +-------------+
| Delivery +------>| Application |
| Model | | BSS/OSS |
| V +-------------+
-----------------------
| Network Orchestration |
-----------------------
| |
+----------------+ |
| Config manager | |
+----------------+ | Device
| | Models
| |
--------------------------------------------
Network
Figure 5: Reference Architecture for the Use of the L2VPN Service Model
Additionally, this data model can be compared with the service delivery models described in [I-D.ietf-bess-l2vpn-yang] and [I-D.ietf-bess-evpn-yang] as discussed in Section 6.
The YANG module is divided in three main containers: customer-info, vpn-services, and sites.
The customer-info defines global parameters for a specific customer.
The vpn-svc container under vpn-services defines global parameters for the VPN service for a specific customer.
A site contains at least one port (i.e., ports providing access to the sites defined in Section 5.1.3.1.8) and there may be multiple ports in case of multihoming. The site to port attachment is done through a bearer with a Layer 2 connection on top. The bearer refers to properties of the attachment that are below layer 2 while the connection refers to layer 2 protocol oriented properties. The bearer may be allocated dynamically by the service provider and the customer may provide some constraints or parameters to drive the placement.
Authorization of traffic exchange is done through what we call a VPN policy or VPN topology defining routing exchange rules between sites.
The figure below describe the overall structure of the YANG module:
module: ietf-l2vpn-svc
+--rw l2vpn-svc
+--rw customer-info
| +--rw customer-info* [customer-account-number customer-name]
| +--rw customer-account-number uint32
| +--rw customer-name string
| +--rw customer-operation-center
| +--rw customer-noc-street-address? string
| +--rw customer-noc-phone-number
| +--rw main-phone-num? uint32
| +--rw extension-options? uint32
+--rw vpn-services
| +--rw vpn-svc* [vpn-id]
| +--rw vpn-id svc-id
| +--rw svc-type? identityref
| +--rw evc-type
| | +--rw evc-id? svc-id
| | +--ro number-of-pe? uint32
| | +--ro number-of-site? uint32
| | +--rw uni-list {uni-list}?
| | +--rw uni-list* [network-access-id]
| | +--rw network-access-id string
| +--rw ovc-type {ovc-type}?
| | +--rw ovc-list* [ovc-id]
| | +--rw ovc-id svc-id
| | +--rw on-net? boolean
| | +--rw off-net? boolean
| +--rw ethernet-svc-type
| | +--rw (ethernet-svc-type)?
| | +--:(e-line)
| | | +--rw epl? boolean
| | | +--rw evpl? boolean
| | +--:(e-lan)
| | | +--rw ep-lan? boolean
| | | +--rw evp-lan? boolean
| | +--:(e-access)
| | +--rw access-epl? boolean
| | +--rw access-evpl? boolean
| +--rw svc-topo? identityref
| +--rw cloud-accesses {cloud-access}?
| | +--rw cloud-access* [cloud-identifier]
| | +--rw cloud-identifier string
| | +--rw (list-flavor)?
| | | +--:(permit-any)
| | | | +--rw permit-any? empty
| | | +--:(deny-any-except)
| | | | +--rw permit-site* -> /l2vpn-svc/sites/site/site-id
| | | +--:(permit-any-except)
| | | +--rw deny-site* -> /l2vpn-svc/sites/site/site-id
| | +--rw authorized-sites
| | | +--rw authorized-site* [site-id]
| | | +--rw site-id -> /l2vpn-svc/sites/site/site-id
| | +--rw denied-sites
| | +--rw denied-site* [site-id]
| | +--rw site-id -> /l2vpn-svc/sites/site/site-id
| +--rw ce-vlan-preservation
| +--rw metro-network-id
| | +--rw inter-mkt-service? boolean
| | +--rw intra-mkt* [metro-mkt-id mkt-name]
| | +--rw metro-mkt-id uint32
| | +--rw mkt-name string
| | +--rw ovc-id? string
| +--rw L2CP-control
| | +--rw stp-rstp-mstp? control-mode
| | +--rw pause? control-mode
| | +--rw lldp? boolean
| +--rw load-balance-options
| | +--rw fat-pw? boolean
| | +--rw entropy-label? boolean
| | +--rw vxlan-source-port? string
| +--rw svlan-id-ethernet-tag? string
| +--rw cvlan-id-to-evc-map* [evc-id type]
| | +--rw evc-id -> /l2vpn-svc/vpn-services/vpn-svc/vpn-id
| | +--rw type identityref
| | +--rw cvlan-id* [vid]
| | +--rw vid identityref
| +--rw service-level-mac-limit? string
| +--rw service-protection
| | +--rw protection-model
| | +--rw peer-evc-id
| +--rw sla-targets
+--rw sites
+--rw site* [site-id site-type]
+--rw site-id string
+--rw site-type identityref
+--rw device
| +--rw devices* [device-id]
| +--rw device-id string
| +--rw site-name? string
| +--rw management
| +--rw address? inet:ip-address
| +--rw management-transport? identityref
+--rw managemnt
| +--rw type? identityref
+--rw location
| +--rw address? string
| +--rw zip-code? string
| +--rw state? string
| +--rw city? string
| +--rw country-code? string
+--rw site-diversity {site-diversity}?
| +--rw groups
| +--rw group* [group-id]
| +--rw group-id string
+--rw vpn-policies
| +--rw vpn-policy* [vpn-policy-id]
| +--rw vpn-policy-id string
| +--rw entries* [id]
| +--rw id string
| +--rw filter
| | +--rw (lan)?
| | +--:(lan-tag)
| | +--rw lan-tag* string
| +--rw vpn
| +--rw vpn-id
| | -> /l2vpn-svc/vpn-services/vpn-svc/vpn-id
| +--rw site-role? identityref
+--rw signaling-option {signaling-option}?
| +--rw signaling-option* [type]
| +--rw type identityref
| +--rw mp-bgp-l2vpn
| | +--rw vpn-id? svc-id
| | +--rw type? identityref
| +--rw mp-bgp-evpn
| | +--rw vpn-id? svc-id
| | +--rw type? identityref
| | +--rw mac-learning-mode? identityref
| | +--rw arp-suppress? boolean
| +--rw t-ldp-pwe
| | +--rw PE-EG-list* [service-ip-lo-addr vc-id]
| | +--rw service-ip-lo-addr inet:ip-address
| | +--rw vc-id string
| +--rw pwe-encapsulation-type
| | +--rw ethernet? boolean
| | +--rw vlan? boolean
| +--rw pwe-mtu
| | +--rw allow-mtu-mismatch? boolean
| +--rw control-word
+--rw load-balance-options
| +--rw fat-pw? boolean
| +--rw entropy-label? boolean
| +--rw vxlan-source-port? string
+--ro actual-site-start? yang:date-and-time
+--ro actual-site-stop? yang:date-and-time
+--rw ports
+--rw port* [network-access-id]
+--rw network-access-id string
+--rw remote-carrier-name? string
+--rw access-diversity {site-diversity}?
| +--rw groups
| | +--rw fate-sharing-group-size? uint16
| | +--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 request-type-profile
| | +--rw (request-type-choice)?
| | +--:(dot1q-case)
| | | +--rw dot1q
| | | +--rw physical-if? string
| | | +--rw vlan-id? uint16
| | +--:(physical-case)
| | +--rw physical-if? string
| | +--rw circuit-id? string
| +--rw always-on? boolean {always-on}?
| +--rw bearer-reference? string {bearer-reference}?
+--rw ethernet-connection
| +--rw ESI? string
| +--rw interface-description? string
| +--rw vlan
| | +--rw vlan-id? uint32
| +--rw dot1q
| | +--rw physical-inf? string
| | +--rw vlan-id? uint32
| +--rw qinq
| | +--rw s-vlan-id? uint32
| | +--rw c-vlan-id? uint32
| +--rw sub-if-id? uint32
| +--rw vxlan
| | +--rw vni-id? uint32
| | +--rw peer-list* [peer-ip]
| | +--rw peer-ip inet:ip-address
| +--rw phy-interface
| | +--rw port-number? uint32
| | +--rw port-speed? uint32
| | +--rw mode? neg-mode
| | +--rw phy-mtu? uint32
| | +--rw flow-control? string
| | +--rw encapsulation-type? enumeration
| | +--rw ethertype? string
| | +--rw lldp? boolean
| | +--rw oam-802.3AH-link {oam-3ah}?
| | | +--rw enable? boolean
| | +--rw uni-loop-prevention? boolean
| +--rw LAG-interface
| +--rw LAG-interface* [LAG-interface-number]
| +--rw LAG-interface-number uint32
| +--rw LACP
| +--rw LACP-state? boolean
| +--rw LACP-mode? boolean
| +--rw LACP-speed? boolean
| +--rw mini-link? uint32
| +--rw system-priority? uint16
| +--rw Micro-BFD {Micro-BFD}?
| | +--rw Micro-BFD-on-off? enumeration
| | +--rw bfd-interval? uint32
| | +--rw bfd-hold-timer? uint32
| +--rw bfd {bfd}?
| | +--rw bfd-enabled? boolean
| | +--rw (holdtime)?
| | +--:(profile)
| | | +--rw profile-name? string
| | +--:(fixed)
| | +--rw fixed-value? uint32
| +--rw Member-link-list
| | +--rw member-link* [name]
| | +--rw name string
| | +--rw port-speed? uint32
| | +--rw mode? neg-mode
| | +--rw mtu? uint32
| | +--rw oam-802.3AH-link {oam-3ah}?
| | +--rw enable? boolean
| +--rw flow-control? string
| +--rw encapsulation-type? enumeration
| +--rw ethertype? string
| +--rw lldp? boolean
+--rw L2CP-control
| +--rw stp-rstp-mstp? control-mode
| +--rw pause? control-mode
| +--rw lacp-lamp? control-mode
| +--rw link-oam? control-mode
| +--rw esmc? control-mode
| +--rw l2cp-802.1x? control-mode
| +--rw e-lmi? control-mode
| +--rw lldp? boolean
| +--rw ptp-peer-delay? control-mode
| +--rw garp-mrp? control-mode
| +--rw provider-bridge-group? control-mode
| +--rw provider-bridge-mvrp? control-mode
+--rw evc-mtu? uint32
+--rw availability
| +--rw (redundancy-mode)?
| +--:(single-active)
| | +--rw single-active? boolean
| +--:(all-active)
| +--rw all-active? boolean
+--rw vpn-attachment
| +--rw device-id? string
| +--rw management
| | +--rw address-family? identityref
| | +--rw address? inet:ip-address
| +--rw (attachment-flavor)
| +--:(vpn-id)
| +--rw vpn-id?
| | -> /l2vpn-svc/vpn-services/vpn-svc/vpn-id
| +--rw site-role? identityref
+--rw service
| +--rw svc-input-bandwidth {input-bw}?
| | +--rw input-bandwidth* [id type]
| | +--rw id string
| | +--rw type identityref
| | +--rw evc-id? svc-id
| | +--rw CIR? uint32
| | +--rw CBS? uint32
| | +--rw EIR? uint32
| | +--rw EBS? uint32
| | +--rw CM? uint32
| +--rw svc-output-bandwidth {output-bw}?
| | +--rw output-bandwidth* [id type]
| | +--rw id string
| | +--rw type identityref
| | +--rw evc-id? svc-id
| | +--rw CIR? uint32
| | +--rw CBS? uint32
| | +--rw EIR? uint32
| | +--rw EBS? uint32
| | +--rw CM? uint32
| +--rw svlan-id-ethernet-tag? string
| +--rw cvlan-id-to-evc-map* [evc-id type]
| | +--rw evc-id
| | | -> /l2vpn-svc/vpn-services/vpn-svc/vpn-id
| | +--rw type identityref
| | +--rw cvlan-id* [vid]
| | +--rw vid identityref
| +--rw service-level-mac-limit? string
| +--rw service-multiplexing? boolean
| +--rw qos {qos}?
| +--rw qos-classification-policy
| | +--rw rule* [id]
| | +--rw id uint16
| | +--rw (match-type)?
| | | +--:(match-flow)
| | | | +--rw match-flow
| | | | +--rw dscp? inet:dscp
| | | | +--rw dot1p? uint8
| | | | +--rw pcp? uint8
| | | | +--rw src-mac? yang:mac-address
| | | | +--rw dst-mac? yang:mac-address
| | | | +--rw cos-color-id
| | | | | +--rw device-id? string
| | | | | +--rw cos-label? identityref
| | | | | +--rw pcp? uint8
| | | | | +--rw dscp? inet:dscp
| | | | +--rw color-type? identityref
| | | | +--rw target-sites* svc-id
| | | +--:(match-phy-port)
| | | +--rw match-phy-port? uint16
| | +--rw target-class-id? string
| +--rw qos-profile
| +--rw (qos-profile)?
| +--:(standard)
| | +--rw ingress-profile? string
| | +--rw egress-profile? string
| +--:(custom)
| +--rw classes {qos-custom}?
| +--rw class* [class-id]
| +--rw class-id string
| +--rw direction? direction-type
| +--rw policing? identityref
| +--rw byte-offset? uint16
| +--rw perf-tier-opt? identityref
| +--rw rate-limit? uint8
| +--rw discard-percentage? uint8
| +--rw frame-delay
| | +--rw (flavor)?
| | +--:(lowest)
| | | +--rw use-low-del? empty
| | +--:(boundary)
| | +--rw delay-bound? uint16
| +--rw frame-jitter
| | +--rw (flavor)?
| | +--:(lowest)
| | | +--rw use-low-jit? empty
| | +--:(boundary)
| | +--rw delay-bound? uint32
| +--rw frame-loss
| +--rw fr-loss-rate? decimal64
+--rw Ethernet-Service-OAM
| +--rw MD-name? string
| +--rw MD-level? uint8
| +--rw cfm-802.1-ag
| | +--rw n2-uni-c* [MAID]
| | | +--rw MAID string
| | | +--rw mep-id? uint32
| | | +--rw mep-level? uint32
| | | +--rw mep-up-down? enumeration
| | | +--rw remote-mep-id? uint32
| | | +--rw cos-for-cfm-pdus? uint32
| | | +--rw ccm-interval? uint32
| | | +--rw ccm-holdtime? uint32
| | | +--rw alarm-priority-defect? identityref
| | | +--rw ccm-p-bits-pri? ccm-priority-type
| | +--rw n2-uni-n* [MAID]
| | +--rw MAID string
| | +--rw mep-id? uint32
| | +--rw mep-level? uint32
| | +--rw mep-up-down? enumeration
| | +--rw remote-mep-id? uint32
| | +--rw cos-for-cfm-pdus? uint32
| | +--rw ccm-interval? uint32
| | +--rw ccm-holdtime? uint32
| | +--rw alarm-priority-defect? identityref
| | +--rw ccm-p-bits-pri? ccm-priority-type
| +--rw y-1731* [MAID]
| +--rw MAID string
| +--rw mep-id? uint32
| +--rw type? identityref
| +--rw remote-mep-id? uint32
| +--rw message-period? uint32
| +--rw measurement-interval? uint32
| +--rw cos? uint32
| +--rw loss-measurement? boolean
| +--rw synthethic-loss-measurement? boolean
| +--rw delay-measurement
| | +--rw enable-dm? boolean
| | +--rw two-way? boolean
| +--rw frame-size? uint32
| +--rw session-type? enumeration
+--rw security-filtering
+--rw mac-loop-prevention
| +--rw frequency? uint32
| +--rw protection-type? identityref
| +--rw number-retries? uint32
+--rw access-control-list
| +--rw mac* [mac-address]
| +--rw mac-address yang:mac-address
+--rw mac-addr-limit
| +--rw exceeding-option? uint32
+--rw B-U-M-storm-control
+--rw BUM-overall-rate? uint32
+--rw BUM-rate-per-type* [type]
+--rw type identityref
+--rw rate? uint32
Figure 6
The L2SM model is structured in a way that allows the provider to list multiple circuits of various service types for the same subscriber.
The "customer-info" container contains essential information to identify the subscriber.
"customer-account-number" is an internal alphanumerical number assigned by the service provider to identify the subscriber. It MUST be unique within the service provider's OSS/BSS system. The actual format depends on the system tool the provider uses. "customer-name" is in a more readable form.
The subscriber operation center and main contact number are also listed here for reference purpose.
A vpn-service list item contains generic informations about the VPN service. The vpn-id of the vpn-service refers to an internal reference for this VPN service. This identifier is purely internal to the organization responsible for the VPN service.
A vpn-service is composed of some characteristics:
The "svc-type" supports two service types: one for EVC (Ethernet Virtual Connection) and the other for OVC (Operator Virtual Connection). These two parameters are not mutually exclusive. Depending on the service-type, a Layer 2 VPN service may be identified by EVCtype, OVCtype, or both. E-Line and E-LAN providers shall have an EVC-ID assigned to the UNI-to-UNI circuit. If the service has remote UNIs in an off-net partner's network, there will be one OVC-ID for the on-net segment between the local UNI and the E-NNI interconnect, and one OVC-ID for each off-net segment from E-NNI to the remote UNI.
E-Access, on the other hand, is an OVC-based service. The E-Access service provider will assign an OVC-ID for the circuit between UNI and E-NNI.
New service types could be added by augmentation.
The "evc" case contains an "evc-id" leaf and "uni-list" container. And the "vpn-id" will be associated with the "evc-id". Only one "evc-id" is allowed for each "vpn-id". The "evc-id" leaf will be specified for E-Line and E-LAN service types. "uni-list" will specify the UNI list associated with the same EVC service.
The EVC-ID is intended to be a structured string. Each service provider can decide the nomenclature in its network. In addition, "number of PEs" and "number of sites" can be specified under the "evc" container.
The "ovc" case contains "ovc-list". For each "ovc-list" entry, there are two boolean subcases ("on-net" and "off-net") and one "ovc-id" leaf is specified.
For E-Access or services with off-net UNIs, the "on-net" leaf MUST be marked TRUE, and the "ovc-id" will be specified.
In case of E-Access, the "vpn-id" will be associated with the on-net "ovc-id". Only one on-net "ovc-id" is allowed for each "vpn-id".
If the service is E-Line or E-LAN with remote UNIs, there will be one, and only one, on-net "ovc-id" and a list of off-net "ovc-id" objects for the remote UNIs. However, the "vpn-id" is still associated with the "evc-id". Only one "evc-id" is allowed for each "vpn-id".
The "ethernet-svc-type" group contains all supported Ethernet connection service types. One, and only one, "ethernet-svc-type" is selected for each "vpn-id".
The currently supported Ethernet Connection service types are listed in Section 3.2. New Ethernet Connection service types can be added in the future.
The type of VPN service topology can be used for configuration if needed. The module currently supports: any-to-any, hub and spoke (where hubs can exchange traffic), and hub and spoke disjoint (where hubs cannot exchange traffic). New topologies could be added by augmentation. By default, the any-to-any VPN service topology is used.
This model provides cloud access configuration through the cloud-access container. The usage of cloud-access is targeted for public cloud and Internet Access. The cloud-access container provides parameters for authorization rules.
Private cloud access may be addressed through the site contianer as described in Section 5.1.3 with the use consistent with sites of type E-NNI.
A cloud identifier is used to reference the target service. This identifier is local to each administration.
Some service providers may divide their networks into multiple administrative domains. And a Layer 2 VPN service may span across more than one metro network belonging to the same service provider. The optional "metro-network-id" container is intended be used by these multi-domain providers to differentiate intra-market versus inter-market services.
When the "inter-mkt-service" leaf is marked TRUE, multiple associated "metro-mkt-id"s will be listed. Otherwise, the service is intra-domain and only one "metro-mkt-id" is allowed.
As the subscribers start to deploy more 10G or 100G Ethernet equipment in their network, the demand for high bandwidth Ethernet connectivity services increases. Along with the great revenue opportunities, these high bandwidth service requests also pose challenges on capacity planning and service delivery in the provider's network, especially when the contractual bandwidth is at, or close to, the speed of physical links of the service provider's core network. Because of the encapsulation overhead, the provider cannot deliver the throughput in the service level agreement over a single link. Although there may be bundled Nx10G or Nx100G aggregation links between core network elements, or Equal Cost Multiple Paths (ECMP) in the network, an Ethernet-over-MPLS (EoMPLS) PWE or VxLAN circuit is considered a single flow to a router or switch which uses the normal IP five-tuples in the hashing algorithm.
Without burdening the core routers with additional processing of deep inspection into the payload, the service provider now has the option of inserting a flow or entropy label into the EoMPLS frames, or using different source UDP ports in case of VxLAN/EVPN, at ingress PE to facility load-balancing on the subsequent nodes along the path. The ingress PE is in a unique position to see the actual unencapsulated service frames and identify data flows based on the original Ethernet and IP header.
On the other hand, not all Layer 2 Ethernet VPNs are suited for load-balancing across diverse ECMP paths. For example, a Layer 2 Ethernet service transported over a single RSVP signaled Label Switched Path will not take multiple ECMP routes. Or if the subscriber is concerned about latency/jitter, then diverse path load-balancing can be undesirable.
The optional "load-balance-option" container is used to capture the load-balancing agreement between the subscriber and the provider. If the "load-balance" Boolean leaf is marked TRUE, then one of the following load-balance methods can be selected: "fat-pw", "entropy-label", or "vxlan-source-udp-port".
Service providers have the option of inserting an outer VLAN tag (the S-tag) into the service frames from the subscriber to improve service scalability and customer VLAN transparency.
Ideally, all external interfaces (UNI and E-NNI) associated with a given service will have the same S-tag assigned. However, this may not always be the case. Traffic with all attachments using different S-tags will need to be "normalized" to a single service S-tag. (One example of this is a multipoint service that involves multiple off-net OVCs terminating on the same E-NNI. Each of these off-net OVCs will have a distinct S-tag which can be different from the S-tag used in the on-net part of the service.)
The purpose of the optional "svlan-id-ethernet-tag" leaf is to identify the service-wide "normalized S-tag".
When more than one service is multiplexed onto the same interface, ingress service frames are conditionally transmitted through one of the EVC/OVCs based upon pre-arranged customer VLAN to EVC mapping. Multiple customer VLANs can be bundled across the same EVC.
"cvlan-id-to-evc-map", when applicable, contains the list of customer vlans to the service mapping in a free-form format. In most cases, this will be the VLAN access-list for the inner 802.1q tag (the C-tag).
When multiple services are provided on the same network element, the MAC address table (and the Routing Information Base space for MAC-routes in the case of EVPN) is a shared common resource. Service providers may impose a maximum number of MAC addresses learned from the subscriber for a single service instance, and may specify the action when the upper limit is exceeded: drop the packet, flood the packet, or simply send a warning log message.
For point-to-point services, if MAC learning is disabled then the MAC address limit is not necessary.
The optional "service-level-mac-limit" container contains the subscriber MAC address limit and information to describe the action when the limit is exceeded.
Sometimes the subscriber may desire end-to-end protection at the service level for applications with high availability requirements. There are two protection schemes to offer redundant services:
The optional "service-protection" container is used to capture the desired service protection agreement between subscriber and provider.
An "peer-evc-id" should be specified when the "protection-model" has been set.
The "site" container is used for the provider to store information of detailed implementation arrangements made with either the subscriber or peer operators at each inter-connect location.
We are restricting the L2SM to exterior interfaces only, so all internal interfaces and the underlying topology are outside the scope of L2SM.
There are two possible types of external facing connections associated with an Ethernet VPN service. These give rise to two different types of site at which the connection is made:
Most of the attributes of a site are common to the two typs of site and so are presented just once. Divergences (that is, attributes that are specific to the type of site) are captured in type-dependent containers. In the text that follows, the phrase "between the subscriber and the provider" is used to follow the more common case of a UNI site, but should also be taken to apply to "between two providers" in the E-NNI case.
For each site, there are sub-containers to maintain physical link attributes, service frame and Layer 2 control protocol frame disposition, Ethernet service OAM attributes, and agreements for service bandwidth profiles and priority levels.
Typically, the following characteristics of a site interface handoff need to be documented as part of the service design:
The "site-id" leaf contains an arbitrary string to uniquely identify the site within the overall network infrastructure. The format of the site-id is determined by the local administration of the VPN service.
The "management" sub-container is intended for site management options, depending on the device ownership and security access control. The followings are three common management models:
The selected management mode is specified under the "type" leaf. The "address" leaf stores CE device management IP information. And the "management-transport" leaf is used to identify the transport protocol for management traffic: IPv4 or IPv6. Additional security options may be derived based on the particular management model selected.
The information in the "location" sub-container under a "site" allows easy retrieval of data about which are the nearest available facilities and can be used for access topology planning. It may also be used by other network orchestration component to choose the targeted upstream PE. Location is expressed in terms of postal information.
Some subscribers may request upstream PE diversity between two or more sites. These sites will share the same diversity group ID under the optional "site-diversity" sub-container.
This sub-container presents parameters for ingress service stream admission control and encryption profile information. It is also a placeholder for further site-security options that may be added by augmentation.
The "signaling-option" container captures service-wide attributes of the L2VPN instance.
Although topology discovery or network device configuration is purposely out of scope for the L2SM model, certain VPN parameters are listed here. The information can then be passed to other elements in the whole automation eco-system (such as the configuration engine) which will handle the actual service provisioning function.
The "signaling-option" list uses the combination of "name" and "type" as the key. The "name" leaf is a free-form string of the VPN instance name. The "type" leaf is for the signaling protocol: BGP-L2VPN, BGP-EVPN, or T-LDP.
[RFC4761] and [RFC6624] describe the mechanism to auto-discover L2VPN VPLS/VPWS end points (CE-ID or VE-ID) and signal the label base and offset at the same time to allow remote PE to derive the VPN label to be used when sending packets to the advertising router.
Due to the way auto-discovery operates, PEs that have at least one attachment circuit associated with a particular VPN service do not need to be specified explicitly.
In the L2SM model, only the target community (or communities) are listed at the service level.
The "type" leaf under "mp-bgp-l2vpn" is an identityref to specify "vpws" or "vpls" sub-types.
Defined in [RFC7432], EVPN is an L2VPN technology based upon BGP MAC routing. It provides similar functionality to BGP VPWS/VPLS with improvement around redundancy, multicast optimization, provisioning, and simplicity.
Due to the way auto-discovery operates, PEs that have at least one attachment circuit associated with a particular VPN service do not need to be specified explicitly.
In the L2SM model, only the target community (or communities) are listed at the service level.
The "type" leaf under "mp-bgp-evpn" is an identityref to specify "vpws" or "vpls" sub-types.
[RFC4762] specifies the method of using targeted LDP sessions between PEs to exchange VC label information. This requires a configured full mesh of targeted LDP sessions between all PEs.
As multiple attachment circuits may terminate on a single PE, this PE-to-PE mesh is not a per-site attribute. All PEs related to the L2VPN service will be listed in the "t-ldp-pwe" with associated "vc-id".
Based on [RFC4448], there are two types of Ethernet services: "Port-to-Port Ethernet PW emulation" and "Vlan-to-Vlan Ethernet PW emulation", commonly referred to as Type 5 and Type 4 respectively. This concept applies to both BGP L2VPN VPWS/VPLS and T-LDP signaled PWE implementations.
The "pwe-encapsulation-type" container contains two Boolean type leaves: "ethernet" and "ethernet-vlan". If "signaling-option" is "mp-bgp-l2vpn" or "t-ldp-pwe", then exactly one of "ethernet" and "ethernet-vlan" MUST be marked TRUE .
During the signaling process of a BGP-L2VPN or T-LDP pseudowire, the pwe-mtu value is exchanged and must match at both ends. By default, the pwe-mtu is derived from physical interface MTU of the attachment circuit minus the EoMPLS transport header. In some cases, however, the physical interface on both ends of the circuit might not have identical MTU settings. For example, due to 802.1ad q-in-q operation, an I-NNI will need an extra four bytes to accommodate the S-tag. The inter-carrier E-NNI link may also have a different MTU size than the internal network interfaces.
[RFC4448] requires the same MTU size on physical interfaces at both ends of the pseudowire. In actual implementations, many router vendors have provided a knob to explicitly specify the pwe-mtu, which can then be decoupled from the physical interface MTU.
When there is a mismatch between the physical interface MTU and configured pwe-mtu, the "allow-mtu-mismatch" leaf in the "pwe-mtu" contained enables definition of the required behavior.
A control word is an optional 4-byte field located between the MPLS label stack and the Layer 2 payload in the pseudowire packet. It plays a crucial role in Any Transport over MPLS (AToM). The 32-bit field carries generic and Layer 2 payload-specific information, including a C-bit which indicates whether the control word will present in the Ethernet over MPLS (EoMPLS) packets. If the C-bit is set to 1, the advertising PE expects the control word to be present in every pseudowire packet on the pseudowire that is being signaled. If the C-bit is set to 0, no control word is expected to be present.
Whether to include control word in the pseudowire packets MUST match on PEs at both ends of the pseudowire and it is non-negotiable during the signaling process.
The use of a control-word applies to pseduowires signaled using either BGP L2VPN VPWS/VPLS or T-LDP. It is a routing-instance level configuration parameter in many cases.
The optional "control-word" leaf is a Boolean field in the L2SM model for the provider to explicitly specify whether the control-word will be signaled for the service instance.
See Section 5.1.2.6.
The L2SM includes a set of essential physical interface properties and Ethernet layer characteristics in the "port" sub-container. Some of these are critical implementation arrangements that require consent from both subscriber and provider.
"id" is a free-form string to identify a given interface. The service provider can decide on the actual nomenclature used in the management systems.
Remote Carrier Name is the Name of Remote Carrier associated with the remote end of an E-NNI and so only applies for that type of VPN connectivity.
In order to help the different placement scenarios, a site-network-access (i.e., port defined in Section 5.1.3.1.8) may be tagged using one or more fate sharing group identifiers. The fate sharing group identifier is a string so it can accommodate both explicit naming of a group of sites (e.g. "multihomed-set1") or a numbered identifier (e.g. 12345678). The meaning of each group-id is local to each customer administrator.
The "bearer" container defines the requirements for the site attachment to the provider network that are below Layer 3.
The bearer parameters will help to determine the access media to be used.
The ethernet-connection container presents two sets of link attributes: physical or optional LAG interface attributes. These parameters are essential for the connection between subscriber and provider edge devices to establish properly.
For each physical interface (phy-interface), there are basic configuration parameters like port number and speed, interface MTU, auto-negotiation and flow-control settings, etc. "encapsulation- type" is for user to select between Ethernet encapsulation (port-based) or Ethernet VLAN encapsulation (VLAN-based). All allowed Ethertypes of ingress service frames can be listed under "ethertype". In addition, the subscriber and provider may decide to enable advanced features, such as LLDP, 802.3AH link OAM, MAC loop detection/prevention at a UNI, based on mutual agreement.
Sometimes, the subscriber may require multiple physical links bundled together to form a single, logical, point-to-point LAG connection to the service provider. Typically, LACP (Link Aggregation Control Protocol) is used to dynamically manage adding or deleting member links of the aggregate group. In general, LAG allows for increased service bandwidth beyond the speed of a single physical link while providing graceful degradation as failure occurs, thus increased availability.
In the L2SM, there is a set of attributes under "LAG-interface" related to link aggregation functionality. The subscriber and provider first need to decide on whether LACP PDU will be exchanged between the edge device by specifying the "LACP-state" to "On" or "Off". If LACP is to be enabled, then both parties need to further specify whether it will be running in active versus passive mode, plus the time interval and priority level of the LACP PDU. The subscriber and provider can also determine the minimum aggregate bandwidth for a LAG to be considered valid path by specifying the optional "mini-link" attribute. To enable fast detection of faulty links, micro-BFD runs independent UDP sessions to monitor the status of each member link. Subscriber and provider should consent to the BFD hello interval and hold time.
Each member link will be listed under the LAG interface with basic physical link properties. Certain attributes like flow-control, encapsulation type, allowed ingress Ethertype and LLDP settings are at the LAG level.
If the Ethernet service is enabled on a logical unit on the connection at the interface, the "sub-if-id" should be specified.
The "Ethernet-connection" container also presents site specific (S-tag, C-tag) management options. The overall S-tag for the Ethernet circuit and C-tag to EVC mapping, if applicable, has been placed in the service container. The S-tag under "port" should match the S-tag in the service container in most cases, however, vlan translation is required for the S-tag in certain deployment at the external facing interface or upstream PEs to "normalize" the outer VLAN tag to the service S-tag into the network and translate back to the site's S-tag in the opposite direction. One example of this is with a Layer 2 aggregation switch along the path: the S-tag for the EVC has been previously assigned to another service thus can not be used by this attachment circuit. Another use case is when multiple E-access OVCs from the same E-NNIs are attached to the same E-LAN service.
The "svlan-id-ethernet-tag" in the "Ethernet-connection" container is either the S-tag inserted at a UNI or the outer tag of ingress packets at an E-NNI. These parameters are included in the L2SM to facilitate other management system to generate proper configuration for the network elements.
The "ethernet-connection" container also contains an optional site-specific C-tag to EVC mapping.
The maximum MTU of subscriber service frames can be derived from the physical interface MTU by default, or specified under the "evc-mtu" leaf if it is different than the default number.
The service provider may choose to impose a per-attachment circuit "mac-addr-limit" in addition to the service-level MAC limit, and specify the behavior when the limit is exceeded accordingly.
EVPN supports PE geo-redundancy in the access domain. The connection between a multi-homed CE to PE is identified with a uniquely assigned ID referred as an Ethernet Segment Identifier (ESI). Because a learned MAC address is propagated via BGP, it allows for multiple active paths in forwarding state and for load-balancing options.
The "availability" container contains ESI and redundancy mode attributes for an EVPN multi-homing site.
To facilitate interoperability between different Multiple System Operators (MSOs), the MEF has provided normative guidance on Layer 2 Control Protocol (L2CP) processing requirements for each service type. Subscriber and provider should make pre- arrangement on whether to allow interaction between the edge device or keep each other's control plane separate on a per-protocol basis.
The destination MAC addresses of these L2CP PDUs fall within two reserved blocks specified by the IEEE 802.1 Working Group. Packet with destination MAC in these multicast ranges have special forwarding rules.
Layer 2 protocol tunneling allows service providers to pass subscriber Layer 2 control PDUs across the network without being interpreted and processed by intermediate network devices. These L2CP PDUs are transparently encapsulated across the MPLS-enabled core network in Q-in-Q fashion.
The "L2CP-control" container contains the list of commonly used L2CP protocols and parameters. The service provider can specify DISCARD, PEER, or TUNNEL mode actions for each individual protocol.
In addition, "provider-bridge-group" and "provider-bridge-mvrp" addresses are also listed in the L2CP container.
The "service" container defines service parameters associated with the site.
The service bandwidth refers to the bandwidth requirement between PE and CE. The requested bandwidth is expressed as svc-input-bandwidth and svc-output-bandwidth. Input/output direction is using customer site as reference: input bandwidth means download bandwidth for the site, and output bandwidth means upload bandwidth for the site.
The service bandwidth is only configurable at the site-network-access level (i.e., for the port associated with the site).
Using a different input and output bandwidth will allow service provider to know if a customer allows for asymmetric bandwidth access like ADSL. It can also be used to set a rate-limit in a different way for upload and download on symmetric bandwidth access.
The bandwidth container may also include a "cos-id" parameter. If the "cos-id" is not present within the bandwidth container, the bandwidth is per evc, which provides rate enforcement for all ingress service frames at the interface that are associated with a particular EVC.
If the "cos-id" is present, the bandwidth is per CoS, which provides rate enforcement for all service frames for a given class of service. The class of service is identified via a CoS identifier. So this bandwidth profile applies to service frames over an EVC with a particular CoS value. Multiple input/output-bandwidthper-cos-id can be associated with the same EVC.
The model defines QoS parameters as an abstraction:
In MEF 23.2 ([MEF-23-2]) three types of model are defined as the following:
Similarly, the cos-color-id can be assigned based on EVC or OVC EP, dot1p value in C-tag, or DSCP in IP header. Ingress service frames are metered against the bandwidth profile based on the cos-identifier. A "color" will be assigned to a service frame to identify its bandwidth profile conformance. A service frame is "green" if it is conformant with "committed" rate of the bandwidth profile. A Service Frame is "yellow" if it is exceeding the "committed" rate but conformant with the "excess" rate of the bandwidth profile. Finally, a service frame is "red" if it is conformant with neither the "committed" nor "excess" rates of the bandwidth profile.
Ingress/egress-bandwidth-profile-per-evc presents the ingress/egress bandwidth profile per EVC, providing rate enforcement for all ingress service frames at the interface that are associated with a particular EVC.
Alternately, ingress/egress-bandwidth-profile-per-cos-id presents the ingress/egress bandwidth profile per CoS, providing rate enforcement for all service frames for a given class of service. The class of service is identified via a CoS identifier. So this bandwidth profile applies to service frames over an EVC with a particular CoS value. Multiple ingress/egress-bandwidth-profile-per-cos-id can be associated with the same EVC.
QoS classification rules are handled by qos-classification-policy. The qos-classification-policy is an ordered list of rules that match a flow or application and set the appropriate target class of service (target-class-id). The user can define the match using physical port reference or a more specific flow definition (based layer 2 source and destination MAC address, cos,dscp,cos-id, color-id etc.). When a flow definition is used, the user can use a target-sites leaf- list to identify the destination of a flow rather than using destination addresses. A rule that does not have a match statement is considered as a match-all rule. A service provider may implement a default terminal classification rule if the customer does not provide it. It will be up to the service provider to determine its default target class.
User can choose between standard profile provided by the operator or a custom profile. The qos-profile defines the traffic scheduling policy to be used by the service provider.
A custom qos-profile is defined as a list of class of services and associated properties. The properties are:
For point-to-point E-LINE services, the provider only needs to deliver a single copy of each service frame to the remote PE, regardless whether the destination MAC address of the incoming frame is unicast, multicast or broadcast. Therefore, all in-profile service frames should be delivered unconditionally.
B-U-M (Broadcast-UnknownUnicast-Multicast) frame forwarding in multipoint-to-multipoint services, on the other hand, involves both local flooding to other attachment circuits on the same PE and remote replication to all other PEs, thus consumes additional resources and core bandwidth. Special B-U-M frame disposition rules can be implemented at external facing interfaces (UNI or E-NNI) to rate-limit the B-U-M frames, in term of number of packets per second or bits per second.
The threshold can apply to all B-U-M traffic, or one for each category.
MAC address flapping between different physical ports typically indicates a bridge loop condition in the subscriber network. Misleading entries in the MAC cache table can cause service frames to circulate around the network indefinitely and saturate the links throughout the provider's network, affecting other services in the same network. In case of EVPN, it also introduces massive BGP updates and control plane instability.
The service provider may opt to implement a switching loop prevention mechanism at the external facing interfaces for multipoint-to-multipoint services by imposing a MAC address move threshold.
The MAC move rate and prevention-type options are listed in the "mac-loop-prevention" container.
See Section 5.1.2.10.
The advent of Ethernet as a wide-area network technology brings additional requirements of end-to-end service monitoring and fault management in the carrier network, particularly in the area of service availability and Mean Time To Repair (MTTR). Ethernet Service OAM in the L2SM refers to the combined protocol suites of IEEE 802.1ag ([IEEE-802-1ag]) and ITU-T Y.1731 ([ITU-T-Y-1731]).
Generally speaking, Ethernet Service OAM enables service providers to perform service continuity check, fault-isolation, and packet delay/jitter measurement at per customer per EVC granularity. The information collected from Ethernet Service OAM data sets is complementary to other higher layer IP/MPLS OSS tools to ensure the required service level agreements (SLAs) can be meet.
The 802.1ag Connectivity Fault Management (CFM) functional model is structured with hierarchical maintenance domains (MDs), each assigned a unique maintenance level. Higher level MDs can be nested over lower level MDs. However, the MDs cannot intersect. The scope of each MD can be solely within a subscriber's network, solely within the provider's network, interact between the subscriber-to-provider or provider-to-provider edge equipment, or tunnel over another provider's network.
Depending on the use case scenario, one or more maintenance end points (MEPs) can be placed on the external facing interface, sending CFM PDUs towards the core network (UP MEP) or downstream link (DOWN MEP).
The "cfm-802.1-ag" sub-container under "port" currently presents two types of CFM maintenance association (MA): UP MEP for UNI-N to UNI-N Maintenance Association (MA) and DOWN MEP for UNI-N to UNI-C MA. For each MA, the user can define the maintenance domain ID (MAID), MEP level, MEP direction, remote MEP ID, CoS level of the CFM PDUs, Continuity Check Message (CCM) interval and hold time, alarm priority defect, CCM priority-type, etc.
ITU-T Y.1731 Performance Monitoring (PM) provides essential network telemetry information that includes the measurement of Ethernet service frame delay, frame delay variation, frame loss, and frame throughput. The delay/jitter measurement can be either one-way or two-way. Typically, a Y.1731 PM probe sends a small amount of synthetic frames along with service frames to measure the SLA parameters.
The "y-1731" sub-container under "port" contains a set of parameters for use to define the PM probe information, including MAID, local and remote MEP-ID, PM PDU type, message period and measurement interval, CoS level of the PM PDUs, loss measurement by synthetic or service frame options, one-way or two-way delay measurement, PM frame size, and session type.
As expressed in Section 4, this service module is not intended to configure the network element, but is instantiated in a management system.
The management system might follow modular design and comprise at least two different components:
In some cases, when a split is needed between the behavior and functions that a customer requests and the technology that the network operator has available to deliver the service [I-D.wu-opsawg-service-model-explained], a new component can be separated out of the service component (let's call it the control component). This component is responsible for network-centric operation and is aware of many features such as topology, technology, and operator policy. As an optional component, it can use the service model as input and is not required at all if the control component delegates its control operations to the configuration component.
In Section 7 we provide some example of translation of service provisioning requests to router configuration lines as an illustration. In the NETCONF/YANG ecosystem, it is expected that NETCONF and YANG will be used between the configuration component and network elements to configure the requested service on those elements.
In this framework, it is expected that YANG models will be used for configuring service components on network elements. There will be a strong relationship between the abstracted view provided by this service model and the detailed configuration view that will be provided by specific configuration models for network elements such as those defined in [I-D.ietf-bess-l2vpn-yang] and [I-D.ietf-bess-evpn-yang]. Service components needing configuration on network elements in support of the service model defined in this document include:
As explained in Section 4, this service model is intended to be instantiated at a management layer and is not intended to be used directly on network elements. The management system serves as a central point of configuration of the overall service.
This section provides an example on how a management system can use this model to configure an L2VPN service on network elements.
The example is for of a VPN service for 3 sites using point-to-point EVC and a Hub and Spoke VPN service topology as shown in Figure 7. Loadbalancing is not considered in this case.
UNI Site1
............
: : E-Line using P2P EVC
:Spoke Site:-----PE1--------------------------+
: : | UNI Site3
:..........: | ............
| : :
PE3-----: Hub Site :
UNI Site2 | : :
............ | :..........:
: : E-Line using P2P EVC |
:Spoke Site:-----PE2--------------------------+
: :
:..........:
Figure 7: Reference Network for Simple Example
<vpn-service>
<vpn-id>12456487</vpn-id>
<svc-id-type>EVC</svc-id-type>
<evc>
<uni-list>
<uni>UNI1</uni>
<uni>UNI3</uni>
</uni-list>
</evc>
<eth-svc-type>eline</eth-svc-type>
<svc-topo>hub-spoke</svc-topo>
</vpn-service>
<vpn-service>
<vpn-id>12456488</vpn-id>
<svc-id-type>EVC</svc-id-type >
<evc>
<uni-list>
<uni>UNI2</uni>
<uni>UNI3</uni>
</uni-list>
</evc>
<eth-svc-type>eline</eth-svc-type>
<svc-topo>hub-spoke</svc-topo>
</vpn-service>
The following XML describes the overall simplified service configuration of this VPN.
When receiving the request for provisioning the VPN service, the management system will internally (or through communication with another OSS component) allocates VPN route-targets. In this specific case two Route Taregts (RTs) will be allocated (100:1 for Hubs and 100:2 for Spokes). The output below describes the configuration of Spoke UNI Site1.
<site>
<site-id>Spoke_Site1</site-id>
<location>
<city>NY</city>
<country-code>US</country-code>
</location>
<signaling-options>
<signaling-option>
<type>VRF</type>
<mp-bgp-l2vpn>
<svc-id>12456487</svc-id>
<type>VPWS</type>
</mp-bgp-l2vpn>
</signaling-option>
</signaling-options>
<site-ports>
<site-port>
<site-port-id>Spoke_UNI-Site1</site-port-id>
<access-diversity>
<groups>
<group>
<group-id>20</group-id>
</group>
</groups>
<access-diversity>
<ethernet-connection>
<vlan>
<vlan-id>17</vlan-id>
</vlan>
<physical-interface>
<encapsulation-type>ETH</encapsulation-type>
</physical-interface>
</ethernet-connection>
<service>
<svc-ingress-bandwidth>
<cir>450000000</cir>
<cbs>20000000</cbs>
<eir>1000000000</eir>
<ebs>200000000</ebs>
</svc-ingress-bandwidth>
<svc-egress-bandwidth>
<cir>350000000</cir>
<cbs>10000000</cbs>
<eir>800000000</eir>
<ebs>200000000</ebs>
</svc-egress-bandwidth>
</service>
<l2cp-protocol>
<stp-rstp-mstp>TUNNEL</stp-rstp-mstp>
<lldp>TRUE</lldp>
</l2cp-protocol>
<vpn-attachment>
<vpn-id>12456487</vpn-id>
<site-role>spoke-role</site-role>
</vpn-attachment>
</site-port>
</site-ports>
<management>
<type>provider-managed</type>
</management>
</site>
When receiving the request for provisioning Spoke1 site, the management system MUST allocate network resources for this site. It MUST first determine the target network elements to provision the access, and especially the PE router (and may be an aggregation switch). As described in Section 5.1.3.1.3, the management system SHOULD use the location information and SHOULD use the access-diversity constraint to find the appropriate PE. In this case, we consider Spoke1 requires PE diversity with Hub and that management system allocate PEs based on lowest distance. Based on the location information, the management system finds the available PEs in the nearest area of the customer and picks one that fits the access- diversity constraint.
When the PE is chosen, the management system needs to allocate interface resources on the node. One interface is selected from the PE available pool. The management system can start provisioning the PE node by using any mean (Netconf, CLI, ...). The management system will check if a VRF is already present that fits the needs. If not, it will provision the VRF: Route Distinguisher will come from internal allocation policy model, route-targets are coming from the vpn-policy configuration of the site (management system allocated some RTs for the VPN). As the site is a Spoke site (site-role), the management system knows which RT must be imported and exported. As the site is provider managed, some management route-targets may also be added (100:5000). Standard provider VPN policies MAY also be added in the configuration.
ip vrf Customer1
export-map STD-CUSTOMER-EXPORT <---- Standard SP configuration
route-distinguisher 100:3123234324
route-target import 100:1
route-target import 100:5000 <---- Standard SP configuration
route-target export 100:2 for provider managed
!
Example of generated PE configuration:
When the VRF has been provisioned, the management system can start configuring the access on the PE using the allocated interface information. The VLAN tag is chosen by the management system. One VLAN tag will be picked from an allocated subnet for the PE, another will be used for the CE configuration. LACP protocols will also be configured between PE and CE and due to provider managed model, the choice is up to service provider. This choice is independent of the LACP protocol chosen by customer.
interface GigabitEthernet0/0/0/3.100 l2transport
encapsulation dot1ad 100
rewrite ingress tag pop 1 symmetric
l2vpn
xconnect group EPL
p2p EPL
interface GigabitEthernet0/0/0/3.100
neighbor 100.100.100.1 pw-id 100
!
interface GigabitEthernet4/8
no ip address
speed nonegotiate
no keepalive
ethernet dot1ad nni
service instance 100 ethernet
encapsulation dot1q 100
rewrite ingress tag pop 1 symmetric
xconnect 100.100.100.2 100 encapsulation mpls
Example of generated PE configuration:
As the CE router is not reachable at this stage, the management system can produce a complete CE configuration that can be uploaded to the node by manual operation before sending the CE to customer premise. The CE configuration will be built as for the PE. Based on the CE type (vendor/model) allocated to the customer and bearer information, the management system knows which interface must be configured on the CE. PE-CE link configuration is expected to be handled automatically using the service provider OSS as both resources are managed internally. CE to LAN interface parameters like dot1Q tag are derived from the ethernet-connection taking into account how management system distributes dot1Q tag between PE and CE within subnet. This will allow to produce a plug'n'play configuration for the CE.
interface GigabitEthernet0/9
switchport trunk allowed vlan none
switchport mode trunk
service instance 100 ethernet
encapsulation default
l2protocol forward cdp
xconnect 1.1.1.1 100 encapsulation mpls
!
Example of generated CE configuration:
<CODE BEGINS>
file "ietf-l2vpn-svc@2017-02-10.yang"
module ietf-l2vpn-svc {
namespace "urn:ietf:params:xml:ns:yang:ietf-l2vpn-svc";
prefix "l2svc";
import ietf-inet-types {
prefix inet;
}
import ietf-yang-types {
prefix yang;
}
import iana-if-type {
prefix ianaift;
}
organization
"IETF L2SM Working Group.";
contact
"WG List: l2sm@ietf.org
Editor: Bin_Wen@comcast.com";
description
"The YANG module defines a generic service configuration
model for Layer 2 VPN services common across all of the
vendor implementations.";
revision 2017-02-13{
description
"Initial revision -04 version";
reference
"draft-wen-l2sm-l2vpn-service-model-04.txt
A YANG Data Model for L2VPN Service Delivery.";
}
/* Features */
feature input-bw {
description
"Input Bandwidth";
}
feature output-bw {
description
"Output Bandwidth";
}
feature uni-list {
description
"Enable support UNI list";
}
feature ovc-type {
description
"Enable support OVC type";
}
feature cloud-access {
description
"Allow VPN to connect to a Cloud Service
provider.";
}
feature oam-3ah {
description
"Enables support of OAM 802.3ah";
}
feature Micro-BFD {
description
"Enables support of Micro-BFD";
}
feature bfd {
description
"Enables support of BFD";
}
feature signaling-option {
description
"Enable support of signaling option";
}
feature site-diversity {
description
"Enables support of site diversity constraints";
}
feature encryption {
description
"Enables support of encryption";
}
feature always-on {
description
"Enables support for always-on access
constraint.";
}
feature requested-type {
description
"Enables support for requested-type access
constraint.";
}
feature bearer-reference {
description
"Enables support for bearer-reference access
constraint.";
}
feature qos {
description
"Enables support of Class of Services";
}
feature qos-custom {
description
"Enables support of custom qos profile";
}
/* Typedefs */
typedef svc-id {
type string;
description
"Service ID";
}
typedef direction-type {
type string;
description
"Direction";
}
typedef evc-id-type {
type string;
description
"EVC ID type";
}
typedef ovc-id-type {
type string;
description
"OVC ID type";
}
typedef ccm-priority-type {
type uint8 {
range "0..7";
}
description
"A 3 bit priority value to be used in the VLAN tag, if present
in the transmitted frame.";
}
typedef control-mode {
type enumeration {
enum peer {
description
"Peer mode";
}
enum tunnel {
description
"Tunnel mode";
}
enum discard {
description
"Discard mode";
}
}
description
"Defining a type of the control mode";
}
typedef neg-mode {
type enumeration {
enum full-duplex {
description
"Full duplex mode";
}
enum auto-neg {
description
"Auto negotiation mode";
}
}
description
"Defining a type of the negotiation mode";
}
/* Identities */
identity bw-type {
description
"Identity of bandwidth";
}
identity bw-per-cos {
base bw-type;
description
"Bandwidth is per cos";
}
identity opaque {
base bw-type;
description
"Opaque";
}
identity site-type {
description
"Identity of site type.";
}
identity uni {
base site-type;
description
"Identity of User Network Interface ";
}
identity enni {
base site-type;
description
"Identity of External Network to Network Interface";
}
identity service-type {
description
"Identity of service type.";
}
identity evc {
base service-type;
description
"EVC type.";
}
identity ovc {
base service-type;
description
"OVC type.";
}
identity bundling-type {
description
"Bundling type.";
}
identity bundling {
base bundling-type;
description
"Identity for bundling";
}
identity all2one-Bundling {
base bundling-type;
description
"Identity for all to one bundling";
}
identity color-id {
description
"Identity of color id";
}
identity color-id-evc {
base color-id;
description
"Identity of color id base on EVC";
}
identity color-id-evc-cvlan {
base color-id;
description
"Identity of color id base on EVC and CVLAN ";
}
identity cos-id {
description
"Identity of class of service id";
}
identity cos-id-evc {
base cos-id;
description
"Identity of cos id based on EVC";
}
identity cos-id-evc-pcp {
base cos-id;
description
"Identity of cos id based on EVC and PCP";
}
identity cos-id-evc-dscp {
base cos-id;
description
"Identity of cos id based on EVC and DSCP";
}
identity cos-id-ovc-ep {
base cos-id;
description
"Identity of cos id based on OVC EP";
}
identity color-type {
description
"Identity of color types";
}
identity green {
base color-type;
description
"Identity of green type";
}
identity yellow {
base color-type;
description
"Identity of yellow type";
}
identity red {
base color-type;
description
"Identity of red type";
}
identity perf-tier-opt {
description
"Identity of performance tier option.";
}
identity metro {
base perf-tier-opt;
description
"Identity of metro";
}
identity regional {
base perf-tier-opt;
description
"Identity of regional";
}
identity continental {
base perf-tier-opt;
description
"Identity of continental";
}
identity global {
base perf-tier-opt;
description
"Identity of global";
}
identity policing {
description
"Identity of policing type";
}
identity one-rate-two-color {
base policing;
description
"Identity of one-rate, two-color (1R2C)";
}
identity two-rate-three-color {
base policing;
description
"Identity of two-rate, three-color (2R3C)";
}
identity BUM-type {
description
"Identity of BUM type";
}
identity broadcast {
base BUM-type;
description
"Identity of broadcast";
}
identity unicast {
base BUM-type;
description
"Identity of unicast";
}
identity multicast {
base BUM-type;
description
"Identity of multicast";
}
identity loop-prevention-type{
description
"Identity of loop prevention";
}
identity shut {
base loop-prevention-type;
description
"Identity of shut protection";
}
identity trap {
base loop-prevention-type;
description
"Identity of trap protection";
}
identity lacp-state {
description
"Identity of LACP state";
}
identity lacp-on {
base lacp-state;
description
"Identity of LCAP on";
}
identity lacp-off {
base lacp-state;
description
"Identity of LACP off";
}
identity lacp-mode {
description
"Identity of LACP mode";
}
identity lacp-passive {
base lacp-mode;
description
"Identity of LACP passive";
}
identity lacp-active {
base lacp-mode;
description
"Identity of LACP active";
}
identity lacp-speed {
description
"Identity of LACP speed";
}
identity lacp-fast {
base lacp-speed;
description
"Identity of LACP fast";
}
identity lacp-slow {
base lacp-speed;
description
"Identity of LACP slow";
}
identity vpn-signaling-type {
description
"Identity of VPN signaling types";
}
identity vrf {
base vpn-signaling-type;
description
"Virtual routing and forwarding (VRF).";
}
identity vfi {
base vpn-signaling-type;
description
"Virtual forwarder interface";
}
identity evi {
base vpn-signaling-type;
description
"Ethernet virtual interconnect.";
}
identity l2vpn-type {
description
"Layer 2 VPN types";
}
identity vpws {
base l2vpn-type;
description
"Virtual Private Wire Service";
}
identity vpls {
base l2vpn-type;
description
"Virtual Private LAN Service";
}
identity evpn {
base l2vpn-type;
description
"Ethernet VPN";
}
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-family {
description
"Base identity for an address family.";
}
identity ipv4 {
base address-family;
description
"Identity for IPv4 address family.";
}
identity ipv6 {
base address-family;
description
"Identity for IPv6 address family.";
}
identity vpn-topology {
description
"Base identity for VPN topology.";
}
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'n'Spoke VPN topology.";
}
identity hub-spoke-disjoint {
base vpn-topology;
description
"Identity for Hub'n'Spoke VPN topology
where Hubs cannot talk between each other.";
}
identity site-role {
description
"Base identity for site type.";
}
identity any-to-any-role {
base site-role;
description
"Site in an any to any IPVPN.";
}
identity spoke-role {
base site-role;
description
"Spoke Site in a Hub & Spoke IPVPN.";
}
identity hub-role {
base site-role;
description
"Hub Site in a Hub & Spoke IPVPN.";
}
identity pm-type {
description
"Performance monitor type";
}
identity loss {
base pm-type;
description
"Loss measurement";
}
identity delay {
base pm-type;
description
"Delay measurement";
}
identity fault-alarm-defect-type {
description
"Indicating the alarm priority defect";
}
identity remote-rdi {
base fault-alarm-defect-type;
description
"Indicates the aggregate health of the remote MEPs.";
}
identity remote-mac-error {
base fault-alarm-defect-type;
description
"Indicates that one or more of the remote MEPs is
reporting a failure in its Port Status TLV or
Interface Status TLV.";
}
identity remote-invalid-ccm {
base fault-alarm-defect-type;
description
"Indicates that at least one of the Remote MEP
state machines is not receiving valid CCMs
from its remote MEP.";
}
identity invalid-ccm {
base fault-alarm-defect-type;
description
"Indicates that one or more invalid CCMs has been
received and that 3.5 times that CCMs transmission
interval has not yet expired.";
}
identity cross-connect-ccm {
base fault-alarm-defect-type;
description
"Indicates that one or more cross connect CCMs has been
received and that 3.5 times of at least one of those
CCMs transmission interval has not yet expired.";
}
identity data-svc-frame-delivery {
description
"Delivery types";
}
identity discard {
base data-svc-frame-delivery;
description
"Service Frames are discarded.";
}
identity unconditional {
base data-svc-frame-delivery;
description
"Service Frames are unconditionally";
}
identity conditional {
base data-svc-frame-delivery;
description
"Service Frame are conditionally
delivered to the destination UNI.";
}
identity svc-topo-type {
description
"Service topology Type";
}
identity point-to-point {
base svc-topo-type;
description
"Point to Point.";
}
identity multipoint-to-multipoint {
base svc-topo-type;
description
"Multipoint to Multipoint.";
}
identity rooted-multipoint {
base svc-topo-type;
description
"Rooted Multipoint.";
}
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";
}
identity same-bearer {
base placement-diversity;
description
"Identity for having sites connected
using the same bearer";
}
identity l2-access-type {
description
"This identify the access type
of the vpn acccess interface";
}
identity untag {
base l2-access-type;
description
"Untag";
}
identity port {
base l2-access-type;
description
"Port";
}
identity dot1q {
base l2-access-type;
description
"Qot1q";
}
identity qinq {
base l2-access-type;
description
"QinQ";
}
identity sub-interface {
base l2-access-type;
description
"Create a default sub-interface and keep vlan";
}
identity vxlan {
base l2-access-type;
description
"Vxlan access into the vpn";
}
identity mac-learning-mode {
description
"MAC learning mode";
}
identity data-plane {
base mac-learning-mode;
description
"User MAC addresses are learned through ARP broadcast.";
}
identity control-plane {
base mac-learning-mode;
description
"User MAC addresses are advertised through EVPN-BGP";
}
/* Groupings */
grouping customer-info-grouping {
list customer-info {
key "customer-account-number customer-name";
leaf customer-account-number {
type uint32;
description
"Customer account number";
}
leaf customer-name {
type string;
description
"Customer name";
}
container customer-operation-center {
leaf customer-noc-street-address {
type string;
description
"Customer NOC street Address.";
}
container customer-noc-phone-number {
leaf main-phone-num {
type uint32;
description
"Main phone number.";
}
leaf extension-options {
type uint32;
description
"Extension or options";
}
description
"Configuration of customer NOCc phone number";
}
description
"Configuration of customer operation center";
}
description
"List of customer information";
}
description
"Grouping for customer information";
}
grouping vpn-service-cloud-access {
container cloud-accesses {
if-feature cloud-access;
list cloud-access {
key cloud-identifier;
leaf cloud-identifier {
type string;
description
"Identification of cloud service. Local
admin meaning.";
}
choice list-flavor {
case permit-any {
leaf permit-any {
type empty;
description
"Allow all sites.";
}
}
case deny-any-except {
leaf-list permit-site {
type leafref {
path "/l2vpn-svc/sites/site/site-id";
}
description
"Site ID to be authorized.";
}
}
case permit-any-except {
leaf-list deny-site {
type leafref {
path "/l2vpn-svc/sites/site/site-id";
}
description
"Site ID to be denied.";
}
}
description
"Choice for cloud access policy.";
}
container authorized-sites {
list authorized-site {
key site-id;
leaf site-id {
type leafref {
path "/l2vpn-svc/sites/site/site-id";
}
description
"Site ID.";
}
description
"List of authorized sites.";
}
description
"Configuration of authorized sites";
}
container denied-sites {
list denied-site {
key site-id;
leaf site-id {
type leafref {
path "/l2vpn-svc/sites/site/site-id";
}
description
"Site ID.";
}
description
"List of denied sites.";
}
description
"Configuration of denied sites";
}
description
"Cloud access configuration.";
}
description
"Container for cloud access configurations";
}
description
"Grouping for vpn cloud definition";
}
grouping site-device {
container device {
list devices {
key "device-id";
leaf device-id {
type string;
description
"Device ID";
}
leaf site-name {
type string;
description
"Site name";
}
container management {
leaf address {
type inet:ip-address;
description
"Address";
}
leaf management-transport {
type identityref {
base address-family;
}
description
"Transport protocol used for management.";
}
description
"Container for management";
}
description
"List of devices";
}
description
"Devices configuration";
}
description
"Device parameters for the site.";
}
grouping site-management {
container managemnt {
leaf type {
type identityref {
base management;
}
description
"Management type of the connection.";
}
description
"Container for management";
}
description
"Grouping for management";
}
grouping site-vpn-policy {
container vpn-policies {
list vpn-policy {
key vpn-policy-id;
leaf vpn-policy-id {
type string;
description
"Unique identifier for the VPN policy.";
}
list entries {
key id;
leaf id {
type string;
description
"Unique identifier for the policy entry.";
}
container filter {
choice lan {
case lan-tag {
leaf-list lan-tag {
type string;
description
"List of lan-tags to be matched.";
}
}
description
"Choice for LAN matching type";
}
description
"If used, it permit to split site LANs
among multiple VPNs.
If no filter used, all the LANs will be
part of the same VPNs with the same
role.";
}
container vpn {
leaf vpn-id {
type leafref {
path "/l2vpn-svc/vpn-services/"+
"vpn-svc/vpn-id";
}
mandatory true;
description
"Reference to an IPVPN.";
}
leaf site-role {
type identityref {
base site-role;
}
default any-to-any-role;
description
"Role of the site in the IPVPN.";
}
description
"List of VPNs the LAN is associated to.";
}
description
"List of entries for export policy.";
}
description
"List of VPN policies.";
}
description
"VPN policy.";
}
description
"VPN policy parameters for the site.";
}
grouping umb-frame-delivery {
leaf unicast-frame-delivery {
type identityref {
base data-svc-frame-delivery;
}
description
"Unicast Data Service Frame Delivery Mode
(unconditional[default], conditional, or discard).";
}
leaf multicast-frame-delivery {
type identityref {
base data-svc-frame-delivery;
}
description
"Multicast Data Service Frame Delivery Mode
(unconditional[default], conditional, or discard).";
}
leaf broadcast-frame-delivery {
type identityref {
base data-svc-frame-delivery;
}
description
"Broadcast Data Service Frame Delivery Mode
(unconditional[default], conditional, or discard).";
}
description
"Grouping for unicast, mulitcast, broadcast frame delivery";
}
grouping customer-location-info {
container location {
leaf address {
type string;
description
"Address (number and street) of the site.";
}
leaf zip-code {
type string;
description
"ZIP code of the site.";
}
leaf state {
type string;
description
"State of the site. This leaf can also be used to
describe a region for country who does not have
states.";
}
leaf city {
type string;
description
"City of the site.";
}
leaf country-code {
type string;
description
"Country of the site.";
}
description
"Location of the site.";
}
description
"This grouping defines customer location parameters";
}
grouping site-diversity {
container site-diversity {
if-feature site-diversity;
container groups {
list group {
key group-id;
leaf group-id {
type string;
description
"Group-id the site is belonging to";
}
description
"List of group-id";
}
description
"Groups the site is belonging to.
All site network accesses will inherit those group
values.";
}
description
"Diversity constraint type.";
}
description
"This grouping defines site diversity parameters";
}
grouping site-service {
leaf svlan-id-ethernet-tag {
type string;
description
"SVLAN-ID/Ethernet Tag configurations";
}
list cvlan-id-to-evc-map {
key "evc-id type";
leaf evc-id {
type leafref {
path "/l2vpn-svc/vpn-services/vpn-svc/vpn-id";
}
description
"EVC ID";
}
leaf type {
type identityref {
base bundling-type;
}
description
"Bundling type";
}
list cvlan-id {
key vid;
leaf vid {
type identityref {
base ianaift:iana-interface-type;
}
description
"CVLAN ID";
}
description
"List of CVLAN-ID to EVC Map configurations";
}
description
"List for cvlan-id to evc map configurations";
}
leaf service-level-mac-limit {
type string;
description
"Service-level MAC-limit (E-LAN only)";
}
description
"This grouping defines site service parameters";
}
grouping service-protection {
container service-protection {
container protection-model {
description
"Container of protection model configurations";
}
container peer-evc-id {
description
"Container of peer EVC ID configurations";
}
description
"Container of End-to-end Service Protection
configurations";
}
description
"Grouping for service protection";
}
grouping ethernet-service-type {
choice ethernet-svc-type {
case e-line {
leaf epl {
type boolean;
description
"Ethernet private line";
}
leaf evpl {
type boolean;
description
"Ethernet virtual private line";
}
description
"Case of e-line";
}
case e-lan {
leaf ep-lan {
type boolean;
description
"Ethernet private LAN";
}
leaf evp-lan {
type boolean;
description
"Ethernet virtual private LAN";
}
description
"Case of e-lan";
}
case e-access {
leaf access-epl {
type boolean;
description
"Access Ethernet virtual private line";
}
leaf access-evpl {
type boolean;
description
"Access Ethernet virtual private line";
}
description
"Case of e-access.";
}
description
"Choice of Ethernet service type";
}
description
"Grouping for Ethernet service type.";
}
grouping signaling-option-grouping {
list signaling-option {
key "type";
leaf type {
type identityref {
base vpn-signaling-type;
}
description
"VPN signaling types";
}
container mp-bgp-l2vpn {
leaf vpn-id {
type svc-id;
description
"Identifies the target VPN";
}
leaf type {
type identityref {
base l2vpn-type;
}
description
"L2VPN types";
}
description
"Container for MP BGP L2VPN";
}
container mp-bgp-evpn {
leaf vpn-id {
type svc-id;
description
"Identifies the target VPN";
}
leaf type {
type identityref {
base l2vpn-type;
}
description
"L2VPN types";
}
leaf mac-learning-mode {
type identityref {
base mac-learning-mode;
}
description
"Indicates through which plane MAC addresses are
advertised.";
}
leaf arp-suppress {
type boolean;
default false;
description
"Indicates whether to suppress ARP broadcast.";
}
description
"Container for MP BGP L2VPN";
}
container t-ldp-pwe {
list PE-EG-list {
key "service-ip-lo-addr vc-id";
leaf service-ip-lo-addr {
type inet:ip-address;
description
"Service ip lo address";
}
leaf vc-id {
type string;
description
"VC id";
}
description
"List of PE/EG";
}
description
"Container of T-LDP PWE configurations";
}
container pwe-encapsulation-type {
leaf ethernet {
type boolean;
description
"Ethernet";
}
leaf vlan {
type boolean;
description
"VLAN";
}
description
"Container of PWE Encapsulation Type configurations";
}
container pwe-mtu {
leaf allow-mtu-mismatch {
type boolean;
description
"Allow MTU mismatch";
}
description
"Container of PWE MTU configurations";
}
container control-word {
description
"Container of control word configurations";
}
description
"List of VPN Signaling Option.";
}
description
"Grouping for signaling option";
}
grouping load-balance-grouping {
leaf fat-pw {
type boolean;
description
"Fat label is applied to Pseudowires across MPLS
network";
}
leaf entropy-label {
type boolean;
description
"Entropy label is applied to IP forwarding,
L2VPN or L3VPN across MPLS network";
}
leaf vxlan-source-port {
type string;
description
"Vxlan source port";
}
description
"Grouping for load balance ";
}
grouping operational-requirements-ops {
leaf actual-site-start {
type yang:date-and-time;
config false;
description
"Optional leaf indicating actual date
and time when the service at a particular
site actually started";
}
leaf actual-site-stop {
type yang:date-and-time;
config false;
description
"Optional leaf indicating actual date
and time when the service at a particular
site actually stopped";
}
description
"This grouping defines some operational parameters
parameters";
}
grouping intra-mkt-grouping {
list intra-mkt {
key "metro-mkt-id mkt-name";
leaf metro-mkt-id {
type uint32;
description
"Metro MKT ID";
}
leaf mkt-name {
type string;
description
"MKT Name";
}
leaf ovc-id {
type string;
description
"OVC identifier";
}
description
"List of intra-MKT";
}
description
"Grouping for intra-MKT";
}
grouping inter-mkt-service {
leaf inter-mkt-service{
type boolean;
description
"Indicate whether service is inter market service.";
}
description
"Grouping for inter-MKT service";
}
grouping evc-id-grouping {
leaf evc-id {
type svc-id;
description
"Ethernet Virtual Connection identifier";
}
description
"Grouping for EVC-ID";
}
grouping svc-type-grouping {
container evc-type {
uses evc-id-grouping;
leaf number-of-pe {
type uint32;
config false;
description
"Number of PE";
}
leaf number-of-site {
type uint32;
config false;
description
"Number of Sites";
}
container uni-list {
if-feature uni-list;
list uni-list {
key "network-access-id";
leaf network-access-id {
type string;
description
"Network Access Identifier";
}
description
"List for UNIs";
}
description
"Container for UNI List";
}
description
"Container for Ethernet virtual connection.";
}
container ovc-type {
if-feature ovc-type;
list ovc-list {
key ovc-id;
leaf ovc-id {
type svc-id;
description
"OVC ID type";
}
leaf on-net {
type boolean;
description
"On net";
}
leaf off-net {
type boolean;
description
"Off net";
}
description
"List for OVC";
}
description
"Container for OVC";
}
description
"Grouping of service types.";
}
grouping cfm-802-grouping {
leaf MAID {
type string;
description
"MA ID";
}
leaf mep-id {
type uint32;
description
"Local MEP ID";
}
leaf mep-level {
type uint32;
description
"MEP level";
}
leaf mep-up-down {
type enumeration {
enum up {
description
"MEP up";
}
enum down {
description
"MEP down";
}
}
description
"MEP up/down";
}
leaf remote-mep-id {
type uint32;
description
"Remote MEP ID";
}
leaf cos-for-cfm-pdus {
type uint32;
description
"COS for CFM PDUs";
}
leaf ccm-interval {
type uint32;
description
"CCM interval";
}
leaf ccm-holdtime {
type uint32;
description
"CCM hold time";
}
leaf alarm-priority-defect {
type identityref {
base fault-alarm-defect-type;
}
description
"The lowest priority defect that is
allowed to generate a Fault Alarm.
The non-existence of this leaf means
that no defects are to be reported";
}
leaf ccm-p-bits-pri {
type ccm-priority-type;
description
"The priority parameter for CCMs transmitted by the MEP";
}
description
"Grouping for 802.1ag CFM attribute";
}
grouping y-1731 {
list y-1731 {
key MAID;
leaf MAID {
type string;
description
"MA ID ";
}
leaf mep-id {
type uint32;
description
"Local MEP ID";
}
leaf type {
type identityref {
base pm-type;
}
description
"Performance monitor types";
}
leaf remote-mep-id {
type uint32;
description
"Remote MEP ID";
}
leaf message-period {
type uint32;
description
"Defines the interval between OAM messages. The message
period is expressed in milliseconds";
}
leaf measurement-interval {
type uint32;
description
"Specifies the measurement interval for statistics. The
measurement interval is expressed in seconds";
}
leaf cos {
type uint32;
description
"Class of service";
}
leaf loss-measurement {
type boolean;
description
"Whether enable loss measurement";
}
leaf synthethic-loss-measurement {
type boolean;
description
"Indicate whether enable synthetic loss measurement";
}
container delay-measurement {
leaf enable-dm {
type boolean;
description
"Whether to enable delay measurement";
}
leaf two-way {
type boolean;
description
"Whether delay measurement is two-way (true) of one-
way (false)";
}
description
"Container for delay measurement";
}
leaf frame-size {
type uint32;
description
"Frame size";
}
leaf session-type {
type enumeration {
enum proactive {
description
"Proactive mode";
}
enum on-demand {
description
"On demand mode";
}
}
description
"Session type";
}
description
"List for y-1731.";
}
description
"Grouping for y.1731";
}
grouping enni-site-info-grouping {
container site-info {
leaf site-name {
type string;
description
"Site name";
}
leaf address {
type inet:ip-address;
description
"Address";
}
leaf Edge-Gateway-Device-Info {
type string;
description
"Edge Gateway Device Info ";
}
description
"Container of site info configurations";
}
description
"Grouping for site information";
}
grouping site-security {
container security-filtering {
uses mac-loop-prevention-grouping;
container access-control-list {
list mac {
key "mac-address";
leaf mac-address {
type yang:mac-address;
description
"MAC address";
}
description
"List for MAC";
}
description
"Container for access control";
}
uses mac-addr-limit-grouping;
uses B-U-M-storm-control-grouping;
description
"Security parameters";
}
description
"This grouping defines security parameters for a site";
}
grouping lacp-grouping {
container LACP {
leaf LACP-state {
type boolean;
description
"LACP on/off";
}
leaf LACP-mode {
type boolean;
description
"LACP mode";
}
leaf LACP-speed {
type boolean;
description
"LACP speed";
}
leaf mini-link {
type uint32;
description
"Mini link";
}
leaf system-priority {
type uint16;
description
"Indicates the LACP priority for the system.
The range is from 0 to 65535.
The default is 32768.";
}
container Micro-BFD {
if-feature Micro-BFD;
leaf Micro-BFD-on-off {
type enumeration {
enum on {
description
"Micro-bfd on";
}
enum off {
description
"Micro-bfd off";
}
}
description
"Micro BFD ON/OFF";
}
leaf bfd-interval {
type uint32;
description
"BFD interval";
}
leaf bfd-hold-timer {
type uint32;
description
"BFD hold timer";
}
description
"Container of Micro-BFD configurations";
}
container bfd {
if-feature bfd;
leaf bfd-enabled {
type boolean;
description
"BFD activation";
}
choice holdtime {
case profile {
leaf profile-name {
type string;
description
"Service provider well known profile.";
}
description
"Service provider well known profile.";
}
case fixed {
leaf fixed-value {
type uint32;
units msec;
description
"Expected hold time expressed in msec.";
}
}
description
"Choice for hold time flavor.";
}
description
"Container for BFD.";
}
container Member-link-list {
list member-link {
key "name";
leaf name {
type string;
description
"Member link name";
}
leaf port-speed {
type uint32;
description
"Port speed";
}
leaf mode {
type neg-mode;
description
"Negotiation mode";
}
leaf mtu {
type uint32;
description
"MTU";
}
container oam-802.3AH-link {
if-feature oam-3ah;
leaf enable {
type boolean;
description
"Indicate whether support oam 802.3 ah link";
}
description
"Container for oam 802.3 ah link.";
}
description
"Member link";
}
description
"Container of Member link list";
}
leaf flow-control {
type string;
description
"Flow control";
}
leaf encapsulation-type {
type enumeration {
enum VLAN {
description
"VLAN";
}
enum ether {
description
"Ethernet";
}
}
description
"Encapsulation type";
}
leaf ethertype {
type string;
description
"Ether type";
}
leaf lldp {
type boolean;
description
"LLDP";
}
description
"LACP";
}
description
"Grouping for lacp";
}
grouping phy-interface-grouping {
container phy-interface {
leaf port-number {
type uint32;
description
"Port number";
}
leaf port-speed {
type uint32;
description
"Port speed";
}
leaf mode {
type neg-mode;
description
"Negotiation mode";
}
leaf phy-mtu {
type uint32;
description
"PHY MTU";
}
leaf flow-control {
type string;
description
"Flow control";
}
leaf encapsulation-type {
type enumeration {
enum VLAN {
description
"VLAN";
}
enum Ethernet {
description
"Ethernet";
}
}
description
"Encapsulation-type";
}
leaf ethertype {
type string;
description
"Ethertype";
}
leaf lldp {
type boolean;
description
"LLDP";
}
container oam-802.3AH-link {
if-feature oam-3ah;
leaf enable {
type boolean;
description
"Indicate whether support oam 802.3 ah link";
}
description
"Container for oam 802.3 ah link.";
}
leaf uni-loop-prevention {
type boolean;
description
"If this leaf set to truth that the port automatically
goes down when a physical loopback is detect.";
}
description
"Container of PHY Interface Attributes configurations";
}
description
"Grouping for phy interface.";
}
grouping lag-interface-grouping {
container LAG-interface {
list LAG-interface {
key "LAG-interface-number";
leaf LAG-interface-number {
type uint32;
description
"LAG interface number";
}
uses lacp-grouping;
description
"List of LAG interfaces";
}
description
"Container of LAG interface attributes configuration";
}
description
"Grouping for LAG interface";
}
grouping l2-access-grouping {
container dot1q {
when "'../l2-access-type'='dot1q'";
leaf physical-inf {
type string;
description
"Physical Interface";
}
leaf vlan-id {
type uint32;
description
"VLAN identifier";
}
description
"Qot1q";
}
container qinq {
when "'../l2-access-type'='qinq'";
leaf s-vlan-id {
type uint32;
description
"S-VLAN Identifier";
}
leaf c-vlan-id {
type uint32;
description
"C-VLAN Identifier";
}
description
"QinQ";
}
leaf sub-if-id {
when "'../l2-access-type'='sub-interface'";
type uint32;
description
"Sub interface ID";
}
container vxlan {
when "'../l2-access-type'='vxlan'";
leaf vni-id {
type uint32;
description
"VNI Identifier";
}
list peer-list {
key peer-ip;
leaf peer-ip {
type inet:ip-address;
description
"Peer IP";
}
description
"List for peer IP";
}
description
"QinQ";
}
description
"Grouping for Layer2 access";
}
grouping ethernet-connection-grouping {
container ethernet-connection {
leaf ESI {
type string;
description
"Ethernet segment id";
}
leaf interface-description {
type string;
description
"Interface description";
}
container vlan {
leaf vlan-id {
type uint32;
description
"VLAN-ID/Ethernet Tag configurations";
}
description
"Abstract container for VLAN";
}
uses l2-access-grouping;
uses phy-interface-grouping;
uses lag-interface-grouping;
description
"Container for bearer";
}
description
"Grouping for bearer.";
}
grouping evc-mtu-grouping {
leaf evc-mtu {
type uint32;
description
"EVC MTU";
}
description
"Grouping for evc mtu";
}
grouping mac-addr-limit-grouping {
container mac-addr-limit {
leaf exceeding-option {
type uint32;
description
"Exceeding option";
}
description
"Container of MAC-Addr limit configurations";
}
description
"Grouping for mac address limit";
}
grouping availability-grouping {
container availability {
choice redundancy-mode {
case single-active {
leaf single-active {
type boolean;
description
"Single active";
}
description
"Single active case";
}
case all-active {
leaf all-active {
type boolean;
description
"All active";
}
description
"All active case";
}
description
"Redundancy mode choice";
}
description
"Container of availability optional configurations";
}
description
"Grouping for availability";
}
grouping l2cp-grouping {
container L2CP-control {
leaf stp-rstp-mstp {
type control-mode;
description
"STP/RSTP/MSTP";
}
leaf pause {
type control-mode;
description
"Pause";
}
leaf lacp-lamp {
type control-mode;
description
"LACP/LAMP";
}
leaf link-oam {
type control-mode;
description
"Link OAM";
}
leaf esmc {
type control-mode;
description
"ESMC";
}
leaf l2cp-802.1x {
type control-mode;
description
"802.x";
}
leaf e-lmi {
type control-mode;
description
"E-LMI";
}
leaf lldp {
type boolean;
description
"LLDP";
}
leaf ptp-peer-delay {
type control-mode;
description
"PTP peer delay";
}
leaf garp-mrp {
type control-mode;
description
"GARP/MRP";
}
leaf provider-bridge-group {
type control-mode;
description
"Provider bridge group reserved MAC address
01-80-C2-00-00-08";
}
leaf provider-bridge-mvrp {
type control-mode;
description
"Provider bridge MVRP reserved MAC address
01-80-C2-00-00-0D";
}
description
"Container of L2CP control configurations";
}
description
"Grouping for l2cp control";
}
grouping service-level-grouping {
container service-level {
leaf cos-identifier {
type identityref {
base cos-id;
}
description
"COS Identifier [ EVC | EVC + PCP ]";
}
leaf color-identifier {
type identityref {
base color-id;
}
description
"Color Identifier [ EVC | EVC + CVLAN ]";
}
leaf ingress-bw-profile-per-evc {
type string;
description
"Ingress Bandwidth Profile per EVC";
}
leaf ingress-bw-profile-per-cos-id {
type string;
description
"Ingress Bandwidth Profile per COS Identifier";
}
leaf egress-bw-profile-per-evc {
type string;
description
"Egress Bandwidth Profile per EVC";
}
leaf egress-bw-profile-per-cos-id {
type string;
description
"Egress Bandwidth Profile per COS Identifier";
}
leaf byte-offset {
type uint16;
description
"For not including extra VLAN tags in the QoS
calculation";
}
leaf policing {
type identityref {
base policing;
}
description
"The policing can be either one-rate,
two-color (1R2C) or two-rate, three-color (2R3C)";
}
leaf perf-tier-opt {
type identityref {
base perf-tier-opt;
}
description
"Performance tier option";
}
leaf COS {
type uint32;
description
"Class of Service";
}
description
"Container of service level configurations.";
}
description
"Grouping for service level.";
}
grouping B-U-M-storm-control-grouping {
container B-U-M-storm-control {
leaf BUM-overall-rate {
type uint32;
description
"overall rate for BUM";
}
list BUM-rate-per-type {
key "type";
leaf type {
type identityref {
base BUM-type;
}
description
"BUM type";
}
leaf rate {
type uint32;
description
"rate for BUM";
}
description
"List of rate per type";
}
description
"Container of B-U-M-strom-control configurations";
}
description
"Grouping for B-U-M-strom-control";
}
grouping mac-loop-prevention-grouping {
container mac-loop-prevention {
leaf frequency {
type uint32;
description
"Frequency";
}
leaf protection-type {
type identityref {
base loop-prevention-type;
}
description
"Protection type";
}
leaf number-retries {
type uint32;
description
"Number of retries";
}
description
"Container of MAC loop prevention.";
}
description
"Grouping for MAC loop prevention";
}
grouping ethernet-svc-oam-grouping {
container Ethernet-Service-OAM {
leaf MD-name {
type string;
description
"Maintenance domain name";
}
leaf MD-level {
type uint8;
description
"Maintenance domain level";
}
container cfm-802.1-ag {
list n2-uni-c {
key "MAID";
uses cfm-802-grouping;
description
"List of UNI-N to UNI-C";
}
list n2-uni-n {
key "MAID";
uses cfm-802-grouping;
description
"List of UNI-N to UNI-N";
}
description
"Container of 802.1ag CFM configurations.";
}
uses y-1731;
description
"Container for Ethernet service OAM.";
}
description
"Grouping for Ethernet service OAM.";
}
grouping fate-sharing-group {
container groups {
leaf fate-sharing-group-size {
type uint16;
description
"Fate sharing group size.";
}
list group {
key group-id;
leaf group-id {
type string;
description
"Group-id the site network access
is belonging to";
}
description
"List of group-id";
}
description
"Groups the fate sharing group member
is belonging to";
}
description
"Grouping for Fate sharing group.";
}
grouping site-group {
container groups {
list group {
key group-id;
leaf group-id {
type string;
description
"Group-id the site is belonging to";
}
description
"List of group-id";
}
description
"Groups the site or site-network-access
is belonging to.";
}
description
"Grouping definition to assign
group-ids to site or site-network-access";
}
grouping access-diversity {
container access-diversity {
if-feature site-diversity;
uses fate-sharing-group;
container constraints {
list constraint {
key constraint-type;
leaf constraint-type {
type identityref {
base placement-diversity;
}
description
"Diversity constraint type.";
}
container target {
choice target-flavor {
case id {
list group {
key group-id;
leaf group-id {
type string;
description
"The constraint will apply
against this particular
group-id";
}
description
"List of groups";
}
}
case all-accesses {
leaf all-other-accesses {
type empty;
description
"The constraint will apply
against all other site network
access of this site";
}
}
case all-groups {
leaf all-other-groups {
type empty;
description
"The constraint will apply
against all other groups the
customer is managing";
}
}
description
"Choice for the group definition";
}
description
"The constraint will apply against
this list of groups";
}
description
"List of constraints";
}
description
"Constraints for placing this site
network access";
}
description
"Diversity parameters.";
}
description
"This grouping defines access diversity
parameters";
}
grouping request-type-profile-grouping {
container request-type-profile {
choice request-type-choice {
case dot1q-case {
container dot1q {
leaf physical-if {
type string;
description
"Physical interface";
}
leaf vlan-id {
type uint16;
description
"VLAN ID";
}
description
"Container for dot1q.";
}
description
"Case for dot1q";
}
case physical-case {
leaf physical-if {
type string;
description
"Physical interface";
}
leaf circuit-id {
type string;
description
"Circuit ID";
}
description
"Physical case";
}
description
"Choice for request type";
}
description
"Container for request type profile.";
}
description
"Grouping for request type profile";
}
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 ... Operator specific.";
}
leaf strict {
type boolean;
default false;
description
"Define if the requested-type is a preference
or a strict requirement.";
}
uses request-type-profile-grouping;
description
"Container for requested type.";
}
leaf always-on {
if-feature always-on;
type boolean;
default true;
description
"Request for an always on access type.
This means no Dial access type for
example.";
}
leaf bearer-reference {
if-feature bearer-reference;
type string;
description
"This is an internal reference for the
service provider.";
}
description
"Bearer specific parameters.
To be augmented.";
}
description
"Grouping to define physical properties of
a site attachment.";
}
grouping vpn-attachment-grouping {
container vpn-attachment {
leaf device-id {
type string;
description
"Device ID";
}
container management {
leaf address-family {
type identityref {
base address-family;
}
description
"Address family used for management.";
}
leaf address {
type inet:ip-address;
description
"Management address";
}
description
"Management configuration..";
}
choice attachment-flavor {
case vpn-id {
leaf vpn-id {
type leafref {
path "/l2vpn-svc/vpn-services"+
"/vpn-svc/vpn-id";
}
description
"Reference to a VPN.";
}
leaf site-role {
type identityref {
base site-role;
}
default any-to-any-role;
description
"Role of the site in the IPVPN.";
}
}
mandatory true;
description
"Choice for VPN attachment flavor.";
}
description
"Defines VPN attachment of a site.";
}
description
"Grouping for access attachment";
}
grouping site-service-basic {
container svc-input-bandwidth {
if-feature input-bw;
list input-bandwidth {
key "id type";
leaf id {
type string;
description
"ID";
}
leaf type {
type identityref {
base bw-type;
}
description
"Bandwidth Type";
}
leaf evc-id {
type svc-id;
description
"EVC ID";
}
leaf CIR {
type uint32;
description
"Committed Information Rate";
}
leaf CBS {
type uint32;
description
"Committed Burst Size";
}
leaf EIR {
type uint32;
description
"Excess Information Rate";
}
leaf EBS {
type uint32;
description
"Excess Burst Size";
}
leaf CM {
type uint32;
description
"Color Mode";
}
description
"List for input bandwidth";
}
description
"From the PE perspective, the service input
bandwidth of the connection.";
}
container svc-output-bandwidth {
if-feature output-bw;
list output-bandwidth {
key "id type";
leaf id {
type string;
description
"ID";
}
leaf type {
type identityref {
base bw-type;
}
description
"Bandwidth Type";
}
leaf evc-id {
type svc-id;
description
"EVC ID";
}
leaf CIR {
type uint32;
description
"Committed Information Rate";
}
leaf CBS {
type uint32;
description
"Committed Burst Size";
}
leaf EIR {
type uint32;
description
"Excess Information Rate";
}
leaf EBS {
type uint32;
description
"Excess Burst Size";
}
leaf CM {
type uint32;
description
"Color Mode";
}
description
"List for output bandwidth";
}
description
"From the PE perspective, the service output
bandwidth of the connection.";
}
description
"Grouping for site service";
}
grouping flow-definition {
container match-flow {
leaf dscp {
type inet:dscp;
description
"DSCP value.";
}
leaf dot1p {
type uint8 {
range "0 .. 7";
}
description
"802.1p matching.";
}
leaf pcp {
type uint8;
description
"PCP value";
}
leaf src-mac {
type yang:mac-address;
description
"Source MAC";
}
leaf dst-mac {
type yang:mac-address;
description
"Destination MAC";
}
container cos-color-id {
leaf device-id {
type string;
description
"Device ID";
}
leaf cos-label {
type identityref {
base cos-id;
}
description
"COS label";
}
leaf pcp {
type uint8;
description
"PCP value";
}
leaf dscp {
type inet:dscp;
description
"DSCP value.";
}
description
"Container for cos color id";
}
leaf color-type {
type identityref {
base color-type;
}
description
"Color Types";
}
leaf-list target-sites {
type svc-id;
description
"Identify a site as traffic destination.";
}
description
"Describe flow matching criterions.";
}
description
"Flow definition based on criteria.";
}
grouping site-service-qos-profile {
container qos {
if-feature qos;
container qos-classification-policy {
list rule {
key id;
ordered-by user;
leaf id {
type uint16;
description
"ID of the rule.";
}
choice match-type {
case match-flow {
uses flow-definition;
}
case match-phy-port {
leaf match-phy-port {
type uint16;
description
"Defines the physical port
to match.";
}
}
description
"Choice for classification";
}
leaf target-class-id {
type string;
description
"Identification of the class of service.
This identifier is internal to the
administration.";
}
description
"List of marking rules.";
}
description
"Need to express marking rules ...";
}
container qos-profile {
choice qos-profile {
description
"Choice for QoS profile.
Can be standard profile or custom.";
case standard {
leaf ingress-profile {
type string;
description
"Ingress QoS Profile to be used";
}
leaf egress-profile {
type string;
description
"Egress QoS Profile to be used";
}
}
case custom {
container classes {
if-feature qos-custom;
list class {
key class-id;
leaf class-id {
type string;
description
"Identification of the class of
service. This identifier is internal
to the administration.";
}
leaf direction {
type direction-type;
description
"Direction type";
}
leaf policing {
type identityref {
base policing;
}
description
"The policing can be either one-rate,
two-color (1R2C) or two-rate, three-color
(2R3C)";
}
leaf byte-offset {
type uint16;
description
"For not including extra VLAN tags in the QoS
calculation";
}
leaf perf-tier-opt {
type identityref {
base perf-tier-opt;
}
description
"Performance tier option";
}
leaf rate-limit {
type uint8;
units percent;
description
"To be used if class must be rate limited.
Expressed as percentage of the svc-bw.";
}
leaf discard-percentage {
type uint8;
default 100;
description
"The value of the discard-percentage,
Expressed as pecentage of the svc-bw ";
}
container frame-delay {
choice flavor {
case lowest {
leaf use-low-del {
type empty;
description
"The traffic class should use
the lowest delay path";
}
}
case boundary {
leaf delay-bound {
type uint16;
units msec;
description
"The traffic class should use
a path with a defined maximum
delay.";
}
}
description
"Delay constraint on the traffic
class";
}
description
"Delay constraint on the traffic
class";
}
container frame-jitter {
choice flavor {
case lowest {
leaf use-low-jit {
type empty;
description
"The traffic class should use
the lowest jitter path";
}
}
case boundary {
leaf delay-bound {
type uint32;
units usec;
description
"The traffic class should use
a path with a defined maximum
jitter.";
}
}
description
"Jitter constraint on the traffic
class";
}
description
"Jitter constraint on the traffic
class";
}
container frame-loss {
leaf fr-loss-rate {
type decimal64 {
fraction-digits 2;
}
description
"Loss constraint on the traffic class";
}
description
"Container for frame loss";
}
description
"List of class of services.";
}
description
"Container for list of class of services.";
}
}
}
description
"Qos profile configuration.";
}
description
"QoS configuration.";
}
description
"This grouping defines QoS parameters
for a site";
}
grouping service-grouping {
container service {
uses site-service-basic;
uses site-service;
leaf service-multiplexing {
type boolean;
description
"Service multiplexing";
}
uses site-service-qos-profile;
description
"Container for service";
}
description
"Grouping for service.";
}
/* MAIN L2VPN SERVICE */
container l2vpn-svc {
container customer-info {
uses customer-info-grouping;
description
"Container for customer information.";
}
container vpn-services {
list vpn-svc {
key "vpn-id";
leaf vpn-id {
type svc-id;
description
"Defining a service id.";
}
leaf svc-type {
type identityref {
base service-type;
}
description
"Service type";
}
uses svc-type-grouping;
container ethernet-svc-type {
uses ethernet-service-type;
description
"Container of Ethernet service type";
}
leaf svc-topo {
type identityref {
base svc-topo-type;
}
description
"Defining service topology, such as
point to point, multipoint to multipoint,
rooted multipoint, etc.";
}
uses vpn-service-cloud-access; // need fixed??
container ce-vlan-preservation {
description
"CE vlan preservation";
}
container metro-network-id {
uses inter-mkt-service;
uses intra-mkt-grouping;
description
"Container of Metro-Network ID configurations";
}
container L2CP-control {
leaf stp-rstp-mstp {
type control-mode;
description
"STP/RSTP/MSTP";
}
leaf pause {
type control-mode;
description
"Pause";
}
leaf lldp {
type boolean;
description
"LLDP";
}
description
"Container of L2CP control configurations";
}
container load-balance-options {
uses load-balance-grouping;
description
"Container for load balance options";
}
uses site-service;
uses service-protection;
container sla-targets {
description
"Container for SLA targets";
}
description
"List of vpn-svc";
}
description
"Container for VPN services.";
}
/* SITE */
container sites {
list site {
key "site-id site-type";
leaf site-id {
type string;
description
"Site id";
}
leaf site-type {
type identityref {
base site-type;
}
description
"Site type";
}
uses site-device;
uses site-management;
uses customer-location-info;
uses site-diversity;
uses site-vpn-policy ;
container signaling-option {
if-feature signaling-option;
uses signaling-option-grouping;
description
"Container for signaling option";
}
container load-balance-options {
uses load-balance-grouping;
description
"Container for load balance options";
}
uses operational-requirements-ops;
container ports {
list port {
key "network-access-id";
leaf network-access-id {
type string;
description
"Identifier of network access";
}
leaf remote-carrier-name {
when "'../site-type' = 'enni'" {
description
"Site type = enni";
}
type string;
description
"Remote carrier name";
}
uses access-diversity;
uses site-attachment-bearer;
uses ethernet-connection-grouping;
uses l2cp-grouping;
uses evc-mtu-grouping;
uses availability-grouping;
uses vpn-attachment-grouping;
uses service-grouping;
uses ethernet-svc-oam-grouping;
uses site-security;
description
"List of ports";
}
description
"Container of port configurations";
}
description
"List of sites";
}
description
"Container of site configurations";
}
description
"Container for L2VPN service";
}
}
<CODE ENDS>
The YANG modules defined in this document MAY be accessed via the RESTCONF protocol [RFC8040] or NETCONF protocol ([RFC6241]). The lowest RESTCONF or NETCONF layer requires that the transport-layer protocol provides both data integrity and confidentiality, see Section 2 in [RFC8040] and [RFC6241]. The client MUST carefully examine the certificate presented by the server to determine if it meets the client's expectations, and the server MUST authenticate client access to any protected resource. The client identity derived from the authentication mechanism used is subject to the NETCONF Access Control Module (NACM) ([RFC6536]). Other protocols to access this YANG module are also required to support the similar mechanism.
The data nodes defined in the "ietf-l2vpn-svc" YANG module MUST be carefully created/read/updated/deleted. The entries in the lists below include customer proprietary or confidential information, therefore only authorized clients MUST access the information and the other clients MUST NOT be able to access to the information.
Thanks to Qin Wu and Adrian Farrel for facilitating work on the initial revisions of this document.
This document has drawn on the work of the L3SM Working Group expressed in [I-D.ietf-l3sm-l3vpn-service-model].
IANA is requested to assign a new URI from the IETF XML registry ([RFC3688]). The following URI is suggested:
URI: urn:ietf:params:xml:ns:yang:ietf-l2vpn-svc
Registrant Contact: L2SM WG
XML: N/A, the requested URI is an XML namespace
This document also requests a new YANG module name in the YANG Module Names registry ([RFC6020]) with the following suggestion:
name: ietf-l2vpn-svc
namespace: urn:ietf:params:xml:ns:yang:ietf-l2vpn-svc
prefix: l2vpn-svc
reference: RFC XXXX