RFC 8783 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
rfc-editor@rfc-editor.org Sun, 31 May 2020 06:14 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 39BE93A1277; Sat, 30 May 2020 23:14:05 -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 SUAmWOGV5rpH; Sat, 30 May 2020 23:14:03 -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 9CB003A1263; Sat, 30 May 2020 23:14:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 475A0F40739; Sat, 30 May 2020 23:13:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8783 on Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
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: <20200531061348.475A0F40739@rfc-editor.org>
Date: Sat, 30 May 2020 23:13:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/m9Y7WOQwj6aKsgHlCNL7fczLvMU>
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: Sun, 31 May 2020 06:14:07 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8783
Title: Distributed Denial-of-Service Open Threat Signaling
(DOTS) Data Channel Specification
Author: M. Boucadair, Ed.,
T. Reddy.K, Ed.
Status: Standards Track
Stream: IETF
Date: May 2020
Mailbox: mohamed.boucadair@orange.com,
kondtir@gmail.com
Pages: 66
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dots-data-channel-31.txt
URL: https://www.rfc-editor.org/info/rfc8783
DOI: 10.17487/RFC8783
The document specifies a Distributed Denial-of-Service Open Threat
Signaling (DOTS) data channel used for bulk exchange of data that
cannot easily or appropriately communicated through the DOTS signal
channel under attack conditions.
This is a companion document to "Distributed Denial-of-Service Open
Threat Signaling (DOTS) Signal Channel Specification" (RFC 8782).
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