Reliable communication is central to industrial automation, where control systems and connected equipment depend on predictable network behavior. The relationship between TSN and DetNet was the focus of a joint workshop held on November 11, 2018, bringing together participants from the IEEE Time-Sensitive Networking (TSN) Task Group and the IETF Deterministic Networking (DetNet) Working Group. The agenda covered how the two efforts define and identify traffic flows, describe quality of service, coordinate control, and address applications such as industrial automation and power systems.
The workshop record documents presentations and discussion topics rather than adopted decisions or measured outcomes. Even so, its scope offers a useful view of the engineering questions involved when deterministic networking concepts cross standards and network environments.
Why TSN and DetNet were discussed together
TSN and DetNet are standards efforts concerned with deterministic communication. Their joint consideration matters to industrial network designers because a communication path may involve different network technologies, architectures, or administrative domains. For such a path to support an application’s requirements, the traffic and service expectations need to be understood consistently at the relevant points.
The workshop began with overviews of the IEEE 802.1 TSN Task Group and the IETF DetNet Working Group, followed by presentations on the basic concepts of each effort. This created a foundation for examining where the approaches relate, including how flows are represented and how service and QoS information might be mapped between them.
TSN and DetNet flow and QoS mapping
A recurring theme in the agenda was the definition and identification of flows. In a deterministic network, it is important to distinguish the traffic associated with a particular communication need so that the network can apply the intended treatment. The workshop included separate presentations on TSN stream identification and DetNet flow definition, identification, features, and mapping to and from TSN.
Participants also examined the relationship between flow information and quality of service (QoS). QoS parameters express how a network service is characterized for traffic, while flow identification helps associate that service with the relevant data. The agenda included a dedicated presentation on TSN and DetNet flow/QoS mapping, reflecting the need to consider both sides together rather than treating traffic identifiers and service expectations as unrelated configuration details.
For system integrators, this topic points to a practical design consideration: when a communication path spans technologies, the network design must account for how the traffic description and QoS expectations are carried or translated between segments. The workshop record identifies this as an area of technical attention; it does not specify a single mapping method or report a final solution.
Control, configuration, and management
Another major part of the workshop addressed how deterministic networks could be controlled and configured. Presentations covered IEEE 802.1 mechanisms and models, including MSRP, LRP, RAP, and YANG, alongside possible directions for the DetNet control plane and YANG-based control for DetNet.
These topics connect network requirements with operational configuration. In an industrial environment, engineers and operations teams need to understand how intended services are represented and how configuration relates to the network’s behavior. The workshop’s focus on control-plane possibilities and YANG-based approaches shows that the discussion extended beyond forwarding concepts to the management structures needed to express and coordinate network intent.
The agenda does not establish that the discussed approaches were finalized or interoperable at that time. Instead, it records that control and configuration were recognized as important areas for continued work across the two communities.
Security and application contexts
Security was explicitly included through a presentation on security considerations in DetNet and TSN. This is relevant to automation decision-makers because deterministic communication requirements do not remove the need to consider network security. The workshop record identifies security as a subject for examination, but does not provide specific recommendations or claim that a particular security design was endorsed.
Use cases helped ground the standards discussion. The agenda included a DetNet use-case overview, a presentation on the IEC/IEEE 60802 TSN profile for industrial automation, and a session on deterministic networking in power automation under IEC TR 61850-90-13. It also included discussion of TSN for service provider networks. Together, these topics show the breadth of contexts considered—from industrial and power systems to service provider networks—without suggesting that one profile or design applies universally.
What the workshop means for industrial network planning
For plant managers, controls engineers, and system integrators, the workshop’s value lies in the range of questions it brought into one discussion. When evaluating deterministic networking, teams should consider more than the network technology in isolation. The agenda highlights several connected concerns:
- Traffic definition: How are the relevant streams or flows identified?
- Service expectations: How are QoS parameters described and related across network segments?
- Configuration: How might control-plane and YANG-based approaches represent or manage network requirements?
- Application fit: Which profiles and use cases align with the requirements of the industrial or power system?
- Security: How are security considerations addressed alongside deterministic communication needs?
These are planning questions, not a checklist of solutions supplied by the workshop. The appropriate answers depend on the application and on the standards, profiles, and network elements involved.
Conclusion
The 2018 TSN–DetNet workshop brought IEEE and IETF participants together around the relationship between deterministic networking efforts. Its agenda covered flow identification, QoS mapping, control and configuration, security, and application profiles for industrial automation and power systems. For technical decision-makers, the practical takeaway is to treat deterministic networking as an end-to-end design and coordination challenge: define traffic and service expectations clearly, consider how they relate across network boundaries, and evaluate control, security, and application-specific requirements together.