IETF Logo Mail Archive

[sacm] Hackathon Goals and Stretch Goals

Adam Montville <adam.w.montville@gmail.com> Tue, 02 May 2017 21:42 UTC

Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75B8127876 for <sacm@ietfa.amsl.com>; Tue, 2 May 2017 14:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 biMx5JrA4KBQ for <sacm@ietfa.amsl.com>; Tue, 2 May 2017 14:42:49 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D176126579 for <sacm@ietf.org>; Tue, 2 May 2017 14:40:16 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id o5so23324125ith.1 for <sacm@ietf.org>; Tue, 02 May 2017 14:40:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=zsgJqkypNkR7w5zKzVmTWQihirYFRb6qfW5wxySuKgM=; b=S0riese1nPVMO+k+Y9OF02rLBAtMCO6jJpWQqnoWkzBKzG6H6LzWYnUbhLYmBK3RV7 Kr0sEdabHH1CME0C1jXq/6364sF4Rg+stOT6u9/wwUdhZCWiwS3u6ztv+uy2F48ZQs73 BcXDjALkLA92LEGvAhMvvxqxktGPJoZ2ZVHPlIgIMEyWc5qj/ghtnyvSZzjTwcfiSsrq nHwG3Y1mvyoOxqCDN4UePS4pZPKq/60cD1HqdxA6B6NzN19IgrSIGghJOi3s/FkSFyc6 BzstcV1zsQ1bdfHfcowrlmiSXHlniUWcY5p4iSSHqDgPaFUa8AMKeRXVnU6jBWJbV9z8 wlHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zsgJqkypNkR7w5zKzVmTWQihirYFRb6qfW5wxySuKgM=; b=AZxJjX4cbkuOLxtK+GGrWtYZTtQrIwm7acELJXqzsUJDkQV5QrThhhmzowg6tRuXgE uynueWbqF1VL2AALkZWx3tYKZ4aKf6Ub5LyvdqLF+mitBFWa3TFPKKtUQPU8nce22zf4 8RZcEMEofJyE70jSMnGcAqHmGYMIUK0XtHa4mft6P+Fchim2Hr6gbrqqik93fhMAbcZi 1wBe2xbk2QQ9kIsjsciX8YqyxlMkuKAWl24ckD76rEVQ/enKZQLP0LVeLD4LF0z0gGF1 VRLKW4YdevmDbFjjdggGecElqXuPd5x8/ploDG8lvZ9stwEVUifM5sxkJDzLBFSlt/Jv RYKg==
X-Gm-Message-State: AN3rC/6WtV3tfXHYkRTtNtjnoQBIPUMtZ1Vp9G9u9+wmQ4mIJvMB9+6G ZmZlvBkl0wEDeQAIyXnmMaJQNotrURS1
X-Received: by 10.36.39.16 with SMTP id g16mr15378415ita.13.1493761215060; Tue, 02 May 2017 14:40:15 -0700 (PDT)
MIME-Version: 1.0
From: Adam Montville <adam.w.montville@gmail.com>
Date: Tue, 02 May 2017 21:40:04 +0000
Message-ID: <CACknUNUhqqdumk1wombsAha0TQS4O4dNpajUs2Ak4jWDWZHXaA@mail.gmail.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="001a1146b32a9a5e8a054e916296"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/7Xxgr32pQDQybHbprgpgR6lZUCA>
Subject: [sacm] Hackathon Goals and Stretch Goals
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 May 2017 21:42:51 -0000

All:

Last week Dave sent a list of milestones to the list. The first of which
was for the WG to define some goals for the IETF 99 hackathon. I can see at
least one primary goal with at least one stretch goal. The primary goal is
to have running code demonstrating the basic/ideal case through our
vulnerability scenario, where a new vulnerability is discovered and we need
to reach out all the way to the endpoint to determine whether it is in fact
vulnerable. A stretch goal might be to have running code demonstrating a
"monitor for this vulnerability from now on" capability (I'm sure I'm not
stating that as well as I could).

Does anyone have additional goals? Or, are there better ways to state these
particular goals (there probably are)?

Kind regards,

Adam

v2.23.0 | Report a Bug | By Email