History log of /lsquic/src/liblsquic/lsquic_handshake.h
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
# a74702c6 06-May-2022 George Wang <gwang@litespeedtech.com>

Release 3.1.0

# 06b2a236 06-Jan-2021 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 2.27.1

- [API] New knob to set outgoing packet batch size.
- Aborted connection now become tickable immediately.
- Abort connection when HTTP/3 frame cannot be opened (can only happen
when malloc fails).

# 2f4629f2 01-Oct-2020 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Fix several thread safety issues

Fixes bug #128 and bug #167.

# 7483dee0 07-Jul-2020 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 2.18.0

- [API] Rename "0-RTT" to "session resumption." In IETF QUIC, "0-RTT"
always refers to early data, meaning a request that the server can
reply to in the very first return flight. A more appropriate name
for what we support on the client site is "session resumption," which
is standard TLS terminology. Later, when we add support for 0-RTT
(early data), we can use the 0-RTT terminology again, this time in
proper context.
- [BUGFIX] Do not set certificate callback if ea_lookup_cert is NULL.
- [BUGFIX] Make connection tickable when it's marked as closed.
- [BUGFIX] Fail certificate lookup if SNI is not present in HTTP mode.
- Several documentation fixes and improvements.
- Minor code cleanup.

# a5fa05f9 12-Mar-2020 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 2.13.0

- [API] Use lsxpack_header structure to process incoming headers.
- [BUGFIX] Fix assertion when zero-padding Initial packet.
- [BUGFIX] Use idle timeout before we learn of peer's value.
- Use ls-hpack 2.0.0 -- has lsxpack_header changes.
- Use ls-qpack 0.14.0 -- new, common with ls-hpack, XXH seed (not used yet).
- Code cleanup: prefix exported functions with "lsquic_".

# 7d09751d 10-Jan-2020 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 2.8.7

- [BUGFIX] Initial packet size check for IETF mini conn applies to
UDP payload, not QUIC packet.
- Support old and new school loss_bits transport parameter.
- Use Q run length of 64 as suggested in the loss bits Draft.
- Undo square wave count when packet is delayed.
- Code cleanup; minor fixes.

# a137764b 11-Dec-2019 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 2.7.2

- [BUGFIX] Send controller: update scheduled bytes when DCID length
changes (IETF client).
- [BUGFIX] Drop alarm check from sanity test. It no longer works now
that we use loss chains.
- [PORTABILITY] Fix build on Alpine Linux.
- [PORTABILITY] Fix build using XCode.
- Client initial DCID length: use RAND_bytes() instead of rand(3).
- Add unit tests for connection min heap.
- [DEBUG] Log CID in gQUIC handshake module
- [DEBUG] Turn on extra checks for IETF client send controller.
- [DEBUG] Dedup next advisory tick messages when reason is IDLE timer.
- [DEBUG] QPACK decoder handler: log header error code.

# 5392f7a3 11-Sep-2019 LiteSpeed Tech <info@litespeedtech.com>

Release 2.2.0: server included, ID-22 supported (#76)

# 90fe3b25 25-Feb-2019 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 1.19.4

- [BUGFIX] Check buffer bounds when looking up version in 0-RTT blob.
- [BUGFIX] http_client: don't fetch 0-rtt info if handshake failed.
- Log number of pacer calls at DEBUG, rather than NOTICE, level.

# 2b051cfe 05-Feb-2019 Stephen Petrides <sdpetrides@gmail.com>

[BUILDFIX] Replace empty arrays in zero_rtt structs with local var ptrs (#66)

# 8ca33e0e 04-Feb-2019 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 1.19.0

- [FEATURE, API Change] 0-RTT support. Add function to export 0-RTT
information; it can be supplied to a subsequent connect() call.
- [FEATURE] Add -0 flag to http_client to exercise 0-RTT support.
- [BUGFIX] Resuscitate the Windows build.
- [BUGFIX] Send HTTP settings (max header list size) if necessary.
- [BUGFIX] Buffered packets can contain ACK frames.
- [BUGFIX] Make packet writeable once all STREAM frames are elided.
- [BUGFIX] Fix potential null dereference when realloc fails.
- cmake: simplify build configuration.

# 229fce07 04-Jan-2019 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Release 1.17.11

Fix strict aliasing warning in when compiling with optimizations

# 7f2bd84c 17-Aug-2018 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

1.12.0: [FEATURE, API Change] Certificate verification

# 9626cfc2 16-Aug-2018 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

1.11.0: [FEATURE] Add support for Q044

# 10c492f0 03-Apr-2018 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Update copyright year; add CONTRIBUTORS.txt

# c51ce338 31-Oct-2017 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Latest changes

- [API Change] Sendfile-like functionality is gone. The stream no
longer opens files and deals with file descriptors. (Among other
things, this makes the code more portable.) Three writing functions
are provided:

lsquic_stream_write
lsquic_stream_writev
lsquic_stream_writef (NEW)

lsquic_stream_writef() is given an abstract reader that has function
pointers for size() and read() functions which the user can implement.
This is the most flexible way. lsquic_stream_write() and
lsquic_stream_writev() are now both implemented as wrappers around
lsquic_stream_writef().

- [OPTIMIZATION] When writing to stream, be it within or without the
on_write() callback, place data directly into packet buffer,
bypassing auxiliary data structures. This reduces amount of memory
required, for the amount of data that can be written is limited
by the congestion window.

To support writes outside the on_write() callback, we keep N
outgoing packet buffers per connection which can be written to
by any stream. One half of these are reserved for the highest
priority stream(s), the other half for all other streams. This way,
low-priority streams cannot write instead of high-priority streams
and, on the other hand, low-priority streams get a chance to send
their packets out.

The algorithm is as follows:

- When user writes to stream outside of the callback:
- If this is the highest priority stream, place it onto the
reserved N/2 queue or fail.
(The actual size of this queue is dynamic -- MAX(N/2, CWND) --
rather than N/2, allowing high-priority streams to write as
much as can be sent.)
- If the stream is not the highest priority, try to place the
data onto the reserved N/2 queue or fail.
- When tick occurs *and* more packets can be scheduled:
- Transfer packets from the high N/2 queue to the scheduled
queue.
- If more scheduling is allowed:
- Call on_write callbacks for highest-priority streams,
placing resulting packets directly onto the scheduled queue.
- If more scheduling is allowed:
- Transfer packets from the low N/2 queue to the scheduled
queue.
- If more scheduling is allowed:
- Call on_write callbacks for non-highest-priority streams,
placing resulting packets directly onto the scheduled queue

The number N is currently 20, but it could be varied based on
resource usage.

- If stream is created due to incoming headers, make headers readable
from on_new.

- Outgoing packets are no longer marked non-writeable to prevent placing
more than one STREAM frame from the same stream into a single packet.
This property is maintained via code flow and an explicit check.
Packets for stream data are allocated using a special function.

- STREAM frame elision is cheaper, as we only perform it if a reset
stream has outgoing packets referencing it.

- lsquic_packet_out_t is smaller, as stream_rec elements are now
inside a union.

# 83287402 09-Oct-2017 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

Latest changes

- Hide handshake implementation behind a set of function pointers
- Use monotonically increasing clock
- Make sure that retx delay is not larger than the max of 60 seconds

# 50aadb33 23-Sep-2017 Dmitri Tikhonov <dtikhonov@litespeedtech.com>

LSQUIC Client: Initial release