Telefonica

Madrid Spain samier.barguilgiraldo.ext@telefonica.com

Telefonica

Madrid Spain oscar.gonzalezdedios@telefonica.com

Orange

France mohamed.boucadair@orange.com

Huawei

101 Software Avenue Yuhua District Nanjing Jiangsu 210012 China bill.wu@huawei.com

opsawg service automation network automation service delivery service provisioning Slice network slicing vitalisation Automation Network Models This document defines a common YANG module that is meant to be reused by various VPN-related modules such as Layer 3 VPN and Layer 2 VPN network models.

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2022 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 () 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.

Table of Contents

• .  Introduction
• .  Terminology
• .  Description of the VPN Common YANG Module
• .  Layer 2/3 VPN Common Module
• .  Security Considerations
• .  IANA Considerations
• .  References
  • .  Normative References
  • .  Informative References
• .  Example of Common Data Nodes in Early L2NM/L3NM Designs
• Acknowledgements
• Contributors
• Authors' Addresses

Introduction The IETF has specified YANG modules for VPN services, e.g., the Layer 3 VPN Service Model (L3SM) or the Layer 2 VPN Service Model (L2SM) . Other relevant YANG data models are the Layer 3 VPN Network Model (L3NM) and the Layer 2 VPN Network Model (L2NM) . There are common data nodes and structures that are present in all of these models or at least a subset of them. This document defines a common YANG module that is meant to be reused by various VPN-related modules such as the L3NM and the L2NM : "ietf-vpn-common" (). The "ietf-vpn-common" module includes a set of identities, types, and groupings that are meant to be reused by other VPN-related YANG modules independently of their layer (e.g., Layer 2, Layer 3) and the type of the module (e.g., network model, service model), including possible future revisions of existing models (e.g., the L3SM or the L2SM ).

Terminology The terminology for describing YANG modules is defined in . The meanings of the symbols in tree diagrams are defined in . The reader may refer to and for VPN-related terms. This document inherits many terms from and (e.g., Enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communications (URLLC), Massive Machine Type Communications (mMTC)).

Description of the VPN Common YANG Module The "ietf-vpn-common" module defines a set of common VPN-related features, including the following:

Encapsulation features, such as the following:

• dot1Q ,
• QinQ ,
• link aggregation , and
• Virtual eXtensible Local Area Networks (VXLANs).

Multicast .

Routing features, such as the following:

• BGP ,
• OSPF ,
• IS-IS ,
• RIP ,
• Bidirectional Forwarding Detection (BFD) , and
• Virtual Router Redundancy Protocol (VRRP) .

Also, the module defines a set of identities, including the following:

'service-type':

Used to identify the VPN service type. Examples of supported service types are as follows:

• L3VPN,
• Virtual Private LAN Service (VPLS) using BGP ,
• VPLS using the Label Distribution Protocol (LDP),
• Virtual Private Wire Service (VPWS),
• BGP MPLS-Based Ethernet VPN,
• Ethernet VPN (EVPN), and
• Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN).

'vpn-signaling-type':

Used to identify the signaling mode used for a given service type. Examples of supported VPN signaling types are as follows:

• L2VPNs using BGP ,
• LDP , and
• Layer Two Tunneling Protocol (L2TP) .

The module covers both IPv4 and IPv6 identities. It also includes multicast-related identities such as Internet Group Management Protocol version 1 (IGMPv1) , IGMPv2 , IGMPv3 , Multicast Listener Discovery version 1 (MLDv1) , MLDv2 , and Protocol Independent Multicast (PIM) . The reader should refer to for the full list of supported identities (identities related to address families, VPN topologies, network access types, operational and administrative status, site or node role, VPN service constraints, routing protocols, route import and export policies, bandwidth, Quality of Service (QoS), etc.). The "ietf-vpn-common" module also contains a set of reusable VPN-related groupings. provides the tree diagram that depicts the common groupings for the "ietf-vpn-common" module.

VPN Common Tree module: ietf-vpn-common grouping vpn-description: +-- vpn-id? vpn-id +-- vpn-name? string +-- vpn-description? string +-- customer-name? string grouping vpn-profile-cfg: +-- valid-provider-identifiers +-- external-connectivity-identifier* [id] | {external-connectivity}? | +-- id string +-- encryption-profile-identifier* [id] | +-- id string +-- qos-profile-identifier* [id] | +-- id string +-- bfd-profile-identifier* [id] | +-- id string +-- forwarding-profile-identifier* [id] | +-- id string +-- routing-profile-identifier* [id] +-- id string grouping oper-status-timestamp: +--ro status? identityref +--ro last-change? yang:date-and-time grouping service-status: +-- status +-- admin-status | +-- status? identityref | +-- last-change? yang:date-and-time +--ro oper-status +--ro status? identityref +--ro last-change? yang:date-and-time grouping underlay-transport: +-- (type)? +--:(abstract) | +-- transport-instance-id? string | +-- instance-type? identityref +--:(protocol) +-- protocol* identityref grouping vpn-route-targets: +-- vpn-target* [id] | +-- id uint8 | +-- route-targets* [route-target] | | +-- route-target rt-types:route-target | +-- route-target-type rt-types:route-target-type +-- vpn-policies +-- import-policy? string +-- export-policy? string grouping route-distinguisher: ... grouping vpn-components-group: +-- groups +-- group* [group-id] +-- group-id string grouping placement-constraints: +-- constraint* [constraint-type] +-- constraint-type? identityref +-- target +-- (target-flavor)? +--:(id) | +-- group* [group-id] | +-- group-id string +--:(all-accesses) | +-- all-other-accesses? empty +--:(all-groups) +-- all-other-groups? empty grouping ports: ... grouping qos-classification-policy: ...

The descriptions of the common groupings are provided below:

'vpn-description':

A YANG grouping that provides common administrative VPN information such as an identifier, a name, a textual description, and a customer name.

'vpn-profile-cfg':

A YANG grouping that defines a set of valid profiles (encryption, routing, forwarding, etc.) that can be bound to a Layer 2/3 VPN. This document does not make any assumptions about the structure of such profiles but allows "gluing" a VPN service with other parameters that can be required locally to provide value-added features to requesting customers. For example, a service provider may provide external connectivity to a VPN customer (e.g., to a private or public cloud, Internet). Such a service may involve tweaking both filtering and NAT rules (e.g., binding a Virtual Routing and Forwarding (VRF) interface with a NAT instance as discussed in ). These value-added features may be bound to all, or a subset of, network accesses. Some of these value-added features may be implemented in nodes other than Provider Edges (PEs) (e.g., a P node or even a dedicated node that hosts the NAT function). Elaborating on the structure of these profiles is beyond the scope of this document.

'oper-status-timestamp':

A YANG grouping that defines the operational status updates of a VPN service or component.

'service-status':

A YANG grouping that defines the administrative and operational status of a component. The grouping can be applied to the whole service or an endpoint.

'underlay-transport':

A YANG grouping that defines the type of the underlay transport for a VPN service or how that underlay is set. The underlay transport can be expressed as an abstract transport instance (e.g., an identifier of a VPN+ instance , a virtual network identifier , or a network slice name ) or as an ordered list of the actual protocols to be enabled in the network. The module supports a rich set of protocol identifiers that can be used, for example, to refer to an underlay transport. Examples of supported protocols are as follows:

• IP in IP ,
• Generic Routing Encapsulation (GRE) ,
• MPLS in UDP ,
• Generic Network Virtualization Encapsulation (Geneve) ,
• Segment Routing (SR) ,
• Resource ReSerVation Protocol (RSVP) with traffic engineering extensions , and
• BGP with labeled prefixes .

'vpn-route-targets':

A YANG grouping that defines Route Target (RT) import/export rules used in a BGP-enabled VPN. This grouping can be used for both L3VPNs and L2VPNs . Note that this is modeled as a list to ease the reuse of this grouping in modules where an RT identifier is needed (e.g., associating an operator with RTs).

'route-distinguisher':

A YANG grouping that defines Route Distinguishers (RDs). As depicted in , the module supports the following RD assignment modes: direct assignment, full automatic assignment, automatic assignment from a given pool, and no assignment. Also, the module accommodates deployments where only the Assigned Number subfield of RDs () is assigned from a pool while the Administrator subfield is set to, for example, the Router ID that is assigned to a VPN node. The module supports three modes for managing the Assigned Number subfield: explicit assignment, automatic assignment from a given pool, and full automatic assignment.

Route Distinguisher Grouping Subtree grouping route-distinguisher: +-- (rd-choice)? +--:(directly-assigned) | +-- rd? rt-types:route-distinguisher +--:(directly-assigned-suffix) | +-- rd-suffix? uint16 +--:(auto-assigned) | +-- rd-auto | +-- (auto-mode)? | | +--:(from-pool) | | | +-- rd-pool-name? string | | +--:(full-auto) | | +-- auto? empty | +--ro auto-assigned-rd? | | rt-types:route-distinguisher +--:(auto-assigned-suffix) | +-- rd-auto-suffix | +-- (auto-mode)? | | +--:(from-pool) | | | +-- rd-pool-name? string | | +--:(full-auto) | | +-- auto? empty | +--ro auto-assigned-rd-suffix? uint16 +--:(no-rd) +-- no-rd? empty

