[secdir] Secdir last call review of draft-ietf-httpbis-priority-10

Robert Sparks via Datatracker <noreply@ietf.org> Wed, 24 November 2021 23:01 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC513A0CC5; Wed, 24 Nov 2021 15:01:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-httpbis-priority.all@ietf.org, ietf-http-wg@w3.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.40.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163779487777.25643.17109907784762380095@ietfa.amsl.com>
Reply-To: Robert Sparks <rjsparks@nostrum.com>
Date: Wed, 24 Nov 2021 15:01:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/gFxqnvYGRbZp3a69rR_ZKy7wDro>
Subject: [secdir] Secdir last call review of draft-ietf-httpbis-priority-10
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Nov 2021 23:01:18 -0000

Reviewer: Robert Sparks
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written primarily for the benefit of the security area directors. Document
editors and WG chairs should treat these comments just like any other last call
comments.

Document reviewed: draft-ietf-httpbis-priority-10

This document is ready for publication as a Proposed Standard RFC

This document is easy to read, and appears straightforward to implement (though
there are complications for implementors that the document does a good job of
exploring). The mechanism improves the overall robustness of the HTTP protocol
family.