RFC 9284 on Multihoming Deployment Considerations for DDoS Open Threat Signaling (DOTS)

rfc-editor@rfc-editor.org Wed, 31 August 2022 04:44 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 11A5BC159491; Tue, 30 Aug 2022 21:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njE0Bu-3ixp7; Tue, 30 Aug 2022 21:44:21 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 671BEC14F6E5; Tue, 30 Aug 2022 21:44:21 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3CDC2C88B6; Tue, 30 Aug 2022 21:44:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9284 on Multihoming Deployment Considerations for DDoS Open Threat Signaling (DOTS)
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: <20220831044421.3CDC2C88B6@rfcpa.amsl.com>
Date: Tue, 30 Aug 2022 21:44:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/d7aU2-VZxqcm3lMrg1F5GkPScUM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 31 Aug 2022 04:44:25 -0000

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

        
        RFC 9284

        Title:      Multihoming Deployment Considerations for DDoS 
                    Open Threat Signaling (DOTS) 
        Author:     M. Boucadair,
                    T. Reddy.K,
                    W. Pan
        Status:     Informational
        Stream:     IETF
        Date:       August 2022
        Mailbox:    mohamed.boucadair@orange.com,
                    kondtir@gmail.com,
                    william.panwei@huawei.com
        Pages:      14
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dots-multihoming-13.txt

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

        DOI:        10.17487/RFC9284

This document discusses multihoming considerations for DDoS Open
Threat Signaling (DOTS). The goal is to provide some guidance for
DOTS clients and client-domain DOTS gateways when multihomed.

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