Network Working Group X. Geng Internet-Draft M. Chen Intended status: Standards Track Huawei Technologies Expires: July 18, 2019 Z. Li China Mobile R. Rahman Cisco Systems January 14, 2019 Deterministic Networking (DetNet) Configuration YANG Model draft-ietf-detnet-yang-01 Abstract This document contains the specification for Deterministic Networking flow configuration YANG Model. The model allows for provisioning of end-to-end DetNet service along the path without dependency on any signaling protocol. The YANG module defined in this document conforms to the Network Management Datastore Architecture (NMDA). Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on July 18, 2019. Geng, et al. Expires July 18, 2019 [Page 1] Internet-Draft DetNet Model January 2019 Copyright Notice Copyright (c) 2019 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 4 3. DetNet Configuration Model . . . . . . . . . . . . . . . . . 4 3.1. DetNet Service Proxy Configuration Attributes . . . . . . 4 3.2. DetNet Service Layer Configuration Attributes . . . . . . 5 3.3. DetNet Transport Layer Configuration Attributes . . . . . 7 4. DetNet Configuration YANG Structure . . . . . . . . . . . . . 8 5. DetNet Configuration YANG Model . . . . . . . . . . . . . . . 14 6. DetNet Configuration Model Classification . . . . . . . . . . 31 6.1. Fully Distributed Configuration Model . . . . . . . . . . 31 6.2. Fully Centralized Configuration Model . . . . . . . . . . 31 6.3. Hybrid Configuration Model . . . . . . . . . . . . . . . 32 7. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 33 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 9. Security Considerations . . . . . . . . . . . . . . . . . . . 33 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 11.1. Normative References . . . . . . . . . . . . . . . . . . 34 11.2. Informative References . . . . . . . . . . . . . . . . . 35 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 1. Introduction Deterministic Networking (DetNet) [I-D.ietf-detnet-architecture] is defined to provide high-quality network service with extremely low packet loss rate, bounded low latency and jitter. DetNet flow information is defined in[I-D.ietf-detnet-flow-information-model], and the DetNet models are categorized as: Geng, et al. Expires July 18, 2019 [Page 2] Internet-Draft DetNet Model January 2019 o Flow models: describe characteristics of data flows. These models describe in detail all relevant aspects of a flow that are needed to support the flow properly by the network between the source and the destination(s). o Service models: describe characteristics of services being provided for data flows over a network. These models can be treated as a network operator independent information model. o Configuration models: describe in detail the settings required on network nodes to serve a data flow properly. Service and flow information models are used between the user and the network operator. Configuration information models are used between the management/control plane entity of the network and the network nodes. They are shown in the Figure 1. User Network Operator flow/service +---+ model +---+ | | <---------------> | X | management/control +---+ +-+-+ plane entity ^ | configuration | model +------------+ v | | +-+ | v network +-+ v +-+ nodes +-+ +-+ +-+ Figure 1. Three Information Models DetNet YANG [RFC7950] [RFC6991] models include: DetNet YANG [RFC7950] [RFC6991] models are used for DetNet service configurations, QoS configuration and topology discovery. DetNet topology model is defined in ietf-detnet-topology-yang. This document defines two YANG models, which are referred to as DetNet flow configuration model and DetNet transport QoS model. DetNet flow model is designed for DetNet flow path configuration and flow status reporting. DetNet transport QoS model is designed for QoS attributes configuration of transport tunnels to achieve end-to-end bounded latency and zero congestion loss. Geng, et al. Expires July 18, 2019 [Page 3] Internet-Draft DetNet Model January 2019 2. Terminologies This documents uses the terminologies defined in [I-D.ietf-detnet-architecture]. 3. DetNet Configuration Model DetNet flow configuration includes DetNet Service Proxy configuration, DetNet Service Layer configuration and DetNet Transport Layer configuration. The corresponding attributes used in different layers are defined in Section 3.1, 3.2, 3.3, respectively. 3.1. DetNet Service Proxy Configuration Attributes DetNet service proxy is responsible for mapping between application flows and DetNet flows at the edge node(egress/ingress node). Where the application flows can be either layer 2 or layer 3 flows. To identify a flow at the User Network Interface (UNI), as defined in [I-D.ietf-detnet-flow-information-model], the following flow attributes are introduced: o DetNet L3 Flow Identification, refers to Section 7.1.1 of [I-D.ietf-detnet-flow-information-model] o DetNet L2 Flow Identification, refers to Section 7.1.2 of [I-D.ietf-detnet-flow-information-model] DetNet service proxy can also do flow filtering and policing at the ingress to prevent the misbehaviored flows from going into the network, which needs: o Traffic Specification, refers to Section 7.2 of [I-D.ietf-detnet-flow-information-model] The YANG module structure is shown below: Geng, et al. Expires July 18, 2019 [Page 4] Internet-Draft DetNet Model January 2019 +--rw client-flow* [flow-id] | +--rw flow-id uint32 | +--rw (flow-type)? | | +--:(l2-flow-identfication) | | | +--rw source-mac-address? yang:mac-address | | | +--rw destination-mac-address? yang:mac-address | | | +--rw ethertype? eth:ethertype | | | +--rw vlan-id? uint16 | | | +--rw pcp | | +--:(l3-flow-identification) | | +--rw (ip-flow-type)? | | | +--:(ipv4) | | | | +--rw src-ipv4-address? inet:ipv4-address | | | | +--rw dest-ipv4-address? inet:ipv4-address | | | | +--rw dscp? uint8 | | | +--:(ipv6) | | | +--rw src-ipv6-address? inet:ipv6-address | | | +--rw dest-ipv6-address? inet:ipv6-address | | | +--rw traffic-class? uint8 | | | +--rw flow-label? inet:ipv6-flow-label | | +--rw source-port? inet:port-number | | +--rw destination-port? inet:port-number | | +--rw protocol? uint8 | +--rw traffic-specification | +--rw interval? uint32 | +--rw max-packets-per-interval? uint32 | +--rw max-payload-size? uint32 | +--rw average-packets-per-interval? uint32 | +--rw average-payload-size? uint32 3.2. DetNet Service Layer Configuration Attributes DetNet service functions, e.g., DetNet tunnel initialization/ termination and service protection, are provided in DetNet service layer. To support these functions, the following service attributes need to be configured: o DetNet flow identification, refers to Section 7.1.3 of [I-D.ietf-detnet-flow-information-model]. o Service function indication, indicates which service function will be invoked at a DetNet edge, relay node or end station. (DetNet tunnel initialization or termination are default functions in DetNet service layer, so there is no need for explicit indication.) o Flow Rank, refers to Section 7.3 of [I-D.ietf-detnet-flow-information-model]. Geng, et al. Expires July 18, 2019 [Page 5] Internet-Draft DetNet Model January 2019 o Service Rank, refers to Section 7.4 of [I-D.ietf-detnet-flow-information-model]. o Service decapsulation, refers to Section 6.2 of [I-D.ietf-detnet-dp-sol-mpls] o Transport decapsulation, refers to Section 6.2 of [I-D.ietf-detnet-dp-sol-mpls] and Section 3 of [I-D.ietf-detnet-dp-sol-ip] o Service encapsulation, refers to Section 6.2 of [I-D.ietf-detnet-dp-sol-mpls] o Transport encapsulation, refers to Section 6.2 of [I-D.ietf-detnet-dp-sol-mpls]and Section 3 of [I-D.ietf-detnet-dp-sol-ip] The YANG module structure is shown below: | +--rw relay-node | +--rw name? string | +--rw flow-rank | +--rw service-rank | +--rw in-segment* [in-segment-id] | | +--rw in-segment-id uint32 | | +--rw (flow-type)? | | | +--:(IP) | | | | +--rw (ip-flow-type)? | | | | | +--:(ipv4) | | | | | | +--rw src-ipv4-address? inet:ipv4-address | | | | | | +--rw dest-ipv4-address? inet:ipv4-address | | | | | | +--rw dscp? uint8 | | | | | +--:(ipv6) | | | | | +--rw src-ipv6-address? inet:ipv6-address | | | | | +--rw dest-ipv6-address? inet:ipv6-address | | | | | +--rw traffic-class? uint8 | | | | | +--rw flow-label? inet:ipv6-flow-label | | | | +--rw source-port? inet:port-number | | | | +--rw destination-port? inet:port-number | | | | +--rw protocol? uint8 | | | +--:(MPLS) | | | +--rw service-label uint32 | | +--rw service-function? service-function-type | +--rw out-segment* [out-segment-id] | +--rw out-segment-id uint32 | +--rw detnet-service-encapsulation | | +--rw service-label uint32 | | +--rw control-word uint32 Geng, et al. Expires July 18, 2019 [Page 6] Internet-Draft DetNet Model January 2019 | +--rw detnet-transport-encapsulation | +--rw (tunnel-type)? | | +--:(IPv4) | | | +--rw ipv4-encaplustion | | | +--rw src-ipv4-address inet:ipv4-address | | | +--rw dest-ipv4-address inet:ipv4-address | | | +--rw protocol uint8 | | | +--rw ttl? uint8 | | | +--rw dscp? uint8 | | +--:(IPv6) | | | +--rw ipv6-encaplustion | | | +--rw src-ipv6-address inet:ipv6-address | | | +--rw dest-ipv6-address inet:ipv6-address | | | +--rw next-header uint8 | | | +--rw traffic-class? uint8 | | | +--rw flow-label? inet:ipv6-flow-label | | | +--rw hop-limit? uint8 | | +--:(MPLS) | | +--rw mpls-encaplustion | | +--rw label-operations* [label-oper-id] | | +--rw label-oper-id uint32 | | +--rw (label-actions)? | | +--:(label-push) | | | +--rw label-push | | | +--rw label uint32 | | | +--rw s-bit? boolean | | | +--rw tc-value? uint8 | | | +--rw ttl-value? uint8 | | +--:(label-swap) | | +--rw label-swap | | +--rw out-label uint32 | | +--rw ttl-action? ttl-action-definition | +--rw interval? uint32 | +--rw max-packets-per-interval? uint32 | +--rw max-payload-size? uint32 | +--rw average-packets-per-interval? uint32 | +--rw average-payload-size? uint32 3.3. DetNet Transport Layer Configuration Attributes As defined in [I-D.ietf-detnet-architecture], DetNet transport layer optionally provides congestion protection for DetNet flows over paths provided by the underlying network. Explicit route is another mechanism that is used by DetNet to avoid temporary interruptions caused by the convergence of routing or bridging protocols, and it is also implemented at the DetNet transport layer. Geng, et al. Expires July 18, 2019 [Page 7] Internet-Draft DetNet Model January 2019 To support congestion protection and explicit route, the following transport layer related attributes are necessary: o Traffic Specification, refers to Section 7.2 of [I-D.ietf-detnet-flow-information-model]. It may used for bandwidth reservation, flow shaping, filtering and policing. o Explicit path, existing explicit route mechanisms can be reused. For example, if Segment Routing (SR) tunnel is used as the transport tunnel, the configuration is mainly at the ingress node of the transport layer; if the static MPLS tunnel is used as the transport tunnel, the configurations need to be at every transit node along the path; for pure IP based transport tunnel, it's similar to the static MPLS case. The YANG module structure is shown below: | +--rw transit-node | +--rw interval? uint32 | +--rw max-packets-per-interval? uint32 | +--rw max-payload-size? uint32 | +--rw average-packets-per-interval? uint32 | +--rw average-payload-size? uint32 The parameters for DetNet transport QoS are defined in Section 5. 4. DetNet Configuration YANG Structure module: ietf-detnet-flow-config +--rw detnet-flow +--rw (detnet-node-role)? +--:(transit-node) | +--rw transit-node | +--rw interval? uint32 | +--rw max-packets-per-interval? uint32 | +--rw max-payload-size? uint32 | +--rw average-packets-per-interval? uint32 | +--rw average-payload-size? uint32 +--:(relay-node) | +--rw relay-node | +--rw name? string | +--rw flow-rank | +--rw service-rank | +--rw in-segment* [in-segment-id] | | +--rw in-segment-id uint32 | | +--rw (flow-type)? | | | +--:(IP) | | | | +--rw (ip-flow-type)? Geng, et al. Expires July 18, 2019 [Page 8] Internet-Draft DetNet Model January 2019 | | | | | +--:(ipv4) | | | | | | +--rw src-ipv4-address? inet:ipv4-address | | | | | | +--rw dest-ipv4-address? inet:ipv4-address | | | | | | +--rw dscp? uint8 | | | | | +--:(ipv6) | | | | | +--rw src-ipv6-address? inet:ipv6-address | | | | | +--rw dest-ipv6-address? inet:ipv6-address | | | | | +--rw traffic-class? uint8 | | | | | +--rw flow-label? inet:ipv6-flow-label | | | | +--rw source-port? inet:port-number | | | | +--rw destination-port? inet:port-number | | | | +--rw protocol? uint8 | | | +--:(MPLS) | | | +--rw service-label uint32 | | +--rw service-function? service-function-type | +--rw out-segment* [out-segment-id] | +--rw out-segment-id uint32 | +--rw detnet-service-encapsulation | | +--rw service-label uint32 | | +--rw control-word uint32 | +--rw detnet-transport-encapsulation | +--rw (tunnel-type)? | | +--:(IPv4) | | | +--rw ipv4-encaplustion | | | +--rw src-ipv4-address inet:ipv4-address | | | +--rw dest-ipv4-address inet:ipv4-address | | | +--rw protocol uint8 | | | +--rw ttl? uint8 | | | +--rw dscp? uint8 | | +--:(IPv6) | | | +--rw ipv6-encaplustion | | | +--rw src-ipv6-address inet:ipv6-address | | | +--rw dest-ipv6-address inet:ipv6-address | | | +--rw next-header uint8 | | | +--rw traffic-class? uint8 | | | +--rw flow-label? inet:ipv6-flow-label | | | +--rw hop-limit? uint8 | | +--:(MPLS) | | +--rw mpls-encaplustion | | +--rw label-operations* [label-oper-id] | | +--rw label-oper-id uint32 | | +--rw (label-actions)? | | +--:(label-push) | | | +--rw label-push | | | +--rw label uint32 | | | +--rw s-bit? boolean | | | +--rw tc-value? uint8 | | | +--rw ttl-value? uint8 Geng, et al. Expires July 18, 2019 [Page 9] Internet-Draft DetNet Model January 2019 | | +--:(label-swap) | | +--rw label-swap | | +--rw out-label uint32 | | +--rw ttl-action? ttl-action-definition | +--rw interval? uint32 | +--rw max-packets-per-interval? uint32 | +--rw max-payload-size? uint32 | +--rw average-packets-per-interval? uint32 | +--rw average-payload-size? uint32 +--:(edge-node) | +--rw edge-node | +--rw client-flow* [flow-id] | | +--rw flow-id uint32 | | +--rw (flow-type)? | | | +--:(l2-flow-identfication) | | | | +--rw source-mac-address? yang:mac-address | | | | +--rw destination-mac-address? yang:mac-address | | | | +--rw ethertype? eth:ethertype | | | | +--rw vlan-id? uint16 | | | | +--rw pcp | | | +--:(l3-flow-identification) | | | +--rw (ip-flow-type)? | | | | +--:(ipv4) | | | | | +--rw src-ipv4-address? inet:ipv4-address | | | | | +--rw dest-ipv4-address? inet:ipv4-address | | | | | +--rw dscp? uint8 | | | | +--:(ipv6) | | | | +--rw src-ipv6-address? inet:ipv6-address | | | | +--rw dest-ipv6-address? inet:ipv6-address | | | | +--rw traffic-class? uint8 | | | | +--rw flow-label? inet:ipv6-flow-label | | | +--rw source-port? inet:port-number | | | +--rw destination-port? inet:port-number | | | +--rw protocol? uint8 | | +--rw traffic-specification | | +--rw interval? uint32 | | +--rw max-packets-per-interval? uint32 | | +--rw max-payload-size? uint32 | | +--rw average-packets-per-interval? uint32 | | +--rw average-payload-size? uint32 | +--rw detnet-service-instance | +--rw name? string | +--rw flow-rank | +--rw service-rank | +--rw in-segment* [in-segment-id] | | +--rw in-segment-id uint32 | | +--rw (flow-type)? | | | +--:(IP) Geng, et al. Expires July 18, 2019 [Page 10] Internet-Draft DetNet Model January 2019 | | | | +--rw (ip-flow-type)? | | | | | +--:(ipv4) | | | | | | +--rw src-ipv4-address? inet:ipv4-address | | | | | | +--rw dest-ipv4-address? inet:ipv4-address | | | | | | +--rw dscp? uint8 | | | | | +--:(ipv6) | | | | | +--rw src-ipv6-address? inet:ipv6-address | | | | | +--rw dest-ipv6-address? inet:ipv6-address | | | | | +--rw traffic-class? uint8 | | | | | +--rw flow-label? inet:ipv6-flow-label | | | | +--rw source-port? inet:port-number | | | | +--rw destination-port? inet:port-number | | | | +--rw protocol? uint8 | | | +--:(MPLS) | | | +--rw service-label uint32 | | +--rw service-function? service-function-type | +--rw out-segment* [out-segment-id] | +--rw out-segment-id uint32 | +--rw detnet-service-encapsulation | | +--rw service-label uint32 | | +--rw control-word uint32 | +--rw detnet-transport-encapsulation | +--rw (tunnel-type)? | | +--:(IPv4) | | | +--rw ipv4-encaplustion | | | +--rw src-ipv4-address inet:ipv4-address | | | +--rw dest-ipv4-address inet:ipv4-address | | | +--rw protocol uint8 | | | +--rw ttl? uint8 | | | +--rw dscp? uint8 | | +--:(IPv6) | | | +--rw ipv6-encaplustion | | | +--rw src-ipv6-address inet:ipv6-address | | | +--rw dest-ipv6-address inet:ipv6-address | | | +--rw next-header uint8 | | | +--rw traffic-class? uint8 | | | +--rw flow-label? inet:ipv6-flow-label | | | +--rw hop-limit? uint8 | | +--:(MPLS) | | +--rw mpls-encaplustion | | +--rw label-operations* [label-oper-id] | | +--rw label-oper-id uint32 | | +--rw (label-actions)? | | +--:(label-push) | | | +--rw label-push | | | +--rw label uint32 | | | +--rw s-bit? boolean | | | +--rw tc-value? uint8 Geng, et al. Expires July 18, 2019 [Page 11] Internet-Draft DetNet Model January 2019 | | | +--rw ttl-value? uint8 | | +--:(label-swap) | | +--rw label-swap | | +--rw out-label uint32 | | +--rw ttl-action? ttl-action-definition | +--rw interval? uint32 | +--rw max-packets-per-interval? uint32 | +--rw max-payload-size? uint32 | +--rw average-packets-per-interval? uint32 | +--rw average-payload-size? uint32 +--:(end-station) +--rw end-station +--rw client-flow* [flow-id] | +--rw flow-id uint32 | +--rw (flow-type)? | | +--:(l2-flow-identfication) | | | +--rw source-mac-address? yang:mac-address | | | +--rw destination-mac-address? yang:mac-address | | | +--rw ethertype? eth:ethertype | | | +--rw vlan-id? uint16 | | | +--rw pcp | | +--:(l3-flow-identification) | | +--rw (ip-flow-type)? | | | +--:(ipv4) | | | | +--rw src-ipv4-address? inet:ipv4-address | | | | +--rw dest-ipv4-address? inet:ipv4-address | | | | +--rw dscp? uint8 | | | +--:(ipv6) | | | +--rw src-ipv6-address? inet:ipv6-address | | | +--rw dest-ipv6-address? inet:ipv6-address | | | +--rw traffic-class? uint8 | | | +--rw flow-label? inet:ipv6-flow-label | | +--rw source-port? inet:port-number | | +--rw destination-port? inet:port-number | | +--rw protocol? uint8 | +--rw traffic-specification | +--rw interval? uint32 | +--rw max-packets-per-interval? uint32 | +--rw max-payload-size? uint32 | +--rw average-packets-per-interval? uint32 | +--rw average-payload-size? uint32 +--rw detnet-service-instance +--rw name? string +--rw flow-rank +--rw service-rank +--rw in-segment* [in-segment-id] | +--rw in-segment-id uint32 | +--rw (flow-type)? Geng, et al. Expires July 18, 2019 [Page 12] Internet-Draft DetNet Model January 2019 | | +--:(IP) | | | +--rw (ip-flow-type)? | | | | +--:(ipv4) | | | | | +--rw src-ipv4-address? inet:ipv4-address | | | | | +--rw dest-ipv4-address? inet:ipv4-address | | | | | +--rw dscp? uint8 | | | | +--:(ipv6) | | | | +--rw src-ipv6-address? inet:ipv6-address | | | | +--rw dest-ipv6-address? inet:ipv6-address | | | | +--rw traffic-class? uint8 | | | | +--rw flow-label? inet:ipv6-flow-label | | | +--rw source-port? inet:port-number | | | +--rw destination-port? inet:port-number | | | +--rw protocol? uint8 | | +--:(MPLS) | | +--rw service-label uint32 | +--rw service-function? service-function-type +--rw out-segment* [out-segment-id] +--rw out-segment-id uint32 +--rw detnet-service-encapsulation | +--rw service-label uint32 | +--rw control-word uint32 +--rw detnet-transport-encapsulation +--rw (tunnel-type)? | +--:(IPv4) | | +--rw ipv4-encaplustion | | +--rw src-ipv4-address inet:ipv4-address | | +--rw dest-ipv4-address inet:ipv4-address | | +--rw protocol uint8 | | +--rw ttl? uint8 | | +--rw dscp? uint8 | +--:(IPv6) | | +--rw ipv6-encaplustion | | +--rw src-ipv6-address inet:ipv6-address | | +--rw dest-ipv6-address inet:ipv6-address | | +--rw next-header uint8 | | +--rw traffic-class? uint8 | | +--rw flow-label? inet:ipv6-flow-label | | +--rw hop-limit? uint8 | +--:(MPLS) | +--rw mpls-encaplustion | +--rw label-operations* [label-oper-id] | +--rw label-oper-id uint32 | +--rw (label-actions)? | +--:(label-push) | | +--rw label-push | | +--rw label uint32 | | +--rw s-bit? boolean Geng, et al. Expires July 18, 2019 [Page 13] Internet-Draft DetNet Model January 2019 | | +--rw tc-value? uint8 | | +--rw ttl-value? uint8 | +--:(label-swap) | +--rw label-swap | +--rw out-label uint32 | +--rw ttl-action? ttl-action-definition +--rw interval? uint32 +--rw max-packets-per-interval? uint32 +--rw max-payload-size? uint32 +--rw average-packets-per-interval? uint32 +--rw average-payload-size? uint32 5. DetNet Configuration YANG Model file "ietf-detnet-config@20190114.yang" module ietf-detnet-config { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-detnet-flow-config"; prefix "detnet-flow"; import ietf-yang-types { prefix "yang"; } import ietf-inet-types{ prefix "inet"; } import ietf-ethertypes { prefix "eth"; } organization "IETF DetNet Working Group"; contact "WG Web: WG List: WG Chair: Lou Berger Janos Farkas Editor: Xuesong Geng Editor: Mach Chen Geng, et al. Expires July 18, 2019 [Page 14] Internet-Draft DetNet Model January 2019 Editor: Zhenqiang Li Editor: Reshad Rahman "; description "This YANG module describes the parameters needed for DetNet flow configuration and flow status reporting."; revision "2018-09-10" { description "initial revision"; reference "RFC XXXX: draft-geng-detnet-config-yang-05"; } identity detnet-node-role { description "base detnet-node-role"; } identity end-station { base detnet-node-role; description "Commonly called a 'host' in IETF documents, and an 'end station' is IEEE 802 documents. End systems of interest to this document are either sources or destinations of DetNet flows. And end system may or may not be DetNet transport layer aware or DetNet service layer aware."; } identity edge-node { base detnet-node-role; description "An instance of a DetNet relay node that includes either a DetNet service layer proxy function for DetNet service protection (e.g. the addition or removal of packet sequencing information) for one or more end systems, or starts or terminate congestion protection at the DetNet transport layer,analogous to a Label Edge Router (LER)."; } identity relay-node { base detnet-node-role; description Geng, et al. Expires July 18, 2019 [Page 15] Internet-Draft DetNet Model January 2019 "A DetNet node including a service layer function that interconnects different DetNet transport layer paths to provide service protection. A DetNet relay node can be a bridge, a router, a firewall, or any other system that participates in the DetNet service layer. It typically incorporates DetNet transport layer functions as well, in which case it is collocated with a transit node."; } identity transit-node { base detnet-node-role; description "A node operating at the DetNet transport layer, that utilizes link layer and/or network layer switching across multiple links and/or sub-networks to provide paths for DetNet service layer functions. Optionally provides congestion protection over those paths. An MPLS LSR is an example of a DetNet transit node."; } identity ttl-action { description "Base identity from which all TTL actions are derived."; } identity no-action { base "ttl-action"; description "Do nothing regarding the TTL."; } identity copy-to-inner { base "ttl-action"; description "Copy the TTL of the outer header to the inner header."; } identity decrease-and-copy-to-inner { base "ttl-action"; description "Decrease TTL by one and copy the TTL to the inner header."; } Geng, et al. Expires July 18, 2019 [Page 16] Internet-Draft DetNet Model January 2019 typedef ttl-action-definition { type identityref { base "ttl-action"; } description "TTL action definition."; } identity detnet-transport-layer { description "The layer that optionally provides congestion protection for DetNet flows over paths provided by the underlying network."; } identity detnet-service-layer { description "The layer at which service protection is provided, either packet sequencing, replication, and elimination or packet encoding"; } typedef service-function-type { type enumeration { enum replication { description "A Packet Replication Function (PRF) replicates DetNet flow packets and forwards them to one or more next hops in the DetNet domain. The number of packet copies sent to each next hop is a DetNet flow specific parameter at the node doing the replication. PRF can be implemented by an edge node, a relay node, or an end system"; } enum elimination { description "A Packet Elimination Function (PEF) eliminates duplicate copies of packets to prevent excess packets flooding the network or duplicate packets being sent out of the DetNet domain. PEF can be implemented by an edge node, a relay node, or an end system."; } enum ordering { description "A Packet Ordering Function (POF) re-orders packets within a DetNet flow that are received out of order. This function can be implemented Geng, et al. Expires July 18, 2019 [Page 17] Internet-Draft DetNet Model January 2019 by an edge node, a relay node, or an end system."; } enum elimination-ordering { description "A combination of PEF and POF that can be implemented by an edge node, a relay node, or an end system."; } enum elimination-replication { description "A combination of PEF and PRF that can be implemented by an edge node, a relay node, or an end system"; } enum elimination-ordering-replicaiton { description "A combination of PEF, POF and PRF that can be implemented by an edge node, a relay node, or an end system"; } } description "DetNet service function and function combination types."; } grouping detnet-transport-qos { description "DetNet transport tunnel QoS attributes."; uses traffic-specification; } grouping ipv4-header { description "The IPv4 header encapsulation information."; leaf src-ipv4-address { type inet:ipv4-address; mandatory true; description "The source IP address of the header."; } leaf dest-ipv4-address { type inet:ipv4-address; mandatory true; description "The destination IP address of the header."; } leaf protocol { Geng, et al. Expires July 18, 2019 [Page 18] Internet-Draft DetNet Model January 2019 type uint8; mandatory true; description "The protocol id of the header."; } leaf ttl { type uint8; description "The TTL of the header."; } leaf dscp { type uint8; description "The DSCP field of the header."; } } grouping ipv6-header { description "The IPv6 header encapsulation information."; leaf src-ipv6-address { type inet:ipv6-address; mandatory true; description "The source IP address of the header."; } leaf dest-ipv6-address { type inet:ipv6-address; mandatory true; description "The destination IP address of the header."; } leaf next-header { type uint8; mandatory true; description "The next header of the IPv6 header."; } leaf traffic-class { type uint8; description "The traffic class value of the header."; } leaf flow-label { type inet:ipv6-flow-label; description "The flow label of the header."; } Geng, et al. Expires July 18, 2019 [Page 19] Internet-Draft DetNet Model January 2019 leaf hop-limit { type uint8 { range "1..255"; } description "The hop limit of the header."; } } grouping mpls-header { description "The MPLS encapsulation header information."; list label-operations { key "label-oper-id"; description "Label operations."; leaf label-oper-id { type uint32; description "An optional identifier that points to a label operation."; } choice label-actions { description "Label action options."; case label-push { container label-push { description "Label push operation."; leaf label { type uint32; mandatory true; description "The label to be pushed."; } leaf s-bit { type boolean; description "The s-bit of the label to be pushed."; } leaf tc-value { type uint8; description "The traffic class value of the label to be pushed."; } leaf ttl-value { type uint8; Geng, et al. Expires July 18, 2019 [Page 20] Internet-Draft DetNet Model January 2019 description "The TTL value of the label to be pushed."; } } } case label-swap { container label-swap { description "Label swap operation."; leaf out-label { type uint32; mandatory true; description "The out MPLS label."; } leaf ttl-action { type ttl-action-definition; description "The label ttl actions: - No-action, or - Copy to inner label,or - Decrease (the in label) by 1 and copy to the out label."; } } } } } } grouping mpls-detnet-header { description "The MPLS DetNet encapsulation header information."; leaf service-label { type uint32; mandatory true; description "The service label."; } leaf control-word { type uint32; mandatory true; description "The control word of the DetNet header."; } } Geng, et al. Expires July 18, 2019 [Page 21] Internet-Draft DetNet Model January 2019 grouping transport-tunnel-encap{ description "Defines the transport tunnel encapsulation header."; choice tunnel-type { description "Tunnel type includes: IPv4, IPv6, MPLS."; case IPv4 { description "IPv4 tunnel."; container ipv4-encapsulation { description "IPv4 encapsulation."; uses ipv4-header; } } case IPv6 { description "IPv6 tunnel."; container ipv6-encapsulation { description "IPv6 encapsulation."; uses ipv6-header; } } case MPLS { description "MPLS tunnel."; container mpls-encapsulation { description "MPLS encapsulation."; uses mpls-header; } } } } grouping detnet-transport-instance { description "An instance of the DetNet transport layer, which depends on the specific data plane that is used as the underlay tunnel."; uses transport-tunnel-encap; uses detnet-transport-qos; } grouping ip-flow-identification { description Geng, et al. Expires July 18, 2019 [Page 22] Internet-Draft DetNet Model January 2019 "IP flow identification."; choice ip-flow-type { description "IP flow types: IPv4, IPv6."; case ipv4 { description "IPv4 flow identification."; leaf src-ipv4-address { type inet:ipv4-address; description "The source IP address of the header."; } leaf dest-ipv4-address { type inet:ipv4-address; description "The destination IP address of the header."; } leaf dscp { type uint8; description "The DSCP field of the header."; } } case ipv6 { description "IPv6 flow identification."; leaf src-ipv6-address { type inet:ipv6-address; description "The source IP address of the header."; } leaf dest-ipv6-address { type inet:ipv6-address; description "The destination IP address of the header."; } leaf traffic-class { type uint8; description "The traffic class value of the header."; } leaf flow-label { type inet:ipv6-flow-label; description "The flow label of the header."; } } } Geng, et al. Expires July 18, 2019 [Page 23] Internet-Draft DetNet Model January 2019 leaf source-port { type inet:port-number; description "The source port number."; } leaf destination-port { type inet:port-number; description "The destination port number."; } leaf protocol { type uint8; description "The protocol id of the header."; } } grouping l3-flow-identification { description "Layer 3 flow identification in the DetNet domain."; choice flow-type { description "L3 DetNet flow types: IP and MPLS."; case IP { description "IP (IPv4 or IPv6) flow identification."; uses ip-flow-identification; } case MPLS { description "MPLS flow identification."; leaf service-label { type uint32; mandatory true; description "The service label."; } } } } //l3-flow-identification grouping in-segments { description "From a receiving node point of view, In-segments are a set of instances of a DetNet flow at the receiving node. This occurs when Packet Replication Function (PRF) is enabled at an upstream node or Geng, et al. Expires July 18, 2019 [Page 24] Internet-Draft DetNet Model January 2019 multiple flows map/aggregate to a single DetNet flow."; list in-segment { key "in-segment-id"; description "A list of in segments, there will be multiple in-segments for a DetNet flow when PRF and PEF enabled."; leaf in-segment-id { type uint32; description "in-segment identifier."; } uses l3-flow-identification; leaf service-function { type service-function-type; description "DetNet service function indication."; } } } grouping out-segments { description "Out-segments are a set of instances of a DetNet flow, this occurs when implement packet replication function, where an in-segment of a DetNet flow is replicated to multiple out-segments."; list out-segment { key "out-segment-id"; description "A list of segments, there will be multiple out-segments when perform PRF."; leaf out-segment-id { type uint32; description "The out-segment identifier"; } container detnet-service-encapsulation { description "Only MPLS based DetNet defines DetNet Geng, et al. Expires July 18, 2019 [Page 25] Internet-Draft DetNet Model January 2019 service layer. The service encapsulation includes service label and control word."; uses mpls-detnet-header; } container detnet-transport-encapsulation { description "Each out-segment corresponds to a transport instance."; uses detnet-transport-instance; } } } grouping detnet-service-instance{ description "An end-2-end DetNet service is consisted of multiple segments. The concept of segment is similar to PW segment. For DetNet, since the existing of PREOF, there could be three cases: 1 - One in-segment maps to multiple out-segments, when implement PRF; 2 - Multiple in-segments map to one out-segment, when implement PEF; 3 - Multiple in-segments map to multiple out-segments, when implement a combination of PEF and PRF."; leaf name { type string; description "The name of the service instance. This MUST be unique across all service instances in a given network device."; } container flow-rank{ description "TBD based on the data plane solution."; } container service-rank{ description "TBD based on the data plane solution."; } uses in-segments; uses out-segments; } grouping l2-flow-identification-at-uni { Geng, et al. Expires July 18, 2019 [Page 26] Internet-Draft DetNet Model January 2019 description "Layer 2 flow identification at UNI."; leaf source-mac-address { type yang:mac-address; description "The source MAC address used for flow identification."; } leaf destination-mac-address { type yang:mac-address; description "The destination MAC address used for flow identification."; } leaf ethertype { type eth:ethertype; description "The Ethernet Type (or Length) value represented in the canonical order defined by IEEE 802. The canonical representation uses lowercase characters."; reference "IEEE 802-2014 Clause 9.2"; } leaf vlan-id { type uint16 { range "1..4094"; } description "Vlan Identifier used for L2 flow identification."; } container pcp { //Todo description "PCP used for L2 flow identification."; } } grouping l3-flow-identification-at-uni { description "Layer 3 flow identification at UNI."; uses ip-flow-identification; } grouping traffic-specification { description Geng, et al. Expires July 18, 2019 [Page 27] Internet-Draft DetNet Model January 2019 "traffic-specification specifies how the Source transmits packets for the flow. This is the promise/request of the Source to the network. The network uses this traffic specification to allocate resources and adjust queue parameters in network nodes."; reference "draft-ietf-detnet-flow-information-model"; leaf interval { type uint32; description "The period of time in which the traffic specification cannot be exceeded"; } leaf max-packets-per-interval{ type uint32; description "The maximum number of packets that the source will transmit in one Interval."; } leaf max-payload-size{ type uint32; description "The maximum payload size that the source will transmit."; } leaf average-packets-per-interval { type uint32; description "The average number of packets that the source will transmit in one Interval"; } leaf average-payload-size { type uint32; description "The average payload size that the source will transmit."; } } grouping client-flows-at-uni { description "The attributes of the client flow at UNI. When flow aggregation is enabled at ingress, multiple client flows map to a DetNet service instance."; list client-flow { key "flow-id"; Geng, et al. Expires July 18, 2019 [Page 28] Internet-Draft DetNet Model January 2019 description "A list of client flows."; leaf flow-id { type uint32; description "Flow identifier that is unique in a network device for client flow identification"; } choice flow-type{ description "Client flow type: layer 2 flow, layer 3 flow."; case l2-flow-identfication { description "Ethernet flow identification."; uses l2-flow-identification-at-uni; } case l3-flow-identification { description "layer 3 flow identification, including IPv4,IPv6 and MPLS."; uses l3-flow-identification-at-uni; } } container traffic-specification { description "The traffic specification of the client flow."; uses traffic-specification; } } } grouping detnet-service-proxy-instance { description "Maps between App-flows and DetNet flows"; uses client-flows-at-uni; container detnet-service-instance { description "A DetNet service instance."; uses detnet-service-instance; } } container detnet-flow{ description "DetNet flow configuration and status reporting."; choice detnet-node-role{ description Geng, et al. Expires July 18, 2019 [Page 29] Internet-Draft DetNet Model January 2019 "Depends on the role of a node to configure corresponding flow parameters."; case transit-node{ description "DetNet flow configuration parameters for transit nodes."; container transit-node { description "transit node container."; uses detnet-transport-qos; } } case relay-node{ description "DetNet flow configuration parameters for relay nodes."; container relay-node { description "Relay node container."; uses detnet-service-instance; } } case edge-node{ description "DetNet flow configuration parameters for edge nodes."; container edge-node { description "Edge node container."; uses detnet-service-proxy-instance; } } case end-station { description "DetNet flow configuration parameters for end stations."; container end-station { description "End station container."; uses detnet-service-proxy-instance; } } } } } Geng, et al. Expires July 18, 2019 [Page 30] Internet-Draft DetNet Model January 2019 6. DetNet Configuration Model Classification This section defines three classes of DetNet configuration model: fully distributed configuration model, fully centralized configuration model, hybrid configuration model, based on different network architectures, showing how configuration information exchanges between various entities in the network. 6.1. Fully Distributed Configuration Model In a fully distributed configuration model, UNI information is transmitted over DetNet UNI protocol from the user side to the network side; then UNI information and network configuration information propagate in the network over distributed control plane protocol. For example: 1) IGP collects topology information and DetNet capabilities of network([I-D.geng-detnet-info-distribution]); 2) Control Plane of the Edge Node(Ingress) receives a flow establishment request from UNI and calculates a/some valid path(s); 3) Using RSVP-TE, Edge Node(Ingress) sends a PATH message with explicit route. After receiving the PATH message, the other Edge Node(Egress) sends a Resv message with distributed label and resource reservation request. Current distributed control plane protocol,e.g., RSVP-TE[RFC3209], SRP[IEEE802.1Qcc], can only reserve bandwidth along the path, while the configuration of a fine-grained schedule, e.g.,Time Aware Shaping(TAS) defined in [IEEE802.1Qbv], is not supported. The fully distributed configuration model is not covered by this draft. It should be discussed in the future DetNet control plane work. 6.2. Fully Centralized Configuration Model In the fully centralized configuration model, UNI information is transmitted from Centralized User Configuration (CUC) to Centralized Network Configuration(CNC). Configurations of routers for DetNet flows are performed by CNC with network management protocol. For example: 1) CNC collects topology information and DetNet capability of network through Netconf; Geng, et al. Expires July 18, 2019 [Page 31] Internet-Draft DetNet Model January 2019 2) CNC receives a flow establishment request from UNI and calculates a/some valid path(s); 3) CNC configures the devices along the path for flow transmission. 6.3. Hybrid Configuration Model In the hybrid configuration model, controller and control plane protocols work together to offer DetNet service, and there are a lot of possible combinations. For example: 1) CNC collects topology information and DetNet capability of network through IGP/BGP-LS; 2) CNC receives a flow establishment request from UNI and calculates a/some valid path(s); 3) Based on the calculation result, CNC distributes flow path information to Edge Node(Ingress) and other information(e.g. replication/elimination) to the relevant nodes. 4) Using RSVP-TE, Edge Node(Ingress) sends a PATH message with explicit route. After receiving the PATH message, the other Edge Node(Egress) sends a Resv message with distributed label and resource reservation request. or 1) Controller collects topology information and DetNet capability of network through IGP/BGP-LS; 2) Control Plane of Edge Node(Ingress) receives a flow establishment request from UNI; 3) Edge Node(Ingress) sends the path establishment request to CNC through PCEP; 4) After Calculation, CNC sends back the path information of the flow to the Edge Node(Ingress) through PCEP; 5) Using RSVP-TE, Edge Node(Ingress) sends a PATH message with explicit route. After receiving the PATH message, the other Edge Node(Egress) sends a Resv message with distributed label and resource reservation request. There are also other variations that can be included in the hybrid model. This draft can not coverer all the control plane data needed Geng, et al. Expires July 18, 2019 [Page 32] Internet-Draft DetNet Model January 2019 in hybrid configuration models. Every solution has there own mechanism and corresponding parameters to make it work. Editor's Note: 1. There are a lot of optional DetNet configuration models, and different scenario in different use case can choose one of them based on its conditions. Maybe next step of the work is to pick up one or more typical scenarios and give a practical solution. 2. [IEEE802.1Qcc] also defines three TSN configuration models: fully-centralized model, fully-distributed model, centralized Network / distributed User Model. This section defines the configuration model roughly the same, to keep the design of L2 and L3 in the same structure. Hybrid configuration model is slightly different from the 'centralized Network / distributed User Model'. The hybrid configuration model intends to contain more variations. 7. Open Issues There are some open issues that are still under discussion: o The Relationship with 802.1 TSN YANG models is TBD. TSN YANG models include: P802.1Qcw, which defines TSN YANG for Qbv, Qbu, and Qci, and P802.1CBcv, which defines YANG for 802.1CB. The possible problem here is how to avoid possible overlap among yang models defined in IETF and IEEE. A common YANG model may be defined in the future to shared by both TSN and DetNet. More discussion are needed here. o How to support DetNet OAM is TBD. These issues will be resolved in the following versions of the draft. 8. IANA Considerations This document makes no request of IANA. Note to RFC Editor: this section may be removed on publication as an RFC. 9. Security Considerations Geng, et al. Expires July 18, 2019 [Page 33] Internet-Draft DetNet Model January 2019 10. Acknowledgements 11. References 11.1. Normative References [I-D.finn-detnet-bounded-latency] Finn, N., Boudec, J., Mohammadpour, E., Zhang, J., Varga, B., and J. Farkas, "DetNet Bounded Latency", draft-finn- detnet-bounded-latency-02 (work in progress), October 2018. [I-D.ietf-detnet-architecture] Finn, N., Thubert, P., Varga, B., and J. Farkas, "Deterministic Networking Architecture", draft-ietf- detnet-architecture-10 (work in progress), December 2018. [I-D.ietf-detnet-dp-sol-ip] Korhonen, J. and B. Varga, "DetNet IP Data Plane Encapsulation", draft-ietf-detnet-dp-sol-ip-01 (work in progress), October 2018. [I-D.ietf-detnet-dp-sol-mpls] Korhonen, J. and B. Varga, "DetNet MPLS Data Plane Encapsulation", draft-ietf-detnet-dp-sol-mpls-01 (work in progress), October 2018. [I-D.ietf-detnet-flow-information-model] Farkas, J., Varga, B., Cummings, R., Jiang, Y., and Y. Zha, "DetNet Flow Information Model", draft-ietf-detnet- flow-information-model-02 (work in progress), October 2018. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . Geng, et al. Expires July 18, 2019 [Page 34] Internet-Draft DetNet Model January 2019 11.2. Informative References [I-D.geng-detnet-info-distribution] Geng, X., Chen, M., and Z. Li, "IGP-TE Extensions for DetNet Information Distribution", draft-geng-detnet-info- distribution-03 (work in progress), October 2018. [I-D.ietf-detnet-use-cases] Grossman, E., "Deterministic Networking Use Cases", draft- ietf-detnet-use-cases-20 (work in progress), December 2018. [I-D.ietf-teas-yang-te] Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and I. Bryskin, "A YANG Data Model for Traffic Engineering Tunnels and Interfaces", draft-ietf-teas-yang-te-17 (work in progress), October 2018. [I-D.ietf-teas-yang-te-topo] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and O. Dios, "YANG Data Model for Traffic Engineering (TE) Topologies", draft-ietf-teas-yang-te-topo-18 (work in progress), June 2018. [I-D.thubert-tsvwg-detnet-transport] Thubert, P., "A Transport Layer for Deterministic Networks", draft-thubert-tsvwg-detnet-transport-01 (work in progress), October 2017. [I-D.varga-detnet-service-model] Varga, B. and J. Farkas, "DetNet Service Model", draft- varga-detnet-service-model-02 (work in progress), May 2017. [IEEE802.1CB] "IEEE, "Frame Replication and Elimination for Reliability (IEEE Draft P802.1CB)", 2017, .", 2016. [IEEE802.1Q-2014] "IEEE, "IEEE Std 802.1Q Bridges and Bridged Networks", 2014, .", 2014. Geng, et al. Expires July 18, 2019 [Page 35] Internet-Draft DetNet Model January 2019 [IEEE802.1Qbu] "IEEE, "IEEE Std 802.1Qbu Bridges and Bridged Networks - Amendment 26: Frame Preemption", 2016, .", 2016. [IEEE802.1Qbv] "IEEE, "IEEE Std 802.1Qbu Bridges and Bridged Networks - Amendment 25: Enhancements for Scheduled Traffic", 2015, .", 2016. [IEEE802.1Qcc] "IEEE, "Stream Reservation Protocol (SRP) Enhancements and Performance Improvements (IEEE Draft P802.1Qcc)", 2017, .". [IEEE802.1Qch] "IEEE, "Cyclic Queuing and Forwarding (IEEE Draft P802.1Qch)", 2017, .", 2016. [IEEE802.1Qci] "IEEE, "Per-Stream Filtering and Policing (IEEE Draft P802.1Qci)", 2016, .", 2016. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, . [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. Yasukawa, Ed., "Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to- Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI 10.17487/RFC4875, May 2007, . [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, . Geng, et al. Expires July 18, 2019 [Page 36] Internet-Draft DetNet Model January 2019 Authors' Addresses Xuesong Geng Huawei Technologies Email: gengxuesong@huawei.com Mach(Guoyi) Chen Huawei Technologies Email: mach.chen@huawei.com Zhenqiang Li China Mobile Email: lizhenqiang@chinamobile.com Reshad Rahman Cisco Systems Email: rrahman@cisco.com Geng, et al. Expires July 18, 2019 [Page 37]