IETF Logo Mail Archive

Re: [quicwg/base-drafts] Auth48: H3 is like H2 but uses QUIC, we get it (Issue #4946)

Lucas Pardue <notifications@github.com> Fri, 01 April 2022 18:42 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015F63A1886 for <quic-issues@ietfa.amsl.com>; Fri, 1 Apr 2022 11:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 myr-yhjP30PY for <quic-issues@ietfa.amsl.com>; Fri, 1 Apr 2022 11:42:25 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E427C3A1869 for <quic-issues@ietf.org>; Fri, 1 Apr 2022 11:42:24 -0700 (PDT)
Received: from github-lowworker-c73936b.ash1-iad.github.net (github-lowworker-c73936b.ash1-iad.github.net [10.56.112.13]) by smtp.github.com (Postfix) with ESMTP id D19BF600FC0 for <quic-issues@ietf.org>; Fri, 1 Apr 2022 11:42:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1648838543; bh=KnKV5sWXNQYdIecQIB0CcYvYUj4CK4NF6plVSfDj5RY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hUPGBxObdz63wAWYS7LL9kXRMXNOLYiSSjLkR/ZKbQraqHK/nNvuquzsDsvf6HGe2 qprBpjsEKjZecyI/vsSJONtRmfkkAV7+9Nxe22vjpYbtXA+oqLXrKauAdbpIXW6d+h SfD8LuYa2U0KmXJ2ydJaWM+x03CKtHI4GvdLvbl4=
Date: Fri, 01 Apr 2022 11:42:23 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7AKFY7Q4EA72VDQ76AKR5A7EVBNHHEHTM6JM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4946/1086218892@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4946@github.com>
References: <quicwg/base-drafts/issues/4946@github.com>
Subject: Re: [quicwg/base-drafts] Auth48: H3 is like H2 but uses QUIC, we get it (Issue #4946)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_6247478fc4461_7ab1c6fc78331e"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/xsvyDJAnaNezE6Akrief5b1M46g>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2022 18:42:28 -0000

Marginal: Section 4.1.1 and 4.1.1.1 seems to have some egregious use of phrasing similar to "Like HTTP/2, ..." or "as in HTTP/2". 

You could possibly condense these to a sentence such as "Like HTTP/2, HTTP/3 has additional considerations related to use of characters in field names, the Connect header field, and pseudo-header fields". That could be inserted into to the second paragraph of 4.1.1 (thus breaking the para so the next one starts with "Characters in field names").

-- 
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4946#issuecomment-1086218892
You are receiving this because you are subscribed to this thread.

Message ID: <quicwg/base-drafts/issues/4946/1086218892@github.com>

v2.8.7 | Report a Bug | By Email