Orange

mohamed.boucadair@orange.com

Juniper

rroberts@juniper.net

Telefonica

oscar.gonzalezdedios@telefonica.com

Nokia

samier.barguil_giraldo@nokia.com

Huawei Technologies

lana.wubo@huawei.com

OPS opsawg Slice Service L3VPN L2VPN Automation Network Automation Orchestration service delivery Service provisioning service segmentation service flexibility service simplification Network Service 3GPP Network Slicing The document specifies a common attachment circuits (ACs) YANG data model, which is designed to be reusable by other models. This design is meant to ensure consistent AC structures among models that manipulate ACs. For example, this common model can be reused by service models to expose ACs as a service, service models that require binding a service to a set of ACs, network and device models to provision ACs, etc.

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) 2025 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
• .  Conventions and Definitions
• .  Relationship to Other AC Data Models
• .  Description of the AC Common YANG Module
  • .  Features
  • .  Identities
  • .  Reusable Groupings
• .  Common Attachment Circuit YANG Module
• .  Security Considerations
• .  IANA Considerations
• .  References
  • .  Normative References
  • .  Informative References
• .  Full Tree
• Acknowledgments
• Contributors
• Authors' Addresses

Introduction Connectivity services are provided by networks to customers via dedicated terminating points (e.g., Service Functions (SFs), Customer Premises Equipment (CPE), Autonomous System Border Routers (ASBRs), data center gateways, or Internet Exchange Points (IXPs)). A connectivity service ensures data transfer from (or destined to) a given terminating point to (or originating from) other terminating points. Objectives for such a connectivity service may be negotiated and agreed upon between a customer and a network provider. For that data transfer to take place within the provider network, it is assumed that adequate setup is provisioned over the links connecting the customer's terminating points to the provider network (typically, a Provider Edge (PE)), thereby enabling successful data exchange. This necessary provisioning is referred to in this document as an "attachment circuit" (AC), while the underlying link is referred to as the "bearer". When a customer requests a new service, that service can be associated with existing ACs or may require the instantiation of new ACs. Whether these ACs are dedicated to a particular service or shared among multiple services depends on the specific deployment. Examples of ACs are depicted in . A Customer Edge (CE) may be realized as a physical node or a logical entity. From the network's perspective, a CE is treated as a peer Service Attachment Point (SAP) . CEs can be dedicated to a single service (e.g., Layer 3 Virtual Private Network (VPN) or Layer 2 VPN) or can host multiple services (e.g., SFs ). A single AC, as viewed by the network provider, may be bound to one or more peer SAPs (e.g., "CE1" and "CE2"). For instance, as discussed in , multiple CEs can attach to a PE over the same AC. This approach is typically deployed when the Layer 2 infrastructure between the CE and the network supports a multipoint service. A single CE may also terminate multiple ACs (e.g., "CE3" and "CE4"), which may be carried over the same or distinct bearers.

Examples of ACs .--------------------. | | .------. | .--. (b1) .-----. | +----. | | +---AC---+ | | CE1 | | | |PE+---AC---+ CE3 | '------' | .--. '--' (b2) '-----' +---AC--+PE| Network | .------. | '--' .--. (b3) .-----. | | | | | +---AC---+ | | CE2 +----' | |PE+---AC---+ CE4 | '------' | '--' (b3) '---+-' | .--. | | '----------+PE+------' | '--' | | | '-----------AC----------' (bx) = bearer Id x

This document specifies a common module ("ietf-ac-common") for ACs (). The module is designed to be reusable by other models, thereby ensuring consistent AC structures among modules that manipulate ACs. For example, the common module can be reused by service models to expose AC as a Service (ACaaS) (e.g., ) or by service models that require binding a service to a set of ACs (e.g., RFC 9543 Network Slice Service )). It can also be used by network models to provision ACs (e.g., ) and device models, among others. The common AC module eases data inheritance between modules (e.g., from service to network models as per ). The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in .

Conventions and Definitions The meanings of the symbols in the YANG tree diagrams are defined in . LxSM refers to both the L2VPN Service Model (L2SM) and the L3VPN Service Model (L3SM) . LxNM refers to both the L2VPN Network Model (L2NM) and the L3VPN Network Model (L3NM) . This document uses the following term:

Bearer:

A physical or logical link that connects a CE (or site) to a provider network. A bearer can be a wireless or wired link. One or multiple technologies can be used to build a bearer. The bearer type can be specified by a customer. The operator allocates a unique bearer reference to identify a bearer within its network (e.g., customer line identifier). Such a reference can be retrieved by a customer and then used in subsequent service placement requests to unambiguously identify where a service is to be bound. The concept of bearer can be generalized to refer to the required underlying connection for the provisioning of an AC. One or multiple ACs may be hosted over the same bearer (e.g., multiple Virtual Local Area Networks (VLANs) on the same bearer that is provided by a physical link).

The names of data nodes are prefixed using the prefix associated with the corresponding imported YANG module as shown in . Modules and Their Associated Prefixes

Prefix	Module	Reference
inet	ietf-inet-types
key-chain	ietf-key-chain
nacm	ietf-netconf-acm
vpn-common	ietf-vpn-common
yang	ietf-yang-types

Relationship to Other AC Data Models depicts the relationship between the various AC data models:

• "ietf-ac-common" ()
• "ietf-bearer-svc" ()
• "ietf-ac-svc" ()
• "ietf-ac-ntw"
• "ietf-ac-glue"

AC Data Models ietf-ac-common ^ ^ ^ | | | .----------' | '----------. | | | | | | ietf-ac-svc <--- ietf-bearer-svc | ^ ^ | | | | | '------------------------ ietf-ac-ntw | ^ | | | | '------------ ietf-ac-glue ----------' X --> Y: X imports Y

The "ietf-ac-common" module is imported by the "ietf-bearer-svc", "ietf-ac-svc", and "ietf-ac-ntw" modules. Bearers managed using the "ietf-bearer-svc" module may be referenced by service ACs managed using the "ietf-ac-svc" module. Similarly, a bearer managed using the "ietf-bearer-svc" module may list the set of ACs that use that bearer. To facilitate correlation between an AC service request and the actual AC provisioned in the network, "ietf-ac-ntw" leverages the AC references exposed by the "ietf-ac-svc" module. Furthermore, to bind Layer 2 VPN or Layer 3 VPN services with ACs, the "ietf-ac-glue" module augments the LxSM and LxNM with AC service references exposed by the "ietf-ac-svc" module and AC network references exposed by the "ietf-ac-ntw" module.

Description of the AC Common YANG Module The full tree diagram of the module is provided in . Subtrees are provided in the following subsections for the reader's convenience.

Features The module defines the following features:

'layer2-ac':

Used to indicate support of ACs with Layer 2 properties.

'layer3-ac':

Used to indicate support of ACs with Layer 3 properties.

'server-assigned-reference':

Used to indicate support of server-generated references to access relevant resources. Typically, a server can be a network controller or a router in a provider network. For example, a bearer request is first created using a name that is assigned by the client, but if this feature is supported, the request will also include a server-generated reference. That reference can be used when requesting the creation of an AC over the existing bearer.

Identities The module defines a set of identities, including the following:

'address-allocation-type':

Used to specify the IP address allocation type in an AC. For example, this identity is used to indicate whether the provider network provides DHCP service, DHCP relay, or static addressing. Note that for the IPv6 case, Stateless Address Autoconfiguration (SLAAC) can be used.

'local-defined-next-hop':

Used to specify next-hop actions. For example, this identity can be used to indicate an action to discard traffic for a given destination or treat traffic towards addresses within the specified next-hop prefix as though they are connected to a local link.

'l2-tunnel-type':

Used to control the Layer 2 tunnel selection for an AC. The current version supports indicating pseudowire, Virtual Private LAN Service (VPLS), and Virtual eXtensible Local Area Network (VXLAN).

'l3-tunnel-type':

Used to control the Layer 3 tunnel selection for an AC. Examples of such type are: IP-in-IP , IPsec , and Generic Routing Encapsulation (GRE) .

'precedence-type':

Used to indicate the redundancy type when requesting ACs. For example, this identity can be used to tag primary and secondary ACs.

'role':

Used to indicate the type of an AC: User-to-Network Interface (UNI), Network-to-Network Interface (NNI), or public NNI. The reader may refer to , , , or for examples of discussions regarding the use of UNI and NNI reference points.

