Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
draft-ietf-dots-signal-channel-03
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (dots WG)
|
|
Last updated |
|
2017-08-16
|
|
Replaces |
|
draft-reddy-dots-signal-channel
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
DOTS T. Reddy
Internet-Draft McAfee
Intended status: Standards Track M. Boucadair
Expires: February 17, 2018 Orange
P. Patil
Cisco
A. Mortensen
Arbor Networks, Inc.
N. Teague
Verisign, Inc.
August 16, 2017
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal
Channel
draft-ietf-dots-signal-channel-03
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.
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 February 17, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
Reddy, et al. Expires February 17, 2018 [Page 1]
Internet-Draft DOTS Signal Channel August 2017
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
2. Notational Conventions and Terminology . . . . . . . . . . . 3
3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 4
4. Happy Eyeballs for DOTS Signal Channel . . . . . . . . . . . 5
5. DOTS Signal Channel . . . . . . . . . . . . . . . . . . . . . 7
5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2. DOTS Signal YANG Model . . . . . . . . . . . . . . . . . 8
5.2.1. Mitigation Request Model structure . . . . . . . . . 8
5.2.2. Mitigation Request Model . . . . . . . . . . . . . . 8
5.2.3. Session Configuration Model structure . . . . . . . . 10
5.2.4. Session Configuration Model . . . . . . . . . . . . . 10
5.3. Mitigation Request . . . . . . . . . . . . . . . . . . . 12
5.3.1. Requesting mitigation . . . . . . . . . . . . . . . . 12
5.3.2. Withdraw a DOTS Signal . . . . . . . . . . . . . . . 17
5.3.3. Retrieving a DOTS Signal . . . . . . . . . . . . . . 18
5.3.4. Efficacy Update from DOTS Client . . . . . . . . . . 23
5.4. DOTS Signal Channel Session Configuration . . . . . . . . 25
5.4.1. Discover Acceptable Configuration Parameters . . . . 26
5.4.2. Convey DOTS Signal Channel Session Configuration . . 27
5.4.3. Delete DOTS Signal Channel Session Configuration . . 30
5.4.4. Retrieving DOTS Signal Channel Session Configuration 30
5.5. Redirected Signaling . . . . . . . . . . . . . . . . . . 31
5.6. Heartbeat Mechanism . . . . . . . . . . . . . . . . . . . 32
6. Mapping parameters to CBOR . . . . . . . . . . . . . . . . . 33
7. (D)TLS Protocol Profile and Performance considerations . . . 34
7.1. MTU and Fragmentation Issues . . . . . . . . . . . . . . 34
8. (D)TLS 1.3 considerations . . . . . . . . . . . . . . . . . . 35
9. Mutual Authentication of DOTS Agents & Authorization of DOTS
Show full document text