Internet DRAFT - draft-xiong-detnet-data-fields-edp
draft-xiong-detnet-data-fields-edp
DETNET Q. Xiong
Internet-Draft A. Liu
Intended status: Standards Track ZTE Corporation
Expires: 11 January 2024 R. Gandhi
Cisco Systems, Inc.
D. Yang
Beijing Jiaotong University
10 July 2023
Data Fields for DetNet Enhanced Data Plane
draft-xiong-detnet-data-fields-edp-01
Abstract
This document discusses the specific metadata which should be carried
in Enhanced Data plane (EDP), proposes the DetNet data fields and
option types for EDP such as Deterministic Latency Action Option.
DetNet Data-Fields for EDP can be encapsulated into a variety of
protocols such as MPLS, IPv6 and SRv6 networks.
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 https://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 11 January 2024.
Copyright Notice
Copyright (c) 2023 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 (https://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
Xiong, et al. Expires 11 January 2024 [Page 1]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. Specific Metadata for DetNet Enhanced Data Plane . . . . . . 3
3.1. Queuing-based Metadata . . . . . . . . . . . . . . . . . 3
3.2. Traffic class Metadata . . . . . . . . . . . . . . . . . 4
4. Data Fields for DetNet Enhanced Data Plane . . . . . . . . . 4
4.1. DetNet Option-Types and Data-Fields . . . . . . . . . . . 5
4.2. DetNet Deterministic Latency Action Option . . . . . . . 5
4.2.1. DetNet DLA Option Header . . . . . . . . . . . . . . 5
4.2.1.1. DetNet DLA Behaviour Type . . . . . . . . . . . . 6
4.2.1.2. DetNet DLA Queuing Type . . . . . . . . . . . . . 7
4.2.2. DetNet DLA Option Data . . . . . . . . . . . . . . . 8
4.2.2.1. Cycle Queuing Data . . . . . . . . . . . . . . . 9
4.2.2.2. Deadline Queuing Data . . . . . . . . . . . . . . 9
4.2.2.3. Local Deadline Queuing Data . . . . . . . . . . . 10
4.2.2.4. Timeslot Queuing Data . . . . . . . . . . . . . . 10
5. Encapsulation Considerations for DetNet Enhanced Data
Plane . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1. Metadata for DetNet Enhanced Data Plane . . . . . . . . . 11
5.2. Encoding for DetNet Enhanced Data Plane . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
9. Normative References . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
According to [RFC8655], Deterministic Networking (DetNet) operates at
the IP layer and delivers service which provides extremely low data
loss rates and bounded latency within a network domain. DetNet data
planes has been specified in [RFC8938]. The existing deterministic
technologies are facing large-scale number of nodes and long-distance
transmission, traffic scheduling, dynamic flows, and other
controversial issues in large-scale networks. The DetNet Enhanced
Data plane (EDP) is required to support a data plane method of flow
identification and packet treatment.
[I-D.ietf-detnet-scaling-requirements]has described the enhancement
requirements for DetNet enhanced data plane, such as aggregated flow
identification, redundancy, explicit path selection and deterministic
Xiong, et al. Expires 11 January 2024 [Page 2]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
latency guarantees. [I-D.xiong-detnet-large-scale-enhancements] has
proposed the overall framework of DetNet enhancements for large-scale
deterministic networks. The packet treatment should schedule the
resources and indicate the behaviour to ensure the deterministic
latency. Moreover, new functions and related metadata should be
supported in enhanced DetNet.
This document discusses the specific metadata which should be carried
in Enhanced Data plane (EDP), proposes the DetNet data fields and
option types for EDP such as Deterministic Latency Action Option.
DetNet Data-Fields for EDP can be encapsulated into a variety of
protocols such as MPLS, IPv6 and SRv6 networks.
2. Conventions used in this document
2.1. Terminology
The terminology is defined as [RFC8655], [RFC8938] and
[I-D.ietf-detnet-scaling-requirements].
2.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Abbreviations and definitions used in this document:
EDP: Enhanced Data plane
SRH: Segment Routing Header
SRv6: Segment Routing for IPv6 forwarding plane
DLA: Deterministic Latency Action
3. Specific Metadata for DetNet Enhanced Data Plane
3.1. Queuing-based Metadata
As per [I-D.xiong-detnet-large-scale-enhancements], the queuing-based
mechanisms is an important type of resource to ensure the
deterministic latency. As described in [RFC9320], the end-to-end
bounded latency depends on the value of queuing delay bound along
with the queuing mechanisms. Multiple queuing mechanisms can be used
to guarantee the bounded latency in DetNet.
Xiong, et al. Expires 11 January 2024 [Page 3]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
And many types of queuing mechanisms have been proposed to provide
diversified deterministic service for various applications. For
example, time-scheduling queuing mechanisms includes the TAS (Time
Aware Shaping) [IIEEE802.1Qbv] and priority-scheduling includes the
CBS (Credit-Based Shaper)[IEEE802.1Q-2014] with ATS (Asynchronous
Traffic Shaping)[IEEE802.1Qcr]. The cyclic-scheduling queuing
mechanism has been proposed such as CQF (Cyclic Queuing and
Forwarding) in [IEEE802.1Qch] and improved as per multi-CQF
[I-D.dang-queuing-with-multiple-cyclic-buffers], T-CQF
[I-D.eckert-detnet-tcqf] and CSQF
[I-D.chen-detnet-sr-based-bounded-latency]. The deadline-scheduling
queuing mechanism has been proposed in [I-D.stein-srtsn] and improved
as per Deadline [I-D.peng-detnet-deadline-based-forwarding]. The
per-flow queuing mechanism includes Guaranteed-Service Integrated
service (IntServ) [RFC2212]. The asynchronous queuing mechanism
includes the Asynchronous Deterministic Networking (ADN) as per
[I-D.joung-detnet-asynch-detnet-framework] and
[I-D.joung-detnet-stateless-fair-queuing]. The Packet Timeslot
Mechanism is also proposed as per TQF
[I-D.peng-detnet-packet-timeslot-mechanism]. The functions such as
the queuing mechanisms should be provided for enhanced DetNet to
ensure the deterministic latency.
And when queuing mechanisms used in large-scale networks, some
queuing parameters should be carried for coordination between nodes
so as to make appropriate packet forwarding and scheduling decisions
to meet the time bounds. The DetNet forwarding nodes along the path
can apply the function and the deterministic latency related
information should be carried as metadata in the packet to achieve
the end-to-end bounded latency.
3.2. Traffic class Metadata
As per [I-D.xiong-detnet-large-scale-enhancements], DetNet service
sub-layer may provide traffic scheduling for multiple DetNet flows to
achieve the end-to-end bounded latency with differentiated DetNet
QoS. The enhanced DetNet data plane may also encode the traffic
class metadata in packets.
The DetNet Traffic Class (DC) has been defined to indicate the DetNet
traffic class as per [I-D.xiong-detnet-teas-te-extensions], The
traffic class information can also reuse the IP DSCP or MPLS TC
field.
4. Data Fields for DetNet Enhanced Data Plane
Xiong, et al. Expires 11 January 2024 [Page 4]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
4.1. DetNet Option-Types and Data-Fields
The enhanced functions and related metadata for DetNet EDP should be
confirmed before the encapsulations. While more than one metadata
should be carried in EDP, the common DetNet header for EDP should be
considered to cover all option-types and data.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DetNet-Type | DetNet-Length | RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| |
~ DetNet Option and Data Space ~
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: DetNet Header for EDP
DetNet-Type: 8-bit unsigned integer, defining the DetNet Option-type
for EDP. This document defines an Option:
Deterministic Latency Action Option as defined in section 4.2.
DetNet-Length: 8-bit unsigned integer, defined the Length of the
DetNet Header for EDP in 4-octet units.
4.2. DetNet Deterministic Latency Action Option
The DetNet Deterministic Latency Action (DLA) Option carries data
that is added by the DetNet encapsulating node and interpreted by the
decapsulating node. The DetNet transit nodes MAY process the data by
forwarding the option data determined by option type and may modify
it. The DetNet DLA Option consist of a fixed-size "DetNet DLA Option
Header" and a variable-size "DetNet DLA Option Data". The Header and
Data may be encapsulated continuously or separately. A Data or more
than one Data in lists can be carried in packets.
4.2.1. DetNet DLA Option Header
DetNet Deterministic Latency Action (DLA) Option header:
Xiong, et al. Expires 11 January 2024 [Page 5]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLA Type | Data Len | Ancillary Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: DLA Option header
DLA(Deterministic Latency Action) Type(16 bits): indicates the type
of deterministic latency actions for DetNet metadata.
The DLA Type can be divided into two parts including behaviour action
type and function/queuing type. The format is 16 bits such as
0xFFFF.
The DLA Type field is designed as follow:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLA B-type | DLA Q-type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: DLA Type
4.2.1.1. DetNet DLA Behaviour Type
DLA B-type(8 bits): indicates the behaviour action type of packet
treatment ensuring the deterministic latency as following shown.
This type can also indicate the traffic class.
Xiong, et al. Expires 11 January 2024 [Page 6]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Behaviour Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0000 | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0100 | Bandwidth guarantee |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0200 | Jitter guarantee |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0300 | Delay guarantee |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0400 | Low delay and jitter guarantee |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0500 |Ultra-low delay and jitter guarantee |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Behaviour Type (B-type)
4.2.1.2. DetNet DLA Queuing Type
DLA Q-type(8 bits): indicates the type of queuing-based mechanisms or
functions ensuring the deterministic latency and related metadata.
For example, the functions such as a particular queuing mechanism may
be indicated and related parameters should be provided as section
3.1.2 shown.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Sub-type| Queuing/Function Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0000 | Unassigned |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0001 | Cycle Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0002 | Deadline Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0003 | Local Deadline Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0x0004 | Time Slot Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Xiong, et al. Expires 11 January 2024 [Page 7]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
Figure 5: Queuing/Function Action Sub-type
Data Len: 8-bit unsigned integer. Length of DLA option data, in
octets.
Ancillary Len: 8-bit unsigned integer. Length of DLA ancillary data,
in octets.
The types of Deterministic Latency functions should cover all the
mechanisms ensuring the Deterministic Latency such as the existing
queuing and scheduling mechanisms and other mechanisms which may be
proposed in the future.
4.2.2. DetNet DLA Option Data
DetNet Deterministic Latency Action option data MUST be aligned by 4
octets:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLA option data field determined by DLA Q-Type (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLA ancillary data field determined by DLA Type (variable)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: DLA Option Data Field
DLA option data: Variable-length field. It provides function-based
or queuing-based information for a node to forward a DetNet flow.
The data of which is determined by the DLA Q-type. The examples of
different types of queuing-based data is as following sections shown.
DLA ancillary data: Variable-length field. It provides additional
information for a node to forward a DetNet flow. The data of which
is determined by the DLA type.
The DetNet option data and Ancillary data can be provided one time or
in list.
Xiong, et al. Expires 11 January 2024 [Page 8]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
4.2.2.1. Cycle Queuing Data
When the Sub-type is set to 0x0001, indicates the Multiple Cyclic
Queuing mechanism as defined in
[I-D.dang-queuing-with-multiple-cyclic-buffers] and
[I-D.chen-detnet-sr-based-bounded-latency]. The Cycle Queuing Data
may be carried and designed as following shown:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cycle Profile ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cycle ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Cycle Queuing Data
Cycle Profile ID (32bits): indicates the profile ID which the cyclic
queue applied at a node.
Cycle ID (32bits): indicates the Cycle ID for a node to forward a
DetNet flow.
4.2.2.2. Deadline Queuing Data
When the Sub-type is set to 0x0002, indicates the deadline mechanisms
as defined in [I-D.peng-detnet-deadline-based-forwarding]. The
Deadline Queuing Data may be carried and designed as follow:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags |M|D| Planned Deadline |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Accumulated Planned Deadline / Accumulated Deadline Deviation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Accumulated Actual Residence Time / Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Xiong, et al. Expires 11 January 2024 [Page 9]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
Figure 8: Deadline Queuing Data
Planned and deadline Deviation has been provided as defined in
[I-D.peng-6man-deadline-option].
4.2.2.3. Local Deadline Queuing Data
When the Sub-type is set to 0x0003, indicates the local deadline
mechanisms as defined in [I-D.stein-srtsn]. The Local Deadline
Queuing Data may be carried and designed as follow:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Deadline |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 9: Local Deadline Queuing Data
Local Deadline: indicates the local deadline as defined in
[I-D.stein-srtsn].
4.2.2.4. Timeslot Queuing Data
When the Sub-type is set to 0x0004, indicates the local deadline
mechanisms as defined in [I-D.peng-detnet-packet-timeslot-mechanism].
The time-slot information may be carried and designed as follow:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timeslot ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 10: Timeslot Queuing Data
Timeslot ID: indicates the identifier of the timeslot as defined in
[I-D.peng-detnet-packet-timeslot-mechanism].
5. Encapsulation Considerations for DetNet Enhanced Data Plane
Xiong, et al. Expires 11 January 2024 [Page 10]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
5.1. Metadata for DetNet Enhanced Data Plane
The packet treatment should indicate the behaviour action ensuring
the deterministic latency at DetNet nodes such as queuing-based
mechanisms. The deterministic latency action type and related
parameters such as queuing-based information should be carried as
metadta in data plane. And the definitions may follow these polices.
The data plane enhancement must be generic and the format must be
applied to all functions and queuing mechanisms. The metadata and
definitions should be common among different candidate queuing
solutions.
Information and metadata MUST be simplified and limited to be carried
in DetNet packets for provided deterministic latency related
scheduling along the forwarding path. For example, the queuing-based
information should be carried in metadata for coordination between
nodes.
The requirement of the flow or service may be not suitable to be
carried explicitly in DetNet data plane. The packet treatment should
schedule the resources and indicate the behaviour to ensure the
deterministic latency in forwarding sub-layer. So the queuing
mechanisms could be viewed as a type of deterministic resources. The
resources type and queuing type should be explicitly indicated.
5.2. Encoding for DetNet Enhanced Data Plane
Reusing the DSCP or existing field is reasonable and simple to define
and easy to standardize. For example, in IPv4 and traditional MPLS
networks, it is not suitable to carry new metadata and it is
suggested to reuse the original bits such as DSCP
[I-D.eckert-detnet-tcqf]. The mapping from DSCP and the metadata
such as queuing information MUST be provided in the controller plane.
DSCP value may be not sufficient and hard to distinguish between the
original DiffServ service and the deterministic service. The DetNet-
specific metadata can also be encoded as a common data fields and the
definition of data fields is independent from the encapsulating
protocols. The data fields could be encapsulated into a variety of
protocols, such as MPLS 2.0 [I-D.sx-detnet-mpls-queue], IPv6
[I-D.xiong-detnet-6man-queuing-option], SRv6
[I-D.xiong-detnet-spring-srh-extensions] and so on.
6. Security Considerations
TBA
Xiong, et al. Expires 11 January 2024 [Page 11]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
7. IANA Considerations
TBA
8. Acknowledgements
TBA
9. Normative References
[I-D.chen-detnet-sr-based-bounded-latency]
Chen, M., Geng, X., Li, Z., Joung, J., and J. Ryoo,
"Segment Routing (SR) Based Bounded Latency", Work in
Progress, Internet-Draft, draft-chen-detnet-sr-based-
bounded-latency-03, 7 July 2023,
<https://datatracker.ietf.org/doc/html/draft-chen-detnet-
sr-based-bounded-latency-03>.
[I-D.dang-queuing-with-multiple-cyclic-buffers]
Liu, B. and J. Dang, "A Queuing Mechanism with Multiple
Cyclic Buffers", Work in Progress, Internet-Draft, draft-
dang-queuing-with-multiple-cyclic-buffers-00, 22 February
2021, <https://datatracker.ietf.org/doc/html/draft-dang-
queuing-with-multiple-cyclic-buffers-00>.
[I-D.eckert-detnet-tcqf]
Eckert, T. T., Li, Y., Bryant, S., Malis, A. G., Ryoo, J.,
Liu, P., Li, G., Ren, S., and F. Yang, "Deterministic
Networking (DetNet) Data Plane - Tagged Cyclic Queuing and
Forwarding (TCQF) for bounded latency with low jitter in
large scale DetNets", Work in Progress, Internet-Draft,
draft-eckert-detnet-tcqf-04, 7 July 2023,
<https://datatracker.ietf.org/doc/html/draft-eckert-
detnet-tcqf-04>.
[I-D.ietf-detnet-scaling-requirements]
Liu, P., Li, Y., Eckert, T. T., Xiong, Q., Ryoo, J.,
zhushiyin, and X. Geng, "Requirements for Scaling
Deterministic Networks", Work in Progress, Internet-Draft,
draft-ietf-detnet-scaling-requirements-03, 7 July 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-detnet-
scaling-requirements-03>.
Xiong, et al. Expires 11 January 2024 [Page 12]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
[I-D.joung-detnet-asynch-detnet-framework]
Joung, J., Ryoo, J., Cheung, T., Li, Y., and P. Liu,
"Asynchronous Deterministic Networking Framework for
Large-Scale Networks", Work in Progress, Internet-Draft,
draft-joung-detnet-asynch-detnet-framework-02, 26 March
2023, <https://datatracker.ietf.org/doc/html/draft-joung-
detnet-asynch-detnet-framework-02>.
[I-D.joung-detnet-stateless-fair-queuing]
Joung, J., Ryoo, J., Cheung, T., Li, Y., and P. Liu,
"Latency Guarantee with Stateless Fair Queuing", Work in
Progress, Internet-Draft, draft-joung-detnet-stateless-
fair-queuing-00, 24 June 2023,
<https://datatracker.ietf.org/doc/html/draft-joung-detnet-
stateless-fair-queuing-00>.
[I-D.peng-6man-deadline-option]
Peng, S., Tan, B., and P. Liu, "Deadline Option", Work in
Progress, Internet-Draft, draft-peng-6man-deadline-option-
01, 11 July 2022, <https://datatracker.ietf.org/doc/html/
draft-peng-6man-deadline-option-01>.
[I-D.peng-detnet-deadline-based-forwarding]
Peng, S., Du, Z., Basu, K., cheng, and D. Yang, "Deadline
Based Deterministic Forwarding", Work in Progress,
Internet-Draft, draft-peng-detnet-deadline-based-
forwarding-06, 7 July 2023,
<https://datatracker.ietf.org/doc/html/draft-peng-detnet-
deadline-based-forwarding-06>.
[I-D.peng-detnet-packet-timeslot-mechanism]
Peng, S., Liu, P., Basu, K., Liu, A., Yang, D., and G.
Peng, "Timeslot Queueing and Forwarding Mechanism", Work
in Progress, Internet-Draft, draft-peng-detnet-packet-
timeslot-mechanism-03, 5 July 2023,
<https://datatracker.ietf.org/doc/html/draft-peng-detnet-
packet-timeslot-mechanism-03>.
[I-D.stein-srtsn]
Stein, Y. J., "Segment Routed Time Sensitive Networking",
Work in Progress, Internet-Draft, draft-stein-srtsn-01, 29
August 2021, <https://datatracker.ietf.org/doc/html/draft-
stein-srtsn-01>.
Xiong, et al. Expires 11 January 2024 [Page 13]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
[I-D.sx-detnet-mpls-queue]
Song, X., Xiong, Q., and R. Gandhi, "MPLS Sub-Stack
Encapsulation for Deterministic Latency Action", Work in
Progress, Internet-Draft, draft-sx-detnet-mpls-queue-06,
26 April 2023, <https://datatracker.ietf.org/doc/html/
draft-sx-detnet-mpls-queue-06>.
[I-D.xiong-detnet-6man-queuing-option]
Xiong, Q. and J. Zhao, "IPv6 Option for DetNet Data
Fields", Work in Progress, Internet-Draft, draft-xiong-
detnet-6man-queuing-option-04, 10 March 2023,
<https://datatracker.ietf.org/doc/html/draft-xiong-detnet-
6man-queuing-option-04>.
[I-D.xiong-detnet-large-scale-enhancements]
Xiong, Q., Du, Z., Zhao, J., and D. Yang, "Enhanced DetNet
Data Plane (EDP) Framework for Scaling Deterministic
Networks", Work in Progress, Internet-Draft, draft-xiong-
detnet-large-scale-enhancements-02, 13 March 2023,
<https://datatracker.ietf.org/doc/html/draft-xiong-detnet-
large-scale-enhancements-02>.
[I-D.xiong-detnet-spring-srh-extensions]
Xiong, Q., Wu, H., and D. Yang, "Segment Routing Header
Extensions for DetNet Data Fields", Work in Progress,
Internet-Draft, draft-xiong-detnet-spring-srh-extensions-
00, 10 March 2023, <https://datatracker.ietf.org/doc/html/
draft-xiong-detnet-spring-srh-extensions-00>.
[I-D.xiong-detnet-teas-te-extensions]
Xiong, Q. and B. Tan, "Traffic Engineering Extensions for
Enhanced DetNet", Work in Progress, Internet-Draft, draft-
xiong-detnet-teas-te-extensions-00, 10 July 2023,
<https://datatracker.ietf.org/api/v1/doc/document/draft-
xiong-detnet-teas-te-extensions/>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC2212] Shenker, S., Partridge, C., and R. Guerin, "Specification
of Guaranteed Quality of Service", RFC 2212,
DOI 10.17487/RFC2212, September 1997,
<https://www.rfc-editor.org/info/rfc2212>.
Xiong, et al. Expires 11 January 2024 [Page 14]
Internet-Draft Data Fields for DetNet Enhanced Data Pla July 2023
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>.
[RFC8938] Varga, B., Ed., Farkas, J., Berger, L., Malis, A., and S.
Bryant, "Deterministic Networking (DetNet) Data Plane
Framework", RFC 8938, DOI 10.17487/RFC8938, November 2020,
<https://www.rfc-editor.org/info/rfc8938>.
[RFC9320] Finn, N., Le Boudec, J.-Y., Mohammadpour, E., Zhang, J.,
and B. Varga, "Deterministic Networking (DetNet) Bounded
Latency", RFC 9320, DOI 10.17487/RFC9320, November 2022,
<https://www.rfc-editor.org/info/rfc9320>.
Authors' Addresses
Quan Xiong
ZTE Corporation
No.6 Huashi Park Rd
Wuhan
Hubei, 430223
China
Email: xiong.quan@zte.com.cn
Aihua Liu
ZTE Corporation
China
Email: liu.aihua@zte.com.cn
Rakesh Gandhi
Cisco Systems, Inc.
Canada
Email: rgandhi@cisco.com
Dong Yang
Beijing Jiaotong University
Beijing
China
Email: dyang@bjtu.edu.cn
Xiong, et al. Expires 11 January 2024 [Page 15]
