Roman Danyliw's Yes on draft-ietf-quic-http-33: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Tue, 19 January 2021 23:28 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D24F3A1879; Tue, 19 Jan 2021 15:28:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-quic-http@ietf.org, quic-chairs@ietf.org, quic@ietf.org, quic-chairs@ietf.org, lucaspardue.24.7@gmail.com
Subject: Roman Danyliw's Yes on draft-ietf-quic-http-33: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <161109891722.24613.15942373190818360435@ietfa.amsl.com>
Date: Tue, 19 Jan 2021 15:28:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xxpTdfz_YCy8c1lsyyePm1RqP8E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 23:28:37 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-quic-http-33: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-quic-http/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The work on this document and its companions is greatly appreciated! Thank you to Hilarie Orman for the SECDIR review. ** Section 3.1. “The host must be listed either as the CN field …”, why not a normative MUST just as there is in the next sentence around the required use of iPAddress? ** Section 3.3 Per “Once a connection exists to a server endpoint, this connection MAY be reused for requests with multiple different URI authority components”, it might be worth repeating here that in cases of https, changes in the authority components still need to occur within the bounds of the certificate validation practices noted in Section 3.1 and in Section 4.3.4 of draft-ietf-httpbis-semantics.
- Roman Danyliw's Yes on draft-ietf-quic-http-33: (… Roman Danyliw via Datatracker
- Re: Roman Danyliw's Yes on draft-ietf-quic-http-3… Lucas Pardue