]> A YANG Data Model for Transport Network Client Signals Huawei Technologies
H1 XiliuBeipo Village, Songshan Lake Dongguan Guangdong China zhenghaomian@huawei.com
Futurewei
aihuaguo.ietf@gmail.com
Huawei Technologies
italo.busi@huawei.com
Cisco
asnizar@cisco.com
Huawei Technologies
yuchaode@huawei.com
Routing CCAMP Working Group next generation unicorn sparkling distributed ledger A transport network is a server-layer network to provide connectivity services to its client. The topology and tunnel information in the transport layer has already been defined by generic Traffic- engineered models and technology-specific models (e.g., OTN, WSON). However, how the client signals are accessing to the network has not been described. These information is necessary to both client and provider. This draft describes how the client signals are carried over transport network and defines YANG data models which are required during configuration procedure. More specifically, several client signal (of transport network) models including ETH, STM-n, FC and so on, are defined in this draft. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Common Control and Measurement Plane Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .
Introduction
Overview A transport network is a server-layer network designed to provide connectivity services for a client-layer network to carry the client traffic transparently across the server-layer network resources. Currently the topology and tunnel models have been defined for transport networks, including and , providing server-layer topology abstraction and tunnel configuration between PEs. However, there is a missing piece for configuring how the PEs should map the client- layer traffic, received from the CE, over the server-layer tunnels: this gap is expected to be solved in this document. This document defines a data model of all transport network client signals, using YANG language defined in . The model can be used by applications exposing to a transport network controller via a RESTconf interface. Furthermore, it can be used by an application for the following purposes (but not limited to):
  • To request/update an end-to-end service by driving a new tunnel to be set up to support this service;
  • To request/update an end-to-end service by using an existing tunnel;
  • To receive notification with regard to the information change of the given service;
The YANG modules defined in this document conforms to the Network Management Datastore Architecture (NMDA) defined in .
Conventions and Definitions
Prefixes in Model Names In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, including , and , which are shown as follow. Prefixes and corresponding YANG modules
Prefix YANG module Reference
yang ietf-yang-types
rt-types ietf-routing-types
te-types ietf-te-types [RFCYYYY]
l1-types ietf-layer1-types [RFCZZZZ]
nw ietf-network
nt ietf-network-topology
te ietf-te [RFCKKKK]
clnt-types ietf-trans-client-svc-types RFC XXXX
etht-types ietf-eth-tran-types RFC XXXX
clnt-svc ietf-trans-client-service RFC XXXX
etht-svc ietf-eth-tran-service RFC XXXX
RFC Editor Note: Please replace XXXX with the number assigned to the RFC once this draft becomes an RFC. Please replace YYYY with the RFC numbers assigned to . Please replace ZZZZ with the RFC numbers assigned to . Please replace KKKK with the RFC numbers assigned to .
Terminology and Notations A simplified graphical representation of the data model is used in this document. The meaning of the symbols in the YANG data tree presented later in this document is defined in . They are provided below for reference.
  • Brackets "[" and "]" enclose list keys.
  • Abbreviations before data node names: "rw" means configuration (read-write) and "ro" state data (read-only).
  • Symbols after data node names: "?" means an optional node, "!" means a presence container, and "*" denotes a list and leaf-list.
  • Parentheses enclose choice and case nodes, and case nodes are also marked with a colon (":").
  • Ellipsis ("...") stands for contents of subtrees that are not shown.
