Lines Matching full:connection

1 QUIC Connection ID Cache
4 The connection ID cache is responsible for managing connection IDs, both local
7 Remote Connection IDs
10 For remote connection IDs, we need to be able to:
12 * add new IDs per connection;
13 * pick a non-retired ID associated from those available for a connection and
14 * select a connection ID by sequence number and retire that and all older IDs.
18 and must maintain a count of the number of connection IDs present.
22 In MVP, a many-to-1 matching of Connection IDs per Connection object
25 When picking a non-retired connection ID for MVP, the youngest available will
28 Local Connection IDs
31 For local connection IDs, we need to be able to:
33 * generate a new connection ID and associate it with a connection;
34 * query if a connection ID is present;
35 * for a server, map a connection ID to a QUIC_CONNECTION;
36 * drop all connection IDs associated with a QUIC_CONNECTION;
37 * select a connection ID by sequence number and retire that and all older IDs
39 * select a connection ID by sequence number and drop that and all older IDs.
41 All connection IDs issued by our stack must be the same length because
42 short form packets include the connection ID but no length byte.  Random
43 connection IDs of this length will be allocated.  Note that no additional
44 information will be contained in the connection ID.
46 There will be one global set of local connection IDs, `QUIC_ROUTE_TABLE`,
53 * For MVP, it would be sufficient to only use a zero length connection ID.
54 * For MVP, a connection ID to QUIC_CONNECTION mapping need not be implemented.
58 * For MVP, the local connection ID cache need only have one element.
64 A pair of connection IDs identify a route between the two ends of the
65 communication.  This contains the connection IDs of both ends of the
66 connection and the common sequence number.  We need to be able to:
68 * select a connection ID by sequence number and retire that and all older IDs
70 * select a connection ID by sequence number and drop that and all older IDs.
72 It is likely that operations on local and remote connection IDs can be
78 Connection IDs are retired by either a [NEW_CONNECTION_ID] or
100 QUIC connection IDs are defined in #18949 but some extra functions
104 /* QUIC connection ID representation. */
126 ### Remote Connection ID APIs
132  * Allocate and free a remote connection ID cache
140  * Add a remote connection ID to the cache
149  * Query a remote connection for a connection ID.
150  * Each connection can have multiple connection IDs associated with different
158  * Retire remote connection IDs up to and including the one determined by the
165  * Remove remote connection IDs up to and including the one determined by the
172 ### Local Connection ID APIs
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.
199  * Returns the connection or NULL if absent.
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
233     unsigned int     retired : 1;   /* Connection ID has been retired */