Distributed-Denial-of-Service Open Threat Signaling (DOTS) Architecture
draft-ietf-dots-architecture-13

Document Type Active Internet-Draft (dots WG)
Last updated 2019-04-03
Replaces draft-mortensen-dots-architecture
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up (wg milestone: Nov 2018 - Architecture documen... )
Document shepherd Valery Smyslov
Shepherd write-up Show (last changed 2019-03-24)
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Roman Danyliw <rdd@cert.org>, Valery Smyslov <valery@smyslov.net>
DOTS                                                   A. Mortensen, Ed.
Internet-Draft                                            Arbor Networks
Intended status: Informational                             T. Reddy, Ed.
Expires: October 5, 2019                                    McAfee, Inc.
                                                            F. Andreasen
                                                                   Cisco
                                                               N. Teague
                                                                Verisign
                                                              R. Compton
                                                                 Charter
                                                          April 03, 2019

Distributed-Denial-of-Service Open Threat Signaling (DOTS) Architecture
                    draft-ietf-dots-architecture-13

Abstract

   This document describes an architecture for establishing and
   maintaining Distributed Denial of Service (DDoS) Open Threat
   Signaling (DOTS) within and between domains.  The document does not
   specify protocols or protocol extensions, instead focusing on
   defining architectural relationships, components and concepts used in
   a DOTS deployment.

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 https://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 October 5, 2019.

Copyright Notice

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

Mortensen, et al.        Expires October 5, 2019                [Page 1]
Internet-Draft              DOTS Architecture                 April 2019

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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.  Context and Motivation  . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.1.  Key Words . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Definition of Terms . . . . . . . . . . . . . . . . .   3
     1.2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  DOTS Architecture . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  DOTS Operations . . . . . . . . . . . . . . . . . . . . .   8
     2.2.  Components  . . . . . . . . . . . . . . . . . . . . . . .   9
       2.2.1.  DOTS Client . . . . . . . . . . . . . . . . . . . . .   9
       2.2.2.  DOTS Server . . . . . . . . . . . . . . . . . . . . .  10
       2.2.3.  DOTS Gateway  . . . . . . . . . . . . . . . . . . . .  11
     2.3.  DOTS Agent Relationships  . . . . . . . . . . . . . . . .  12
       2.3.1.  Gatewayed Signaling . . . . . . . . . . . . . . . . .  14
   3.  Concepts  . . . . . . . . . . . . . . . . . . . . . . . . . .  16
     3.1.  DOTS Sessions . . . . . . . . . . . . . . . . . . . . . .  16
       3.1.1.  Preconditions . . . . . . . . . . . . . . . . . . . .  16
       3.1.2.  Establishing the DOTS Session . . . . . . . . . . . .  17
       3.1.3.  Maintaining the DOTS Session  . . . . . . . . . . . .  18
     3.2.  Modes of Signaling  . . . . . . . . . . . . . . . . . . .  18
       3.2.1.  Direct Signaling  . . . . . . . . . . . . . . . . . .  18
       3.2.2.  Redirected Signaling  . . . . . . . . . . . . . . . .  18
       3.2.3.  Recursive Signaling . . . . . . . . . . . . . . . . .  20
       3.2.4.  Anycast Signaling . . . . . . . . . . . . . . . . . .  22
       3.2.5.  Signaling Considerations for Network Address
               Translation . . . . . . . . . . . . . . . . . . . . .  23
     3.3.  Triggering Requests for Mitigation  . . . . . . . . . . .  26
       3.3.1.  Manual Mitigation Request . . . . . . . . . . . . . .  26
       3.3.2.  Automated Conditional Mitigation Request  . . . . . .  27
       3.3.3.  Automated Mitigation on Loss of Signal  . . . . . . .  28
Show full document text