[Dots] RFC 8782 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
rfc-editor@rfc-editor.org Sun, 31 May 2020 06:14 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 9510C3A1264; Sat, 30 May 2020 23:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 WOI4gxjD4fjU; Sat, 30 May 2020 23:13:58 -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 814333A1261; Sat, 30 May 2020 23:13:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2C772F4071C; Sat, 30 May 2020 23:13:43 -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: <20200531061343.2C772F4071C@rfc-editor.org>
Date: Sat, 30 May 2020 23:13:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/NG94r6tJl_4Epc0Z5quL1TOrFr8>
Subject: [Dots] RFC 8782 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
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: Sun, 31 May 2020 06:14:02 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8782 Title: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification Author: T. Reddy.K, Ed., M. Boucadair, Ed., P. Patil, A. Mortensen, N. Teague Status: Standards Track Stream: IETF Date: May 2020 Mailbox: kondtir@gmail.com, mohamed.boucadair@orange.com, praspati@cisco.com, andrew@moretension.com, nteague@ironmountain.co.uk Pages: 100 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dots-signal-channel-41.txt URL: https://www.rfc-editor.org/info/rfc8782 DOI: 10.17487/RFC8782 This document specifies the Distributed Denial-of-Service Open Threat Signaling (DOTS) signal channel, a protocol for signaling the need for protection against Distributed Denial-of-Service (DDoS) attacks to a server capable of enabling network traffic mitigation on behalf of the requesting client. A companion document defines the DOTS data channel, a separate reliable communication layer for DOTS management and configuration purposes. 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