IETF Logo Mail Archive

Re: [quicwg/base-drafts] Need to clarify QUIC stream usage in HTTP/2 mapping (#1882)

Magnus Westerlund <notifications@github.com> Mon, 29 October 2018 10:24 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 CD061130E3E for <quic-issues@ietfa.amsl.com>; Mon, 29 Oct 2018 03:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level:
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 7kdOcdXCL1Ly for <quic-issues@ietfa.amsl.com>; Mon, 29 Oct 2018 03:24:23 -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 2F016126CC7 for <quic-issues@ietf.org>; Mon, 29 Oct 2018 03:24:23 -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=Jq4Y7Q6bZovIYR/qRV+pflBze+I=; b=wQoc8SJ1s/x6HFeD 5c9rI9k7zmi5YiUFwo4HvqQ8HuR3fGs2xb8UeLOp8xgg7gFUvhxP0BaqUCxBJyoz pWhVSEPUQo0eaaDcb9trgBAqOD5RpMUtqlpu86sf3haNnnSwlaHViQ2FfpDJNhkj ybeOM+0id5hcEtIbjO7Jg7R8F2A=
Received: by filter1179p1las1.sendgrid.net with SMTP id filter1179p1las1-3956-5BD6DFD5-15 2018-10-29 10:24:21.551294556 +0000 UTC m=+217735.514704645
Received: from github-lowworker-cef7735.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0002p1iad2.sendgrid.net (SG) with ESMTP id pnNP7IL1RZis8SEKO8-0Dg for <quic-issues@ietf.org>; Mon, 29 Oct 2018 10:24:21.467 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-cef7735.cp1-iad.github.net (Postfix) with ESMTP id 6C7261E0373 for <quic-issues@ietf.org>; Mon, 29 Oct 2018 03:24:21 -0700 (PDT)
Date: Mon, 29 Oct 2018 10:24:21 +0000
From: Magnus Westerlund <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2ff2e961caf205fac06e7c6112cfd6eaff51cb3a92cf0000000117eea1d592a169ce1623af22@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1882/433859009@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1882@github.com>
References: <quicwg/base-drafts/issues/1882@github.com>
Subject: Re: [quicwg/base-drafts] Need to clarify QUIC stream usage in HTTP/2 mapping (#1882)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bd6dfd56adc6_62783fe15c6d45c0189623a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gloinul
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0PSS2PvyiTnGorQ5whBqyWP5SM6NGx5U4u5q SbdlTNXqEPRdnW3jQbbs1o8qzbEasoJrygIj5/h0Y/WAAUoJlgFYYcysEhf39LeULCldbgrcWOAZEn KFOFhT8I/Vn6KA1GEjuSs+4MP9y+lX8RdszbVdprOw+o1aF68fqP7jyrY/GVkbmoSDh17Os/9fr6cE 4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/AcenKy3dZOSJIcwD2R7Ehb0L8fc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Oct 2018 10:24:25 -0000

Yes, the actual use of the different streams, especially the different unidirectional are clearer. What is not clear is how one determine which QUIC streams are bi-directional client (or server) initiated or unidirectional in a particular direction. The only indication of that is that client intiated bi-directional are the ones numbered as x mod 4 == 0. So that needs to be clarified. 

And isn't the stream usage defined by this document? From QUICs perspective it has bi-directional streams from 0 to 2^62-1 and that all. Either you define the pattern for which main class each QUIC stream has based on its steam ID or we need to add a explicit signalling for that also at stream start. 

-- 
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/1882#issuecomment-433859009

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