Inter-Domain DOTS Use Cases
draft-nishizuka-dots-inter-domain-usecases-02

Document Type Active Internet-Draft (individual)
Last updated 2016-09-19
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: Informational                        September 20, 2016
Expires: March 24, 2017

                      Inter-Domain DOTS Use Cases
             draft-nishizuka-dots-inter-domain-usecases-02

Abstract

   This document describes inter-domain use cases of the DDoS Open
   Threat Signaling(DOTS).  The use cases descirbed in this draft will
   be merged into [I-D.draft-ietf-dots-use-cases].

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 March 24, 2017.

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.

Nishizuka                Expires March 24, 2017                 [Page 1]
Internet-Draft         Inter-Domain DOTS Use Cases        September 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Inter-Domain DDoS Protection Scenario . . . . . . . . . . . .   3
     3.1.  Protection Methods  . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  Blackholing . . . . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Selective Blackholing . . . . . . . . . . . . . . . .   5
       3.1.3.  RTBH with uRPF  . . . . . . . . . . . . . . . . . . .   5
       3.1.4.  BGP flowspec  . . . . . . . . . . . . . . . . . . . .   6
       3.1.5.  Filtering(ACL)  . . . . . . . . . . . . . . . . . . .   7
       3.1.6.  DDoS mitigation Appliances  . . . . . . . . . . . . .   7
       3.1.7.  Detouring Technologies  . . . . . . . . . . . . . . .   8
     3.2.  Restriction on the Range of IP Addresses  . . . . . . . .   8
     3.3.  Attack Telemetry  . . . . . . . . . . . . . . . . . . . .   8
     3.4.  DDoS Protection Status  . . . . . . . . . . . . . . . . .  11
     3.5.  DDoS Protection Registration  . . . . . . . . . . . . . .  12
   4.  Inter-Domain Dots Use Cases . . . . . . . . . . . . . . . . .  13
     4.1.  Customer-to-Provider Cases  . . . . . . . . . . . . . . .  13
       4.1.1.  Usecase 1: Single-home Model  . . . . . . . . . . . .  13
       4.1.2.  Usecase 2: Multi-home Model . . . . . . . . . . . . .  14
     4.2.  Provider-to-Provider Cases  . . . . . . . . . . . . . . .  15
       4.2.1.  Usecase 3: Delegation Model . . . . . . . . . . . . .  15
       4.2.2.  Usecase 4: Distributed Architecture Model . . . . . .  17
       4.2.3.  Usecase 5: Centralized Architecture Model . . . . . .  18
   5.  Consolidated Usecases . . . . . . . . . . . . . . . . . . . .  19
     5.1.  Intra-domain Use Case . . . . . . . . . . . . . . . . . .  19
     5.2.  Primary Inter-domain Usecase  . . . . . . . . . . . . . .  20
     5.3.  Primary Inter-domain Usecase with multiple upstream DDoS
           mitigation providers  . . . . . . . . . . . . . . . . . .  20
     5.4.  Inter-domain Usecase with Client-Side DOTS Relay  . . . .  20
     5.5.  Inter-domain Usecase with Server-Side DOTS Relay  . . . .  21
     5.6.  Inter-domain Usecase with bilateral coordination  . . . .  21
     5.7.  Inter-domain Usecase with multilateral coordination . . .  22
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  22
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  22
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  22
     8.2.  URL References  . . . . . . . . . . . . . . . . . . . . .  24
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  24
Show full document text