Inter-organization cooperative DDoS protection mechanism
draft-nishizuka-dots-inter-domain-mechanism-02

Document Type Active Internet-Draft (individual)
Last updated 2016-12-27
Stream (None)
Intended RFC status (None)
Formats plain text 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                                                        K. Nishizuka
Internet-Draft                                        NTT Communications
Intended status: Standards Track                                  L. Xia
Expires: June 30, 2017                                            J. Xia
                                           Huawei Technologies Co., Ltd.
                                                                D. Zhang

                                                                 L. Fang
                                                               Microsoft
                                                                 C. Gray
                                                           Comcast, Inc.
                                                              R. Compton
                                            Charter Communications, Inc.
                                                       December 27, 2016

        Inter-organization cooperative DDoS protection mechanism
          draft-nishizuka-dots-inter-domain-mechanism-02

Abstract

   As DDoS attacks evolve rapidly in the aspect of volume and
   sophistication, cooperation among operators has become very necessary
   because it gives us quicker and more sophisticated protection to cope
   with the varius DDoS attacks.  This document describes possible
   mechanisms which implement the cooperative inter-organization DDoS
   protection by DOTS protocol.  The described data models are intended
   to cover intra-organization and inter-organization solutions.

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 June 30, 2017.

Nishizuka, et al.         Expires June 30, 2017                 [Page 1]
Internet-Draft     Inter-organization DDoS protection      December 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.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Key Words . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Definition of Terms . . . . . . . . . . . . . . . . . . .   4
   3.  Inter-organization DDoS Protection Requirements . . . . . . .   4
     3.1.  Provisioning Requirements . . . . . . . . . . . . . . . .   4
       3.1.1.  Automatic Provisioning vs Manual Provisioning . . . .   5
     3.2.  Coordination Requirements . . . . . . . . . . . . . . . .   5
       3.2.1.  Near Source Protection Problem  . . . . . . . . . . .   5
     3.3.  Returning Path Requirements . . . . . . . . . . . . . . .   6
   4.  Inter-organization DOTS Architecture  . . . . . . . . . . . .   6
     4.1.  Distributed Architecture  . . . . . . . . . . . . . . . .   7
     4.2.  Centralized Architecture  . . . . . . . . . . . . . . . .  10
   5.  Inter-organization DOTS Protocol  . . . . . . . . . . . . . .  11
     5.1.  Provisioning Stage  . . . . . . . . . . . . . . . . . . .  13
       5.1.1.  Messages  . . . . . . . . . . . . . . . . . . . . . .  13
       5.1.2.  Operations  . . . . . . . . . . . . . . . . . . . . .  17
     5.2.  Signaling Stage . . . . . . . . . . . . . . . . . . . . .  18
       5.2.1.  Messages  . . . . . . . . . . . . . . . . . . . . . .  18
       5.2.2.  Operations  . . . . . . . . . . . . . . . . . . . . .  24
   6.  Other Considerations  . . . . . . . . . . . . . . . . . . . .  25
     6.1.  Billing Data  . . . . . . . . . . . . . . . . . . . . . .  25
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  26
Show full document text