Network Working Group                                            X. Geng
Internet-Draft                                                   M. Chen
Intended status: Standards Track                     Huawei Technologies
Expires: September 27, 2019 January 9, 2020                                         Y. Ryoo
                                                                    ETRI
                                                                   Z. Li
                                                            China Mobile
                                                               R. Rahman
                                                           Cisco Systems
                                                          March 26,
                                                           July 08, 2019

       Deterministic Networking (DetNet) Configuration YANG Model
                       draft-ietf-detnet-yang-02
                       draft-ietf-detnet-yang-03

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 September 27, 2019. January 9, 2020.

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 . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  DetNet Configuration Model  . . . . . . . . . . . . . . . . .   4   3
     3.1.  DetNet Service Proxy Appliction Flow Configuration Attributes . . . . . .   4   3
     3.2.  DetNet Service Layer Sub-layer Configuration Attributes . . . . . .   5   4
     3.3.  DetNet Transport Layer Forwarding Sub-layer Configuration Attributes  . .   4
     3.4.  DetNet Sub-network Configurations Attributes  . . .   8 . . .   5
   4.  Overview of DetNet Configuration YANG Structure . . . . . . . . . . . . . .   5
     4.1.  DetNet YANG Structure Considerations  . . . . . . . . . .   5
     4.2.  DetNet YANG Structure . . . . . . . . . . . . . . . . . .   6
       4.2.1.  YANG Structure of Application Flow  . . . . . . . . .   6
       4.2.2.  YANG Structure of DetNet Service Sub-layer  . . . . .   6
       4.2.3.  YANG Structure of DetNet Forwarding Sub-layer . . . .   8
       4.2.4.  YANG Structure of DetNet sub-network  . . . . . . . .   9
   5.  DetNet Configuration YANG Model . . . . . . . . . . . . . . .  17  10
   6.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .  42  34
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  43  34
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  43  34
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  43  34
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  43  34
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  43  34
     10.2.  Informative References . . . . . . . . . . . . . . . . .  44  35
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  46  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

   Information models for DetNet are categorized as:

   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, service
   models are used between the user and the network
      operator. configuration models, which is defined in
   [I-D.ietf-detnet-flow-information-model].

   Configuration information models are used between the
      management/control plane entity of the network for DetNet topology discovery and the network
      nodes.

   They are shown in the Figure 1.

               User                Network Operator
                      flow/service
              +---+      model        +---+
              |   | <---------------> | X |    management/control
              +---+                   +-+-+       plane entity
                                        ^
                                        |
   DetNet flow configuration
                                        | . This document defines a YANG model
                                 +------------+
                                 v      |     |
                                +-+     |     v  network
                                +-+     v    +-+  nodes
                                       +-+   +-+
                                       +-+

                     Figure 1. Three Information Models for
   DetNet flow configurations based on YANG [RFC7950] data types and modeling
   language defined in [RFC6991] models include:

   DetNet YANG [RFC7950] [RFC6991] models are used for DetNet service
   configurations, QoS configuration and topology discovery.  DetNet
   topology [RFC7950].  A YANG model for
   topology discovery is defined in ietf-detnet-topology-yang.  This
   document defines two YANG models, which are referred to as [I-D.ietf-detnet-topology-yang].
   The DetNet
   flow configuration model and DetNet transport QoS model.  DetNet flow YANG model is designed for DetNet flow path configuration and
   establishment, flow status
   reporting. reporting, and DetNet transport QoS model is designed for QoS attributes functions
   configuration of transport tunnels in order to achieve end-to-end bounded latency and zero
   congestion loss.

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 App-flow configuration,
   DetNet Service Layer Sub-layer configuration, and DetNet Forwarding Sub-
   layer configuration and DetNet
   Transport Layer configuration. sub-network.  The corresponding
   attributes used in different layers sub-layers are defined in Section 3.1,
   3.2, 3.3, 3.4 respectively.

3.1.  DetNet Service Proxy Appliction Flow Configuration Attributes

   DetNet service proxy application flow 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

   Application flow 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:

                  |  +--rw client-flow* [flow-id]
                  |  |  +--rw flow-id                    uint32
                  |  |  +--rw flow-rank?                 boolean
                  |  |  +--rw (flow-type)?
                  |  |  |  +--:(l2-flow)
                  |  |  |  |  +--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)
                  |  |  |     +--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 service-function?                  service-function-type
                  |  +--rw sequence-number-generation-type?   sequence-number-generation
                  |  +--rw sequence-number-length?            uint8

3.2.  DetNet Service Layer Sub-layer Configuration Attributes

   DetNet service functions, e.g., DetNet tunnel initialization/
   termination and service protection, are provided in DetNet service
   layer.
   sub-layer.  To support these functions, the following service
   attributes need to be configured:

   o  DetNet flow identification, refers to Section 7.1.3 8.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 8.3 of
      [I-D.ietf-detnet-flow-information-model].

   o  Service Rank, refers to Section 7.4 16 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, Sub-layer, refers to Section 6.2 of
      [I-D.ietf-detnet-dp-sol-mpls] 4.5 and Section 3 4.6 of
      [I-D.ietf-detnet-dp-sol-ip]
      [I-D.ietf-detnet-mpls]

   o  Service encapsulation,  Forwarding Sub-layer, refers to Section 6.2 4.3 of
      [I-D.ietf-detnet-dp-sol-mpls]

   o  Transport encapsulation, refers to
      [I-D.ietf-detnet-ip] and Section 6.2 of
      [I-D.ietf-detnet-dp-sol-mpls]and 4.5 and Section 3 4.6 of
      [I-D.ietf-detnet-dp-sol-ip]

   The
      [I-D.ietf-detnet-mpls]

3.3.  DetNet Forwarding Sub-layer Configuration Attributes

   As defined in [I-D.ietf-detnet-architecture], DetNet forwarding sub-
   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 forwarding sub-layer.

   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.

3.4.  DetNet Sub-network Configurations Attributes

   TBD

4.  Overview of DetNet YANG module Structure

4.1.  DetNet YANG Structure Considerations

   The picture shows that the general structure is shown below:

          +--:(relay-node) {detnet-mpls-dp-sol}?
         |  +--rw relay-node
         |     +--rw name?           string
         |     +--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
         |     |  | of the DetNet YANG
   Model:

                        +-----------+
                        |ietf-detnet|
                        +-----+-----+
                              |
         +-------------+------+--------+--------------+
         |     +--rw dest-ipv6-address?   inet:ipv6-address             |               |              |
   +-----+-----+ +-----+-----+ +-------+------+ +-----+-----+
   | App Flows | |service s-l| |forwarding s-l| |sub-network|
   +-----------+ +-----------+ +--------------+ +-----------+

   There are four instances in DetNet YANG Model: App-flow instance,
   service sub-layer instance, forwarding sub-layer instance and sub-
   network instance, respectively corresponding to four parts of DetNet
   functions defined in section 3.  In each instance, there are four
   elements: name, in-segments, out-segments and operations, which
   means:

   o  Name: indicates the key value of the instance identification.

   o  In-segments: indicates the key value of identification, e.g.,
      Layer 2 App flow identification, Layer 3 App flow identification
      and DetNet flow identification.

   o  Out-segments: indicates the information of DetNet processing(e.g.,
      DetNet forwarding, DetNet header Encapsulation) and the mapping
      relationship to the lower sub-layer/sub-network.

   o  Operations: indicates DetNet functions, e.g., DetNet forwarding
      functions, DetNet Service functions, DetNet Resource Reservation.

   These elements are different when the technologies used for the
   specific instance is different.  So this structure is abstract, which
   allows for different technology specifics as defined in different
   data plane drafts.

4.2.  DetNet YANG Structure

