[quicwg/base-drafts] What happens if you get a stream of the wrong parity? (#791)
ekr <notifications@github.com> Mon, 25 September 2017 07:39 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 C35DE13292E for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 00:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.474
X-Spam-Level:
X-Spam-Status: No, score=-0.474 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_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 l0Xs-QmydE3w for <quic-issues@ietfa.amsl.com>; Mon, 25 Sep 2017 00:39:34 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 CC4FB124B18 for <quic-issues@ietf.org>; Mon, 25 Sep 2017 00:39:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=2sALqr0T6EFM7W92OJXsNq9RUUU=; b=kQpF/x9UNFT3WpxJ VhkWL61ZuuTXgs+it6mh7JtQoFhPUeDojZwKoT1i4A0eqhK3kuIXK7i792SYFlUS iSCi5/0PmJYUZT9WqS+fyjKftqmVSWxlj5/iCYpT03WATxTGc05nCbcuodhY3Xcu 4QFfon1uxXZlDqaK29NlxQMbBEI=
Received: by filter1150p1mdw1.sendgrid.net with SMTP id filter1150p1mdw1-24177-59C8B2B5-D 2017-09-25 07:39:33.745331882 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id kHuhoG2iRpSvNL-k-PjcFg for <quic-issues@ietf.org>; Mon, 25 Sep 2017 07:39:33.695 +0000 (UTC)
Date: Mon, 25 Sep 2017 07:39:33 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab337e0e87ee485682e7608e975da5ab756e1e830792cf0000000115e074b592a169ce0f820add@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@github.com>
Subject: [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_59c8b2b596c1d_3143fc42e82af788156b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak07uV6XC50oLEAYol7ehpk5LYLzDGq14N4g3u 1GK0qkpWOjyb/XeDShw4rFG+6+GvXL7KqFiu3CdKMHVi5kXy2N/bH2+wMxRjuG5QfFrAwRjk+4arNs DFIyCLkRVFKoutOEZ7BtEUjbXapKF3Xd/+MfdBEm7sCnr5bNXj2gQJKpiA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/AXIk0kkk3sdhkakZd7pdEW6AcfM>
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 07:39:36 -0000
The client has odd streams and the server even, so what happens if the client sends frame data on stream 2 before the server has opened it? -- 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
- 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