Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification
draft-ietf-dots-data-channel-16
|
| Document |
Type |
|
Active Internet-Draft (dots WG)
|
|
Last updated |
|
2018-05-18
|
|
Replaces |
|
draft-reddy-dots-data-channel
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ietf-dots-data-channel-16.txt:
xym 0.4:
Extracting 'ietf-dots-data-channel@2018-05-15.yang'
Removed 0 empty lines
ietf-dots-data-channel@2018-05-15.yang:
pyang 1.7.5: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Additional URLs |
|
|
| Stream |
WG state
|
|
WG Document
(wg milestone:
Aug 2018 - Data channel documen...
)
|
|
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, Ed.
Internet-Draft McAfee
Intended status: Standards Track M. Boucadair, Ed.
Expires: November 18, 2018 Orange
K. Nishizuka
NTT Communications
L. Xia
Huawei
P. Patil
Cisco
A. Mortensen
Arbor Networks, Inc.
N. Teague
Verisign, Inc.
May 17, 2018
Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel
Specification
draft-ietf-dots-data-channel-16
Abstract
The document specifies a Distributed Denial-of-Service Open Threat
Signaling (DOTS) data channel used for bulk exchange of data that
cannot easily or appropriately communicated through the DOTS signal
channel under attack conditions.
This is a companion document to the DOTS signal channel
specification.
Editorial Note (To be removed by RFC Editor)
Please update these statements 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) Data Channel Specification";
o reference: RFC XXXX
Please update these statements with the RFC number to be assigned to
the following documents:
Reddy, et al. Expires November 18, 2018 [Page 1]
Internet-Draft DOTS Data Channel Protocol May 2018
o "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling
(DOTS) Signal Channel Specification" (used to be
[I-D.ietf-dots-signal-channel])
o "RFC ZZZZ: Network Access Control List (ACL) YANG Data Model"
(used to be [I-D.ietf-netmod-acl-model])
Please update the "revision" date of the YANG module.
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 November 18, 2018.
Copyright Notice
Copyright (c) 2018 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.
Reddy, et al. Expires November 18, 2018 [Page 2]
Internet-Draft DOTS Data Channel Protocol May 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. DOTS Data Channel . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Design Overview . . . . . . . . . . . . . . . . . . . . . 6
3.2. DOTS Server(s) Discovery . . . . . . . . . . . . . . . . 8
3.3. NAT Considerations . . . . . . . . . . . . . . . . . . . 8
3.4. DOTS Gateways . . . . . . . . . . . . . . . . . . . . . . 8
3.5. Detect and Prevent Infinite Loops . . . . . . . . . . . . 9
3.6. Stale Entries . . . . . . . . . . . . . . . . . . . . . . 10
4. DOTS Data Channel YANG Module . . . . . . . . . . . . . . . . 10
4.1. Tree Structure . . . . . . . . . . . . . . . . . . . . . 10
4.2. Filtering Fields . . . . . . . . . . . . . . . . . . . . 14
Show full document text