Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
draft-ietf-dots-signal-channel-10

The information below is for an old version of the document
Document Type Active Internet-Draft (dots WG)
Last updated 2017-12-01
Replaces draft-reddy-dots-signal-channel
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Aug 2018 - Signal channel docum... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DOTS                                                            T. Reddy
Internet-Draft                                                    McAfee
Intended status: Standards Track                            M. Boucadair
Expires: June 3, 2018                                             Orange
                                                                P. Patil
                                                                   Cisco
                                                            A. Mortensen
                                                    Arbor Networks, Inc.
                                                               N. Teague
                                                          Verisign, Inc.
                                                       November 30, 2017

   Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal
                                Channel
                   draft-ietf-dots-signal-channel-10

Abstract

   This document specifies the DOTS signal channel, a protocol for
   signaling the need for protection against Distributed Denial-of-
   Service (DDoS) attacks to a server capable of enabling network
   traffic mitigation on behalf of the requesting client.

   A companion document defines the DOTS data channel, a separate
   reliable communication layer for DOTS management and configuration.

Editorial Note (To be removed by RFC Editor)

   Please update these statements with the RFC number to be assigned to
   this document:

   o  "This version of this YANG module is part of RFC XXXX;"

   o  "RFC XXXX: Distributed Denial-of-Service Open Threat Signaling
      (DOTS) Signal Channel";

   o  "| 3.00 | Alternate server | [RFCXXXX] |"

   o  reference: RFC XXXX

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

Reddy, et al.             Expires June 3, 2018                  [Page 1]
Internet-Draft             DOTS Signal Channel             November 2017

   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 June 3, 2018.

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
   (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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Notational Conventions and Terminology  . . . . . . . . . . .   5
   3.  Design Overview . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  DOTS Signal Channel: Messages & Behaviors . . . . . . . . . .   7
     4.1.  DOTS Server(s) Discovery  . . . . . . . . . . . . . . . .   7
     4.2.  CoAP URIs . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.3.  Happy Eyeballs for DOTS Signal Channel  . . . . . . . . .   8
     4.4.  DOTS Mitigation Methods . . . . . . . . . . . . . . . . .   9
       4.4.1.  Request Mitigation  . . . . . . . . . . . . . . . . .  10
       4.4.2.  Withdraw a Mitigation . . . . . . . . . . . . . . . .  18
       4.4.3.  Retrieve Information Related to a Mitigation  . . . .  19
       4.4.4.  Efficacy Update from DOTS Clients . . . . . . . . . .  26
     4.5.  DOTS Signal Channel Session Configuration . . . . . . . .  28
       4.5.1.  Discover Configuration Parameters . . . . . . . . . .  29
       4.5.2.  Convey DOTS Signal Channel Session Configuration  . .  31
       4.5.3.  Delete DOTS Signal Channel Session Configuration  . .  35
     4.6.  Redirected Signaling  . . . . . . . . . . . . . . . . . .  36
     4.7.  Heartbeat Mechanism . . . . . . . . . . . . . . . . . . .  37
   5.  DOTS Signal Channel YANG Modules  . . . . . . . . . . . . . .  38
     5.1.  Mitigation Request YANG Module Tree Structure . . . . . .  38
     5.2.  Mitigation Request YANG Module  . . . . . . . . . . . . .  39

Reddy, et al.             Expires June 3, 2018                  [Page 2]
Internet-Draft             DOTS Signal Channel             November 2017
Show full document text