IETF-90 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Deterministic Networking (detnet) (WG)

Minutes   |   Jabber Logs  |   Mailing List Archives

Additional information is available at tools.ietf.org/wg/detnet

Chair(s):

Routing Area Area Director(s):

Assigned Area Director



Recordings:

No Recordings Present

Meeting Slides:

No Slides Present

No Current Internet-Drafts

No Request for Comments

Charter (as of 2015-08-28):

The Deterministic Networking (DetNet) Working Group will focus on
deterministic data paths that operate over Layer 2 Bridged and Layer 3
routed segments, where such paths can provide bounded latency, loss and
packet delay variation (jitter). The Working Group will address Layer 3
aspects in support of applications requiring deterministic networking.
The group will collaborate with IEEE802.1 TSN, which is responsible for
Layer 2 operations, to define a common architecture to support IEEE802.1
TSN applications. For the common architecture, a number of elements such
as the IEEE802.1 TSN host operation should be agnostic to the choice of
network used for the connectivity.

The Working Group will specify an overall architecture that encompasses
the data plane, OAM, management, control, and security aspects that are
required to enable a multi-hop path, and forwarding along that path,
with the deterministic properties of controlled latency, low packet
loss, low packet delay variation, and high reliability. The work will
apply to flows that 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 will cover 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; it will
not include end-to-end considerations such as transport protocols,
modification of OAM, L3 forwarding and encapsulations, or control plane
protocols. Candidate Layer 3 data plane technologies that may be used,
without modification, include: IPv4, IPv6, MPLS. As part of the overall
architecture work, the working group will document which deployment
environments and types of topologies that are within (or outside) the
scope of the DetNet architecture. This work focuses on the data plane
aspects and is independent from any path setup protocol or mechanism.
The data plane will be compatible with the work done in IEEE802.1 TSN.

DetNet is chartered to work in the following areas:

* Overall architecture: This work encompasses the data plane, OAM,
management, control, and security aspects.

* Data plane: This work will document a data plane method of flow
identification and packet forwarding over Layer 3.

* Data flow information model: This work will identify the information
needed for flow establishment and control and be used by a
reservation protocol or by YANG data models. The work will be
independent from the protocol(s) used to control the flows
(e.g. YANG+NETCONF/RESTCONF, PCEP or GMPLS).

* Identification of additional YANG augmentations: This work will
document device and link capabilities (feature support) and resources
(e.g. buffers, bandwidth) for use in device configuration and status
reporting. Such information may also be used when advertising the
deterministic network elements to a control plane. The work will be
independent from the protocol(s) that may be used to advertise this
information (e.g. IS-IS or GMPLS extensions). Any YANG work will be
coordinated with the working groups that define the base models.

* As needed, problem statement: This effort will establish the
deployment environment and deterministic network requirements.

* As needed, vertical requirements: This effort will detail the
requirements for deterministic networks in various industries, for
example, professional audio, electrical utilities, building
automation systems, wireless for industrial applications.

The WG will coordinate with other relevant IETF Working Groups,
including CCAMP, PCE, PALS, TEAS, OSPF, IS-IS, TSVWG, and 6TisSCH. As
the work progresses, requirements may be provided to the responsible
Working Group, e.g. PCE, TEAS, and CCAMP, with DetNet acting as a focal
point to maintain the consistency of the overall architecture. The WG
will liaise with appropriate groups in IEEE and other Standards
Development Organizations (SDOs).