draft-finn-detnet-architecture-07.txt   draft-finn-detnet-architecture-08.txt 
DetNet N. Finn DetNet N. Finn
Internet-Draft P. Thubert Internet-Draft P. Thubert
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: January 26, 2017 M. Johas Teener Expires: February 19, 2017 August 18, 2016
Broadcom
July 25, 2016
Deterministic Networking Architecture Deterministic Networking Architecture
draft-finn-detnet-architecture-07 draft-finn-detnet-architecture-08
Abstract Abstract
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 data loss rates and bounded latency. Techniques with extremely low data loss rates and bounded latency. Techniques
used include: 1) reserving data plane resources for individual (or used include: 1) reserving data plane resources for individual (or
aggregated) DetNet flows in some or all of the intermediate nodes aggregated) DetNet flows in some or all of the intermediate nodes
(e.g. bridges or routers) along the path of the flow; 2) providing (e.g. bridges or routers) along the path of the flow; 2) providing
explicit routes for DetNet flows that do not rapidly change with the explicit routes for DetNet flows that do not rapidly change with the
skipping to change at page 1, line 42 skipping to change at page 1, line 40
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 January 26, 2017. This Internet-Draft will expire on February 19, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 20 skipping to change at page 2, line 16
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Terms used in this document . . . . . . . . . . . . . . . 4 2.1. Terms used in this document . . . . . . . . . . . . . . . 4
2.2. IEEE 802 TSN to DetNet dictionary . . . . . . . . . . . . 6 2.2. IEEE 802 TSN to DetNet dictionary . . . . . . . . . . . . 5
3. Providing the DetNet Quality of Service . . . . . . . . . . . 6 3. Providing the DetNet Quality of Service . . . . . . . . . . . 6
3.1. Congestion protection . . . . . . . . . . . . . . . . . . 8 3.1. Congestion protection . . . . . . . . . . . . . . . . . . 8
3.2. Explicit routes . . . . . . . . . . . . . . . . . . . . . 9 3.2. Explicit routes . . . . . . . . . . . . . . . . . . . . . 8
3.3. Jitter Reduction . . . . . . . . . . . . . . . . . . . . 9 3.3. Jitter Reduction . . . . . . . . . . . . . . . . . . . . 9
3.4. Packet Replication and Elimination . . . . . . . . . . . 10 3.4. Packet Replication and Elimination . . . . . . . . . . . 10
3.5. Packet encoding for service protection . . . . . . . . . 12 3.5. Packet encoding for service protection . . . . . . . . . 11
4. DetNet Architecture . . . . . . . . . . . . . . . . . . . . . 12 4. DetNet Architecture . . . . . . . . . . . . . . . . . . . . . 12
4.1. Traffic Engineering for DetNet . . . . . . . . . . . . . 12 4.1. Traffic Engineering for DetNet . . . . . . . . . . . . . 12
4.1.1. The Application Plane . . . . . . . . . . . . . . . . 12 4.1.1. The Application Plane . . . . . . . . . . . . . . . . 12
4.1.2. The Controller Plane . . . . . . . . . . . . . . . . 13 4.1.2. The Controller Plane . . . . . . . . . . . . . . . . 13
4.1.3. The Network Plane . . . . . . . . . . . . . . . . . . 13 4.1.3. The Network Plane . . . . . . . . . . . . . . . . . . 13
4.2. DetNet flows . . . . . . . . . . . . . . . . . . . . . . 14 4.2. DetNet flows . . . . . . . . . . . . . . . . . . . . . . 14
4.2.1. Source guarantees . . . . . . . . . . . . . . . . . . 15 4.2.1. Source guarantees . . . . . . . . . . . . . . . . . . 14
4.2.2. Incomplete Networks . . . . . . . . . . . . . . . . . 16 4.2.2. Incomplete Networks . . . . . . . . . . . . . . . . . 16
4.3. Queuing, Shaping, Scheduling, and Preemption . . . . . . 16 4.3. Queuing, Shaping, Scheduling, and Preemption . . . . . . 16
4.4. Coexistence with normal traffic . . . . . . . . . . . . . 17 4.4. Coexistence with normal traffic . . . . . . . . . . . . . 17
4.5. Fault Mitigation . . . . . . . . . . . . . . . . . . . . 17 4.5. Fault Mitigation . . . . . . . . . . . . . . . . . . . . 17
4.6. Representative Protocol Stack Model . . . . . . . . . . . 18 4.6. Representative Protocol Stack Model . . . . . . . . . . . 18
4.7. Exporting flow identification . . . . . . . . . . . . . . 20 4.7. Exporting flow identification . . . . . . . . . . . . . . 20
4.8. Advertising resources, capabilities and adjacencies . . . 22 4.8. Advertising resources, capabilities and adjacencies . . . 22
4.9. Provisioning model . . . . . . . . . . . . . . . . . . . 22 4.9. Provisioning model . . . . . . . . . . . . . . . . . . . 22
4.9.1. Centralized Path Computation and Installation . . . . 22 4.9.1. Centralized Path Computation and Installation . . . . 22
4.9.2. Distributed Path Setup . . . . . . . . . . . . . . . 23 4.9.2. Distributed Path Setup . . . . . . . . . . . . . . . 22
4.10. Scaling to larger networks . . . . . . . . . . . . . . . 23 4.10. Scaling to larger networks . . . . . . . . . . . . . . . 23
4.11. Connected islands vs. networks . . . . . . . . . . . . . 23 4.11. Connected islands vs. networks . . . . . . . . . . . . . 23
5. Compatibility with Layer-2 . . . . . . . . . . . . . . . . . 24 5. Compatibility with Layer-2 . . . . . . . . . . . . . . . . . 23
6. Open Questions . . . . . . . . . . . . . . . . . . . . . . . 24 6. Open Questions . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. Flat vs. hierarchical control . . . . . . . . . . . . . . 24 6.1. Flat vs. hierarchical control . . . . . . . . . . . . . . 24
6.2. Peer-to-peer reservation protocol . . . . . . . . . . . . 25 6.2. Peer-to-peer reservation protocol . . . . . . . . . . . . 24
6.3. Wireless media interactions . . . . . . . . . . . . . . . 25 6.3. Wireless media interactions . . . . . . . . . . . . . . . 25
7. Security Considerations . . . . . . . . . . . . . . . . . . . 25 7. Security Considerations . . . . . . . . . . . . . . . . . . . 25
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26
11. Access to IEEE 802.1 documents . . . . . . . . . . . . . . . 26 11. Access to IEEE 802.1 documents . . . . . . . . . . . . . . . 26
12. Informative References . . . . . . . . . . . . . . . . . . . 27 12. Informative References . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
Deterministic Networking (DetNet) is a service that can be offered by Deterministic Networking (DetNet) is a service that can be offered by
a network to DetNet flows. DetNet provides these flows extremely low a network to DetNet flows. DetNet provides these flows extremely low
packet loss rates and assured maximum end-to-end delivery latency. packet loss rates and assured maximum end-to-end delivery latency.
This is accomplished by dedicating network resources such as link This is accomplished by dedicating network resources such as link
bandwidth and buffer space to DetNet flows and/or classes of DetNet bandwidth and buffer space to DetNet flows and/or classes of DetNet
flows, and by replicating packets along multiple paths. Unused flows, and by replicating packets along multiple paths. Unused
reserved resources are available to non-DetNet packets. reserved resources are available to non-DetNet packets.
skipping to change at page 26, line 43 skipping to change at page 26, line 28
9. IANA Considerations 9. IANA Considerations
This document does not require an action from IANA. This document does not require an action from IANA.
10. Acknowledgements 10. Acknowledgements
The authors wish to thank Jouni Korhonen, Erik Nordmark, George The authors wish to thank Jouni Korhonen, Erik Nordmark, George
Swallow, Rudy Klecka, Anca Zamfir, David Black, Thomas Watteyne, Swallow, Rudy Klecka, Anca Zamfir, David Black, Thomas Watteyne,
Shitanshu Shah, Craig Gunther, Rodney Cummings, Balazs Varga, Shitanshu Shah, Craig Gunther, Rodney Cummings, Balazs Varga,
Wilfried Steiner, Marcel Kiessling, Karl Weber, Janos Farkas, Ethan Wilfried Steiner, Marcel Kiessling, Karl Weber, Janos Farkas, Ethan
Grossman, Pat Thaler, and Lou Berger for their various contribution Grossman, Pat Thaler, Lou Berger, and especially Michael Johas
with this work. Teener, for their various contribution with this work.
11. Access to IEEE 802.1 documents 11. Access to IEEE 802.1 documents
To access password protected IEEE 802.1 drafts, see the IETF IEEE To access password protected IEEE 802.1 drafts, see the IETF IEEE
802.1 information page at https://www.ietf.org/proceedings/52/slides/ 802.1 information page at https://www.ietf.org/proceedings/52/slides/
bridge-0/tsld003.htm. bridge-0/tsld003.htm.
12. Informative References 12. Informative References
[AVnu] http://www.avnu.org/, "The AVnu Alliance tests and [AVnu] http://www.avnu.org/, "The AVnu Alliance tests and
skipping to change at page 27, line 32 skipping to change at page 27, line 17
functions primarily as a protocol for creating media functions primarily as a protocol for creating media
redundancy while PRP, as described in the previous redundancy while PRP, as described in the previous
section, creates network redundancy. PRP and HSR are both section, creates network redundancy. PRP and HSR are both
described in the IEC 62439 3 standard.", described in the IEC 62439 3 standard.",
<http://webstore.iec.ch/webstore/webstore.nsf/ <http://webstore.iec.ch/webstore/webstore.nsf/
artnum/046615!opendocument>. artnum/046615!opendocument>.
[I-D.dt-detnet-dp-alt] [I-D.dt-detnet-dp-alt]
Korhonen, J., Farkas, J., Mirsky, G., Thubert, P., Korhonen, J., Farkas, J., Mirsky, G., Thubert, P.,
Zhuangyan, Z., and L. Berger, "DetNet Data Plane Protocol Zhuangyan, Z., and L. Berger, "DetNet Data Plane Protocol
and Solution Alternatives", draft-dt-detnet-dp-alt-01 and Solution Alternatives", draft-dt-detnet-dp-alt-03
(work in progress), July 2016. (work in progress), August 2016.
[I-D.ietf-6tisch-architecture] [I-D.ietf-6tisch-architecture]
Thubert, P., "An Architecture for IPv6 over the TSCH mode Thubert, P., "An Architecture for IPv6 over the TSCH mode
of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work
in progress), June 2016. in progress), June 2016.
[I-D.ietf-6tisch-tsch] [I-D.ietf-6tisch-tsch]
Watteyne, T., Palattella, M., and L. Grieco, "Using Watteyne, T., Palattella, M., and L. Grieco, "Using
IEEE802.15.4e TSCH in an IoT context: Overview, Problem IEEE802.15.4e TSCH in an IoT context: Overview, Problem
Statement and Goals", draft-ietf-6tisch-tsch-06 (work in Statement and Goals", draft-ietf-6tisch-tsch-06 (work in
skipping to change at page 32, line 31 skipping to change at line 1491
Pascal Thubert Pascal Thubert
Cisco Systems Cisco Systems
Village d'Entreprises Green Side Village d'Entreprises Green Side
400, Avenue de Roumanille 400, Avenue de Roumanille
Batiment T3 Batiment T3
Biot - Sophia Antipolis 06410 Biot - Sophia Antipolis 06410
FRANCE FRANCE
Phone: +33 4 97 23 26 34 Phone: +33 4 97 23 26 34
Email: pthubert@cisco.com Email: pthubert@cisco.com
Michael Johas Teener
Broadcom Corp.
3151 Zanker Rd.
San Jose, California 95134
USA
Phone: +1 831 824 4228
Email: MikeJT@broadcom.com
 End of changes. 14 change blocks. 
18 lines changed or deleted 16 lines changed or added

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