[rfc-dist] RFC 8973 on DDoS Open Threat Signaling (DOTS) Agent Discovery
rfc-editor@rfc-editor.org Wed, 13 January 2021 06:51 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A2113A0C57 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 12 Jan 2021 22:51:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 xYI1lXo7MfSs for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 12 Jan 2021 22:51:08 -0800 (PST)
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 8BFB23A0C67 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 12 Jan 2021 22:51:08 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 23EDAF4073A; Tue, 12 Jan 2021 22:50:58 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id D00EBF40738; Tue, 12 Jan 2021 22:50:56 -0800 (PST)
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
Message-Id: <20210113065056.D00EBF40738@rfc-editor.org>
Date: Tue, 12 Jan 2021 22:50:56 -0800
Subject: [rfc-dist] RFC 8973 on DDoS Open Threat Signaling (DOTS) Agent Discovery
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dots@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8973
Title: DDoS Open Threat Signaling (DOTS)
Agent Discovery
Author: M. Boucadair,
T. Reddy.K
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: mohamed.boucadair@orange.com,
tirumaleswarreddy_konda@mcafee.com
Pages: 22
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dots-server-discovery-15.txt
URL: https://www.rfc-editor.org/info/rfc8973
DOI: 10.17487/RFC8973
This document specifies mechanisms to configure DDoS Open Threat
Signaling (DOTS) clients with their DOTS servers. The discovery
procedure also covers the DOTS signal channel Call Home. It can be
useful to know the appropriate DOTS server for a given location in
order to engage mitigation actions. This is true even in cases where
the DOTS client cannot localize the attack: cases where it only knows
that some resources are under attack and that help is needed.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org