--- 1/draft-ietf-detnet-problem-statement-06.txt 2018-10-03 01:13:25.161898557 -0700 +++ 2/draft-ietf-detnet-problem-statement-07.txt 2018-10-03 01:13:25.185899137 -0700 @@ -1,19 +1,19 @@ -detnet N. Finn +DetNet N. Finn Internet-Draft Huawei Technologies Co. Ltd Intended status: Informational P. Thubert -Expires: January 17, 2019 Cisco - July 16, 2018 +Expires: April 6, 2019 Cisco + October 3, 2018 Deterministic Networking Problem Statement - draft-ietf-detnet-problem-statement-06 + draft-ietf-detnet-problem-statement-07 Abstract This paper documents the needs in various industries to establish multi-hop paths for characterized flows with deterministic properties. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -22,21 +22,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 January 17, 2019. + This Internet-Draft will expire on April 6, 2019. Copyright Notice Copyright (c) 2018 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 @@ -53,21 +53,21 @@ 3. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Supported topologies . . . . . . . . . . . . . . . . . . 6 3.2. Flow Characterization . . . . . . . . . . . . . . . . . . 6 3.3. Centralized Path Computation and Installation . . . . . . 6 3.4. Distributed Path Setup . . . . . . . . . . . . . . . . . 7 3.5. Duplicated data format . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 7. Informative References . . . . . . . . . . . . . . . . . . . 9 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction The Deterministic Networking Use Cases [I-D.ietf-detnet-use-cases] document illustrates that beyond the classical case of industrial automation and control systems (IACS), there are in fact multiple industries with strong and yet relatively similar needs for deterministic network services with latency guarantees and ultra-low packet loss. @@ -84,38 +84,40 @@ 2 control systems, whereas public infrastructures such as Electricity Automation require deterministic properties over the Wide Area. The realization is now coming that the convergence of IT and Operational Technology (OT) networks requires Layer-3, as well as Layer-2, capabilities. While the initial user base has focused almost entirely on Ethernet physical media and Ethernet-based bridging protocol (from several Standards Development Organizations), the need for Layer-3 expressed above, must not be confined to Ethernet and Ethernet-like media, and - while such media must be encompassed by any useful DetNet - architecture, cooperation between IETF and other SDOs must not be - limited to IEEE or IEEE 802. Furthermore, while the work completed - and ongoing in other SDOs, and in IEEE 802 in particular, provide an - obvious starting point for a DetNet architecture, we must not assume - that these other SDOs' work confines the space in which the DetNet - architecture progresses. + while such media must be encompassed by any useful Deterministic + Networking (DetNet) Architecture, cooperation between IETF and other + SDOs must not be limited to IEEE or IEEE 802. Furthermore, while the + work completed and ongoing in other SDOs, and in IEEE 802 in + particular, provide an obvious starting point for a DetNet + architecture, we must not assume that these other SDOs' work confines + the space in which the DetNet architecture progresses. The properties of deterministic networks will have specific requirements for the use of routed networks to support these applications and a new model must be proposed to integrate determinism in IT technology. The proposed model should enable a fully scheduled operation orchestrated by a central controller, and may support a more distributed operation with probably lesser capabilities. In any fashion, the model should not compromise the ability of a network to keep carrying the sorts of traffic that is already carried today in conjunction with new, more deterministic - flows. + flows. Forward note: The DetNet Architecture + [I-D.ietf-detnet-architecture] is the document produced by the DetNet + WG to describe that model. Once the abstract model is agreed upon, the IETF will need to specify the signaling elements to be used to establish a path and the tagging elements to be used identify the flows that are to be forwarded along that path. The IETF will also need to specify the necessary protocols, or protocol additions, based on relevant IETF technologies, to implement the selected model. As a result of this work, it will be possible to establish a multi- hop path over the IP or MPLS network, for a particular flow with @@ -137,27 +139,30 @@ The Internet is not the only digital network that has grown dramatically over the last 30-40 years. Video and audio entertainment, and control systems for machinery, manufacturing processes, and vehicles are also ubiquitous, and are now based almost entirely on digital technologies. Over the past 10 years, engineers in these fields have come to realize that significant advantages in both cost and in the ability to accelerate growth can be obtained by basing all of these disparate digital technologies on packet networks. - The goals of Deterministic Networking (DetNet) are to enable the - migration of applications with critical timing and reliability issues - that currently use special-purpose fieldbus technologies (HDMI, - CANbus, ProfiBus, etc... even RS-232!) to packet technologies in - general, and the Internet Protocol in particular, and to support both - these new applications, and existing packet network applications, - over the same physical network. + The goals of Deterministic Networking are to enable the migration of + applications with critical timing and reliability issues that + currently use special-purpose fieldbus technologies (HDMI, CANbus, + ProfiBus, etc... even RS-232!) to packet technologies in general, and + the Internet Protocol in particular, and to support both these new + applications, and existing packet network applications, over the same + physical network. In other words, a Deterministic Network is + backwards compatible with - capable of transporting - statistically + multiplexed traffic while preserving the properties of the accepted + deterministic flows. Considerable experience ([ODVA]/[EIP],[AVnu], [Profinet],[HART],[IEC62439], [ISA100.11a] and [WirelessHART], etc...) has shown that these applications need a some or all of a suite of features that includes: 1. Time synchronization of all host and network nodes (routers and/ or bridges), accurate to something between 10 nanoseconds and 10 microseconds, depending on the application. @@ -184,21 +189,23 @@ transmission schedule, or by a maximum bandwidth and packet size; 3. Multiple methods to schedule, shape, limit, and otherwise control the transmission of critical packets at each hop through the network data plane; 4. Robust defenses against misbehaving hosts, routers, or bridges, both in the data and control planes, with guarantees that a critical flow within its guaranteed resources cannot be affected - by other flows whatever the pressures on the network; + by other flows whatever the pressures on the network - more on + the specific threats against DetNet in the DetNet Security + Considerations [I-D.ietf-detnet-security] document; 5. One or more methods to reserve resources in bridges and routers to carry these flows. Time synchronization techniques need not be addressed by an IETF Working Group; there are a number of standards available for this purpose, including IEEE 1588, IEEE 802.1AS, and more. The multicast, latency, loss ratio, and non-throttling needs are made necessary by the algorithms employed by the applications. They are @@ -371,36 +379,40 @@ other flows at other times. The overall security of a deterministic system must cover: o the protection of the signaling protocol o the authentication and authorization of the controlling nodes including plug-and-play participating end systems. o the identification and shaping of the flows + o the isolation of flows from leakage and other influences from any activity sharing physical resources. + The specific threats against DetNet are further discussed in the + DetNet Security Considerations [I-D.ietf-detnet-security] document. + 5. IANA Considerations This document does not require an action from IANA. 6. Acknowledgments The authors wish to thank Lou Berger, Stewart Bryant, Janos Farkas, - Andrew Malis, Jouni Korhonen, Erik Nordmark, George Swallow, Rudy - Klecka, Anca Zamfir, David Black, Thomas Watteyne, Shitanshu Shah, - Kiran Makhijani, Craig Gunther, Rodney Cummings, Wilfried Steiner, - Marcel Kiessling, Karl Weber, Ethan Grossman, Patrick Wetterwald, - Subha Dhesikan, Rudy Klecka and Pat Thaler for their various - contributions to this work. + Andrew Malis, Jouni Korhonen, Erik Nordmark, George Swallow, Lou + Berger, Ines Robles, Shwetha Bhandari, Rudy Klecka, Anca Zamfir, + David Black, Thomas Watteyne, Shitanshu Shah, Kiran Makhijani, Craig + Gunther, Rodney Cummings, Wilfried Steiner, Marcel Kiessling, Karl + Weber, Ethan Grossman, Patrick Wetterwald, Subha Dhesikan, Rudy + Klecka and Pat Thaler for their various contributions to this work. 7. Informative References [AVnu] http://www.avnu.org/, "The AVnu Alliance tests and certifies devices for interoperability, providing a simple and reliable networking solution for AV network implementation based on the IEEE Audio Video Bridging (AVB) and Time-Sensitive Networking (TSN) standards.". [EIP] http://www.odva.org/, "EtherNet/IP provides users with the @@ -409,23 +421,35 @@ automation applications while enabling Internet and enterprise connectivity data anytime, anywhere.", . [HART] www.hartcomm.org, "Highway Addressable Remote Transducer, a group of specifications for industrial process and control devices administered by the HART Foundation". + [I-D.ietf-detnet-architecture] + Finn, N., Thubert, P., Varga, B., and J. Farkas, + "Deterministic Networking Architecture", draft-ietf- + detnet-architecture-08 (work in progress), September 2018. + + [I-D.ietf-detnet-security] + Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, + J., Austad, H., Stanton, K., and N. Finn, "Deterministic + Networking (DetNet) Security Considerations", draft-ietf- + detnet-security-02 (work in progress), April 2018. + [I-D.ietf-detnet-use-cases] Grossman, E., "Deterministic Networking Use Cases", draft- - ietf-detnet-use-cases-17 (work in progress), June 2018. + ietf-detnet-use-cases-18 (work in progress), September + 2018. [IEC62439] IEC, "Industrial communication networks - High availability automation networks - Part 3: Parallel Redundancy Protocol (PRP) and High-availability Seamless Redundancy (HSR) - IEC62439-3", 2012, . [IEEE802.1TSNTG] IEEE Standards Association, "IEEE 802.1 Time-Sensitive