[quicwg/base-drafts] Meaning of "application-owned streams" is unclear (#1297)

Dmitri Tikhonov <notifications@github.com> Tue, 17 April 2018 19:18 UTC

Date: Tue, 17 Apr 2018 12:18:14 -0700
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfaf0d388ec93d02f40abfcbdb5e59726c1d4399892cf0000000116ee0a7692a169ce12c9801e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1297@github.com>
Subject: [quicwg/base-drafts] Meaning of "application-owned streams" is unclear (#1297)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ad64876625b7_6cfa3fb3ad510f7c41935"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/BqUGYkiJQbFMvsLgGqCHt40SHgE>

This wording -- "application-owned stream" -- is only used to describe the QUIC transport parameters.  I tracked down the introduction of this concept to f6157a0b51f14ee1583df3cc7408d8ae86174180.

Based on the diff, I gather that this simply means "not the crypto stream," at least at the time of this writing. Nevertheless, I think that the concept of an application-owned stream should be defined before it is used.

-- 
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/1297

[quicwg/base-drafts] Meaning of "application-owne… Dmitri Tikhonov
Re: [quicwg/base-drafts] Meaning of "application-… Lucas Pardue
Re: [quicwg/base-drafts] Meaning of "application-… Martin Thomson