draft-ietf-detnet-architecture-07.txt   draft-ietf-detnet-architecture-08.txt 
DetNet N. Finn DetNet N. Finn
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track P. Thubert Intended status: Standards Track P. Thubert
Expires: February 4, 2019 Cisco Expires: March 16, 2019 Cisco
B. Varga B. Varga
J. Farkas J. Farkas
Ericsson Ericsson
August 3, 2018 September 12, 2018
Deterministic Networking Architecture Deterministic Networking Architecture
draft-ietf-detnet-architecture-07 draft-ietf-detnet-architecture-08
Abstract Abstract
Deterministic Networking (DetNet) provides a capability to carry This document provides the overall Architecture for Deterministic
specified unicast or multicast data flows for real-time applications Networking (DetNet), which provides a capability to carry specified
with extremely low data loss rates and bounded latency. Techniques unicast or multicast data flows for real-time applications with
used include: 1) reserving data plane resources for individual (or extremely low data loss rates and bounded latency. Techniques 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 immediately change with explicit routes for DetNet flows that do not immediately change with
the network topology; and 3) distributing data from DetNet flow the network topology; and 3) distributing data from DetNet flow
packets over time and/or space to ensure delivery of each packet's packets over time and/or space to ensure delivery of each packet's
data in spite of the loss of a path. data in spite of the loss of a path. DetNet operates at the IP layer
and delivers service over sub-network technologies such as MPLS and
IEEE 802.1 TSN.
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 February 4, 2019. This Internet-Draft will expire on March 16, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 2, line 20 skipping to change at page 2, line 25
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.1 TSN to DetNet dictionary . . . . . . . . . . . 6 2.2. IEEE 802.1 TSN to DetNet dictionary . . . . . . . . . . . 7
3. Providing the DetNet Quality of Service . . . . . . . . . . . 7 3. Providing the DetNet Quality of Service . . . . . . . . . . . 7
3.1. Primary goals defining the DetNet QoS . . . . . . . . . . 7 3.1. Primary goals defining the DetNet QoS . . . . . . . . . . 7
3.2. Mechanisms to achieve DetNet QoS . . . . . . . . . . . . 9 3.2. Mechanisms to achieve DetNet QoS . . . . . . . . . . . . 9
3.2.1. Congestion protection . . . . . . . . . . . . . . . . 9 3.2.1. Congestion protection . . . . . . . . . . . . . . . . 9
3.2.1.1. Eliminate congestion loss . . . . . . . . . . . . 9 3.2.1.1. Eliminate congestion loss . . . . . . . . . . . . 9
3.2.1.2. Jitter Reduction . . . . . . . . . . . . . . . . 10 3.2.1.2. Jitter Reduction . . . . . . . . . . . . . . . . 10
3.2.2. Service Protection . . . . . . . . . . . . . . . . . 11 3.2.2. Service Protection . . . . . . . . . . . . . . . . . 11
3.2.2.1. In-Order Delivery . . . . . . . . . . . . . . . . 11 3.2.2.1. In-Order Delivery . . . . . . . . . . . . . . . . 11
3.2.2.2. Packet Replication and Elimination . . . . . . . 11 3.2.2.2. Packet Replication and Elimination . . . . . . . 11
3.2.2.3. Packet encoding for service protection . . . . . 13 3.2.2.3. Packet encoding for service protection . . . . . 13
3.2.3. Explicit routes . . . . . . . . . . . . . . . . . . . 13 3.2.3. Explicit routes . . . . . . . . . . . . . . . . . . . 13
3.3. Secondary goals for DetNet . . . . . . . . . . . . . . . 14 3.3. Secondary goals for DetNet . . . . . . . . . . . . . . . 14
3.3.1. Coexistence with normal traffic . . . . . . . . . . . 14 3.3.1. Coexistence with normal traffic . . . . . . . . . . . 15
3.3.2. Fault Mitigation . . . . . . . . . . . . . . . . . . 15 3.3.2. Fault Mitigation . . . . . . . . . . . . . . . . . . 15
4. DetNet Architecture . . . . . . . . . . . . . . . . . . . . . 16 4. DetNet Architecture . . . . . . . . . . . . . . . . . . . . . 16
4.1. DetNet stack model . . . . . . . . . . . . . . . . . . . 16 4.1. DetNet stack model . . . . . . . . . . . . . . . . . . . 16
4.1.1. Representative Protocol Stack Model . . . . . . . . . 16 4.1.1. Representative Protocol Stack Model . . . . . . . . . 16
4.1.2. DetNet Data Plane Overview . . . . . . . . . . . . . 18 4.1.2. DetNet Data Plane Overview . . . . . . . . . . . . . 18
4.1.3. Network reference model . . . . . . . . . . . . . . . 20 4.1.3. Network reference model . . . . . . . . . . . . . . . 20
4.2. DetNet systems . . . . . . . . . . . . . . . . . . . . . 21 4.2. DetNet systems . . . . . . . . . . . . . . . . . . . . . 22
4.2.1. End system . . . . . . . . . . . . . . . . . . . . . 21 4.2.1. End system . . . . . . . . . . . . . . . . . . . . . 22
4.2.2. DetNet edge, relay, and transit nodes . . . . . . . . 22 4.2.2. DetNet edge, relay, and transit nodes . . . . . . . . 23
4.3. DetNet flows . . . . . . . . . . . . . . . . . . . . . . 23 4.3. DetNet flows . . . . . . . . . . . . . . . . . . . . . . 23
4.3.1. DetNet flow types . . . . . . . . . . . . . . . . . . 23 4.3.1. DetNet flow types . . . . . . . . . . . . . . . . . . 23
4.3.2. Source transmission behavior . . . . . . . . . . . . 23 4.3.2. Source transmission behavior . . . . . . . . . . . . 24
4.3.3. Incomplete Networks . . . . . . . . . . . . . . . . . 25 4.3.3. Incomplete Networks . . . . . . . . . . . . . . . . . 25
4.4. Traffic Engineering for DetNet . . . . . . . . . . . . . 25 4.4. Traffic Engineering for DetNet . . . . . . . . . . . . . 25
4.4.1. The Application Plane . . . . . . . . . . . . . . . . 25 4.4.1. The Application Plane . . . . . . . . . . . . . . . . 26
4.4.2. The Controller Plane . . . . . . . . . . . . . . . . 26 4.4.2. The Controller Plane . . . . . . . . . . . . . . . . 26
4.4.3. The Network Plane . . . . . . . . . . . . . . . . . . 26 4.4.3. The Network Plane . . . . . . . . . . . . . . . . . . 27
4.5. Queuing, Shaping, Scheduling, and Preemption . . . . . . 27 4.5. Queuing, Shaping, Scheduling, and Preemption . . . . . . 28
4.6. Service instance . . . . . . . . . . . . . . . . . . . . 28 4.6. Service instance . . . . . . . . . . . . . . . . . . . . 29
4.7. Flow identification at technology borders . . . . . . . . 30 4.7. Flow identification at technology borders . . . . . . . . 30
4.7.1. Exporting flow identification . . . . . . . . . . . . 30 4.7.1. Exporting flow identification . . . . . . . . . . . . 30
4.7.2. Flow attribute mapping between layers . . . . . . . . 31 4.7.2. Flow attribute mapping between layers . . . . . . . . 32
4.7.3. Flow-ID mapping examples . . . . . . . . . . . . . . 32 4.7.3. Flow-ID mapping examples . . . . . . . . . . . . . . 33
4.8. Advertising resources, capabilities and adjacencies . . . 34 4.8. Advertising resources, capabilities and adjacencies . . . 35
4.9. Scaling to larger networks . . . . . . . . . . . . . . . 35 4.9. Scaling to larger networks . . . . . . . . . . . . . . . 35
4.10. Compatibility with Layer-2 . . . . . . . . . . . . . . . 35 4.10. Compatibility with Layer-2 . . . . . . . . . . . . . . . 35
5. Security Considerations . . . . . . . . . . . . . . . . . . . 35 5. Security Considerations . . . . . . . . . . . . . . . . . . . 36
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 36 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36
9. Informative References . . . . . . . . . . . . . . . . . . . 37 9. Informative References . . . . . . . . . . . . . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
Deterministic Networking (DetNet) is a service that can be offered by This document provides the overall Architecture for Deterministic
a network to DetNet flows. DetNet provides these flows with Networking (DetNet), which provides a capability for the delivery of
extremely low packet loss rates and assured maximum end-to-end data flows with extremely low packet loss rates and bounded end-to-
delivery latency. This is accomplished by dedicating network end delivery latency. DetNet operates at the IP layer and delivers
resources such as link bandwidth and buffer space to DetNet flows service over sub-network technologies such as MPLS and IEEE 802.1
and/or classes of DetNet flows, and by replicating packets along TSN. DetNet accomplishes these goals by dedicating network resources
multiple paths. Unused reserved resources are available to non- such as link bandwidth and buffer space to DetNet flows and/or
DetNet packets. classes of DetNet flows, and by replicating packets along multiple
paths. Unused reserved resources are available to non-DetNet
packets.
The Deterministic Networking Problem Statement The Deterministic Networking Problem Statement
[I-D.ietf-detnet-problem-statement] introduces Deterministic [I-D.ietf-detnet-problem-statement] introduces Deterministic
Networking, and Deterministic Networking Use Cases Networking, and Deterministic Networking Use Cases
[I-D.ietf-detnet-use-cases] summarizes the need for it. See [I-D.ietf-detnet-use-cases] summarizes the need for it. See
[I-D.ietf-detnet-dp-sol-mpls] and [I-D.ietf-detnet-dp-sol-ip] for [I-D.ietf-detnet-dp-sol-mpls] and [I-D.ietf-detnet-dp-sol-ip] for
specific techniques that can be used to identify DetNet flows and specific techniques that can be used to identify DetNet flows and
assign them to specific paths through a network. assign them to specific paths through a network.
A goal of DetNet is a converged network in all respects. That is, A goal of DetNet is a converged network in all respects. That is,
skipping to change at page 40, line 40 skipping to change at page 40, line 44
July 2018, <https://www.rfc-editor.org/info/rfc8402>. July 2018, <https://www.rfc-editor.org/info/rfc8402>.
[TEAS] IETF, "Traffic Engineering Architecture and Signaling [TEAS] IETF, "Traffic Engineering Architecture and Signaling
Working Group", Working Group",
<https://datatracker.ietf.org/doc/charter-ietf-teas/>. <https://datatracker.ietf.org/doc/charter-ietf-teas/>.
Authors' Addresses Authors' Addresses
Norman Finn Norman Finn
Huawei Huawei
3755 Avocado Blvd. 3101 Rio Way
PMB 436 Spring Valley, California 91977
La Mesa, California 91941
US US
Phone: +1 925 980 6430 Phone: +1 925 980 6430
Email: norman.finn@mail01.huawei.com Email: norman.finn@mail01.huawei.com
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
 End of changes. 16 change blocks. 
34 lines changed or deleted 38 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/