QUIC MSST: Documentation fixes

Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20765)

diff --git a/doc/man3/SSL_accept_stream.pod b/doc/man3/SSL_accept_stream.pod
index 88fbb0db8d8b983428782e70706a9ab0eda98625..430b3dd3644c976d3da5528885e01f6c31c23521 100644 (file)
--- a/doc/man3/SSL_accept_stream.pod
+++ b/doc/man3/SSL_accept_stream.pod
@@ -27,9 +27,7 @@ function may still return NULL in blocking mode, for example if the underlying
 connection is terminated.
 
 The caller is responsible for managing the lifetime of the returned QUIC stream
-SSL object. The lifespan of the parent QUIC connection SSL object must exceed
-that of the QUIC stream SSL object; that is, the stream object must be freed
-first, using L<SSL_free(3)>.
+SSL object; for more information, see L<SSL_free(3)>.
 
 This function will block if the QUIC connection SSL object is configured in
 blocking mode (see L<SSL_set_blocking_mode(3)>), but this may be bypassed by

diff --git a/doc/man3/SSL_free.pod b/doc/man3/SSL_free.pod
index 73c6065795ba4a561ca5171e7bd44b2323f8586e..61ce50e9cc9c5b5b04be0b485f71a79e6e0f5d24 100644 (file)
--- a/doc/man3/SSL_free.pod
+++ b/doc/man3/SSL_free.pod
@@ -62,6 +62,10 @@ stream in turn (which is its sending part).
 
 =back
 
+A QUIC stream SSL object maintains a reference to a QUIC connection SSL object
+internally, therefore a QUIC stream SSL object and its parent QUIC connection
+SSL object can be freed in either order.
+
 =head1 RETURN VALUES
 
 SSL_free() does not provide diagnostic information.