'vpn-components-group':

A YANG grouping that is used to group VPN nodes, VPN network accesses, or sites. For example, diversity or redundancy constraints can be applied on a per-group basis.

'placement-constraints':

A YANG grouping that is used to define the placement constraints of a VPN node, VPN network access, or site.

'ports':

A YANG grouping that defines ranges of source and destination port numbers and operators. The subtree of this grouping is depicted in .

Port Numbers Grouping Subtree grouping ports: +-- (source-port)? | +--:(source-port-range-or-operator) | +-- source-port-range-or-operator | +-- (port-range-or-operator)? | +--:(range) | | +-- lower-port inet:port-number | | +-- upper-port inet:port-number | +--:(operator) | +-- operator? operator | +-- port inet:port-number +-- (destination-port)? +--:(destination-port-range-or-operator) +-- destination-port-range-or-operator +-- (port-range-or-operator)? +--:(range) | +-- lower-port inet:port-number | +-- upper-port inet:port-number +--:(operator) +-- operator? operator +-- port inet:port-number

'qos-classification-policy':

A YANG grouping that defines a set of QoS classification policies based on various Layer 3/4 and application match criteria. The subtree of this grouping is depicted in . The QoS match criteria reuse groupings that are defined in the packet fields module "ietf-packet-fields" (). Any Layer 4 protocol can be indicated in the 'protocol' data node under 'l3', but only TCP- and UDP-specific match criteria are elaborated on in this version, as these protocols are widely used in the context of VPN services. Future revisions can be considered to add other Layer-4-specific parameters (e.g., the Stream Control Transmission Protocol ), if needed. Some transport protocols use existing protocols (e.g., TCP or UDP) as the substrate. The match criteria for such protocols may rely upon the 'protocol' under 'l3', TCP/UDP match criteria as shown in , part of the TCP/UDP payload, or a combination thereof. This version of the module does not support such advanced match criteria. Future revisions of the module may consider adding match criteria based on the transport protocol payload (e.g., by means of a bitmask match).

QoS Classification Subtree grouping qos-classification-policy: +-- rule* [id] +-- id string +-- (match-type)? | +--:(match-flow) | | +-- (l3)? | | | +--:(ipv4) | | | | +-- ipv4 | | | | +-- dscp? inet:dscp | | | | +-- ecn? uint8 | | | | +-- length? uint16 | | | | +-- ttl? uint8 | | | | +-- protocol? uint8 | | | | +-- ihl? uint8 | | | | +-- flags? bits | | | | +-- offset? uint16 | | | | +-- identification? uint16 | | | | +-- (destination-network)? | | | | | +--:(destination-ipv4-network) | | | | | +-- destination-ipv4-network? | | | | | inet:ipv4-prefix | | | | +-- (source-network)? | | | | +--:(source-ipv4-network) | | | | +-- source-ipv4-network? | | | | inet:ipv4-prefix | | | +--:(ipv6) | | | +-- ipv6 | | | +-- dscp? inet:dscp | | | +-- ecn? uint8 | | | +-- length? uint16 | | | +-- ttl? uint8 | | | +-- protocol? uint8 | | | +-- (destination-network)? | | | | +--:(destination-ipv6-network) | | | | +-- destination-ipv6-network? | | | | inet:ipv6-prefix | | | +-- (source-network)? | | | | +--:(source-ipv6-network) | | | | +-- source-ipv6-network? | | | | inet:ipv6-prefix | | | +-- flow-label? | | | inet:ipv6-flow-label | | +-- (l4)? | | +--:(tcp) | | | +-- tcp | | | +-- sequence-number? uint32 | | | +-- acknowledgement-number? uint32 | | | +-- data-offset? uint8 | | | +-- reserved? uint8 | | | +-- flags? bits | | | +-- window-size? uint16 | | | +-- urgent-pointer? uint16 | | | +-- options? binary | | | +-- (source-port)? | | | | +--:(source-port-range-or-operator) | | | | +-- source-port-range-or-operator | | | | +-- (port-range-or-operator)? | | | | +--:(range) | | | | | +-- lower-port | | | | | | inet:port-number | | | | | +-- upper-port | | | | | inet:port-number | | | | +--:(operator) | | | | +-- operator? operator | | | | +-- port | | | | inet:port-number | | | +-- (destination-port)? | | | +--:(destination-port-range-or-operator) | | | +-- destination-port-range-or-operator | | | +-- (port-range-or-operator)? | | | +--:(range) | | | | +-- lower-port | | | | | inet:port-number | | | | +-- upper-port | | | | inet:port-number | | | +--:(operator) | | | +-- operator? operator | | | +-- port | | | inet:port-number | | +--:(udp) | | +-- udp | | +-- length? uint16 | | +-- (source-port)? | | | +--:(source-port-range-or-operator) | | | +-- source-port-range-or-operator | | | +-- (port-range-or-operator)? | | | +--:(range) | | | | +-- lower-port | | | | | inet:port-number | | | | +-- upper-port | | | | inet:port-number | | | +--:(operator) | | | +-- operator? operator | | | +-- port | | | inet:port-number | | +-- (destination-port)? | | +--:(destination-port-range-or-operator) | | +-- destination-port-range-or-operator | | +-- (port-range-or-operator)? | | +--:(range) | | | +-- lower-port | | | | inet:port-number | | | +-- upper-port | | | inet:port-number | | +--:(operator) | | +-- operator? operator | | +-- port | | inet:port-number | +--:(match-application) | +-- match-application? identityref +-- target-class-id? string

