Management Information Base for the Transmission Control Protocol (TCP)
RFC 4022

 
Document
Type RFC - Proposed Standard (March 2005; No errata)
Obsoletes RFC 2452, RFC 2012
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream
WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG
IESG state RFC 4022 (Proposed Standard)
Telechat date
Responsible AD Margaret Wasserman
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

Network Working Group                               R. Raghunarayan, Ed.
Request for Comments: 4022                                 Cisco Systems
Obsoletes: 2452, 2012                                         March 2005
Category: Standards Track

                      Management Information Base
              for the Transmission Control Protocol (TCP)

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects used for implementations
   of the Transmission Control Protocol (TCP) in an IP version
   independent manner.  This memo obsoletes RFCs 2452 and 2012.

Table of Contents

   1.  The Internet-Standard Management Framework  . . . . . . . . .   2
   2.  Overview. . . . . . . . . . . . . . . . . . . . . . . . . . .   2
       2.1.  Relationship to Other MIBs. . . . . . . . . . . . . . .   2
   3.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Acknowledgements. . . . . . . . . . . . . . . . . . . . . . .  20
   5.  References. . . . . . . . . . . . . . . . . . . . . . . . . .  20
       5.1.  Normative References. . . . . . . . . . . . . . . . . .  20
       5.2.  Informative References. . . . . . . . . . . . . . . . .  21
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   7.  Contributors. . . . . . . . . . . . . . . . . . . . . . . . .  23
   Editor's Address. . . . . . . . . . . . . . . . . . . . . . . . .  23
   Full Copyright Statement. . . . . . . . . . . . . . . . . . . . .  24

Raghunarayan                Standards Track                     [Page 1]
RFC 4022                      MIB for TCP                     March 2005

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

2.  Overview

   The current TCP-MIB defined in this memo consists of two tables and a
   group of scalars:

      -  The tcp group of scalars includes two sets of objects:

         o  Parameters of a TCP protocol engine.  These include
            parameters such as the retransmission algorithm in use
            (e.g., vanj [VANJ]) and the retransmission timeout values.

         o  Statistics of a TCP protocol engine.  These include counters
            for the number of active/passive opens, input/output
            segments, and errors.  Discontinuities in the stats are
            identified identified via the sysUpTime object, defined in
            [RFC3418].

      -  The tcpConnectionTable provides access to status information
         for all TCP connections handled by a TCP protocol engine.  In
         addition, the table reports identification of the operating
         system level processes that handle the TCP connections.

      -  The tcpListenerTable provides access to information about all
         TCP listening endpoints known by a TCP protocol engine.  And as
         with the connection table, the tcpListenerTable also reports
         the identification of the operating system level processes that
         handle this listening TCP endpoint.

2.1.  Relationship to Other MIBs

   This section discusses the relationship of this TCP-MIB module to
   other MIB modules.

Raghunarayan                Standards Track                     [Page 2]
RFC 4022                      MIB for TCP                     March 2005

2.1.1.  Relationship to RFC1213-MIB

   TCP related MIB objects were originally defined as part of the
   RFC1213-MIB defined in RFC 1213 [RFC1213].  The TCP related objects
   of the RFC1213-MIB were later copied into a separate MIB module and
Show full document text