4.2.1.  YANG Structure of Application Flow

   The picture below shows that the general YANG structure of DetNet
   App-flow:

         +--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) {ipv4-tunnel}?
         |           |  |  +--rw ipv4-encapsulation
         |           |  |     +--rw src-ipv4-address     inet:ipv4-address
         |           |  |     +--rw dest-ipv4-address    inet:ipv4-address
         |           |  |     +--rw protocol             uint8
         |           |  |     +--rw ttl?                 uint8
         |           |  |     +--rw dscp?                uint8
         |           |  +--:(IPv6) {ipv6-tunnel}?
         |           |  |  +--rw ipv6-encapsulation
         |           |  |     +--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) {mpls-tunnel}?
         |           |  |  +--rw mpls-encapsulation
         |           |  |     +--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
         |           |  +--:(MPLS-over-UDP) {mpls-over-udp-tunnel}?
         |           |     +--rw mpls-over-udp-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 source-port?         inet:port-number
         |           |        +--rw destination-port?    inet:port-number
         |           |        +--rw (address-family)?
         |           |           +--:(IPv4)
         |           |           |  +--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 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

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.

   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:

            +--:(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

   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) {detnet-mpls-dp-sol}?
         |  +--rw relay-node
         |     +--rw name?           string
         |     +--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
         |        +--rw detnet-transport-encapsulation
         |           +--rw (tunnel-type)?
         |           |  +--:(IPv4) {ipv4-tunnel}?
         |           |  |  +--rw ipv4-encapsulation
         |           |  |     +--rw src-ipv4-address     inet:ipv4-address
         |           |  |     +--rw dest-ipv4-address    inet:ipv4-address
         |           |  |     +--rw protocol             uint8
         |           |  |     +--rw ttl?                 uint8
         |           |  |     +--rw dscp?                uint8
         |           |  +--:(IPv6) {ipv6-tunnel}?
         |           |  |  +--rw ipv6-encapsulation
         |           |  |     +--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) {mpls-tunnel}?
         |           |  |  +--rw mpls-encapsulation
         |           |  |     +--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
         |           |  +--:(MPLS-over-UDP) {mpls-over-udp-tunnel}?
         |           |     +--rw mpls-over-udp-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 source-port?         inet:port-number
         |           |        +--rw destination-port?    inet:port-number
         |           |        +--rw (address-family)?
         |           |           +--:(IPv4)
         |           |           |  +--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 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
         |           +--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) {detnet-mpls-dp-sol}?
         |  +--rw edge-node
         |     +--rw (edge-node-type)?
         |        +--:(ingress-node)
         |        |  +--rw client-flow* [flow-id]
         |        |  |  +--rw flow-id                    uint32
         |        |  |  +--rw flow-rank?                 boolean
         |        |  |  +--rw (flow-type)?
         |        |  |  |  +--:(l2-flow)
         |        |  |  |  |  +--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)
         |        |  |  |     +--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 service-function?                  service-function-type
         |        |  +--rw sequence-number-generation-type?   sequence-number-generation
         |        |  +--rw sequence-number-length?            uint8
         |        |  +--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) {ipv4-tunnel}?
         |        |        |  |  +--rw ipv4-encapsulation
         |        |        |  |     +--rw src-ipv4-address     inet:ipv4-address
         |        |        |  |     +--rw dest-ipv4-address    inet:ipv4-address
         |        |        |  |     +--rw protocol             uint8
         |        |        |  |     +--rw ttl?                 uint8
         |        |        |  |     +--rw dscp?                uint8
         |        |        |  +--:(IPv6) {ipv6-tunnel}?
         |        |        |  |  +--rw ipv6-encapsulation
         |        |        |  |     +--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) {mpls-tunnel}?
         |        |        |  |  +--rw mpls-encapsulation
         |        |        |  |     +--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
         |        |        |  +--:(MPLS-over-UDP) {mpls-over-udp-tunnel}?
         |        |        |     +--rw mpls-over-udp-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 source-port?         inet:port-number
         |        |        |        +--rw destination-port?    inet:port-number
         |        |        |        +--rw (address-family)?
         |        |        |           +--:(IPv4)
         |        |        |           |  +--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 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
         |        |        +--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
         |        +--:(egress-node)
         |           +--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
         | app-flow
         |  +--rw operations
         |  |  +--rw destination-port?    inet:port-number sequence-number
         |  |     +--rw sequence-number-generation-type?   sequence-number-generation-type
         |  |     +--rw protocol? sequence-number-length?            uint8
         |           |  |  +--:(MPLS)
         |           |  |  +--rw service-label        uint32 in-segments
         |  |  +--rw service-function?    service-function-type app-flow-type?             flow-type-ref
         |           +--rw (tunnel-type)?  |  +--rw source-mac-address?        yang:mac-address
         |  +--:(ipv4) {ipv4-tunnel}?  |  +--rw destination-mac-address?   yang:mac-address
         |  |  +--rw ipv4-decap
         | ethertype?                 eth:ethertype
         |  |  +--rw ipv4-decap    tunnel-decap-action-def
         | vlan-id?                   uint16
         |  |  +--rw ttl-action?   ttl-action-def
         | pcp?                       uint8
         |  +--:(ipv6) {ipv6-tunnel}?  |  +--rw src-ipv4-prefix            inet:ipv4-prefix
         |  |  +--rw ipv6-decap
         | dest-ipv4-prefix           inet:ipv4-prefix
         |  |  +--rw ipv6-decap          tunnel-decap-action-def
         | protocol                   uint8
         |  |  +--rw hop-limit-action?   hop-limit-action-def dscp?                      uint8
         |  |  +--:(mpls) {mpls-tunnel}?  +--rw dscp-bitmask?              uint8
         |  |  +--rw label-pop src-ipv6-prefix            inet:ipv6-prefix
         |  |  +--rw label-pop     mpls-label-action-def dest-ipv6-prefix           inet:ipv6-prefix
         |  |  +--rw ttl-action?   ttl-action-def next-header                uint8
         |           +--rw label-pop                          mpls-label-action-def  |  +--rw ttl-action?                        ttl-action-def
         +--:(end-station)
            +--rw end-station
               +--rw (edge-node-type)?
                  +--:(ingress-node) traffic-class?             uint8
         |  |  +--rw client-flow* [flow-id] traffic-class-bitmask?     uint8
         |  |  +--rw flow-id                    uint32 flow-label?                inet:ipv6-flow-label
         |  |  +--rw flow-rank? flow-label-flag?           boolean
         |  |  +--rw (flow-type)?
                  |  |  |  +--:(l2-flow)
                  |  | lower-source-port?         inet:port-number
         |  |  +--rw source-mac-address?        yang:mac-address
                  |  | upper-source-port?         inet:port-number
         |  |  +--rw destination-mac-address?   yang:mac-address
                  |  | lower-destination-port?    inet:port-number
         |  |  +--rw ethertype?                 eth:ethertype
                  |  |  | upper-destination-port?    inet:port-number
         |  +--rw vlan-id?                   uint16 out-segments
         |     +--rw detnet-service-sub-layer?   lower-layer-ref

4.2.2.  YANG Structure of DetNet Service Sub-layer

   The picture shows that the general YANG structure of DetNet Service
   Sub-layer:

         +--rw service-sub-layer
         |  +--rw operations
         |  |  +--rw pcp
                  | service-operation
         |  |  +--:(l3-flow)  |  +--rw service-operation-type?   service-operation-ref
         |  |  +--rw (ip-flow-type)? service-protection
         |  |     +--rw service-protection-type?   service-protection-type
         |  +--rw in-segments
         |  +--:(ipv4)  |  +--rw detnet-service-type?   flow-type-ref
         |  |  +--rw detnet-service-list* [detnet-service-index]
         |  |     +--rw src-ipv4-address?          inet:ipv4-address
                  | detnet-service-index        uint8
         |  |     +--rw src-ipv4-prefix             inet:ipv4-prefix
         |  |     +--rw dest-ipv4-address?         inet:ipv4-address
                  | dest-ipv4-prefix            inet:ipv4-prefix
         |  |     +--rw protocol                    uint8
         |  |     +--rw dscp?                       uint8
         |  |  |     |  +--:(ipv6)
                  |  |  |     |     +--rw src-ipv6-address?          inet:ipv6-address dscp-bitmask?               uint8
         |  |     +--rw src-ipv6-prefix             inet:ipv6-prefix
         |  |     +--rw dest-ipv6-address?         inet:ipv6-address dest-ipv6-prefix            inet:ipv6-prefix
         |  |     +--rw next-header                 uint8
         |  |     +--rw traffic-class?              uint8
         |  |     +--rw traffic-class-bitmask?      uint8
         |  |     +--rw flow-label?                 inet:ipv6-flow-label
         |  |  |     +--rw source-port?               inet:port-number
                  | flow-label-flag?            boolean
         |  |     +--rw destination-port?          inet:port-number
                  | mpls-flow-identification
         |  |        +--rw protocol?                  uint8 platform-label-flag?        boolean
         |  |        +--rw traffic-specification non-platform-label-space
         |  |        |  +--rw interval?                       uint32 incoming-interface?         if:interface-ref
         |  |        |  +--rw max-packets-per-interval?       uint32 non-platform-label-stack* [index]
         |  |        |     +--rw max-payload-size?               uint32 index    uint8
         |  |        |     +--rw average-packets-per-interval?   uint32 label?   rt-type:mpls-label
         |  |        |     +--rw average-payload-size?           uint32 tc?      uint8
         |  |        +--rw service-function?                  service-function-type platform-label-space
         |  |           +--rw sequence-number-generation-type?   sequence-number-generation label?   rt-type:mpls-label
         |  |           +--rw sequence-number-length? tc?      uint8
         |  +--rw out-segment* [out-segment-id] out-segments
         |     +--rw out-segment-id                    uint32 detnet-service-processing-type?   flow-type-ref
         |     +--rw detnet-service-encapsulation
         |     |        +--rw service-label    uint32
                  | detnet-service-processing-list* [detnet-service-processing-index]
         |           +--rw control-word? detnet-service-processing-index     uint32
         |           +--rw detnet-transport-encapsulation
                  |        +--rw (tunnel-type)?
                  |        |  +--:(IPv4) {ipv4-tunnel}?
                  | ip-flow
         |           |  +--rw ipv4-encapsulation ipv4-flow
         |           |  |  +--rw src-ipv4-address     inet:ipv4-address
         |           |  |  +--rw dest-ipv4-address    inet:ipv4-address
         |           |  |  +--rw protocol             uint8
         |           |  |  +--rw ttl?                 uint8
                  |        |  |     +--rw dscp?                uint8
         |           |  +--:(IPv6) {ipv6-tunnel}?
                  |        |  |  +--rw ipv6-encapsulation ipv6-flow
         |           |  |  +--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) {mpls-tunnel}?
                  | l4-port-header
         |           |     +--rw mpls-encapsulation
                  | source-port?        inet:port-number
         |           |     +--rw label-operations* [label-oper-id]
                  |        | destination-port?   inet:port-number
         |           +--rw label-oper-id    uint32
                  | mpls-flow
         |           |  +--rw (label-actions)?
                  |        |  |           +--:(label-push)
                  |        | detnet-mpls-label-stack* [index]
         |           |     +--rw label-push
                  |        | index                    uint8
         |           |     +--rw label        uint32 label?                   rt-type:mpls-label
         |           |     +--rw tc?                      uint8
         |           |     +--rw s-bit?                   boolean
         |           |  |     +--rw d-cw-encapsulate-flag?   boolean
         |           +--rw tc-value?    uint8 detnet-forwarding-sub-layer-info
         |              +--rw detnet-forwarding-sub-layer?   lower-layer-ref

