Uses of Package
io.github.mahmoudimus.quic.crypto

Package
Description
The sans-I/O QUIC connection and endpoint, ported from quinn-proto: the Connection state machine (handshake, packet assembly and processing, key updates, closing and draining), the Endpoint that routes datagrams and answers with Version Negotiation, Retry and stateless resets, their configurations (TransportConfig, ServerConfig, ClientConfig, EndpointConfig), and the building blocks they are made of: range sets (RangeSet), reassembly of received data (Assembler), buffering of sent data (SendBuffer), streams and flow control (StreamsState), packet number spaces and ACK generation (PacketSpace), loss detection (Recovery), pacing (Pacer), path MTU discovery (MtuDiscovery) and timers (TimerTable).
QUIC packet protection (RFC 9001 section 5): AEAD payload keys, header protection keys, Initial keys per version, key updates and the Retry integrity tag.
QUIC packets (RFC 9000 section 17, RFC 9369): header encoding and partial decoding, packet number truncation and recovery, coalesced datagrams, and protecting and unprotecting whole packets in place.
  • Class
    Description
    The packet protection keys of one encryption level, from one endpoint's point of view: local protects what it sends and remote removes protection from what it receives.
  • Class
    Description
    The keys that protect packets in one direction at one encryption level: a header protection key and a packet (payload) key.
    A header protection key (RFC 9001 section 5.4): masks the low bits of the first byte and the packet number with five bytes derived from a 16-byte sample of the ciphertext.
    The packet protection keys of one encryption level, from one endpoint's point of view: local protects what it sends and remote removes protection from what it receives.
    The AEAD key and IV that protect packet payloads in one direction (RFC 9001 section 5.3).
  • Class
    Description
    The keys that protect packets in one direction at one encryption level: a header protection key and a packet (payload) key.
    A header protection key (RFC 9001 section 5.4): masks the low bits of the first byte and the packet number with five bytes derived from a 16-byte sample of the ciphertext.
    The AEAD key and IV that protect packet payloads in one direction (RFC 9001 section 5.3).