Lines Matching refs:segments

8 segments between trusted peers. It adds a new TCP header option with
49  |replayed TCP segments |                        |Extension (SNE) and    |
131    of segments with TCP-AO but that do not match an MKT. The initial default
135    Alternately, the configuration can be changed to discard segments with
141    segments with TCP-AO are not discarded solely because they include
145 segments with unknown key signatures are discarded with warnings logged.
153    >> All TCP segments MUST be checked against the set of MKTs for matching
175    by TCP-AO when processing received TCP segments as discussed in the segment
179    segments are received out of order, and is considered a feature of TCP-AO,
217 that would allow accepting segments without a sign (which would be insecure).
330 - for good segments (properly signed)
331 - for bad segments (failed TCP-AO verification)
332 - for segments with unknown keys
333 - for segments where an AO signature was expected, but wasn't found
435 segments for the simplicity of the algorithm and what seems better behaviour