Lines Matching +full:multi +full:- +full:protocol

5 openssl-quic - OpenSSL QUIC
9 OpenSSL 3.2 and later features support for the QUIC transport protocol.
11 This man page describes how to let applications use the QUIC protocol using the
14 The QUIC protocol maps to the standard SSL API. A QUIC connection is represented
16 are needed to existing applications which use libssl API to bring QUIC protocol
28 Default stream mode versus multi-stream mode for clients;
32 The changes to existing libssl APIs which are driven by QUIC-related
46 New, QUIC-specific APIs.
53 stream mode, which is intended to provide compatibility with existing non-QUIC
57 client-initiated or server-initiated from a QUIC perspective depends on whether
62 instead adopt the multi-stream API. See the RECOMMENDATIONS FOR NEW APPLICATIONS
68 multi-stream mode. By default, a newly created QUIC connection SSL object uses
80 whether a stream is client-initiated or server-initiated. In default stream
82 L<SSL_write(3)> on the connection, it is assumed that the application protocol
83 is using a server-initiated stream, and the L<SSL_read(3)> call will not
87 connection, it is assumed that a client-initiated stream is to be used
91 New applications adopting QUIC should use multi-stream mode, described below,
98 using additional streams are strongly recommended to use multi-stream mode
105 =head2 Multi-Stream Mode
107 The recommended usage mode for new applications adopting QUIC is multi-stream
114 To use multi-stream mode, call L<SSL_set_default_stream_mode(3)> with an
119 When multi-stream mode is used, meaning that no default stream is associated
148 L<BIO_s_dgram_pair(3)> provides BIO pair-like functionality but with datagram
154 L<BIO_s_dgram_mem(3)> provides a simple memory BIO-like interface but with
173 Traditionally, whether the application-level I/O APIs (such as L<SSL_read(3)>
177 application-level blocking mode using L<SSL_set_blocking_mode(3)>. See
182 Network-level I/O must always be performed in a nonblocking manner. The
183 application can still enjoy blocking semantics for calls to application-level
186 in nonblocking mode. For application-level blocking functionality, see
204 RFC-conformant QUIC shutdown process may take an extended amount of time. This
205 may not be suitable for short-lived processes which should exit immediately
226 loops need to use these functions; see B<APPLICATION-DRIVEN EVENT LOOPS> for
282 TLS Next Protocol Negotiation cannot be used and is superseded by ALPN, which
287 Post-Handshake Client Authentication is not available as QUIC prohibits its use.
307 but calls to the relevant functions are treated as no-ops:
353 address; see the B<QUIC-SPECIFIC APIS> section for details.
390 Changes needed: The custom BIO must be re-architected to have datagram
450 L<SSL_shutdown_ex(3)> API instead. See B<QUIC-SPECIFIC APIS> for details.
467 to manage its own polling and event loop; see B<APPLICATION-DRIVEN EVENT LOOPS>.
488 Applications which wish to implement QUIC-specific protocols should be aware of
489 the APIs listed under B<QUIC-SPECIFIC APIS> which provide access to
490 QUIC-specific functionality. For example, L<SSL_stream_conclude(3)> can be used
495 applications avoid use of the default stream mode and use the multi-stream API
499 =head1 QUIC-SPECIFIC APIS
519 This is a non-specific I/O operation which makes a best effort attempt to
540 in a protocol-agnostic manner.
543 client-only usage. The listener interface may expand to support additional
549 I<ssl>. See L<SSL_new_domain(3)> and L<openssl-quic-concurrency(7)> for details
591 detail in L<openssl-quic-concurrency(7)>.
650 This allows an application to indicate the non-normal termination of the sending
661 signalled by a peer which has performed a non-normal stream termination of the
684 Returns the QUIC stream ID which the QUIC protocol has associated with a QUIC
689 Creates a new QUIC stream SSL object representing a new, locally-initiated QUIC
695 remotely-initiated QUIC stream, blocking until one is available if the
700 Provides information on the number of pending remotely-initiated streams.
704 Configures how incoming, remotely-initiated streams are handled. The incoming
716 facilitate QUIC-specific requirements and are closely associated with its use:
790 =head1 APPLICATION-DRIVEN EVENT LOOPS
917 Copyright 2022-2025 The OpenSSL Project Authors. All Rights Reserved.