[Dots] RFC 9244 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
rfc-editor@rfc-editor.org Mon, 20 June 2022 17:49 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 10784C14F75F; Mon, 20 Jun 2022 10:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 XLqZmy6fsEbZ; Mon, 20 Jun 2022 10:49:29 -0700 (PDT)
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 6ED87C14F612; Mon, 20 Jun 2022 10:49:29 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0D005AEA1; Mon, 20 Jun 2022 10:49:28 -0700 (PDT)
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: <20220620174929.0D005AEA1@rfcpa.amsl.com>
Date: Mon, 20 Jun 2022 10:49:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/eDV2Lc07iBAEiI6qIp_1B6KGU3U>
Subject: [Dots] RFC 9244 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
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: Mon, 20 Jun 2022 17:49:33 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9244 Title: Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry Author: M. Boucadair, Ed., T. Reddy.K, Ed., E. Doron, M. Chen, J. Shallow Status: Standards Track Stream: IETF Date: June 2022 Mailbox: mohamed.boucadair@orange.com, kondtir@gmail.com, ehudd@radware.com, chenmeiling@chinamobile.com, supjps-ietf@jpshallow.com Pages: 108 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dots-telemetry-25.txt URL: https://www.rfc-editor.org/info/rfc9244 DOI: 10.17487/RFC9244 This document aims to enrich the Distributed Denial-of-Service Open Threat Signaling (DOTS) signal channel protocol with various telemetry attributes, allowing for optimal Distributed Denial-of-Service (DDoS) attack mitigation. It specifies the normal traffic baseline and attack traffic telemetry attributes a DOTS client can convey to its DOTS server in the mitigation request, the mitigation status telemetry attributes a DOTS server can communicate to a DOTS client, and the mitigation efficacy telemetry attributes a DOTS client can communicate to a DOTS server. The telemetry attributes can assist the mitigator in choosing the DDoS mitigation techniques and performing optimal DDoS attack mitigation. This document specifies two YANG modules: one for representing DOTS telemetry message types and one for sharing the attack mapping details over the DOTS data channel. 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