I-D Action: draft-teague-dots-protocol-02.txt

internet-drafts@ietf.org Wed, 15 February 2017 18:49 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC8E12954A for <i-d-announce@ietf.org>; Wed, 15 Feb 2017 10:49:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-teague-dots-protocol-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148718458404.28198.1152326453597771995.idtracker@ietfa.amsl.com>
Date: Wed, 15 Feb 2017 10:49:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/Ld5xd1tIS-YS97WNk7CC3UoaBTg>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 18:49:44 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : DDoS Open Threat Signaling Protocol
        Authors         : Nik Teague
                          Andrew Mortensen
	Filename        : draft-teague-dots-protocol-02.txt
	Pages           : 30
	Date            : 2017-02-15

Abstract:
   This document describes Distributed-Denial-of-Service (DDoS) Open
   Threat Signaling (DOTS), a protocol for requesting and managing
   mitigation of DDoS attacks.

   DOTS mitigation requests over the signal channel permit domains to
   signal the need for help fending off DDoS attacks, setting the scope
   and duration of the requested mitigation.  Elements called DOTS
   servers field the signals for help, and enable defensive
   countermeasures to defend against the attack reported by the clients,
   reporting the status of the delegated defense to the requesting
   clients.  DOTS clients additionally may use a reliable data channel
   to manage filters and black- and white-lists to restrict or allow
   traffic to the clients' domains arbitrarily.  The DOTS signal channel
   may operate over UDP [RFC0768] and if necessary TCP [RFC0793].  This
   revision discusses a transport-agnostic approach to this channel,
   focusing on the message exchanges and delegating transport specifics
   to other documents.  Discussion of the reliable data channel may be
   found in [I-D.reddy-dots-data-channel].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-teague-dots-protocol/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-teague-dots-protocol-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-teague-dots-protocol-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/