[Sdn] new draft on SDN for DDoS mitigation

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

Return-Path: <wes@mti-systems.com>
X-Original-To: sdn@ietfa.amsl.com
Delivered-To: sdn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFABB1B2D7A for <sdn@ietfa.amsl.com>; Wed, 12 Aug 2015 06:16:56 -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 WeTpV87lT7m1 for <sdn@ietfa.amsl.com>; Wed, 12 Aug 2015 06:16:55 -0700 (PDT)
Received: from atl4mhob13.myregisteredsite.com (atl4mhob13.myregisteredsite.com [209.17.115.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3C98B1B2D79 for <sdn@irtf.org>; Wed, 12 Aug 2015 06:16:54 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob13.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t7CDGrqN029268 for <sdn@irtf.org>; Wed, 12 Aug 2015 09:16:53 -0400
Received: (qmail 18823 invoked by uid 0); 12 Aug 2015 13:16:53 -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:16:53 -0000
To: sdn@irtf.org
From: Wesley Eddy <wes@mti-systems.com>
X-Enigmail-Draft-Status: N1110
Organization: MTI Systems
Message-ID: <55CB473A.3010505@mti-systems.com>
Date: Wed, 12 Aug 2015 09:16:42 -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/sdn/tTw0ncVZfIuEDfFWpPl2K-GdUr0>
Cc: "gclark mti-systems.com" <gclark@mti-systems.com>, Justin Dailey <Justin@mti-systems.com>
Subject: [Sdn] new draft on SDN for DDoS mitigation
X-BeenThere: sdn@mail.ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List to Discuss SDN Research Group in the IRTF <sdn.mail.ietf.org>
List-Unsubscribe: <https://mail.ietf.org/mailman/options/sdn>, <mailto:sdn-request@mail.ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sdn/>
List-Post: <mailto:sdn@mail.ietf.org>
List-Help: <mailto:sdn-request@mail.ietf.org?subject=help>
List-Subscribe: <https://mail.ietf.org/mailman/listinfo/sdn>, <mailto:sdn-request@mail.ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2015 13:16:57 -0000

Hello, we wanted to make people aware of a new I-D that uses SDN (or
more specifically OpenFlow) as a tool to improve DDoS mitigation:

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

The interesting part of this for SDNRG is probably the sub-controller
concept, which is how we allow OpenFlow to be used inter-domain (for
customers to control aspects of their ISP's network), and the three-
stage organization of flow tables.

The content is fairly specific to DDoS, but could be extended and
generalized for other uses.

Much of the other interdomain SDN work has the ISPs setting up virtual
networks for each customer, or slice-based constructions, which are not
required by this sub-controller approach.  It may be of interest as
an alternative construction with its own set of advantages and
disadvantages in comparison to other interdomain SDN approaches.

We're eager to hear your comments, criticisms, and questions.

-- 
Wes Eddy
MTI Systems