draft-ietf-detnet-flow-information-model-10.txt   draft-ietf-detnet-flow-information-model-11.txt 
DetNet B. Varga DetNet B. Varga
Internet-Draft J. Farkas Internet-Draft J. Farkas
Intended status: Informational Ericsson Intended status: Informational Ericsson
Expires: November 16, 2020 R. Cummings Expires: April 24, 2021 R. Cummings
National Instruments National Instruments
Y. Jiang Y. Jiang
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
D. Fedyk D. Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
May 15, 2020 October 21, 2020
DetNet Flow Information Model DetNet Flow Information Model
draft-ietf-detnet-flow-information-model-10 draft-ietf-detnet-flow-information-model-11
Abstract Abstract
This document describes flow and service information model for This document describes flow and service information model for
Deterministic Networking (DetNet). These models are defined for IP Deterministic Networking (DetNet). These models are defined for IP
and MPLS DetNet data planes and MPLS DetNet data planes
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 November 16, 2020. This Internet-Draft will expire on April 24, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
3.2. Reference Points Used in Modeling . . . . . . . . . . . . 7 3.2. Reference Points Used in Modeling . . . . . . . . . . . . 7
3.3. Information Elements . . . . . . . . . . . . . . . . . . 8 3.3. Information Elements . . . . . . . . . . . . . . . . . . 8
4. App-flow Related Parameters . . . . . . . . . . . . . . . . . 8 4. App-flow Related Parameters . . . . . . . . . . . . . . . . . 8
4.1. App-flow Characteristics . . . . . . . . . . . . . . . . 8 4.1. App-flow Characteristics . . . . . . . . . . . . . . . . 8
4.2. App-flow Requirements . . . . . . . . . . . . . . . . . . 9 4.2. App-flow Requirements . . . . . . . . . . . . . . . . . . 9
5. DetNet Flow Related Parameters . . . . . . . . . . . . . . . 9 5. DetNet Flow Related Parameters . . . . . . . . . . . . . . . 9
5.1. Management ID of the DetNet Flow . . . . . . . . . . . . 10 5.1. Management ID of the DetNet Flow . . . . . . . . . . . . 10
5.2. Payload type of the DetNet Flow . . . . . . . . . . . . . 10 5.2. Payload type of the DetNet Flow . . . . . . . . . . . . . 10
5.3. Format of the DetNet Flow . . . . . . . . . . . . . . . . 10 5.3. Format of the DetNet Flow . . . . . . . . . . . . . . . . 10
5.4. Identification and Specification of DetNet Flows . . . . 10 5.4. Identification and Specification of DetNet Flows . . . . 10
5.4.1. DetNet MPLS Flow Identification and Specification . . 10 5.4.1. DetNet MPLS Flow Identification and Specification . . 11
5.4.2. DetNet IP Flow Identification and Specification . . . 11 5.4.2. DetNet IP Flow Identification and Specification . . . 11
5.5. Traffic Specification of the DetNet Flow . . . . . . . . 11 5.5. Traffic Specification of the DetNet Flow . . . . . . . . 11
5.6. Endpoints of the DetNet Flow . . . . . . . . . . . . . . 12 5.6. Endpoints of the DetNet Flow . . . . . . . . . . . . . . 12
5.7. Rank of the DetNet Flow . . . . . . . . . . . . . . . . . 12 5.7. Rank of the DetNet Flow . . . . . . . . . . . . . . . . . 12
5.8. Status of the DetNet Flow . . . . . . . . . . . . . . . . 12 5.8. Status of the DetNet Flow . . . . . . . . . . . . . . . . 12
5.9. Requirements of the DetNet Flow . . . . . . . . . . . . . 13 5.9. Requirements of the DetNet Flow . . . . . . . . . . . . . 13
5.9.1. Minimum Bandwidth of the DetNet Flow . . . . . . . . 13 5.9.1. Minimum Bandwidth of the DetNet Flow . . . . . . . . 13
5.9.2. Maximum Latency of the DetNet Flow . . . . . . . . . 13 5.9.2. Maximum Latency of the DetNet Flow . . . . . . . . . 13
5.9.3. Maximum Latency Variation of the DetNet Flow . . . . 13 5.9.3. Maximum Latency Variation of the DetNet Flow . . . . 14
5.9.4. Maximum Loss of the DetNet Flow . . . . . . . . . . . 13 5.9.4. Maximum Loss of the DetNet Flow . . . . . . . . . . . 14
5.9.5. Maximum Consecutive Loss of the DetNet Flow . . . . . 14 5.9.5. Maximum Consecutive Loss of the DetNet Flow . . . . . 14
5.9.6. Maximum Misordering Tolerance of the DetNet Flow . . 14 5.9.6. Maximum Misordering Tolerance of the DetNet Flow . . 14
5.10. BiDir requirement of the DetNet Flow . . . . . . . . . . 14 5.10. BiDir requirement of the DetNet Flow . . . . . . . . . . 14
6. DetNet Service Related Parameters . . . . . . . . . . . . . . 14 6. DetNet Service Related Parameters . . . . . . . . . . . . . . 14
6.1. Management ID of the DetNet service . . . . . . . . . . . 14 6.1. Management ID of the DetNet service . . . . . . . . . . . 15
6.2. Delivery Type of the DetNet service . . . . . . . . . . . 15 6.2. Delivery Type of the DetNet service . . . . . . . . . . . 15
6.3. Delivery Profile of the DetNet Service . . . . . . . . . 15 6.3. Delivery Profile of the DetNet Service . . . . . . . . . 15
6.3.1. Minimum Bandwidth of the DetNet Service . . . . . . . 15 6.3.1. Minimum Bandwidth of the DetNet Service . . . . . . . 15
6.3.2. Maximum Latency of the DetNet Service . . . . . . . . 15 6.3.2. Maximum Latency of the DetNet Service . . . . . . . . 15
6.3.3. Maximum Latency Variation of the DetNet Service . . . 15 6.3.3. Maximum Latency Variation of the DetNet Service . . . 15
6.3.4. Maximum Loss of the DetNet Service . . . . . . . . . 15 6.3.4. Maximum Loss of the DetNet Service . . . . . . . . . 15
6.3.5. Maximum Consecutive Loss of the DetNet Service . . . 15 6.3.5. Maximum Consecutive Loss of the DetNet Service . . . 16
6.3.6. Maximum Misordering Tolerance of the DetNet Service . 16 6.3.6. Maximum Misordering Tolerance of the DetNet Service . 16
6.4. Connectivity Type of the DetNet Service . . . . . . . . . 16 6.4. Connectivity Type of the DetNet Service . . . . . . . . . 16
6.5. BiDir requirement of the DetNet Service . . . . . . . . . 16 6.5. BiDir requirement of the DetNet Service . . . . . . . . . 16
6.6. Rank of the DetNet Service . . . . . . . . . . . . . . . 16 6.6. Rank of the DetNet Service . . . . . . . . . . . . . . . 16
6.7. Status of the DetNet Service . . . . . . . . . . . . . . 16 6.7. Status of the DetNet Service . . . . . . . . . . . . . . 16
7. Flow Specific Operations . . . . . . . . . . . . . . . . . . 17 7. Flow Specific Operations . . . . . . . . . . . . . . . . . . 17
7.1. Join Operation . . . . . . . . . . . . . . . . . . . . . 18 7.1. Join Operation . . . . . . . . . . . . . . . . . . . . . 18
7.2. Leave Operation . . . . . . . . . . . . . . . . . . . . . 18 7.2. Leave Operation . . . . . . . . . . . . . . . . . . . . . 18
7.3. Modify Operation . . . . . . . . . . . . . . . . . . . . 18 7.3. Modify Operation . . . . . . . . . . . . . . . . . . . . 18
8. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10. Security Considerations . . . . . . . . . . . . . . . . . . . 19 10. Security Considerations . . . . . . . . . . . . . . . . . . . 19
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
11.1. Normative References . . . . . . . . . . . . . . . . . . 19 11.1. Normative References . . . . . . . . . . . . . . . . . . 19
11.2. Informative References . . . . . . . . . . . . . . . . . 19 11.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
Deterministic Networking (DetNet) provides a capability to carry Deterministic Networking (DetNet) provides a capability to carry
specified unicast or multicast data flows for real-time applications specified unicast or multicast data flows for real-time applications
with extremely low packet loss rates and assured maximum end-to-end with extremely low packet loss rates and assured maximum end-to-end
delivery latency. A description of the general background and delivery latency. A description of the general background and
concepts of DetNet can be found in [RFC8655]. concepts of DetNet can be found in [RFC8655].
This document describes the Detnet Flow Service Information Model. This document describes the Detnet Flow and Service Information
For reference [RFC3444] describes the rational behind Information Model. For reference [RFC3444] describes the rational behind
Models in general. This document describes the Flow and Service Information Models in general. This document describes the Flow and
information models for operators and users to understand Detnet Service information models for operators and users to understand
services, and for implementors as a guide to the functionality Detnet services, and for implementors as a guide to the functionality
required by Detnet services. required by Detnet services.
The DetNet Architecture treats the DetNet related data plane The DetNet Architecture treats the DetNet related data plane
functions decomposed into two sub-layers: a service sub-layer and a functions decomposed into two sub-layers: a service sub-layer and a
forwarding sub-layer. The service sub-layer is used to provide forwarding sub-layer. The service sub-layer is used to provide
DetNet service protection and reordering. The forwarding sub-layer DetNet service protection and reordering. The forwarding sub-layer
provides resource allocation (to ensure low loss, assured latency, provides resource allocation (to ensure low loss, assured latency,
and limited out-of-order delivery) and leverages Traffic Engineering and limited out-of-order delivery) and leverages Traffic Engineering
mechanisms. mechanisms.
skipping to change at page 4, line 28 skipping to change at page 4, line 28
As shown in Figure 1 as per [I-D.ietf-detnet-data-plane-framework] a As shown in Figure 1 as per [I-D.ietf-detnet-data-plane-framework] a
DetNet flow can be treated as an application level flow (App-flow) DetNet flow can be treated as an application level flow (App-flow)
e.g., at DetNet flow aggregation or in a sub-network that e.g., at DetNet flow aggregation or in a sub-network that
interconnects DetNet nodes. interconnects DetNet nodes.
The DetNet flow and service information model provided by this The DetNet flow and service information model provided by this
document contains both DetNet flow and App-flow specific information document contains both DetNet flow and App-flow specific information
in an integrated fashion. in an integrated fashion.
In a given network scenario three information models can In a given network scenario three information models can be
distinguished: distinguished:
o Flow models that describe characteristics of data flows. These o Flow models that describe characteristics of data flows. These
models describe in detail all relevant aspects of a flow that are models describe in detail all relevant aspects of a flow that are
needed to support the flow properly by the network between the needed to support the flow properly by the network between the
source and the destination(s). source and the destination(s).
o Service models that describe characteristics of services being o Service models that describe characteristics of services being
provided for data flows over a network. These models can be provided for data flows over a network. These models can be
treated as a network operator independent information model. treated as a network operator independent information model.
skipping to change at page 5, line 25 skipping to change at page 5, line 25
+-+ | v Network +-+ | v Network
+-+ v +-+ nodes +-+ v +-+ nodes
+-+ +-+ +-+ +-+
+-+ +-+
Figure 2: Usage of Information models (flow, service and Figure 2: Usage of Information models (flow, service and
configuration) configuration)
DetNet flow and service information model is based on [RFC8655] and DetNet flow and service information model is based on [RFC8655] and
on the concept of data model specified by [IEEE8021Qcc]. on the concept of data model specified by [IEEE8021Qcc].
Furthermore, the origination of the DetNet flow information model was Furthermore, the DetNet flow and service information models described
the flow identification possibilities described in Section 6. of in this document are based on [IEEE8021Qcc]. In addition to the TSN
[IEEE8021CB], which is used by [IEEE8021Qcc] as well. In addition to data model, [IEEE8021Qcc] also specifies configuration of TSN
the TSN data model, [IEEE8021Qcc] also specifies configuration of TSN
features (e.g., traffic scheduling specified by [IEEE8021Qbv]). The features (e.g., traffic scheduling specified by [IEEE8021Qbv]). The
common architecture and flow model, allow configured features to be common architecture and flow model, allow configured features to be
consistent in certain deployment scenarios, e.g., when the network consistent in certain deployment scenarios, e.g., when the network
that provides the DetNet service includes both L3 and L2 network that provides the DetNet service includes both L3 and L2 network
segments. segments.
1.1. Goals 1.1. Goals
As expressed in the [IETFDetNet] Charter, the DetNet WG collaborates As expressed in the [IETFDetNet] Charter, the DetNet WG collaborates
with IEEE 802.1 TSN in order to define a common architecture for both with IEEE 802.1 TSN in order to define a common architecture for both
skipping to change at page 8, line 50 skipping to change at page 8, line 48
App-flow characteristics are described by the following parameters: App-flow characteristics are described by the following parameters:
o FlowID: a unique (management) identifier of the App-flow. It can o FlowID: a unique (management) identifier of the App-flow. It can
be used to define the N:1 mapping of App-flows to a DetNet flow. be used to define the N:1 mapping of App-flows to a DetNet flow.
o FlowType: set by the encapsulation format of the flow. It can be o FlowType: set by the encapsulation format of the flow. It can be
Ethernet (TSN), MPLS, or IP. Ethernet (TSN), MPLS, or IP.
o DataFlowSpecification: a flow descriptor, defining which packets o DataFlowSpecification: a flow descriptor, defining which packets
belongs to a flow using, specific packet header fields such as belongs to a flow, using specific packet header fields such as
src-addr, dst-addr, label, VLAN-ID, etc. src-addr, dst-addr, label, VLAN-ID, etc.
o TrafficSpecification: a flow descriptor, defining traffic o TrafficSpecification: a flow descriptor, defining traffic
parameters such as packet size, transmission time interval, and parameters such as packet size, transmission time interval, and
maximum packets per time interval. maximum packets per time interval.
o FlowEndpoints: delineate the start and termination reference o FlowEndpoints: delineate the start and termination reference
points of the App-flow by pointing to the source interface/node points of the App-flow by pointing to the source interface/node
and destination interface(s)/node(s). and destination interface(s)/node(s).
o FlowStatus: indicates the status of the App-flow with respect to o FlowStatus: indicates the status of the App-flow with respect to
the establishment of the flow by the connected network, e.g., the establishment of the flow by the connected network, e.g.,
ready, failed, etc. ready, failed, etc.
o FlowRank: indicates the rank of this flow relative to other flows o FlowRank: indicates the rank of this flow relative to other flows
in the connected network. in the connected network.
Note: When defining the N:1 mapping of App-flows to a DetNet flow,
the App-flows must have the same FlowType and different
DataFlowSpecification parameters
4.2. App-flow Requirements 4.2. App-flow Requirements
App-flow requirements are described by the following parameters: App-flow requirements are described by the following parameters:
o FlowRequirements: defines the attributes of the App-flow regarding o FlowRequirements: defines the attributes of the App-flow regarding
bandwidth, latency, latency variation, loss, and misordering bandwidth, latency, latency variation, loss, and misordering
tolerance. tolerance.
o FlowBiDir: defines the data path requirement of the App-flow o FlowBiDir: defines the data path requirement of the App-flow
whether it must share the same data path and physical path for whether it must share the same data path and physical path for
skipping to change at page 9, line 41 skipping to change at page 9, line 45
paths in the two directions. paths in the two directions.
5. DetNet Flow Related Parameters 5. DetNet Flow Related Parameters
The Data model specified by [IEEE8021Qcc] describes data flows using The Data model specified by [IEEE8021Qcc] describes data flows using
TSN service as periodic flows with fix packet size (i.e., Constant TSN service as periodic flows with fix packet size (i.e., Constant
Bit Rate (CBR) flows) or with variable packet size. The same concept Bit Rate (CBR) flows) or with variable packet size. The same concept
is applied for flows using DetNet service. is applied for flows using DetNet service.
Latency and loss parameters are correlated because the effect of late Latency and loss parameters are correlated because the effect of late
delivery can result data loss for an application. However, not all delivery can result in data loss for an application. However, not
applications require hard limits on both latency and loss. For all applications require hard limits on both latency and loss. For
example, some real-time applications allow graceful degradation if example, some real-time applications allow graceful degradation if
loss happens (e.g., sample-based data processing, media loss happens (e.g., sample-based data processing, media
distribution). Some other applications may require high-bandwidth distribution). Some other applications may require high-bandwidth
connections that make use of packet replication techniques which are connections that make use of packet replication techniques which are
economically challenging or even impossible. Some applications may economically challenging or even impossible. Some applications may
not tolerate loss, but are not delay sensitive (e.g., bufferless not tolerate loss, but are not delay sensitive (e.g., bufferless
sensors). Time or loss sensitive applications may have somewhat sensors). Time or loss sensitive applications may have somewhat
special requirements especially for loss (e.g., no loss over two special requirements especially for loss (e.g., no loss over two
consecutive communication cycles; very low outage time, etc.). consecutive communication cycles; very low outage time, etc.).
skipping to change at page 10, line 51 skipping to change at page 11, line 10
Identification options for DetNet flows at the Ingress/Egress and Identification options for DetNet flows at the Ingress/Egress and
within the DetNet domain are specified as follows; see Section 5.4.1 within the DetNet domain are specified as follows; see Section 5.4.1
for DetNet MPLS flows and Section 5.4.2 for DetNetw IP flows. for DetNet MPLS flows and Section 5.4.2 for DetNetw IP flows.
5.4.1. DetNet MPLS Flow Identification and Specification 5.4.1. DetNet MPLS Flow Identification and Specification
The identification of DetNet MPLS flows within the DetNet domain is The identification of DetNet MPLS flows within the DetNet domain is
based on the MPLS context in the service information model. The based on the MPLS context in the service information model. The
attributes are specific to the MPLS forwarding paradigm within the attributes are specific to the MPLS forwarding paradigm within the
DetNet domain [I-D.ietf-detnet-mpls]. DetNetwork MPLS flows can be DetNet domain [I-D.ietf-detnet-mpls]. DetNet MPLS flows can be
identified and specified by the following attributes: identified and specified by the following attributes:
a. SLabel a. SLabel
b. FLabelStack b. FLabelStack
5.4.2. DetNet IP Flow Identification and Specification 5.4.2. DetNet IP Flow Identification and Specification
DetNet IP flows can be identified and specified by the following DetNet IP flows can be identified and specified by the following
attributes [I-D.ietf-detnet-ip]: attributes [I-D.ietf-detnet-ip]:
skipping to change at page 13, line 4 skipping to change at page 13, line 13
* OutOfService: Administratively blocked. * OutOfService: Administratively blocked.
b. DnEgressStatus is an enumeration for the status of the flow's b. DnEgressStatus is an enumeration for the status of the flow's
Egress reference points: Egress reference points:
* None: no Egress. * None: no Egress.
* Ready: all Egresses are ready. * Ready: all Egresses are ready.
* PartialFailed: One or more Egress ready, and one or more * PartialFailed: One or more Egress ready, and one or more
Egress failed. The DetNet flow can be used if the Ingress is Egress failed. The DetNet flow can be used if the Ingress is
Ready. Ready.
* Failed: All Egresses failed. * Failed: All Egresses failed.
* OutOfService: Administratively blocked. * OutOfService: All Egresses are administratively blocked.
c. FailureCode: A non-zero code that specifies the error if the c. FailureCode: A non-zero code that specifies the error if the
DetNet flow encounters a failure (e.g., packet replication and DetNet flow encounters a failure (e.g., packet replication and
elimination is requested but not possible, or DnIngressStatus is elimination is requested but not possible, or DnIngressStatus is
Failed, or DnEgressStatus is Failed, or DnEgressStatus is Failed, or DnEgressStatus is Failed, or DnEgressStatus is
PartialFailed). PartialFailed).
Defining FailureCodes for DetNet is out-of-scope in this document. Defining FailureCodes for DetNet is out-of-scope in this document.
Table 46-1 of [IEEE8021Qcc] describes TSN failure codes. Table 46-1 of [IEEE8021Qcc] describes TSN failure codes.
skipping to change at page 18, line 45 skipping to change at page 19, line 4
that the resources committed to the current flow are in use. By that the resources committed to the current flow are in use. By
using Modify the controller entity knows that the resources using Modify the controller entity knows that the resources
supporting the current flow can be available for supporting the supporting the current flow can be available for supporting the
altered flow. Modify is considered to be an optional operation due altered flow. Modify is considered to be an optional operation due
to possible controller plane limitations. to possible controller plane limitations.
8. Summary 8. Summary
This document describes the DetNet flow information model and the This document describes the DetNet flow information model and the
service information model for DetNet IP networks and DetNet MPLS service information model for DetNet IP networks and DetNet MPLS
networks. These models are used as input for the YANG model. networks. These models are used as input for creating the DetNet
specific YANG model.
9. IANA Considerations 9. IANA Considerations
N/A. N/A.
10. Security Considerations 10. Security Considerations
The external interfaces of the DetNet domain need to be subject to The external interfaces of the DetNet domain need to be subject to
appropriate confidentiality. Additionally, knowledge of which flows/ appropriate confidentiality. Additionally, knowledge of which flows/
services are provided to a customer or delivered by a network services are provided to a customer or delivered by a network
skipping to change at page 19, line 22 skipping to change at page 19, line 28
in detail in [I-D.ietf-detnet-security]. General security in detail in [I-D.ietf-detnet-security]. General security
considerations are described in [RFC8655]. This document discusses considerations are described in [RFC8655]. This document discusses
modeling the information, not how it is exchanged. modeling the information, not how it is exchanged.
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.ietf-detnet-ip] [I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., and S. Varga, B., Farkas, J., Berger, L., Fedyk, D., and S.
Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-06 Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-07
(work in progress), April 2020. (work in progress), July 2020.
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S., Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S.,
and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf- and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf-
detnet-mpls-06 (work in progress), April 2020. detnet-mpls-13 (work in progress), October 2020.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655, "Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019, DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>. <https://www.rfc-editor.org/info/rfc8655>.
11.2. Informative References 11.2. Informative References
[I-D.ietf-detnet-data-plane-framework] [I-D.ietf-detnet-data-plane-framework]
Varga, B., Farkas, J., Berger, L., Malis, A., and S. Varga, B., Farkas, J., Berger, L., Malis, A., and S.
Bryant, "DetNet Data Plane Framework", draft-ietf-detnet- Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
data-plane-framework-06 (work in progress), May 2020. data-plane-framework-06 (work in progress), May 2020.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T. and E. Grossman, "Deterministic Networking Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic
(DetNet) Security Considerations", draft-ietf-detnet- Networking (DetNet) Security Considerations", draft-ietf-
security-09 (work in progress), March 2020. detnet-security-12 (work in progress), October 2020.
[IEEE8021CB]
IEEE Standards Association, "IEEE Std 802.1CB-2017 IEEE
Standard for Local and metropolitan area networks - Frame
Replication and Elimination for Reliability", 2017,
<https://ieeexplore.ieee.org/document/8091139/>.
[IEEE8021Q] [IEEE8021Q]
IEEE Standards Association, "IEEE Std 802.1Q-2018 IEEE IEEE Standards Association, "IEEE Std 802.1Q-2018 IEEE
Standard for Local and metropolitan area networks - Standard for Local and metropolitan area networks -
Bridges and Bridged Networks", 2018, Bridges and Bridged Networks", 2018,
<https://ieeexplore.ieee.org/document/8403927>. <https://ieeexplore.ieee.org/document/8403927>.
[IEEE8021Qbv] [IEEE8021Qbv]
IEEE Standards Association, "IEEE Std 802.1Qbv-2015 IEEE IEEE Standards Association, "IEEE Std 802.1Qbv-2015 IEEE
Standard for Local and metropolitan area networks - Standard for Local and metropolitan area networks -
 End of changes. 22 change blocks. 
39 lines changed or deleted 36 lines changed or added

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