Re: [quicwg/base-drafts] Stream correlation in Transport (#672)

MikkelFJ <notifications@github.com> Wed, 28 June 2017 23:09 UTC

Date: Wed, 28 Jun 2017 23:09:48 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab7c94d2eacdef5f8bb424f35e1d8160b554ad72ea92cf00000001156bf93a92a169ce0e43a87c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/672/c311817033@github.com>
In-Reply-To: <quicwg/base-drafts/pull/672@github.com>
References: <quicwg/base-drafts/pull/672@github.com>
Subject: Re: [quicwg/base-drafts] Stream correlation in Transport (#672)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5954373ace026_49533ff48e8d3c3c1808bd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ZVmWY-PWQ5WQl1xS7yx31Xf7w5k>

I have so far only looked at transport.md - I think the exact encoding is not too important for now - notably var length integers might replace bits in the type byte.

One thought is that it might not be desirable to check for association errors because the initial stream might be closed and gone before a response arrives. Checking validity would require state to be retained - in principle indefinitely. But the association type may still be useful to and API layer.

-- 
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/pull/672#issuecomment-311817033

[quicwg/base-drafts] Stream correlation in Transp… Mike Bishop
Re: [quicwg/base-drafts] Stream correlation in Tr… MikkelFJ
Re: [quicwg/base-drafts] Stream correlation in Tr… Mike Bishop
Re: [quicwg/base-drafts] Stream correlation in Tr… Martin Thomson
Re: [quicwg/base-drafts] Stream correlation in Tr… Mike Bishop
Re: [quicwg/base-drafts] Stream correlation in Tr… Mike Bishop