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

This document discusses multihoming considerations for DDoS Open Threat Signaling (DOTS). The goal is to provide some guidance for DOTS clients and…

Read RFC 9284 on the RFC Editor

Outgoing relationships (16 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
Normative reference — RFC 8811: DDoS Open Threat Signaling (DOTS) Architecture
Informative reference — RFC 4732: Internet Denial-of-Service Considerations
Informative reference — RFC 3582: Goals for IPv6 Site-Multihoming Architectures
Informative reference — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Informative reference — RFC 8783: Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
Informative reference — RFC 7556: Multiple Provisioning Domain Architecture
Informative reference — RFC 4116: IPv4 Multihoming Practices and Limitations
Informative reference — RFC 4218: Threats Relating to IPv6 Multihoming Solutions
Informative reference — RFC 8612: DDoS Open Threat Signaling (DOTS) Requirements
Informative reference — RFC 8903: Use Cases for DDoS Open Threat Signaling
Informative reference — RFC 8803: 0-RTT TCP Convert Protocol
Informative reference — RFC 8043: Source-Address-Dependent Routing and Source Address Selection for IPv6 Hosts: Overview of the Problem Space
Informative reference — RFC 8973: DDoS Open Threat Signaling (DOTS) Agent Discovery