expand attack type in signal channel
draft-meiling-dots-attack-type-expansion-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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                                                             M. Chen
Internet-Draft                                                    Li. Su
Intended status: Experimental                                       CMCC
Expires: September 10, 2019                                March 9, 2019

                  expand attack type in signal channel
              draft-meiling-dots-attack-type-expansion-00

Abstract

   This document describes a DDoS Mitigation Request parameter used in
   the Signal Channel request, as an expansion of the signal channel for
   mitigating DDoS attack accurately with attack types.  The proposed
   parameter will help to achieve fine-grained disposition for the
   attack traffic to be cleaned.

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 September 10, 2019.

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.

Chen & Su              Expires September 10, 2019               [Page 1]
Internet-Draft              dots-attack-type                  March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Request Mitigation expansion  . . . . . . . . . . . . . . . .   4
   4.  Standard of Attack Type Definition  . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Distributed Denial of Service (DDoS) is a type of resource-consuming
   attack, which exploits a large number of attack resources and uses
   standard protocols to attack target objects.  DDoS attacks consume a
   large amount of target object network resources or server resources
   (including computing power, storage capacity, etc.) of the target
   object, so that the target object cannot provide network services
   normally.  At present, DDoS attack is one of the most powerful and
   indefensible attacks on the Internet, and due to the extensive use of
   mobile devices and IoT devices in recent years, it is easier for DDoS
   attackers to attack with real attack sources (broilers).

   Why again raise the parameter of attack type to add to mitigation
   request for discussion; Although the scope of DOTS work now is the
   interaction between DOTS client and DOTS server, the mitigator and
   attack target roles must be considered in the implementation when use
   DOTS mechanism.  It has been discussed before whether it is
   appropriate to carry the type of attack in the mitigation request
   parameters.  Some views hold that the type of attack reported is not
   credible.The premise of this view is that both attack detection and
   attack disposal belong to the mitigator role.  But there is another
   scenario in which attack detection and attack disposal are separated,
   and one possible scenario in which the attack detection is at the
   attack target and the attack disposal is at the mitigator, then
   attack informations such as the attack type is trusted.We can also
   consider a scenario, if an entity is not only the attack target, but
   also a mitigator, when ddos attack occurs, it requires other
   mitigators upper link to mitigate the attack flow, so it will use
   dots client send mitigation reqest to other top link mitigator
Show full document text