Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
draft-ietf-dots-signal-filter-control-02
Document Type Active Internet-Draft (dots WG)
Last updated 2019-09-17
Replaces draft-nishizuka-dots-signal-control-filtering
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-dots-signal-control@2019-05-13.yang
- Yang impact analysis for draft-ietf-dots-signal-filter-control
- Mailing list discussion
Stream WG state WG Consensus: Waiting for Write-Up
Doc Shepherd Follow-up Underway
Document shepherd Liang Xia
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Valery Smyslov <valery@smyslov.net>, Liang Xia <frank.xialiang@huawei.com>
Email authors Email WG IPR References Referenced by Nits 
DOTS                                                        K. Nishizuka
Internet-Draft                                        NTT Communications
Intended status: Standards Track                            M. Boucadair
Expires: March 19, 2020                                           Orange
                                                                T. Reddy
                                                                  McAfee
                                                               T. Nagata
                                                                 Lepidum
                                                      September 16, 2019

  Controlling Filtering Rules Using Distributed Denial-of-Service Open
                 Threat Signaling (DOTS) Signal Channel
                draft-ietf-dots-signal-filter-control-02

Abstract

   This document specifies an extension to the DOTS signal channel
   protocol so that DOTS clients can control their filtering rules when
   an attack mitigation is active.

   Particularly, this extension allows a DOTS client to activate or de-
   activate existing filtering rules during a DDoS attack.  The
   characterization of these filtering rules is supposed to be conveyed
   by a DOTS client during an idle time by means of the DOTS data
   channel protocol.

Editorial Note (To be removed by RFC Editor)

   Please update these statements within the document 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: Controlling Filtering Rules Using Distributed Denial-
      of-Service Open Threat Signaling (DOTS) Signal Channel";

   o  reference: RFC XXXX

   o  [RFCXXXX]

   Please update these statements with the RFC number to be assigned to
   the following documents:

   o  "RFC SSSS: Distributed Denial-of-Service Open Threat Signaling
      (DOTS) Signal Channel Specification" (used to be
      [I-D.ietf-dots-signal-channel])

Nishizuka, et al.        Expires March 19, 2020                 [Page 1]
Internet-Draft         DOTS Signal Filter Control         September 2019

   o  "RFC DDDD: Distributed Denial-of-Service Open Threat Signaling
      (DOTS) Data Channel Specification" (used to be
      [I-D.ietf-dots-data-channel])

   Please update the "revision" date of the YANG module.

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 March 19, 2020.

Copyright Notice

   Copyright (c) 2019 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
     1.1.  The Problem . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  The Solution  . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Controlling Filtering Rules of a DOTS Client  . . . . . . . .   5
     3.1.  Binding DOTS Data and Signal Channels . . . . . . . . . .   5
     3.2.  DOTS Signal Channel Extension . . . . . . . . . . . . . .   6
       3.2.1.  Parameters and Behaviors  . . . . . . . . . . . . . .   6

Nishizuka, et al.        Expires March 19, 2020                 [Page 2]
Internet-Draft         DOTS Signal Filter Control         September 2019

       3.2.2.  DOTS Signal Filtering Control Module  . . . . . . . .   9
         3.2.2.1.  Tree Structure  . . . . . . . . . . . . . . . . .   9
         3.2.2.2.  YANG Module . . . . . . . . . . . . . . . . . . .  10
   4.  Sample Examples . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Conflict Handling . . . . . . . . . . . . . . . . . . . .  12
     4.2.  On-Demand Activation of an Accept-List Filter . . . . . .  17
     4.3.  DOTS Servers/Mitigators Lacking Capacity  . . . . . . . .  18
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools