Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

activeReadBeforeSend may not always work with Initiate #13

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

activeReadBeforeSend may not always work with Initiate #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-taps-quic-mapping.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Connection Object:
: A Connection object in the Transport Services API maps to a single QUIC stream between two hosts. This stream can be bidirectional or unidirectional.

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.
: 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 the Selection Property `activeReadBeforeSend` (see {{Section 6.2.18 of I-D.ietf-taps-impl}}) is Preferred or Required, the new stream must be created by sending a QUIC STREAM frame with no data. From {{Section 2.4 of RFC9000}}, it is not certain that a QUIC implementation will offer this ability in its API, and if it this functionality is not available, such a call to `Initiate` (or `InitiateWithSend`, described below) results in an `InititateError`. 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.
Expand Down
Loading