Lines Matching refs:a
17 * The focus for the next releases is QUIC, with the objective of providing a
18 fully functional QUIC implementation over a series of releases (2-3).
22 a pluggable record layer interface to be implemented to enable this to be less
25 record layer interface will be internal only for MVP and be public in a future
34 implementations (via a provider).
36 * The minimum viable product (MVP) for the next release is a pluggable record
37 layer interface and a single stream QUIC client in the form of s_client that
41 * The MVP will not contain a library API for an HTTP/3 implementation (it is a
46 * Once we have a fully functional QUIC implementation (in a subsequent release),
48 record layer interface and it should offer a stable ABI (via a provider).
56 is a non-goal.
61 * For the MVP a single interop target (i.e. the server implementation list):
65 * Testing against other implementations is not a release requirement for the MVP.
81 The OMC additionally published a
90 * In TLS/DTLS each connection represents a single stream and each connection is
92 handle a collection of streams will be necessary for many applications. With the
96 * The majority of existing applications operate using a single connection (i.e.
101 to work in a QUIC environment while expanding our APIs to enable future
109 in a future OpenSSL release will be provided.
135 at a network level as well as OS interactions (IO handling, thread handling,
137 away what they’ve got. Where QUIC necessitates a change they would be willing to
152 * It shouldn’t be harder to do single stream just because multi stream as a
161 other major implementations and measured by a) handshakes per second
162 b) application data throughput (bytes per second) for a single stream/connection
172 Single copy for sending data occurs when the application supplies a buffer of
175 to the kernel for sending via a system call.
177 Single copy for receiving data occurs when a library supplied buffer is filled
178 by the kernel via a system call from the socket. No further copies of that data
179 are made until it is decrypted. It is decrypted directly into a buffer made
189 * a pluggable record layer (not public for MVP)
191 * a single stream QUIC client in the form of s_client that does not require
198 * Testing against other implementations is not a release requirement for the MVP.
