This draft describes extended performance statistics for TCP. They are designed to use TCP's ideal vantage point to diagnose performance problems in both the network and the application. If a network based application is performing poorly, TCP can determine if the bottleneck is in the sender, the receiver or the network itself. If the bottleneck is in the network, TCP can provide specific information about its nature.
Please get the most up-to-date date TCP-ESTATS-MIB here:
[the already out of date IETF draft] [live draft with change bars since the IETF draft]
NOTE: This page is current as of November 2005 (during IETF 64).
We are pushing hard to finish this MIB. It is currently under "MIB doctor review" and we plan to issue a WG last-call as soon as feasible.
We are not expecting any major changes to the document through the review process. If you have been waiting for the document to stabilize before reviewing it carefully, now would be the time to do so.
We are expecting to publish a new revision with a couple of minor corrections just prior to the WGLC. It is our hope that this revision will be the one to proceed through the rest of the RFC2026 standards process.
If you want to be included in the design team, drop a note to Peter O'Neil <firstname.lastname@example.org> and we will add you to the list.
The Web100 project has implemented TCP kernel instrumentation that approximates this MIB. The Web100 instruments are exported via the Linux /proc interface (not SNMP), and differ slightly from this draft. The Web100 user community has provided extensive feedback on the individual "leaf" objects, but not the SMI itself or the MIB table structure, because the Web100 implementation does reflect these aspects of the MIB.
Both IBM and Microsoft have experimental implementations of this MIB and have provided valuable comments that are reflected in the current draft.
Prior versions of this page:
Please send comments and suggestions to email@example.com.
This document is a product of the Web100 project.