--- 1/draft-ietf-detnet-ip-over-tsn-04.txt 2020-12-14 00:14:00.430641922 -0800 +++ 2/draft-ietf-detnet-ip-over-tsn-05.txt 2020-12-14 00:14:00.458642638 -0800 @@ -1,22 +1,22 @@ DetNet B. Varga, Ed. Internet-Draft J. Farkas Intended status: Informational Ericsson -Expires: May 6, 2021 A. Malis +Expires: June 16, 2021 A. Malis Malis Consulting S. Bryant Futurewei Technologies - November 2, 2020 + December 13, 2020 DetNet Data Plane: IP over IEEE 802.1 Time Sensitive Networking (TSN) - draft-ietf-detnet-ip-over-tsn-04 + draft-ietf-detnet-ip-over-tsn-05 Abstract This document specifies the Deterministic Networking IP data plane when operating over a TSN sub-network. This document does not define new procedures or processes. Whenever this document makes requirements statements or recommendations, these are taken from normative text in the referenced RFCs. Status of This Memo @@ -27,21 +27,21 @@ 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 May 6, 2021. + This Internet-Draft will expire on June 16, 2021. Copyright Notice Copyright (c) 2020 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 @@ -50,59 +50,58 @@ 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Terms Used In This Document . . . . . . . . . . . . . . . 3 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 - 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 3 3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 3 4. DetNet IP Flows over an IEEE 802.1 TSN sub-network . . . . 4 4.1. Functions for DetNet Flow to TSN Stream Mapping . . . . . 5 4.2. TSN requirements of IP DetNet nodes . . . . . . . . . . . 6 - 4.3. Service protection within the TSN sub-network . . . . . . 8 - 4.4. Aggregation during DetNet flow to TSN Stream mapping . . 8 + 4.3. Service protection within the TSN sub-network . . . . . . 7 + 4.4. Aggregation during DetNet flow to TSN Stream mapping . . 7 5. Management and Control Implications . . . . . . . . . . . . . 8 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9.1. Normative references . . . . . . . . . . . . . . . . . . 10 - 9.2. Informative references . . . . . . . . . . . . . . . . . 11 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 + 9.2. Informative references . . . . . . . . . . . . . . . . . 10 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction Deterministic Networking (DetNet) is a service that can be offered by a network to DetNet flows. DetNet provides these flows extremely low packet loss rates and assured maximum end-to-end delivery latency. General background and concepts of DetNet can be found in the DetNet Architecture [RFC8655]. - [I-D.ietf-detnet-ip] specifies the DetNet data plane operation for IP - hosts and routers that provide DetNet service to IP encapsulated - data. This document focuses on the scenario where DetNet IP nodes - are interconnected by a TSN sub-network. + [RFC8939] specifies the DetNet data plane operation for IP hosts and + routers that provide DetNet service to IP encapsulated data. This + document focuses on the scenario where DetNet IP nodes are + interconnected by a TSN sub-network. The DetNet Architecture decomposes the DetNet related data plane functions into two sub-layers: a service sub-layer and a forwarding sub-layer. The service sub-layer is used to provide DetNet service protection and reordering. The forwarding sub-layer is used to provides congestion protection (low loss, assured latency, and - limited reordering). As described in [I-D.ietf-detnet-ip] no DetNet - specific headers are added to support DetNet IP flows, only the - forwarding sub-layer functions are supported inside the DetNet - domain. Service protection can be provided on a per sub-network - basis as shown here for the IEEE802.1 TSN sub-network scenario. + limited reordering). As described in [RFC8939] no DetNet specific + headers are added to support DetNet IP flows, only the forwarding + sub-layer functions are supported inside the DetNet domain. Service + protection can be provided on a per sub-network basis as shown here + for the IEEE802.1 TSN sub-network scenario. 2. Terminology 2.1. Terms Used In This Document This document uses the terminology and concepts established in the DetNet architecture [RFC8655], and the reader is assumed to be familiar with that document and its terminology. 2.2. Abbreviations @@ -118,36 +117,27 @@ L2 Layer-2. L3 Layer-3. PREOF Packet Replication, Ordering and Elimination Function. TSN Time-Sensitive Networking, TSN is a Task Group of the IEEE 802.1 Working Group. -2.3. 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 IP Data Plane Overview - [I-D.ietf-detnet-ip] describes how IP is used by DetNet nodes, i.e., - hosts and routers, to identify DetNet flows and provide a DetNet - service. From a data plane perspective, an end-to-end IP model is - followed. DetNet uses "6-tuple" based flow identification, where - "6-tuple" refers to information carried in IP and higher layer - protocol headers. + [RFC8939] describes how IP is used by DetNet nodes, i.e., hosts and + routers, to identify DetNet flows and provide a DetNet service. From + a data plane perspective, an end-to-end IP model is followed. DetNet + uses "6-tuple" based flow identification, where "6-tuple" refers to + information carried in IP and higher layer protocol headers. DetNet flow aggregation may be enabled via the use of wildcards, masks, prefixes and ranges. IP tunnels may also be used to support flow aggregation. In these cases, it is expected that DetNet aware intermediate nodes will provide DetNet service assurance on the aggregate through resource allocation and congestion control mechanisms. Congestion protection, latency control and the resource allocation (queuing, policing, shaping) are supported using the underlying link @@ -339,33 +329,33 @@ DetNet flow and TSN Stream mapping related information are required only for TSN-aware IP (DetNet) nodes. From the Data Plane perspective there is no practical difference based on the origin of flow mapping related information (management plane or control plane). The following summarizes the set of information that is needed to configure DetNet IP over TSN: o DetNet IP related configuration information according to the - DetNet role of the DetNet IP node, as per [I-D.ietf-detnet-ip]. + DetNet role of the DetNet IP node, as per [RFC8939]. o TSN related configuration information according to the TSN role of the DetNet IP node, as per [IEEE8021Q], [IEEE8021CB] and [IEEEP8021CBdb]. o Mapping between DetNet IP flow(s) (as flow identification defined - in [I-D.ietf-detnet-ip], it is summarized in Section 5.1 of that - document, and includes all wildcards, port ranges and the ability - to ignore specific IP fields) and TSN Stream(s) (as stream - identification information defined in [IEEE8021CB] and - [IEEEP8021CBdb]). Note, that managed objects for TSN Stream - identification can be found in [IEEEP8021CBcv]. + in [RFC8939], it is summarized in Section 5.1 of that document, + and includes all wildcards, port ranges and the ability to ignore + specific IP fields) and TSN Stream(s) (as stream identification + information defined in [IEEE8021CB] and [IEEEP8021CBdb]). Note, + that managed objects for TSN Stream identification can be found in + [IEEEP8021CBcv]. This information must be provisioned per DetNet flow. Mappings between DetNet and TSN management and control planes are out of scope of the document. Some of the challanges are highligthed below. TSN-aware IP DetNet nodes are member of both the DetNet domain and the TSN sub-network. Within the TSN sub-network the TSN-aware IP (DetNet) node has a TSN-aware Talker/Listener role, so TSN specific @@ -411,23 +401,23 @@ Configuration of TSN specific functions (e.g., FRER) inside the TSN sub-network is a TSN domain specific decision and may not be visible in the DetNet domain. 6. Security Considerations Security considerations for DetNet are described in detail in [I-D.ietf-detnet-security]. General security considerations are described in [RFC8655]. DetNet IP data plane specific considerations - are summarized in [I-D.ietf-detnet-ip]. This section considers - exclusively security considerations which are specific to the DetNet - IP over TSN sub-network scenario. + are summarized in [RFC8939]. This section considers exclusively + security considerations which are specific to the DetNet IP over TSN + sub-network scenario. The sub-network between DetNet nodes needs to be subject to appropriate confidentiality. Additionally, knowledge of what DetNet/ TSN services are provided by a sub-network may supply information that can be used in a variety of security attacks. The ability to modify information exchanges between connected DetNet nodes may result in bogus operations. Therefore, it is important that the interface between DetNet nodes and TSN sub-network are subject to authorization, authentication, and encryption. @@ -443,42 +433,27 @@ 8. Acknowledgements The authors wish to thank Norman Finn, Lou Berger, Craig Gunther, Christophe Mangin and Jouni Korhonen for their various contributions to this work. 9. References 9.1. Normative references - [I-D.ietf-detnet-ip] - Varga, B., Farkas, J., Berger, L., Fedyk, D., and S. - Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-07 - (work in progress), July 2020. - - [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, - DOI 10.17487/RFC2119, March 1997, - . - - [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC - 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, - May 2017, . + [RFC8939] Varga, B., Ed., Farkas, J., Berger, L., Fedyk, D., and S. + Bryant, "Deterministic Networking (DetNet) Data Plane: + IP", RFC 8939, DOI 10.17487/RFC8939, November 2020, + . 9.2. Informative references - [I-D.ietf-detnet-flow-information-model] - Varga, B., Farkas, J., Cummings, R., Jiang, Y., and D. - Fedyk, "DetNet Flow Information Model", draft-ietf-detnet- - flow-information-model-11 (work in progress), October - 2020. - [I-D.ietf-detnet-security] Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic Networking (DetNet) Security Considerations", draft-ietf- detnet-security-12 (work in progress), October 2020. [IEEE802.1AE-2018] IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC Security (MACsec)", 2018, .