Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
draft-ietf-dots-telemetry-15
|
Document |
Type |
|
Active Internet-Draft (dots WG)
|
|
Authors |
|
Mohamed Boucadair
,
Tirumaleswar Reddy.K
,
Ehud Doron
,
chenmeiling
,
Jon Shallow
|
|
Last updated |
|
2021-01-19
(latest revision 2020-12-08)
|
|
Replaces |
|
draft-reddy-dots-telemetry
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
|
Yang Validation |
|
☯
0 errors, 1 warnings.
draft-ietf-dots-telemetry-15.txt:
xym 0.4.10:
Extracting 'ietf-dots-telemetry@2020-12-07.yang'
Removed 0 empty lines
Extracting 'ietf-dots-mapping@2020-06-26.yang'
Removed 0 empty lines
ietf-dots-telemetry@2020-12-07.yang:
pyang 2.4.0: pyang --verbose --ietf -p {libs} {model}:
# module search path: a/www/ietf-ftp/yang/rfcmod/:/a/www/ietf-ftp/yang/draftmod/:/a/www/ietf-ftp/yang/ianamod/:/a/www/ietf-ftp/yang/catalogmod/:.:/var/lib/wwwrun/yang/modules:/a/www/ietf-datatracker/7.24.0/env/share/yang/modules
# read ietf-dots-telemetry@2020-12-07.yang (CL)
# read /a/www/ietf-ftp/yang/draftmod/ietf-dots-signal-channel@2020-09-24.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-inet-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-inet-types@2020-07-06.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-yang-types@2020-07-06.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-dots-data-channel@2020-05-28.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-access-control-list.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-access-control-list@2019-03-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-packet-fields.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-packet-fields@2019-03-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-ethertypes.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-ethertypes@2019-03-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-interfaces.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-interfaces@2018-02-20.yang
# read /a/www/ietf-ftp/yang/draftmod/iana-dots-signal-channel@2020-09-24.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-yang-structure-ext.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-yang-structure-ext@2020-06-17.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-network-topology.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-network-topology@2018-02-26.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-network.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-network@2018-02-26.yang
ietf-dots-telemetry@2020-12-07.yang:6: warning: imported module "ietf-dots-signal-channel" not used
yanglint SO 1.6.7: yanglint --verbose -p {tmplib} -p {rfclib} -p {draftlib} -p {ianalib} -p {cataloglib} {model} -i:
No validation errors
ietf-dots-mapping@2020-06-26.yang:
pyang 2.4.0: pyang --verbose --ietf -p {libs} {model}:
# module search path: a/www/ietf-ftp/yang/rfcmod/:/a/www/ietf-ftp/yang/draftmod/:/a/www/ietf-ftp/yang/ianamod/:/a/www/ietf-ftp/yang/catalogmod/:.:/var/lib/wwwrun/yang/modules:/a/www/ietf-datatracker/7.24.0/env/share/yang/modules
# read ietf-dots-mapping@2020-06-26.yang (CL)
# read /a/www/ietf-ftp/yang/rfcmod/ietf-dots-data-channel@2020-05-28.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-inet-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-inet-types@2020-07-06.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-access-control-list.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-access-control-list@2019-03-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-yang-types@2020-07-06.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-packet-fields.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-packet-fields@2019-03-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-ethertypes.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-ethertypes@2019-03-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-interfaces.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-interfaces@2018-02-20.yang
yanglint SO 1.6.7: yanglint --verbose -p {tmplib} -p {rfclib} -p {draftlib} -p {ianalib} -p {cataloglib} {model} -i:
No validation errors
|
|
Reviews |
|
|
|
Additional Resources |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Valery Smyslov
|
|
Shepherd write-up |
|
Show
(last changed 2021-01-19)
|
IESG |
IESG state |
|
Publication Requested
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Benjamin Kaduk
|
|
Send notices to |
|
valery@smyslov.net
|
DOTS M. Boucadair, Ed.
Internet-Draft Orange
Intended status: Standards Track T. Reddy, Ed.
Expires: June 11, 2021 McAfee
E. Doron
Radware Ltd.
M. Chen
CMCC
J. Shallow
December 8, 2020
Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
draft-ietf-dots-telemetry-15
Abstract
This document aims to enrich DOTS signal channel protocol with
various telemetry attributes allowing optimal Distributed Denial-of-
Service attack mitigation. It specifies the normal traffic baseline
and attack traffic telemetry attributes a DOTS client can convey to
its DOTS server in the mitigation request, the mitigation status
telemetry attributes a DOTS server can communicate to a DOTS client,
and the mitigation efficacy telemetry attributes a DOTS client can
communicate to a DOTS server. The telemetry attributes can assist
the mitigator to choose the DDoS mitigation techniques and perform
optimal DDoS attack mitigation.
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 June 11, 2021.
Boucadair, et al. Expires June 11, 2021 [Page 1]
Internet-Draft DOTS Telemetry December 2020
Copyright Notice
Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. DOTS Telemetry: Overview and Purpose . . . . . . . . . . . . 6
3.1. Need More Visibility . . . . . . . . . . . . . . . . . . 6
3.2. Enhanced Detection . . . . . . . . . . . . . . . . . . . 7
3.3. Efficient Mitigation . . . . . . . . . . . . . . . . . . 9
4. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. Overview of Telemetry Operations . . . . . . . . . . . . 10
4.2. Generic Considerations . . . . . . . . . . . . . . . . . 10
4.2.1. DOTS Client Identification . . . . . . . . . . . . . 10
4.2.2. DOTS Gateways . . . . . . . . . . . . . . . . . . . . 10
4.2.3. Empty URI Paths . . . . . . . . . . . . . . . . . . . 11
4.2.4. Controlling Configuration Data . . . . . . . . . . . 11
4.3. Block-wise Transfer . . . . . . . . . . . . . . . . . . . 11
4.4. DOTS Multi-homing Considerations . . . . . . . . . . . . 11
4.5. YANG Considerations . . . . . . . . . . . . . . . . . . . 12
4.6. A Note About Examples . . . . . . . . . . . . . . . . . . 13
5. Telemetry Operation Paths . . . . . . . . . . . . . . . . . . 13
6. DOTS Telemetry Setup Configuration . . . . . . . . . . . . . 14
6.1. Telemetry Configuration . . . . . . . . . . . . . . . . . 15
6.1.1. Retrieve Current DOTS Telemetry Configuration . . . . 15
6.1.2. Convey DOTS Telemetry Configuration . . . . . . . . . 17
6.1.3. Retrieve Installed DOTS Telemetry Configuration . . . 20
6.1.4. Delete DOTS Telemetry Configuration . . . . . . . . . 21
6.2. Total Pipe Capacity . . . . . . . . . . . . . . . . . . . 21
6.2.1. Convey DOTS Client Domain Pipe Capacity . . . . . . . 22
Show full document text