Layer 2/3 VPN Common Module This module uses types defined in , , and . It also uses the extension defined in . module ietf-vpn-common { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-vpn-common"; prefix vpn-common; import ietf-netconf-acm { prefix nacm; reference "RFC 8341: Network Configuration Access Control Model"; } import ietf-routing-types { prefix rt-types; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Data Types, Section 3"; } import ietf-packet-fields { prefix packet-fields; reference "RFC 8519: YANG Data Model for Network Access Control Lists (ACLs)"; } organization "IETF OPSAWG (Operations and Management Area Working Group)"; contact "WG Web: <https://datatracker.ietf.org/wg/opsawg/> WG List: <mailto:opsawg@ietf.org> Editor: Mohamed Boucadair <mailto:mohamed.boucadair@orange.com> Author: Samier Barguil <mailto:samier.barguilgiraldo.ext@telefonica.com> Editor: Oscar Gonzalez de Dios <mailto:oscar.gonzalezdedios@telefonica.com> Author: Qin Wu <mailto:bill.wu@huawei.com>"; description "This YANG module defines a common module that is meant to be reused by various VPN-related modules (e.g., the Layer 3 VPN Service Model (L3SM), the Layer 2 VPN Service Model (L2SM), the Layer 3 VPN Network Model (L3NM), and the Layer 2 VPN Network Model (L2NM)). Copyright (c) 2022 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC 9181; see the RFC itself for full legal notices."; revision 2022-02-11 { description "Initial revision."; reference "RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs"; } /******** Collection of VPN-related features ********/ /* * Features related to encapsulation schemes */ feature dot1q { description "Indicates support for dot1Q encapsulation."; reference "IEEE Std 802.1Q: IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"; } feature qinq { description "Indicates support for QinQ encapsulation."; reference "IEEE Std 802.1ad: IEEE Standard for Local and Metropolitan Area Networks---Virtual Bridged Local Area Networks---Amendment 4: Provider Bridges"; } feature vxlan { description "Indicates support for Virtual eXtensible Local Area Network (VXLAN) encapsulation."; reference "RFC 7348: Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks"; } feature qinany { description "Indicates support for QinAny encapsulation. The outer VLAN tag is set to a specific value, but the inner VLAN tag is set to any."; } feature lag-interface { description "Indicates support for Link Aggregation Groups (LAGs) between VPN network accesses."; reference "IEEE Std 802.1AX: IEEE Standard for Local and Metropolitan Area Networks--Link Aggregation"; } /* * Features related to multicast */ feature multicast { description "Indicates support for multicast capabilities in a VPN."; reference "RFC 6513: Multicast in MPLS/BGP IP VPNs"; } feature igmp { description "Indicates support for the Internet Group Management Protocol (IGMP)."; reference "RFC 1112: Host Extensions for IP Multicasting RFC 2236: Internet Group Management Protocol, Version 2 RFC 3376: Internet Group Management Protocol, Version 3"; } feature mld { description "Indicates support for Multicast Listener Discovery (MLD)."; reference "RFC 2710: Multicast Listener Discovery (MLD) for IPv6 RFC 3810: Multicast Listener Discovery Version 2 (MLDv2) for IPv6"; } feature pim { description "Indicates support for Protocol Independent Multicast (PIM)."; reference "RFC 7761: Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"; } /* * Features related to address family types */ feature ipv4 { description "Indicates IPv4 support in a VPN. That is, IPv4 traffic can be carried in the VPN, IPv4 addresses/prefixes can be assigned to a VPN network access, IPv4 routes can be installed for the Customer Edge to Provider Edge (CE-PE) link, etc."; reference "RFC 791: Internet Protocol"; } feature ipv6 { description "Indicates IPv6 support in a VPN. That is, IPv6 traffic can be carried in the VPN, IPv6 addresses/prefixes can be assigned to a VPN network access, IPv6 routes can be installed for the CE-PE link, etc."; reference "RFC 8200: Internet Protocol, Version 6 (IPv6) Specification"; } /* * Features related to routing protocols */ feature rtg-ospf { description "Indicates support for OSPF as the Provider Edge to Customer Edge (PE-CE) routing protocol."; reference "RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol"; } feature rtg-ospf-sham-link { description "Indicates support for OSPF sham links."; reference "RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs), Section 4.2.7 RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol, Section 5"; } feature rtg-bgp { description "Indicates support for BGP as the PE-CE routing protocol."; reference "RFC 4271: A Border Gateway Protocol 4 (BGP-4)"; } feature rtg-rip { description "Indicates support for RIP as the PE-CE routing protocol."; reference "RFC 2453: RIP Version 2 RFC 2080: RIPng for IPv6"; } feature rtg-isis { description "Indicates support for IS-IS as the PE-CE routing protocol."; reference "ISO10589: Information technology - Telecommunications and information exchange between systems - Intermediate System to Intermediate System intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)"; } feature rtg-vrrp { description "Indicates support for the Virtual Router Redundancy Protocol (VRRP) in the CE-PE link."; reference "RFC 5798: Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6"; } feature bfd { description "Indicates support for Bidirectional Forwarding Detection (BFD) between the CE and the PE."; reference "RFC 5880: Bidirectional Forwarding Detection (BFD)"; } /* * Features related to VPN service constraints */ feature bearer-reference { description "A bearer refers to properties of the CE-PE attachment that are below Layer 3. This feature indicates support for the bearer reference access constraint, i.e., the reuse of a network connection that was already ordered to the service provider apart from the IP VPN site."; } feature placement-diversity { description "Indicates support for placement diversity constraints in the customer premises. An example of these constraints may be to avoid connecting a site network access to the same PE as a target site network access."; } /* * Features related to bandwidth and Quality of Service (QoS) */ feature qos { description "Indicates support for Classes of Service (CoSes) in the VPN."; } feature inbound-bw { description "Indicates support for the inbound bandwidth in a VPN, i.e., support for specifying the download bandwidth from the service provider network to the VPN site. Note that the L3SM uses 'input' to identify the same feature. That terminology should be deprecated in favor of the terminology defined in this module."; } feature outbound-bw { description "Indicates support for the outbound bandwidth in a VPN, i.e., support for specifying the upload bandwidth from the VPN site to the service provider network. Note that the L3SM uses 'output' to identify the same feature. That terminology should be deprecated in favor of the terminology defined in this module."; } /* * Features related to security and resilience */ feature encryption { description "Indicates support for encryption in the VPN."; } feature fast-reroute { description "Indicates support for Fast Reroute (FRR) capabilities for a VPN site."; } /* * Features related to advanced VPN options */ feature external-connectivity { description "Indicates support for the VPN to provide external connectivity (e.g., Internet, private or public cloud)."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), Section 11"; } feature extranet-vpn { description "Indicates support for extranet VPNs, i.e., the capability of a VPN to access a list of other VPNs."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), Section 1.1"; } feature carriers-carrier { description "Indicates support for Carriers' Carriers in VPNs."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), Section 9"; } /* * Identities related to address families */ identity address-family { description "Defines a type for the address family."; } identity ipv4 { base address-family; description "Identity for an IPv4 address family."; } identity ipv6 { base address-family; description "Identity for an IPv6 address family."; } identity dual-stack { base address-family; description "Identity for IPv4 and IPv6 address families."; } /* * Identities related to VPN topology */ identity vpn-topology { description "Base identity of the VPN topology."; } identity any-to-any { base vpn-topology; description "Identity for any-to-any VPN topology. All VPN sites can communicate with each other without any restrictions."; } identity hub-spoke { base vpn-topology; description "Identity for Hub-and-Spoke VPN topology. All Spokes can communicate with Hubs only and not with each other. Hubs can communicate with each other."; } identity hub-spoke-disjoint { base vpn-topology; description "Identity for Hub-and-Spoke VPN topology where Hubs cannot communicate with each other."; } identity custom { base vpn-topology; description "Identity for custom VPN topologies where the role of the nodes is not strictly Hub or Spoke. The VPN topology is controlled by the import/export policies. The custom topology reflects more complex VPN nodes, such as a VPN node that acts as a Hub for certain nodes and a Spoke for others."; } /* * Identities related to network access types */ identity site-network-access-type { description "Base identity for site network access types."; } identity point-to-point { base site-network-access-type; description "Point-to-point access type."; } identity multipoint { base site-network-access-type; description "Multipoint access type."; } identity irb { base site-network-access-type; description "Integrated Routing and Bridging (IRB). Identity for pseudowire connections."; } identity loopback { base site-network-access-type; description "Loopback access type."; } /* * Identities related to operational and administrative status */ identity operational-status { description "Base identity for operational status."; } identity op-up { base operational-status; description "Operational status is Up/Enabled."; } identity op-down { base operational-status; description "Operational status is Down/Disabled."; } identity op-unknown { base operational-status; description "Operational status is Unknown."; } identity administrative-status { description "Base identity for administrative status."; } identity admin-up { base administrative-status; description "Administrative status is Up/Enabled."; } identity admin-down { base administrative-status; description "Administrative status is Down/Disabled."; } identity admin-testing { base administrative-status; description "Administrative status is Up for testing purposes."; } identity admin-pre-deployment { base administrative-status; description "Administrative status reflects a pre-deployment phase, i.e., prior to the actual deployment of a service."; } /* * Identities related to site or node roles */ identity role { description "Base identity of a site or node role."; } identity any-to-any-role { base role; description "Any-to-any role."; } identity spoke-role { base role; description "A node or a site is acting as a Spoke."; } identity hub-role { base role; description "A node or a site is acting as a Hub."; } identity custom-role { base role; description "VPN node with a custom or complex role in the VPN. For some sources/destinations, it can behave as a Hub, but for others, it can act as a Spoke, depending on the configured policy."; } /* * Identities related to VPN service constraints */ identity placement-diversity { description "Base identity for access placement constraints."; } identity bearer-diverse { base placement-diversity; description "Bearer diversity. The bearers should not use common elements."; } identity pe-diverse { base placement-diversity; description "PE diversity."; } identity pop-diverse { base placement-diversity; description "Point of Presence (POP) diversity."; } identity linecard-diverse { base placement-diversity; description "Linecard diversity."; } identity same-pe { base placement-diversity; description "Having sites connected on the same PE."; } identity same-bearer { base placement-diversity; description "Having sites connected using the same bearer."; } /* * Identities related to service types */ identity service-type { description "Base identity for service types."; } identity l3vpn { base service-type; description "L3VPN service."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)"; } identity vpls { base service-type; description "Virtual Private LAN Service (VPLS)."; reference "RFC 4761: Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling RFC 4762: Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling"; } identity vpws { base service-type; description "Virtual Private Wire Service (VPWS)."; reference "RFC 4664: Framework for Layer 2 Virtual Private Networks (L2VPNs), Section 3.1.1"; } identity vpws-evpn { base service-type; description "Ethernet VPN (EVPN) used to support VPWS."; reference "RFC 8214: Virtual Private Wire Service Support in Ethernet VPN"; } identity pbb-evpn { base service-type; description "Provider Backbone Bridging (PBB) EVPN service."; reference "RFC 7623: Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)"; } identity mpls-evpn { base service-type; description "MPLS-based EVPN service."; reference "RFC 7432: BGP MPLS-Based Ethernet VPN"; } identity vxlan-evpn { base service-type; description "VXLAN-based EVPN service."; reference "RFC 8365: A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)"; } /* * Identities related to VPN signaling types */ identity vpn-signaling-type { description "Base identity for VPN signaling types."; } identity bgp-signaling { base vpn-signaling-type; description "Layer 2 VPNs using BGP signaling."; reference "RFC 6624: Layer 2 Virtual Private Networks Using BGP for Auto-Discovery and Signaling RFC 7432: BGP MPLS-Based Ethernet VPN"; } identity ldp-signaling { base vpn-signaling-type; description "Targeted Label Distribution Protocol (LDP) signaling."; reference "RFC 5036: LDP Specification"; } identity l2tp-signaling { base vpn-signaling-type; description "Layer Two Tunneling Protocol (L2TP) signaling."; reference "RFC 3931: Layer Two Tunneling Protocol - Version 3 (L2TPv3)"; } /* * Identities related to routing protocols */ identity routing-protocol-type { description "Base identity for routing protocol types."; } identity static-routing { base routing-protocol-type; description "Static routing protocol."; } identity bgp-routing { if-feature "rtg-bgp"; base routing-protocol-type; description "BGP routing protocol."; reference "RFC 4271: A Border Gateway Protocol 4 (BGP-4)"; } identity ospf-routing { if-feature "rtg-ospf"; base routing-protocol-type; description "OSPF routing protocol."; reference "RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol"; } identity rip-routing { if-feature "rtg-rip"; base routing-protocol-type; description "RIP routing protocol."; reference "RFC 2453: RIP Version 2 RFC 2080: RIPng for IPv6"; } identity isis-routing { if-feature "rtg-isis"; base routing-protocol-type; description "IS-IS routing protocol."; reference "ISO10589: Information technology - Telecommunications and information exchange between systems - Intermediate System to Intermediate System intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)"; } identity vrrp-routing { if-feature "rtg-vrrp"; base routing-protocol-type; description "VRRP protocol. This is to be used when LANs are directly connected to PEs."; reference "RFC 5798: Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6"; } identity direct-routing { base routing-protocol-type; description "Direct routing. This is to be used when LANs are directly connected to PEs and must be advertised in the VPN."; } identity any-routing { base routing-protocol-type; description "Any routing protocol. For example, this can be used to set policies that apply to any routing protocol in place."; } identity isis-level { if-feature "rtg-isis"; description "Base identity for the IS-IS level."; reference "ISO10589: Information technology - Telecommunications and information exchange between systems - Intermediate System to Intermediate System intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)"; } identity level-1 { base isis-level; description "IS-IS Level 1."; } identity level-2 { base isis-level; description "IS-IS Level 2."; } identity level-1-2 { base isis-level; description "IS-IS Levels 1 and 2."; } identity bfd-session-type { if-feature "bfd"; description "Base identity for the BFD session type."; } identity classic-bfd { base bfd-session-type; description "Classic BFD."; reference "RFC 5880: Bidirectional Forwarding Detection (BFD)"; } identity s-bfd { base bfd-session-type; description "Seamless BFD."; reference "RFC 7880: Seamless Bidirectional Forwarding Detection (S-BFD)"; } /* * Identities related to route import and export policies */ identity ie-type { description "Base identity for import/export routing profiles. These profiles can be reused between VPN nodes."; } identity import { base ie-type; description "Import routing profile."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), Section 4.3.1"; } identity export { base ie-type; description "Export routing profile."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), Section 4.3.1"; } identity import-export { base ie-type; description "Import/export routing profile."; } /* * Identities related to bandwidth and QoS */ identity bw-direction { description "Base identity for the bandwidth direction."; } identity inbound-bw { if-feature "inbound-bw"; base bw-direction; description "Inbound bandwidth."; } identity outbound-bw { if-feature "outbound-bw"; base bw-direction; description "Outbound bandwidth."; } identity bw-type { description "Base identity for the bandwidth type."; } identity bw-per-cos { if-feature "qos"; base bw-type; description "The bandwidth is per CoS."; } identity bw-per-port { base bw-type; description "The bandwidth is per a given site network access."; } identity bw-per-site { base bw-type; description "The bandwidth is per site. It is applicable to all the site network accesses within a site."; } identity bw-per-service { base bw-type; description "The bandwidth is per VPN service."; } identity qos-profile-direction { if-feature "qos"; description "Base identity for the QoS profile direction."; } identity site-to-wan { base qos-profile-direction; description "From the customer site to the provider's network. This is typically the CE-to-PE direction."; } identity wan-to-site { base qos-profile-direction; description "From the provider's network to the customer site. This is typically the PE-to-CE direction."; } identity both { base qos-profile-direction; description "Both the WAN-to-site direction and the site-to-WAN direction."; } /* * Identities related to underlay transport instances */ identity transport-instance-type { description "Base identity for underlay transport instance types."; } identity virtual-network { base transport-instance-type; description "Virtual network."; reference "RFC 8453: Framework for Abstraction and Control of TE Networks (ACTN)"; } identity enhanced-vpn { base transport-instance-type; description "Enhanced VPN (VPN+). VPN+ is an approach that is based on existing VPN and Traffic Engineering (TE) technologies but adds characteristics that specific services require over and above classical VPNs."; reference "draft-ietf-teas-enhanced-vpn-09: A Framework for Enhanced Virtual Private Network (VPN+) Services"; } identity ietf-network-slice { base transport-instance-type; description "IETF network slice. An IETF network slice is a logical network topology connecting a number of endpoints using a set of shared or dedicated network resources that are used to satisfy specific service objectives."; reference "draft-ietf-teas-ietf-network-slices-05: Framework for IETF Network Slices"; } /* * Identities related to protocol types. These types are * typically used to identify the underlay transport. */ identity protocol-type { description "Base identity for protocol types."; } identity ip-in-ip { base protocol-type; description "Transport is based on IP in IP."; reference "RFC 2003: IP Encapsulation within IP RFC 2473: Generic Packet Tunneling in IPv6 Specification"; } identity ip-in-ipv4 { base ip-in-ip; description "Transport is based on IP over IPv4."; reference "RFC 2003: IP Encapsulation within IP"; } identity ip-in-ipv6 { base ip-in-ip; description "Transport is based on IP over IPv6."; reference "RFC 2473: Generic Packet Tunneling in IPv6 Specification"; } identity gre { base protocol-type; description "Transport is based on Generic Routing Encapsulation (GRE)."; reference "RFC 1701: Generic Routing Encapsulation (GRE) RFC 1702: Generic Routing Encapsulation over IPv4 networks RFC 7676: IPv6 Support for Generic Routing Encapsulation (GRE)"; } identity gre-v4 { base gre; description "Transport is based on GRE over IPv4."; reference "RFC 1702: Generic Routing Encapsulation over IPv4 networks"; } identity gre-v6 { base gre; description "Transport is based on GRE over IPv6."; reference "RFC 7676: IPv6 Support for Generic Routing Encapsulation (GRE)"; } identity vxlan-trans { base protocol-type; description "Transport is based on VXLANs."; reference "RFC 7348: Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks"; } identity geneve { base protocol-type; description "Transport is based on Generic Network Virtualization Encapsulation (Geneve)."; reference "RFC 8926: Geneve: Generic Network Virtualization Encapsulation"; } identity ldp { base protocol-type; description "Transport is based on LDP."; reference "RFC 5036: LDP Specification"; } identity mpls-in-udp { base protocol-type; description "Transport is based on MPLS in UDP."; reference "RFC 7510: Encapsulating MPLS in UDP"; } identity sr { base protocol-type; description "Transport is based on Segment Routing (SR)."; reference "RFC 8660: Segment Routing with the MPLS Data Plane RFC 8663: MPLS Segment Routing over IP RFC 8754: IPv6 Segment Routing Header (SRH)"; } identity sr-mpls { base sr; description "Transport is based on SR with the MPLS data plane."; reference "RFC 8660: Segment Routing with the MPLS Data Plane"; } identity srv6 { base sr; description "Transport is based on SR over IPv6."; reference "RFC 8754: IPv6 Segment Routing Header (SRH)"; } identity sr-mpls-over-ip { base sr; description "Transport is based on SR over MPLS over IP."; reference "RFC 8663: MPLS Segment Routing over IP"; } identity rsvp-te { base protocol-type; description "Transport setup relies upon RSVP-TE."; reference "RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels"; } identity bgp-lu { base protocol-type; description "Transport setup relies upon BGP-based labeled prefixes."; reference "RFC 8277: Using BGP to Bind MPLS Labels to Address Prefixes"; } identity unknown { base protocol-type; description "Unknown protocol type."; } /* * Identities related to encapsulation types */ identity encapsulation-type { description "Base identity for encapsulation types."; } identity priority-tagged { base encapsulation-type; description "Priority-tagged interface."; } identity dot1q { if-feature "dot1q"; base encapsulation-type; description "dot1Q encapsulation."; } identity qinq { if-feature "qinq"; base encapsulation-type; description "QinQ encapsulation."; } identity qinany { if-feature "qinany"; base encapsulation-type; description "QinAny encapsulation."; } identity vxlan { if-feature "vxlan"; base encapsulation-type; description "VXLAN encapsulation."; } identity ethernet-type { base encapsulation-type; description "Ethernet encapsulation type."; } identity vlan-type { base encapsulation-type; description "VLAN encapsulation type."; } identity untagged-int { base encapsulation-type; description "Untagged interface type."; } identity tagged-int { base encapsulation-type; description "Tagged interface type."; } identity lag-int { if-feature "lag-interface"; base encapsulation-type; description "LAG interface type."; } /* * Identities related to VLAN tags */ identity tag-type { description "Base identity for VLAN tag types."; } identity c-vlan { base tag-type; description "Indicates a Customer VLAN (C-VLAN) tag, normally using the 0x8100 Ethertype."; } identity s-vlan { base tag-type; description "Indicates a Service VLAN (S-VLAN) tag."; } identity s-c-vlan { base tag-type; description "Uses both an S-VLAN tag and a C-VLAN tag."; } /* * Identities related to VXLANs */ identity vxlan-peer-mode { if-feature "vxlan"; description "Base identity for VXLAN peer modes."; } identity static-mode { base vxlan-peer-mode; description "VXLAN access in the static mode."; } identity bgp-mode { base vxlan-peer-mode; description "VXLAN access by BGP EVPN learning."; } /* * Identities related to multicast */ identity multicast-gp-address-mapping { if-feature "multicast"; description "Base identity for multicast group mapping types."; } identity static-mapping { base multicast-gp-address-mapping; description "Static mapping, i.e., an interface is attached to the multicast group as a static member."; } identity dynamic-mapping { base multicast-gp-address-mapping; description "Dynamic mapping, i.e., an interface is added to the multicast group as a result of snooping."; } identity multicast-tree-type { if-feature "multicast"; description "Base identity for multicast tree types."; } identity ssm-tree-type { base multicast-tree-type; description "Source-Specific Multicast (SSM) tree type."; } identity asm-tree-type { base multicast-tree-type; description "Any-Source Multicast (ASM) tree type."; } identity bidir-tree-type { base multicast-tree-type; description "Bidirectional tree type."; } identity multicast-rp-discovery-type { if-feature "multicast"; description "Base identity for Rendezvous Point (RP) discovery types."; } identity auto-rp { base multicast-rp-discovery-type; description "Auto-RP discovery type."; } identity static-rp { base multicast-rp-discovery-type; description "Static type."; } identity bsr-rp { base multicast-rp-discovery-type; description "Bootstrap Router (BSR) discovery type."; } identity group-management-protocol { if-feature "multicast"; description "Base identity for multicast group management protocols."; } identity igmp-proto { base group-management-protocol; description "IGMP."; reference "RFC 1112: Host Extensions for IP Multicasting RFC 2236: Internet Group Management Protocol, Version 2 RFC 3376: Internet Group Management Protocol, Version 3"; } identity mld-proto { base group-management-protocol; description "MLD."; reference "RFC 2710: Multicast Listener Discovery (MLD) for IPv6 RFC 3810: Multicast Listener Discovery Version 2 (MLDv2) for IPv6"; } identity pim-proto { if-feature "pim"; base routing-protocol-type; description "PIM."; reference "RFC 7761: Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"; } identity igmp-version { if-feature "igmp"; description "Base identity for indicating the IGMP version."; } identity igmpv1 { base igmp-version; description "IGMPv1."; reference "RFC 1112: Host Extensions for IP Multicasting"; } identity igmpv2 { base igmp-version; description "IGMPv2."; reference "RFC 2236: Internet Group Management Protocol, Version 2"; } identity igmpv3 { base igmp-version; description "IGMPv3."; reference "RFC 3376: Internet Group Management Protocol, Version 3"; } identity mld-version { if-feature "mld"; description "Base identity for indicating the MLD version."; } identity mldv1 { base mld-version; description "MLDv1."; reference "RFC 2710: Multicast Listener Discovery (MLD) for IPv6"; } identity mldv2 { base mld-version; description "MLDv2."; reference "RFC 3810: Multicast Listener Discovery Version 2 (MLDv2) for IPv6"; } /* * Identities related to traffic types */ identity tf-type { description "Base identity for traffic types."; } identity multicast-traffic { base tf-type; description "Multicast traffic."; } identity broadcast-traffic { base tf-type; description "Broadcast traffic."; } identity unknown-unicast-traffic { base tf-type; description "Unknown unicast traffic."; } /* * Identities related to customer applications */ identity customer-application { description "Base identity for customer applications."; } identity web { base customer-application; description "Web applications (e.g., HTTP, HTTPS)."; } identity mail { base customer-application; description "Mail application."; } identity file-transfer { base customer-application; description "File transfer application (e.g., FTP, Secure FTP (SFTP))."; } identity database { base customer-application; description "Database application."; } identity social { base customer-application; description "Social-network application."; } identity games { base customer-application; description "Gaming application."; } identity p2p { base customer-application; description "Peer-to-peer application."; } identity network-management { base customer-application; description "Management application (e.g., Telnet, syslog, SNMP)."; } identity voice { base customer-application; description "Voice application."; } identity video { base customer-application; description "Video-conference application."; } identity embb { base customer-application; description "Enhanced Mobile Broadband (eMBB) application. Note that eMBB applications demand network performance with a wide variety of such characteristics as data rate, latency, loss rate, reliability, and many other parameters."; } identity urllc { base customer-application; description "Ultra-Reliable and Low Latency Communications (URLLC) application. Note that URLLC applications demand network performance with a wide variety of such characteristics as latency, reliability, and many other parameters."; } identity mmtc { base customer-application; description "Massive Machine Type Communications (mMTC) application. Note that mMTC applications demand network performance with a wide variety of such characteristics as data rate, latency, loss rate, reliability, and many other parameters."; } /* * Identities related to service bundling */ identity bundling-type { description "The base identity for the bundling type. It supports a subset or all Customer Edge VLAN IDs (CE-VLAN IDs) associated with an L2VPN service."; } identity multi-svc-bundling { base bundling-type; description "Multi-service bundling, i.e., multiple CE-VLAN IDs can be associated with an L2VPN service at a site."; } identity one2one-bundling { base bundling-type; description "One-to-one service bundling, i.e., each L2VPN can be associated with only one CE-VLAN ID at a site."; } identity all2one-bundling { base bundling-type; description "All-to-one bundling, i.e., all CE-VLAN IDs are mapped to one L2VPN service."; } /* * Identities related to Ethernet services */ identity control-mode { description "Base identity for the type of control mode used with the Layer 2 Control Protocol (L2CP)."; } identity peer { base control-mode; description "'peer' mode, i.e., participate in the protocol towards the CE. Peering is common for the Link Aggregation Control Protocol (LACP) and the Ethernet Local Management Interface (E-LMI) and, occasionally, for the Link Layer Discovery Protocol (LLDP). For VPLSs and VPWSs, the subscriber can also request that the peer service provider enable spanning tree."; } identity tunnel { base control-mode; description "'tunnel' mode, i.e., pass to the egress or destination site. For Ethernet Private Lines (EPLs), the expectation is that L2CP frames are tunneled."; } identity discard { base control-mode; description "'Discard' mode, i.e., discard the frame."; } identity neg-mode { description "Base identity for the type of negotiation mode."; } identity full-duplex { base neg-mode; description "Full-duplex negotiation mode."; } identity auto-neg { base neg-mode; description "Auto-negotiation mode."; } /******** VPN-related type ********/ typedef vpn-id { type string; description "Defines an identifier that is used with a VPN module. For example, this can be a service identifier, a node identifier, etc."; } /******* VPN-related reusable groupings *******/ grouping vpn-description { description "Provides common VPN information."; leaf vpn-id { type vpn-common:vpn-id; description "A VPN identifier that uniquely identifies a VPN. This identifier has a local meaning, e.g., within a service provider network."; } leaf vpn-name { type string; description "Used to associate a name with the service in order to facilitate the identification of the service."; } leaf vpn-description { type string; description "Textual description of a VPN."; } leaf customer-name { type string; description "Name of the customer that actually uses the VPN."; } } grouping vpn-profile-cfg { description "Grouping for VPN profile configuration."; container valid-provider-identifiers { description "Container for valid provider profile identifiers."; list external-connectivity-identifier { if-feature "external-connectivity"; key "id"; description "List of profile identifiers that uniquely identify profiles governing how external connectivity is provided to a VPN. A profile indicates the type of external connectivity (Internet, cloud, etc.), the sites/nodes that are associated with a connectivity profile, etc. A profile can also indicate filtering rules and/or address translation rules. Such features may involve PE, P, or dedicated nodes as a function of the deployment."; leaf id { type string; description "Identification of an external connectivity profile. The profile only has significance within the service provider's administrative domain."; } } list encryption-profile-identifier { key "id"; description "List of encryption profile identifiers."; leaf id { type string; description "Identification of the encryption profile to be used. The profile only has significance within the service provider's administrative domain."; } } list qos-profile-identifier { key "id"; description "List of QoS profile identifiers."; leaf id { type string; description "Identification of the QoS profile to be used. The profile only has significance within the service provider's administrative domain."; } } list bfd-profile-identifier { key "id"; description "List of BFD profile identifiers."; leaf id { type string; description "Identification of the BFD profile to be used. The profile only has significance within the service provider's administrative domain."; } } list forwarding-profile-identifier { key "id"; description "List of forwarding profile identifiers."; leaf id { type string; description "Identification of the forwarding profile to be used. The profile only has significance within the service provider's administrative domain."; } } list routing-profile-identifier { key "id"; description "List of routing profile identifiers."; leaf id { type string; description "Identification of the routing profile to be used by the routing protocols within sites, VPN network accesses, or VPN nodes for referring to VRF's import/export policies. The profile only has significance within the service provider's administrative domain."; } } nacm:default-deny-write; } } grouping oper-status-timestamp { description "This grouping defines some operational parameters for the service."; leaf status { type identityref { base operational-status; } config false; description "Operational status."; } leaf last-change { type yang:date-and-time; config false; description "Indicates the actual date and time of the service status change."; } } grouping service-status { description "Service status grouping."; container status { description "Service status."; container admin-status { description "Administrative service status."; leaf status { type identityref { base administrative-status; } description "Administrative service status."; } leaf last-change { type yang:date-and-time; description "Indicates the actual date and time of the service status change."; } } container oper-status { config false; description "Operational service status."; uses oper-status-timestamp; } } } grouping underlay-transport { description "This grouping defines the type of underlay transport for the VPN service or how that underlay is set. It can include an identifier for an abstract transport instance to which the VPN is grafted or indicate a technical implementation that is expressed as an ordered list of protocols."; choice type { description "A choice based on the type of underlay transport constraints."; case abstract { description "Indicates that the transport constraint is an abstract concept."; leaf transport-instance-id { type string; description "An optional identifier of the abstract transport instance."; } leaf instance-type { type identityref { base transport-instance-type; } description "Indicates a transport instance type. For example, it can be a VPN+, an IETF network slice, a virtual network, etc."; } } case protocol { description "Indicates a list of protocols."; leaf-list protocol { type identityref { base protocol-type; } ordered-by user; description "A client-ordered list of transport protocols."; } } } } grouping vpn-route-targets { description "A grouping that specifies Route Target (RT) import/export rules used in a BGP-enabled VPN."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs) RFC 4664: Framework for Layer 2 Virtual Private Networks (L2VPNs)"; list vpn-target { key "id"; description "RTs. AND/OR operations may be defined based on the assigned RTs."; leaf id { type uint8; description "Identifies each VPN target."; } list route-targets { key "route-target"; description "List of RTs."; leaf route-target { type rt-types:route-target; description "Conveys an RT value."; } } leaf route-target-type { type rt-types:route-target-type; mandatory true; description "Import/export type of the RT."; } } container vpn-policies { description "VPN service policies. 'vpn-policies' contains references to the import and export policies to be associated with the VPN service."; leaf import-policy { type string; description "Identifies the import policy."; } leaf export-policy { type string; description "Identifies the export policy."; } } } grouping route-distinguisher { description "Grouping for Route Distinguishers (RDs)."; choice rd-choice { description "RD choice between several options for providing the RD value."; case directly-assigned { description "Explicitly assigns an RD value."; leaf rd { type rt-types:route-distinguisher; description "Indicates an RD value that is explicitly assigned."; } } case directly-assigned-suffix { description "The value of the Assigned Number subfield of the RD. The Administrator subfield of the RD will be based on other configuration information such as the Router ID or Autonomous System Number (ASN)."; leaf rd-suffix { type uint16; description "Indicates the value of the Assigned Number subfield that is explicitly assigned."; } } case auto-assigned { description "The RD is auto-assigned."; container rd-auto { description "The RD is auto-assigned."; choice auto-mode { description "Indicates the auto-assignment mode. The RD can be automatically assigned with or without indicating a pool from which the RD should be taken. For both cases, the server will auto-assign an RD value 'auto-assigned-rd' and use that value operationally."; case from-pool { leaf rd-pool-name { type string; description "The auto-assignment will be made from the pool identified by 'rd-pool-name'."; } } case full-auto { leaf auto { type empty; description "Indicates that an RD is fully auto-assigned."; } } } leaf auto-assigned-rd { type rt-types:route-distinguisher; config false; description "The value of the auto-assigned RD."; } } } case auto-assigned-suffix { description "The value of the Assigned Number subfield will be auto-assigned. The Administrator subfield will be based on other configuration information such as the Router ID or ASN."; container rd-auto-suffix { description "The Assigned Number subfield is auto-assigned."; choice auto-mode { description "Indicates the auto-assignment mode of the Assigned Number subfield. This number can be automatically assigned with or without indicating a pool from which the value should be taken. For both cases, the server will auto-assign 'auto-assigned-rd-suffix' and use that value to build the RD that will be used operationally."; case from-pool { leaf rd-pool-name { type string; description "The assignment will be made from the pool identified by 'rd-pool-name'."; } } case full-auto { leaf auto { type empty; description "Indicates that the Assigned Number subfield is fully auto-assigned."; } } } leaf auto-assigned-rd-suffix { type uint16; config false; description "Includes the value of the Assigned Number subfield that is auto-assigned."; } } } case no-rd { description "Uses the 'empty' type to indicate that the RD has no value and is not to be auto-assigned."; leaf no-rd { type empty; description "No RD is assigned."; } } } } grouping vpn-components-group { description "Grouping definition to assign group IDs to associate VPN nodes, sites, or network accesses."; container groups { description "Lists the groups to which a VPN node, a site, or a network access belongs."; list group { key "group-id"; description "List of group IDs."; leaf group-id { type string; description "The group ID to which a VPN node, a site, or a network access belongs."; } } } } grouping placement-constraints { description "Constraints related to placement of a network access."; list constraint { key "constraint-type"; description "List of constraints."; leaf constraint-type { type identityref { base placement-diversity; } description "Diversity constraint type."; } container target { description "The constraint will apply against this list of groups."; choice target-flavor { description "Choice for the group definition."; case id { list group { key "group-id"; description "List of groups."; leaf group-id { type string; description "The constraint will apply against this particular group ID."; } } } case all-accesses { leaf all-other-accesses { type empty; description "The constraint will apply against all other network accesses of a site."; } } case all-groups { leaf all-other-groups { type empty; description "The constraint will apply against all other groups managed by the customer."; } } } } } } grouping ports { description "Choice of specifying source or destination port numbers."; choice source-port { description "Choice of specifying the source port or referring to a group of source port numbers."; container source-port-range-or-operator { description "Source port definition."; uses packet-fields:port-range-or-operator; } } choice destination-port { description "Choice of specifying a destination port or referring to a group of destination port numbers."; container destination-port-range-or-operator { description "Destination port definition."; uses packet-fields:port-range-or-operator; } } } grouping qos-classification-policy { description "Configuration of the traffic classification policy."; list rule { key "id"; ordered-by user; description "List of marking rules."; leaf id { type string; description "An identifier of the QoS classification policy rule."; } choice match-type { default "match-flow"; description "Choice for classification."; case match-flow { choice l3 { description "Either IPv4 or IPv6."; container ipv4 { description "Rule set that matches the IPv4 header."; uses packet-fields:acl-ip-header-fields; uses packet-fields:acl-ipv4-header-fields; } container ipv6 { description "Rule set that matches the IPv6 header."; uses packet-fields:acl-ip-header-fields; uses packet-fields:acl-ipv6-header-fields; } } choice l4 { description "Includes Layer-4-specific information. This version focuses on TCP and UDP."; container tcp { description "Rule set that matches the TCP header."; uses packet-fields:acl-tcp-header-fields; uses ports; } container udp { description "Rule set that matches the UDP header."; uses packet-fields:acl-udp-header-fields; uses ports; } } } case match-application { leaf match-application { type identityref { base customer-application; } description "Defines the application to match."; } } } leaf target-class-id { type string; description "Identification of the class of service. This identifier is internal to the administration."; } } } }

