[Detnet] New Version Notification for draft-han-detnet-anomalous-packets-handling-02.txt
"韩政鑫(联通集团本部)" <hanzx21@chinaunicom.cn> Tue, 03 March 2026 09:43 UTC
Return-Path: <hanzx21@chinaunicom.cn>
X-Original-To: detnet@mail2.ietf.org
Delivered-To: detnet@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1F67EC3517AA for <detnet@mail2.ietf.org>; Tue, 3 Mar 2026 01:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SxNHDtzoSdq for <detnet@mail2.ietf.org>; Tue, 3 Mar 2026 01:43:25 -0800 (PST)
Received: from sendb.mailex.chinaunicom.cn (sendb.mailex.chinaunicom.cn [123.138.59.137]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 56748C3517A5 for <detnet@ietf.org>; Tue, 3 Mar 2026 01:43:23 -0800 (PST)
Received: from bg5.exmail.qq.com (unknown [10.172.147.156]) by sendb.mailex.chinaunicom.cn (SkyGuard) with ESMTPS id 4fQ9pX4zljzrgXlt for <detnet@ietf.org>; Tue, 3 Mar 2026 17:43:16 +0800 (CST)
X-QQ-mid: qylesmxpt1772530995thwaf8x4r
Received: from DESKTOP-3A9Q6SH ( [10.2.113.166]) by bizesmtp.qq.com (ESMTP) with SMTP id 0 for <detnet@ietf.org>; Tue, 03 Mar 2026 17:43:14 +0800 (CST)
X-QQ-SSF: 01000000000000B0P410000A0000000
X-QQ-FEAT: kSk7kcQy/atqzp+9EB4EQBlyZRd1FnJJ
X-QQ-GoodBg: 0
Date: Tue, 03 Mar 2026 17:43:15 +0800
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.528[cn]
Mime-Version: 1.0
Message-ID: <2026030317431530657745@chinaunicom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart676158008261_=----"
From: "韩政鑫(联通集团本部)" <hanzx21@chinaunicom.cn>
To: detnet <detnet@ietf.org>
X-QQ-SENDSIZE: 520
Feedback-ID: qylesmxpt:chinaunicom.cn:xx-kxq-mail-:xx-kxq-mail-0001.novalocal
Message-ID-Hash: EWUTXZSNLXFPG24R5LB4AQVMQTSEZWC2
X-Message-ID-Hash: EWUTXZSNLXFPG24R5LB4AQVMQTSEZWC2
X-MailFrom: hanzx21@chinaunicom.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-detnet.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Detnet] New Version Notification for draft-han-detnet-anomalous-packets-handling-02.txt
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/3TLJ0DubX7sknP1pomb8G4VmcNs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Owner: <mailto:detnet-owner@ietf.org>
List-Post: <mailto:detnet@ietf.org>
List-Subscribe: <mailto:detnet-join@ietf.org>
List-Unsubscribe: <mailto:detnet-leave@ietf.org>
Dear All, A new version of the draft-han-detnet-anomalous-packets-handling has been uploaded. It based on the comments from presentation in IETF124 and the progress of the DetNet WG. The link as follows: URL: https://www.ietf.org/archive/id/draft-han-detnet-anomalous-packets-handling-02.txt Diff: https://author-tools.ietf.org/iddiff?url2=draft-han-detnet-anomalous-packets-handling-02 The main updates in new version are as follows: 1. Clarifies that "anomalous" refers to temporary traffic deviations (e.g., microbursts) from reserved resources, framing them as normal operational behaviors rather than network faults. 2. Specifies the document's applicability by stating that the proposed squeezing and degrading policies can be applied to any DetNet queuing mechanism that meets certain criteria. Looking forward to your review and further comments. Cheers, Zhengxin Han