Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
draft-ietf-dots-signal-channel-27
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (dots WG)
|
|
Last updated |
|
2019-01-18
|
|
Replaces |
|
draft-reddy-dots-signal-channel
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
(wg milestone:
Aug 2018 - Signal channel docum...
)
|
|
Document shepherd |
|
Liang Xia
|
|
Shepherd write-up |
|
Show
(last changed 2018-09-19)
|
| IESG |
IESG state |
|
AD Evaluation
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Benjamin Kaduk
|
|
Send notices to |
|
Liang Xia <frank.xialiang@huawei.com>
|
DOTS T. Reddy, Ed.
Internet-Draft McAfee
Intended status: Standards Track M. Boucadair, Ed.
Expires: July 22, 2019 Orange
P. Patil
Cisco
A. Mortensen
Arbor Networks, Inc.
N. Teague
Verisign, Inc.
January 18, 2019
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal
Channel Specification
draft-ietf-dots-signal-channel-27
Abstract
This document specifies the DOTS signal channel, a protocol for
signaling the need for protection against Distributed Denial-of-
Service (DDoS) attacks to a server capable of enabling network
traffic mitigation on behalf of the requesting client.
A companion document defines the DOTS data channel, a separate
reliable communication layer for DOTS management and configuration
purposes.
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: Distributed Denial-of-Service Open Threat Signaling
(DOTS) Signal Channel Specification";
o "| [RFCXXXX] |"
o reference: RFC XXXX
Please update this statement with the RFC number to be assigned to
the following documents:
o "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling
(DOTS) Data Channel Specification (used to be
[I-D.ietf-dots-data-channel])
Reddy, et al. Expires July 22, 2019 [Page 1]
Internet-Draft DOTS Signal Channel Protocol January 2019
Please update TBD/TBD1/TBD2 statements with the assignments made by
IANA to DOTS Signal Channel Protocol.
Also, please update the "revision" date of the YANG modules.
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 July 22, 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 6
4. DOTS Signal Channel: Messages & Behaviors . . . . . . . . . . 9
4.1. DOTS Server(s) Discovery . . . . . . . . . . . . . . . . 9
4.2. CoAP URIs . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3. Happy Eyeballs for DOTS Signal Channel . . . . . . . . . 9
4.4. DOTS Mitigation Methods . . . . . . . . . . . . . . . . . 11
4.4.1. Request Mitigation . . . . . . . . . . . . . . . . . 12
Reddy, et al. Expires July 22, 2019 [Page 2]
Internet-Draft DOTS Signal Channel Protocol January 2019
4.4.2. Retrieve Information Related to a Mitigation . . . . 26
4.4.2.1. DOTS Servers Sending Mitigation Status . . . . . 31
4.4.2.2. DOTS Clients Polling for Mitigation Status . . . 34
4.4.3. Efficacy Update from DOTS Clients . . . . . . . . . . 35
4.4.4. Withdraw a Mitigation . . . . . . . . . . . . . . . . 37
4.5. DOTS Signal Channel Session Configuration . . . . . . . . 38
Show full document text