[Dots] RFC 9362 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission
rfc-editor@rfc-editor.org Wed, 01 March 2023 07:09 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C823C14CE5E; Tue, 28 Feb 2023 23:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oe4afHpGdneO; Tue, 28 Feb 2023 23:09:44 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E053C14CE4E; Tue, 28 Feb 2023 23:09:44 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 4F23117748A9; Tue, 28 Feb 2023 23:09:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dots@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230301070944.4F23117748A9@rfcpa.amsl.com>
Date: Tue, 28 Feb 2023 23:09:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/C2mjxlGsKCZkWXOayctSgXdQRKc>
Subject: [Dots] RFC 9362 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Configuration Attributes for Robust Block Transmission
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2023 07:09:49 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9362
Title: Distributed Denial-of-Service Open Threat Signaling
(DOTS) Signal Channel Configuration Attributes for
Robust Block Transmission
Author: M. Boucadair,
J. Shallow
Status: Standards Track
Stream: IETF
Date: February 2023
Mailbox: mohamed.boucadair@orange.com,
supjps-ietf@jpshallow.com
Pages: 21
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dots-robust-blocks-06.txt
URL: https://www.rfc-editor.org/info/rfc9362
DOI: 10.17487/RFC9362
This document specifies new DDoS Open Threat Signaling (DOTS) signal
channel configuration parameters that can be negotiated between DOTS
peers to enable the use of Q-Block1 and Q-Block2 Constrained
Application Protocol (CoAP) options. These options enable robust and
faster transmission rates for large amounts of data with less packet
interchanges as well as support for faster recovery should any of the
blocks get lost in transmission (especially during DDoS attacks).
Also, this document defines a YANG data model for representing these
new DOTS signal channel configuration parameters. This model augments
the DOTS signal YANG module ("ietf-dots-signal-channel") defined in
RFC 9132.
This document is a product of the DDoS Open Threat Signaling Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC