Lines Matching full:future

20 - Support connection migration and preferred addressing in the future.
35 cases in the future. For example, it could be used for TLS over TCP to make
42 support DTLS in the future in the same way as QUIC, etc.
105  * TCP and DTLS can be supported in the future; not supported for non-QUIC
153 /* Returns 1 for QLSOs (or future TLS/DTLS listeners) only. */
305 ### Future Compatibility: TLS over TCP Support
337 Thus, this API should be compatible with any future adaptation to also support
340 ### Future Compatibility: DTLS over UDP Support
343 so this API should also be adaptable to support DTLS in the future, providing
358 theoretically possible in future and is discussed in the next section.
362 ### Roles and Domains: Concepts and Future Evolution
398   A domain could contain multiple QLSOs (i.e., multiple UDP sockets) in future.
453 intended to demonstrate potential future directions and the adaptability of the
454 design to future evolution. There is no immediate plan to implement a QDSO