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

5 ossl-guide-quic-introduction
6 - OpenSSL Guide: An introduction to QUIC in OpenSSL
13 some OpenSSL and TLS fundamentals (see L<ossl-guide-libraries-introduction(7)>
14 and L<ossl-guide-tls-introduction(7)>).
23 integrity and authentication (see L<ossl-guide-tls-introduction(7)>).
36 "head-of-line blocking"). It also enables an application to open additional
37 logical streams without requiring a round-trip exchange of packets between the
43 Since QUIC is the basis of HTTP/3, support for QUIC also enables applications
44 to use HTTP/3 using a suitable third-party library.
48 Future versions of OpenSSL will offer support for 0-RTT connection initiation,
50 transmitted without any waiting time. This is similar to TLS 1.3's 0-RTT
52 it is similar to a combination of TLS 1.3 0-RTT and TCP Fast Open.
56 Future versions of OpenSSL will offer support for connection migration, allowing
61 Future versions of OpenSSL will offer support for the QUIC datagram extension,
62 allowing support for both TLS and DTLS-style use cases on a single connection.
75 Because QUIC is UDP-based, it is possible to multiplex a QUIC connection on the
76 same UDP socket as some other UDP-based protocols, such as RTP.
100 OpenSSL provides an optional "thread assisted mode" that will automatically
112 without using TLS - although some TLS handshake messages may still be sent in
125 QUIC introduces the concept of "streams". A stream provides a reliable
129 effectively has one bi-directional stream available to it per TLS connection. A
130 QUIC application can have multiple uni-directional or bi-directional streams
136 additional B<SSL> objects can be created to represent streams (known as stream
137 B<SSL> objects). Unless configured otherwise, a "default" stream is also
140 connection B<SSL> objects, and some can only be used with stream B<SSL> objects.
143 default stream attached to it can be used in contexts that require a connection
144 B<SSL> object or in contexts that require a stream B<SSL> object.
148 TLS assumes "stream" type semantics for its underlying transport layer protocol
151 BIO to represent the underlying transport layer. This BIO must support datagrams
163 in blocking mode. So, from an application's perspective, calls to functions such
171 See L<ossl-guide-quic-client-block(7)> to see an example of applying these
174 See L<ossl-guide-quic-server-block(7)> to see an example of applying these
179 L<ossl-guide-introduction(7)>, L<ossl-guide-libraries-introduction(7)>,
180 L<ossl-guide-libssl-introduction(7)>, L<ossl-guide-tls-introduction(7)>,
181 L<ossl-guide-tls-client-block(7)>, L<ossl-guide-quic-client-block(7)>,
182 L<ossl-guide-quic-client-non-block(7)>, L<ossl-guide-quic-multi-stream(7)>,
183 L<ossl-guide-quic-server-block(7)>, L<ossl-guide-quic-server-non-block(7)>,
188 Copyright 2023-2025 The OpenSSL Project Authors. All Rights Reserved.