Searched hist:"6 a7be6e8e00c40ad6d03410d56236ca0ed3a635e" (Results 1 – 3 of 3) sorted by relevance
| /freebsd/sys/netinet/ |
| H A D | tcp_fsm.h | diff 6a7be6e8e00c40ad6d03410d56236ca0ed3a635e Sat Aug 27 00:27:16 CEST 1994 Garrett Wollman <wollman@FreeBSD.org> Obey RFC 793, section 3.4:
Several examples of connection initiation follow. Although these
examples do not show connection synchronization using data-carrying
segments, this is perfectly legitimate, so long as the receiving TCP
doesn't deliver the data to the user until it is clear the data is
valid (i.e., the data must be buffered at the receiver until the
connection reaches the ESTABLISHED state).
diff 6a7be6e8e00c40ad6d03410d56236ca0ed3a635e Sat Aug 27 00:27:16 CEST 1994 Garrett Wollman <wollman@FreeBSD.org> Obey RFC 793, section 3.4:
Several examples of connection initiation follow. Although these
examples do not show connection synchronization using data-carrying
segments, this is perfectly legitimate, so long as the receiving TCP
doesn't deliver the data to the user until it is clear the data is
valid (i.e., the data must be buffered at the receiver until the
connection reaches the ESTABLISHED state).
|
| H A D | tcp_reass.c | diff 6a7be6e8e00c40ad6d03410d56236ca0ed3a635e Sat Aug 27 00:27:16 CEST 1994 Garrett Wollman <wollman@FreeBSD.org> Obey RFC 793, section 3.4:
Several examples of connection initiation follow. Although these
examples do not show connection synchronization using data-carrying
segments, this is perfectly legitimate, so long as the receiving TCP
doesn't deliver the data to the user until it is clear the data is
valid (i.e., the data must be buffered at the receiver until the
connection reaches the ESTABLISHED state).
diff 6a7be6e8e00c40ad6d03410d56236ca0ed3a635e Sat Aug 27 00:27:16 CEST 1994 Garrett Wollman <wollman@FreeBSD.org> Obey RFC 793, section 3.4:
Several examples of connection initiation follow. Although these
examples do not show connection synchronization using data-carrying
segments, this is perfectly legitimate, so long as the receiving TCP
doesn't deliver the data to the user until it is clear the data is
valid (i.e., the data must be buffered at the receiver until the
connection reaches the ESTABLISHED state).
|
| H A D | tcp_input.c | diff 6a7be6e8e00c40ad6d03410d56236ca0ed3a635e Sat Aug 27 00:27:16 CEST 1994 Garrett Wollman <wollman@FreeBSD.org> Obey RFC 793, section 3.4:
Several examples of connection initiation follow. Although these
examples do not show connection synchronization using data-carrying
segments, this is perfectly legitimate, so long as the receiving TCP
doesn't deliver the data to the user until it is clear the data is
valid (i.e., the data must be buffered at the receiver until the
connection reaches the ESTABLISHED state).
diff 6a7be6e8e00c40ad6d03410d56236ca0ed3a635e Sat Aug 27 00:27:16 CEST 1994 Garrett Wollman <wollman@FreeBSD.org> Obey RFC 793, section 3.4:
Several examples of connection initiation follow. Although these
examples do not show connection synchronization using data-carrying
segments, this is perfectly legitimate, so long as the receiving TCP
doesn't deliver the data to the user until it is clear the data is
valid (i.e., the data must be buffered at the receiver until the
connection reaches the ESTABLISHED state).
|