Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
draft-ietf-dots-signal-filter-control-07

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: kaduk@mit.edu, frank.xialiang@huawei.com, draft-ietf-dots-signal-filter-control@ietf.org, The IESG <iesg@ietf.org>, Liang Xia <frank.xialiang@huawei.com>, rfc-editor@rfc-editor.org, dots-chairs@ietf.org, Valery Smyslov <valery@smyslov.net>, dots@ietf.org
Subject: Protocol Action: 'Controlling Filtering Rules Using Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel' to Proposed Standard (draft-ietf-dots-signal-filter-control-07.txt)

The IESG has approved the following document:
- 'Controlling Filtering Rules Using Distributed Denial-of-Service Open
   Threat Signaling (DOTS) Signal Channel'
  (draft-ietf-dots-signal-filter-control-07.txt) as Proposed Standard

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-signal-filter-control/

Ballot Text

Technical Summary

This document specifies an extension to the DOTS signal channel protocol so that DOTS clients
can control their filtering rules when an attack mitigation is active. Particularly, this extension
allows a DOTS client to activate or de-activate existing filtering rules (but not create new ones)
during a DDoS attack.

Working Group Summary

The working group has the consensus to publish it as a Proposed Standard since it is a protocol
draft, which is stable in technical aspect and has enough community interest to be considered as valuable.

Document Quality

The issue which led to the extension defined in the draft was found in IETF103
DOTS hackathon:
https://datatracker.ietf.org/meeting/103/materials/slides-103-dots-interop-report-from-ietf-103-hackathon-00.
No controversial issues was raised during the development of the document. And
since then, the specification went through many iterations to take into
account the comments from the WG. Right now, two interoperable implementations
are available (NTT, NCC) and the interoperability testing (e.g., IETF104 at
https://datatracker.ietf.org/meeting/104/materials/slides-104-dots-interoperability-and-hackathon-report-00)
has justified and improved the specification.

Personnel

The Document Shepherd is Liang Xia.
The Responsible AD is Benjamin Kaduk.

RFC Editor Note