4.2.3.  YANG Structure of DetNet Forwarding Sub-layer

   The picture shows that the general YANG structure of DetNet
   Forwarding Sub-layer:

         +--rw forwarding-sub-layer
         |  +--rw operations
         |  |  +--rw ttl-value?   uint8
                  | forwarding-operation
         |  |           +--:(label-swap)  |  +--rw forwarding-operation-type?   forwarding-operation-ref
         |  |  +--rw label-swap resource-allocate
         |  |  |  +--rw out-label interval?                       uint32
         |  |  |  +--rw ttl-action?   ttl-action-definition
                  |        |  +--:(MPLS-over-UDP) {mpls-over-udp-tunnel}?
                  | max-packets-per-interval?       uint32
         |     +--rw mpls-over-udp-encaplustion  |  |  +--rw label-operations* [label-oper-id] max-payload-size?               uint32
         |  |  |  +--rw label-oper-id average-packets-per-interval?   uint32
         |  |  |  +--rw (label-actions)?
                  |        |        |     +--:(label-push)
                  |        | average-payload-size?           uint32
         |  |  +--rw label-push
                  |        |        | qos
         |  +--rw label        uint32 in-segments
         |  |  +--rw detnet-forwarding-type?     flow-type-ref
         |  |  +--rw s-bit?       boolean src-ipv4-prefix             inet:ipv4-prefix
         |  |  +--rw dest-ipv4-prefix            inet:ipv4-prefix
         |  |  +--rw tc-value? protocol                    uint8
         |  |        |     |  +--rw ttl-value? dscp?                       uint8
         |  |  +--rw dscp-bitmask?               uint8
         |     +--:(label-swap)  |  +--rw src-ipv6-prefix             inet:ipv6-prefix
         |  |  +--rw label-swap
                  | dest-ipv6-prefix            inet:ipv6-prefix
         |  |  +--rw out-label     uint32
                  | next-header                 uint8
         |  |  +--rw ttl-action?   ttl-action-definition traffic-class?              uint8
         |  |  +--rw source-port?         inet:port-number traffic-class-bitmask?      uint8
         |  |  +--rw destination-port?    inet:port-number flow-label?                 inet:ipv6-flow-label
         |  |  +--rw (address-family)?
                  | flow-label-flag?            boolean
         |           +--:(IPv4)  |  +--rw mpls-flow-identification
         |  |     +--rw src-ipv4-address     inet:ipv4-address
                  | platform-label-flag?        boolean
         |  |     +--rw dest-ipv4-address    inet:ipv4-address non-platform-label-space
         |  |     |  +--rw protocol             uint8 incoming-interface?         if:interface-ref
         |  |     |  +--rw ttl?                 uint8 non-platform-label-stack* [index]
         |  |     |     +--rw dscp? index    uint8
         |  |           +--:(IPv6)
                  |     |     +--rw src-ipv6-address     inet:ipv6-address
                  | label?   rt-type:mpls-label
         |              +--rw dest-ipv6-address    inet:ipv6-address  |     |     +--rw next-header tc?      uint8
         |  |     +--rw traffic-class?       uint8 platform-label-space
         |  |        +--rw flow-label?          inet:ipv6-flow-label label?   rt-type:mpls-label
         |  |        +--rw hop-limit? tc?      uint8
         |  +--rw interval?                       uint32
                  |        +--rw max-packets-per-interval?       uint32
                  |        +--rw max-payload-size?               uint32 out-segments
         |     +--rw average-packets-per-interval?   uint32 detnet-forwarding-processing-type?   flow-type-ref
         |     +--rw average-payload-size?           uint32
                  +--:(egress-node)
                     +--rw in-segment* [in-segment-id] natively-detnet-forwarding
         |  +--rw in-segment-id        uint32     |  +--rw (flow-type)? ipv4-flow
         |     |  +--:(IP)  |  +--rw ipv4-next-hop-address?   inet:ipv4-address
         |     |  +--rw (ip-flow-type)? ipv6-flow
         |     |     +--rw ipv6-next-hop-address?   inet:ipv6-address
         |     +--rw detnet-forwarding-encapsulation
         |  +--:(ipv4)        +--rw ip-flow
         |        |  +--rw ipv4-flow
         |        |  |  +--rw src-ipv4-address? src-ipv4-address     inet:ipv4-address
         |        |  |  |  |  +--rw dest-ipv4-address? dest-ipv4-address    inet:ipv4-address
         |        |  |  +--rw protocol             uint8
         |        |  |  +--rw dscp?                uint8
         |        |  +--rw ipv6-flow
         |        |  +--:(ipv6)  |  +--rw src-ipv6-address     inet:ipv6-address
         |        |  |  +--rw src-ipv6-address? dest-ipv6-address    inet:ipv6-address
         |        |  |  |  +--rw dest-ipv6-address?   inet:ipv6-address
                     | next-header          uint8
         |        |  |  +--rw traffic-class?       uint8
         |        |  |  |  +--rw flow-label?          inet:ipv6-flow-label
         |        |  +--rw l4-port-header
         |        |     +--rw source-port?        inet:port-number
         |        |  |     +--rw destination-port?   inet:port-number
         |  |  |        +--rw protocol?            uint8
                     |  |  +--:(MPLS) mpls-flow
         |        |  +--rw service-label        uint32 detnet-mpls-label-stack* [index]
         |  +--rw service-function?    service-function-type
                     +--rw (tunnel-type)?        |  +--:(ipv4) {ipv4-tunnel}?     +--rw index                    uint8
         |        |     +--rw ipv4-decap label?                   rt-type:mpls-label
         |        |     +--rw ipv4-decap    tunnel-decap-action-def tc?                      uint8
         |        |     +--rw ttl-action?   ttl-action-def
                     |  +--:(ipv6) {ipv6-tunnel}? s-bit?                   boolean
         |        |     +--rw ipv6-decap
                     | d-cw-encapsulate-flag?   boolean
         |        +--rw ipv6-decap          tunnel-decap-action-def lower-layer-info
         |           +--rw lower-layer-type?   flow-type-ref
         |           +--rw hop-limit-action?   hop-limit-action-def interface
         |  +--:(mpls) {mpls-tunnel}?           |  +--rw label-pop outgoing-interface?   if:interface-ref
         |           +--rw label-pop     mpls-label-action-def sub-layer
         |              +--rw ttl-action?   ttl-action-def
                     +--rw label-pop                          mpls-label-action-def
                     +--rw ttl-action?                        ttl-action-def sub-layer?   lower-layer-ref

4.2.4.  YANG Structure of DetNet sub-network

   TBD

5.  DetNet Configuration YANG Model

<CODE BEGINS> file "ietf-detnet@20190321.yang" ietf-detnet-config@20190324.yang
module ietf-detnet{ ietf-detnet-config {
  namespace "urn:ietf:params:xml:ns:yang:ietf-detnet";
     //yang-version 1.1; "urn:ietf:params:xml:ns:yang:ietf-detnet-config";
  prefix "detnet-flow"; "ietf-detnet";

  import ietf-yang-types {
    prefix "yang";
  }

  import ietf-interfaces {
       prefix "if";
     }

     import ietf-inet-types{
    prefix "inet";
  }

   /*

  import ietf-ethertypes {
    prefix "eth";
       }*/
  }

