DDoS Open Threat Signaling Protocol
draft-teague-dots-protocol-02

Document Type Active Internet-Draft (individual)
Last updated 2017-02-15
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DOTS                                                           N. Teague
Internet-Draft                                            Verisign, Inc.
Intended status: Standards Track                            A. Mortensen
Expires: August 19, 2017                            Arbor Networks, Inc.
                                                       February 15, 2017

                  DDoS Open Threat Signaling Protocol
                     draft-teague-dots-protocol-02

Abstract

   This document describes Distributed-Denial-of-Service (DDoS) Open
   Threat Signaling (DOTS), a protocol for requesting and managing
   mitigation of DDoS attacks.

   DOTS mitigation requests over the signal channel permit domains to
   signal the need for help fending off DDoS attacks, setting the scope
   and duration of the requested mitigation.  Elements called DOTS
   servers field the signals for help, and enable defensive
   countermeasures to defend against the attack reported by the clients,
   reporting the status of the delegated defense to the requesting
   clients.  DOTS clients additionally may use a reliable data channel
   to manage filters and black- and white-lists to restrict or allow
   traffic to the clients' domains arbitrarily.  The DOTS signal channel
   may operate over UDP [RFC0768] and if necessary TCP [RFC0793].  This
   revision discusses a transport-agnostic approach to this channel,
   focusing on the message exchanges and delegating transport specifics
   to other documents.  Discussion of the reliable data channel may be
   found in [I-D.reddy-dots-data-channel].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 19, 2017.

Teague & Mortensen       Expires August 19, 2017                [Page 1]
Internet-Draft     DDoS Open Threat Signaling Protocol     February 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  DOTS Agents . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  DOTS Communication Channels . . . . . . . . . . . . . . . . .   5
   4.  Signal Channel  . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Minimum Viable Information  . . . . . . . . . . . . . . .   6
     4.2.  Signal Channel Messages . . . . . . . . . . . . . . . . .   7
       4.2.1.  Messaging Overview  . . . . . . . . . . . . . . . . .   7
       4.2.2.  Message Definition and Serialization  . . . . . . . .   9
       4.2.3.  Client Message Fields . . . . . . . . . . . . . . . .   9
       4.2.4.  Mitigation Request Fields . . . . . . . . . . . . . .  10
       4.2.5.  DOTS Server Message Fields  . . . . . . . . . . . . .  11
       4.2.6.  Server Errors . . . . . . . . . . . . . . . . . . . .  11
       4.2.7.  Server Mitigation Status Fields . . . . . . . . . . .  13
     4.3.  Interactions  . . . . . . . . . . . . . . . . . . . . . .  13
       4.3.1.  Session Initialization  . . . . . . . . . . . . . . .  13
       4.3.2.  Heartbeat . . . . . . . . . . . . . . . . . . . . . .  15
       4.3.3.  Mitigation Request Handling . . . . . . . . . . . . .  18
       4.3.4.  Ancillary Messages  . . . . . . . . . . . . . . . . .  20
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  23
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  23
   7.  Appendix A: Message Schemas . . . . . . . . . . . . . . . . .  23
Show full document text