Security Considerations The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. The "ietf-vpn-common" module defines a set of identities, types, and groupings. These nodes are intended to be reused by other YANG modules. The module by itself does not expose any data nodes that are writable, data nodes that contain read-only state, or RPCs. As such, there are no additional security issues related to the "ietf-vpn-common" module that need to be considered. Modules that use the groupings that are defined in this document should identify the corresponding security considerations. For example, reusing some of these groupings will expose privacy-related information (e.g., 'customer-name'). Disclosing such information may be considered a violation of the customer-provider trust relationship.

IANA Considerations IANA has registered the following URI in the "ns" subregistry within the "IETF XML Registry" :

URI:

urn:ietf:params:xml:ns:yang:ietf-vpn-common

Registrant Contact:

The IESG.

XML:

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

IANA has registered the following YANG module in the "YANG Module Names" subregistry within the "YANG Parameters" registry.

Name:

ietf-vpn-common

Namespace:

urn:ietf:params:xml:ns:yang:ietf-vpn-common

Maintained by IANA?

N

Prefix:

vpn-common

Reference:

RFC 9181

References Normative References This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK] YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). This document defines a collection of common data types using the YANG data modeling language. These derived common types are designed to be imported by other modules defined in the routing area. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document obsoletes RFC 6536. This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. This document defines a data model for Access Control Lists (ACLs). An ACL is a user-ordered set of rules used to configure the forwarding behavior in a device. Each rule is used to find a match on a packet and define actions that will be performed on the packet. Informative References Work in Progress Huawei University of Surrey China Mobile KDDI Corporation Samsung This document describes the framework for Enhanced Virtual Private Network (VPN+) services. The purpose of enhanced VPNs is to support the needs of new applications, particularly applications that are associated with 5G services, by utilizing an approach that is based on existing VPN and Traffic Engineering (TE) technologies and adds characteristics that specific services require over those provided by traditional VPNs. Typically, VPN+ will be used to underpin network slicing, but could also be of use in its own right providing enhanced connectivity services between customer sites. It is envisaged that enhanced VPNs will be delivered using a combination of existing, modified, and new networking technologies. This document provides an overview of relevant technologies and identifies some areas for potential new work. Work in Progress IEEE IEEE IEEE ISO International Standard 10589:2002, Second Edition Work in Progress Work in Progress This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Recommended procedure for IP multicasting in the Internet. This RFC obsoletes RFCs 998 and 1054. [STANDARDS-TRACK] This document specifies a protocol for performing encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. This memo addresses the case of using IP as the delivery protocol or the payload protocol and the special case of IP as both the delivery and payload. This memo also describes using IP addresses and autonomous system numbers as part of a GRE source route. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram. [STANDARDS-TRACK] This document specifies a routing protocol for an IPv6 internet. It is based on protocols and algorithms currently in wide use in the IPv4 Internet [STANDARDS-TRACK] This memo documents IGMPv2, used by IP hosts to report their multicast group memberships to routers. It updates STD 5, RFC 1112. [STANDARDS-TRACK] This document specifies an extension of the Routing Information Protocol (RIP) to expand the amount of useful information carried in RIP messages and to add a measure of security. [STANDARDS-TRACK] This document defines the model and generic mechanisms for IPv6 encapsulation of Internet packets, such as IPv6 and IPv4. [STANDARDS-TRACK] This document specifies the protocol used by an IPv6 router to discover the presence of multicast listeners (that is, nodes wishing to receive multicast packets) on its directly attached links, and to discover specifically which multicast addresses are of interest to those neighboring nodes. [STANDARDS-TRACK] This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels. A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702. [STANDARDS-TRACK] This document updates RFC 2710, and it specifies Version 2 of the ulticast Listener Discovery Protocol (MLDv2). MLD is used by an IPv6 router to discover the presence of multicast listeners on directly attached links, and to discover which multicast addresses are of interest to those neighboring nodes. MLDv2 is designed to be interoperable with MLDv1. MLDv2 adds the ability for a node to report interest in listening to packets with a particular multicast address only from specific source addresses or from all sources except for specific source addresses. [STANDARDS-TRACK] This document describes "version 3" of the Layer Two Tunneling Protocol (L2TPv3). L2TPv3 defines the base control protocol and encapsulation for tunneling multiple Layer 2 connections between two IP nodes. Additional documents detail the specifics for each data link type being emulated. [STANDARDS-TRACK] The widespread interest in provider-provisioned Virtual Private Network (VPN) solutions lead to memos proposing different and overlapping solutions. The IETF working groups (first Provider Provisioned VPNs and later Layer 2 VPNs and Layer 3 VPNs) have discussed these proposals and documented specifications. This has lead to the development of a partially new set of concepts used to describe the set of VPN services. To a certain extent, more than one term covers the same concept, and sometimes the same term covers more than one concept. This document seeks to make the terminology in the area clearer and more intuitive. This memo provides information for the Internet community. This document provides a framework for the operation and management of Layer 3 Virtual Private Networks (L3VPNs). This framework intends to produce a coherent description of the significant technical issues that are important in the design of L3VPN management solutions. The selection of specific approaches, and making choices among information models and protocols are outside the scope of this document. This memo provides information for the Internet community. This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol. The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced. BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths. This document obsoletes RFC 1771. [STANDARDS-TRACK] Many Service Providers offer Virtual Private Network (VPN) services to their customers, using a technique in which customer edge routers (CE routers) are routing peers of provider edge routers (PE routers). The Border Gateway Protocol (BGP) is used to distribute the customer's routes across the provider's IP backbone network, and Multiprotocol Label Switching (MPLS) is used to tunnel customer packets across the provider's backbone. This is known as a "BGP/MPLS IP VPN". The base specification for BGP/MPLS IP VPNs presumes that the routing protocol on the interface between a PE router and a CE router is BGP. This document extends that specification by allowing the routing protocol on the PE/CE interface to be the Open Shortest Path First (OSPF) protocol. This document updates RFC 4364. [STANDARDS-TRACK] This document provides a framework for Layer 2 Provider Provisioned Virtual Private Networks (L2VPNs). This framework is intended to aid in standardizing protocols and mechanisms to support interoperable L2VPNs. This memo provides information for the Internet community. Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature. This document describes the functions required to offer VPLS, a mechanism for signaling a VPLS, and rules for forwarding VPLS frames across a packet switched network. [STANDARDS-TRACK] This document describes a Virtual Private LAN Service (VPLS) solution using pseudowires, a service previously implemented over other tunneling technologies and known as Transparent LAN Services (TLS). A VPLS creates an emulated LAN segment for a given set of users; i.e., it creates a Layer 2 broadcast domain that is fully capable of learning and forwarding on Ethernet MAC addresses and that is closed to a given set of users. Multiple VPLS services can be supported from a single Provider Edge (PE) node. This document describes the control plane functions of signaling pseudowire labels using Label Distribution Protocol (LDP), extending RFC 4447. It is agnostic to discovery protocols. The data plane functions of forwarding are also described, focusing in particular on the learning of MAC addresses. The encapsulation of VPLS packets is described by RFC 4448. [STANDARDS-TRACK] This document obsoletes RFC 2960 and RFC 3309. It describes the Stream Control Transmission Protocol (SCTP). SCTP is designed to transport Public Switched Telephone Network (PSTN) signaling messages over IP networks, but is capable of broader applications. SCTP is a reliable transport protocol operating on top of a connectionless packet network such as IP. It offers the following services to its users: -- acknowledged error-free non-duplicated transfer of user data, -- data fragmentation to conform to discovered path MTU size, -- sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages, -- optional bundling of multiple user messages into a single SCTP packet, and -- network-level fault tolerance through supporting of multi-homing at either or both ends of an association. The design of SCTP includes appropriate congestion avoidance behavior and resistance to flooding and masquerade attacks. [STANDARDS-TRACK] The architecture for Multiprotocol Label Switching (MPLS) is described in RFC 3031. A fundamental concept in MPLS is that two Label Switching Routers (LSRs) must agree on the meaning of the labels used to forward traffic between and through them. This common understanding is achieved by using a set of procedures, called a label distribution protocol, by which one LSR informs another of label bindings it has made. This document defines a set of such procedures called LDP (for Label Distribution Protocol) by which LSRs distribute labels to support MPLS forwarding along normally routed paths. [STANDARDS-TRACK] This memo defines the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It is version three (3) of the protocol, and it is based on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in "Virtual Router Redundancy Protocol for IPv6". VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IPv4 or IPv6 address(es) associated with a virtual router is called the Master, and it forwards packets sent to these IPv4 or IPv6 addresses. VRRP Master routers are configured with virtual IPv4 or IPv6 addresses, and VRRP Backup routers infer the address family of the virtual addresses being carried based on the transport protocol. Within a VRRP router, the virtual routers in each of the IPv4 and IPv6 address families are a domain unto themselves and do not overlap. The election process provides dynamic failover in the forwarding responsibility should the Master become unavailable. For IPv4, the advantage gained from using VRRP is a higher-availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. For IPv6, the advantage gained from using VRRP for IPv6 is a quicker switchover to Backup routers than can be obtained with standard IPv6 Neighbor Discovery mechanisms. [STANDARDS-TRACK] This document describes a protocol intended to detect faults in the bidirectional path between two forwarding engines, including interfaces, data link(s), and to the extent possible the forwarding engines themselves, with potentially very low latency. It operates independently of media, data protocols, and routing protocols. [STANDARDS-TRACK] In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual Private Network) to travel from one VPN site to another, special protocols and procedures must be implemented by the VPN Service Provider. These protocols and procedures are specified in this document. [STANDARDS-TRACK] Many Service Providers (SPs) offer Virtual Private Network (VPN) services to their customers using a technique in which Customer Edge (CE) routers are routing peers of Provider Edge (PE) routers. The Border Gateway Protocol (BGP) is used to distribute the customer's routes across the provider's IP backbone network, and Multiprotocol Label Switching (MPLS) is used to tunnel customer packets across the provider's backbone. Support currently exists for both IPv4 and IPv6 VPNs; however, only Open Shortest Path First version 2 (OSPFv2) as PE-CE protocol is specified. This document extends those specifications to support OSPF version 3 (OSPFv3) as a PE-CE routing protocol. The OSPFv3 PE-CE functionality is identical to that of OSPFv2 except for the differences described in this document. [STANDARDS-TRACK] Layer 2 Virtual Private Networks (L2VPNs) based on Frame Relay or ATM circuits have been around a long time; more recently, Ethernet VPNs, including Virtual Private LAN Service, have become popular. Traditional L2VPNs often required a separate Service Provider infrastructure for each type and yet another for the Internet and IP VPNs. In addition, L2VPN provisioning was cumbersome. This document presents a new approach to the problem of offering L2VPN services where the L2VPN customer's experience is virtually identical to that offered by traditional L2VPNs, but such that a Service Provider can maintain a single network for L2VPNs, IP VPNs, and the Internet, as well as a common provisioning methodology for all services. This document is not an Internet Standards Track specification; it is published for informational purposes. This document describes Virtual eXtensible Local Area Network (VXLAN), which is used to address the need for overlay networks within virtualized data centers accommodating multiple tenants. The scheme and the related protocols can be used in networks for cloud service providers and enterprise data centers. This memo documents the deployed VXLAN protocol for the benefit of the Internet community. This document describes procedures for BGP MPLS-based Ethernet VPNs (EVPN). The procedures described here meet the requirements specified in RFC 7209 -- "Requirements for Ethernet VPN (EVPN)". This document specifies an IP-based encapsulation for MPLS, called MPLS-in-UDP for situations where UDP (User Datagram Protocol) encapsulation is preferred to direct use of MPLS, e.g., to enable UDP-based ECMP (Equal-Cost Multipath) or link aggregation. The MPLS- in-UDP encapsulation technology must only be deployed within a single network (with a single network operator) or networks of an adjacent set of cooperating network operators where traffic is managed to avoid congestion, rather than over the Internet where congestion control is required. Usage restrictions apply to MPLS-in-UDP usage for traffic that is not congestion controlled and to UDP zero checksum usage with IPv6. This document discusses how Ethernet Provider Backbone Bridging (PBB) can be combined with Ethernet VPN (EVPN) in order to reduce the number of BGP MAC Advertisement routes by aggregating Customer/Client MAC (C-MAC) addresses via Provider Backbone MAC (B-MAC) address, provide client MAC address mobility using C-MAC aggregation, confine the scope of C-MAC learning to only active flows, offer per-site policies, and avoid C-MAC address flushing on topology changes. The combined solution is referred to as PBB-EVPN. Generic Routing Encapsulation (GRE) can be used to carry any network- layer payload protocol over any network-layer delivery protocol. Currently, GRE procedures are specified for IPv4, used as either the payload or delivery protocol. However, GRE procedures are not specified for IPv6. This document specifies GRE procedures for IPv6, used as either the payload or delivery protocol. This document specifies Protocol Independent Multicast - Sparse Mode (PIM-SM). PIM-SM is a multicast routing protocol that can use the underlying unicast routing information base or a separate multicast-capable routing information base. It builds unidirectional shared trees rooted at a Rendezvous Point (RP) per group, and it optionally creates shortest-path trees per source. This document obsoletes RFC 4601 by replacing it, addresses the errata filed against it, removes the optional (*,*,RP), PIM Multicast Border Router features and authentication using IPsec that lack sufficient deployment experience (see Appendix A), and moves the PIM specification to Internet Standard. This document defines Seamless Bidirectional Forwarding Detection (S-BFD), a simplified mechanism for using BFD with a large proportion of negotiation aspects eliminated, thus providing benefits such as quick provisioning, as well as improved control and flexibility for network nodes initiating path monitoring. This document updates RFC 5880. This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460. This document describes how Ethernet VPN (EVPN) can be used to support the Virtual Private Wire Service (VPWS) in MPLS/IP networks. EVPN accomplishes the following for VPWS: provides Single-Active as well as All-Active multihoming with flow-based load-balancing, eliminates the need for Pseudowire (PW) signaling, and provides fast protection convergence upon node or link failure. This document specifies a set of procedures for using BGP to advertise that a specified router has bound a specified MPLS label (or a specified sequence of MPLS labels organized as a contiguous part of a label stack) to a specified address prefix. This can be done by sending a BGP UPDATE message whose Network Layer Reachability Information field contains both the prefix and the MPLS label(s) and whose Next Hop field identifies the node at which said prefix is bound to said label(s). This document obsoletes RFC 3107. This document defines a YANG data model that can be used for communication between customers and network operators and to deliver a Layer 3 provider-provisioned VPN service. This document is limited to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364. This model is intended to be instantiated at the management system to deliver the overall service. It is not a configuration model to be used directly on network elements. This model provides an abstracted view of the Layer 3 IP VPN service configuration components. It will be up to the management system to take this model as input and use specific configuration models to configure the different network elements to deliver the service. How the configuration of network elements is done is out of scope for this document. This document obsoletes RFC 8049; it replaces the unimplementable module in that RFC with a new module with the same name that is not backward compatible. The changes are a series of small fixes to the YANG module and some clarifications to the text. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. This document specifies how Ethernet VPN (EVPN) can be used as a Network Virtualization Overlay (NVO) solution and explores the various tunnel encapsulation options over IP and their impact on the EVPN control plane and procedures. In particular, the following encapsulation options are analyzed: Virtual Extensible LAN (VXLAN), Network Virtualization using Generic Routing Encapsulation (NVGRE), and MPLS over GRE. This specification is also applicable to Generic Network Virtualization Encapsulation (GENEVE); however, some incremental work is required, which will be covered in a separate document. This document also specifies new multihoming procedures for split-horizon filtering and mass withdrawal. It also specifies EVPN route constructions for VXLAN/NVGRE encapsulations and Autonomous System Border Router (ASBR) procedures for multihoming of Network Virtualization Edge (NVE) devices. Traffic Engineered (TE) networks have a variety of mechanisms to facilitate the separation of the data plane and control plane. They also have a range of management and provisioning protocols to configure and activate network resources. These mechanisms represent key technologies for enabling flexible and dynamic networking. The term "Traffic Engineered network" refers to a network that uses any connection-oriented technology under the control of a distributed or centralized control plane to support dynamic provisioning of end-to- end connectivity. Abstraction of network resources is a technique that can be applied to a single network domain or across multiple domains to create a single virtualized network that is under the control of a network operator or the customer of the operator that actually owns the network resources. This document provides a framework for Abstraction and Control of TE Networks (ACTN) to support virtual network services and connectivity services. This document defines a YANG data model that can be used to configure a Layer 2 provider-provisioned VPN service. It is up to a management system to take this as an input and generate specific configuration models to configure the different network elements to deliver the service. How this configuration of network elements is done is out of scope for this document. The YANG data model defined in this document includes support for point-to-point Virtual Private Wire Services (VPWSs) and multipoint Virtual Private LAN Services (VPLSs) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFCs 4761 and 6624. The YANG data model defined in this document conforms to the Network Management Datastore Architecture defined in RFC 8342. This document defines a YANG module for the Network Address Translation (NAT) function. Network Address Translation from IPv4 to IPv4 (NAT44), Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64), customer-side translator (CLAT), Stateless IP/ICMP Translation (SIIT), Explicit Address Mappings (EAM) for SIIT, IPv6-to-IPv6 Network Prefix Translation (NPTv6), and Destination NAT are covered in this document. Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. In the MPLS data plane, the SR header is instantiated through a label stack. This document specifies the forwarding behavior to allow instantiating SR over the MPLS data plane (SR-MPLS). MPLS Segment Routing (SR-MPLS) is a method of source routing a packet through an MPLS data plane by imposing a stack of MPLS labels on the packet to specify the path together with any packet-specific instructions to be executed on it. SR-MPLS can be leveraged to realize a source-routing mechanism across MPLS, IPv4, and IPv6 data planes by using an MPLS label stack as a source-routing instruction set while making no changes to SR-MPLS specifications and interworking with SR-MPLS implementations. This document describes how SR-MPLS-capable routers and IP-only routers can seamlessly coexist and interoperate through the use of SR-MPLS label stacks and IP encapsulation/tunneling such as MPLS-over-UDP as defined in RFC 7510. Segment Routing can be applied to the IPv6 data plane using a new type of Routing Extension Header called the Segment Routing Header (SRH). This document describes the SRH and how it is used by nodes that are Segment Routing (SR) capable. Network virtualization involves the cooperation of devices with a wide variety of capabilities such as software and hardware tunnel endpoints, transit fabrics, and centralized control clusters. As a result of their role in tying together different elements of the system, the requirements on tunnels are influenced by all of these components. Therefore, flexibility is the most important aspect of a tunneling protocol if it is to keep pace with the evolution of technology. This document describes Geneve, an encapsulation protocol designed to recognize and accommodate these changing capabilities and needs.

