[secdir] Secdir last call review of draft-ietf-masque-h3-datagram-09

David Mandelberg via Datatracker <noreply@ietf.org> Sat, 28 May 2022 02:02 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: David Mandelberg via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-masque-h3-datagram.all@ietf.org, last-call@ietf.org, masque@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165370335586.6065.7293070667026764807@ietfa.amsl.com>
Reply-To: David Mandelberg <david@mandelberg.org>
Date: Fri, 27 May 2022 19:02:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/wfAmjZ8L8U8ohOI01xPD03Mg5DU>
Subject: [secdir] Secdir last call review of draft-ietf-masque-h3-datagram-09

Reviewer: David Mandelberg
Review result: Ready

I did not notice any security issues with this document, and the security
considerations section seems straightforward.

(nit / question / feel free to ignore) I was a bit confused by the term "HTTP
extensions" at first, but from context, I'm guessing it's used loosely to mean
any addition to HTTP? I found RFC 2774 when I was looking to see if it meant
something specific, but I'm guessing it's not a reference to a 20+ year old
experimental RFC?

[secdir] Secdir last call review of draft-ietf-ma… David Mandelberg via Datatracker
Re: [secdir] Secdir last call review of draft-iet… David Schinazi