New administrative status types:

In addition to the status types already defined in , this document defines:

• 'awaiting-validation' to report that a request is pending an administrator approval.
• 'awaiting-processing' to report that a request was approved and validated but is awaiting more processing before activation.
• 'admin-prohibited' to report that a request cannot be handled because of administrative policies.
• 'rejected' to report that a request was rejected due to reasons not covered by the other status types.

'bgp-role':

Used to indicate the BGP role when establishing a BGP session per .

Reusable Groupings The module also defines a set of reusable groupings, including the following:

'service-status' ():

Controls the administrative service status and reports the operational service status.

'ac-profile-cfg' ():

A grouping with a set of valid provider profile identifiers. The following profiles are supported:

'encryption-profile-identifier':

Refers to a set of policies related to the encryption setup that can be applied when provisioning an AC.

'qos-profile-identifier':

Refers to a set of policies, such as classification, marking, and actions (e.g., ).

'failure-detection-profile-identifier':

Refers to a set of failure detection policies (e.g., Bidirectional Forwarding Detection (BFD) policies ) that can be invoked when building an AC.

'forwarding-profile-identifier':

Refers to the policies that apply to the forwarding of packets conveyed within an AC. Such policies may consist, for example, of applying Access Control Lists (ACLs).

'routing-profile-identifier':

Refers to a set of routing policies that will be invoked (e.g., BGP policies) when building an AC.

'op-instructions' ():

Defines a set of parameters to specify basic scheduling instructions and report related events for a service request (e.g., AC or bearer) ('service-status'). Advanced scheduling groupings are defined in .

Service Status, Profiles, and Operational Instructions Groupings grouping service-status: +-- status +-- admin-status | +-- status? identityref | +--ro last-change? yang:date-and-time +--ro oper-status +--ro status? identityref +--ro last-change? yang:date-and-time grouping ac-profile-cfg: +-- valid-provider-identifiers +-- encryption-profile-identifier* [id] | +-- id string +-- qos-profile-identifier* [id] | +-- id string +-- failure-detection-profile-identifier* [id] | +-- id string +-- forwarding-profile-identifier* [id] | +-- id string +-- routing-profile-identifier* [id] +-- id string grouping op-instructions: +-- requested-start? yang:date-and-time +-- requested-stop? yang:date-and-time +--ro actual-start? yang:date-and-time +--ro actual-stop? yang:date-and-time

Layer 2 encapsulations ():

Groupings for the following encapsulation schemes are supported: dot1Q, QinQ, and priority-tagged.

Layer 2 tunnel services ():

These groupings are used to define Layer 2 tunnel services that may be needed for the activation of an AC. Examples of supported Layer 2 services are the pseudowire (), VPLS, or VXLAN .

Layer 2 Connection Groupings grouping dot1q: +-- tag-type? identityref +-- cvlan-id? uint16 grouping priority-tagged: +-- tag-type? identityref grouping qinq: +-- tag-type? identityref +-- svlan-id? uint16 +-- cvlan-id? uint16 grouping pseudowire: +-- vcid? uint32 +-- far-end? union grouping vpls: +-- vcid? uint32 +-- far-end* union grouping vxlan: +-- vni-id? uint32 +-- peer-mode? identityref +-- peer-ip-address* inet:ip-address grouping l2-tunnel-service: +-- type? identityref +-- pseudowire | +-- vcid? uint32 | +-- far-end? union +-- vpls | +-- vcid? uint32 | +-- far-end* union +-- vxlan +-- vni-id? uint32 +-- peer-mode? identityref +-- peer-ip-address* inet:ip-address

Layer 3 address allocation ():

Defines both IPv4 and IPv6 groupings to specify IP address allocation over an AC. Both dynamic and static address schemes are supported. For both IPv4 and IPv6, 'address-allocation-type' is used to indicate the IP address allocation mode to activate. When 'address-allocation-type' is set to 'provider-dhcp', DHCP assignments can be made locally or by an external DHCP server. Such behavior is controlled by setting 'dhcp-service-type'. Note that if 'address-allocation-type' is set to 'slaac', the Prefix Information option of Router Advertisements that will be issued for SLAAC purposes will carry the IPv6 prefix that is determined by 'local-address' and 'prefix-length'.

IP connections ():

Defines IPv4 and IPv6 groupings for managing Layer 3 connectivity over an AC. Both basic and more elaborated IP connection groupings are supported.

Layer 3 Connection Groupings grouping ipv4-allocation-type: +-- prefix-length? uint8 +-- address-allocation-type? identityref grouping ipv6-allocation-type: +-- prefix-length? uint8 +-- address-allocation-type? identityref grouping ipv4-connection-basic: +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) +-- (provider-dhcp)? | +--:(dhcp-service-type) | +-- dhcp-service-type? enumeration +-- (dhcp-relay)? +--:(customer-dhcp-servers) +-- customer-dhcp-servers +-- server-ip-address* inet:ipv4-address grouping ipv6-connection-basic: +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) +-- (provider-dhcp)? | +--:(dhcp-service-type) | +-- dhcp-service-type? enumeration +-- (dhcp-relay)? +--:(customer-dhcp-servers) +-- customer-dhcp-servers +-- server-ip-address* inet:ipv6-address grouping ipv4-connection: +-- local-address? inet:ipv4-address +-- virtual-address? inet:ipv4-address +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) | +-- (address-assign)? | | +--:(number) | | | +-- number-of-dynamic-address? uint16 | | +--:(explicit) | | +-- customer-addresses | | +-- address-pool* [pool-id] | | +-- pool-id string | | +-- start-address inet:ipv4-address | | +-- end-address? inet:ipv4-address | +-- (provider-dhcp)? | | +--:(dhcp-service-type) | | +-- dhcp-service-type? enumeration | +-- (dhcp-relay)? | +--:(customer-dhcp-servers) | +-- customer-dhcp-servers | +-- server-ip-address* inet:ipv4-address +--:(static-addresses) +-- address* [address-id] +-- address-id string +-- customer-address? inet:ipv4-address grouping ipv6-connection: +-- local-address? inet:ipv6-address +-- virtual-address? inet:ipv6-address +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) | +-- (address-assign)? | | +--:(number) | | | +-- number-of-dynamic-address? uint16 | | +--:(explicit) | | +-- customer-addresses | | +-- address-pool* [pool-id] | | +-- pool-id string | | +-- start-address inet:ipv6-address | | +-- end-address? inet:ipv6-address | +-- (provider-dhcp)? | | +--:(dhcp-service-type) | | +-- dhcp-service-type? enumeration | +-- (dhcp-relay)? | +--:(customer-dhcp-servers) | +-- customer-dhcp-servers | +-- server-ip-address* inet:ipv6-address +--:(static-addresses) +-- address* [address-id] +-- address-id string +-- customer-address? inet:ipv6-address

Routing parameters & Operations, Administration, and Maintenance (OAM) ():

In addition to static routing, the module supports the following routing protocols: BGP , OSPF , IS-IS , and RIP . For all supported routing protocols, 'address-family' indicates whether IPv4, IPv6, or both address families are to be activated. For example, this parameter is used to determine whether RIPv2 , RIP Next Generation (RIPng), or both are to be enabled . More details about supported routing groupings are provided hereafter:

Authentication:

These groupings include the required information to manage the authentication of OSPF, IS-IS, BGP, and RIP. The groupings support local specification of authentication keys and the associated authentication algorithm to accommodate legacy implementations that do not support key chains . Note that this version of the common AC model covers authentication options that are common to both OSPFv2 and OSPFv3 ; as such, the model does not support . Similar to , this version of the common AC model assumes that parameters specific to the TCP Authentication Option (TCP-AO) are preconfigured as part of the key chain that is referenced in the model. No assumption is made about how such a key chain is preconfigured. However, the structure of the key chain should cover data nodes beyond those in , mainly SendID and RecvID ().

BGP peer groups ('bgp-peer-group-without-name' and 'bgp-peer-group-with-name'):

Includes a set of parameters to identify a BGP peer group. Such a group can be defined by providing a local Autonomous System Number (ASN), a customer's ASN, and the address families to be activated for this group. BGP peer groups can be identified by a name ('bgp-peer-group-with-name').