  import ietf-routing-types {
    prefix "rt-types"; "rt-type";
  }

  import ietf-interfaces {
    prefix "if";
  }

  organization "IETF DetNet Working Group";

  contact
    "WG Web:   <http://tools.ietf.org/wg/detnet/>
     WG List:  <mailto: detnet@ietf.org>
     WG Chair: Lou Berger
                 <mailto:lberger@labn.net>

                 Janos Farkas
                  <janos.farkas@ericsson.com>
                 <mailto:janos.farkas@ericsson.com>

     Editor:   Xuesong Geng
                <mailto:gengxuesong@huawei.com>

     Editor:   Mach Chen
                <mailto:mach.chen@huawei.com>

     Editor:   Zhenqiang Li
                  <lizhenqiang@chinamobile.com>
                <mailto:lizhenqiang@chinamobile.com>

     Editor:   Reshad Rahman
                  <rrahman@cisco.com>";
                <mailto:rrahman@cisco.com>

     Editor:   Yeoncheol Ryoo
                <mailto:dbduscjf@etri.re.kr>";

  description
    "This YANG module describes the parameters needed
     for DetNet flow configuration and flow status
        reporting."; reporting";

  revision "2018-09-10" 2019-03-24 {
    description "initial revision";
    reference "RFC XXXX: draft-geng-detnet-config-yang-05"; draft-ietf-detnet-yang-02";
  }

     feature ipv4-tunnel

  identity ttl-action {
    description
         "This feature means that a node support
      "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";
  }

  identity config-type {
    description
      "Base identity from which all configuration instances are derived";
  }

  identity App-flow {
    base "config-type";
    description
      "App-flow configuration";
  }

  identity service-sub-layer {
    base "config-type";
    description
      "A DetNet MPLS or IP service sub-layer configuration";
  }

  identity forwarding-sub-layer {
    base "config-type";
    description
      "A DetNet MPLS or IP forwarding sub-layer configuration";
  }

  identity tsn-sub-network {
    base "config-type";
    description
      "A TSN sub-net configuration";
  }

  identity flow-type {
    description
      "Base identity from which all flow type are derived";
  }

  identity ipv4 {
    base "flow-type";
    description
      "An IPv4 tunnel encapsulation capability."; flow";
  }

     feature ipv6-tunnel

  identity ipv6 {
    base "flow-type";
    description
         "This feature means that a node support
      "An IPv6 tunnel encapsulation capability."; flow";
  }

     feature mpls-tunnel

  identity mpls {
    base "flow-type";
    description
         "This feature means that a node support
      "An MPLS tunnel encapsulation capability."; flow";
  }

     feature mpls-over-udp-tunnel

  identity l2 {
    base "flow-type";
    description
         "This feature means that a node supports
      "An MPLS over UDP tunnel encapsulation
          capability."; flow";

  }

     feature detnet-mpls-dp-sol

  identity tsn {
    base "flow-type";
    description
         "This feature means that
      "An MPLS data plane
          solution is supported."; flow";
  }

