Expand description
APIs for implementing QUIC TLS
Structs§
- Accepted
- Represents that a
ClientHellomessage has been received. - Client
Connection - A QUIC client connection.
- Directional
Keys - Keys used to communicate in a single direction
- KeyBuilder
- Helper for building QUIC packet and header protection keys
- Keys
- Complete set of keys used to communicate with the peer
- Needs
Input - More data needs to be received to make progress.
- Packet
KeySet - Packet protection keys for bidirectional 1-RTT communication
- Secrets
- Secrets used to encrypt/decrypt traffic
- Server
Connection - A QUIC server connection.
- Suite
- Produces QUIC initial keys from a TLS 1.3 ciphersuite and a QUIC key generation algorithm.
- Tag
- Authentication tag from an AEAD seal operation.
Enums§
- KeyChange
- Key material for use in QUIC packet spaces
- Quic
Event - QUIC events that should be handled by the caller.
- Server
Handshake - An in-progress TLS server handshake.
- Side
- Side of the connection.
- Version
- QUIC protocol version
Traits§
- Algorithm
- How a
Tls13CipherSuitegeneratesPacketKeys andHeaderProtectionKeys. - Connection
- A QUIC client or server connection.
- Header
Protection Key - A QUIC header protection key
- Packet
Key - Keys to encrypt or decrypt the payload of a packet