Transport Network Client Signal Overview
Overview of Service Request and Network Configuration Scenarios A global view of a multi-domain service can be described as the . The customer is usually responsible to configure the CE nodes and to request to the provider the service intent, from the CE nodes perspective, while the provider is responsible to configure the whole network (including the PE nodes) to support the customer service intent. Generally speaking, the network configurations required to support a customer service can be split into two different groups: CE-PE and PE-PE. The CE-PE configuration deals with the client layer one-hop access link, while PE-PE configuration deals with the server layer tunnel. In we mark the intermediate nodes as 'P', which has same switching capability of PE but just not the 'end-point'. In this example, the link P-P and PE-P are a server-layer intra-domain or inter-domain link.
Global view of Client Service with the Network Provider
According to the responsibilities of each controller in , the controllers have different views of the service request and network configuration. The duty of CNC is to give the MDSC a description of the customer service intent: candidate YANG models include L1CSM , L2SM and L3SM , which are classified as customer service models, according to . These models provide necessary attributes to describe the customer service intent from the customer/CE perspective, and do not provide any specific network configuration. These models also implies that the customer service description can be considered in a separate manner rather than integratig with network configurations, which also enable the controllers to abstract/virtualize the network resource to make them visible to the customer and also easier to manage. In other words, the network knowledge is not necessary at CNC and CMI, which is seen in an abstracted form as shown in .
CNC Viewpoint on the Client Service
The functionalities of MDSC have been described in , which include the customer mapping/translation and multi-domain coordination. By receiving the request from CNC, MDSC need to understand what network configuration can support the customer service intent and turn to the corresponding PNCs for configuration. The service request is therefore decomposed by MDSC into a few network configurations and forwarded to one or multiple PNCs respectively in single-domain and multi-domain scenario. In general, the MDSC has the view of both PE and CE nodes and of some abstract information regarding the P nodes, as shown in . It is worth noting that this MDSC view is different with at the intra- domain link. Usually these details are hidden, for scalability purposes, and therefore the MDSC has only an abstract view of each domain internal topology.
MDSC view of both Client Service and Network Abstraction
PNC is the controller that configure the physical devices, based on the network configuration received from the MDSC. Each PNC has the detailed view of its own domain, the example of view from PNC in domain 1 is shown in . The PNC has all the detailed topology information on PE and P nodes and on the intra-domain links. The PNC configures the tunnel/tunnel segment within its domain based on the network configuration provided by the MDSC. The PNC also configures the network part of the CE-PE access links as well as the mapping of the client-layer traffic and the server-layer tunnels, based on the network configuration provided by the MDSC. The interaction between PNC and MDSC for the client-layer network configuration is accomplished by the models defined in this draft.
PNC view on Network Configuration
Applicability of Proposed Model Existing TE and technology-specific models, such as topology models and tunnel models, support the network configuration among PEs and Ps. The customer service models, such as L1CSM, L2SM and L3SM, focus on describing the attributes among CEs. However, there is a missing piece on how to configure the CE-PE session. The models defined in this document provide the configuration on CE-PE when the provider server-layer network is TE-based technology. In the example of OTN as the server-layer transport network, a full list of G-PID was summarized in , which can be divided into a few categories. The G-PID signals can be categorized into transparent and non-transparent. Examples of transparent signals may include Ethernetphysical interfaces, FC, STM-n and so on. In this approach the OTN devices is not aware of the client signal type, and this information is only necessary among the controllers. Once the OTN tunnel is set up, there is no switching requested on the client layer, and therefore only signal mapping is needed, without a client tunnel set up. The models that supporting the configuration of transparent signals are defined in . The other category would be non-transparent, such as Carrier Ethernet and MPLS-TP, with a switching request on the client layer. Once the OTN tunnel is set up, a corresponding tunnel in the client layer has to be set up to carry services. The models that supporting the configuration of transparent signals are defined in . It is also worth noting that some client signal can be carried over multiple types of networks. For example, the Ethernet services can be carried over either OTN or Ethernet TE tunnels (over optical or microwave networks). The model specified in this document allows the support from networks with different technologies. The list of identities for client signals are defined in .
Identifier and Readable Information Name: The identifier of the client signal service can be configured or retrieved by the name information. The naming of this attribute is based on the requirements of unifying with TE tunnel models. It can be readable or unreadable. If it is readable, to make it unique, it is needed to specify a unified structure for all the PNC systems. It is hard to do that for the reason of a lot of customized requirements from different Operators. In the ICT technology, UUID format could be a good option. Title: The title of client signal service can be configured with its readable name. Description: More detail information of client signal service, such as some administrative information or location information. User-label: An alias of client signal service which is used to tag based on the maintenance requirement.
Unified Resource Identifiers In , it is recognized that if the used topology resource adopts TE modeling, there could be two identifier systems, one is the network modeling system and the other one from TE topology modeling. The access ports of client signal service or end points of Ethernet service also adopt the TE topology resources. So two identifiers are both fine to specified in the configuration requests.
Threshold Configuration Some PM data are quite critical for client signal service users' experience, e.g. latency value. For the Operators, they can configure a service-oriented threshold for the PM data, to make the maintenance engineer recognize the network issues in time.
State data of Services
Generic Requirements States have been defined to retrieve the status of the delivered services. A few generic states defined in are reused in this document. These states include the operational state and the provisioning state.
Timestamp and Administrative information A few other parameters are defined for the management of the services. Given the complicated labor division, the creation, update and maintainance may have different responsible systems. So the log of the service would be helpful and should be easy to retrived in a standard way as well. These information include, but not restricted to the following:
  • When the service is created and has been last updated, these are specified in the creation-time and last-updated-time.
  • Who created the service and who made the last update to the service, these are specified in the created-by and last-updated- by.
  • The owner of the service is specifed as owned-by, which would be useful when the service is delegated by or to a specific system. The identifier of the system is used to represent such information.
