Re: [quicwg/base-drafts] Default settings in HTTP (#2038)
Mike Bishop <notifications@github.com> Mon, 26 November 2018 20:04 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 2EBB0130FAE for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 12:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 R0fNFXPd5nIy for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 12:04:04 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3589130E17 for <quic-issues@ietf.org>; Mon, 26 Nov 2018 12:04:04 -0800 (PST)
Date: Mon, 26 Nov 2018 12:04:02 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543262642; bh=FWItygAZ80b69BxGLOfbio5bbRsZPqpjnq6M/10/d6Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pQTtEX9qK2rOFCS4G5kYWgu+qr1iGfaPg5P5q+xZmh6A7duI7qWp0nrtrUogeDiz6 5470SOanhEbJXg6XcTFG2NfAvjxW708PCnIO6oLue+h7KX25tXC7dv9dokek06yybN wOmDiBFavQsSUm3/1xGTJ3bwH6WjrVRknxrTHWB4=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab85dd341a459ae519d7aaa0585fa4e8c17d6dce6492cf00000001181413b292a169ce16d8e664@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2038/c441778525@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2038@github.com>
References: <quicwg/base-drafts/pull/2038@github.com>
Subject: Re: [quicwg/base-drafts] Default settings in HTTP (#2038)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bfc51b2ec395_4dfe3f87b14d45b81045b1"; 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/cNmiInReR_-NxDECqHtbXZJI-Sc>
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, 26 Nov 2018 20:04:06 -0000
You're still required to send/consume SETTINGS -- you're just allowed to use a basic version of the protocol for the (hopefully very brief) period where you haven't seen it yet. I'm dubious anyone would decide it's better to send an empty SETTINGS frame and continue using the defaults forever, certainly not to the point that extensibility withers. (And hopefully extensions will be compelling enough that they justify sending and looking for a setting.) -- 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/pull/2038#issuecomment-441778525
- Re: [quicwg/base-drafts] Default settings in HTTP… Ryan Hamilton
- [quicwg/base-drafts] Default settings in HTTP (#2… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Martin Thomson
- Re: [quicwg/base-drafts] Default settings in HTTP… Lucas Pardue
- Re: [quicwg/base-drafts] Default settings in HTTP… Kazuho Oku
- Re: [quicwg/base-drafts] Default settings in HTTP… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Default settings in HTTP… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Default settings in HTTP… MikkelFJ
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… afrind
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Lucas Pardue
- Re: [quicwg/base-drafts] Default settings in HTTP… Martin Thomson
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Lucas Pardue
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop
- Re: [quicwg/base-drafts] Default settings in HTTP… Mike Bishop