RFC 8903 on Use Cases for DDoS Open Threat Signaling
rfc-editor@rfc-editor.org Thu, 27 May 2021 21:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B1773A13D0; Thu, 27 May 2021 14:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6ecnq337npd; Thu, 27 May 2021 14:34:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6959B3A13D5; Thu, 27 May 2021 14:34:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 69ABCF40719; Thu, 27 May 2021 14:34:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8903 on Use Cases for DDoS Open Threat Signaling
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210527213431.69ABCF40719@rfc-editor.org>
Date: Thu, 27 May 2021 14:34:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/I1tBhBaY8HynJVD1_nSZSIfW_cA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2021 21:34:50 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8903 Title: Use Cases for DDoS Open Threat Signaling Author: R. Dobbins, D. Migault, R. Moskowitz, N. Teague, L. Xia, K. Nishizuka Status: Informational Stream: IETF Date: May 2021 Mailbox: roland.dobbins@netscout.com, daniel.migault@ericsson.com, rgm@labs.htt-consult.com, nteague@ironmountain.co.uk, frank.xialiang@huawei.com, kaname@nttv6.jp Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dots-use-cases-25.txt URL: https://www.rfc-editor.org/info/rfc8903 DOI: 10.17487/RFC8903 The DDoS Open Threat Signaling (DOTS) effort is intended to provide protocols to facilitate interoperability across disparate DDoS Mitigation solutions. This document presents sample use cases that describe the interactions expected between the DOTS components as well as DOTS messaging exchanges. These use cases are meant to identify the interacting DOTS components, how they collaborate, and what the typical information to be exchanged is. 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