performance monitoring status For the Operators, there are also some requirements to provide some PM data to the service users. Especially some PM data are quite critical for users' experience. For example, one of the great advantage of client signal service is it can provide deterministic low latency. Some industry users, e.g. stock trading company, have great demand of stable short latency service to ensure their high-frequency fast trading operations can be finished quickly and definitely. In addition to provision a low- latency client signal service, Operators can also provide some other differentiated services for these kinds of service users. For example latency visibility can be provided to the users, to let them monitor the latency values. The latency measurement mechanism can be referenced from sub-clause 7.10.1 of . And PNC can provide a measurement latency after service is provisioned if the devices support this measurement mechanism. Otherwise providing an estimated value could be a workaround solution.
Error Message Report Once the processing of client signal service configuration, including creation, updating, deletion, meets with some internal problems, such as no enough available bandwidth, or wrong client signal mapping .etc., the problems should be reported to the client system to make the issues read by the maintenance engineers. Since these error messages are more technologies-specific, especially sometimes accurate location information is needed in these messages, it is hard to standardize these error messages by RESTCONF protocol errors. For the client systems, they would like to get these messages both from notifications and retrieval. So this document defines an error container in the YANG data model to let the PNC to provide these messages.
YANG Model for Transport Network Client Signal
YANG Tree for Ethernet Service
/te:te/tunnels/tunnel/name | | | +--rw encoding? identityref | | | +--rw switching-type? identityref | | +--:(frame-base) | | | +--rw otn-tunnels* [name] | | | +--rw name | | | | -> /te:te/tunnels/tunnel/name | | | +--rw encoding? identityref | | | +--rw switching-type? identityref | | +--:(mpls-tp) | | +--rw pw | | +--rw pw-id? string | | +--rw pw-name? string | | +--rw transmit-label? | | | rt-types:mpls-label | | +--rw receive-label? | | | rt-types:mpls-label | | +--rw encapsulation-type? identityref | | +--ro oper-status? identityref | | +--rw ingress-bandwidth-profile | | | +--rw (style)? | | | +--:(named) | | | | +--rw bandwidth-profile-name? leafref | | | +--:(value) | | | +--rw bandwidth-profile-type? | | | | etht-types:bandwidth-profile-ty\ pe | | | +--rw CIR? uint64 | | | +--rw CBS? uint64 | | | +--rw EIR? uint64 | | | +--rw EBS? uint64 | | +--rw pw-paths* [path-id] | | +--rw path-id uint8 | | +--rw tp-tunnels* [name] | | +--rw name string | +--rw src-split-horizon-group? string | +--rw dst-split-horizon-group? string +--rw admin-status? identityref +--ro state +--ro operational-state? identityref +--ro provisioning-state? identityref +--ro creation-time? yang:date-and-time +--ro last-updated-time? yang:date-and-time +--ro created-by? string +--ro last-updated-by? string +--ro owned-by? string +--ro pm-state | +--ro latency? uint32 +--ro error-info +--ro error-code? uint16 +--ro error-description? string +--ro error-timestamp? yang:date-and-time ]]>
YANG Tree for other Transport Network Client Signal Model
YANG Code for Transport Network Client Signal
The ETH Service YANG Code This module imports typedefs and modules from , , .
WG List: Editor: Haomian Zheng Editor: Aihua Guo Editor: Italo Busi Editor: Anton Snitser Editor: Chaode Yu "; description "This module defines a YANG data model for describing Ethernet transport network client services. The model fully conforms to the Network Management Datastore Architecture (NMDA). Copyright (c) 2024 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 XXXX; see the RFC itself for full legal notices."; revision 2024-01-11 { description "Initial Version"; reference "RFC XXXX: A YANG Data Model for Transport Network Client Signals"; } // RFC Editor: replace XXXX with the actual RFC number assigned // to the RFC once this draft // becomes an RFC, update date information and remove this note. /* * Groupings */ grouping vlan-classification { description "A grouping which represents classification on an 802.1Q VLAN tag."; leaf tag-type { type etht-types:eth-tag-classify; description "The tag type used for VLAN classification."; } choice individual-bundling-vlan { description "VLAN based classification can be individual or bundling."; case individual-vlan { leaf vlan-value { type etht-types:vlanid; description "VLAN ID value."; } } case vlan-bundling { leaf vlan-range { type etht-types:vid-range-type; description "List of VLAN ID values."; } } } } grouping vlan-write { description "A grouping which represents push/pop operations of an 802.1Q VLAN tag."; leaf tag-type { type etht-types:eth-tag-type; description "The VLAN tag type to push/swap."; } leaf vlan-value { type etht-types:vlanid; description "The VLAN ID value to push/swap."; } /* * To be added: this attribute is used when: * a) the ETH service has only one CoS (as in current version) * b) as a default when a mapping between a given CoS value * and the PCP value is not defined (in future versions) */ leaf default-pcp { type uint8 { range "0..7"; } description "The default Priority Code Point (PCP) value to push/swap"; } } grouping vlan-operations { description "A grouping which represents VLAN operations."; leaf pop-tags { type uint8 { range "1..2"; } description "The number of VLAN tags to pop (or swap if used in conjunction with push-tags)"; } container push-tags { description "The VLAN tags to push (or swap if used in conjunction with pop-tags)"; container outer-tag { presence "Indicates existence of the outermost VLAN tag to push/swap"; description "The outermost VLAN tag to push/swap."; uses vlan-write; } container second-tag { must '../outer-tag/tag-type = "etht-types:s-vlan-tag-type" and ' + 'tag-type = "etht-types:c-vlan-tag-type"' { error-message " When pushing/swapping two tags, the outermost tag must be specified and of S-VLAN type and the second outermost tag must be of C-VLAN tag type. "; description " For IEEE 802.1Q interoperability, when pushing/swapping two tags, it is required that the outermost tag exists and is an S-VLAN, and the second outermost tag is a C-VLAN. "; } presence "Indicates existence of a second outermost VLAN tag to push/swap"; description "The second outermost VLAN tag to push/swap."; uses vlan-write; } } } grouping named-or-value-bandwidth-profile { description "A grouping to configure a bandwdith profile either by referencing a named bandwidth profile or by configuring the values of the bandwidth profile attributes."; choice style { description "Whether the bandwidth profile is named or defined by value"; case named { description "Named bandwidth profile."; leaf bandwidth-profile-name { type leafref { path "/etht-svc:etht-svc/etht-svc:globals/" + "etht-svc:named-bandwidth-profiles/" + "etht-svc:bandwidth-profile-name"; } description "Name of the bandwidth profile."; } } case value { description "Bandwidth profile configured by value."; uses etht-types:etht-bandwidth-profiles; } } } grouping bandwidth-profiles { description "A grouping which represent bandwidth profile configuration."; choice direction { description "Whether the bandwidth profiles are symmetrical or asymmetrical"; case symmetrical { description "The same bandwidth profile is used to describe both the ingress and the egress bandwidth profile."; container ingress-egress-bandwidth-profile { description "The bandwdith profile used in both directions."; uses named-or-value-bandwidth-profile; } } case asymmetrical { description "Ingress and egress bandwidth profiles can be specified."; container ingress-bandwidth-profile { description "The bandwdith profile used in the ingress direction."; uses named-or-value-bandwidth-profile; } container egress-bandwidth-profile { description "The bandwdith profile used in the egress direction."; uses named-or-value-bandwidth-profile; } } } } grouping etht-svc-access-parameters { description "ETH services access parameters"; leaf access-node-id { type te-types:te-node-id; description "The identifier of the access node in the ETH TE topology."; } leaf access-node-uri { type nw:node-id; description "The identifier of the access node in the network."; } leaf access-ltp-id { type te-types:te-tp-id; description "The TE link termination point identifier, used together with access-node-id to identify the access LTP."; } leaf access-ltp-uri { type nt:tp-id; description "The link termination point identifier in network topology, used together with access-node-uri to identify the access LTP."; } leaf access-role { type identityref { base etht-types:access-role; } description "Indicate the role of access, e.g., working or protection. "; } container pm-config { uses pm-config-grouping; description "This grouping is used to set the threshold value for performance monitoring. "; } container state { config false; description "The state is used to monitor the status of service. "; leaf operational-state { type identityref { base te-types:tunnel-state-type; } description "Indicating the operational state of client signal. "; } leaf provisioning-state { type identityref { base te-types:lsp-state-type; } description "Indicating the provisional state of client signal, especially when there is a change, i.e., revise, create. "; } } leaf performance { type identityref { base etht-types:performance; } config false; description "Performance Monitoring for the service. "; } } grouping etht-svc-tunnel-parameters { description "ETH services tunnel parameters."; choice technology { description "Service multiplexing is optional and flexible."; case native-ethernet { /* placeholder to support proprietary multiplexing (for further discussion) */ list eth-tunnels { key name; description "ETH Tunnel list in native Ethernet scenario."; uses tunnels-grouping; } } case frame-base { list otn-tunnels { key name; description "OTN Tunnel list in Frame-based scenario."; uses tunnels-grouping; } } case mpls-tp { container pw { description "Pseudowire information for Ethernet over MPLS-TP."; uses pw-segment-grouping; } } } /* * Open issue: * can we constraints it to be used only with mp services? */ leaf src-split-horizon-group { type string; description "Identify a split horizon group at the source Tunnel Termination Point (TTP)."; } leaf dst-split-horizon-group { type string; description "Identify a split horizon group at the destination Tunnel Termination Point (TTP)."; } } grouping etht-svc-pm-threshold-config { description "Configuraiton parameters for Ethernet service PM thresholds."; leaf sending-rate-high { type uint64; description "High threshold of packet sending rate in kbps."; } leaf sending-rate-low { type uint64; description "Low threshold of packet sending rate in kbps."; } leaf receiving-rate-high { type uint64; description "High threshold of packet receiving rate in kbps."; } leaf receiving-rate-low { type uint64; description "Low threshold of packet receiving rate in kbps."; } } grouping etht-svc-pm-stats { description "Ethernet service PM statistics."; leaf sending-rate-too-high { type uint32; description "Counter that indicates the number of times the sending rate is above the high threshold"; } leaf sending-rate-too-low { type uint32; description "Counter that indicates the number of times the sending rate is below the low threshold"; } leaf receiving-rate-too-high { type uint32; description "Counter that indicates the number of times the receiving rate is above the high threshold"; } leaf receiving-rate-too-low { type uint32; description "Counter that indicates the number of times the receiving rate is below the low threshold"; } } grouping etht-svc-instance-config { description "Configuraiton parameters for Ethernet services."; leaf etht-svc-name { type string; description "Name of the ETH service."; } leaf etht-svc-title { type string; description "The Identifier of the ETH service."; } leaf user-label { type string; description "Alias of the ETH service."; } leaf etht-svc-descr { type string; description "Description of the ETH service."; } leaf etht-svc-customer { type string; description "Customer of the ETH service."; } leaf etht-svc-type { type etht-types:service-type; description "Type of ETH service (p2p, mp2mp or rmp)."; /* Add default as p2p */ } leaf etht-svc-lifecycle { type etht-types:lifecycle-status; description "Lifecycle state of ETH service."; /* Add default as installed */ } uses te-types:te-topology-identifier; uses resilience-grouping; list etht-svc-end-points { key etht-svc-end-point-name; description "The logical end point for the ETH service. "; uses etht-svc-end-point-grouping; } container alarm-threshold { description "threshold configuration for the E2E client signal"; uses alarm-threshold-grouping; } container underlay { description "The unterlay tunnel information that carrying the ETH service. "; uses etht-svc-tunnel-parameters; } leaf admin-status { type identityref { base te-types:tunnel-admin-state-type; } default te-types:tunnel-admin-state-up; description "ETH service administrative state."; } } grouping etht-svc-instance-state { description "State parameters for Ethernet services."; leaf operational-state { type identityref { base te-types:tunnel-state-type; } default te-types:tunnel-state-up; description "ETH service operational state."; } leaf provisioning-state { type identityref { base te-types:lsp-state-type; } description "ETH service provisioning state."; } leaf creation-time { type yang:date-and-time; description "Time of ETH service creation."; } leaf last-updated-time { type yang:date-and-time; description "Time of ETH service last update."; } leaf created-by { type string; description "The client signal is created by whom, can be a system or staff ID."; } leaf last-updated-by { type string; description "The client signal is last updated by whom, can be a system or staff ID."; } leaf owned-by { type string; description "The client signal is last updated by whom, can be a system ID."; } container pm-state { description "PM data of E2E Ethernet service"; uses pm-state-grouping; } container error-info { description "error messages of configuration"; uses error-info-grouping; } } grouping pm-state-grouping { description "Performance Monitoring (PM) state attributes"; leaf latency { type uint32; units microsecond; description "latency value of the E2E Ethernet service"; } } grouping error-info-grouping { description "Error information parameters"; leaf error-code { type uint16; description "error code"; } leaf error-description { type string; description "detail message of error"; } leaf error-timestamp { type yang:date-and-time; description "the date and time error is happened"; } } grouping alarm-threshold-grouping { description "Alarm threshold parameters."; leaf latency-threshold { type uint32; units microsecond; description "a threshold for the E2E client signal service's latency. Once the latency value exceed this threshold, an alarm should be triggered."; } } grouping resilience-grouping { description "Grouping for resilience configuration. "; container resilience { description "To configure the data plane protection parameters, currently a placeholder only, future candidate attributes include, Revert, WTR, Hold-off Timer, ..."; uses te:protection-restoration-properties; } } grouping etht-svc-end-point-grouping { description "Grouping for the end point configuration."; leaf etht-svc-end-point-name { type string; description "The name of the logical end point of ETH service. "; } leaf etht-svc-end-point-id { type string; description "The identifier of the logical end point of ETH service."; } leaf etht-svc-end-point-descr { type string; description "The description of the logical end point of ETH service. "; } leaf topology-role { type identityref { base etht-types:topology-role; } description "Indicating the underlay topology role, e.g., hub,spoke, any-to-any "; } container resilience { description "Placeholder for resilience configuration, for future study."; } list etht-svc-access-points { key access-point-id; min-elements "1"; /* Open Issue: Is it possible to limit the max-elements only for p2p services? max-elements "2"; */ description "List of the ETH trasport services access point instances."; leaf access-point-id { type string; description "ID of the service access point instance"; } uses etht-svc-access-parameters; } leaf service-classification-type { type identityref { base etht-types:service-classification-type; } description "Service classification type."; } choice service-classification { description "Access classification can be port-based or VLAN based."; case port-classification { /* no additional information */ } case vlan-classification { container outer-tag { presence "The outermost VLAN tag exists"; description "Classifies traffic using the outermost VLAN tag."; uses vlan-classification; } container second-tag { must '../outer-tag/tag-type = "etht-types:classify-s-vlan"' + ' and tag-type = "etht-types:classify-c-vlan"' { error-message " When matching two tags, the outermost tag must be specified and of S-VLAN type and the second outermost tag must be of C-VLAN tag type. "; description " For IEEE 802.1Q interoperability, when matching two tags, it is required that the outermost tag exists and is an S-VLAN, and the second outermost tag is a C-VLAN. "; } presence "The second outermost VLAN tag exists"; description "Classifies traffic using the second outermost VLAN tag."; uses vlan-classification; } } } /* * Open issue: * can we constraints it to be used only with mp services? */ leaf split-horizon-group { type string; description "Identify a split horizon group"; } uses bandwidth-profiles; container vlan-operations { description "Configuration of VLAN operations."; choice direction { description "Whether the VLAN operations are symmetrical or asymmetrical"; case symmetrical { container symmetrical-operation { uses vlan-operations; description "Symmetrical operations. Expressed in the ingress direction, but the reverse operation is applied to egress traffic"; } } case asymmetrical { container asymmetrical-operation { description "Asymmetrical operations"; container ingress { uses vlan-operations; description "Ingress operations"; } container egress { uses vlan-operations; description "Egress operations"; } } } } } } grouping pm-config-grouping { description "Grouping used for Performance Monitoring Configuration. "; leaf pm-enable { type boolean; description "Whether to enable the performance monitoring."; } leaf sending-rate-high { type uint64; description "The upperbound of sending rate."; } leaf sending-rate-low { type uint64; description "The lowerbound of sending rate."; } leaf receiving-rate-high { type uint64; description "The upperbound of receiving rate."; } leaf receiving-rate-low { type uint64; description "The lowerbound of receiving rate."; } } grouping pw-segment-grouping { description "Grouping used for PW configuration. "; leaf pw-id { type string; description "The Identifier information of pseudowire. "; } leaf pw-name { type string; description "The name information of pseudowire."; } leaf transmit-label { type rt-types:mpls-label; description "Transmit label information in PW. "; } leaf receive-label { type rt-types:mpls-label; description "Receive label information in PW. "; } leaf encapsulation-type { type identityref { base etht-types:encapsulation-type; } description "The encapsulation type, raw or tag. "; } leaf oper-status { type identityref { base te-types:tunnel-state-type; } config false; description "The operational state of the PW segment. "; } container ingress-bandwidth-profile { description "Bandwidth Profile for ingress. "; uses pw-segment-named-or-value-bandwidth-profile; } list pw-paths { key path-id; description "A list of pw paths. "; leaf path-id { type uint8; description "The identifier of pw paths. "; } list tp-tunnels { key name; description "Names of TP Tunnel underlay"; leaf name { type string; description "Names of TP Tunnel underlay"; } } } } grouping pw-segment-named-or-value-bandwidth-profile { description "A grouping to configure a bandwdith profile either by referencing a named bandwidth profile or by configuring the values of the bandwidth profile attributes."; choice style { description "Whether the bandwidth profile is named or defined by value"; case named { description "Named bandwidth profile."; leaf bandwidth-profile-name { type leafref { path "/etht-svc:etht-svc/etht-svc:globals/" + "etht-svc:named-bandwidth-profiles/" + "etht-svc:bandwidth-profile-name"; } description "Name of the bandwidth profile."; } } case value { description "Bandwidth profile configured by value."; uses etht-types:pw-segement-bandwidth-profile-grouping; } } } grouping tunnels-grouping { description "A group of tunnels. "; leaf name { type leafref { path "/te:te/te:tunnels/te:tunnel/te:name"; require-instance false; } description "Dependency tunnel name"; } leaf encoding { type identityref { base te-types:lsp-encoding-types; } description "LSP encoding type"; reference "RFC3945"; } leaf switching-type { type identityref { base te-types:switching-capabilities; } description "LSP switching type"; reference "RFC3945"; } } /* * Data nodes */ container etht-svc { description "ETH services."; container globals { description "Globals Ethernet configuration data container"; list named-bandwidth-profiles { key bandwidth-profile-name; description "List of named bandwidth profiles used by Ethernet services."; leaf bandwidth-profile-name { type string; description "Name of the bandwidth profile."; } uses etht-types:etht-bandwidth-profiles; } } list etht-svc-instances { key etht-svc-name; description "The list of p2p ETH service instances"; uses etht-svc-instance-config; container state { config false; description "Ethernet Service states."; uses etht-svc-instance-state; } } } } ]]>
YANG Code for ETH type This module references a few documents including , , , , and .
WG List: Editor: Haomian Zheng Editor: Aihua Guo Editor: Italo Busi Editor: Anton Snitser Editor: Chaode Yu "; description "This module defines a collection of common YANG identity, data type and grouping definitions for describing Ethernet transport network clients. Copyright (c) 2024 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 XXXX; see the RFC itself for full legal notices."; revision 2024-01-11 { description "Initial Version"; reference "RFC XXXX: A YANG Data Model for Transport Network Client Signals"; } // RFC Editor: replace XXXX with the actual RFC number assigned // to the RFC once this draft // becomes an RFC, update date information and remove this note. /* * Identities */ identity eth-vlan-tag-type { description "ETH VLAN tag type."; } identity c-vlan-tag-type { base eth-vlan-tag-type; description "802.1Q Customer VLAN"; } identity s-vlan-tag-type { base eth-vlan-tag-type; description "802.1Q Service VLAN (QinQ)"; } identity service-classification-type { description "Service classification."; } identity port-classification { base service-classification-type; description "Port classification."; } identity vlan-classification { base service-classification-type; description "VLAN classification."; } identity eth-vlan-tag-classify { description "VLAN tag classification."; } identity classify-c-vlan { base eth-vlan-tag-classify; description "Classify 802.1Q Customer VLAN tag. Only C-tag type is accepted"; } identity classify-s-vlan { base eth-vlan-tag-classify; description "Classify 802.1Q Service VLAN (QinQ) tag. Only S-tag type is accepted"; } identity classify-s-or-c-vlan { base eth-vlan-tag-classify; description "Classify S-VLAN or C-VLAN tag-classify. Either tag is accepted"; } identity bandwidth-profile-type { description "Bandwidth Profile Types"; } identity mef-10-bwp { base bandwidth-profile-type; description "MEF 10 Bandwidth Profile"; } identity rfc-2697-bwp { base bandwidth-profile-type; description "RFC 2697 Bandwidth Profile"; } identity rfc-2698-bwp { base bandwidth-profile-type; description "RFC 2698 Bandwidth Profile"; } identity rfc-4115-bwp { base bandwidth-profile-type; description "RFC 4115 Bandwidth Profile"; } identity service-type { description "Type of Ethernet service."; } identity p2p-svc { base service-type; description "Ethernet point-to-point service (EPL, EVPL)."; } identity rmp-svc { base service-type; description "Ethernet rooted-multitpoint service (E-TREE, EP-TREE)."; } identity mp2mp-svc { base service-type; description "Ethernet multipoint-to-multitpoint service (E-LAN, EP-LAN)."; } identity lifecycle-status { description "Lifecycle Status."; } identity installed { base lifecycle-status; description "Installed."; } identity planned { base lifecycle-status; description "Planned."; } identity pending-removal { base lifecycle-status; description "Pending Removal."; } identity topology-role { description "The role of underlay topology: e.g., hub, spoke, any-to-any."; } identity resilience { description "Placeholder for resilience information in data plane, for future study. "; } identity access-role { description "Indicating whether the access is a working or protection access."; } identity root-primary { base access-role; description "Designates the primary root UNI of an E-Tree service, and may also designates the UNI access role of E-LINE and E-LAN service."; } identity root-backup { base access-role; description "Designates the backup root UNI of an E-Tree service."; } identity leaf-access { base access-role; description "Designates the leaf UNI of an E-Tree service."; } identity performance { description "Placeholder for performance information, for future study."; } identity encapsulation-type { description "Indicating how the service is encapsulated (to PW), e.g, raw or tag. "; } /* * Data Types */ typedef eth-tag-type { type identityref { base eth-vlan-tag-type; } description "Identifies a specific ETH VLAN tag type."; } typedef eth-tag-classify { type identityref { base eth-vlan-tag-classify; } description "Identifies a specific VLAN tag classification."; } typedef vlanid { type uint16 { range "1..4094"; } description "The 12-bit VLAN-ID used in the VLAN Tag header."; } typedef vid-range-type { type string { pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; } description "A list of VLAN Ids, or non overlapping VLAN ranges, in ascending order, between 1 and 4094. This type is used to match an ordered list of VLAN Ids, or contiguous ranges of VLAN Ids. Valid VLAN Ids must be in the range 1 to 4094, and included in the list in non overlapping ascending order. For example: 1,10-100,50,500-1000"; } typedef bandwidth-profile-type { type identityref { base bandwidth-profile-type; } description "Identifies a specific Bandwidth Profile type."; } typedef service-type { type identityref { base service-type; } description "Identifies the type of Ethernet service."; } typedef lifecycle-status { type identityref { base lifecycle-status; } description "Identifies the lLifecycle Status ."; } /* * Groupings */ grouping etht-bandwidth-profiles { description "Bandwidth profile configuration paramters."; leaf bandwidth-profile-type { type etht-types:bandwidth-profile-type; description "The type of bandwidth profile."; } leaf CIR { type uint64; description "Committed Information Rate in Kbps"; } leaf CBS { type uint64; description "Committed Burst Size in in KBytes"; } leaf EIR { type uint64; /* Need to indicate that EIR is not supported by RFC 2697 must '../bw-profile-type = "mef-10-bwp" or ' + '../bw-profile-type = "rfc-2698-bwp" or ' + '../bw-profile-type = "rfc-4115-bwp"' must '../bw-profile-type != "rfc-2697-bwp"' */ description "Excess Information Rate in Kbps In case of RFC 2698, PIR = CIR + EIR"; } leaf EBS { type uint64; description "Excess Burst Size in KBytes. In case of RFC 2698, PBS = CBS + EBS"; } leaf color-aware { type boolean; description "Indicates weather the color-mode is color-aware or color-blind."; } leaf coupling-flag { type boolean; /* Need to indicate that Coupling Flag is defined only for MEF 10 must '../bw-profile-type = "mef-10-bwp"' */ description "Coupling Flag."; } } grouping pw-segement-bandwidth-profile-grouping { description "bandwidth profile grouping for PW segment."; leaf bandwidth-profile-type { type etht-types:bandwidth-profile-type; description "The type of bandwidth profile."; } leaf CIR { type uint64; description "Committed Information Rate in Kbps"; } leaf CBS { type uint64; description "Committed Burst Size in in KBytes"; } leaf EIR { type uint64; /* Need to indicate that EIR is not supported by RFC 2697 must '../bw-profile-type = "mef-10-bwp" or ' + '../bw-profile-type = "rfc-2698-bwp" or ' + '../bw-profile-type = "rfc-4115-bwp"' must '../bw-profile-type != "rfc-2697-bwp"' */ description "Excess Information Rate in Kbps In case of RFC 2698, PIR = CIR + EIR"; } leaf EBS { type uint64; description "Excess Burst Size in KBytes. In case of RFC 2698, PBS = CBS + EBS"; } } grouping eth-bandwidth { description "Available bandwith for ethernet."; leaf eth-bandwidth { type uint64{ range "0..10000000000"; } units "Kbps"; description "Available bandwith value expressed in kilobits per second"; } } grouping eth-label-restriction { description "Label Restriction for ethernet."; leaf tag-type { type etht-types:eth-tag-type; description "VLAN tag type."; } leaf priority { type uint8; description "priority."; } } grouping eth-label { description "Label for ethernet."; leaf vlanid { type etht-types:vlanid; description "VLAN tag id."; } } grouping eth-label-step { description "Label step for Ethernet VLAN"; leaf eth-step { type uint16 { range "1..4095"; } default 1; description "Label step which represent possible increments for an Ethernet VLAN tag."; reference "IEEE 802.1ad: Provider Bridges."; } } } ]]>
Other Client Signal YANG Code This module imports typedefs and modules from , , .
WG List: Editor: Haomian Zheng Editor: Aihua Guo Editor: Italo Busi Editor: Anton Snitser Editor: Chaode Yu "; description "This module defines a YANG data model for describing transport network client services. The model fully conforms to the Network Management Datastore Architecture (NMDA). Copyright (c) 2024 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 XXXX; see the RFC itself for full legal notices."; revision 2024-01-11 { description "Initial Version"; reference "RFC XXXX: A YANG Data Model for Transport Network Client Signals"; } // RFC Editor: replace XXXX with the actual RFC number assigned // to the RFC once this draft // becomes an RFC, update date information and remove this note. /* * Groupings */ grouping client-svc-access-parameters { description "Transport network client signals access parameters"; leaf access-node-id { type te-types:te-node-id; description "The identifier of the access node in the TE topology."; } leaf access-node-uri { type nw:node-id; description "The identifier of the access node in the network."; } leaf access-ltp-id { type te-types:te-tp-id; description "The TE link termination point identifier in TE topology, used together with access-node-id to identify the access Link Termination Point (LTP)."; } leaf access-ltp-uri { type nt:tp-id; description "The link termination point identifier in network topology, used together with access-node-uri to identify the access LTP"; } leaf client-signal { type identityref { base l1-types:client-signal; } description "Identify the client signal type associated with this port"; } } grouping pm-state-grouping { description "Performance Monitoring (PM) state attributes"; leaf latency { type uint32; units microsecond; description "latency value of the E2E client signal service"; } } grouping error-info-grouping { description "Error information parameters"; leaf error-code { type uint16; description "error code"; } leaf error-description { type string; description "detail message of error"; } leaf error-timestamp { type yang:date-and-time; description "the date and time error is happened"; } } grouping alarm-threshold-grouping { description "Alarm threshold parameters."; leaf latency-threshold { type uint32; units microsecond; description "a threshold for the E2E client signal service's latency. Once the latency value exceed this threshold, an alarm should be triggered."; } } grouping client-svc-tunnel-parameters { description "Transport network client signals tunnel parameters"; leaf tunnel-name { type string; description "TE tunnel instance name."; } } grouping client-svc-instance-config { description "Configuration parameters for client services."; leaf client-svc-name { type string; description "Identifier of the p2p transport network client signals."; } leaf client-svc-title { type string; description "Name of the p2p transport network client signals."; } leaf user-label { type string; description "Alias of the p2p transport network client signals."; } leaf client-svc-descr { type string; description "Description of the transport network client signals."; } leaf client-svc-customer { type string; description "Customer of the transport network client signals."; } container resilience { description "Place holder for resilience functionalities"; } uses te-types:te-topology-identifier; leaf admin-status { type identityref { base te-types:tunnel-admin-state-type; } default te-types:tunnel-admin-state-up; description "Client signals administrative state."; } container src-access-ports { description "Source access port of a client signal."; uses client-svc-access-parameters; } container dst-access-ports { description "Destination access port of a client signal."; uses client-svc-access-parameters; } container pm-state { config false; description "PM data of E2E client signal"; uses pm-state-grouping; } container error-info { config false; description "error messages of configuration"; uses error-info-grouping; } container alarm-threshold { description "threshold configuration for the E2E client signal"; uses alarm-threshold-grouping; } leaf direction { type identityref { base clnt-types:direction; } description "Uni-dir or Bi-dir for the client signal."; } list svc-tunnels { key tunnel-name; description "List of the TE Tunnels supporting the client signal."; uses client-svc-tunnel-parameters; } } grouping client-svc-instance-state { description "State parameters for client services."; leaf operational-state { type identityref { base te-types:tunnel-state-type; } config false; description "Client signal operational state."; } leaf provisioning-state { type identityref { base te-types:lsp-state-type; } config false; description "Client signal provisioning state."; } leaf creation-time { type yang:date-and-time; config false; description "The time of the client signal be created."; } leaf last-updated-time { type yang:date-and-time; config false; description "The time of the client signal's latest update."; } leaf created-by { type string; config false; description "The client signal is created by whom, can be a system or staff ID."; } leaf last-updated-by { type string; config false; description "The client signal is last updated by whom, can be a system or staff ID."; } leaf owned-by { type string; config false; description "The client signal is owned by whom, can be a system ID."; } } /* * Data nodes */ container client-svc { description "Transport client services."; list client-svc-instances { key client-svc-name; description "The list of p2p transport client service instances"; uses client-svc-instance-config; uses client-svc-instance-state; } } } ]]>
Other Client Signal Types YANG Code This module defines the types for other client signal types.
WG List: Editor: Haomian Zheng Editor: Aihua Guo Editor: Italo Busi Editor: Anton Snitser Editor: Chaode Yu "; description "This module defines a collection of common YANG identity definitions for describing Costant Bit Rate (CBR) transport network clients. Copyright (c) 2024 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 XXXX; see the RFC itself for full legal notices."; revision 2024-01-11 { description "Initial Version"; reference "RFC XXXX: A YANG Data Model for Transport Network Client Signals"; } // RFC Editor: replace XXXX with the actual RFC number assigned // to the RFC once this draft // becomes an RFC, update date information and remove this note. /* * Identities */ identity direction { description "Direction information of Client Signal."; } identity bidirectional { base direction; description "Client Signal is bi-directional."; } identity unidirectional { base direction; description "Client Signal is uni-directional."; } } ]]>
Implementation Status [Note to the RFC Editor - remove this section before publication, as well as remove the reference to RFC .] This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to , "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".
Usage of the ETH Service YANG Model on ONAP The implementation of the CCVPN (Cross Domain and Cross Layer VPN) use-case on ONAP follows the ACTN architecture. In the design of CCVPN, ONAP presumes the responsibility of the MDSC, and third party network domain controllers the PNCs. Consequently, the ETH Service YANG model is used as the MPI between ONAP and the domain controllers.
  • Organization: China Mobile, Huawei Technologies, etc.
  • Implementation: ONAP CCVPN uses the ETH Service YANG model as the ACTN MPI
  • Description: ONAP CCVPN realizes the E-LINE and E-TREE service on a multi-domain network. Both of the services are modeled on ONAP by the ETH Service YANG model, and the model instances (e.g., JSON objects) are sent between ONAP and the domain controllers. Refer to the following CCVPN wiki for more information: https://wiki.onap.org/display/DW/ CCVPN%28Cross+Domain+and+Cross+Layer+VPN%29+USE+CASE
  • Maturity Level: Prototype
  • Coverage: Partial
  • Contact: henry.yu1@huawei.com
