Use cases for DDoS Open Threat Signaling (DDoS) Open Threat Signaling
draft-ietf-dots-use-cases-05
|
| Document |
Type |
|
Active Internet-Draft (dots WG)
|
|
Last updated |
|
2017-05-09
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
(wg milestone:
Jul 2017 - Use case document to...
)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
DOTS WG R. Dobbins, Ed.
Internet-Draft Arbor Networks
Intended status: Informational S. Fouant
Expires: November 9, 2017
D. Migault
Ericsson
R. Moskowitz
HTT Consulting
N. Teague
Verisign Inc
L. Xia
Huawei
K. Nishizuka
NTT Communications
May 8, 2017
Use cases for DDoS Open Threat Signaling (DDoS) Open Threat Signaling
draft-ietf-dots-use-cases-05
Abstract
The DDoS Open Threat Signaling (DOTS) effort is intended to provide a
dynamic solution for DDoS cooperation between networks to
appropriately react to DDoS attacks. This document presents use
cases to evaluate the interactions expected between the DOTS
components as well as the DOTS exchanges. The purpose of the use
cases is to identify the interacting DOTS components, how they
collaborate and what are the types of information to be exchanged.
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 November 9, 2017.
Dobbins, et al. Expires November 9, 2017 [Page 1]
Internet-Draft DOTS Use cases May 2017
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
(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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Acronyms . . . . . . . . . . . . . . . . . . 3
3. Use Cases Scenarios . . . . . . . . . . . . . . . . . . . . . 3
3.1. Inter-domain Use Cases . . . . . . . . . . . . . . . . . 4
3.1.1. Enterprise with an upstream transit provider DDoS
mitigation Service . . . . . . . . . . . . . . . . . 4
3.1.2. Enterprise with a Cloud DDoS Mitigation Provider . . 5
3.2. Intra-domain Use Cases . . . . . . . . . . . . . . . . . 6
3.2.1. Homenet DDoS Detection Collaboration for ISP network
management . . . . . . . . . . . . . . . . . . . . . 6
3.2.2. DDoS Orchestration . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
7. Informative References . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
Currently, distributed denial-of-service (DDoS) attack mitigation
solutions are largely based upon siloed, proprietary communications
schemes which result in vendor lock-in. As a side-effect, this makes
the configuration, provisioning, operation, and activation of these
solutions a highly manual and often time-consuming process.
Additionally, coordination of multiple DDoS mitigation solutions
Show full document text