Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry Specifications
draft-doron-dots-telemetry-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml 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                                                            E. Doron
Internet-Draft                                              Radware Ltd.
Intended status: Informational                                  T. Reddy
Expires: May 3, 2017                                        F. Andreasen
                                                     Cisco Systems, Inc.
                                                                  L. Xia
                                                                  Huawei
                                                            K. Nishizuka
                                                      NTT Communications
                                                        October 30, 2016

  Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
                             Specifications
                     draft-doron-dots-telemetry-00

Abstract

   This document aims to enrich DOTS Signaling with various telemetry
   attributes allowing optimal DDoS/DoS attack mitigation.  The nature
   of the DOTS architecture is to allow DOTS Agents to be integrated in
   highly diverse environments.  Therefore, the DOTS architecture
   imposes a significant challenge in delivering optimal mitigation
   services.  The DOTS Telemetry covered in this document aims to
   provide all needed attributes and feedback signaled from DOTS Agents
   such that optimal mitigation services can be delivered based on DOTS
   Signaling.

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 May 3, 2017.

Doron, et al.              Expires May 3, 2017                  [Page 1]
Internet-Draft               DOTS Telemetry                 October 2016

Copyright Notice

   Copyright (c) 2016 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.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     1.2.  Definition of Terms . . . . . . . . . . . . . . . . . . .   4
   2.  Using the DOTS telemetry for a successful mitigation  . . . .   4
   3.  DOTS Telemetry attributes . . . . . . . . . . . . . . . . . .   8
     3.1.  Pre-mitigation DOTS Telemetry attributes  . . . . . . . .   9
       3.1.1.  "Normal Baselines" of legitimate traffic  . . . . . .   9
       3.1.2.  "Total Attack Traffic volume" . . . . . . . . . . . .   9
       3.1.3.  "Attack Details"  . . . . . . . . . . . . . . . . . .   9
       3.1.4.  "Total pipe capacity" . . . . . . . . . . . . . . . .  10
       3.1.5.  List of already "Authenticated source IPs"  . . . . .  10
     3.2.  Client to Server Mitigation Status DOTS Telemetry
           attributes  . . . . . . . . . . . . . . . . . . . . . . .  10
       3.2.1.  Current "Total traffic volumes" . . . . . . . . . . .  11
       3.2.2.  Current "Total Attack Traffic"  . . . . . . . . . . .  11
       3.2.3.  "Mitigation Efficacy Factor"  . . . . . . . . . . . .  11
       3.2.4.  "Attack Details"  . . . . . . . . . . . . . . . . . .  11
     3.3.  Server to Client Mitigation Status DOTS Telemetry
           attributes  . . . . . . . . . . . . . . . . . . . . . . .  11
       3.3.1.  Current "Mitigation Countermeasure status"  . . . . .  11
   4.  DOTS Telemetry Use-cases  . . . . . . . . . . . . . . . . . .  12
     4.1.  Hybrid anti-DoS services use-case . . . . . . . . . . . .  12
     4.2.  MSP to MSP anti-DoS services use-case . . . . . . . . . .  13
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text