draft-ietf-detnet-yang-03.txt   draft-ietf-detnet-yang-04.txt 
Network Working Group X. Geng Network Working Group X. Geng
Internet-Draft M. Chen Internet-Draft M. Chen
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: January 9, 2020 Y. Ryoo Expires: May 7, 2020 Y. Ryoo
ETRI ETRI
Z. Li Z. Li
China Mobile China Mobile
R. Rahman R. Rahman
Cisco Systems Cisco Systems
July 08, 2019 November 04, 2019
Deterministic Networking (DetNet) Configuration YANG Model Deterministic Networking (DetNet) Configuration YANG Model
draft-ietf-detnet-yang-03 draft-ietf-detnet-yang-04
Abstract Abstract
This document contains the specification for Deterministic Networking This document contains the specification for Deterministic Networking
flow configuration YANG Model. The model allows for provisioning of flow configuration YANG Model. The model allows for provisioning of
end-to-end DetNet service along the path without dependency on any end-to-end DetNet service along the path without dependency on any
signaling protocol. signaling protocol.
The YANG module defined in this document conforms to the Network The YANG module defined in this document conforms to the Network
Management Datastore Architecture (NMDA). Management Datastore Architecture (NMDA).
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 9, 2020. This Internet-Draft will expire on May 7, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 4
3. DetNet Configuration Model . . . . . . . . . . . . . . . . . 3 3. DetNet Service Module . . . . . . . . . . . . . . . . . . . . 4
3.1. DetNet Appliction Flow Configuration Attributes . . . . . 3 3.1. Service Quality . . . . . . . . . . . . . . . . . . . . . 4
3.2. DetNet Service Sub-layer Configuration Attributes . . . . 4 3.2. Service Endpoints . . . . . . . . . . . . . . . . . . . . 4
3.3. DetNet Forwarding Sub-layer Configuration Attributes . . 4 3.3. Service Encapsulation . . . . . . . . . . . . . . . . . . 5
3.4. DetNet Sub-network Configurations Attributes . . . . . . 5 4. DetNet Configuration Module . . . . . . . . . . . . . . . . . 5
4. Overview of DetNet YANG Structure . . . . . . . . . . . . . . 5 4.1. DetNet Appliction Flow Configuration Attributes . . . . . 5
4.1. DetNet YANG Structure Considerations . . . . . . . . . . 5 4.2. DetNet Service Sub-layer Configuration Attributes . . . . 5
4.2. DetNet YANG Structure . . . . . . . . . . . . . . . . . . 6 4.3. DetNet Forwarding Sub-layer Configuration Attributes . . 6
4.2.1. YANG Structure of Application Flow . . . . . . . . . 6 4.4. DetNet Sub-network Configurations Attributes . . . . . . 6
4.2.2. YANG Structure of DetNet Service Sub-layer . . . . . 6 5. Overview of DetNet YANG . . . . . . . . . . . . . . . . . . . 7
4.2.3. YANG Structure of DetNet Forwarding Sub-layer . . . . 8 5.1. DetNet YANG Considerations . . . . . . . . . . . . . . . 7
4.2.4. YANG Structure of DetNet sub-network . . . . . . . . 9 5.1.1. DetNet Service YANG Considerations . . . . . . . . . 7
5. DetNet Configuration YANG Model . . . . . . . . . . . . . . . 10 5.1.2. DetNet Configuration YANG Considerations . . . . . . 7
6. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.2. DetNet YANG Structures . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 5.2.1. DetNet Service YANG Structure . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 34 5.2.2. DetNet Configuration YANG Structure . . . . . . . . . 8
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 6. DetNet Service YANG Model . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 7. DetNet Configuration YANG Model . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . 34 8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 35
10.2. Informative References . . . . . . . . . . . . . . . . . 35 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 10. Security Considerations . . . . . . . . . . . . . . . . . . . 36
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
12.1. Normative References . . . . . . . . . . . . . . . . . . 36
12.2. Informative References . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39
1. Introduction 1. Introduction
Deterministic Networking (DetNet) [I-D.ietf-detnet-architecture] is DetNet (Deterministic Networking) provides a capability to carry
defined to provide high-quality network service with extremely low specified unicast or multicast data flows for real-time applications
packet loss rate, bounded low latency and jitter. with extremely low packet loss rates and assured maximum end-to-end
delivery latency. A description of the general background and
concepts of DetNet can be found in [I-D.ietf-detnet-architecture].
Information models for DetNet are categorized as flow models, service This document defines a YANG model for DetNet based on YANG data
models and configuration models, which is defined in types and modeling language defined in [RFC6991] and [RFC7950], which
[I-D.ietf-detnet-flow-information-model]. includes DetNet service module and DetNet configuration module, and
YANG model for topology discovery is defined in
[I-D.ietf-detnet-topology-yang]. DetNet service module is designed
for describe characteristics of services being provided for
application flows over a network, while the DetNet configuration
module is designed for DetNet flow path establishment, flow status
reporting, and DetNet functions configuration in order to achieve
end-to-end bounded latency and zero congestion loss.
Configuration models are used for DetNet topology discovery and DetNet Relay Transit Relay DetNet
DetNet flow configuration . This document defines a YANG model for End System Node Node Node End System
DetNet flow configurations based on YANG data types and modeling (T-PE) (S-PE) (LSR) (S-PE) (T-PE)
language defined in [RFC6991] and [RFC7950]. A YANG model for +----------+ +----------+
topology discovery is defined in [I-D.ietf-detnet-topology-yang]. | Appl. |<------------ End to End Service ----------->| Appl. |
The DetNet configuration YANG model is designed for DetNet flow path +----------+ +---------+ +---------+ +----------+
establishment, flow status reporting, and DetNet functions | Service |<--| Service |-- DetNet flow --| Service |-->| Service |
configuration in order to achieve end-to-end bounded latency and zero +----------+ +---------+ +----------+ +---------+ +----------+
congestion loss. |Forwarding| |Fwd| |Fwd| |Forwarding| |Fwd| |Fwd| |Forwarding|
+-------.--+ +-.-+ +-.-+ +----.---.-+ +-.-+ +-.-+ +---.------+
: Link : / ,-----. \ : Link : / ,-----. \
+........+ +-[ Sub ]-+ +......+ +-[ Sub ]-+
[Network] [Network]
`-----' `-----'
Figure 1: An End-to-end DetNet-Enabled Network
As showed in the picture, in an end-to-end DetNet-enabled network,
application flow is carried over a DetNet service and the DetNet
service is instantiated as different configuration parameters in
different network device along the path. DetNet service is an
abstract concept for service provider, and DetNet configuration needs
device specific attributes. YANG Models for DetNet service and
DetNet configuration are defined in detail respectively in section 3
and section 4.
Editor's notes:
Detnet YANG model and DetNet information model are supposed to keep
the same structure and describes the same attributes by different
methods. But the design of these two models are still under
discussion. The divergence will be settled in the following
versions.
2. Terminologies 2. Terminologies
This documents uses the terminologies defined in This documents uses the terminologies defined in
[I-D.ietf-detnet-architecture]. [I-D.ietf-detnet-architecture].
3. DetNet Configuration Model 3. DetNet Service Module
DetNet flow configuration includes DetNet App-flow configuration, DetNet Service Module includes service quality attributes, service
endpoints attributes and service encapsulation type attributes, which
are defined in Section 3.1, 3.2, 3.3 respectively.
3.1. Service Quality
DetNet service quality includes the following attributes:
o Maximum Latency: MaxLatency is the maximum latency from Ingress to
Egress(es) for a single packet of the DetNet flow. MaxLatency is
specified as an integer number of nanoseconds.
o Maximum Latency Variation: MaxLatencyVariation is the difference
between the minimum and the maximum end-to-end one-way latency.
MaxLatencyVariation is specified as an integer number of
nanoseconds.
o Maximum Loss: MaxLoss defines the maximum Packet Loss Ratio (PLR)
parameter for the DetNet service between the Ingress and
Egress(es) of the DetNet domain.
o Maximum Consecutive Loss: Maximum Consecutive Loss defines the
consecutive packet loss number.
o Maximum Misordering: MaxMisordering describes the maximum number
of packets that can be received out of order.
3.2. Service Endpoints
Endpoints attribute defines the starting and termination reference
points of the DetNet flow by pointing to the ingress interface/node
and egress interface(s)/node(s).
3.3. Service Encapsulation
Service Encapsulation attribute defines the data plane type of the
DetNet service in a DetNet domain, e.g., MPLS, IP.
Editor's notes: DetNet service module is just defined in the document
and the yang model is still under work.
4. DetNet Configuration Module
DetNet configuration module includes DetNet App-flow configuration,
DetNet Service Sub-layer configuration, and DetNet Forwarding Sub- DetNet Service Sub-layer configuration, and DetNet Forwarding Sub-
layer configuration and DetNet sub-network. The corresponding layer configuration and DetNet sub-network. The corresponding
attributes used in different sub-layers are defined in Section 3.1, attributes used in different sub-layers are defined in Section 3.1,
3.2, 3.3, 3.4 respectively. 3.2, 3.3, 3.4 respectively.
3.1. DetNet Appliction Flow Configuration Attributes 4.1. DetNet Appliction Flow Configuration Attributes
DetNet application flow is responsible for mapping between DetNet application flow is responsible for mapping between
application flows and DetNet flows at the edge node(egress/ingress application flows and DetNet flows at the edge node(egress/ingress
node). Where the application flows can be either layer 2 or layer 3 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 flows. To identify a flow at the User Network Interface (UNI), as
defined in [I-D.ietf-detnet-flow-information-model], the following defined in [I-D.ietf-detnet-flow-information-model], the following
flow attributes are introduced: flow attributes are introduced:
o DetNet L3 Flow Identification, refers to Section 7.1.1 of o DetNet L3 Flow Identification, refers to Section 7.1.1 of
[I-D.ietf-detnet-flow-information-model] [I-D.ietf-detnet-flow-information-model]
skipping to change at page 4, line 5 skipping to change at page 5, line 43
o DetNet L2 Flow Identification, refers to Section 7.1.2 of o DetNet L2 Flow Identification, refers to Section 7.1.2 of
[I-D.ietf-detnet-flow-information-model] [I-D.ietf-detnet-flow-information-model]
Application flow can also do flow filtering and policing at the Application flow can also do flow filtering and policing at the
ingress to prevent the misbehaviored flows from going into the ingress to prevent the misbehaviored flows from going into the
network, which needs: network, which needs:
o Traffic Specification, refers to Section 7.2 of o Traffic Specification, refers to Section 7.2 of
[I-D.ietf-detnet-flow-information-model] [I-D.ietf-detnet-flow-information-model]
3.2. DetNet Service Sub-layer Configuration Attributes 4.2. DetNet Service Sub-layer Configuration Attributes
DetNet service functions, e.g., DetNet tunnel initialization/ DetNet service functions, e.g., DetNet tunnel initialization/
termination and service protection, are provided in DetNet service termination and service protection, are provided in DetNet service
sub-layer. To support these functions, the following service sub-layer. To support these functions, the following service
attributes need to be configured: attributes need to be configured:
o DetNet flow identification, refers to Section 8.1.3 of o DetNet flow identification, refers to Section 8.1.3 of
[I-D.ietf-detnet-flow-information-model]. [I-D.ietf-detnet-flow-information-model].
o Service function indication, indicates which service function will o Service function indication, indicates which service function will
skipping to change at page 4, line 34 skipping to change at page 6, line 24
o Service Rank, refers to Section 16 of o Service Rank, refers to Section 16 of
[I-D.ietf-detnet-flow-information-model]. [I-D.ietf-detnet-flow-information-model].
o Service Sub-layer, refers to Section 4.5 and Section 4.6 of o Service Sub-layer, refers to Section 4.5 and Section 4.6 of
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
o Forwarding Sub-layer, refers to Section 4.3 of o Forwarding Sub-layer, refers to Section 4.3 of
[I-D.ietf-detnet-ip] and Section 4.5 and Section 4.6 of [I-D.ietf-detnet-ip] and Section 4.5 and Section 4.6 of
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
3.3. DetNet Forwarding Sub-layer Configuration Attributes 4.3. DetNet Forwarding Sub-layer Configuration Attributes
As defined in [I-D.ietf-detnet-architecture], DetNet forwarding sub- As defined in [I-D.ietf-detnet-architecture], DetNet forwarding sub-
layer optionally provides congestion protection for DetNet flows over layer optionally provides congestion protection for DetNet flows over
paths provided by the underlying network. Explicit route is another paths provided by the underlying network. Explicit route is another
mechanism that is used by DetNet to avoid temporary interruptions mechanism that is used by DetNet to avoid temporary interruptions
caused by the convergence of routing or bridging protocols, and it is caused by the convergence of routing or bridging protocols, and it is
also implemented at the DetNet forwarding sub-layer. also implemented at the DetNet forwarding sub-layer.
To support congestion protection and explicit route, the following To support congestion protection and explicit route, the following
transport layer related attributes are necessary: transport layer related attributes are necessary:
skipping to change at page 5, line 9 skipping to change at page 6, line 48
bandwidth reservation, flow shaping, filtering and policing. bandwidth reservation, flow shaping, filtering and policing.
o Explicit path, existing explicit route mechanisms can be reused. o Explicit path, existing explicit route mechanisms can be reused.
For example, if Segment Routing (SR) tunnel is used as the For example, if Segment Routing (SR) tunnel is used as the
transport tunnel, the configuration is mainly at the ingress node transport tunnel, the configuration is mainly at the ingress node
of the transport layer; if the static MPLS tunnel is used as the of the transport layer; if the static MPLS tunnel is used as the
transport tunnel, the configurations need to be at every transit transport tunnel, the configurations need to be at every transit
node along the path; for pure IP based transport tunnel, it's node along the path; for pure IP based transport tunnel, it's
similar to the static MPLS case. similar to the static MPLS case.
3.4. DetNet Sub-network Configurations Attributes 4.4. DetNet Sub-network Configurations Attributes
TBD TBD
4. Overview of DetNet YANG Structure 5. Overview of DetNet YANG
4.1. DetNet YANG Structure Considerations 5.1. DetNet YANG Considerations
5.1.1. DetNet Service YANG Considerations
TBD
5.1.2. DetNet Configuration YANG Considerations
The picture shows that the general structure of the DetNet YANG The picture shows that the general structure of the DetNet YANG
Model: Model:
+-----------+ +-----------+
|ietf-detnet| |ietf-detnet|
+-----+-----+ +-----+-----+
| |
+-------------+------+--------+--------------+ +-------------+------+--------+--------------+
| | | | | | | |
skipping to change at page 6, line 7 skipping to change at page 8, line 5
relationship to the lower sub-layer/sub-network. relationship to the lower sub-layer/sub-network.
o Operations: indicates DetNet functions, e.g., DetNet forwarding o Operations: indicates DetNet functions, e.g., DetNet forwarding
functions, DetNet Service functions, DetNet Resource Reservation. functions, DetNet Service functions, DetNet Resource Reservation.
These elements are different when the technologies used for the These elements are different when the technologies used for the
specific instance is different. So this structure is abstract, which specific instance is different. So this structure is abstract, which
allows for different technology specifics as defined in different allows for different technology specifics as defined in different
data plane drafts. data plane drafts.
4.2. DetNet YANG Structure 5.2. DetNet YANG Structures
4.2.1. YANG Structure of Application Flow 5.2.1. DetNet Service YANG Structure
The picture below shows that the general YANG structure of DetNet TBD
App-flow:
5.2.2. DetNet Configuration YANG Structure
+--rw app-flow +--rw app-flow
| +--rw operations | +--rw operations
| | +--rw sequence-number | | +--rw sequence-number
| | +--rw sequence-number-generation-type? sequence-number-generation-type | | +--rw sequence-number-generation-type? sequence-number-generation-type
| | +--rw sequence-number-length? uint8 | | +--rw sequence-number-length? uint8
| +--rw in-segments | +--rw in-segments
| | +--rw app-flow-type? flow-type-ref | | +--rw app-flow-type? flow-type-ref
| | +--rw source-mac-address? yang:mac-address | | +--rw source-mac-address? yang:mac-address
| | +--rw destination-mac-address? yang:mac-address | | +--rw destination-mac-address? yang:mac-address
skipping to change at page 6, line 44 skipping to change at page 8, line 43
| | +--rw traffic-class? uint8 | | +--rw traffic-class? uint8
| | +--rw traffic-class-bitmask? uint8 | | +--rw traffic-class-bitmask? uint8
| | +--rw flow-label? inet:ipv6-flow-label | | +--rw flow-label? inet:ipv6-flow-label
| | +--rw flow-label-flag? boolean | | +--rw flow-label-flag? boolean
| | +--rw lower-source-port? inet:port-number | | +--rw lower-source-port? inet:port-number
| | +--rw upper-source-port? inet:port-number | | +--rw upper-source-port? inet:port-number
| | +--rw lower-destination-port? inet:port-number | | +--rw lower-destination-port? inet:port-number
| | +--rw upper-destination-port? inet:port-number | | +--rw upper-destination-port? inet:port-number
| +--rw out-segments | +--rw out-segments
| +--rw detnet-service-sub-layer? lower-layer-ref | +--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 service-sub-layer
| +--rw operations | +--rw operations
| | +--rw service-operation | | +--rw service-operation
| | | +--rw service-operation-type? service-operation-ref | | | +--rw service-operation-type? service-operation-ref
| | +--rw service-protection | | +--rw service-protection
| | +--rw service-protection-type? service-protection-type | | +--rw service-protection-type? service-protection-type
| +--rw in-segments | +--rw in-segments
| | +--rw detnet-service-type? flow-type-ref | | +--rw detnet-service-type? flow-type-ref
| | +--rw detnet-service-list* [detnet-service-index] | | +--rw detnet-service-list* [detnet-service-index]
| | +--rw detnet-service-index uint8 | | +--rw detnet-service-index uint8
skipping to change at page 8, line 16 skipping to change at page 10, line 8
| | +--rw destination-port? inet:port-number | | +--rw destination-port? inet:port-number
| +--rw mpls-flow | +--rw mpls-flow
| | +--rw detnet-mpls-label-stack* [index] | | +--rw detnet-mpls-label-stack* [index]
| | +--rw index uint8 | | +--rw index uint8
| | +--rw label? rt-type:mpls-label | | +--rw label? rt-type:mpls-label
| | +--rw tc? uint8 | | +--rw tc? uint8
| | +--rw s-bit? boolean | | +--rw s-bit? boolean
| | +--rw d-cw-encapsulate-flag? boolean | | +--rw d-cw-encapsulate-flag? boolean
| +--rw detnet-forwarding-sub-layer-info | +--rw detnet-forwarding-sub-layer-info
| +--rw detnet-forwarding-sub-layer? lower-layer-ref | +--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 forwarding-sub-layer
| +--rw operations | +--rw operations
| | +--rw forwarding-operation | | +--rw forwarding-operation
| | | +--rw forwarding-operation-type? forwarding-operation-ref | | | +--rw forwarding-operation-type? forwarding-operation-ref
| | +--rw resource-allocate | | +--rw resource-allocate
| | | +--rw interval? uint32 | | | +--rw interval? uint32
| | | +--rw max-packets-per-interval? uint32 | | | +--rw max-packets-per-interval? uint32
| | | +--rw max-payload-size? uint32 | | | +--rw max-payload-size? uint32
| | | +--rw average-packets-per-interval? uint32 | | | +--rw average-packets-per-interval? uint32
| | | +--rw average-payload-size? uint32 | | | +--rw average-payload-size? uint32
skipping to change at page 9, line 47 skipping to change at page 11, line 33
| | +--rw tc? uint8 | | +--rw tc? uint8
| | +--rw s-bit? boolean | | +--rw s-bit? boolean
| | +--rw d-cw-encapsulate-flag? boolean | | +--rw d-cw-encapsulate-flag? boolean
| +--rw lower-layer-info | +--rw lower-layer-info
| +--rw lower-layer-type? flow-type-ref | +--rw lower-layer-type? flow-type-ref
| +--rw interface | +--rw interface
| | +--rw outgoing-interface? if:interface-ref | | +--rw outgoing-interface? if:interface-ref
| +--rw sub-layer | +--rw sub-layer
| +--rw sub-layer? lower-layer-ref | +--rw sub-layer? lower-layer-ref
4.2.4. YANG Structure of DetNet sub-network 6. DetNet Service YANG Model
TBD TBD
5. DetNet Configuration YANG Model 7. DetNet Configuration YANG Model
<CODE BEGINS> file ietf-detnet-config@20190324.yang <CODE BEGINS> file ietf-detnet-config@20190324.yang
module ietf-detnet-config { module ietf-detnet-config {
namespace "urn:ietf:params:xml:ns:yang:ietf-detnet-config"; namespace "urn:ietf:params:xml:ns:yang:ietf-detnet-config";
prefix "ietf-detnet"; prefix "ietf-detnet";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
skipping to change at page 34, line 4 skipping to change at page 35, line 34
container sub-network { container sub-network {
when "../config-type = 'ietf-detnet:tsn-sub-network'"; when "../config-type = 'ietf-detnet:tsn-sub-network'";
description description
"sub-network"; "sub-network";
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. Open Issues
8. Open Issues
There are some open issues that are still under discussion: There are some open issues that are still under discussion:
o The Relationship with 802.1 TSN YANG models is TBD. TSN YANG o The Relationship with 802.1 TSN YANG models is TBD. TSN YANG
models include: P802.1Qcw, which defines TSN YANG for Qbv, Qbu, models include: P802.1Qcw, which defines TSN YANG for Qbv, Qbu,
and Qci, and P802.1CBcv, which defines YANG for 802.1CB. The and Qci, and P802.1CBcv, which defines YANG for 802.1CB. The
possible problem here is how to avoid possible overlap among yang possible problem here is how to avoid possible overlap among yang
models defined in IETF and IEEE. A common YANG model may be models defined in IETF and IEEE. A common YANG model may be
defined in the future to shared by both TSN and DetNet. More defined in the future to shared by both TSN and DetNet. More
discussion are needed here. discussion are needed here.
o How to support DetNet OAM is TBD. o How to support DetNet OAM is TBD.
These issues will be resolved in the following versions of the draft. These issues will be resolved in the following versions of the draft.
7. IANA Considerations 9. IANA Considerations
This document makes no request of IANA. This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an Note to RFC Editor: this section may be removed on publication as an
RFC. RFC.
8. Security Considerations 10. Security Considerations
<TBD> <TBD>
9. Acknowledgements 11. Acknowledgements
10. References 12. References
10.1. Normative References 12.1. Normative References
[I-D.finn-detnet-bounded-latency] [I-D.finn-detnet-bounded-latency]
Finn, N., Boudec, J., Mohammadpour, E., Zhang, J., Varga, Finn, N., Boudec, J., Mohammadpour, E., Zhang, J., Varga,
B., and J. Farkas, "DetNet Bounded Latency", draft-finn- B., and J. Farkas, "DetNet Bounded Latency", draft-finn-
detnet-bounded-latency-04 (work in progress), June 2019. detnet-bounded-latency-04 (work in progress), June 2019.
[I-D.ietf-detnet-architecture] [I-D.ietf-detnet-architecture]
Finn, N., Thubert, P., Varga, B., and J. Farkas, Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", draft-ietf- "Deterministic Networking Architecture", draft-ietf-
detnet-architecture-13 (work in progress), May 2019. detnet-architecture-13 (work in progress), May 2019.
[I-D.ietf-detnet-flow-information-model] [I-D.ietf-detnet-flow-information-model]
Farkas, J., Varga, B., Cummings, R., and Y. Jiang, "DetNet Farkas, J., Varga, B., Cummings, R., Jiang, Y., and D.
Flow Information Model", draft-ietf-detnet-flow- Fedyk, "DetNet Flow Information Model", draft-ietf-detnet-
information-model-03 (work in progress), March 2019. flow-information-model-06 (work in progress), October
2019.
[I-D.ietf-detnet-ip] [I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: IP", Bryant, S., and J. Korhonen, "DetNet Data Plane: IP",
draft-ietf-detnet-ip-01 (work in progress), July 2019. draft-ietf-detnet-ip-03 (work in progress), October 2019.
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS", Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS",
draft-ietf-detnet-mpls-00 (work in progress), May 2019. draft-ietf-detnet-mpls-03 (work in progress), October
2019.
[I-D.ietf-detnet-topology-yang] [I-D.ietf-detnet-topology-yang]
Geng, X., Chen, M., Li, Z., and R. Rahman, "Deterministic Geng, X., Chen, M., Li, Z., and R. Rahman, "Deterministic
Networking (DetNet) Topology YANG Model", draft-ietf- Networking (DetNet) Topology YANG Model", draft-ietf-
detnet-topology-yang-00 (work in progress), January 2019. detnet-topology-yang-00 (work in progress), January 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
10.2. Informative References 12.2. Informative References
[I-D.geng-detnet-info-distribution] [I-D.geng-detnet-info-distribution]
Geng, X., Chen, M., and Z. Li, "IGP-TE Extensions for Geng, X., Chen, M., Li, Z., Qin, F., and L. Qiang, "IGP-TE
DetNet Information Distribution", draft-geng-detnet-info- Extensions for DetNet Information Distribution", draft-
distribution-03 (work in progress), October 2018. geng-detnet-info-distribution-04 (work in progress), July
2019.
[I-D.ietf-detnet-use-cases] [I-D.ietf-detnet-use-cases]
Grossman, E., "Deterministic Networking Use Cases", draft- Grossman, E., "Deterministic Networking Use Cases", draft-
ietf-detnet-use-cases-20 (work in progress), December ietf-detnet-use-cases-20 (work in progress), December
2018. 2018.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels and
Interfaces", draft-ietf-teas-yang-te-21 (work in Interfaces", draft-ietf-teas-yang-te-21 (work in
 End of changes. 34 change blocks. 
83 lines changed or deleted 163 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/