Manageability Considerations TBD
Security Considerations The data following the model defined in this document is exchanged via, for example, the interface between an orchestrator and a network domain controller. The YANG module defined in this document can be accessed via the RESTCONF protocol defined in , or maybe via the NETCONF protocol . There are a number of data nodes defined in the YANG module which are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., POST) to these data nodes without proper protection can have a negative effect on network operations.
IANA Considerations It is proposed that IANA should assign new URIs from the "IETF XML Registry" as follows: This document registers following YANG modules in the YANG Module Names registry .
References Normative References Optical transport network: Protocol-neutral management information model for the network element view International Telecommunication Union A YANG Data Model for Optical Transport Network Topology Huawei Technologies Huawei Technologies IBM Corporation Nokia Telefonica This document defines a YANG data model for representing, retrieving, and manipulating Optical Transport Network (OTN) topologies. It is independent of control plane protocols and captures topological and resource-related information pertaining to OTN. OTN Tunnel YANG Model Huawei Technologies Huawei Technologies Nokia Nokia CAICT This document describes the YANG data model for tunnels in OTN TE networks. The model can be used to do the configuration in order to establish the tunnel in OTN network. This work is independent with the control plane protocols. The YANG 1.1 Data Modeling Language 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). Common YANG Data Types This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. Common YANG Data Types for the Routing Area 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. A YANG Data Model for Network Topologies This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models. Common YANG Data Types for Traffic Engineering Huawei Futurewei Technologies Alef Edge Cisco Systems Inc. Individual This document defines a collection of common data types, identities, and groupings in YANG data modeling language. These derived common data types, identities and groupings are intended to be imported by other modules, e.g., those which model the Traffic Engineering (TE) configuration and state capabilities. This document obsoletes RFC 8776. Common YANG Data Types for Layer 1 Networks Huawei Technologies Huawei Technologies This document defines a collection of common common data types, identities, and groupings in the YANG data modeling language. These derived common common data types, identities, and groupings are intended to be imported by modules that model Layer 1 configuration and state capabilities. The Layer 1 types are representative of Layer 1 client signals applicable to transport networks, such as Optical Transport Networks (OTN). The Optical Transport Network (OTN) data structures are included in this document as Layer 1 types. A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces Cisco Systems Inc Cisco Systems Inc Alef Edge Juniper Networks Individual This document defines a YANG data model for the provisioning and management of Traffic Engineering (TE) tunnels, Label Switched Paths (LSPs), and interfaces. The model covers data that is independent of any technology or dataplane encapsulation and is divided into two YANG modules that cover device-specific, and device independent data. This model covers data for configuration, operational state, remote procedural calls, and event notifications. A YANG Data Model for L1 Connectivity Service Model (L1CSM) Samsung Korea Telecom Huawei Technologies Telefonica Cisco This document provides a YANG Layer 1 Connectivity Service Model (L1CSM). This model can be utilized by a customer network controller to initiate a connectivity service request as well as to retrieve service states for a Layer 1 network controller communicating with its customer network controller. This YANG model is in compliance of Network Management Datastore Architecture (NMDA). GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport Networks ITU-T Recommendation G.709 [G709-2012] introduced new Optical channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e, and ODUflex) and enhanced Optical Transport Network (OTN) flexibility. This document updates the ODU-related portions of RFC 4328 to provide extensions to GMPLS signaling to control the full set of OTN features, including ODU0, ODU4, ODU2e, and ODUflex. RESTCONF 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). Network Configuration Protocol (NETCONF) 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] YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF) 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] Informative References IEEE Standard for Local and Metropolitan Area Networks - Virtual Bridged Local Area Networks - Amendment 4: Provider Bridges Institute of Electrical and Electronics Engineers IEEE Standard for Local and Metropolitan Area Networks - Bridges and Bridged Networks Ethernet Services Attributes Phase 1 MEF Forum Network Management Datastore Architecture (NMDA) 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. YANG Tree Diagrams 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. Framework for Abstraction and Control of TE Networks (ACTN) 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. A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery 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. YANG Data Model for L3VPN Service Delivery 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. Service Models Explained The IETF has produced many modules in the YANG modeling language. The majority of these modules are used to construct data models to model devices or monolithic functions. A small number of YANG modules have been defined to model services (for example, the Layer 3 Virtual Private Network Service Model (L3SM) produced by the L3SM working group and documented in RFC 8049). This document describes service models as used within the IETF and also shows where a service model might fit into a software-defined networking architecture. Note that service models do not make any assumption of how a service is actually engineered and delivered for a customer; details of how network protocols and devices are engineered to deliver a service are captured in other modules that are not exposed through the interface between the customer and the provider. A Single Rate Three Color Marker This document defines a Single Rate Three Color Marker (srTCM), which can be used as component in a Diffserv traffic conditioner. This memo provides information for the Internet community. A Two Rate Three Color Marker This document defines a Two Rate Three Color Marker (trTCM), which can be used as a component in a Diffserv traffic conditioner. This memo provides information for the Internet community. A Differentiated Service Two-Rate, Three-Color Marker with Efficient Handling of in-Profile Traffic This document describes a two-rate, three-color marker that has been in use for data services including Frame Relay services. This marker can be used for metering per-flow traffic in the emerging IP and L2 VPN services. The marker defined here is different from previously defined markers in the handling of the in-profile traffic. Furthermore, this marker doesn't impose peak-rate shaping requirements on customer edge (CE) devices. This memo provides information for the Internet community. Improving Awareness of Running Code: The Implementation Status Section This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice. The IETF XML Registry 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.
Acknowledgments We would like to acknowledge the contribution from Francesco Lazzeri to the initial versions of this document, before it has been adopted by CCAMP WG. We would like to thank Igor Bryskin and Daniel King for their comments and discussions.
Contributors CAICT
xuyunbin@caict.ac.cn
China Mobile
zhaoyangyjy@chinamobile.com
Alef Edge
xufeng.liu.ietf@gmail.com
Huawei Technologies
giuseppe.fioccola@huawei.com
Huawei Technologies
liuzhe123@huawei.com
Nokia
sergio.belotti@nokia.com
Shanghai Bell
yingxi.yao@nokia-sbell.com
Huawei Technologies
henry.yu1@huawei.com