tcpEStatsStackWillUseSACK

Enabled(1) if the local host will process SACK options,
selfDisabled(2) if SACK is disabled or not implemented on
the local host, or peerDisabled(3) if the remote host sends
              
duplicate ACKs without SACK options, or the local host
otherwise decides not to process received SACK options.
              
Unlike other TCP options, the remote data receiver cannot
explicitly indicate if it is able to generate SACK options.
When sending data, the local host has to deduce if the
remote receiver is sending SACK options.  This object can
transition from Enabled(1) to peerDisabled(3) after the SYN
exchange.
              
Note that SACK negotiation is not symmetrical.  SACK can
enabled on one side of the connection and not the other.

MIB

TCP-ESTATS-MIB

OID

.1.3.6.1.2.1.156.1.1.5.1.9

Type

column

Access

readonly

Status

current

Parent

tcpEStatsStackEntry