Example of Common Data Nodes in Early L2NM/L3NM Designs In order to avoid duplication of data nodes and to ease passing data among layers (i.e., from the service layer to the network layer and vice versa), early versions of the L3NM reused many of the data nodes that are defined in the L3SM. Nevertheless, that approach was abandoned because that design was interpreted as if the deployment of the L3NM depends on the L3SM, while this is not required. For example, a service provider may decide to use the L3NM to build its L3VPN services without exposing the L3SM to customers. Likewise, early versions of the L2NM reused many of the data nodes that are defined in both the L2SM and the L3NM. An example of L3NM groupings reused in the L2NM is shown in . Such reuse of data nodes was interpreted as if the deployment of the L2NM requires support for the L3NM, which is not required.

Excerpt from the L2NM YANG Module module ietf-l2vpn-ntw { ... import ietf-l3vpn-ntw { prefix l3vpn-ntw; reference "RFC 9182: A YANG Network Data Model for Layer 3 VPNs"; } ... container l2vpn-ntw { ... container vpn-services { list vpn-service { ... uses l3vpn-ntw:service-status; uses l3vpn-ntw:svc-transport-encapsulation; ... } } ... } }

Acknowledgements During the discussions of this work, helpful comments and reviews were received from (listed alphabetically) , , , , , , , , , , , , and . Many thanks to them. This work is partially supported by the European Commission under Horizon 2020 Secured autonomic traffic management for a Tera of SDN flows (Teraflow) project (grant agreement number 101015857). Many thanks to for the YANG Doctors review, for the tsvart review, and for the RtgDir review, for the genart review, for the opsdir review, and for the intdir review. Special thanks to for the AD review. Thanks to , , , , , , and for the IESG review.

Contributors Huawei Technologies

Italo.Busi@huawei.com

Vodafone

luis-angel.munoz@vodafone.com

Nokia

Madrid Spain victor.lopez@nokia.com

Authors' Addresses Telefonica

Madrid Spain samier.barguilgiraldo.ext@telefonica.com

Telefonica

Madrid Spain oscar.gonzalezdedios@telefonica.com

Orange

France mohamed.boucadair@orange.com

Huawei

101 Software Avenue Yuhua District Nanjing Jiangsu 210012 China bill.wu@huawei.com