Clarifying the Data Read state

Hugo Landau <hlandau@openssl.org> Fri, 22 March 2024 08:24 UTC

Message-ID: <e0adf945-3777-4309-b3df-4504f2678db9@openssl.org>
Date: Fri, 22 Mar 2024 08:24:04 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: quic@ietf.org
From: Hugo Landau <hlandau@openssl.org>
Subject: Clarifying the Data Read state
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SYTLsKKo7ixpNE8Jd3dSRss7fFc>
Precedence: list

The Data Read state is intended to reflect all of a stream's data having 
been passed to an application. It's unclear to me from reading RFC 9000 
whether the Data Read state is intended to be reached after the 
FIN/end-of-stream event has been passed to the application, or simply 
when all data has been read by the application (but not necessarily the 
end-of-stream event).

In other words, does the "App Read All Data" event in the diagram in RFC 
9000 s. 3.2 include or exclude the FIN in that definition?

Clarifying the Data Read state Hugo Landau
Re: Clarifying the Data Read state Martin Thomson