Deterministic Networking Architecture
draft-ietf-detnet-architecture-01
DetNet N. Finn
Internet-Draft Huawei Technologies Co. Ltd
Intended status: Standards Track P. Thubert
Expires: September 14, 2017 Cisco
B. Varga
J. Farkas
Ericsson
March 13, 2017
Deterministic Networking Architecture
draft-ietf-detnet-architecture-01
Abstract
Deterministic Networking (DetNet) provides a capability to carry
specified unicast or multicast data flows for real-time applications
with 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
(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
network topology; and 3) distributing data from DetNet flow packets
over time and/or space to ensure delivery of each packet's data' in
spite of the loss of a path. The capabilities can be managed by
configuration, or by manual or automatic network management.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 http://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 September 14, 2017.
Finn, et al. Expires September 14, 2017 [Page 1]
Internet-Draft Deterministic Networking Architecture March 2017
Copyright Notice
Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Terms used in this document . . . . . . . . . . . . . . . 4
2.2. IEEE 802 TSN to DetNet dictionary . . . . . . . . . . . . 6
3. Providing the DetNet Quality of Service . . . . . . . . . . . 6
3.1. Congestion protection . . . . . . . . . . . . . . . . . . 8
3.2. Explicit routes . . . . . . . . . . . . . . . . . . . . . 9
3.3. Jitter Reduction . . . . . . . . . . . . . . . . . . . . 10
3.4. Packet Replication and Elimination . . . . . . . . . . . 10
3.5. Packet encoding for service protection . . . . . . . . . 12
4. DetNet Architecture . . . . . . . . . . . . . . . . . . . . . 12
4.1. DetNet systems . . . . . . . . . . . . . . . . . . . . . 12
4.1.1. Network reference model . . . . . . . . . . . . . . . 13
4.1.2. End system . . . . . . . . . . . . . . . . . . . . . 14
4.2. Traffic Engineering for DetNet . . . . . . . . . . . . . 15
4.2.1. The Application Plane . . . . . . . . . . . . . . . . 16
4.2.2. The Controller Plane . . . . . . . . . . . . . . . . 16
4.2.3. The Network Plane . . . . . . . . . . . . . . . . . . 17
4.3. DetNet flows . . . . . . . . . . . . . . . . . . . . . . 18
4.3.1. DetNet flow types . . . . . . . . . . . . . . . . . . 18
4.3.2. Source guarantees . . . . . . . . . . . . . . . . . . 19
4.3.3. Incomplete Networks . . . . . . . . . . . . . . . . . 20
4.4. Queuing, Shaping, Scheduling, and Preemption . . . . . . 20
4.5. Service instance . . . . . . . . . . . . . . . . . . . . 21
4.6. Coexistence with normal traffic . . . . . . . . . . . . . 22
Show full document text