IETF Logo Mail Archive

Re: [quicwg/base-drafts] Server's SETTINGS can be omitted in 0-RTT (#1809)

Martin Thomson <notifications@github.com> Fri, 28 September 2018 20:35 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 C08F212F1A2 for <quic-issues@ietfa.amsl.com>; Fri, 28 Sep 2018 13:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Level:
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 D3REcE-OFWdf for <quic-issues@ietfa.amsl.com>; Fri, 28 Sep 2018 13:35:28 -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 23F8E127B92 for <quic-issues@ietf.org>; Fri, 28 Sep 2018 13:35:28 -0700 (PDT)
Date: Fri, 28 Sep 2018 13:35:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538166927; bh=h52ja2wwzKvmhtnu+KP2Y+kPmNtryfo24sXFR8JAT2E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WuyFiuGDH04Qqivq7hlirshn2fwtqw7nqjQkJDCm1SuJSjJHhvqe508iM0zy5Ch8A k0nLvByapgJs5M4K/qQyA2wo5mcn1QMaWFIWeHGOwruamf6JMSz49LdGg10YaBDRP7 MGzg4GgBTiWgRn5aHh1UNXeizOBNSHvGiG4wBhuk=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab065974ae8253057d6306ef42fcc71b22aac11b2b92cf0000000117c6528f92a169ce15bcc36c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1809/425558307@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1809@github.com>
References: <quicwg/base-drafts/issues/1809@github.com>
Subject: Re: [quicwg/base-drafts] Server's SETTINGS can be omitted in 0-RTT (#1809)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bae908f4c813_357a3fac286d45c01500c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/bbxu9xTLZ6igvmRN2CJfkHqiPns>
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, 28 Sep 2018 20:35:30 -0000

That's an implementation choice.  I think that #1808 covers things well enough.  I don't see any reason to - for example - force the client to wait on SETTINGS before writing requests in 1-RTT, for example.

-- 
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/1809#issuecomment-425558307

v2.29.0 | Report a Bug | By Email | System Status