[quicwg/base-drafts] Reduce HTTP/3 editorial dependence on HTTP/2 (#3264)

"Roy T. Fielding" <notifications@github.com> Tue, 19 November 2019 02:29 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 B279B120236 for <quic-issues@ietfa.amsl.com>; Mon, 18 Nov 2019 18:29:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 hgH8HobybDmn for <quic-issues@ietfa.amsl.com>; Mon, 18 Nov 2019 18:29:27 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 641A412004E for <quic-issues@ietf.org>; Mon, 18 Nov 2019 18:29:27 -0800 (PST)
Received: from github-lowworker-275fa97.va3-iad.github.net (github-lowworker-275fa97.va3-iad.github.net [10.48.17.64]) by smtp.github.com (Postfix) with ESMTP id 97266C61F05 for <quic-issues@ietf.org>; Mon, 18 Nov 2019 18:29:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1574130566; bh=n18LMddRtAIrPxLxmok2WMvR/GBKgql7tG7BWcaQNAU=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=XTLCUGk+fs3xqtlX5VJ3nW93HyRU208QaDUFbzsCti6tsHzGWUSfspfjJ+TTQQ6wB Xe6w49xke3q1f/HV/zkqp4P5Ou4xox2U7XKkW8DXa9MVyHpQ6CiW5k5L9WyUnkwQMq CbWmEPPat5srvSa/Dt0hLD+XfinoQ0BWG93cp+jY=
Date: Mon, 18 Nov 2019 18:29:26 -0800
From: "Roy T. Fielding" <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2R6KSWSQ2ZSF4K67N34CDANEVBNHHB6RWN54@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3264@github.com>
Subject: [quicwg/base-drafts] Reduce HTTP/3 editorial dependence on HTTP/2 (#3264)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd35386876a6_16d3fc5e14cd95c866e"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: royfielding
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/WJJlv-o4COS4sUapbdzpQH2wf1w>
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: Tue, 19 Nov 2019 02:29:29 -0000

The HTTP/3 draft relies on the reader's familiarity with the HTTP/2 spec, bouncing between normative references to HTTP/2 and specification as a delta to some prior decision for HTTP/2. While that's understandable for initial development and for a section on gatewaying to h2, I don't think it is appropriate for a standards track document that will eventually (or at least likely) obsolete HTTP/2.

I don't expect readers (outside of the WG members) to have implemented h2, even if the design is based on h2. I would like all of the necessary concepts, aside from what can be normatively referenced via http-core, to be fully defined within this spec, even if that means copy and paste from h2.

(I would label this as editorial and -http)

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