Re: [quicwg/base-drafts] What happens if you get a stream of the wrong parity? (#791)
Patrick McManus <notifications@github.com> Mon, 25 September 2017 14:47 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 41418134498 for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 07:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level:
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8, 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 QEflBMNDtvYJ for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 07:47:39 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25D09134494 for <quic-issues@ietf.org>; Mon, 25 Sep 2017 07:47:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=2P8SyBpdOQJvZnqSis5tTiXU5mw=; b=NqLvjYYM0YhdMmIm Xt6FuQehiXNI0pC0KkEpnE0ttI/UziwEA5dHHuQbOOHQotrxuYqVa/o/eXtusUjb Da+F8R7x5H8iXeUaReUxnOp9L/VXCPlYPCNKujx6/ZNg8/1WKu1B6QFs+vWv269i lTZn65cLDD+jliQlHJTPVMFfkhI=
Received: by filter0556p1mdw1.sendgrid.net with SMTP id filter0556p1mdw1-6453-59C916CB-71 2017-09-25 14:46:35.964719819 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0007p1iad2.sendgrid.net (SG) with ESMTP id qGAjcwZDRaqC_0FDyWYF_Q for <quic-issues@ietf.org>; Mon, 25 Sep 2017 14:46:35.877 +0000 (UTC)
Date: Mon, 25 Sep 2017 14:46:37 +0000
From: Patrick McManus <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab85233a393e6a4296602025b0c41f7cf356863b6292cf0000000115e0d8cb92a169ce0f820add@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/791/331904775@github.com>
In-Reply-To: <quicwg/base-drafts/issues/791@github.com>
References: <quicwg/base-drafts/issues/791@github.com>
Subject: Re: [quicwg/base-drafts] What happens if you get a stream of the wrong parity? (#791)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c916cbc77e2_b07b3f9a9a52af8452275"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mcmanus
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak32tjYcBAy4oIzIIU+bHe+CNeKb6ZI+1+RSOl KMTohzEOl+DGETDZ/Wd1kAYh3GFcZoG2T3SjUJsw3CTehh08T54IEAq09QVzcNjPPnT+Zilx2zRNqh nzNTpbLXqNbz0FOsoX7XKf9/sV2lFiWTSKnm59JaJoKy93VFXURftrIMnGhYGMycKl7ZHlKTtzAIVU g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/r-wrI21ITioi1hTPZNJ14TJAnfA>
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: Mon, 25 Sep 2017 14:47:46 -0000
perhaps 10.1 needs to be tweaked to have a normative MUST, but otherwise I think the framework is all there. 10.1. <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#rfc.section.10.1> Stream Identifiers <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#stream-id> Streams are identified by an unsigned 32-bit integer, referred to as the Stream ID. To avoid Stream ID collision, clients initiate streams using odd-numbered Stream IDs; streams initiated by the server use even-numbered Stream IDs. *10.2* In the absence of more specific guidance elsewhere in this document, implementations SHOULD treat the receipt of a frame that is not expressly permitted in the description of a state as a connection error (see Section 12 <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#error-handling> ). 12. <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#rfc.section.12> Error Handling <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#error-handling> An endpoint that detects an error SHOULD signal the existence of that error to its peer. Errors can affect an entire connection (see Section 12.1 <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#connection-errors>), or a single stream (see Section 12.2 <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#stream-errors> ). The most appropriate error code (Section 12.3 <https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#error-codes>) SHOULD be included in the frame that signals the error. Where this specification identifies error conditions, it also identifies the error code that is used. On Mon, Sep 25, 2017 at 10:19 AM, ekr <notifications@github.com> wrote: > @mcmanus <https://github.com/mcmanus>: where do you think this is > specified? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/quicwg/base-drafts/issues/791#issuecomment-331896091>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAP5s_szLBRTSB8L45vUl72yVGHDMZzuks5sl7ZbgaJpZM4PiURJ> > . > -- 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/791#issuecomment-331904775
- Re: [quicwg/base-drafts] What happens if you get … Martin Thomson
- [quicwg/base-drafts] What happens if you get a st… ekr
- Re: [quicwg/base-drafts] What happens if you get … Patrick McManus
- Re: [quicwg/base-drafts] What happens if you get … ekr
- Re: [quicwg/base-drafts] What happens if you get … Patrick McManus
- Re: [quicwg/base-drafts] What happens if you get … Martin Thomson