IETF Logo Mail Archive

Re: [quicwg/base-drafts] Ben Kaduk's HTTP/3 Comment 4 (#4779)

Mike Bishop <notifications@github.com> Fri, 22 January 2021 18:48 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 B65193A13F5 for <quic-issues@ietfa.amsl.com>; Fri, 22 Jan 2021 10:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.804
X-Spam-Level:
X-Spam-Status: No, score=-1.804 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, 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] 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 2qhxr47coYLj for <quic-issues@ietfa.amsl.com>; Fri, 22 Jan 2021 10:48:53 -0800 (PST)
Received: from smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B5B13A13FB for <quic-issues@ietf.org>; Fri, 22 Jan 2021 10:48:53 -0800 (PST)
Received: from github.com (hubbernetes-node-1fbe417.ash1-iad.github.net [10.56.120.39]) by smtp.github.com (Postfix) with ESMTPA id A191F840DE4 for <quic-issues@ietf.org>; Fri, 22 Jan 2021 10:48:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611341332; bh=oIs/WK9CqNiu2wgUaXJgavmZ4XtlJJYOjtDH9NmUvpM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YZ/UY+7znI55ETZf1ccdIFP014E89/vBuFngV3KxIb6Mfryc1feGjjpFs7A95/mX1 hFzwYJDIuHcwC92+BVtvRNiZHZHmIOZh7fWmE+TaoQRIhe+IB9PCV0CFvq66swCJRt E5ZXBxFVAR3D7YzCWLcaaN+XdFuzV6LPXTyiCgB4=
Date: Fri, 22 Jan 2021 10:48:52 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK527WP3E5652AM3RNF6C37RJEVBNHHC6GTPEA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4779/765615056@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4779@github.com>
References: <quicwg/base-drafts/issues/4779@github.com>
Subject: Re: [quicwg/base-drafts] Ben Kaduk's HTTP/3 Comment 4 (#4779)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_600b1e149eb5b_5c1a041037d7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/jJaCwWcleGnk1Y0gpTGWaan3dvw>
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, 22 Jan 2021 18:48:55 -0000

The draft currently says:

> A QUIC stream provides reliable in-order delivery of bytes, but makes no
guarantees about order of delivery with regard to bytes on other streams. On the
wire, data is framed into QUIC STREAM frames, but this framing is invisible to
the HTTP framing layer. The transport layer buffers and orders received QUIC
STREAM frames, exposing the data contained within as a reliable byte stream to
the application. Although QUIC permits out-of-order delivery within a stream,
HTTP/3 does not make use of this feature.

This seems sufficient to me.

-- 
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/4779#issuecomment-765615056

v2.23.0 | Report a Bug | By Email