DDoS Open Threat Signaling (DOTS) Architecture
draft-ietf-dots-architecture-18

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Roman Danyliw <rdd@cert.org>, Valery Smyslov <valery@smyslov.net>, valery@smyslov.net, rdd@cert.org, The IESG <iesg@ietf.org>, rfc-editor@rfc-editor.org, draft-ietf-dots-architecture@ietf.org, dots@ietf.org, dots-chairs@ietf.org
Subject: Document Action: 'Distributed-Denial-of-Service Open Threat Signaling (DOTS) Architecture' to Informational RFC (draft-ietf-dots-architecture-18.txt)

The IESG has approved the following document:
- 'Distributed-Denial-of-Service Open Threat Signaling (DOTS)
   Architecture'
  (draft-ietf-dots-architecture-18.txt) as Informational RFC

This document is the product of the DDoS Open Threat Signaling Working Group.

The IESG contact persons are Benjamin Kaduk and Roman Danyliw.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-architecture/

Ballot Text

Technical Summary

   This document describes an architecture for establishing and
   maintaining Distributed Denial of Service (DDoS) Open Threat
   Signaling (DOTS) within and between domains.  The document does not
   specify protocols or protocol extensions, instead focusing on
   defining architectural relationships, components and concepts used in
   a DOTS deployment.

Working Group Summary

The WG adopted this draft in July 2016 (-00) from an individual submission which was first published in March 2016.  This draft has evolved through substantial WG discussions to the current -10 version. Feedback on this draft came from vendors, operators and the current implementers of the signal and data channels drafts that realize this architecture.

This draft iteratively evolved with further refinement of the use cases (draft-ietf-dots-use-cases); increased maturity of the signal (draft-ietf-dots-use-cases) and data (draft-ietf-dots-data-channel) channel; and corresponding interop feedback.  The notable evolutions of the draft were:

** Multi-homing architecture considerations were added and refined starting in -02, but ultimately removed by WG consensus and added to a separate document, draft-ietf-dots-multihoming-01.

** Addition of a construct for recursive signaling came in -04 

** Guidance around handling environment with Network Address Translation first emerged in -06.

The WG convened a WGLC on -08 of the draft on November 27, 2018 (https://mailarchive.ietf.org/arch/msg/dots/DR2Pu9EzJXJn5uOQ13ien9vvqCY).  This feedback resulted in the publication of -09 and -10.  Key changes in these revisions included consistently clarifying the definition of a session; referencing a specific requirements (in draft-ietf-dots-requirements) and needed updates identified during the review of the signal channel (draft-ietf-dots-requirements).  Issues identified during AD, shepherd, and directorate review were addressed in -11 to -16.

The WG reached consensus to publish this draft as an Informational document consistent with the charter and milestones.  Publication of this draft has been intentionally delayed to coincide with the publication of the signal and data channel specifications 

Document Quality

This document was informed by four implementations of the underlying protocols (draft-ietf-dots-signal-channel and draft-ietf-dots-data-channel) that manifest this architecture (open source go-dots from NTT and  proprietary demos from NCC, Huawei and Netscout Arbor). 

It has been subjected to substantial review from the community of interest.

Personnel

The document shepherd is Valery Smyslov. 
The responsible Area Director is Roman Danyliw.

RFC Editor Note