Skip to main content

Liaison statement
Liaison from detnet to ITU-T-SG-13 Question 6

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2025-02-07
From Group detnet
From Contact John Scudder
To Group ITU-T-SG-13
To Contacts tatiana.kurakova@itu.int
Cc Deterministic Networking Discussion List <detnet@ietf.org>
Lou Berger <lberger@labn.net>
Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Scott Mansfield <Scott.Mansfield@Ericsson.com>
John Scudder <jgs@juniper.net>
János Farkas <janos.farkas@ericsson.com>
Jim Guichard <james.n.guichard@futurewei.com>
Response Contact Lou Berger <lberger@labn.net>
János Farkas <janos.farkas@ericsson.com>
Purpose For action
Deadline 2025-03-31 Action Needed
Attachments (None)
Liaisons referred by this one LS on request for feedback on work items related to deterministic networking in SG13
Body
Body:

The Internet Engineering Task Force (IETF) Deterministic Networking (DetNet)
Working Group would like to thank ITU-T Study Group 13 for the information
provided in liaison statement https://datatracker.ietf.org/liaison/1951/ "LS on
request for feedback on work items related to deterministic networking in SG13".

The DetNet Working Group focuses on deterministic data paths that operate over
Layer 2 bridged and Layer 3 routed segments, where such paths can provide
bounds on reordering, latency, loss, packet delay variation (jitter), and high
reliability. DetNet solutions apply to both wireless and wired networks. The
Working Group addresses Layer 3 aspects in support of applications requiring
deterministic networking. The Working Group collaborates with other IETF
Working Groups and the IEEE 802.1 Time-Sensitive Networking (TSN) Task Group,
which is responsible for Layer 2 operations, to define a common architecture
for both Layer 2 and Layer 3. The Working Group currently focuses on solutions
for networks that are under a single administrative control or within a closed
group of administrative control; these include not only campus-wide networks
but also private WANs. The Working Group is responsible for the overall DetNet
architecture and DetNet-specific specifications that encompass the data plane,
OAM (Operations, Administration, and Maintenance), time synchronization,
management, control, and security aspects which are required to enable a
multi-hop path, and forwarding along the path, with the deterministic
properties of controlled latency, low packet loss, low packet delay variation,
and high reliability. The work applies to point-to-point (unicast) and
point-to-multipoint (multicast) flows, which can be characterized in a manner
that allows the network to 1) reserve the appropriate resources for the flows
in advance and 2) release/reuse the resources when they are no longer required.
The work covers the characterization of flows, the encapsulation of frames, the
required forwarding behaviors, as well as the state that may need to be
established in intermediate nodes. The work also includes detailing the
requirements for deterministic networks in various industries.

For more information on the Working Group and standards that have been
published see:https://datatracker.ietf.org/wg/detnet/about/.

The following is a list of documents that the Working Group is actively working
on via the standard IETF process (RFC 2026):

  * draft-ietf-detnet-controller-plane-framework: "Deterministic Networking
  (DetNet) Controller Plane Framework" * draft-ietf-raw-technologies: "Reliable
  and Available Wireless Technologies" * draft-ietf-raw-architecture: "Reliable
  and Available Wireless Architecture" *
  draft-ietf-detnet-scaling-requirements: "Requirements for Scaling
  Deterministic Networks" * draft-ietf-detnet-dataplane-taxonomy: "Dataplane
  Enhancement Taxonomy"
Other documents from individual contributors are under consideration, but have
not yet been accepted as Working Group documents. A list of those documents can
be found at: https://datatracker.ietf.org/wg/detnet/documents/

As a reminder, the IETF is a contribution-driven organization, with a formal
process defined in RFC 2026 and RFC 8789. Additionally, IETF Working Group
process is defined in RFC 2418. Notably, IETF positions require community rough
consensus with input from Working Groups via process managed by the Internet
Engineering Steering Group (IESG). Without a community consensus process, there
is no agreement or concurrence on any topic raised with or to the IETF. This
includes Liaison Statements.

In our understanding, the scope of ITU-T Y.Det-qos-intwk-wan "Requirements and
framework of deterministic QoS interworking mechanism in wide area network
including IMT-2020 and beyond" includes functional requirements and framework
for deterministic QoS interworking mechanism in wide area network limited to
fixed networks such as backbone network or metropolitan area network within a
single provider. This scope is within the charter of the DetNet Working Group.

We invite contributions from members of your group to our efforts in the
development of DetNet. If gaps are perceived in meeting requirements, we
encourage contributions related to those aspects to the DetNet Working Group.
For example, the DetNet Working Group is currently working on a requirements
document: draft-ietf-detnet-scaling-requirements: "Requirements for Scaling
Deterministic Networks". If your requirements are not covered in this document,
then we invite you to contribute your requirements to this document of the
DetNet Working Group. There is an opportunity to discuss any feedback at IETF
122 (15-21 March) or IETF 123 (19-25 July). Note, as well, that IETF working
groups conduct discussions on their mailing lists year-round, so any
contribution can be provided there as soon as it is ready.