Basic OSPF and IS-IS parameters ('ospf-basic' and 'isis-basic'):

These groupings include the minimal set of routing configuration that is required for the activation of OSPF and IS-IS.

Static routing:

Parameters to configure an entry or a list of IP static routing entries.

The 'redundancy-group' grouping lists the groups to which an AC belongs . For example, the 'group-id' is used to associate redundancy or protection constraints of ACs.

Routing & OAM Groupings grouping bgp-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(ao) | +-- enable-ao? boolean | +-- ao-keychain? key-chain:key-chain-ref +--:(md5) | +-- md5-keychain? key-chain:key-chain-ref +--:(explicit) +-- key-id? uint32 +-- key? string +-- crypto-algorithm? identityref grouping ospf-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(auth-key-chain) | +-- key-chain? key-chain:key-chain-ref +--:(auth-key-explicit) +-- key-id? uint32 +-- key? string +-- crypto-algorithm? identityref grouping isis-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(auth-key-chain) | +-- key-chain? key-chain:key-chain-ref +--:(auth-key-explicit) +-- key-id? uint32 +-- key? string +-- crypto-algorithm? identityref grouping rip-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(auth-key-chain) | +-- key-chain? key-chain:key-chain-ref +--:(auth-key-explicit) +-- key? string +-- crypto-algorithm? identityref grouping bgp-peer-group-without-name: +-- local-as? inet:as-number +-- peer-as? inet:as-number +-- address-family? identityref +-- role? identityref grouping bgp-peer-group-with-name: +-- name? string +-- local-as? inet:as-number +-- peer-as? inet:as-number +-- address-family? identityref +-- role? identityref grouping ospf-basic: +-- address-family? identityref +-- area-id yang:dotted-quad +-- metric? uint16 grouping isis-basic: +-- address-family? identityref +-- area-address area-address grouping ipv4-static-rtg-entry: +-- lan? inet:ipv4-prefix +-- lan-tag? string +-- next-hop? union +-- metric? uint32 grouping ipv4-static-rtg: +-- ipv4-lan-prefixes* [lan next-hop] {vpn-common:ipv4}? +-- lan inet:ipv4-prefix +-- lan-tag? string +-- next-hop union +-- metric? uint32 +-- status +-- admin-status | +-- status? identityref | +--ro last-change? yang:date-and-time +--ro oper-status +--ro status? identityref +--ro last-change? yang:date-and-time grouping ipv6-static-rtg-entry: +-- lan? inet:ipv6-prefix +-- lan-tag? string +-- next-hop? union +-- metric? uint32 grouping ipv6-static-rtg: +-- ipv6-lan-prefixes* [lan next-hop] {vpn-common:ipv6}? +-- lan inet:ipv6-prefix +-- lan-tag? string +-- next-hop union +-- metric? uint32 +-- status +-- admin-status | +-- status? identityref | +--ro last-change? yang:date-and-time +--ro oper-status +--ro status? identityref +--ro last-change? yang:date-and-time grouping bfd: +-- holdtime? uint32 grouping redundancy-group: +-- group* [group-id] +-- group-id? string +-- precedence? identityref

Bandwidth parameters ():

Bandwidth parameters can be represented using the Committed Information Rate (CIR), the Excess Information Rate (EIR), or the Peak Information Rate (PIR). These parameters can be provided per bandwidth type. Type values are taken from . For example, the following values can be used:

'bw-per-cos':

The bandwidth is per Class of Service (CoS).

'bw-per-site':

The bandwidth is for all ACs that belong to the same site.

Bandwidth Groupings grouping bandwidth-parameters: +-- cir? uint64 +-- cbs? uint64 +-- eir? uint64 +-- ebs? uint64 +-- pir? uint64 +-- pbs? uint64 grouping bandwidth-per-type: +-- bandwidth* [bw-type] +-- bw-type identityref +-- (type)? +--:(per-cos) | +-- cos* [cos-id] | +-- cos-id uint8 | +-- cir? uint64 | +-- cbs? uint64 | +-- eir? uint64 | +-- ebs? uint64 | +-- pir? uint64 | +-- pbs? uint64 +--:(other) +-- cir? uint64 +-- cbs? uint64 +-- eir? uint64 +-- ebs? uint64 +-- pir? uint64 +-- pbs? uint64

