Re: [quicwg/base-drafts] Tolerate unknown stream types, add greasing (#1525)
Martin Thomson <notifications@github.com> Sun, 08 July 2018 23:49 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 A442D130EDD for <quic-issues@ietfa.amsl.com>; Sun, 8 Jul 2018 16:49:21 -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 BIk3iiZh7ODq for <quic-issues@ietfa.amsl.com>; Sun, 8 Jul 2018 16:49:19 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9664A127148 for <quic-issues@ietf.org>; Sun, 8 Jul 2018 16:49:19 -0700 (PDT)
Date: Sun, 08 Jul 2018 16:49:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531093758; bh=6Qs2MNkwWDBgMkDapTYV+XZI8zU0RH00UbS4qBhzF3k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Uynn0ENp2XI7GiQYO2pprx4h5jCsT3uS9rvtSMfIVPXMDLqfulWI8ouU+LRcdQP5P O9dU3Kas8XM+pEB9img4xV1wTO1MGOSUVdQfDI5tTrfeL0PV36UJ1oTuHhSnSS9j5A hd+xhYsev9XE0fb1BeYaQ/c0YijNfJ9ljzeCVkOY=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abaf9c71ea4cf28abb4700581bbca8412a4efa392192cf00000001175a64fe92a169ce142f90e7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1525/review/135250643@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1525@github.com>
References: <quicwg/base-drafts/pull/1525@github.com>
Subject: Re: [quicwg/base-drafts] Tolerate unknown stream types, add greasing (#1525)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b42a2fe7774f_e902ad7ee64af50468151"; 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/fPpc7I6eVJ0GF9F2JlqzckLZlHY>
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: Sun, 08 Jul 2018 23:49:22 -0000
martinthomson commented on this pull request. > unknown. Implementations SHOULD NOT send stream types the peer is not already -known to support, since a stream error can be promoted to a connection error at -the peer's discretion (see {{errors}}). +known to support. Recipients of unknown stream types MAY trigger a QUIC +STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE, but MUST NOT +consider such streams to be an error of any kind. + +### Reserved Stream Types {#stream-grease} + +Stream types of the format `0x1f * N` are reserved to exercise the requirement +that unknown types be ignored. These streams have no semantic meaning, and can +be sent when application-layer padding is desired. They MAY also be sent on Padding using bogus frames might work, but there are two problems with this: 1. Not all streams use frames. 2. Padding that uses bogus unidirectional streams isn't guaranteed to be placed in the same packet as the data that it pads. -- 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/1525#discussion_r200859004
- Re: [quicwg/base-drafts] Tolerate unknown stream … Lucas Pardue
- Re: [quicwg/base-drafts] Tolerate unknown stream … Lucas Pardue
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … Lucas Pardue
- Re: [quicwg/base-drafts] Tolerate unknown stream … Lucas Pardue
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … janaiyengar
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … Martin Thomson
- Re: [quicwg/base-drafts] Tolerate unknown stream … Martin Thomson
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … Lucas Pardue
- Re: [quicwg/base-drafts] Tolerate unknown stream … Mike Bishop
- [quicwg/base-drafts] Tolerate unknown stream type… Mike Bishop
- Re: [quicwg/base-drafts] Tolerate unknown stream … Martin Thomson