[Dots] Status going into the Prague meeting

"Roman D. Danyliw" <rdd@cert.org> Sun, 19 July 2015 12:49 UTC

Return-Path: <rdd@cert.org>
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 3F4CC1ACE83 for <dots@ietfa.amsl.com>; Sun, 19 Jul 2015 05:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 fzH1FJz0_FXv for <dots@ietfa.amsl.com>; Sun, 19 Jul 2015 05:49:27 -0700 (PDT)
Received: from plainfield.sei.cmu.edu (plainfield.sei.cmu.edu [192.58.107.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 535BC1ACE7B for <dots@ietf.org>; Sun, 19 Jul 2015 05:49:27 -0700 (PDT)
Received: from timber.sei.cmu.edu (timber.sei.cmu.edu [10.64.21.23]) by plainfield.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id t6JCnQG0024327 for <dots@ietf.org>; Sun, 19 Jul 2015 08:49:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1437310166; bh=58O8n+zPWrwg54Dy9wbQGnkV9Ww65+9stqx3JnKKiTo=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version:Sender:Reply-To:Cc: In-Reply-To:References; b=iKA8V1rCH59i8PNkaPR7TGjA5Di1Fs4uU2CPtwNvSWT6MzZ9Kg+Le9t7sZF/YMi8/ f8CuisQ1Mo8tTTvrOHoqORD5/GtOjYKSwij74E7OFABL61vyuweoJhbBdfxHH6Kta0 WAVG9qOqtwbn5pkG9bbgltFtJjkIfU7L51/WzUJM=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by timber.sei.cmu.edu (8.14.4/8.14.4/1456) with ESMTP id t6JCnKhA014209 for <dots@ietf.org>; Sun, 19 Jul 2015 08:49:20 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0210.002; Sun, 19 Jul 2015 08:49:20 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: Status going into the Prague meeting
Thread-Index: AdDCIGm19UmymlV+S5+NT/S2IjDJdw==
Date: Sun, 19 Jul 2015 12:49:19 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD94BEA83@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/T2NYjynCBBhvCfcsKCdIjHaNU8Q>
Subject: [Dots] Status going into the Prague meeting
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: Sun, 19 Jul 2015 12:49:31 -0000

Hello WG!

Just a reminder, we're meeting on Tuesday at 1740 in Congress Hall II.  Unfortunately, we only got 1 hour of official time.  As you can see from the agenda [1], it's very compressed primarily focused on introducing topics leaving little time for discussion.  Our first order of business is to clarify what problems DOTS will solve -- requirements and use cases.

To date, two independent drafts [2] [3] and mailing list discussions have voiced the following use cases:

(1) "On-premise: Symmetric" (Section 3.1 of [2])
(2) "On-premise: Assymetric" (Section 3.2 of [2])
(3) "Cloud" (Section 4 of [2])
(4) "Data mining DDOS protection" (Section 3 of [3])
(5) "NFV Based Distributed DDoS Mitigation" (Section 4 of [3])
(6) "Inbound link saturation attack" (Item 1 of [5])
(7) "N/M inline mitigation through traffic redirection" (Item 2 of [5])
(8) "Virtualized DDoS mitigation appliance" (Item 3 of [5])

If you have additional use cases, please let your thoughts be known on the list.  From the list of articulated use cases, we need to discuss their suitability for the WG, overlap between each other and whether their scope is sufficiently understood.  If you have thoughts on any of those, please comment.

Another independent draft [4] introduced a set of requirements.  The specific draft and the requirements conversation overall needs further discussion.

A number of individual drafts discussing transport [6] [8] and data model [6] [7] [9] have been updated since the BOF [6] [7] and others are new [8] [9] since we met in Dallas.  While it is premature to delve into the specifics, they too can inform our requirements and use case discussion.  Please review these as well.

Safe travels to Prague!
Roman

[1] https://www.ietf.org/proceedings/93/agenda/agenda-93-dots 
[2] draft-mglt-dots-use-cases-00
[3] draft-xia-dots-extended-use-cases-00
[4] draft-mortensen-threat-signaling-requirements-00
[5] https://mailarchive.ietf.org/arch/msg/dots/QrPIV2Yl2vNaG3um3jMyrMOo8IY
[6] draft-teague-open-threat-signaling-01
[7] draft-fu-ipfix-network-security-01
[8] draft-reddy-dots-transport-00
[9] draft-reddy-dots-info-model-00