Lines Matching refs:local
4 The connection ID cache is responsible for managing connection IDs, both local
31 For local connection IDs, we need to be able to:
46 There will be one global set of local connection IDs, `QUIC_ROUTE_TABLE`,
58 * For MVP, the local connection ID cache need only have one element.
72 It is likely that operations on local and remote connection IDs can be
178 * Allocate and free a local connection ID cache
184 * Generate a new random local connection ID and associate it with a connection.
192 * Remove a local connection and all associated cached IDs
198 * Lookup a local connection by ID.
206 * Retire local connection IDs up to and including the one specified by the
213 * Remove local connection IDs up to and including the one specified by the
230 QUIC_CONN_ID local;
255 * Query a route table entry by either local or remote ID