Common Attachment Circuit YANG Module This module uses types defined in , , , and . module ietf-ac-common { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ac-common"; prefix ac-common; import ietf-vpn-common { prefix vpn-common; reference "RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs"; } import ietf-netconf-acm { prefix nacm; reference "RFC 8341: Network Configuration Access Control Model"; } import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types, Section 4"; } import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Data Types, Section 3"; } import ietf-key-chain { prefix key-chain; reference "RFC 8177: YANG Data Model for Key Chains"; } 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> Editor: Richard Roberts <mailto:rroberts@juniper.net> Author: Oscar Gonzalez de Dios <mailto:oscar.gonzalezdedios@telefonica.com> Author: Samier Barguil <mailto:ssamier.barguil_giraldo@nokia.com> Author: Bo Wu <mailto:lana.wubo@huawei.com>"; description "This YANG module defines a common attachment circuit (AC) YANG module with a set of reusable features, types, identities, and groupings. Copyright (c) 2025 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 9833; see the RFC itself for full legal notices."; revision 2025-09-29 { description "Initial revision."; reference "RFC 9833: A Common YANG Data Model for Attachment Circuits"; } /****************************Features************************/ feature layer2-ac { description "Indicates support of Layer 2 ACs."; } feature layer3-ac { description "Indicates support of Layer 3 ACs."; } feature server-assigned-reference { description "Indicates support for server-generated references and use of such references to access related resources."; } /****************************Identities************************/ // IP address allocation types identity address-allocation-type { description "Base identity for address allocation type on the AC."; } identity provider-dhcp { base address-allocation-type; description "The provider's network provides a DHCP service to the customer."; } identity provider-dhcp-relay { base address-allocation-type; description "The provider's network provides a DHCP relay service to the customer."; } identity provider-dhcp-slaac { if-feature "vpn-common:ipv6"; base address-allocation-type; description "The provider's network provides a DHCP service to the customer as well as IPv6 Stateless Address Autoconfiguration (SLAAC)."; reference "RFC 4862: IPv6 Stateless Address Autoconfiguration"; } identity static-address { base address-allocation-type; description "The provider's network provides static IP addressing to the customer."; } identity slaac { if-feature "vpn-common:ipv6"; base address-allocation-type; description "The provider's network uses IPv6 SLAAC to provide addressing to the customer."; reference "RFC 4862: IPv6 Stateless Address Autoconfiguration"; } identity dynamic-infra { base address-allocation-type; description "The IP address is dynamically allocated by the hosting infrastructure."; } // next-hop actions identity local-defined-next-hop { description "Base identity of local defined next hops."; } identity discard { base local-defined-next-hop; description "Indicates an action to discard traffic for the corresponding destination."; } identity local-link { base local-defined-next-hop; description "Treat traffic towards addresses within the specified next-hop prefix as though they are connected to a local link."; } // Layer 2 tunnel types identity l2-tunnel-type { description "Base identity for Layer 2 tunnel selection for an AC."; } identity pseudowire { base l2-tunnel-type; description "Pseudowire tunnel termination for the AC."; } identity vpls { base l2-tunnel-type; description "Virtual Private LAN Service (VPLS) tunnel termination for the AC."; } identity vxlan { base l2-tunnel-type; description "Virtual eXtensible Local Area Network (VXLAN) tunnel termination for the AC."; } // Layer 3 tunnel types identity l3-tunnel-type { description "Base identity for Layer 3 tunnel selection for an AC."; } identity ip-in-ip { base l3-tunnel-type; description "IP-in-IP tunneling."; reference "RFC 2003: IP Encapsulation within IP"; } identity ipsec { base l3-tunnel-type; description "IP Security (IPsec)."; reference "RFC 4301: Security Architecture for the Internet Protocol"; } identity gre { base l3-tunnel-type; description "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)"; } // Tagging precedence identity precedence-type { description "Redundancy type. Attachment to a network can be created with primary and secondary tagging."; } identity primary { base precedence-type; description "Identifies the main AC."; } identity secondary { base precedence-type; description "Identifies a secondary AC."; } // AC type identity role { description "Base identity for the network role of an AC."; } identity uni { base role; description "User-to-Network Interface (UNI)."; } identity nni { base role; description "Network-to-Network Interface (NNI)."; } identity public-nni { base role; description "Public peering. This is typically set using a shared network, such as an Internet Exchange Point (IXP)."; } // More Admin status types identity awaiting-validation { base vpn-common:administrative-status; description "This administrative status reflects that a request is pending an administrator approval."; } identity awaiting-processing { base vpn-common:administrative-status; description "This administrative status reflects that a request was approved and validated but is awaiting more processing before activation."; } identity admin-prohibited { base vpn-common:administrative-status; description "This administrative status reflects that a request cannot be handled because of administrative policies."; } identity rejected { base vpn-common:administrative-status; description "This administrative status reflects that a request was rejected because, e.g., there are no sufficient resources or other reasons not covered by the other status types."; } // BGP role identity bgp-role { description "Used to indicate the BGP role when establishing a BGP session."; reference "RFC 9234: Route Leak Prevention and Detection Using Roles in UPDATE and OPEN Messages, Section 4"; } identity provider { base bgp-role; description "The local AS is a transit provider of the remote AS."; } identity client { base bgp-role; description "The local AS is a transit customer of the remote AS."; } identity rs { base bgp-role; description "The local AS is a Route Server (RS)."; } identity rs-client { base bgp-role; description "The local AS is a client of an RS, and the RS is the remote AS."; } identity peer { base bgp-role; description "The local and remote ASes have a peering relationship."; } /****************************Typedefs************************/ typedef predefined-next-hop { type identityref { base local-defined-next-hop; } description "Predefined next-hop designation for locally generated routes."; } typedef area-address { type string { pattern '[0-9A-Fa-f]{2}(\.[0-9A-Fa-f]{4}){0,6}'; } description "This type defines the area address format."; } /************************Reusable groupings********************/ /**** Service Status ****/ grouping service-status { description "Service status grouping."; container status { description "Service status."; container admin-status { description "Administrative service status."; leaf status { type identityref { base vpn-common:administrative-status; } description "Administrative service status."; } leaf last-change { type yang:date-and-time; config false; description "Indicates the actual date and time of the service status change."; } } container oper-status { config false; description "Operational service status."; uses vpn-common:oper-status-timestamp; } } } /**** A set of profiles ****/ grouping ac-profile-cfg { description "Grouping for AC profile configuration."; container valid-provider-identifiers { description "Container for valid provider profile identifiers. The profiles only have 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."; } } 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."; } } list failure-detection-profile-identifier { key "id"; description "List of BFD profile identifiers."; leaf id { type string; description "Identification of the failure detection (e.g., BFD) profile to be used."; } } 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."; } } 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 over an AC."; } } nacm:default-deny-write; } } /**** Operational instructions ****/ grouping op-instructions { description "Scheduling instructions."; leaf requested-start { type yang:date-and-time; description "Indicates the requested date and time when the service is expected to be active."; } leaf requested-stop { type yang:date-and-time; description "Indicates the requested date and time when the service is expected to be disabled."; } leaf actual-start { type yang:date-and-time; config false; description "Indicates the actual date and time when the service actually was enabled."; } leaf actual-stop { type yang:date-and-time; config false; description "Indicates the actual date and time when the service actually was disabled."; } } /**** Layer 2 encapsulations ****/ // Dot1q grouping dot1q { description "Defines a grouping for tagged interfaces."; leaf tag-type { type identityref { base vpn-common:tag-type; } description "Tag type."; } leaf cvlan-id { type uint16 { range "1..4094"; } description "VLAN identifier."; } } // priority-tagged grouping priority-tagged { description "Priority tagged."; leaf tag-type { type identityref { base vpn-common:tag-type; } description "Tag type."; } } // QinQ grouping qinq { description "Includes QinQ parameters."; leaf tag-type { type identityref { base vpn-common:tag-type; } description "Tag type."; } leaf svlan-id { type uint16 { range "1..4094"; } description "Service VLAN (S-VLAN) identifier."; } leaf cvlan-id { type uint16 { range "1..4094"; } description "Customer VLAN (C-VLAN) identifier."; } } /**** Layer 2 tunnel services ****/ // pseudowire (PW) grouping pseudowire { description "Includes pseudowire termination parameters."; leaf vcid { type uint32; description "Indicates a PW or virtual circuit (VC) identifier."; } leaf far-end { type union { type uint32; type inet:ip-address; } description "Neighbor reference."; reference "RFC 8077: Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP), Section 6.1"; } } // VPLS grouping vpls { description "VPLS termination parameters."; leaf vcid { type uint32; description "VC identifier."; } leaf-list far-end { type union { type uint32; type inet:ip-address; } description "Neighbor reference."; } } // VXLAN grouping vxlan { description "VXLAN termination parameters."; leaf vni-id { type uint32; description "VXLAN Network Identifier (VNI)."; } leaf peer-mode { type identityref { base vpn-common:vxlan-peer-mode; } description "Specifies the VXLAN access mode. By default, the peer mode is set to 'static-mode'."; } leaf-list peer-ip-address { type inet:ip-address; description "List of a peer's IP addresses."; } } // Layer 2 Tunnel service grouping l2-tunnel-service { description "Defines a Layer 2 tunnel termination."; leaf type { type identityref { base l2-tunnel-type; } description "Selects the tunnel termination type for an AC."; } container pseudowire { when "derived-from-or-self(../type, 'ac-common:pseudowire')" { description "Only applies when the Layer 2 service type is 'pseudowire'."; } description "Includes pseudowire termination parameters."; uses pseudowire; } container vpls { when "derived-from-or-self(../type, 'ac-common:vpls')" { description "Only applies when the Layer 2 service type is 'vpls'."; } description "VPLS termination parameters."; uses vpls; } container vxlan { when "derived-from-or-self(../type, 'ac-common:vxlan')" { description "Only applies when the Layer 2 service type is 'vxlan'."; } description "VXLAN termination parameters."; uses vxlan; } } /**** Layer 3 connection *****/ // IPv4 allocation type grouping ipv4-allocation-type { description "IPv4-specific parameters."; leaf prefix-length { type uint8 { range "0..32"; } description "Subnet prefix length expressed in bits. It is applied to both local and customer addresses."; } leaf address-allocation-type { type identityref { base address-allocation-type; } must "not(derived-from-or-self(current(), 'ac-common:slaac') " + "or derived-from-or-self(current(), " + "'ac-common:provider-dhcp-slaac'))" { error-message "SLAAC is only applicable to IPv6."; } description "Defines how IPv4 addresses are allocated to the peer termination points."; } } // IPv6 allocation type grouping ipv6-allocation-type { description "IPv6-specific parameters."; leaf prefix-length { type uint8 { range "0..128"; } description "Subnet prefix length expressed in bits. It is applied to both local and customer addresses."; } leaf address-allocation-type { type identityref { base address-allocation-type; } description "Defines how IPv6 addresses are allocated to the peer termination points."; } } // Basic parameters for an IPv4 connection grouping ipv4-connection-basic { description "Basic set for IPv4-specific parameters for the connection."; uses ipv4-allocation-type; choice allocation-type { description "Choice of the IPv4 address allocation."; case dynamic { description "When the addresses are allocated by DHCP or other dynamic means local to the infrastructure."; choice provider-dhcp { description "Parameters related to DHCP-allocated addresses. IP addresses are allocated by DHCP, which is provided by the operator."; leaf dhcp-service-type { type enumeration { enum server { description "Local DHCP server."; } enum relay { description "Local DHCP relay. DHCP requests are relayed to a provider's server."; } } description "Indicates the type of DHCP service to be enabled on an AC."; } } choice dhcp-relay { description "The DHCP relay is provided by the operator."; container customer-dhcp-servers { description "Container for a list of the customer's DHCP servers."; leaf-list server-ip-address { type inet:ipv4-address; description "IPv4 addresses of the customer's DHCP server."; } } } } } } // Basic parameters for an IPv6 connection grouping ipv6-connection-basic { description "Basic set for IPv6-specific parameters for the connection."; uses ipv6-allocation-type; choice allocation-type { description "Choice of the IPv6 address allocation."; case dynamic { description "When the addresses are allocated by DHCP or other dynamic means local to the infrastructure."; choice provider-dhcp { description "Parameters related to DHCP-allocated addresses. IP addresses are allocated by DHCP, which is provided by the operator."; leaf dhcp-service-type { type enumeration { enum server { description "Local DHCP server."; } enum relay { description "Local DHCP relay. DHCP requests are relayed to a provider's server."; } } description "Indicates the type of DHCP service to be enabled on the AC."; } } choice dhcp-relay { description "The DHCP relay is provided by the operator."; container customer-dhcp-servers { description "Container for a list of the customer's DHCP servers."; leaf-list server-ip-address { type inet:ipv6-address; description "IPv6 addresses of the customer's DHCP server."; } } } } } } // Full parameters for the IPv4 connection grouping ipv4-connection { description "IPv4-specific connection parameters."; leaf local-address { type inet:ipv4-address; description "The IP address used at the provider's interface."; } leaf virtual-address { type inet:ipv4-address; description "This address may be used for redundancy purposes."; } uses ipv4-allocation-type; choice allocation-type { description "Choice of the IPv4 address allocation."; case dynamic { description "When the addresses are allocated by DHCP or other dynamic means local to the infrastructure."; choice address-assign { description "A choice for how IPv4 addresses are assigned."; case number { leaf number-of-dynamic-address { type uint16; description "Specifies the number of IP addresses to be assigned to the customer on the AC."; } } case explicit { container customer-addresses { description "Container for customer addresses to be allocated using DHCP."; list address-pool { key "pool-id"; description "Describes IP addresses to be dynamically allocated. When only 'start-address' is present, it represents a single address. When both 'start-address' and 'end-address' are specified, it implies a range inclusive of both addresses."; leaf pool-id { type string; description "A pool identifier for the address range from 'start-address' to 'end-address'."; } leaf start-address { type inet:ipv4-address; mandatory true; description "Indicates the first address in the pool."; } leaf end-address { type inet:ipv4-address; description "Indicates the last address in the pool."; } } } } } choice provider-dhcp { description "Parameters related to DHCP-allocated addresses. IP addresses are allocated by DHCP, which is provided by the operator."; leaf dhcp-service-type { type enumeration { enum server { description "Local DHCP server."; } enum relay { description "Local DHCP relay. DHCP requests are relayed to a provider's server."; } } description "Indicates the type of DHCP service to be enabled on this AC."; } } choice dhcp-relay { description "The DHCP relay is provided by the operator."; container customer-dhcp-servers { description "Container for a list of the customer's DHCP servers."; leaf-list server-ip-address { type inet:ipv4-address; description "IPv4 addresses of the customer's DHCP server."; } } } } case static-addresses { description "Lists the IPv4 addresses that are used."; list address { key "address-id"; ordered-by user; description "Lists the IPv4 addresses that are used. The first address of the list is the primary address of the connection."; leaf address-id { type string; description "An identifier of the static IPv4 address."; } leaf customer-address { type inet:ipv4-address; description "An IPv4 address of the customer side."; } } } } } // Full parameters for the IPv6 connection grouping ipv6-connection { description "IPv6-specific connection parameters."; leaf local-address { type inet:ipv6-address; description "IPv6 address of the provider side."; } leaf virtual-address { type inet:ipv6-address; description "This address may be used for redundancy purposes."; } uses ipv6-allocation-type; choice allocation-type { description "Choice of the IPv6 address allocation."; case dynamic { description "When the addresses are allocated by DHCP or other dynamic means local to the infrastructure."; choice address-assign { description "A choice for how IPv6 addresses are assigned."; case number { leaf number-of-dynamic-address { type uint16; description "Specifies the number of IP addresses to be assigned to the customer on this access."; } } case explicit { container customer-addresses { description "Container for customer addresses to be allocated using DHCP."; list address-pool { key "pool-id"; description "Describes IP addresses to be dynamically allocated. When only 'start-address' is present, it represents a single address. When both 'start-address' and 'end-address' are specified, it implies a range inclusive of both addresses."; leaf pool-id { type string; description "A pool identifier for the address range from 'start-address' to 'end-address'."; } leaf start-address { type inet:ipv6-address; mandatory true; description "Indicates the first address in the pool."; } leaf end-address { type inet:ipv6-address; description "Indicates the last address in the pool."; } } } } } choice provider-dhcp { description "Parameters related to DHCP-allocated addresses. IP addresses are allocated by DHCP, which is provided by the operator."; leaf dhcp-service-type { type enumeration { enum server { description "Local DHCP server."; } enum relay { description "Local DHCP relay. DHCP requests are relayed to a provider's server."; } } description "Indicates the type of DHCP service to be enabled on this access."; } } choice dhcp-relay { description "The DHCP relay is provided by the operator."; container customer-dhcp-servers { description "Container for a list of the customer's DHCP servers."; leaf-list server-ip-address { type inet:ipv6-address; description "IPv6 addresses of the customer's DHCP server."; } } } } case static-addresses { description "Lists the IPv6 addresses that are used by the customer."; list address { key "address-id"; ordered-by user; description "Lists the IPv6 addresses that are used. The first address of the list is the primary IP address of the connection."; leaf address-id { type string; description "An identifier of the static IPv6 address."; } leaf customer-address { type inet:ipv6-address; description "An IPv6 address of the customer side."; } } } } } /**** Routing ****/ // Routing authentication grouping bgp-authentication { description "Grouping for BGP authentication parameters."; container authentication { description "Container for BGP authentication parameters."; leaf enabled { type boolean; description "Enables or disables authentication."; } container keying-material { when "../enabled = 'true'"; description "Container for describing how a BGP routing session is to be secured on an AC."; choice option { description "Choice of authentication options."; case ao { description "Uses the TCP Authentication Option (TCP-AO)."; reference "RFC 5925: The TCP Authentication Option"; leaf enable-ao { type boolean; description "Enables the TCP-AO."; } leaf ao-keychain { type key-chain:key-chain-ref; description "Reference to the TCP-AO key chain."; reference "RFC 8177: YANG Data Model for Key Chains"; } } case md5 { description "Uses MD5 to secure the session."; reference "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), Section 13.2"; leaf md5-keychain { type key-chain:key-chain-ref; description "Specifies a reference to the MD5 key chain."; reference "RFC 8177: YANG Data Model for Key Chains"; } } case explicit { leaf key-id { type uint32; description "Specifies a key identifier."; } leaf key { type string; description "BGP authentication key. This model only supports the subset of keys that are representable as ASCII strings."; } leaf crypto-algorithm { type identityref { base key-chain:crypto-algorithm; } description "Indicates the cryptographic algorithm associated with the key."; } } } } } } grouping ospf-authentication { description "Authentication configuration."; container authentication { description "Container for OSPF authentication parameters."; leaf enabled { type boolean; description "Enables or disables authentication."; } container keying-material { when "../enabled = 'true'"; description "Container for describing how an OSPF session is to be secured for an AC."; choice option { description "Options for OSPF authentication."; case auth-key-chain { leaf key-chain { type key-chain:key-chain-ref; description "Specifies the name of the key chain."; } } case auth-key-explicit { leaf key-id { type uint32; description "Specifies a key identifier."; } leaf key { type string; description "OSPF authentication key. This model only supports the subset of keys that are representable as ASCII strings."; } leaf crypto-algorithm { type identityref { base key-chain:crypto-algorithm; } description "Indicates the cryptographic algorithm associated with the key."; } } } } } } grouping isis-authentication { description "IS-IS authentication configuration."; container authentication { description "Container for IS-IS authentication parameters."; leaf enabled { type boolean; description "Enables or disables authentication."; } container keying-material { when "../enabled = 'true'"; description "Describes how an IS-IS session is secured over an AC."; choice option { description "Options for IS-IS authentication."; case auth-key-chain { leaf key-chain { type key-chain:key-chain-ref; description "Specifies the name of the key chain."; } } case auth-key-explicit { leaf key-id { type uint32; description "Indicates a key identifier."; } leaf key { type string; description "IS-IS authentication key. This model only supports the subset of keys that are representable as ASCII strings."; } leaf crypto-algorithm { type identityref { base key-chain:crypto-algorithm; } description "Indicates the cryptographic algorithm associated with the key."; } } } } } } grouping rip-authentication { description "RIP authentication configuration."; container authentication { description "Includes RIP authentication parameters."; leaf enabled { type boolean; description "Enables or disables authentication."; } container keying-material { when "../enabled = 'true'"; description "Describes how a RIP session is to be secured on an AC."; choice option { description "Specifies the authentication scheme."; case auth-key-chain { leaf key-chain { type key-chain:key-chain-ref; description "Indicates the name of the key chain."; } } case auth-key-explicit { leaf key { type string; description "Specifies a RIP authentication key. This model only supports the subset of keys that are representable as ASCII strings."; } leaf crypto-algorithm { type identityref { base key-chain:crypto-algorithm; } description "Indicates the cryptographic algorithm associated with the key."; } } } } } } // Basic routing parameters grouping bgp-peer-group-without-name { description "Identifies a BGP peer-group configured on the local system."; leaf local-as { type inet:as-number; description "Indicates a local Autonomous System Number (ASN). This ASN is exposed to a customer so that it knows which ASN to use to set up a BGP session."; } leaf peer-as { type inet:as-number; description "Indicates the customer's ASN when the customer requests BGP routing."; } leaf address-family { type identityref { base vpn-common:address-family; } description "This node contains the address families to be activated. 'dual-stack' means that both IPv4 and IPv6 will be activated."; } leaf role { type identityref { base ac-common:bgp-role; } description "Specifies the BGP role (provider, customer, peer, etc.)."; reference "RFC 9234: Route Leak Prevention and Detection Using Roles in UPDATE and OPEN Messages, Section 4"; } } grouping bgp-peer-group-with-name { description "Identifies a BGP peer-group configured on the local system, identified by a peer-group name."; leaf name { type string; description "Specifies the name of the BGP peer-group."; } uses bgp-peer-group-without-name; } grouping ospf-basic { description "Includes configuration specific to OSPF."; leaf address-family { type identityref { base vpn-common:address-family; } description "Indicates whether IPv4, IPv6, or both are to be activated."; } leaf area-id { type yang:dotted-quad; mandatory true; description "Specifies an area ID."; reference "RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs), Section 4.2.3 RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol, Section 4.2"; } leaf metric { type uint16; description "Metric of the AC. It is used in the routing state calculation and path selection."; } } grouping isis-basic { description "Basic configuration specific to IS-IS."; leaf address-family { type identityref { base vpn-common:address-family; } description "Indicates whether IPv4, IPv6, or both are to be activated."; } leaf area-address { type area-address; mandatory true; description "Specifies an area address."; } } // Static routing grouping ipv4-static-rtg-entry { description "Parameters to configure a specific IPv4 static routing entry."; leaf lan { type inet:ipv4-prefix; description "Indicates an IPv4 LAN prefix."; } leaf lan-tag { type string; description "Internal tag to be used in service policies."; } leaf next-hop { type union { type inet:ip-address; type predefined-next-hop; } description "The next hop that is to be used for the static route. This may be specified as an IP address or a predefined next-hop type (e.g., 'discard' or 'local-link')."; } leaf metric { type uint32; description "Indicates the metric associated with the static route."; } } grouping ipv4-static-rtg { description "A set of parameters specific to IPv4 static routing."; list ipv4-lan-prefixes { if-feature "vpn-common:ipv4"; key "lan next-hop"; description "List of LAN prefixes for the site."; uses ipv4-static-rtg-entry; uses ac-common:service-status; } } grouping ipv6-static-rtg-entry { description "Parameters to configure a specific IPv6 static routing entry."; leaf lan { type inet:ipv6-prefix; description "Indicates an IPv6 LAN prefix."; } leaf lan-tag { type string; description "Internal tag to be used in service (e.g., VPN) policies."; } leaf next-hop { type union { type inet:ip-address; type predefined-next-hop; } description "The next hop that is to be used for the static route. This may be specified as an IP address or a predefined next-hop type (e.g., 'discard' or 'local-link')."; } leaf metric { type uint32; description "Indicates the metric associated with the static route."; } } grouping ipv6-static-rtg { description "A set of parameters specific to IPv6 static routing."; list ipv6-lan-prefixes { if-feature "vpn-common:ipv6"; key "lan next-hop"; description "List of LAN prefixes for the customer-terminating points."; uses ipv6-static-rtg-entry; uses ac-common:service-status; } } // OAM grouping bfd { description "Groups a set of basic BFD parameters."; leaf holdtime { type uint32; units "milliseconds"; description "Specifies the expected BFD holdtime. The customer may impose some fixed values for the holdtime period if the provider allows the customer to use this function. If the provider doesn't allow the customer to use this function, fixed values will not be set."; reference "RFC 5880: Bidirectional Forwarding Detection (BFD), Section 6.8.18"; } } // redundancy grouping redundancy-group { description "A grouping for redundancy group."; list group { key "group-id"; description "Specifies a list of group identifiers."; leaf group-id { type string; description "Indicates the group-id to which an AC belongs."; } leaf precedence { type identityref { base ac-common:precedence-type; } description "Defines redundancy of an AC."; } } } // QoS grouping bandwidth-parameters { description "A grouping for bandwidth parameters."; leaf cir { type uint64; units "bps"; description "Committed Information Rate (CIR). The maximum number of bits that a port can receive or send during one second over an interface."; } leaf cbs { type uint64; units "bytes"; description "Committed Burst Size (CBS). CBS controls the bursty nature of the traffic. Traffic that does not use the configured CIR accumulates credits until the credits reach the configured CBS."; } leaf eir { type uint64; units "bps"; description "Excess Information Rate (EIR), i.e., excess frame delivery allowed not subject to a Service Level Agreement (SLA). The traffic rate can be limited by EIR."; } leaf ebs { type uint64; units "bytes"; description "Excess Burst Size (EBS). The bandwidth available for burst traffic from the EBS is subject to the amount of bandwidth that is accumulated during periods when traffic allocated by the EIR policy is not used."; } leaf pir { type uint64; units "bps"; description "Peak Information Rate (PIR), i.e., maximum frame delivery allowed. It is equal to or less than the sum of the CIR and EIR."; } leaf pbs { type uint64; units "bytes"; description "Peak Burst Size (PBS)."; } } grouping bandwidth-per-type { description "Grouping for bandwidth per type."; list bandwidth { key "bw-type"; description "List for bandwidth per type parameters."; leaf bw-type { type identityref { base vpn-common:bw-type; } description "Indicates the bandwidth type."; } choice type { description "Choice based upon bandwidth type."; case per-cos { description "Bandwidth per Class of Service (CoS)."; list cos { key "cos-id"; description "List of CoSes."; leaf cos-id { type uint8; description "Identifier of the CoS, indicated by a Differentiated Services Code Point (DSCP) or a CE-CLAN CoS (802.1p) value in the service frame."; reference "IEEE Std 802.1Q: Bridges and Bridged Networks"; } uses bandwidth-parameters; } } case other { description "Other bandwidth types."; uses bandwidth-parameters; } } } } }