  identity detnet-node-role service-operation {
    description
         "base detnet-node-role";
     }
      "Base 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 from which all service layer aware."; operation are derived";
  }

  identity edge-node service-initiation {
    base detnet-node-role; "service-operation";
    description
         "An instance of a DetNet relay node that
          includes either a DetNet service layer proxy
          function for
      "A 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)."; encapsulates";
  }

  identity relay-node service-termination {
    base detnet-node-role; "service-operation";
    description
      "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."; decapsulates";
  }

  identity transit-node service-relay {
    base detnet-node-role; "service-operation";
    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."; swap";
  }

  identity tunnel-decap-action forwarding-operation {
    description
      "Base identify identity from which all tunnel decap
          actions data plane operation are derived.
          Tunnel decap actions include:
          ipv4-decap - derived";
  }

  identity natively-forward {
    base "forwarding-operation";
    description
      "A packet natively forward to decap an IPv4 tunnel,
          ipv6-decap - lower-layer";
  }

  identity impose-and-forward {
    base "forwarding-operation";
    description
      "Impose a header(MPLS/IP) and forward to decap an IPv6 tunnel."; lower-layer";
  }
  identity ipv4-decap pop-and-forward {
    base "tunnel-decap-action"; "forwarding-operation";
    description
         "IPv4 tunnel decap.";
      "Pop an identified packet header and forward to lower-layer";
  }

  identity ipv6-decap pop-impose-and-forward {
    base "tunnel-decap-action"; "forwarding-operation";
    description
         "IPv4 tunnel decap.";
      "Pop an identified packet header, impose a one or more outgoing
       header and forward to lower-layer ";
  }

     typedef tunnel-decap-action-def

  identity swap-and-forward {
       type identityref
    base "forwarding-operation";
    description
      "Swap an identified packet header with outgoing header and forward
       to lower-layer ";
  }

  identity pop-and-lookup {
    base "tunnel-decap-action";
       } "forwarding-operation";
    description
         "Tunnel decap def.";
      "Pop an identified packet header and perform a lookup";
  }
  identity ttl-action label-space {
    description
      "Base identity from which all TTL
          actions label space are derived.";
     }

     identity no-action {
       base "ttl-action";
       description
         "Do nothing regarding the TTL."; derived";
  }

  identity copy-to-inner platform-label {
    base "ttl-action"; "label-space";
    description
         "Copy the TTL of the outer header
          to
      "label allocated from the inner header."; platform label space";
  }

  identity decrease-and-copy-to-inner non-platform-label {
    base "ttl-action"; "label-space";
    description
         "Decrease TTL by one and copy the TTL
          to
      "label allocated from the inner header."; non-platform label space";
  }

  typedef ttl-action-def ttl-action-definition {
    type identityref {
      base "ttl-action";
    }
    description
      "TTL action definition.";
     }

     identity hop-limit-action {
       description
         "Base identity from which all hop limit
          actions are derived."; definition";

  }

  typedef hop-limit-action-def config-type-ref {
    type identityref {
      base "hop-limit-action"; "config-type";
    }
    description
         "hop limit action definition.";
      "config-type-ref";
  }

     identity mpls-label-action

  typedef flow-type-ref {
       description
         "Base identity from which all MPLS label
          operations are derived.
          The MPLS label stack operations include:
          push - to add a new label to a label stack,
          pop - to pop the top label from a label stack,
          swap - to exchange the top label of a label
                 stack with new label.";
     }

     identity label-push
    type identityref {
      base "mpls-label-action"; "flow-type";
    }
    description
         "MPLS label stack operation: push.";
      "flow-type-ref";
  }

     identity label-pop

  typedef service-operation-ref{
    type identityref {
      base "mpls-label-action"; "service-operation";
  }
  description
         "MPLS label stack operation: pop.";
    "service-operation-ref";
  }

     identity label-swap

  typedef forwarding-operation-ref {
    type identityref {
      base "mpls-label-action"; "forwarding-operation";
    }
    description
         "MPLS label stack operation: swap.";
      "forwarding-operation-ref";
  }

  typedef mpls-label-action-def label-space-ref {
    type identityref {
      base "mpls-label-action"; "label-space";
    }
    description
         "MPLS label action definition.";
      "label-space-ref";
  }
     identity detnet-transport-layer

  typedef lower-layer-ref {
       description
         "The layer that optionally provides congestion
          protection for DetNet flows over paths provided
          by the underlying network.";
     }

     identity detnet-service-layer
    type leafref {
      path "/ietf-detnet:detnet-config/ietf-detnet:detnet-config-list"
      + "/ietf-detnet:name";
    }
    description
         "The layer at which service protection is
          provided, either packet sequencing, replication,
          and elimination or packet encoding";
     "lower-layer-ref";
  }

  typedef service-function-type service-protection-type {
    type enumeration {
      enum null none {
        description
             "No
          "no service function is enabled."; protection provide";
    }
    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
           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.";
      "service-protection-type";
  }

  typedef sequence-number-generation sequence-number-generation-type {
    type enumeration {
     enum "copy-from-app-flow" none {
       description
             "DetNet flow
          "No sequence number is copied
              from application flow."; generation function provide";
    }
    enum "generated-by-edge-node" copy-from-app-flow {
      description
             "DetNet flow
        "Copy the app-flow sequence number to the DetNet-flow";
    }
    enum generate-by-detnet-flow {
      description
        "Generate the sequence number is generated by DetNet edge node."; flow";
    }
  }
  description
         "DetNet sequence number generation types.";
    "sequence-number-generation-type";
  }

  grouping detnet-sequence-number {
       description
         "DetNet sequence number.";
       leaf sequence-number-generation-type l4-port-header {
         type sequence-number-generation;
    description
      "The way on how sequence number is generated.";
         } TCP/UDP port(source/destination) information";
    leaf sequence-number-length source-port {
      type uint8;
         description
           "DetNet sequence number length.";
       }
     }

     grouping detnet-transport-identifier {
       description
         "DetNet transport identifier";
     }

     grouping detnet-transport-qos {
       //Editor notes: this will be defined in a separate
       //              YANG model (detnet-transport-qos).
       //              More inputs and discussions are needed here. inet:port-number;
      description
         "DetNet transport tunnel QoS attributes.";
       uses traffic-specification;
        "The source port number";
    }
    leaf destination-port {
      type inet:port-number;
      description
        "The destination port number";
    }
  }

  grouping ipv4-header {
    description
      "The IPv4 packet header encapsulation information."; information";

    leaf src-ipv4-address {
      type inet:ipv4-address;
      mandatory true;
      description
        "The source IP address of the header."; header";
    }
    leaf dest-ipv4-address {
      type inet:ipv4-address;
      mandatory true;
      description
        "The destination IP address of the header."; header";
    }
    leaf protocol {
      type uint8;
      mandatory true;
      description
        "The protocol id of the header.";
       }
       leaf ttl {
         type uint8;
         description
           "The TTL of the header."; header";
    }
    leaf dscp {
      type uint8;
      description
        "The DSCP field of the header."; header";
    }
  }

  grouping ipv6-header {
    description
      "The IPv6 packet header encapsulation information."; information";
    leaf src-ipv6-address {
      type inet:ipv6-address;
      mandatory true;
      description
        "The source IP address of the header."; header";
    }
    leaf dest-ipv6-address {
      type inet:ipv6-address;
      mandatory true;
      description
        "The destination IP address of the header."; header";
    }
    leaf next-header {
      type uint8;
      mandatory true;
      description
        "The next header of the IPv6 header."; header";
    }
    leaf traffic-class {
      type uint8;
      description
        "The traffic class value of the header."; header";
    }
    leaf flow-label {
      type inet:ipv6-flow-label;
      description
        "The flow label value of the header.";
       }
       leaf hop-limit {
         type uint8 {
           range "1..255";
         }
         description
           "The hop limit of the header."; header";
    }
  }

  grouping mpls-header {
    description
      "The MPLS encapsulation packet 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."; information";
    leaf label {
      type uint32;
                 mandatory true; rt-type:mpls-label;
      description
        "The label to be pushed.";
               }
               leaf s-bit {
                 type boolean;
                 description
                   "The s-bit value of the label to be pushed."; MPLS header";
    }
    leaf tc-value tc {
      type uint8;
      description
        "The traffic class value of the label
                    to be pushed."; MPLS header";
    }
    leaf ttl-value s-bit {
      type uint8; boolean;
      description
        "The TTL s-bit 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."; header,
         which indicates the bottom of the label shack";
    }
    leaf ttl-action d-cw-encapsulate-flag {
      type ttl-action-def; boolean;
      description
                   "The label ttl actions:
                    - No-action,
        "the indication of whether D-CW  is encapsulated or
                    - Copy to inner label,or
                    - Decrease (the in label) by 1 and
                      copy to not,
         when the out label.";
               }
             }
           }
         } D-CW is encapsulated, the sequence number is
         determined by sequence generation type";
    }
  }

  grouping mpls-detnet-header l2-header {
    description
      "The MPLS DetNet encapsulation Ethernet or TSN packet header information."; information";
    leaf service-label source-mac-address {
      type uint32;
         mandatory true; yang:mac-address;
      description
        "The service label source MAC address value of the DetNet header."; ethernet header";
    }
    leaf control-word destination-mac-address {
      type uint32; yang:mac-address;
      description
        "The control word destination MAC address value of the DetNet header.";
       } ethernet header";
    }

     grouping udp-header {
       description
         "UDP header.";
    leaf source-port ethertype {
      type inet:port-number; eth:ethertype;
      description
        "The source port number."; ethernet packet type value of the ethernet header";
    }
    leaf destination-port vlan-id {
      type inet:port-number; uint16;
      description
        "The destination port number.";
       }

     }

     grouping transport-tunnel-encap {
       description
         "Defines Vlan value of the transport tunnel encapsulation
          header.";
       choice tunnel-type {
         description
           "Tunnel type includes: IPv4, IPv6, MPLS,
            MPLS over UDP tunnels.";

         case IPv4 {
           if-feature ipv4-tunnel;
           description
             "IPv4 tunnel.";
           container ipv4-encapsulation {
             description
               "IPv4 encapsulation.";
             uses ipv4-header;
           }
         }
         case IPv6 {
           if-feature ipv6-tunnel;
           description
             "IPv6 tunnel.";
           container ipv6-encapsulation {
             description
               "IPv6 encapsulation.";
             uses ipv6-header;
           } ethernet header";
    }
         case MPLS {
           if-feature mpls-tunnel;
           description
             "MPLS tunnel.";
           container mpls-encapsulation
    leaf pcp {
      type uint8;
      description
               "MPLS encapsulation.";
             uses mpls-header;
        "The priority value of the ethernet header";
    }
  }
         case MPLS-over-UDP

  grouping l4-port-identification {
           if-feature mpls-over-udp-tunnel;
    description
             "MPLS over UDP tunnel.";
           container mpls-over-udp-encaplustion
      "The TCP/UDP port(source/destination) identification information";
    leaf lower-source-port {
      type inet:port-number;
      description
               "MPLS over udp encapsulation.";

             uses mpls-header;
             uses udp-header;
             choice address-family
        "The lower source port number of the source port range";
    }
    leaf upper-source-port {
      type inet:port-number;
      description
                 "According to IP address family(IPv4 and IPv6)
                  to apply corresponding IP header.";
               case IPv4
        "The upper source port number of the source port range";
    }
    leaf lower-destination-port {
      type inet:port-number;
      description
                   "IPv4 address family.";
                 uses ipv4-header;
        "The lower destination port number or the destination port range";
    }
               case IPv6
    leaf upper-destination-port {
      type inet:port-number;
      description
                   "IPv6 address family.";
                 uses ipv6-header;
               }
             }
           }
         }
        "The upper destination port number of the destination port range";
    }
  }

  grouping transport-tunnel-decap ipv4-flow-identification {
    description
         "Tunnel decapsulation inforamtion.";
       choice tunnel-type
      "The IPv4 packet header identification information";

    leaf src-ipv4-prefix {
         description
           "Nexthop tunnel
      type options.";
         case ipv4 {
           if-feature ipv4-tunnel;
           container ipv4-decap inet:ipv4-prefix;
      mandatory true;
      description
        "The source IP address of the header";
    }
    leaf dest-ipv4-prefix {
      type inet:ipv4-prefix;
      mandatory true;
      description
               "IPv4 decap.";
        "The destination IP address of the header";
    }
    leaf ipv4-decap protocol {
      type tunnel-decap-action-def; uint8;
      mandatory true;
      description
                 "IPv4 decap operations.";
        "The protocol of the header";
    }
    leaf ttl-action dscp {
      type ttl-action-def; uint8;
      description
        "The ttl actions:
                  no-action or copy to inner header."; DSCP field of the header";
    }
    leaf dscp-bitmask {
      type uint8;
      description
        "The bitmask value that determines whether to use
         the DSCP(IPv4) value for flow identification or not";
     }
  }
         case ipv6 {
           if-feature ipv6-tunnel;
           container ipv6-decap

  grouping ipv6-flow-identification {
    description
               "IPv6 decap.";
      "The IPv6 packet header identification information";
    leaf ipv6-decap src-ipv6-prefix {
      type tunnel-decap-action-def; inet:ipv6-prefix;
      mandatory true;
      description
                 "IPv6 decap operations.";
        "The source IP address of the header";
    }
    leaf hop-limit-action dest-ipv6-prefix {
      type hop-limit-action-def; inet:ipv6-prefix;
      mandatory true;
      description
        "The hop limit actions:
                  no-action or copy to inner header.";
             }
           } destination IP address of the header";
    }
         case mpls {
           if-feature mpls-tunnel;
           container label-pop {
             description
               "MPLS decap.";
    leaf label-pop next-header {
      type mpls-label-action-def; uint8;
      mandatory true;
      description
                 "Pop a label from
        "The next header of the label stack."; IPv6 header";
    }
    leaf ttl-action traffic-class {
      type ttl-action-def; uint8;
      description
        "The label ttl actions:
                  no-action or copy to inner label/header.";
             }
           }
         } traffic class value of the header";
    }
    leaf traffic-class-bitmask {
      type uint8;
      description
        "The bitmask value that determines whether to use
         the Traffic class(IPv6) value for flow identification or not";
    }

     grouping detnet-transport-instance
    leaf flow-label {
      type inet:ipv6-flow-label;
      description
         "An instance
        "The flow label value of the DetNet transport layer, which
          depends on the specific data plane header";
    }
    leaf flow-label-flag {
      type boolean;
      description
        "The flag that is used
          as determines whether to use
         the underlay tunnel.";
       uses transport-tunnel-encap;
       uses detnet-transport-qos; Flow Label value for flow identification or not";
    }
  }

  grouping ipv6-flow-identification mpls-flow-identification {
    description
         "IPv6 flow identification.";
      "The MPLS packet header identification information";
    leaf src-ipv6-address label {
      type inet:ipv6-address; rt-type:mpls-label;
      description
        "The source IP address label value of the header."; MPLS header";
    }
    leaf dest-ipv6-address tc {
      type inet:ipv6-address; uint8;
      description
        "The destination IP address traffic class value of the header."; MPLS header";
    }
  }

  grouping l2-flow-identification {
    description
      "The Ethernet or TSN packet header identification information";
    leaf traffic-class source-mac-address {
      type uint8; yang:mac-address;
      description
        "The traffic class source MAC address value of the header."; ethernet header";
    }
    leaf flow-label destination-mac-address {
      type inet:ipv6-flow-label; yang:mac-address;
      description
        "The flow label destination MAC address value of the header."; ethernet header";
    }
    leaf source-port ethertype {
      type inet:port-number; eth:ethertype;
      description
        "The source port number."; ethernet packet type value of the ethernet header";
    }
    leaf destination-port vlan-id {
      type inet:port-number; uint16;
      description
        "The destination port number."; Vlan value of the ethernet header";
    }
    leaf protocol pcp {
      type uint8;
      description
        "The protocol id priority value of the header."; ethernet header";
    }
  }

  grouping ipv4-flow-identification traffic-specification {
    description
         "IPv4 flow identification.";
      "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 src-ipv4-address interval {
      type inet:ipv4-address; uint32;
        description
          "The source IP address period of time in which the header of
            a DetNet flow."; traffic
           specification cannot be exceeded";
    }
    leaf dest-ipv4-address { max-packets-per-interval{
      type inet:ipv4-address; uint32;
      description
        "The destination IP address maximum number of packets that the header
            of a DetNet flow.";
         source will transmit in one Interval.";
    }
    leaf dscp max-payload-size{
      type uint32;
      description
        "The maximum payload size that the source
         will transmit.";
    }
    leaf average-packets-per-interval {
      type uint8; uint32;
      description
        "The DSCP field average number of packets that the header of a DetNet flow..";
         source will transmit in one Interval";
    }
    leaf source-port average-payload-size {
      type inet:port-number; uint32;
      description
        "The average payload size that the
         source port number."; will transmit.";
    }
  }

  container detnet-config {
    description
      "DetNet configurations";
    leaf destination-port node-id {
      type inet:port-number; yang:dotted-quad;
      description
           "The destination port number.";
        "A 32-bit number in the form of a dotted quad that is used by
         identifying a DetNet node";
    }
    list detnet-config-list {
      key "name";
      description
        "list of the DetNet configurations";
      leaf protocol name {
        type uint8; string;
        description
          "The protocol id of name to identify the header of a DetNet flow..";
       } configuration";
      }

     grouping ip-flow-identification
      leaf config-type {
        type config-type-ref;
        description
           "IP flow identification.";
       choice ip-flow-type
          "The DetNet configuration type such as a App-flow, service
           sub-layer, forwarding sub-layer, and TSN sub-network";
      }
      container App-flow {
        when "../config-type = 'ietf-detnet:App-flow'";
        description
           "IP flow types: IPv4, IPv6.";
         case ipv4
          "The DetNet App-flow configuration";
        container operations {
          description
             "IPv4 flow identification.";
           leaf src-ipv4-address "operations";
          container sequence-number {
             type inet:ipv4-address;
            description "The source IP address of the header.";
           } DetNet sequence number operations grouping";
            leaf dest-ipv4-address sequence-number-generation-type {
              type inet:ipv4-address; sequence-number-generation-type;
              description "The destination IP address of the header."; DetNet sequence number generation type";
            }
            leaf dscp sequence-number-length {
              type uint8;
              description
                "The DSCP field of the header."; DetNet sequence number length";
            }
          }
         case ipv6
        }
        container in-segments {
          description
             "IPv6 flow identification."; "The App-flow identification information";
          leaf src-ipv6-address app-flow-type {
            type inet:ipv6-address; flow-type-ref;
            description
              "The source IP address of the header."; App-flow type such as a L2, IPv4, and IPv6";
          }
           leaf dest-ipv6-address
          uses l2-flow-identification {
             type inet:ipv6-address;
             description
               "The destination IP address of the header.";
            when "app-flow-type = 'ietf-detnet:tsn' or 'ietf-detnet:l2'";
          }
           leaf traffic-class
          uses ipv4-flow-identification {
            when "app-flow-type = 'ietf-detnet:ipv4'";
          }
          uses ipv6-flow-identification {
            when "app-flow-type = 'ietf-detnet:ipv6'";
          }
          uses l4-port-identification {
when "app-flow-type = 'ietf-detnet:ipv6' or 'ietf-detnet:ipv4'";
            or 'ietf-detnet:ipv4'";
          }
        }
        container out-segments {
             type uint8;
          description
            "The traffic class value of the header.";
           } DetNet service information associated with this App-flow";
          leaf flow-label detnet-service-sub-layer {
            type inet:ipv6-flow-label;  lower-layer-ref;
            description
               "The flow label of the header."; "Specify associated service sub-layer";
          }
        }
      }
       leaf source-port
      container service-sub-layer {
         type inet:port-number;
        when "../config-type = 'ietf-detnet:service-sub-layer'";
        description "The source port number.";
       } DetNet service sub-layer configuration";
        container operations {
          description
            "The DetNet service sub-layer operations grouping";
          container service-operation {
            description "The DetNet service operations grouping";
            leaf destination-port service-operation-type {
              type inet:port-number; service-operation-ref;
              description
              "The destination port number."; DetNet service operations type such as DetNet
               service initiation, termination, and relay";
            }
          }
          container service-protection {
            description
              "The DetNet service protection operations grouping";
            leaf protocol service-protection-type {
              type uint8; service-protection-type;
              description
                "The protocol id of the header."; DetNet service protection type such as PRF, PEF, PEOF,
                 PERF, and PEORF";
            }
          }

     grouping l3-flow-identification
        }
        container in-segments {
          when "../operations/service-operation"
          + "/service-operation-type != 'service-initation'";
          description
         "Layer 3 flow
            "DetNet service identification in a DetNet
          domain.";
       choice flow-type information";
          leaf detnet-service-type {
            type flow-type-ref;
          description
           "L3
            "incoming DetNet service flow types: IP and MPLS.";
         case IP type";
          }
          list detnet-service-list {
            key "detnet-service-index";
            description
             "IP (IPv4
              "Incoming DetNet member flows or IPv6) flow identification."; a compound flow";
            leaf detnet-service-index {
              type uint8;
              description
                "Incoming DetNet service index";
            }
            uses ipv4-flow-identification {
      when "../detnet-service-type = 'ietf-detnet:ipv4'";
            }
            uses ip-flow-identification; ipv6-flow-identification {
      when "../detnet-service-type = 'ietf-detnet:ipv6'";
            }
         case MPLS
            container mpls-flow-identification {
              when "../../detnet-service-type = 'ietf-detnet:mpls'";
              description
                "MPLS flow identification."; type DetNet service identification";
      leaf service-label label-space {
        type uint32;
             mandatory true; label-space-ref;
                description
               "The service
                  "Indicate the incoming MPLS label of a DetNet flow.";
           }
         }
       } is associated with
                   platform label space or not";
              } //l3-flow-identification

     grouping in-segments
              container non-platform-label-space {
when "../label-space = 'ietf-detnet:non-platform-label'";
                description
         "From a receiving node point of view, In-segments
          are a set of instances
                  "MPLS label is associated with non-platform label space,
                   all of a DetNet flow at the
          receiving node. This occurs when Packet Replication
          Function (PRF) is enabled at an upstream node or
          multiple flows map/aggregate to a single DetNet
          flow."; F-labels and incoming interface information was
                   used for identification";
                leaf incoming-interface {
                  type if:interface-ref;
                  description
                    "DetNet service incoming interface information";
                }
                list in-segment non-platform-label-stack {
                  key "in-segment-id"; "index";
                  description
           "A list
                    "All of in segments, there will be
            multiple in-segments for a DetNet flow
            when PRF and PEF enabled."; the label information from the outer label
                     to the current label";
                  leaf in-segment-id index {
                    type uint32; uint8;
                    description
             "in-segment identifier.";
                      "Index of the labels stack";
                  }
                  uses l3-flow-identification;

         leaf service-function mpls-flow-identification;
                }
              }
              container platform-label-space {
           type service-function-type;
        when "../label-space = 'ietf-detnet:platform-label'";
                description
             "DetNet service function indication.";
                  "MPLS label is associated with platform label space, only
                   the F-label is used for identification";
                uses mpls-flow-identification;
              }
            }
          }

     grouping
        }
        container 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 "../operations/service-operation"
          + "/service-operation-type != 'service-termination'";
          description
            "DetNet Service outgoing processing grouping";

          leaf detnet-service-processing-type {
            type flow-type-ref;
          description
            "Outgoing DetNet service flow is replicated
          to multiple out-segments."; type";
          }
          container detnet-service-encapsulation {
            description
              "DetNet service encapsulation information";
            list out-segment detnet-service-processing-list {
              key "out-segment-id"; "detnet-service-processing-index";
              description
           "A
                "The list of segments, there will be single or multiple
            out-segments when perform PRF."; outgoing DetNet service(s)";
              leaf out-segment-id detnet-service-processing-index {
                type uint32;
                description
             "The out-segment identifier"; "Outgoing segment entry";
              }
              container detnet-service-encapsulation ip-flow {
                when "../../../detnet-service-processing-type ="
                + "'ietf-detnet:ipv4' or 'ietf-detnet:ipv6'";
                description
             "Only MPLS based DetNet defines
                  "IP type DetNet
              service layer. The service flow(s) encapsulation
              includes service label and control word."; information";
                container ipv4-flow {
                  when "../../../../detnet-service-processing-type ="
                  + "'ietf-detnet:ipv4'";
                  description
                    "IPv4 packet header encapsulation information";
                  uses mpls-detnet-header; ipv4-header;
                }
                container detnet-transport-encapsulation ipv6-flow {
                  when "../../../../detnet-service-processing-type ="
                  + "'ietf-detnet:ipv6'";
                    description
             "Each out-segment corresponds to a
              transport instance.";
                      "IPv6 packet header encapsulation information";
                    uses detnet-transport-instance;
         }
       } ipv6-header;
                }

     grouping detnet-service-instance
                container l4-port-header {
                  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
                    "TCP/UDP source or destination port number";
                  uses l4-port-header;
                }
              }
              container mpls-flow {
                when "../../../detnet-service-processing-type ="
                + "'ietf-detnet:mpls'";
                description
                  "MPLS type string; DetNet flow(s) encapsulation information";
                  list detnet-mpls-label-stack {
                    key "index";
                    description
                      "The name list of the service instance. This MUST
            be unique across all service instances in
            a given network device.";
       } MPLS labels stack for swap or encapsulation";
                    leaf service-rank index {
                      type boolean; uint8;
                      description
           "Service rank is used by the network to decide
            which services can and cannot exist when network
            resources reach their limit.  Rank is used to help
            to determine which services can be dropped (i.e.,
            removed from node configuration) if a port "Index of a
            node becomes oversubscribed (e.g., due to network
            reconfiguration).  The true value is more important
            than the false value (i.e., services with false
            are dropped first).";
         reference
           "draft-ietf-detnet-flow-information-model"; labels stack";
                    }
                    uses in-segments;
       uses out-segments; mpls-header;
                  }

     grouping l2-flow-identification-at-uni
              }
              container detnet-forwarding-sub-layer-info {
                description
         "Layer 2 flow identification at UNI.";
                  "The forwarding sub-layer information that associated with
                   this DetNet service sub-layer";
                leaf source-mac-address detnet-forwarding-sub-layer {
                  type yang:mac-address; lower-layer-ref;
                  description
           "The source MAC address used for
            flow identification.";
                    "Specify associated forwarding sub-layer";
                }
       leaf destination-mac-address
              }
            }
          }
        }
      }
      container forwarding-sub-layer {
         type yang:mac-address;
        when "../config-type = 'ietf-detnet:forwarding-sub-layer'";
        description
                  "The destination MAC address used for
            flow identification.";
       }

   /*    leaf ethertype DetNet forwarding sub-layer configuration";
        container operations {
         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";
       }
   */ DetNet forwarding sub-layer operations grouping";
          container forwarding-operation {
            description
              "DetNet forwarding function operations grouping";
            leaf vlan-id forwarding-operation-type {
              type uint16 {
           range "1..4094"; forwarding-operation-ref;
              description
                "DetNet forwarding operation type such as
                 natively forward, impose and forward, pop and forward,
                 pop and impose and forward, swap and forward,
                 and pop and lookup";
            }
          }
          container resource-allocate {
            description
           "Vlan Identifier used for L2 flow identification.";
              "resource-allocation function operations grouping";
            uses traffic-specification;
          }
          container pcp qos {
         //Todo
            description
           "PCP used for L2 flow identification.";
              "QoS function operations grouping";
          }
        }

     grouping l3-flow-identification-at-uni
        container in-segments {
          description
         "Layer 3 flow
            "DetNet forwarding sub-layer packet identification at UNI."; information";
          leaf detnet-forwarding-type {
            type flow-type-ref;
            description
              "incoming DetNet forwarding packet type";
          }
          uses ip-flow-identification; ipv4-flow-identification {
    when "detnet-forwardinge-type = 'ietf-detnet:ipv4'";
          }

     grouping traffic-specification
          uses ipv6-flow-identification {
    when "detnet-forwarding-type = 'ietf-detnet:ipv6'";
          }
          container mpls-flow-identification {
            when "../detnet-forwarding-type = 'ietf-detnet:mpls'";
            description
         "traffic-specification specifies how the Source
          transmits packets for
              "MPLS type identification information";
    leaf label-space {
      type label-space-ref;
              description
                "Indicate the flow.  This incoming MPLS label 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 associated with platform
                 label space or not";
            }
            container non-platform-label-space {
         type uint32;
when "../label-space = 'ietf-detnet:non-platform-label'";
              description
           "The period
                "MPLS label is associated with non-platform label space,
                 all of time in which the traffic
            specification cannot be exceeded";
       } F-labels and incoming interface information was
                 used for identification";
              leaf max-packets-per-interval incoming-interface {
                type uint32; if:interface-ref;
                description
                  "The maximum number information of packets that the
            source will transmit in one Interval."; DetNet forwarding packet incoming
                   interface";
              }
       leaf max-payload-size
              list non-platform-label-stack {
         type uint32;
                key "index";
                description
            "The maximum payload size that
                  "All of the source
             will transmit.";
       } label information from the outer label to
                   the current label";
                leaf average-packets-per-interval index {
                  type uint32; uint8;
                  description
             "The average
                    "index number of packets that the
              source will transmit in one Interval"; 0 indicate last inner label";
                }
       leaf average-payload-size
                uses mpls-flow-identification;
              }
            }
            container platform-label-space {
           type uint32;
             when "../label-space = 'ietf-detnet:platform-label'";
              description
            "The average payload size that
                "MPLS label is associated with platform label space, only
                 the
             source will transmit."; F-label is used for identification";
              uses mpls-flow-identification;
            }
          }

     grouping client-flows-at-uni
        }
        container out-segments {
          description
         "The attributes of the client flow at UNI. When
          flow aggregation is enabled at ingress, multiple
          client flows map to a
            "DetNet forwarding sub-layer packet processing information";
          leaf detnet-forwarding-processing-type {
            type flow-type-ref;
            description
              "outgoing DetNet service instance.";
       list client-flow forwarding packet type";
          }
          container natively-detnet-forwarding {
         key "flow-id";
            when "../../operations/forwarding-operation"
            + " /forwarding-operation-type = 'natively-forwarding'";
            description
            "Packet forwarding processing information";
            container ipv4-flow {
              when "../../detnet-forwarding-processing-type ="
              + "'ietf-detnet:ipv4'";
              description
           "A list of client flows.";
                "IPv4 type packet forwarding information";
              leaf flow-id ipv4-next-hop-address {
                type uint32; inet:ipv4-address;
                description
             "Flow identifier that is unique in a network
              device for client flow identification";
                  "IPv4 type Next hop IP address";
              }
            }
            container ipv6-flow {
              when "../../detnet-forwarding-processing-type ="
              + "'ietf-detnet:ipv6'";
              description
                "IPv6 type packet forwarding information";
              leaf flow-rank ipv6-next-hop-address {
                type boolean; inet:ipv6-address;
                description
             "Flow rank is used by the network
              to decide which flows can and cannot exist
              when network resources reach their limit.
              Rank is used to help to determine which flows
              can be dropped (i.e., removed from node
              configuration) if a port of a node becomes
              oversubscribed (e.g., due to network
              reconfiguration).  The true value is more
              important than the false value (i.e., flows
              with false are dropped first).";
           reference
             "draft-ietf-detnet-flow-information-model";
                  "IPv6 type Next hop IP address";
              }
         choice flow-type

            }
          }
          container detnet-forwarding-encapsulation {
            when "../../operations/forwarding-operation"
            + "/forwarding-operation-type != 'natively-forward'";
            description
             "Client flow type: layer 2 flow, layer 3
              flow.";
           case l2-flow
              "Packet encapsulation information";
            container ip-flow {
              when "../../detnet-forwarding-processing-type = "
              + "'ietf-detnet:ipv4' or 'ietf-detnet:ipv6'";
              description
               "Ethernet flow identification.";
                "The IP type DetNet flow(s) encapsulation information";
              container ipv4-flow {
                when "../../../detnet-forwarding-processing-type = "
                + "'ietf-detnet:ipv4'";
                description
                  "IPv4 packet header encapsulation information";
                uses ipv4-header;
              }
              container ipv6-flow {
                when "../../../detnet-forwarding-processing-type = "
                + "'ietf-detnet:ipv6'";
                description
                  "IPv6 packet header encapsulation information";
                uses l2-flow-identification-at-uni; ipv6-header;
              }
           case l3-flow
              container l4-port-header {
                description
               "Layer 3 flow identification, including
                IPv4,IPv6 and MPLS.";
                   "TCP/UDP source or destination port number";
                uses l3-flow-identification-at-uni; l4-port-header;
              }
            }
            container traffic-specification mpls-flow {
              when "../../detnet-forwarding-processing-type = "
              + "'ietf-detnet:mpls'";
              description
             "The traffic specification of the client flow.";
           uses traffic-specification;
         }
       }
     }

     grouping detnet-service-decap
                "MPLS label encapsulation information";
              list detnet-mpls-label-stack {
                key "index";
                  description
         "DetNet service decapsulation inforamtion.";
                    "The list of MPLS labels stack for swap or encapsulation";
                leaf service-label-pop index {
                  type mpls-label-action-def;
         mandatory true; uint8;
                  description
           "Pop
                   "Index of the DetNet service label."; labels stack";
                }
       leaf ttl-action {
         type ttl-action-def;
         description
           "The label ttl actions:
            no-action or copy to inner label/header.";
                uses mpls-header;
              }

            }

     grouping detnet-service-proxy-instance
            container lower-layer-info {
              description
         "Mapping between App-flows and DetNet flows.";

       choice edge-node-type
                "The lower-layer information associated with
                 this forwarding sub-layer";
              leaf lower-layer-type {
                type flow-type-ref;
                description
           "There are two types of edge node: ingress node and
            egress node";
         case ingress-node
                  "indicate lower-layer type";
              }
              container interface {
           uses client-flows-at-uni;
                when "../lower-layer-type = 'ietf-detnet:l2'";
                description
                  "indicate the lower-layer is the outgoing interface";
                leaf service-function outgoing-interface {
                  type service-function-type; if:interface-ref;
                  description
               "DetNet service function indication.";
           }
           uses detnet-sequence-number;
           uses out-segments;
         }
         case egress-node {
           uses in-segments;
           uses transport-tunnel-decap;
           uses detnet-service-decap;
         }
                   "Outgoing interface";
                }
              }
              container detnet-flow sub-layer {
                when "../lower-layer-type != 'ietf-detnet:l2'";
                description
         "DetNet flow configuration and status reporting.";
       choice detnet-node-role{
         description
           "Depends on
                  "indicate the role lower-layer is some of a node to configure
            corresponding flow parameters.";
         case transit-node {
           description
             "DetNet flow configuration parameters for
              transit nodes.";
           container transit-node the DetNet sub-layer
                   or TSN sub-network";
                leaf sub-layer {
                  type lower-layer-ref;
                  description
               "Transit node container.";
             uses detnet-transport-qos;
                   "Specify associated DetNet sub-layer or TSN sub-network";
                }
              }
         case relay-node {
           if-feature detnet-mpls-dp-sol;
           description
             "DetNet flow configuration parameters for
              relay nodes.";
           container relay-node {
             description
               "Relay node container.";
             uses detnet-service-instance;
            }
          }
         case edge-node {
           if-feature detnet-mpls-dp-sol;
           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 sub-network {
        when "../config-type = 'ietf-detnet:tsn-sub-network'";
       description
               "End station container.";
             uses detnet-service-proxy-instance;
           }
         "sub-network";
      }
    }
  }
}

