[Dots] use of SDN for DDoS mitigation

Wesley Eddy <wes@mti-systems.com> Wed, 12 August 2015 13:25 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C86A21B2DB7 for <dots@ietfa.amsl.com>; Wed, 12 Aug 2015 06:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFQUrZYktdO5 for <dots@ietfa.amsl.com>; Wed, 12 Aug 2015 06:25:37 -0700 (PDT)
Received: from atl4mhob03.myregisteredsite.com (atl4mhob03.myregisteredsite.com [209.17.115.41]) by ietfa.amsl.com (Postfix) with ESMTP id D16F81B2DBC for <dots@ietf.org>; Wed, 12 Aug 2015 06:25:36 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t7CDPYQx012824 for <dots@ietf.org>; Wed, 12 Aug 2015 09:25:34 -0400
Received: (qmail 2459 invoked by uid 0); 12 Aug 2015 13:25:34 -0000
X-TCPREMOTEIP: 24.166.126.82
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.0.135?) (wes@mti-systems.com@24.166.126.82) by 0 with ESMTPA; 12 Aug 2015 13:25:34 -0000
To: "dots@ietf.org" <dots@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
X-Enigmail-Draft-Status: N1110
Organization: MTI Systems
Message-ID: <55CB494A.9020706@mti-systems.com>
Date: Wed, 12 Aug 2015 09:25:30 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/-1hoKo4GOqbRuOm417GnONwRv8o>
Cc: "gclark mti-systems.com" <gclark@mti-systems.com>, Justin Dailey <Justin@mti-systems.com>
Subject: [Dots] use of SDN for DDoS mitigation
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2015 13:25:42 -0000

This is not strictly within the scope of the DOTS charter, but
because it's related to DDoS mitigation, we thought it might
be of interest to the DOTS list.

This draft was posted to the SDNRG, and discusses use of OpenFlow
interdomain, for delegating control of ISP network filtering to
customers:

https://datatracker.ietf.org/doc/draft-eddy-sdnrg-customer-filters/

We're eager to hear your comments, criticisms, and questions, but I
assume that the DOTS chairs would like this to be offlist (or on the
SDNRG list) since it is not really in-scope for DOTS and might be a
distraction from the chartered work.

-- 
Wes Eddy
MTI Systems