Lines Matching full:segment

10 of a TCP segment using a hashing function with a password known to both peers.
118    If the segment is a SYN, then this is the first segment of a new
119    connection. Find the matching MKT for this segment, using the segment's
123       i. If there is no matching MKT, remove TCP-AO from the segment.
124          Proceed with further TCP handling of the segment.
163        1. If the MKT corresponding to the segment’s socket pair and RNextKeyID
165        segment needs to match the MKT’s SendID).
175    by TCP-AO when processing received TCP segments as discussed in the segment
184    2. If the matching MKT corresponding to the segment’s socket pair and
194    Multiple MKTs may match a single outgoing segment, e.g., when MKTs
197    given outgoing segment.
199    >> An outgoing TCP segment MUST match at most one desired MKT, indicated
200    by the segment’s socket pair. The segment MAY match multiple MKTs, provided
202    the segment MAY be used to determine the desired MKT when multiple MKTs
222    TCP-AO requires that every protected TCP segment match exactly one MKT.
226    >> An incoming TCP segment including TCP-AO MUST match exactly one MKT,
227    indicated solely by the segment’s socket pair and its TCP-AO KeyID.
326 Linux TCP-AO also provides a bunch of segment counters that can be helpful
346 flags. If a segment has a TCP-AO header, the filters may also include
425 tcp_ao_compute_sne() is called for each TCP-AO segment. It compares SEQ numbers
426 from the segment with snd_una or rcv_nxt and fits the result into a 2GB window around them,
432 a rollover. It allows more TCP segment replays, but yet all regular
433 TCP checks in tcp_sequence() are applied on the verified segment.