[Manycouches] Secdir last call review of draft-ietf-shmoo-hackathon-07

Kathleen Moriarty via Datatracker <noreply@ietf.org> Fri, 22 July 2022 22:13 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: manycouches@ietf.org
Delivered-To: manycouches@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 417C1C1527AF; Fri, 22 Jul 2022 15:13:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kathleen Moriarty via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-shmoo-hackathon.all@ietf.org, last-call@ietf.org, manycouches@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165852803726.36777.11091395442864489395@ietfa.amsl.com>
Reply-To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Date: Fri, 22 Jul 2022 15:13:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/wRHKXM9IhvBixl6qTOQDJqfguTI>
Subject: [Manycouches] Secdir last call review of draft-ietf-shmoo-hackathon-07
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "List for discussion of remote meeting attendance and virtual IETF meetings, as well as for SHMOO working group" <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2022 22:13:57 -0000

Reviewer: Kathleen Moriarty
Review result: Ready

I am seeing that this draft is now listed as approved, announcement to be sent
with a revision needed. Sorry for the late review.

This document contains the formalities of the Hack-a-thon event, including use
of tools as well as setting expectations for the event. As such many security
considerations such as secure coding practices (e.g. references to SafeCode or
OWASP) and recommendations are out-of-scope. From a security perspective, this
document is ready for publication.