[Dots] RFC 9133 on Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel

rfc-editor@rfc-editor.org Thu, 02 September 2021 22:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 DFBB63A167C; Thu, 2 Sep 2021 15:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, 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 IoBcZgZEVcbK; Thu, 2 Sep 2021 15:56:33 -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 947413A1673; Thu, 2 Sep 2021 15:56:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 54908F40767; Thu, 2 Sep 2021 15:56:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20210902225610.54908F40767@rfc-editor.org>
Date: Thu, 02 Sep 2021 15:56:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/xU3j0ph2toz8lmnIoMrnjbiLtv4>
Subject: [Dots] RFC 9133 on Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 02 Sep 2021 22:56:52 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9133

        Title:      Controlling Filtering Rules Using Distributed 
                    Denial-of-Service Open Threat Signaling (DOTS) Signal 
                    Channel 
        Author:     K. Nishizuka,
                    M. Boucadair,
                    T. Reddy.K,
                    T. Nagata
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2021 
        Mailbox:    kaname@nttv6.jp,
                    mohamed.boucadair@orange.com,
                    kondtir@gmail.com,
                    nagata@lepidum.co.jp
        Pages:      26
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dots-signal-filter-control-07.txt

        URL:        https://www.rfc-editor.org/info/rfc9133

        DOI:        10.17487/RFC9133

This document specifies an extension to the Distributed
Denial-of-Service Open Threat Signaling (DOTS) signal channel
protocol so that DOTS clients can control their filtering rules when
an attack mitigation is active.

Particularly, this extension allows a DOTS client to activate or
deactivate existing filtering rules during a Distributed
Denial-of-Service (DDoS) attack. The characterization of these
filtering rules is conveyed by a DOTS client during an 'idle' time
(i.e., no mitigation is active) by means of the DOTS data channel
protocol.

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