xref: /freebsd/share/man/man4/tcp.4 (revision 42249ef2)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.
3.\" Copyright (c) 2010-2011 The FreeBSD Foundation
4.\" All rights reserved.
5.\"
6.\" Portions of this documentation were written at the Centre for Advanced
7.\" Internet Architectures, Swinburne University of Technology, Melbourne,
8.\" Australia by David Hayes under sponsorship from the FreeBSD Foundation.
9.\"
10.\" Redistribution and use in source and binary forms, with or without
11.\" modification, are permitted provided that the following conditions
12.\" are met:
13.\" 1. Redistributions of source code must retain the above copyright
14.\"    notice, this list of conditions and the following disclaimer.
15.\" 2. Redistributions in binary form must reproduce the above copyright
16.\"    notice, this list of conditions and the following disclaimer in the
17.\"    documentation and/or other materials provided with the distribution.
18.\" 3. Neither the name of the University nor the names of its contributors
19.\"    may be used to endorse or promote products derived from this software
20.\"    without specific prior written permission.
21.\"
22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32.\" SUCH DAMAGE.
33.\"
34.\"     From: @(#)tcp.4	8.1 (Berkeley) 6/5/93
35.\" $FreeBSD$
36.\"
37.Dd August 26, 2019
38.Dt TCP 4
39.Os
40.Sh NAME
41.Nm tcp
42.Nd Internet Transmission Control Protocol
43.Sh SYNOPSIS
44.In sys/types.h
45.In sys/socket.h
46.In netinet/in.h
47.In netinet/tcp.h
48.Ft int
49.Fn socket AF_INET SOCK_STREAM 0
50.Sh DESCRIPTION
51The
52.Tn TCP
53protocol provides reliable, flow-controlled, two-way
54transmission of data.
55It is a byte-stream protocol used to
56support the
57.Dv SOCK_STREAM
58abstraction.
59.Tn TCP
60uses the standard
61Internet address format and, in addition, provides a per-host
62collection of
63.Dq "port addresses" .
64Thus, each address is composed
65of an Internet address specifying the host and network,
66with a specific
67.Tn TCP
68port on the host identifying the peer entity.
69.Pp
70Sockets utilizing the
71.Tn TCP
72protocol are either
73.Dq active
74or
75.Dq passive .
76Active sockets initiate connections to passive
77sockets.
78By default,
79.Tn TCP
80sockets are created active; to create a
81passive socket, the
82.Xr listen 2
83system call must be used
84after binding the socket with the
85.Xr bind 2
86system call.
87Only passive sockets may use the
88.Xr accept 2
89call to accept incoming connections.
90Only active sockets may use the
91.Xr connect 2
92call to initiate connections.
93.Pp
94Passive sockets may
95.Dq underspecify
96their location to match
97incoming connection requests from multiple networks.
98This technique, termed
99.Dq "wildcard addressing" ,
100allows a single
101server to provide service to clients on multiple networks.
102To create a socket which listens on all networks, the Internet
103address
104.Dv INADDR_ANY
105must be bound.
106The
107.Tn TCP
108port may still be specified
109at this time; if the port is not specified, the system will assign one.
110Once a connection has been established, the socket's address is
111fixed by the peer entity's location.
112The address assigned to the
113socket is the address associated with the network interface
114through which packets are being transmitted and received.
115Normally, this address corresponds to the peer entity's network.
116.Pp
117.Tn TCP
118supports a number of socket options which can be set with
119.Xr setsockopt 2
120and tested with
121.Xr getsockopt 2 :
122.Bl -tag -width ".Dv TCP_FUNCTION_BLK"
123.It Dv TCP_INFO
124Information about a socket's underlying TCP session may be retrieved
125by passing the read-only option
126.Dv TCP_INFO
127to
128.Xr getsockopt 2 .
129It accepts a single argument: a pointer to an instance of
130.Vt "struct tcp_info" .
131.Pp
132This API is subject to change; consult the source to determine
133which fields are currently filled out by this option.
134.Fx
135specific additions include
136send window size,
137receive window size,
138and
139bandwidth-controlled window space.
140.It Dv TCP_CCALGOOPT
141Set or query congestion control algorithm specific parameters.
142See
143.Xr mod_cc 4
144for details.
145.It Dv TCP_CONGESTION
146Select or query the congestion control algorithm that TCP will use for the
147connection.
148See
149.Xr mod_cc 4
150for details.
151.It Dv TCP_FUNCTION_BLK
152Select or query the set of functions that TCP will use for this connection.
153This allows a user to select an alternate TCP stack.
154The alternate TCP stack must already be loaded in the kernel.
155To list the available TCP stacks, see
156.Va functions_available
157in the
158.Sx MIB Variables
159section further down.
160To list the default TCP stack, see
161.Va functions_default
162in the
163.Sx MIB Variables
164section.
165.It Dv TCP_KEEPINIT
166This
167.Xr setsockopt 2
168option accepts a per-socket timeout argument of
169.Vt "u_int"
170in seconds, for new, non-established
171.Tn TCP
172connections.
173For the global default in milliseconds see
174.Va keepinit
175in the
176.Sx MIB Variables
177section further down.
178.It Dv TCP_KEEPIDLE
179This
180.Xr setsockopt 2
181option accepts an argument of
182.Vt "u_int"
183for the amount of time, in seconds, that the connection must be idle
184before keepalive probes (if enabled) are sent for the connection of this
185socket.
186If set on a listening socket, the value is inherited by the newly created
187socket upon
188.Xr accept 2 .
189For the global default in milliseconds see
190.Va keepidle
191in the
192.Sx MIB Variables
193section further down.
194.It Dv TCP_KEEPINTVL
195This
196.Xr setsockopt 2
197option accepts an argument of
198.Vt "u_int"
199to set the per-socket interval, in seconds, between keepalive probes sent
200to a peer.
201If set on a listening socket, the value is inherited by the newly created
202socket upon
203.Xr accept 2 .
204For the global default in milliseconds see
205.Va keepintvl
206in the
207.Sx MIB Variables
208section further down.
209.It Dv TCP_KEEPCNT
210This
211.Xr setsockopt 2
212option accepts an argument of
213.Vt "u_int"
214and allows a per-socket tuning of the number of probes sent, with no response,
215before the connection will be dropped.
216If set on a listening socket, the value is inherited by the newly created
217socket upon
218.Xr accept 2 .
219For the global default see the
220.Va keepcnt
221in the
222.Sx MIB Variables
223section further down.
224.It Dv TCP_NODELAY
225Under most circumstances,
226.Tn TCP
227sends data when it is presented;
228when outstanding data has not yet been acknowledged, it gathers
229small amounts of output to be sent in a single packet once
230an acknowledgement is received.
231For a small number of clients, such as window systems
232that send a stream of mouse events which receive no replies,
233this packetization may cause significant delays.
234The boolean option
235.Dv TCP_NODELAY
236defeats this algorithm.
237.It Dv TCP_MAXSEG
238By default, a sender- and
239.No receiver- Ns Tn TCP
240will negotiate among themselves to determine the maximum segment size
241to be used for each connection.
242The
243.Dv TCP_MAXSEG
244option allows the user to determine the result of this negotiation,
245and to reduce it if desired.
246.It Dv TCP_NOOPT
247.Tn TCP
248usually sends a number of options in each packet, corresponding to
249various
250.Tn TCP
251extensions which are provided in this implementation.
252The boolean option
253.Dv TCP_NOOPT
254is provided to disable
255.Tn TCP
256option use on a per-connection basis.
257.It Dv TCP_NOPUSH
258By convention, the
259.No sender- Ns Tn TCP
260will set the
261.Dq push
262bit, and begin transmission immediately (if permitted) at the end of
263every user call to
264.Xr write 2
265or
266.Xr writev 2 .
267When this option is set to a non-zero value,
268.Tn TCP
269will delay sending any data at all until either the socket is closed,
270or the internal send buffer is filled.
271.It Dv TCP_MD5SIG
272This option enables the use of MD5 digests (also known as TCP-MD5)
273on writes to the specified socket.
274Outgoing traffic is digested;
275digests on incoming traffic are verified.
276When this option is enabled on a socket, all inbound and outgoing
277TCP segments must be signed with MD5 digests.
278.Pp
279One common use for this in a
280.Fx
281router deployment is to enable
282based routers to interwork with Cisco equipment at peering points.
283Support for this feature conforms to RFC 2385.
284.Pp
285In order for this option to function correctly, it is necessary for the
286administrator to add a tcp-md5 key entry to the system's security
287associations database (SADB) using the
288.Xr setkey 8
289utility.
290This entry can only be specified on a per-host basis at this time.
291.Pp
292If an SADB entry cannot be found for the destination,
293the system does not send any outgoing segments and drops any inbound segments.
294.Pp
295Each dropped segment is taken into account in the TCP protocol statistics.
296.It Dv TCP_TXTLS_ENABLE
297Enable in-kernel Transport Layer Security (TLS) for data written to this
298socket.
299The
300.Vt struct tls_so_enable
301argument defines the encryption and authentication algorithms and keys
302used to encrypt the socket data as well as the maximum TLS record
303payload size.
304.Pp
305All data written to this socket will be encapsulated in TLS records
306and subsequently encrypted.
307By default all data written to this socket is treated as application data.
308Individual TLS records with a type other than application data
309(for example, handshake messages),
310may be transmitted by invoking
311.Xr sendmsg 2
312with a custom TLS record type set in a
313.Dv TLS_SET_RECORD_TYPE
314control message.
315The payload of this control message is a single byte holding the desired
316TLS record type.
317.Pp
318Data read from this socket will still be encrypted and must be parsed by
319a TLS-aware consumer.
320.Pp
321At present, only a single key may be set on a socket.
322As such, users of this option must disable rekeying.
323.It Dv TCP_TXTLS_MODE
324The integer argument can be used to get or set the current TLS mode of a
325socket.
326Setting the mode can only used to toggle between software and NIC TLS after
327TLS has been initially enabled via the
328.Dv TCP_TXTLS_ENABLE
329option.
330The available modes are:
331.Bl -tag -width "Dv TCP_TLS_MODE_IFNET"
332.It Dv TCP_TLS_MODE_NONE
333In-kernel TLS framing and encryption is not enabled for this socket.
334.It Dv TCP_TLS_MODE_SW
335TLS records are encrypted by the kernel prior to placing the data in the
336socket buffer.
337Typically this encryption is performed in software.
338.It Dv TCP_TLS_MODE_IFNET
339TLS records are encrypted by the network interface card (NIC).
340.El
341.El
342.Pp
343The option level for the
344.Xr setsockopt 2
345call is the protocol number for
346.Tn TCP ,
347available from
348.Xr getprotobyname 3 ,
349or
350.Dv IPPROTO_TCP .
351All options are declared in
352.In netinet/tcp.h .
353.Pp
354Options at the
355.Tn IP
356transport level may be used with
357.Tn TCP ;
358see
359.Xr ip 4 .
360Incoming connection requests that are source-routed are noted,
361and the reverse source route is used in responding.
362.Pp
363The default congestion control algorithm for
364.Tn TCP
365is
366.Xr cc_newreno 4 .
367Other congestion control algorithms can be made available using the
368.Xr mod_cc 4
369framework.
370.Ss MIB Variables
371The
372.Tn TCP
373protocol implements a number of variables in the
374.Va net.inet.tcp
375branch of the
376.Xr sysctl 3
377MIB.
378.Bl -tag -width ".Va TCPCTL_DO_RFC1323"
379.It Dv TCPCTL_DO_RFC1323
380.Pq Va rfc1323
381Implement the window scaling and timestamp options of RFC 1323
382(default is true).
383.It Dv TCPCTL_MSSDFLT
384.Pq Va mssdflt
385The default value used for the maximum segment size
386.Pq Dq MSS
387when no advice to the contrary is received from MSS negotiation.
388.It Dv TCPCTL_SENDSPACE
389.Pq Va sendspace
390Maximum
391.Tn TCP
392send window.
393.It Dv TCPCTL_RECVSPACE
394.Pq Va recvspace
395Maximum
396.Tn TCP
397receive window.
398.It Va log_in_vain
399Log any connection attempts to ports where there is not a socket
400accepting connections.
401The value of 1 limits the logging to
402.Tn SYN
403(connection establishment) packets only.
404That of 2 results in any
405.Tn TCP
406packets to closed ports being logged.
407Any value unlisted above disables the logging
408(default is 0, i.e., the logging is disabled).
409.It Va msl
410The Maximum Segment Lifetime, in milliseconds, for a packet.
411.It Va keepinit
412Timeout, in milliseconds, for new, non-established
413.Tn TCP
414connections.
415The default is 75000 msec.
416.It Va keepidle
417Amount of time, in milliseconds, that the connection must be idle
418before keepalive probes (if enabled) are sent.
419The default is 7200000 msec (2 hours).
420.It Va keepintvl
421The interval, in milliseconds, between keepalive probes sent to remote
422machines, when no response is received on a
423.Va keepidle
424probe.
425The default is 75000 msec.
426.It Va keepcnt
427Number of probes sent, with no response, before a connection
428is dropped.
429The default is 8 packets.
430.It Va always_keepalive
431Assume that
432.Dv SO_KEEPALIVE
433is set on all
434.Tn TCP
435connections, the kernel will
436periodically send a packet to the remote host to verify the connection
437is still up.
438.It Va icmp_may_rst
439Certain
440.Tn ICMP
441unreachable messages may abort connections in
442.Tn SYN-SENT
443state.
444.It Va do_tcpdrain
445Flush packets in the
446.Tn TCP
447reassembly queue if the system is low on mbufs.
448.It Va blackhole
449If enabled, disable sending of RST when a connection is attempted
450to a port where there is not a socket accepting connections.
451See
452.Xr blackhole 4 .
453.It Va delayed_ack
454Delay ACK to try and piggyback it onto a data packet.
455.It Va delacktime
456Maximum amount of time, in milliseconds, before a delayed ACK is sent.
457.It Va path_mtu_discovery
458Enable Path MTU Discovery.
459.It Va tcbhashsize
460Size of the
461.Tn TCP
462control-block hash table
463(read-only).
464This may be tuned using the kernel option
465.Dv TCBHASHSIZE
466or by setting
467.Va net.inet.tcp.tcbhashsize
468in the
469.Xr loader 8 .
470.It Va pcbcount
471Number of active process control blocks
472(read-only).
473.It Va syncookies
474Determines whether or not
475.Tn SYN
476cookies should be generated for outbound
477.Tn SYN-ACK
478packets.
479.Tn SYN
480cookies are a great help during
481.Tn SYN
482flood attacks, and are enabled by default.
483(See
484.Xr syncookies 4 . )
485.It Va isn_reseed_interval
486The interval (in seconds) specifying how often the secret data used in
487RFC 1948 initial sequence number calculations should be reseeded.
488By default, this variable is set to zero, indicating that
489no reseeding will occur.
490Reseeding should not be necessary, and will break
491.Dv TIME_WAIT
492recycling for a few minutes.
493.It Va reass.cursegments
494The current total number of segments present in all reassembly queues.
495.It Va reass.maxsegments
496The maximum limit on the total number of segments across all reassembly
497queues.
498The limit can be adjusted as a tunable.
499.It Va reass.maxqueuelen
500The maximum number of segments allowed in each reassembly queue.
501By default, the system chooses a limit based on each TCP connection's
502receive buffer size and maximum segment size (MSS).
503The actual limit applied to a session's reassembly queue will be the lower of
504the system-calculated automatic limit and the user-specified
505.Va reass.maxqueuelen
506limit.
507.It Va rexmit_initial , rexmit_min , rexmit_slop
508Adjust the retransmit timer calculation for
509.Tn TCP .
510The slop is
511typically added to the raw calculation to take into account
512occasional variances that the
513.Tn SRTT
514(smoothed round-trip time)
515is unable to accommodate, while the minimum specifies an
516absolute minimum.
517While a number of
518.Tn TCP
519RFCs suggest a 1
520second minimum, these RFCs tend to focus on streaming behavior,
521and fail to deal with the fact that a 1 second minimum has severe
522detrimental effects over lossy interactive connections, such
523as a 802.11b wireless link, and over very fast but lossy
524connections for those cases not covered by the fast retransmit
525code.
526For this reason, we use 200ms of slop and a near-0
527minimum, which gives us an effective minimum of 200ms (similar to
528.Tn Linux ) .
529The initial value is used before an RTT measurement has been performed.
530.It Va initcwnd_segments
531Enable the ability to specify initial congestion window in number of segments.
532The default value is 10 as suggested by RFC 6928.
533Changing the value on fly would not affect connections using congestion window
534from the hostcache.
535Caution:
536This regulates the burst of packets allowed to be sent in the first RTT.
537The value should be relative to the link capacity.
538Start with small values for lower-capacity links.
539Large bursts can cause buffer overruns and packet drops if routers have small
540buffers or the link is experiencing congestion.
541.It Va rfc3042
542Enable the Limited Transmit algorithm as described in RFC 3042.
543It helps avoid timeouts on lossy links and also when the congestion window
544is small, as happens on short transfers.
545.It Va rfc3390
546Enable support for RFC 3390, which allows for a variable-sized
547starting congestion window on new connections, depending on the
548maximum segment size.
549This helps throughput in general, but
550particularly affects short transfers and high-bandwidth large
551propagation-delay connections.
552.It Va sack.enable
553Enable support for RFC 2018, TCP Selective Acknowledgment option,
554which allows the receiver to inform the sender about all successfully
555arrived segments, allowing the sender to retransmit the missing segments
556only.
557.It Va sack.maxholes
558Maximum number of SACK holes per connection.
559Defaults to 128.
560.It Va sack.globalmaxholes
561Maximum number of SACK holes per system, across all connections.
562Defaults to 65536.
563.It Va maxtcptw
564When a TCP connection enters the
565.Dv TIME_WAIT
566state, its associated socket structure is freed, since it is of
567negligible size and use, and a new structure is allocated to contain a
568minimal amount of information necessary for sustaining a connection in
569this state, called the compressed TCP TIME_WAIT state.
570Since this structure is smaller than a socket structure, it can save
571a significant amount of system memory.
572The
573.Va net.inet.tcp.maxtcptw
574MIB variable controls the maximum number of these structures allocated.
575By default, it is initialized to
576.Va kern.ipc.maxsockets
577/ 5.
578.It Va nolocaltimewait
579Suppress creating of compressed TCP TIME_WAIT states for connections in
580which both endpoints are local.
581.It Va fast_finwait2_recycle
582Recycle
583.Tn TCP
584.Dv FIN_WAIT_2
585connections faster when the socket is marked as
586.Dv SBS_CANTRCVMORE
587(no user process has the socket open, data received on
588the socket cannot be read).
589The timeout used here is
590.Va finwait2_timeout .
591.It Va finwait2_timeout
592Timeout to use for fast recycling of
593.Tn TCP
594.Dv FIN_WAIT_2
595connections.
596Defaults to 60 seconds.
597.It Va ecn.enable
598Enable support for TCP Explicit Congestion Notification (ECN).
599ECN allows a TCP sender to reduce the transmission rate in order to
600avoid packet drops.
601Settings:
602.Bl -tag -compact
603.It 0
604Disable ECN.
605.It 1
606Allow incoming connections to request ECN.
607Outgoing connections will request ECN.
608.It 2
609Allow incoming connections to request ECN.
610Outgoing connections will not request ECN.
611.El
612.It Va ecn.maxretries
613Number of retries (SYN or SYN/ACK retransmits) before disabling ECN on a
614specific connection.
615This is needed to help with connection establishment
616when a broken firewall is in the network path.
617.It Va pmtud_blackhole_detection
618Turn on automatic path MTU blackhole detection.
619In case of retransmits OS will
620lower the MSS to check if it's MTU problem.
621If current MSS is greater than
622configured value to try, it will be set to configured value, otherwise,
623MSS will be set to default values
624.Po Va net.inet.tcp.mssdflt
625and
626.Va net.inet.tcp.v6mssdflt
627.Pc .
628.It Va pmtud_blackhole_mss
629MSS to try for IPv4 if PMTU blackhole detection is turned on.
630.It Va v6pmtud_blackhole_mss
631MSS to try for IPv6 if PMTU blackhole detection is turned on.
632.It Va pmtud_blackhole_activated
633Number of times configured values were used in an attempt to downshift.
634.It Va pmtud_blackhole_activated_min_mss
635Number of times default MSS was used in an attempt to downshift.
636.It Va pmtud_blackhole_failed
637Number of connections for which retransmits continued even after MSS
638downshift.
639.It Va functions_available
640List of available TCP function blocks (TCP stacks).
641.It Va functions_default
642The default TCP function block (TCP stack).
643.It Va functions_inherit_listen_socket_stack
644Determines whether to inherit listen socket's tcp stack or use the current
645system default tcp stack, as defined by
646.Va functions_default .
647Default is true.
648.It Va insecure_rst
649Use criteria defined in RFC793 instead of RFC5961 for accepting RST segments.
650Default is false.
651.It Va insecure_syn
652Use criteria defined in RFC793 instead of RFC5961 for accepting SYN segments.
653Default is false.
654.It Va ts_offset_per_conn
655When initializing the TCP timestamps, use a per connection offset instead of a
656per host pair offset.
657Default is to use per connection offsets as recommended in RFC 7323.
658.El
659.Sh ERRORS
660A socket operation may fail with one of the following errors returned:
661.Bl -tag -width Er
662.It Bq Er EISCONN
663when trying to establish a connection on a socket which
664already has one;
665.It Bo Er ENOBUFS Bc or Bo Er ENOMEM Bc
666when the system runs out of memory for
667an internal data structure;
668.It Bq Er ETIMEDOUT
669when a connection was dropped
670due to excessive retransmissions;
671.It Bq Er ECONNRESET
672when the remote peer
673forces the connection to be closed;
674.It Bq Er ECONNREFUSED
675when the remote
676peer actively refuses connection establishment (usually because
677no process is listening to the port);
678.It Bq Er EADDRINUSE
679when an attempt
680is made to create a socket with a port which has already been
681allocated;
682.It Bq Er EADDRNOTAVAIL
683when an attempt is made to create a
684socket with a network address for which no network interface
685exists;
686.It Bq Er EAFNOSUPPORT
687when an attempt is made to bind or connect a socket to a multicast
688address.
689.It Bq Er EINVAL
690when trying to change TCP function blocks at an invalid point in the session;
691.It Bq Er ENOENT
692when trying to use a TCP function block that is not available;
693.El
694.Sh SEE ALSO
695.Xr getsockopt 2 ,
696.Xr socket 2 ,
697.Xr sysctl 3 ,
698.Xr blackhole 4 ,
699.Xr inet 4 ,
700.Xr intro 4 ,
701.Xr ip 4 ,
702.Xr mod_cc 4 ,
703.Xr siftr 4 ,
704.Xr syncache 4 ,
705.Xr setkey 8 ,
706.Xr tcp_functions 9
707.Rs
708.%A "V. Jacobson"
709.%A "R. Braden"
710.%A "D. Borman"
711.%T "TCP Extensions for High Performance"
712.%O "RFC 1323"
713.Re
714.Rs
715.%A "A. Heffernan"
716.%T "Protection of BGP Sessions via the TCP MD5 Signature Option"
717.%O "RFC 2385"
718.Re
719.Rs
720.%A "K. Ramakrishnan"
721.%A "S. Floyd"
722.%A "D. Black"
723.%T "The Addition of Explicit Congestion Notification (ECN) to IP"
724.%O "RFC 3168"
725.Re
726.Sh HISTORY
727The
728.Tn TCP
729protocol appeared in
730.Bx 4.2 .
731The RFC 1323 extensions for window scaling and timestamps were added
732in
733.Bx 4.4 .
734The
735.Dv TCP_INFO
736option was introduced in
737.Tn Linux 2.6
738and is
739.Em subject to change .
740