Use cases for DDoS Open Threat Signaling
draft-ietf-dots-use-cases-00

The information below is for an old version of the document
Document Type Active Internet-Draft (dots WG)
Last updated 2015-10-19
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DOTS WG                                                  R. Dobbins, Ed.
Internet-Draft                                            Arbor Networks
Intended status: Informational                                 S. Fouant
Expires: April 21, 2016                          Corero Network Security
                                                              D. Migault
                                                                Ericsson
                                                            R. Moskowitz
                                                          HTT Consulting
                                                               N. Teague
                                                            Verisign Inc
                                                                  L. Xia
                                                                  Huawei
                                                        October 19, 2015

                Use cases for DDoS Open Threat Signaling
                    draft-ietf-dots-use-cases-00.txt

Abstract

   This document delineates principal and ancillary use cases for DDoS
   Open Threat Signaling (DOTS), a communications protocol intended to
   facilitate the programmatic, coordinated mitigation of Distributed
   Denial of Service (DDoS) attacks via a standards-based mechanism.
   DOTS is purposely designed to support requests for DDoS mitigation
   services and status updates across inter-organizational
   administrative boundaries.

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 April 21, 2016.

Dobbins, et al.          Expires April 21, 2016                 [Page 1]
Internet-Draft               DOTS Use cases                 October 2015

Copyright Notice

   Copyright (c) 2015 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.  Requirements notation . . . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology and Acronyms  . . . . . . . . . . . . . . . . . .   4
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Primary Use Cases . . . . . . . . . . . . . . . . . . . .   5
       4.1.1.  Successful Automatic or Operator-Assisted CPE or PE
               Mitigators Request Upstream DDoS Mitigation Services    5
       4.1.2.  Successful Automatic or Operator-Assisted CPE or PE
               Network Infrastructure Element Request to Upstream
               Mitigator . . . . . . . . . . . . . . . . . . . . . .   7
       4.1.3.  Successful Automatic or Operator-Assisted CPE or PE
               Attack Telemetry Detection/Classification System
               Request to Upstream Mitigator . . . . . . . . . . . .   9
       4.1.4.  Successful Automatic or Operator-Assisted Targeted
               Service/Application Request to Upstream Mitigator . .  12
       4.1.5.  Successful Manual Web Portal Request to Upstream
               Mitigator . . . . . . . . . . . . . . . . . . . . . .  14
       4.1.6.  Successful Manual Mobile Device Application Request
               to Upstream Mitigator . . . . . . . . . . . . . . . .  16
       4.1.7.  Unsuccessful Automatic or Operator-Assisted CPE or PE
               Mitigators Request Upstream DDoS Mitigation Services   18
     4.2.  Ancillary Use Cases . . . . . . . . . . . . . . . . . . .  19
       4.2.1.  Auto-registration of DOTS clients with DOTS servers .  19
       4.2.2.  Auto-provisioning of DDoS countermeasures . . . . . .  20
       4.2.3.  Informational DDoS attack notification to interested
               and authorized third parties  . . . . . . . . . . . .  20
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
Show full document text