Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490)

Kazuho Oku <notifications@github.com> Thu, 28 June 2018 01:16 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 4167C130E75 for <quic-issues@ietfa.amsl.com>; Wed, 27 Jun 2018 18:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 GMCjq87Rhom1 for <quic-issues@ietfa.amsl.com>; Wed, 27 Jun 2018 18:16:40 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53648130E8A for <quic-issues@ietf.org>; Wed, 27 Jun 2018 18:16:40 -0700 (PDT)
Date: Wed, 27 Jun 2018 18:16:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530148599; bh=Ny+6eDtlOR5M59EITrAqwtkqEyPBO5bRLiovAlHVEDc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fc9nTUki4ISLNvHzcEgM32B/x/NetP0TW7Qf9PdheJNybnXmvvLoSLLXBZq4HJMRT VbOZKwl1KTVOwoT3g/raehP/tgViw8xtYlDalQUVkLuE8r6cdIMAEIZTMgz6z4BpeG icjp8//tIhoiWqANNm1NQY6qn9aor/WlSfGamJWI=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab51ed156af4ac408386403dd45c3a0efe0c051aef92cf00000001174bf8f792a169ce140bbcee@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1490/400879652@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1490@github.com>
References: <quicwg/base-drafts/issues/1490@github.com>
Subject: Re: [quicwg/base-drafts] Greasing for Unidirectional Stream Types (#1490)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b3436f74da53_27e02b0226616f54628cd"; 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/3SfUaZatGdv5NslpX2zjgIAXsEQ>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 28 Jun 2018 01:16:43 -0000

> A middle ground might say that stream extensions should be aware of the trade off in committing resource to data that could be ignored by the peer vs. negotiating at the cost of latency.

Yes. IMO, having a statement that suggests extensions to consider using SETTINGS for negotiation is a good idea, and that is what we have in https://httpwg.org/specs/rfc7540.html#extensibility for frames. My point is that there is no need to switch to a different approach for frames *and unidirectional streams* to be defined in hq.

-- 
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/1490#issuecomment-400879652