[I2nsf] FW: [Sdn] new draft on SDN for DDoS mitigation

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 13 August 2015 08:45 UTC

X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 13 Aug 2015 04:45:41 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Thu, 13 Aug 2015 10:45:40 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [Sdn] new draft on SDN for DDoS mitigation
Thread-Index: AQHQ1QEte5zztIXNB0GlPAL7BGuG0Z4Jnh5w
Date: Thu, 13 Aug 2015 08:45:39 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5CAF9ABD@AZ-FFEXMB04.global.avaya.com>
References: <55CB473A.3010505@mti-systems.com>
In-Reply-To: <55CB473A.3010505@mti-systems.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.47]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2nsf/8xRV2qbcb6Ms6_O21oIJwWy7TCc>
Cc: Wesley Eddy <wes@mti-systems.com>
Subject: [I2nsf] FW: [Sdn] new draft on SDN for DDoS mitigation
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2015 08:45:44 -0000

Hi,

>From the SDNRG mail list. 

This I-D is interesting, I believe - looks like another I2NSF use case. 

Regards,

Dan


> -----Original Message-----
> From: sdn [mailto:sdn-bounces@mail.ietf.org] On Behalf Of Wesley Eddy
> Sent: Wednesday, August 12, 2015 4:17 PM
> To: sdn@irtf.org
> Cc: gclark mti-systems.com; Justin Dailey
> Subject: [Sdn] new draft on SDN for DDoS mitigation
> 
> 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
>

[I2nsf] FW: [Sdn] new draft on SDN for DDoS mitig… Romascanu, Dan (Dan)