draft-ietf-detnet-bounded-latency-05.txt   draft-ietf-detnet-bounded-latency-06.txt 
DetNet N. Finn DetNet N. Finn
Internet-Draft Huawei Technologies Co. Ltd Internet-Draft Huawei Technologies Co. Ltd
Intended status: Informational J-Y. Le Boudec Intended status: Informational J-Y. Le Boudec
Expires: October 17, 2021 E. Mohammadpour Expires: November 18, 2021 E. Mohammadpour
EPFL EPFL
J. Zhang J. Zhang
Huawei Technologies Co. Ltd Huawei Technologies Co. Ltd
B. Varga B. Varga
J. Farkas J. Farkas
Ericsson Ericsson
April 15, 2021 May 17, 2021
DetNet Bounded Latency DetNet Bounded Latency
draft-ietf-detnet-bounded-latency-05 draft-ietf-detnet-bounded-latency-06
Abstract Abstract
This document references specific queuing mechanisms, defined in This document references specific queuing mechanisms, defined in
other documents, that can be used to control packet transmission at other documents, that can be used to control packet transmission at
each output port and achieve the DetNet qualities of service. This each output port and achieve the DetNet qualities of service. This
document presents a timing model for sources, destinations, and the document presents a timing model for sources, destinations, and the
DetNet transit nodes that relay packets that is applicable to all of DetNet transit nodes that relay packets that is applicable to all of
those referenced queuing mechanisms. Using the model presented in those referenced queuing mechanisms. Using the model presented in
this document, it should be possible for an implementor, user, or this document, it should be possible for an implementor, user, or
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 October 17, 2021. This Internet-Draft will expire on November 18, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 16, line 26 skipping to change at page 16, line 26
In the considered queuing model, we considered the four traffic In the considered queuing model, we considered the four traffic
classes (Definition 3.268 of [IEEE8021Q]): control-data traffic classes (Definition 3.268 of [IEEE8021Q]): control-data traffic
(CDT), class A, class B, and best effort (BE) in decreasing order of (CDT), class A, class B, and best effort (BE) in decreasing order of
priority. Flows of classes A and B are together referred as AVB priority. Flows of classes A and B are together referred as AVB
flows. This model is a subset of Time-Sensitive Networking as flows. This model is a subset of Time-Sensitive Networking as
described next. described next.
Based on the timing model described in Figure 1, the contention Based on the timing model described in Figure 1, the contention
occurs only at the output port of a DetNet transit node; therefore, occurs only at the output port of a DetNet transit node; therefore,
the focus of the rest of this subsection is on the regulator and the focus of the rest of this subsection is on the regulator and
queuing subsystem in the output port of a DetNet transit node. Then, queuing subsystem in the output port of a DetNet transit node. The
the input flows are identified using the information in (Section 5.1 input flows are identified using the information in (Section 5.1 of
of [RFC8939]). Then they are aggregated into eight macro flows based [RFC8939]). Then they are aggregated into eight macro flows based on
on their DetNet flow aggregate. We refer to each macro flow as a their service requirements; we refer to each macro flow as a class.
class. The output port performs aggregate scheduling with eight The output port performs aggregate scheduling with eight queues
queues (queuing subsystems): one for CDT, one for class A flows, one (queuing subsystems): one for CDT, one for class A flows, one for
for class B flows, and five for BE traffic denoted as BE0-BE4. The class B flows, and five for BE traffic denoted as BE0-BE4. The
queuing policy for each queuing subsystem is FIFO. In addition, each queuing policy for each queuing subsystem is FIFO. In addition, each
node output port also performs per-flow regulation for AVB flows node output port also performs per-flow regulation for AVB flows
using an interleaved regulator (IR), called Asynchronous Traffic using an interleaved regulator (IR), called Asynchronous Traffic
Shaper [IEEE8021Qcr]. Thus, at each output port of a node, there is Shaper [IEEE8021Qcr]. Thus, at each output port of a node, there is
one interleaved regulator per-input port and per-class; the one interleaved regulator per-input port and per-class; the
interleaved regulator is mapped to the regulator depicted in interleaved regulator is mapped to the regulator depicted in
Figure 1. The detailed picture of scheduling and regulation Figure 1. The detailed picture of scheduling and regulation
architecture at a node output port is given by Figure 4. The packets architecture at a node output port is given by Figure 4. The packets
received at a node input port for a given class are enqueued in the received at a node input port for a given class are enqueued in the
respective interleaved regulator at the output port. Then, the respective interleaved regulator at the output port. Then, the
 End of changes. 5 change blocks. 
11 lines changed or deleted 11 lines changed or added

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