draft-ietf-detnet-flow-information-model-06.txt   draft-ietf-detnet-flow-information-model-07.txt 
DetNet J. Farkas DetNet J. Farkas
Internet-Draft B. Varga Internet-Draft B. Varga
Intended status: Standards Track Ericsson Intended status: Informational Ericsson
Expires: April 29, 2020 R. Cummings Expires: September 2, 2020 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.
October 27, 2019 March 1, 2020
DetNet Flow Information Model DetNet Flow Information Model
draft-ietf-detnet-flow-information-model-06 draft-ietf-detnet-flow-information-model-07
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 April 29, 2020. This Internet-Draft will expire on September 2, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 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
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
skipping to change at page 2, line 18 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Non Goals . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2. Non Goals . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Terms Used in This Document . . . . . . . . . . . . . . . 6 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 6
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 7 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 7
2.3. Naming Conventions . . . . . . . . . . . . . . . . . . . 7 2.3. Naming Conventions . . . . . . . . . . . . . . . . . . . 7
2.4. Requirements Language . . . . . . . . . . . . . . . . . . 7
3. DetNet Domain and its Modeling . . . . . . . . . . . . . . . 7 3. DetNet Domain and its Modeling . . . . . . . . . . . . . . . 7
3.1. DetNet Service Overview . . . . . . . . . . . . . . . . . 7 3.1. DetNet Service Overview . . . . . . . . . . . . . . . . . 7
3.2. Reference Points Used in Modeling . . . . . . . . . . . . 8 3.2. Reference Points Used in Modeling . . . . . . . . . . . . 7
3.3. Information Elements . . . . . . . . . . . . . . . . . . 8 3.3. Information Elements . . . . . . . . . . . . . . . . . . 8
4. App-flow Related Parameters . . . . . . . . . . . . . . . . . 9 4. App-flow Related Parameters . . . . . . . . . . . . . . . . . 8
4.1. App-flow Characteristics . . . . . . . . . . . . . . . . 9 4.1. App-flow Characteristics . . . . . . . . . . . . . . . . 9
4.2. App-flow Requirements . . . . . . . . . . . . . . . . . . 9 4.2. App-flow Requirements . . . . . . . . . . . . . . . . . . 9
5. DetNet Flow Related Parameters . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . 11 5.2. Payload type of the DetNet Flow . . . . . . . . . . . . . 10
5.3. Format of the DetNet Flow . . . . . . . . . . . . . . . . 11 5.3. Format of the DetNet Flow . . . . . . . . . . . . . . . . 10
5.4. Identification and Specification of DetNet Flows . . . . 11 5.4. Identification and Specification of DetNet Flows . . . . 11
5.4.1. DetNet MPLS Flow Identification and Specification . . 11 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 . . . . . . . . . . . . . . . . 13 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 . . . . . . . . 14 5.9.1. Minimum Bandwidth of the DetNet Flow . . . . . . . . 13
5.9.2. Maximum Latency of the DetNet Flow . . . . . . . . . 14 5.9.2. Maximum Latency of the DetNet Flow . . . . . . . . . 14
5.9.3. Maximum Latency Variation of the DetNet Flow . . . . 14 5.9.3. Maximum Latency Variation of the DetNet Flow . . . . 14
5.9.4. Maximum Loss of the DetNet Flow . . . . . . . . . . . 14 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 . . . . . . . . . . . . . . 15 6. DetNet Service Related Parameters . . . . . . . . . . . . . . 14
6.1. Management ID of the DetNet service . . . . . . . . . . . 15 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 . . . . . . . . 16 6.3.2. Maximum Latency of the DetNet Service . . . . . . . . 15
6.3.3. Maximum Latency Variation of the DetNet Service . . . 16 6.3.3. Maximum Latency Variation of the DetNet Service . . . 16
6.3.4. Maximum Loss of the DetNet Service . . . . . . . . . 16 6.3.4. Maximum Loss of the DetNet Service . . . . . . . . . 16
6.3.5. Maximum Consecutive Loss of the DetNet Service . . . 16 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 . . . . . . . . . . . . . . . 17 6.6. Rank of the DetNet Service . . . . . . . . . . . . . . . 16
6.7. Status of the DetNet Service . . . . . . . . . . . . . . 17 6.7. Status of the DetNet Service . . . . . . . . . . . . . . 17
7. Flow Specific Operations . . . . . . . . . . . . . . . . . . 18 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 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 . . . . . . . . . . . . . . . . . 20 11.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
skipping to change at page 7, line 35 skipping to change at page 7, line 35
o Names SHOULD be descriptive. o Names SHOULD be descriptive.
o Names MUST start with uppercase letters. o Names MUST start with uppercase letters.
o Composed names MUST use capital letters for the first letter of o Composed names MUST use capital letters for the first letter of
each component. All other letters are lowercase, even for each component. All other letters are lowercase, even for
acronyms. Exceptions are made for acronyms containing a mixture acronyms. Exceptions are made for acronyms containing a mixture
of lowercase and capital letters, such as IPv6. Example composed of lowercase and capital letters, such as IPv6. Example composed
names are SourceMacAddress and DestinationIPv6Address. names are SourceMacAddress and DestinationIPv6Address.
2.4. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. DetNet Domain and its Modeling 3. DetNet Domain and its Modeling
3.1. DetNet Service Overview 3.1. DetNet Service Overview
The DetNet service can be defined as a service that provides a The DetNet service can be defined as a service that provides a
capability to carry a unicast or a multicast data flow for an capability to carry a unicast or a multicast data flow for an
application with constrained requirements on network performance, application with constrained requirements on network performance,
e.g., low packet loss rate and/or latency. e.g., low packet loss rate and/or latency.
Figure 5 and Figure 8 in [I-D.ietf-detnet-architecture] show the Figure 5 and Figure 8 in [I-D.ietf-detnet-architecture] show the
skipping to change at page 11, line 35 skipping to change at page 11, line 25
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]. DetNetwork 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 (6-tuple) [I-D.ietf-detnet-ip]: attributes [I-D.ietf-detnet-ip]:
a. SourceIpAddress a. SourceIpAddress
b. DestinationIpAddress b. DestinationIpAddress
c. IPv6FlowLabel c. IPv6FlowLabel
d. Dscp (attribute) d. Dscp (attribute)
e. Protocol e. Protocol
f. SourcePort f. SourcePort
g. DestinationPort g. DestinationPort
h. IPSecSpi h. IPSecSpi
The IP 6-tuple that is used for DetNet IP flow identification
consists of items a, b, d, e, f, and g. Items c and h are additional
attributes that can be used for DetNet flow identification in
addition to the 6-tuple.
5.5. Traffic Specification of the DetNet Flow 5.5. Traffic Specification of the DetNet Flow
DnTrafficSpecification attributes specify how the DN Ingress DnTrafficSpecification attributes specify how the DN Ingress
transmits packets for the DetNet flow. This is effectively the transmits packets for the DetNet flow. This is effectively the
promise/request of the DN Ingress to the network. The network uses promise/request of the DN Ingress to the network. The network uses
this traffic specification to allocate resources and adjust queue this traffic specification to allocate resources and adjust queue
parameters in network nodes. parameters in network nodes.
TrafficSpecification has the following attributes: TrafficSpecification has the following attributes:
skipping to change at page 13, line 10 skipping to change at page 12, line 49
resources reach their limit. Rank is used to help to determine which resources reach their limit. Rank is used to help to determine which
flows can be bumped (i.e., removed from node configuration thereby flows can be bumped (i.e., removed from node configuration thereby
releasing its resources) if for example a port of a node becomes releasing its resources) if for example a port of a node becomes
oversubscribed (e.g., due to network re-configuration). oversubscribed (e.g., due to network re-configuration).
5.8. Status of the DetNet Flow 5.8. Status of the DetNet Flow
DnFlowStatus provides the status of the DetNet flow with respect to DnFlowStatus provides the status of the DetNet flow with respect to
the establishment of the flow by the DetNet domain. the establishment of the flow by the DetNet domain.
The DnFlowStatus SHALL include the following attributes: The DnFlowStatus includes the following attributes:
a. DnIngressStatus is an enumeration for the status of the flow's a. DnIngressStatus is an enumeration for the status of the flow's
Ingress reference point: Ingress reference point:
* None: no Ingress. * None: no Ingress.
* Ready: Ingress is ready. * Ready: Ingress is ready.
* Failed: Ingress failed. * Failed: Ingress failed.
* 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
skipping to change at page 17, line 19 skipping to change at page 17, line 14
(range: 0-255) is used by the network in case of network resource (range: 0-255) is used by the network in case of network resource
limitation scenarios. limitation scenarios.
6.7. Status of the DetNet Service 6.7. Status of the DetNet Service
DnServiceStatus information group includes elements that specify the DnServiceStatus information group includes elements that specify the
status of the service specific state of the DetNet domain. This status of the service specific state of the DetNet domain. This
information group informs the user whether or not the service is information group informs the user whether or not the service is
ready for use. ready for use.
The DnServiceStatus SHALL include the following attributes: The DnServiceStatus includes the following attributes:
a. DnServiceIngressStatus is an enumeration for the status of the a. DnServiceIngressStatus is an enumeration for the status of the
service's Ingress: service's Ingress:
* None: no Ingress. * None: no Ingress.
* Ready: Ingress is ready. * Ready: Ingress is ready.
* Failed: Ingress failed. * Failed: Ingress failed.
* OutOfService: Administratively blocked. * OutOfService: Administratively blocked.
b. DnServiceEgressStatus is an enumeration for the status of the b. DnServiceEgressStatus is an enumeration for the status of the
skipping to change at page 18, line 37 skipping to change at page 18, line 29
to its DetNet service at a DN Ingress or a DN Egress (similarly to to its DetNet service at a DN Ingress or a DN Egress (similarly to
App-flows at a Source or a Destination): App-flows at a Source or a Destination):
o Join: DN Ingress/DN Egress intends to join the flow. o Join: DN Ingress/DN Egress intends to join the flow.
o Leave: DN Ingress/DN Egress intends to leave the flow. o Leave: DN Ingress/DN Egress intends to leave the flow.
o Modify: DN Ingress/DN Egress intends to change the flow. o Modify: DN Ingress/DN Egress intends to change the flow.
7.1. Join Operation 7.1. Join Operation
For the join operation, the DnFlowSpecification, DnFlowRank, For the join operation, the DnFlowSpecification, DnFlowRank,
DnFlowEndpoint, and DnTrafficSpecification SHALL be included within DnFlowEndpoint, and DnTrafficSpecification are included within the
the DnIngress or DnEgress information group. For the join operation, DnIngress or DnEgress information group. For the join operation, the
the DnServiceRequirements groups MAY be included. DnServiceRequirements groups can be included.
7.2. Leave Operation 7.2. Leave Operation
For the leave operation, the DnFlowSpecification and DnFlowEndpoint For the leave operation, the DnFlowSpecification and DnFlowEndpoint
SHALL be included within the DnIngress or DnEgress information group. are included within the DnIngress or DnEgress information group.
7.3. Modify Operation 7.3. Modify Operation
For the modify operation, the DnFlowSpecification, DnFlowRank, For the modify operation, the DnFlowSpecification, DnFlowRank,
DnFlowEndpoint, and DnTrafficSpecification SHALL be included within DnFlowEndpoint, and DnTrafficSpecification are included within the
the DnIngress or DnEgress information group. For the join operation, DnIngress or DnEgress information group. For the join operation, the
the DnServiceRequirements groups MAY be included. DnServiceRequirements groups can be included.
The Modify operation can be considered to address cases when a flow The Modify operation can be considered to address cases when a flow
is slightly changed, e.g., only MaxPayloadSize (Section 5.5) has been is slightly changed, e.g., only MaxPayloadSize (Section 5.5) has been
changed. The advantage of having a Modify is that it allows changed. The advantage of having a Modify is that it allows
initiation of a change of flow spec while leaving the current flow is initiation of a change of flow spec while leaving the current flow is
operating until the change is accepted. If there is no linkage operating until the change is accepted. If there is no linkage
between the Join and the Leave, then while figuring out whether the between the Join and the Leave, then while figuring out whether the
new flow spec can be supported, the controller entity has to assume new flow spec can be supported, the controller entity has to assume
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
skipping to change at page 19, line 46 skipping to change at page 19, line 38
11.1. Normative References 11.1. Normative References
[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-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", and S. Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-
draft-ietf-detnet-ip-01 (work in progress), July 2019. ip-05 (work in progress), February 2020.
[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-01 (work in progress), July 2019. draft-ietf-detnet-mpls-05 (work in progress), February
2020.
[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>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
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., Fedyk, D., Malis, A., Varga, B., Farkas, J., Berger, L., Malis, A., and S.
Bryant, S., and J. Korhonen, "DetNet Data Plane Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
Framework", draft-ietf-detnet-data-plane-framework-02 data-plane-framework-04 (work in progress), February 2020.
(work in progress), September 2019.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell,
J., Austad, H., Stanton, K., and N. Finn, "Deterministic J., Austad, H., and N. Finn, "Deterministic Networking
Networking (DetNet) Security Considerations", draft-ietf- (DetNet) Security Considerations", draft-ietf-detnet-
detnet-security-05 (work in progress), August 2019. security-08 (work in progress), February 2020.
[IEEE8021CB] [IEEE8021CB]
IEEE Standards Association, "IEEE Std 802.1CB-2017 IEEE IEEE Standards Association, "IEEE Std 802.1CB-2017 IEEE
Standard for Local and metropolitan area networks - Frame Standard for Local and metropolitan area networks - Frame
Replication and Elimination for Reliability", 2017, Replication and Elimination for Reliability", 2017,
<https://ieeexplore.ieee.org/document/8091139/>. <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 -
 End of changes. 28 change blocks. 
46 lines changed or deleted 42 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/