Lines Matching +full:stream +full:- +full:mode +full:- +full:support

1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-QUIC-INTRODUCTION 7ossl"
58 .TH OSSL-GUIDE-QUIC-INTRODUCTION 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-quic\-introduction
65 \&\- OpenSSL Guide: An introduction to QUIC in OpenSSL
71 some OpenSSL and TLS fundamentals (see \fBossl\-guide\-libraries\-introduction\fR\|(7)
72 and \fBossl\-guide\-tls\-introduction\fR\|(7)).
80 integrity and authentication (see \fBossl\-guide\-tls\-introduction\fR\|(7)).
90 "head-of-line blocking"). It also enables an application to open additional
91 logical streams without requiring a round-trip exchange of packets between the
96 Since QUIC is the basis of HTTP/3, support for QUIC also enables applications
97 to use HTTP/3 using a suitable third-party library.
100 Future versions of OpenSSL will offer support for 0\-RTT connection initiation,
102 transmitted without any waiting time. This is similar to TLS 1.3's 0\-RTT
104 it is similar to a combination of TLS 1.3 0\-RTT and TCP Fast Open.
107 Future versions of OpenSSL will offer support for connection migration, allowing
111 Future versions of OpenSSL will offer support for the QUIC datagram extension,
112 allowing support for both TLS and DTLS-style use cases on a single connection.
123 Because QUIC is UDP-based, it is possible to multiplex a QUIC connection on the
124 same UDP socket as some other UDP-based protocols, such as RTP.
145 OpenSSL provides an optional "thread assisted mode" that will automatically
156 without using TLS \- although some TLS handshake messages may still be sent in
168 QUIC introduces the concept of "streams". A stream provides a reliable
172 effectively has one bi-directional stream available to it per TLS connection. A
173 QUIC application can have multiple uni-directional or bi-directional streams
179 additional \fBSSL\fR objects can be created to represent streams (known as stream
180 \&\fBSSL\fR objects). Unless configured otherwise, a "default" stream is also
183 connection \fBSSL\fR objects, and some can only be used with stream \fBSSL\fR objects.
186 default stream attached to it can be used in contexts that require a connection
187 \&\fBSSL\fR object or in contexts that require a stream \fBSSL\fR object.
190 TLS assumes "stream" type semantics for its underlying transport layer protocol
193 BIO to represent the underlying transport layer. This BIO must support datagrams
205 in blocking mode. So, from an application's perspective, calls to functions such
212 See \fBossl\-guide\-quic\-client\-block\fR\|(7) to see an example of applying these
215 See \fBossl\-guide\-quic\-server\-block\fR\|(7) to see an example of applying these
219 \&\fBossl\-guide\-introduction\fR\|(7), \fBossl\-guide\-libraries\-introduction\fR\|(7),
220 \&\fBossl\-guide\-libssl\-introduction\fR\|(7), \fBossl\-guide\-tls\-introduction\fR\|(7),
221 \&\fBossl\-guide\-tls\-client\-block\fR\|(7), \fBossl\-guide\-quic\-client\-block\fR\|(7),
222 \&\fBossl\-guide\-quic\-client\-non\-block\fR\|(7), \fBossl\-guide\-quic\-multi\-stream\fR\|(7),
223 \&\fBossl\-guide\-quic\-server\-block\fR\|(7), \fBossl\-guide\-quic\-server\-non\-block\fR\|(7),
227 Copyright 2023\-2025 The OpenSSL Project Authors. All Rights Reserved.