Security Considerations The "ietf-ac-common" YANG module defines a data model that is designed to be accessed via YANG-based management protocols, such as NETCONF and RESTCONF . These protocols have to use a secure transport layer (e.g., SSH , TLS , and QUIC ) and have to use mutual authentication. 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 YANG 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 YANG 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., 'ipv6-lan-prefixes' or 'ipv4-lan-prefixes'). Disclosing such information may be considered a violation of the customer-provider trust relationship. Several groupings ('bgp-authentication', 'ospf-authentication', 'isis-authentication', and 'rip-authentication') rely upon for authentication purposes. As such, modules that will reuse these groupings will inherit the security considerations discussed in . Also, these groupings support supplying explicit keys as strings in ASCII format. The use of keys in hexadecimal string format would afford greater key entropy with the same number of key-string octets. However, such a format is not included in this version of the common AC model, because it is not supported by the underlying device modules (e.g., ).

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-ac-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-ac-common

Maintained by IANA?

N

Namespace:

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

Prefix:

ac-common

Reference:

RFC 9833

References Normative References IEEE ISO/IEC This memo specifies an integrated routing protocol, based on the OSI Intra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a single routing protocol to be used to support pure IP environments, pure OSI environments, and dual environments. This specification was developed by the IS-IS working group of the Internet Engineering Task Force. [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 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 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 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 specifies a method for exchanging IPv6 routing information using the IS-IS routing protocol. The described method utilizes two new TLVs: a reachability TLV and an interface address TLV to distribute the necessary IPv6 information throughout a routing domain. Using this method, one can route IPv6 along with IPv4 and OSI using a single intra-domain routing protocol. [STANDARDS-TRACK] This document specifies the TCP Authentication Option (TCP-AO), which obsoletes the TCP MD5 Signature option of RFC 2385 (TCP MD5). TCP-AO specifies the use of stronger Message Authentication Codes (MACs), protects against replays even for long-lived TCP connections, and provides more details on the association of security with TCP connections than TCP MD5. TCP-AO is compatible with either a static Master Key Tuple (MKT) configuration or an external, out-of-band MKT management mechanism; in either case, TCP-AO also protects connections when using the same MKT across repeated instances of a connection, using traffic keys derived from the MKT, and coordinates MKT changes between endpoints. The result is intended to support current infrastructure uses of TCP MD5, such as to protect long-lived connections (as used, e.g., in BGP and LDP), and to support a larger set of MACs with minimal other system and operational changes. TCP-AO uses a different option identifier than TCP MD5, even though TCP-AO and TCP MD5 are never permitted to be used simultaneously. TCP-AO supports IPv6, and is fully compatible with the proposed requirements for the replacement of TCP MD5. [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] 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] This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. 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. Layer 2 services (such as Frame Relay, Asynchronous Transfer Mode, and Ethernet) can be emulated over an MPLS backbone by encapsulating the Layer 2 Protocol Data Units (PDUs) and then transmitting them over pseudowires (PWs). It is also possible to use pseudowires to provide low-rate Time-Division Multiplexed and Synchronous Optical NETworking circuit emulation over an MPLS-enabled network. This document specifies a protocol for establishing and maintaining the pseudowires, using extensions to the Label Distribution Protocol (LDP). Procedures for encapsulating Layer 2 PDUs are specified in other documents. This document is a rewrite of RFC 4447 for publication as an Internet Standard. This document describes the key chain YANG data model. Key chains are commonly used for routing protocol authentication and other applications requiring symmetric keys. A key chain is a list containing one or more elements containing a Key ID, key string, send/accept lifetimes, and the associated authentication or encryption algorithm. By properly overlapping the send and accept lifetimes of multiple key chain elements, key strings and algorithms may be gracefully updated. By representing them in a YANG data model, key distribution can be automated. 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. Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. 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. Informative References The Metro Ethernet Forum MEF Technical Specification The Metro Ethernet Forum MEF Technical Specification 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 presents an object-oriented information model for representing Quality of Service (QoS) network management policies. This document is based on the IETF Policy Core Information Model and its extensions. It defines an information model for QoS enforcement for differentiated and integrated services using policy. It is important to note that this document defines an information model, which by definition is independent of any particular data storage mechanism and access protocol. The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are described in separate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK] This document describes an updated version of the "Security Architecture for IP", which is designed to provide security services for traffic at the IP layer. This document obsoletes RFC 2401 (November 1998). [STANDARDS-TRACK] 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] This document describes means and mechanisms to provide authentication/confidentiality to OSPFv3 using an IPv6 Authentication Header/Encapsulating Security Payload (AH/ESP) extension header. [STANDARDS-TRACK] This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link. [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] This document describes a method for controlling two specific types of Ethernet switching via Generalized Multi-Protocol Label Switching (GMPLS). This document supports the types of switching corresponding to the Ethernet services that have been defined in the context of the Metro Ethernet Forum (MEF) and International Telecommunication Union (ITU) G.8011. Specifically, switching in support of Ethernet private line and Ethernet virtual private line services are covered. Support for MEF- and ITU-defined parameters is also covered. The framework for MPLS in transport networks (RFC 5921) provides reference models for the MPLS Transport Profile (MPLS-TP) Transport Service Interfaces, which are a User-to-Network Interface (UNI), and a Network-to-Network Interface (NNI). This document updates those reference models to show detailed reference points for these interfaces, along with further clarification of the functional architecture of MPLS-TP at a UNI and NNI. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge (PWE3) architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T. This document is not an Internet Standards Track specification; it is published for informational purposes. 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 an architecture for the specification, creation, and ongoing maintenance of Service Function Chains (SFCs) in a network. It includes architectural concepts, principles, and components used in the construction of composite services through deployment of SFCs, with a focus on those to be standardized in the IETF. This document does not propose solutions, protocols, or extensions to existing protocols. 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 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 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 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 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 describes a data model for the management of the Routing Information Protocol (RIP). Both RIP version 2 and RIPng are covered. The data model includes definitions for configuration, operational state, and Remote Procedure Calls (RPCs). The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA). Data models provide a programmatic approach to represent services and networks. Concretely, they can be used to derive configuration information for network and service components, and state information that will be monitored and tracked. Data models can be used during the service and network management life cycle (e.g., service instantiation, service provisioning, service optimization, service monitoring, service diagnosing, and service assurance). Data models are also instrumental in the automation of network management, and they can provide closed-loop control for adaptive and deterministic service creation, delivery, and maintenance. This document describes a framework for service and network management automation that takes advantage of YANG modeling technologies. This framework is drawn from a network operator perspective irrespective of the origin of a data model; thus, it can accommodate YANG modules that are developed outside the IETF. This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. As a complement to the Layer 3 Virtual Private Network Service Model (L3SM), which is used for communication between customers and service providers, this document defines an L3VPN Network Model (L3NM) that can be used for the provisioning of Layer 3 Virtual Private Network (L3VPN) services within a service provider network. The model provides a network-centric view of L3VPN services. The L3NM is meant to be used by a network controller to derive the configuration information that will be sent to relevant network devices. The model can also facilitate communication between a service orchestrator and a network controller/orchestrator. Route leaks are the propagation of BGP prefixes that violate assumptions of BGP topology relationships, e.g., announcing a route learned from one transit provider to another transit provider or a lateral (i.e., non-transit) peer or announcing a route learned from one lateral peer to another lateral peer or a transit provider. These are usually the result of misconfigured or absent BGP route filtering or lack of coordination between autonomous systems (ASes). Existing approaches to leak prevention rely on marking routes by operator configuration, with no check that the configuration corresponds to that of the External BGP (eBGP) neighbor, or enforcement of the two eBGP speakers agreeing on the peering relationship. This document enhances the BGP OPEN message to establish an agreement of the peering relationship on each eBGP session between autonomous systems in order to enforce appropriate configuration on both sides. Propagated routes are then marked according to the agreed relationship, allowing both prevention and detection of route leaks. This document defines an L2VPN Network Model (L2NM) that can be used to manage the provisioning of Layer 2 Virtual Private Network (L2VPN) services within a network (e.g., a service provider network). The L2NM complements the L2VPN Service Model (L2SM) by providing a network-centric view of the service that is internal to a service provider. The L2NM is particularly meant to be used by a network controller to derive the configuration information that will be sent to relevant network devices. Also, this document defines a YANG module to manage Ethernet segments and the initial versions of two IANA-maintained modules that include a set of identities of BGP Layer 2 encapsulation types and pseudowire types. This document defines a YANG data model for representing an abstract view of the provider network topology that contains the points from which its services can be attached (e.g., basic connectivity, VPN, network slices). Also, the model can be used to retrieve the points where the services are actually being delivered to customers (including peer networks). This document augments the 'ietf-network' data model defined in RFC 8345 by adding the concept of Service Attachment Points (SAPs). The SAPs are the network reference points to which network services, such as Layer 3 Virtual Private Network (L3VPN) or Layer 2 Virtual Private Network (L2VPN), can be attached. One or multiple services can be bound to the same SAP. Both User-to-Network Interface (UNI) and Network-to-Network Interface (NNI) are supported in the SAP data model. Orange Juniper Telefonica Nokia Huawei Technologies Orange Juniper Telefonica Nokia Huawei Technologies Orange Juniper Nokia Telefonica Huawei Technologies Huawei Technologies Ciena Cisco Systems, Inc Cisco Systems, Inc This document defines a YANG data model for RFC 9543 Network Slice Service. The model can be used in the Network Slice Service interface between a customer and a provider that offers RFC 9543 Network Slice Services. Work in Progress Huawei Huawei Orange Lancaster University Work in Progress

