draft-ietf-dots-requirements-13.txt   draft-ietf-dots-requirements-14.txt 
DOTS A. Mortensen DOTS A. Mortensen
Internet-Draft Arbor Networks Internet-Draft Arbor Networks
Intended status: Informational R. Moskowitz Intended status: Informational R. Moskowitz
Expires: August 11, 2018 Huawei Expires: August 12, 2018 Huawei
T. Reddy T. Reddy
McAfee McAfee
February 07, 2018 February 08, 2018
Distributed Denial of Service (DDoS) Open Threat Signaling Requirements Distributed Denial of Service (DDoS) Open Threat Signaling Requirements
draft-ietf-dots-requirements-13 draft-ietf-dots-requirements-14
Abstract Abstract
This document defines the requirements for the Distributed Denial of This document defines the requirements for the Distributed Denial of
Service (DDoS) Open Threat Signaling (DOTS) protocols enabling Service (DDoS) Open Threat Signaling (DOTS) protocols enabling
coordinated response to DDoS attacks. coordinated response to DDoS attacks.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 11, 2018. This Internet-Draft will expire on August 12, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 18 skipping to change at page 2, line 18
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Context and Motivation . . . . . . . . . . . . . . . . . 2 1.1. Context and Motivation . . . . . . . . . . . . . . . . . 2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. General Requirements . . . . . . . . . . . . . . . . . . 6 2.1. General Requirements . . . . . . . . . . . . . . . . . . 6
2.2. Signal Channel Requirements . . . . . . . . . . . . . . . 7 2.2. Signal Channel Requirements . . . . . . . . . . . . . . . 7
2.3. Data Channel Requirements . . . . . . . . . . . . . . . . 12 2.3. Data Channel Requirements . . . . . . . . . . . . . . . . 12
2.4. Security Requirements . . . . . . . . . . . . . . . . . . 13 2.4. Security Requirements . . . . . . . . . . . . . . . . . . 13
2.5. Data Model Requirements . . . . . . . . . . . . . . . . . 14 2.5. Data Model Requirements . . . . . . . . . . . . . . . . . 14
3. Congestion Control Considerations . . . . . . . . . . . . . . 16 3. Congestion Control Considerations . . . . . . . . . . . . . . 15
3.1. Signal Channel . . . . . . . . . . . . . . . . . . . . . 16 3.1. Signal Channel . . . . . . . . . . . . . . . . . . . . . 15
3.2. Data Channel . . . . . . . . . . . . . . . . . . . . . . 16 3.2. Data Channel . . . . . . . . . . . . . . . . . . . . . . 16
4. Security Considerations . . . . . . . . . . . . . . . . . . . 16 4. Security Considerations . . . . . . . . . . . . . . . . . . . 16
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . 19 8.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
skipping to change at page 7, line 27 skipping to change at page 7, line 27
exchange. exchange.
GEN-004 Mitigation Hinting: DOTS clients may have access to attack GEN-004 Mitigation Hinting: DOTS clients may have access to attack
details which can be used to inform mitigation techniques. details which can be used to inform mitigation techniques.
Example attack details might include locally collected Example attack details might include locally collected
fingerprints for an on-going attack, or anticipated or active fingerprints for an on-going attack, or anticipated or active
attack focal points based on other threat intelligence. DOTS attack focal points based on other threat intelligence. DOTS
clients MAY send mitigation hints derived from attack details to clients MAY send mitigation hints derived from attack details to
DOTS servers, in the full understanding that the DOTS server MAY DOTS servers, in the full understanding that the DOTS server MAY
ignore mitigation hints. Mitigation hints MAY be transmitted ignore mitigation hints. Mitigation hints MAY be transmitted
across either signal or data channel. DOTS server treatment of across either signal or data channel. DOTS server handling of
mitigation hints, and how such hints shape mitigation, are mitigation hints is implementation-specific.
implementation-specific.
GEN-005 Loop Handling: In specific scenarios, it may be possible for GEN-005 Loop Handling: In certain scenarios, typically involving
communication between DOTS agents to loop, for example as a result misconfiguration of DNS or routing policy, it may be possible for
of misconfiguration or aggressive caching. Signal and data communication between DOTS agents to loop. Signal and data
channel implementations should be prepared to detect and terminate channel implementations should be prepared to detect and terminate
such loops to prevent service disruption. such loops to prevent service disruption.
2.2. Signal Channel Requirements 2.2. Signal Channel Requirements
SIG-001 Use of Common Transport Protocols: DOTS MUST operate over SIG-001 Use of Common Transport Protocols: DOTS MUST operate over
common widely deployed and standardized transport protocols. common widely deployed and standardized transport protocols.
While connectionless transport such as the User Datagram Protocol While connectionless transport such as the User Datagram Protocol
(UDP) [RFC0768] SHOULD be used for the signal channel, the (UDP) [RFC0768] SHOULD be used for the signal channel, the
Transmission Control Protocol (TCP) [RFC0793] MAY be used if Transmission Control Protocol (TCP) [RFC0793] MAY be used if
 End of changes. 7 change blocks. 
12 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/