From 1748ee69749c4ddfb0a878cf6e2abb36126ed4af Mon Sep 17 00:00:00 2001 From: Michael Welzl Date: Mon, 7 Aug 2023 12:19:37 +0200 Subject: [PATCH] InitiateWithSend can also just start a new stream. --- draft-taps-quic-mapping.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-taps-quic-mapping.md b/draft-taps-quic-mapping.md index 11e6bd8..4655f43 100644 --- a/draft-taps-quic-mapping.md +++ b/draft-taps-quic-mapping.md @@ -58,7 +58,7 @@ Initiate: : Calling `Initiate` on a QUIC stream Connection causes the implementation to prepare a new QUIC stream to the Remote Endpoint. If there is already a QUIC connection to the Remote Endpoint, `Initiate` simply prepares a new stream by allocating a stream ID. If there is not already a QUIC connection established, the implementation will establish a connection first. InitiateWithSend: -: Early data sent in `InitiateWithSend` will be used for 0-RTT QUIC connection establishment, if the QUIC connection to the Remote Endpoint is not already established and the local device has previously negotiated support for 0-RTT establishment with the Remote Endpoint. +: Early data sent in `InitiateWithSend` will be used for 0-RTT QUIC connection establishment, if the QUIC connection to the Remote Endpoint is not already established and the local device has previously negotiated support for 0-RTT establishment with the Remote Endpoint. If there is already a QUIC connection to the Remote Endpoint, `InitiateWithSend` prepares a new stream by allocating a stream ID and sends the data on that new stream. Ready: : A QUIC stream Connection is ready once the underlying QUIC connection is established, and once a stream ID can be allocated. This may be delayed if stream creation is blocked due to reaching the maximum streams limit.