[Dots] RFC 9387 on Use Cases for DDoS Open Threat Signaling (DOTS) Telemetry
rfc-editor@rfc-editor.org Fri, 21 April 2023 04:06 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 2BC11C151B26; Thu, 20 Apr 2023 21:06:41 -0700 (PDT)
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=ham 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 p7HLtSlfoTM6; Thu, 20 Apr 2023 21:06:36 -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 E8258C151B00; Thu, 20 Apr 2023 21:06:36 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id C37FF56692; Thu, 20 Apr 2023 21:06:36 -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: <20230421040636.C37FF56692@rfcpa.amsl.com>
Date: Thu, 20 Apr 2023 21:06:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/MCp1IKZ5NPr5W3E0iwdXELiOlb4>
Subject: [Dots] RFC 9387 on Use Cases for DDoS 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: Fri, 21 Apr 2023 04:06:41 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9387 Title: Use Cases for DDoS Open Threat Signaling (DOTS) Telemetry Author: Y. Hayashi, M. Chen, L. Su Status: Informational Stream: IETF Date: April 2023 Mailbox: yuuhei.hayashi@gmail.com, chenmeiling@chinamobile.com, suli@chinamobile.com Pages: 26 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dots-telemetry-use-cases-16.txt URL: https://www.rfc-editor.org/info/rfc9387 DOI: 10.17487/RFC9387 DDoS Open Threat Signaling (DOTS) telemetry enriches the base DOTS protocols to assist the mitigator in using efficient DDoS attack mitigation techniques in a network. This document presents sample use cases for DOTS telemetry. It discusses what components are deployed in the network, how they cooperate, and what information is exchanged to effectively use these techniques. This document is a product of the DDoS Open Threat Signaling Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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