[Dots] WG document summary, IETF 103 call agenda, WG next steps?

Roman Danyliw <rdd@cert.org> Sat, 06 October 2018 19:45 UTC

Return-Path: <rdd@cert.org>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 950E2130DEF for <dots@ietfa.amsl.com>; Sat, 6 Oct 2018 12:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 6jNrkBi1-xio for <dots@ietfa.amsl.com>; Sat, 6 Oct 2018 12:45:26 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D66F5130DED for <dots@ietf.org>; Sat, 6 Oct 2018 12:45:25 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w96JjOxI015551 for <dots@ietf.org>; Sat, 6 Oct 2018 15:45:24 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu w96JjOxI015551
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1538855124; bh=7lwlmlxc72p/XIxWgPOGdk0AYtdaljrsB2aaTGoqhp8=; h=From:To:Subject:Date:From; b=Lbx429u4ChlqsPdUz1XsoRcDI5Mo8dIvW0wv83l+xX6SJUv9vQFvk5i791CnlUqjC wdFgR7ychjh4S/6jtEan4HHVNqTr+oqmT4qTTO5pRIXR6L+Rtqfko1D1RlgMKzNG9V 97K+MNqwzTWkXhGuTl2qhzpz45mKDi3XiALQhu5c=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id w96JjJ9Z001184 for <dots@ietf.org>; Sat, 6 Oct 2018 15:45:19 -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.0399.000; Sat, 6 Oct 2018 15:45:19 -0400
From: Roman Danyliw <rdd@cert.org>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: WG document summary, IETF 103 call agenda, WG next steps?
Thread-Index: AdRdqvQVTtrWA4LmQ0mlR3KJG9bKUA==
Date: Sat, 6 Oct 2018 19:45:18 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC014C461612@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: <https://mailarchive.ietf.org/arch/msg/dots/MzMVYYXLrC_BXEyLkBdEDzSoqKU>
Subject: [Dots] WG document summary, IETF 103 call agenda, WG next steps?
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 06 Oct 2018 19:45:28 -0000

Hello WG!

We've been making good progress on our milestones in recent months.  A summary of our current situation is as follows:

** draft-ietf-dots-data-channel -- submitted for publication
** draft-ietf-dots-signal-channel -- submitted for publication
** draft-ietf-dots-requirements -- submitted for publication
** draft-ietf-dots-architecture -- ready for publication; shepherd write-up blocked by need for IPR statements.  See https://www.ietf.org/mail-archive/web/dots/current/msg02707.html
** draft-ietf-dots-use-cases -- no open issues; awaiting draft update to issue WGLC

With IETF 103 coming the next month, we need to begin planning next steps (if any) for the WG group beyond our current milestones and how to use this meeting time (if needed).  To that end:

** If you would like time on the agenda at IETF 103, please let the chairs know  
** If you have thoughts on additional work for the WG please share your thinking

Roman