[quicwg/base-drafts] Handling of Frames Inappropriate for Unidirectional Streams (#1047)
martinduke <notifications@github.com> Tue, 09 January 2018 20:39 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 A0C2812708C for <quic-issues@ietfa.amsl.com>; Tue, 9 Jan 2018 12:39:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.595
X-Spam-Level:
X-Spam-Status: No, score=-5.595 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 j6MAPWM1qUqT for <quic-issues@ietfa.amsl.com>; Tue, 9 Jan 2018 12:39:23 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF2E712D871 for <quic-issues@ietf.org>; Tue, 9 Jan 2018 12:39:22 -0800 (PST)
Date: Tue, 09 Jan 2018 12:39:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1515530362; bh=2eaAKuAy27gHrjYPAPrsccSplWImdBRBGIaAM8VfvDw=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Iql2Oues6GD4MNeH4j49PK/VsLQVtxP1IgJDvodleoDnVFBfECd46nuk1DgqsXQ8l ptbTmgG0LiEwJQAFhxjyIcSEegBaC2HZoWmp2h8JbaTc+T0AqBOj0Tezsnrlbn8atJ SernE5CE71TPjj7H22hdz7s+aBm6sFL+qDJ3z/7k=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb7803894066f45ec805bc9798e61199566d9992a92cf00000001166cea7992a169ce111ead73@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1047@github.com>
Subject: [quicwg/base-drafts] Handling of Frames Inappropriate for Unidirectional Streams (#1047)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a552879f2249_45d2afbe81c2ec4960e9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/UghFWjZOmGhd-u7rr9aJ9AuW2cw>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 09 Jan 2018 20:39:24 -0000
Something I can't seem to find in the transport doc: if I have a unidirectional stream, various frame types don't make any sense. Send-only streams shouldn't see STREAM, STREAM_BLOCKED, or RST_STREAM frames. Receive-only streams shouldn't see MAX_STREAM_DATA, STOP_SENDING There are several courses of action here: - blow up the connection with error code XXXX* - blow up the stream with error code XXXX* - drop the whole containing packet as somehow compromised, and continue - ignore the frame and continue. * I think there's a decent case for STREAM_DIRECTION_ERROR or something similar. Early responders on the mailing list thought it should be a fatal connection error. I don't have a strong opinion but we should document the correct behavior. -- 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/1047
- [quicwg/base-drafts] Handling of Frames Inappropr… martinduke
- Re: [quicwg/base-drafts] Handling of Frames Inapp… ianswett
- Re: [quicwg/base-drafts] Handling of Frames Inapp… MikkelFJ
- Re: [quicwg/base-drafts] Handling of Frames Inapp… MikkelFJ
- Re: [quicwg/base-drafts] Handling of Frames Inapp… Martin Thomson
- Re: [quicwg/base-drafts] Handling of Frames Inapp… janaiyengar
- Re: [quicwg/base-drafts] Handling of Frames Inapp… Martin Thomson
- Re: [quicwg/base-drafts] Handling of Frames Inapp… martinduke
- Re: [quicwg/base-drafts] Handling of Frames Inapp… janaiyengar
- Re: [quicwg/base-drafts] Handling of Frames Inapp… Martin Thomson