Full Tree module: ietf-ac-common grouping service-status: +-- status +-- admin-status | +-- status? identityref | +--ro last-change? yang:date-and-time +--ro oper-status +--ro status? identityref +--ro last-change? yang:date-and-time grouping ac-profile-cfg: +-- valid-provider-identifiers +-- encryption-profile-identifier* [id] | +-- id string +-- qos-profile-identifier* [id] | +-- id string +-- failure-detection-profile-identifier* [id] | +-- id string +-- forwarding-profile-identifier* [id] | +-- id string +-- routing-profile-identifier* [id] +-- id string grouping op-instructions: +-- requested-start? yang:date-and-time +-- requested-stop? yang:date-and-time +--ro actual-start? yang:date-and-time +--ro actual-stop? yang:date-and-time grouping dot1q: +-- tag-type? identityref +-- cvlan-id? uint16 grouping priority-tagged: +-- tag-type? identityref grouping qinq: +-- tag-type? identityref +-- svlan-id uint16 +-- cvlan-id uint16 grouping pseudowire: +-- vcid? uint32 +-- far-end? union grouping vpls: +-- vcid? uint32 +-- far-end* union grouping vxlan: +-- vni-id uint32 +-- peer-mode? identityref +-- peer-ip-address* inet:ip-address grouping l2-tunnel-service: +-- type? identityref +-- pseudowire | +-- vcid? uint32 | +-- far-end? union +-- vpls | +-- vcid? uint32 | +-- far-end* union +-- vxlan +-- vni-id uint32 +-- peer-mode? identityref +-- peer-ip-address* inet:ip-address grouping ipv4-allocation-type: +-- prefix-length? uint8 +-- address-allocation-type? identityref grouping ipv6-allocation-type: +-- prefix-length? uint8 +-- address-allocation-type? identityref grouping ipv4-connection-basic: +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) +-- (provider-dhcp)? | +--:(dhcp-service-type) | +-- dhcp-service-type? enumeration +-- (dhcp-relay)? +--:(customer-dhcp-servers) +-- customer-dhcp-servers +-- server-ip-address* inet:ipv4-address grouping ipv6-connection-basic: +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) +-- (provider-dhcp)? | +--:(dhcp-service-type) | +-- dhcp-service-type? enumeration +-- (dhcp-relay)? +--:(customer-dhcp-servers) +-- customer-dhcp-servers +-- server-ip-address* inet:ipv6-address grouping ipv4-connection: +-- local-address? inet:ipv4-address +-- virtual-address? inet:ipv4-address +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) | +-- (address-assign)? | | +--:(number) | | | +-- number-of-dynamic-address? uint16 | | +--:(explicit) | | +-- customer-addresses | | +-- address-pool* [pool-id] | | +-- pool-id string | | +-- start-address inet:ipv4-address | | +-- end-address? inet:ipv4-address | +-- (provider-dhcp)? | | +--:(dhcp-service-type) | | +-- dhcp-service-type? enumeration | +-- (dhcp-relay)? | +--:(customer-dhcp-servers) | +-- customer-dhcp-servers | +-- server-ip-address* inet:ipv4-address +--:(static-addresses) +-- address* [address-id] +-- address-id string +-- customer-address? inet:ipv4-address grouping ipv6-connection: +-- local-address? inet:ipv6-address +-- virtual-address? inet:ipv6-address +-- prefix-length? uint8 +-- address-allocation-type? identityref +-- (allocation-type)? +--:(dynamic) | +-- (address-assign)? | | +--:(number) | | | +-- number-of-dynamic-address? uint16 | | +--:(explicit) | | +-- customer-addresses | | +-- address-pool* [pool-id] | | +-- pool-id string | | +-- start-address inet:ipv6-address | | +-- end-address? inet:ipv6-address | +-- (provider-dhcp)? | | +--:(dhcp-service-type) | | +-- dhcp-service-type? enumeration | +-- (dhcp-relay)? | +--:(customer-dhcp-servers) | +-- customer-dhcp-servers | +-- server-ip-address* inet:ipv6-address +--:(static-addresses) +-- address* [address-id] +-- address-id string +-- customer-address? inet:ipv6-address grouping bgp-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(ao) | +-- enable-ao? boolean | +-- ao-keychain? key-chain:key-chain-ref +--:(md5) | +-- md5-keychain? key-chain:key-chain-ref +--:(explicit) +-- key-id? uint32 +-- key? string +-- crypto-algorithm? identityref grouping ospf-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(auth-key-chain) | +-- key-chain? key-chain:key-chain-ref +--:(auth-key-explicit) +-- key-id? uint32 +-- key? string +-- crypto-algorithm? identityref grouping isis-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(auth-key-chain) | +-- key-chain? key-chain:key-chain-ref +--:(auth-key-explicit) +-- key-id? uint32 +-- key? string +-- crypto-algorithm? identityref grouping rip-authentication: +-- authentication +-- enabled? boolean +-- keying-material +-- (option)? +--:(auth-key-chain) | +-- key-chain? key-chain:key-chain-ref +--:(auth-key-explicit) +-- key? string +-- crypto-algorithm? identityref grouping bgp-peer-group-without-name: +-- local-as? inet:as-number +-- peer-as? inet:as-number +-- address-family? identityref +-- role? identityref grouping bgp-peer-group-with-name: +-- name? string +-- local-as? inet:as-number +-- peer-as? inet:as-number +-- address-family? identityref +-- role? identityref grouping ospf-basic: +-- address-family? identityref +-- area-id yang:dotted-quad +-- metric? uint16 grouping isis-basic: +-- address-family? identityref +-- area-address area-address grouping ipv4-static-rtg-entry: +-- lan? inet:ipv4-prefix +-- lan-tag? string +-- next-hop? union +-- metric? uint32 grouping ipv4-static-rtg: +-- ipv4-lan-prefixes* [lan next-hop] {vpn-common:ipv4}? +-- lan inet:ipv4-prefix +-- lan-tag? string +-- next-hop union +-- metric? uint32 +-- status +-- admin-status | +-- status? identityref | +--ro last-change? yang:date-and-time +--ro oper-status +--ro status? identityref +--ro last-change? yang:date-and-time grouping ipv6-static-rtg-entry: +-- lan? inet:ipv6-prefix +-- lan-tag? string +-- next-hop? union +-- metric? uint32 grouping ipv6-static-rtg: +-- ipv6-lan-prefixes* [lan next-hop] {vpn-common:ipv6}? +-- lan inet:ipv6-prefix +-- lan-tag? string +-- next-hop union +-- metric? uint32 +-- status +-- admin-status | +-- status? identityref | +--ro last-change? yang:date-and-time +--ro oper-status +--ro status? identityref +--ro last-change? yang:date-and-time grouping bfd: +-- holdtime? uint32 grouping redundancy-group: +-- group* [group-id] +-- group-id string +-- precedence? identityref grouping bandwidth-parameters: +-- cir? uint64 +-- cbs? uint64 +-- eir? uint64 +-- ebs? uint64 +-- pir? uint64 +-- pbs? uint64 grouping bandwidth-per-type: +-- bandwidth* [bw-type] +-- bw-type identityref +-- (type)? +--:(per-cos) | +-- cos* [cos-id] | +-- cos-id uint8 | +-- cir? uint64 | +-- cbs? uint64 | +-- eir? uint64 | +-- ebs? uint64 | +-- pir? uint64 | +-- pbs? uint64 +--:(other) +-- cir? uint64 +-- cbs? uint64 +-- eir? uint64 +-- ebs? uint64 +-- pir? uint64 +-- pbs? uint64

Acknowledgments The document reuses many of the structures that were defined in and . Thanks to for the YANG Doctors review, and for the RTGDIR reviews, for the SECDIR review, and for the GENART review. Thanks to for the shepherd review. Thanks to for the AD review. Thanks to , , , and for the IESG review.

Contributors Nokia

victor.lopez@nokia.com

Ribbon Communications

Ivan.Bykov@rbbn.com

Huawei

bill.wu@huawei.com

KDDI

ke-oogaki@kddi.com

Vodafone

luis-angel.munoz@vodafone.com

Authors' Addresses Orange

mohamed.boucadair@orange.com

Juniper

rroberts@juniper.net

Telefonica

oscar.gonzalezdedios@telefonica.com

Nokia

samier.barguil_giraldo@nokia.com

Huawei Technologies

lana.wubo@huawei.com