# 确定性网络——DetNet工作组介绍

#### 一、DetNet工作组介绍

##### 1.1 工作组章程

DetNet工作组英文全称是Deterministic Networking WG (detnet)，官方文档在https://datatracker.ietf.org/wg/detnet/about/中可见。

• 主要工作：工作组关注第3层网络，与负责第2层网络的IEEE802.1 TSN合作定义了共同的体系结构，提供有边界保障的延迟、丢失和抖动以及高可靠性。

• 适用应用：包括专业和家庭音频/视频，交通多媒体，发动机控制系统，和IEEE 802.1 TSN任务组正在考虑的其他通用工业和车辆应用。

• 网络范围：在单一行政管制下或在封闭的行政管制组内的网络，如校园网络，私人wan。

• 标准内容：

(1) 总体架构:该工作包括数据平面、OAM、时间同步、管理、控制和安全方面。

(2) 数据平面:这项工作将记录如何使用IP和/或MPLS，以及相关的OAM，以支持流识别的数据平面方法和第三层上的数据包转发。

(3) 控制面: “控制面和管理面的集合”，这项工作将记录如何使用IETF控制平面解决方案来支持DetNet。

(4) 数据流信息模型:这项工作将确定流建立和控制所需的信息，并被保留协议和YANG数据模型所使用。

(5) YANG models:这项工作将记录设备和链接能力(特性支持)和资源(例如缓冲区、带宽)，以便在设备配置和状态报告中使用。

Charter原文如下，（注：可用名词加粗，不太理解的斜体）

The Deterministic Networking (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 latency, loss, and packet delay variation (jitter), and high reliability. The Working Group addresses Layer 3 aspects in support of applications requiring deterministic networking. The Working Group collaborates with IEEE802.1 Time-Sensitive Networking (TSN), which is responsible for Layer 2 operations, to define a common architecture for both Layer 2 and Layer 3. Example applications for deterministic networks include professional and home audio/video, multimedia in transportation, engine control systems, and other general industrial and vehicular applications being considered by the IEEE 802.1 TSN Task Group. The Working Group will initially focus 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 can include private WANs. The DetNet WG will not spend energy on solutions for large groups of domains such as the Internet. The Working Group is responsible for the overall DetNet architecture and DetNet-specific specifications that encompasses 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. Layer 3 data plane technologies that can be used include: IP and MPLS, and Layer 2 encapsulations that run over IP and/or MPLS, such as pseudowires and GRE. The Working Group will document which deployment environments and types of topologies 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 Working Group will also document DetNet Controller Plane approaches that reuse existing IETF solutions, such as Path Computation Element (PCE), and identify the Working Group responsible for any extensions needed to support DetNet. Documents produced by the Working Group will be compatible with the work done in IEEE802.1 TSN and other IETF Working Groups. The Working Group’s scope explicitly excludes modifications of transport protocols, OAM, Layer 3 forwarding, and encapsulations, but it may discuss requirements for such modifications and the work will be done in the Working Group responsible for the technology. DetNet is chartered to work in the following areas: Overall architecture: This work encompasses the data plane, OAM, time synchronization, management, control, and security aspects. Data plane: This work will document how to use IP and/or MPLS, and related OAM, to support a data plane method of flow identification and packet forwarding over Layer 3. Other IETF defined data plane technologies may also be used. Controller Plane: The DetNet Controller Plane is defined in RFC 8655 as “the aggregation of the Control and Management Planes”. This work will document how to use IETF control plane solutions to support DetNet, including the identification of any gaps in existing solutions. Any modification to Controller Plane protocols to address identified gaps should be carried out in their associated Working Groups, but may be done in DetNet if agreed to by the relevant Working Group chairs and responsible Area Directors. Data flow information model: This work will identify the information needed for flow establishment and control and be used by reservation protocols and 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). YANG models: 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. Control plane related information will be independent from the protocol(s) which may be used to advertise this information (e.g. IS-IS or GMPLS extensions). Any new YANG models will be coordinated with the Working Groups that define any base models that are to be augmented. As needed,vertical requirements: This effort will detail the requirements for deterministic networks in various industries that have previously not been documented and cannot be supported using defined DetNet solutions. To investigate whether existing data plane encryption mechanisms can be applied, possibly opportunistically, to improve security and privacy. The Working Group coordinates with other relevant IETF Working Groups, including CCAMP, IPPM, LSR, PCE, PALS, TEAS, TSVWG, RAW, and 6TiSCH. 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 and related solutions. The WG will liaise with appropriate groups in IEEE and other Standards Development Organizations (SDOs).

确定性网络(DetNet)工作组主要关注在第2层桥接和第3层路由段上运行的确定性数据路径，在这些路径中，这些路径可以

DetNet工作组不会把精力花在解决Internet等大型领域的解决方案上。

DetNet被授权从事以下领域的工作:总体架构:该工作包括数据平面、OAM、时间同步、管理、控制和安全方面。

YANG models:这项工作将记录设备和链接能力(特性支持)和资源(例如缓冲区、带宽)，以便在设备配置和状态报告中使用。

#### 二、DetNet技术文档

• draft-du-detnet-layer3-low-latency-00：一种降低三层网络中低延迟流量微突发的方法。https://tools.ietf.org/id/draft-du-detnet-layer3-low-latency-00.txt
• draft-geng-detnet-dp-sol-srv6-02：此文档为SRv6封装的用户数据指定了确定性网络数据平面操作。https://tools.ietf.org/id/draft-geng-detnet-dp-sol-srv6-02.txt
• draft-malis-detnet-controller-plane-framework-04：本文档提供了确定性网络(DetNet)控制器平面的框架概述。它讨论将作为Detnet控制器平面解决方案文档基础的概念和需求。https://tools.ietf.org/id/draft-malis-detnet-controller-plane-framework-04.txt
• draft-mirsky-detnet-ip-oam-02：本文档定义了在具有IP数据平面的确定性网络中使用操作、管理和维护协议和机制的原则。https://tools.ietf.org/id/draft-mirsky-detnet-ip-oam-02.txt
• draft-mirsky-detnet-mpls-oam-01：本文档定义了在具有IP数据平面的确定性网络中使用操作、管理和维护协议和机制的原则。本文档列出了确定性网络(DetNet)中操作、管理和维护(OAM)工具集的功能需求，并使用这些需求;定义在DetNet网络上与MPLS数据平面相关联的通道的格式和使用DetNet服务的主体。https://tools.ietf.org/id/draft-mirsky-detnet-mpls-oam-01.txt
• draft-xiong-detnet-qos-policy-02：本文档提出了一个服务质量(QoS)策略来应用确定性网络(DetNet)的差异化服务(DiffServ)模型，并定义了一个DetNet差异化服务机制，包括DetNet IP和MPLS封装。
• draft-ietf-detnet-topology-yang-00：本文档定义了用于确定性网络(DetNet)拓扑发现和能力配置的YANG数据模型。本文档中定义的YANG模块符合网络管理数据存储体系结构(NMDA)。
12-22

06-11 1万+
05-14 1万+
12-16 1万+
11-20 4万+
03-26 4599
04-19 2688
03-02 5172