<CODE ENDS>
6.  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.

7.  IANA Considerations

   This document makes no request of IANA.

   Note to RFC Editor: this section may be removed on publication as an
   RFC.

8.  Security Considerations

   <TBD>

9.  Acknowledgements

10.  References

10.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-03
              detnet-bounded-latency-04 (work in progress), March June 2019.

   [I-D.ietf-detnet-architecture]
              Finn, N., Thubert, P., Varga, B., and J. Farkas,
              "Deterministic Networking Architecture", draft-ietf-
              detnet-architecture-12
              detnet-architecture-13 (work in progress), March May 2019.

   [I-D.ietf-detnet-dp-sol-ip]
              Korhonen, J. and B.

   [I-D.ietf-detnet-flow-information-model]
              Farkas, J., Varga, B., Cummings, R., and Y. Jiang, "DetNet IP Data Plane
              Encapsulation", draft-ietf-detnet-dp-sol-ip-02
              Flow Information Model", draft-ietf-detnet-flow-
              information-model-03 (work in progress), March 2019.

   [I-D.ietf-detnet-dp-sol-mpls]
              Korhonen, J. and B.

   [I-D.ietf-detnet-ip]
              Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
              Bryant, S., and J. Korhonen, "DetNet MPLS Data Plane
              Encapsulation", draft-ietf-detnet-dp-sol-mpls-02 Plane: IP",
              draft-ietf-detnet-ip-01 (work in progress), March July 2019.

   [I-D.ietf-detnet-flow-information-model]
              Farkas, J.,

   [I-D.ietf-detnet-mpls]
              Varga, B., Cummings, R., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
              Bryant, S., and Y. Jiang, J. Korhonen, "DetNet
              Flow Information Data Plane: MPLS",
              draft-ietf-detnet-mpls-00 (work in progress), May 2019.

   [I-D.ietf-detnet-topology-yang]
              Geng, X., Chen, M., Li, Z., and R. Rahman, "Deterministic
              Networking (DetNet) Topology YANG Model", draft-ietf-detnet-flow-
              information-model-03 draft-ietf-
              detnet-topology-yang-00 (work in progress), March January 2019.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC6991]  Schoenwaelder, J., Ed., "Common YANG Data Types",
              RFC 6991, DOI 10.17487/RFC6991, July 2013,
              <https://www.rfc-editor.org/info/rfc6991>.

   [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
              RFC 7950, DOI 10.17487/RFC7950, August 2016,
              <https://www.rfc-editor.org/info/rfc7950>.

10.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., and I. Bryskin,
              "A YANG Data Model for Traffic Engineering Tunnels and
              Interfaces", draft-ietf-teas-yang-te-19 draft-ietf-teas-yang-te-21 (work in
              progress), February April 2019.

   [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-19 draft-ietf-teas-yang-te-topo-22 (work in
              progress), February June 2019.

   [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, "IEEE, "Frame Replication and Elimination for
              Reliability (IEEE Draft P802.1CB)", 2017,
              <http://www.ieee802.org/1/files/private/cb-drafts/>.",
              2016.

   [IEEE802.1Q-2014]
              "IEEE, "IEEE Std 802.1Q Bridges and Bridged Networks",
              2014, <http://ieeexplore.ieee.org/document/6991462/>.",
              2014.

   [IEEE802.1Qbu]
              IEEE, "IEEE, "IEEE Std 802.1Qbu Bridges and Bridged
              Networks - Amendment 26: Frame Preemption", 2016,
              <http://ieeexplore.ieee.org/document/7553415/>.", 2016.

   [IEEE802.1Qbv]
              "IEEE, "IEEE Std 802.1Qbu Bridges and Bridged Networks -
              Amendment 25: Enhancements for Scheduled Traffic", 2015,
              <http://ieeexplore.ieee.org/document/7572858/>.", 2016.

   [IEEE802.1Qcc]
              IEEE, "IEEE, "Stream Reservation Protocol (SRP)
              Enhancements and Performance Improvements (IEEE Draft
              P802.1Qcc)", 2017,
              <http://www.ieee802.org/1/files/private/cc-drafts/>.".

   [IEEE802.1Qch]
              IEEE, "IEEE, "Cyclic Queuing and Forwarding (IEEE Draft
              P802.1Qch)", 2017,
              <http://www.ieee802.org/1/files/private/ch-drafts/>.",
              2016.

   [IEEE802.1Qci]
              IEEE, "IEEE, "Per-Stream Filtering and Policing (IEEE
              Draft P802.1Qci)", 2016,
              <http://www.ieee802.org/1/files/private/ci-drafts/>.",
              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,
              <https://www.rfc-editor.org/info/rfc3209>.

   [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,
              <https://www.rfc-editor.org/info/rfc4875>.

   [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,
              <https://www.rfc-editor.org/info/rfc8342>.

Authors' Addresses

   Xuesong Geng
   Huawei Technologies

   Email: gengxuesong@huawei.com

   Mach(Guoyi) Chen
   Huawei Technologies

   Email: mach.chen@huawei.com

   Yeoncheol Ryoo
   ETRI

   Email: dbduscjf@etri.re.kr

   Zhenqiang Li
   China Mobile

   Email: lizhenqiang@chinamobile.com
   Reshad Rahman
   Cisco Systems

   Email: rrahman@cisco.com