IETF Logo Mail Archive

Re: [quicwg/base-drafts] Can an H3 server send a response before receiving the SETTINGS frame? (#2726)

Kazuho Oku <notifications@github.com> Mon, 20 May 2019 15:30 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 9200F12008F for <quic-issues@ietfa.amsl.com>; Mon, 20 May 2019 08:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.393
X-Spam-Level:
X-Spam-Status: No, score=-6.393 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-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 zebVzWfIM5BU for <quic-issues@ietfa.amsl.com>; Mon, 20 May 2019 08:30:15 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FE761200E5 for <quic-issues@ietf.org>; Mon, 20 May 2019 08:30:15 -0700 (PDT)
Date: Mon, 20 May 2019 08:30:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558366214; bh=m3s3wDZHiisIo+laCU8iaviYV4HFkMGBz6jaX/5vUOw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XUFvtgRr8GRVG84BfDQYTqC3aSQZ87gDHgTIiYKCbos3IvsvMqmcr/9ALzThfz6jc RISC2OVoUXX3nkeV2D//oElSMbguN1WxvePE49mCJwys8YXPC+uFWyYpSX47Nr3XsM 8sfSHwoyn/adM9NqBdE+Aza1ywzrjuqQM4z2YRso=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4QZPSHGEQUNNRHXYV2575INEVBNHHBVF6KIQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2726/494036891@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2726@github.com>
References: <quicwg/base-drafts/issues/2726@github.com>
Subject: Re: [quicwg/base-drafts] Can an H3 server send a response before receiving the SETTINGS frame? (#2726)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce2c8069f675_76053f93f74cd9645345"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/V64pk948sOCjTG7RfrnVs-IovMk>
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: Mon, 20 May 2019 15:30:17 -0000

It's my understanding that the endpoints (both the server and the client) can make that call (i.e. either wait for SETTINGS before sending a HTTP message, or send the HTTP message right away sacrificing some efficiency).

>> Each side MUST initiate a single control stream at the beginning of the connection and send its SETTINGS frame as the first frame on this stream.
> This allows endpoints to defer sending the SETTINGS indefinitely (as long as they don't send anything else on the control stream).

If the current sentence sounds unclear, it might be worth rephrasing it to "Each side MUST initiate a single control stream and send its SETTINGS frame as the first frame on this stream at the beginning of the connection".

-- 
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/2726#issuecomment-494036891

v2.23.0 | Report a Bug | By Email