draft-ietf-dots-requirements-14.txt   draft-ietf-dots-requirements-15.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 12, 2018 Huawei Expires: March 2, 2019 Huawei
T. Reddy T. Reddy
McAfee McAfee
February 08, 2018 August 29, 2018
Distributed Denial of Service (DDoS) Open Threat Signaling Requirements Distributed Denial of Service (DDoS) Open Threat Signaling Requirements
draft-ietf-dots-requirements-14 draft-ietf-dots-requirements-15
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 12, 2018. This Internet-Draft will expire on March 2, 2019.
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 5, line 8 skipping to change at page 5, line 8
DDoS attack causing network congestion. DDoS attack causing network congestion.
DOTS signal: A concise authenticated status/control message DOTS signal: A concise authenticated status/control message
transmitted over the signal channel between DOTS agents, used to transmitted over the signal channel between DOTS agents, used to
indicate the client's need for mitigation, as well as to convey indicate the client's need for mitigation, as well as to convey
the status of any requested mitigation. the status of any requested mitigation.
Heartbeat: A message transmitted between DOTS agents over the signal Heartbeat: A message transmitted between DOTS agents over the signal
channel, used as a keep-alive and to measure peer health. channel, used as a keep-alive and to measure peer health.
Data channel: A bidirectional, mutually authentication Data channel: A bidirectional, mutually authentication communication
communincation channel between two DOTS agents used for infrequent channel between two DOTS agents used for infrequent but reliable
but reliable bulk exchange of data not easily or appropriately bulk exchange of data not easily or appropriately communicated
communicated through the signal channel under attack conditions. through the signal channel under attack conditions.
Filter: A specification of a matching network traffic flow or set of Filter: A specification of a matching network traffic flow or set of
flows. The filter will typically have a policy associated with flows. The filter will typically have a policy associated with
it, e.g., rate-limiting or discarding matching traffic [RFC4949]. it, e.g., rate-limiting or discarding matching traffic [RFC4949].
Blacklist: A list of filters indicating sources from which traffic Blacklist: A list of filters indicating sources from which traffic
should be blocked, regardless of traffic content. should be blocked, regardless of traffic content.
Whitelist: A list of filters indicating sources from which traffic Whitelist: A list of filters indicating sources from which traffic
should always be allowed, regardless of contradictory data gleaned should always be allowed, regardless of contradictory data gleaned
skipping to change at page 19, line 32 skipping to change at page 19, line 32
DOI 10.17487/RFC5952, August 2010, DOI 10.17487/RFC5952, August 2010,
<https://www.rfc-editor.org/info/rfc5952>. <https://www.rfc-editor.org/info/rfc5952>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-dots-architecture] [I-D.ietf-dots-architecture]
Mortensen, A., Andreasen, F., Reddy, T., Mortensen, A., Andreasen, F., Reddy, T.,
christopher_gray3@cable.comcast.com, c., Compton, R., and christopher_gray3@cable.comcast.com, c., Compton, R., and
N. Teague, "Distributed-Denial-of-Service Open Threat N. Teague, "Distributed-Denial-of-Service Open Threat
Signaling (DOTS) Architecture", draft-ietf-dots- Signaling (DOTS) Architecture", draft-ietf-dots-
architecture-05 (work in progress), October 2017. architecture-06 (work in progress), March 2018.
[I-D.ietf-dots-use-cases] [I-D.ietf-dots-use-cases]
Dobbins, R., Migault, D., Fouant, S., Moskowitz, R., Dobbins, R., Migault, D., Fouant, S., Moskowitz, R.,
Teague, N., Xia, L., and K. Nishizuka, "Use cases for DDoS Teague, N., Xia, L., and K. Nishizuka, "Use cases for DDoS
Open Threat Signaling", draft-ietf-dots-use-cases-09 (work Open Threat Signaling", draft-ietf-dots-use-cases-16 (work
in progress), November 2017. in progress), July 2018.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<https://www.rfc-editor.org/info/rfc3261>. <https://www.rfc-editor.org/info/rfc3261>.
[RFC7092] Kaplan, H. and V. Pascual, "A Taxonomy of Session [RFC7092] Kaplan, H. and V. Pascual, "A Taxonomy of Session
Initiation Protocol (SIP) Back-to-Back User Agents", Initiation Protocol (SIP) Back-to-Back User Agents",
RFC 7092, DOI 10.17487/RFC7092, December 2013, RFC 7092, DOI 10.17487/RFC7092, December 2013,
 End of changes. 7 change blocks. 
11 lines changed or deleted 11 lines changed or added

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