IETF Logo Mail Archive

Re: [quicwg/base-drafts] Stream creation order (#634)

MikkelFJ <notifications@github.com> Wed, 27 September 2017 19:30 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 0AC85134F19 for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 12:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.8
X-Spam-Level:
X-Spam-Status: No, score=-9.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_DNSWL_HI=-5, 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 yfAR5ymNdxyt for <quic-issues@ietfa.amsl.com>; Wed, 27 Sep 2017 12:30:56 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 523931342DB for <quic-issues@ietf.org>; Wed, 27 Sep 2017 12:30:56 -0700 (PDT)
Date: Wed, 27 Sep 2017 12:30:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1506540655; bh=So9mH7zbriUPW0bzNGpwVZpYqwI/YK0efpFjXtiU4YY=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M0ZeXIaQKt2/JNjeZoKVOFm8oqJq/yEJCWLeYxzMvXi0q9NpriM6N1G/iZu0J9bOP v4Sp6NwVo1nsBXl8YoVh+eMN+7fZbUMVZxkFuFpxRyZK0R/A9rs6C8Wc2grOgq/qZs 4XPrgKKjg4cq1qRkabUhOiheCkf8iV1SB8WBlXaU=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab72d1eb6280587259c3cc71ad85de9693154e452892cf0000000115e3be6f92a169ce0e164e9f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/634/332630536@github.com>
In-Reply-To: <quicwg/base-drafts/issues/634@github.com>
References: <quicwg/base-drafts/issues/634@github.com>
Subject: Re: [quicwg/base-drafts] Stream creation order (#634)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59cbfc6f97a41_2d33fd853caaf38204a3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/J9PdovsVFgkJiT6rq_t2D50vd3g>
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: Wed, 27 Sep 2017 19:30:58 -0000

SHOULD would void any transport level simplifications so you might as well remove the constraint if not strictly enforced. If course specific app protocols may differ but transport is still affected.

________________________________
From: janaiyengar <notifications@github.com>
Sent: Wednesday, September 27, 2017 9:13:47 PM
To: quicwg/base-drafts
Cc: MikkelFJ; Comment
Subject: Re: [quicwg/base-drafts] Stream creation order (#634)


I'm hearing the argument for keeping this restriction, which is that it allows for a simpler implementation. It doesn't break the protocol if the sender doesn't open streams sequentially. Together, these seem to suggest that we should keep this restriction, but make it a SHOULD from a MUST.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/quicwg/base-drafts/issues/634#issuecomment-332626142>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AALzN1fFt6gkIbpzIThG4vW0c29qcvzzks5smp5rgaJpZM4N73Yh>.


-- 
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/634#issuecomment-332630536

v2.39.1 | Report a Bug | By Email | System Status