draft-ietf-ipngwg-rfc2012-update-00.txt   draft-ietf-ipngwg-rfc2012-update-01.txt 
IPv6 MIB Revision Design Team Bill Fenner IPv6 MIB Revision Design Team Bill Fenner
INTERNET-DRAFT AT&T Research INTERNET-DRAFT AT&T Research
Expires: January 2002 Brian Haberman Expires: May 2002 Brian Haberman
Nortel Networks Nortel Networks
Keith McCloghrie Keith McCloghrie
Cisco Systems Cisco Systems
Juergen Schoenwalder Juergen Schoenwalder
TU Braunschweig TU Braunschweig
Dave Thaler Dave Thaler
Microsoft Microsoft
November 2001
Management Information Base Management Information Base
for the Transmission Control Protocol (TCP) for the Transmission Control Protocol (TCP)
draft-ietf-ipngwg-rfc2012-update-00.txt draft-ietf-ipngwg-rfc2012-update-01.txt
Status of this Document Status of this Document
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 3, line 9 skipping to change at page 3, line 9
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects used for implementations of the particular, it describes managed objects used for implementations of the
Transmission Control Protocol (TCP) [5] in an IP version independent Transmission Control Protocol (TCP) [5] in an IP version independent
manner. manner.
Table of Contents Table of Contents
1. The SNMP Management Framework . . . . . . . . . . . . . . . . . . 3 1. The SNMP Management Framework . . . . . . . . . . . . . . . . . . 3
2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . 18 5. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . 23
7. Security Considerations . . . . . . . . . . . . . . . . . . . . . 20 7. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8. Editor's Address. . . . . . . . . . . . . . . . . . . . . . . . . 21 8. Security Considerations . . . . . . . . . . . . . . . . . . . . . 25
9. Full Copyright Statement. . . . . . . . . . . . . . . . . . . . . 21 9. Editor's Address. . . . . . . . . . . . . . . . . . . . . . . . . 25
10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 26
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [7]. o An overall architecture, described in RFC 2571 [7].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
skipping to change at page 4, line 21 skipping to change at page 4, line 21
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Revision History 2. Revision History
Changes from draft-ietf-ipngwg-rfc2012-update-00.txt:
14 November 2001
Added HC versions of connection counters.
Added Listener table, with counters for accepted and timed out
connection attempts.
Added tcp{Connection,Listener}ProcessID to index into SYSAPPL-MIB
or HOST-RESOURCES-MIB.
Removed tcpConnectionRemAddrType, it must be the same as
tcpConnectionLocalAddrType.
Changes from draft-ops-rfc2012-update-00.txt Changes from draft-ops-rfc2012-update-00.txt
Turned into IPNG WG document Turned into IPNG WG document
Added tcpCountersGroup for per-connection counters Added tcpCountersGroup for per-connection counters
Changes from first draft posted to v6mib mailing list: Changes from first draft posted to v6mib mailing list:
Made threshold for HC packet counters 1Mpps Made threshold for HC packet counters 1Mpps
Added copyright statements and table of contents Added copyright statements and table of contents
skipping to change at page 5, line 15 skipping to change at page 5, line 28
addresses plus 4-byte scope, but it's just a strawman) addresses plus 4-byte scope, but it's just a strawman)
Used InetPortNumber TC from updated INET-ADDRESS-MIB Used InetPortNumber TC from updated INET-ADDRESS-MIB
Updated compliance statements. Updated compliance statements.
Added Keith to authors Added Keith to authors
Added open issues section. Added open issues section.
3. Definitions Changes from RFC 2012
Deprecated tcpConnTable
Added tcpConnectionTable
3. MIB Structure
(Obviously this section needs a lot of work)
Addresses are as seen on the wire, not necessarily as the socket sees
them (e.g. IPv4 address, not IPv6-mapped IPv4)
Listener on in6addr_any without IPV6_V6ONLY socket option set (i.e.
willing to accept v4 or v6) is indicated by remote AF = unknown.
4. Definitions
TCP-MIB DEFINITIONS ::= BEGIN TCP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Gauge32, MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32,
Counter32, Counter64, IpAddress, mib-2 Gauge32, Counter32, Counter64, IpAddress, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TimeStamp FROM SNMPv2-TC TimeStamp FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetPortNumber FROM INET-ADDRESS-MIB; InetPortNumber FROM INET-ADDRESS-MIB;
tcpMIB MODULE-IDENTITY tcpMIB MODULE-IDENTITY
LAST-UPDATED "200107120000Z" LAST-UPDATED "200111140000Z"
ORGANIZATION "IETF IPv6 MIB Revision Team" ORGANIZATION "IETF IPv6 MIB Revision Team"
CONTACT-INFO CONTACT-INFO
"Bill Fenner (editor) "Bill Fenner (editor)
AT&T Labs -- Research AT&T Labs -- Research
75 Willow Rd. 75 Willow Rd.
Menlo Park, CA 94025 Menlo Park, CA 94025
Phone: +1 650 330-7893 Phone: +1 650 330-7893
Email: <fenner@research.att.com>" Email: <fenner@research.att.com>"
DESCRIPTION DESCRIPTION
"The MIB module for managing TCP implementations." "The MIB module for managing TCP implementations."
REVISION "200107120000Z" REVISION "200111140000Z"
DESCRIPTION DESCRIPTION
"IP version neutral revision, published as RFC XXXX." "IP version neutral revision, published as RFC XXXX."
REVISION "9411010000Z" REVISION "9411010000Z"
DESCRIPTION DESCRIPTION
"Initial SMIv2 version, published as RFC 2012." "Initial SMIv2 version, published as RFC 2012."
REVISION "9103310000Z" REVISION "9103310000Z"
DESCRIPTION DESCRIPTION
"The initial revision of this MIB module was part of MIB-II." "The initial revision of this MIB module was part of MIB-II."
::= { mib-2 49 } ::= { mib-2 49 }
skipping to change at page 9, line 52 skipping to change at page 10, line 33
::= { tcp 18 } ::= { tcp 18 }
-- The TCP Connection table -- The TCP Connection table
tcpConnectionTable OBJECT-TYPE tcpConnectionTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpConnectionEntry SYNTAX SEQUENCE OF TcpConnectionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing information about existing TCP "A table containing information about existing TCP
connections or listeners." connections. Note that unlike earlier TCP MIBs, there is a
seperate table for connections in the LISTEN state."
::= { tcp 19 } ::= { tcp 19 }
tcpConnectionEntry OBJECT-TYPE tcpConnectionEntry OBJECT-TYPE
SYNTAX TcpConnectionEntry SYNTAX TcpConnectionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row of the tcpConnectionTable containing "A conceptual row of the tcpConnectionTable containing
information about a particular current TCP connection. Each information about a particular current TCP connection. Each
row of this table is transient, in that it ceases to exist row of this table is transient, in that it ceases to exist
when (or soon after) the connection makes the transition to when (or soon after) the connection makes the transition to
the CLOSED state." the CLOSED state."
INDEX { tcpConnectionLocalAddressType, INDEX { tcpConnectionLocalAddressType,
tcpConnectionLocalAddress, tcpConnectionLocalAddress,
tcpConnectionLocalPort, tcpConnectionLocalPort,
tcpConnectionRemAddressType,
tcpConnectionRemAddress, tcpConnectionRemAddress,
tcpConnectionRemPort } tcpConnectionRemPort }
::= { tcpConnectionTable 1 } ::= { tcpConnectionTable 1 }
TcpConnectionEntry ::= SEQUENCE { TcpConnectionEntry ::= SEQUENCE {
tcpConnectionLocalAddressType InetAddressType, tcpConnectionLocalAddressType InetAddressType,
tcpConnectionLocalAddress InetAddress, tcpConnectionLocalAddress InetAddress,
tcpConnectionLocalPort InetPortNumber, tcpConnectionLocalPort InetPortNumber,
tcpConnectionRemAddressType InetAddressType,
tcpConnectionRemAddress InetAddress, tcpConnectionRemAddress InetAddress,
tcpConnectionRemPort InetPortNumber, tcpConnectionRemPort InetPortNumber,
tcpConnectionState INTEGER, tcpConnectionState INTEGER,
tcpConnectionInPackets Integer32, tcpConnectionInPackets Counter32,
tcpConnectionOutPackets Integer32, tcpConnectionOutPackets Counter32,
tcpConnectionInOctets Integer32, tcpConnectionInOctets Counter32,
tcpConnectionOutOctets Integer32, tcpConnectionOutOctets Counter32,
tcpConnectionStartTime TimeStamp tcpConnectionHCInPackets Counter64,
tcpConnectionHCOutPackets Counter64,
tcpConnectionHCInOctets Counter64,
tcpConnectionHCOutOctets Counter64,
tcpConnectionStartTime TimeStamp,
tcpConnectionProcessID Unsigned32
} }
tcpConnectionLocalAddressType OBJECT-TYPE tcpConnectionLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address type of tcpConnectionLocalAddress. Only IPv4 "The address type of tcpConnectionLocalAddress. Only IPv4
and IPv6 addresses are expected." and IPv6 addresses are expected."
::= { tcpConnectionEntry 1 } ::= { tcpConnectionEntry 1 }
skipping to change at page 11, line 19 skipping to change at page 12, line 5
::= { tcpConnectionEntry 2 } ::= { tcpConnectionEntry 2 }
tcpConnectionLocalPort OBJECT-TYPE tcpConnectionLocalPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local port number for this TCP connection." "The local port number for this TCP connection."
::= { tcpConnectionEntry 3 } ::= { tcpConnectionEntry 3 }
tcpConnectionRemAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type of tcpConnectionRemAddress. Only IPv4 and
IPv6 addresses are expected. Must be the same as
tcpConnectionLocalAddressType."
::= { tcpConnectionEntry 4 }
tcpConnectionRemAddress OBJECT-TYPE tcpConnectionRemAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE(0..36)) SYNTAX InetAddress (SIZE(0..36))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote IP address for this TCP connection." "The remote IP address for this TCP connection."
::= { tcpConnectionEntry 5 } ::= { tcpConnectionEntry 4 }
tcpConnectionRemPort OBJECT-TYPE tcpConnectionRemPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote port number for this TCP connection." "The remote port number for this TCP connection."
::= { tcpConnectionEntry 6 } ::= { tcpConnectionEntry 5 }
tcpConnectionState OBJECT-TYPE tcpConnectionState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
closed(1), closed(1),
listen(2), listen(2),
synSent(3), synSent(3),
synReceived(4), synReceived(4),
established(5), established(5),
finWait1(6), finWait1(6),
finWait2(7), finWait2(7),
skipping to change at page 12, line 17 skipping to change at page 12, line 41
lastAck(9), lastAck(9),
closing(10), closing(10),
timeWait(11), timeWait(11),
deleteTCB(12) deleteTCB(12)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of this TCP connection. "The state of this TCP connection.
The value listen(2) is included only for parallelism to the
old tcpConnTable, and should not be used. A connection in
LISTEN state should be present in the tcpListenerTable.
The only value which may be set by a management station is The only value which may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an agent deleteTCB(12). Accordingly, it is appropriate for an agent
to return a `badValue' response if a management station to return a `badValue' response if a management station
attempts to set this object to any other value. attempts to set this object to any other value.
If a management station sets this object to the value If a management station sets this object to the value
deleteTCB(12), then this has the effect of deleting the TCB deleteTCB(12), then this has the effect of deleting the TCB
(as defined in RFC 793) of the corresponding connection on (as defined in RFC 793) of the corresponding connection on
the managed node, resulting in immediate termination of the the managed node, resulting in immediate termination of the
connection. connection.
As an implementation-specific option, a RST segment may be As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note sent from the managed node to the other TCP endpoint (note
however that RST segments are not sent reliably)." however that RST segments are not sent reliably)."
::= { tcpConnectionEntry 7 } ::= { tcpConnectionEntry 6 }
tcpConnectionInPackets OBJECT-TYPE tcpConnectionInPackets OBJECT-TYPE
SYNTAX Integer32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets received on this connection. This "The number of packets received on this connection. This
count includes retransmitted data." count includes retransmitted data."
::= { tcpConnectionEntry 8 } ::= { tcpConnectionEntry 7 }
tcpConnectionOutPackets OBJECT-TYPE tcpConnectionOutPackets OBJECT-TYPE
SYNTAX Integer32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets transmitted on this connection. This "The number of packets transmitted on this connection. This
count includes retransmitted data." count includes retransmitted data."
::= { tcpConnectionEntry 9 } ::= { tcpConnectionEntry 8 }
tcpConnectionInOctets OBJECT-TYPE tcpConnectionInOctets OBJECT-TYPE
SYNTAX Integer32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets received on this connection. This "The number of octets received on this connection. This
count includes retransmitted data." count includes retransmitted data."
::= { tcpConnectionEntry 10 } ::= { tcpConnectionEntry 9 }
tcpConnectionOutOctets OBJECT-TYPE tcpConnectionOutOctets OBJECT-TYPE
SYNTAX Integer32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets transmitted on this connection. This "The number of octets transmitted on this connection. This
count includes retransmitted data." count includes retransmitted data."
::= { tcpConnectionEntry 10 }
tcpConnectionHCInPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received on this connection. This
count includes retransmitted data."
::= { tcpConnectionEntry 11 } ::= { tcpConnectionEntry 11 }
tcpConnectionHCOutPackets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets transmitted on this connection. This
count includes retransmitted data."
::= { tcpConnectionEntry 12 }
tcpConnectionHCInOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets received on this connection. This
count includes retransmitted data."
::= { tcpConnectionEntry 13 }
tcpConnectionHCOutOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets transmitted on this connection. This
count includes retransmitted data."
::= { tcpConnectionEntry 14 }
tcpConnectionStartTime OBJECT-TYPE tcpConnectionStartTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this connection was "The value of sysUpTime at the time this connection was
established, or when this listening socket was opened." established"
::= { tcpConnectionEntry 12 } ::= { tcpConnectionEntry 15 }
tcpConnectionProcessID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system's process ID for the process associated with this
connection, or zero if there is no such process. This value
is expected to be the same as HOST-RESOURCES-
MIB::hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for
some row in the appropriate tables."
::= { tcpConnectionEntry 16 }
-- The TCP Listener table
tcpListenerTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information about TCP listeners."
::= { tcp 20 }
tcpListenerEntry OBJECT-TYPE
SYNTAX TcpListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row of the tcpListenerTable containing
information about a particular TCP listener."
INDEX { tcpListenerLocalAddressType,
tcpListenerLocalAddress,
tcpListenerLocalPort,
tcpListenerRemAddressType }
::= { tcpListenerTable 1 }
TcpListenerEntry ::= SEQUENCE {
tcpListenerLocalAddressType InetAddressType,
tcpListenerLocalAddress InetAddress,
tcpListenerLocalPort InetPortNumber,
tcpListenerRemAddressType InetAddressType,
tcpListenerConnectionsTimedOut Counter32,
tcpListenerHCConnectionsTimedOut Counter64,
tcpListenerConnectionsAccepted Counter32,
tcpListenerHCConnectionsAccepted Counter64,
tcpListenerStartTime TimeStamp,
tcpListenerProcessID Unsigned32
}
tcpListenerLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type of tcpListenerLocalAddress. Only IPv4 and
IPv6 addresses are expected."
::= { tcpListenerEntry 1 }
tcpListenerLocalAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE(0..36))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local IP address for this TCP connection. In the case
of a connection in the listen state which is willing to
accept connections for any IP interface associated with the
node, a value of all zeroes is used."
::= { tcpListenerEntry 2 }
tcpListenerLocalPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local port number for this TCP connection."
::= { tcpListenerEntry 3 }
tcpListenerRemAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address type of connections that will be accepted by
this listener. Only IPv4 and IPv6 addresses are expected,
or unknown to indicate an endpoint willing to accept both
IPv4 and IPv6 connections."
::= { tcpListenerEntry 4 }
tcpListenerConnectionsTimedOut OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of connection attempts to this endpoint which
have failed due to timeout of the three-way handshake, i.e.
the row was removed from the tcpConnectionTable but
tcpConnectionState never moved from synReceived to
established."
::= { tcpListenerEntry 5 }
tcpListenerHCConnectionsTimedOut OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of connection attempts to this endpoint which
have failed due to timeout of the three-way handshake, i.e.
the row was removed from the tcpConnectionTable but
tcpConnectionState never moved from synReceived to
established."
::= { tcpListenerEntry 6 }
tcpListenerConnectionsAccepted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of connections which have been established to
this endpoint."
::= { tcpListenerEntry 7 }
tcpListenerHCConnectionsAccepted OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of connections which have been established to
this endpoint."
::= { tcpListenerEntry 8 }
tcpListenerStartTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this listener was
established."
::= { tcpListenerEntry 9 }
tcpListenerProcessID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system's process ID for the process associated with this
listener, or zero if there is no such process. This value
is expected to be the same as HOST-RESOURCES-
MIB::hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for
some row in the appropriate tables."
::= { tcpListenerEntry 10 }
-- The deprecated TCP Connection table -- The deprecated TCP Connection table
tcpConnTable OBJECT-TYPE tcpConnTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpConnEntry SYNTAX SEQUENCE OF TcpConnEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table containing information about existing IPv4-specific "A table containing information about existing IPv4-specific
TCP connections or listeners. This table has been TCP connections or listeners. This table has been
skipping to change at page 16, line 4 skipping to change at page 20, line 21
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The remote port number for this TCP connection." "The remote port number for this TCP connection."
::= { tcpConnEntry 5 } ::= { tcpConnEntry 5 }
-- conformance information -- conformance information
tcpMIBConformance OBJECT IDENTIFIER ::= { tcpMIB 2 } tcpMIBConformance OBJECT IDENTIFIER ::= { tcpMIB 2 }
tcpMIBCompliances OBJECT IDENTIFIER ::= { tcpMIBConformance 1 } tcpMIBCompliances OBJECT IDENTIFIER ::= { tcpMIBConformance 1 }
tcpMIBGroups OBJECT IDENTIFIER ::= { tcpMIBConformance 2 } tcpMIBGroups OBJECT IDENTIFIER ::= { tcpMIBConformance 2 }
-- compliance statements -- compliance statements
tcpMIBCompliance2 MODULE-COMPLIANCE tcpMIBCompliance2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for systems which implement TCP." "The compliance statement for systems which implement TCP."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { tcpBaseGroup, tcpConnectionGroup } MANDATORY-GROUPS { tcpBaseGroup, tcpConnectionGroup, tcpListenerGroup }
GROUP tcpHCGroup GROUP tcpHCGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those systems which are capable "This group is mandatory for those systems which are capable
of receiving or transmitting more than 1 million TCP of receiving or transmitting more than 1 million TCP
packets per second. 1 million packets per second will packets per second. 1 million packets per second will
cause a Counter32 to wrap in just over an hour." cause a Counter32 to wrap in just over an hour."
GROUP tcpCountersGroup GROUP tcpStatisticsGroup
DESCRIPTION DESCRIPTION
"This group is optional. It provides visibility for counters "This group is optional. It provides visibility for counters
that some systems already implement." that some systems already implement."
GROUP tcpHCStatisticsGroup
DESCRIPTION
"This group is mandatory for those systems which implement
the tcpStatisticsGroup and are capable of receiving or
transmitting more than 1 million TCP packets per second.
1 million packets per second will cause a Counter32 to
wrap in just over an hour."
OBJECT tcpConnectionState OBJECT tcpConnectionState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { tcpMIBCompliances 2 } ::= { tcpMIBCompliances 2 }
tcpMIBCompliance MODULE-COMPLIANCE tcpMIBCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for IPv4-only systems which "The compliance statement for IPv4-only systems which
implement TCP. In order to be IP version independent, this implement TCP. In order to be IP version independent, this
compliance statement is deprecated in favor of compliance statement is deprecated in favor of
tcpMIBCompliance2." tcpMIBCompliance2. However, agents are still encouraged to
implement these objects in order to interoperate with the
deployed base of managers."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { tcpGroup } MANDATORY-GROUPS { tcpGroup }
OBJECT tcpConnState OBJECT tcpConnState
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { tcpMIBCompliances 1 } ::= { tcpMIBCompliances 1 }
-- units of conformance -- units of conformance
skipping to change at page 17, line 42 skipping to change at page 22, line 23
TCP implementations." TCP implementations."
::= { tcpMIBGroups 3 } ::= { tcpMIBGroups 3 }
tcpConnectionGroup OBJECT-GROUP tcpConnectionGroup OBJECT-GROUP
OBJECTS { tcpConnectionState } OBJECTS { tcpConnectionState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table of TCP connections." "The table of TCP connections."
::= { tcpMIBGroups 4 } ::= { tcpMIBGroups 4 }
tcpCountersGroup OBJECT-GROUP tcpListenerGroup OBJECT-GROUP
OBJECTS { tcpListenerRemAddressType }
STATUS current
DESCRIPTION
"The table of TCP listeners."
::= { tcpMIBGroups 5 }
tcpStatisticsGroup OBJECT-GROUP
OBJECTS { tcpConnectionInPackets, tcpConnectionOutPackets, OBJECTS { tcpConnectionInPackets, tcpConnectionOutPackets,
tcpConnectionInOctets, tcpConnectionOutOctets, tcpConnectionInOctets, tcpConnectionOutOctets,
tcpConnectionStartTime } tcpConnectionStartTime, tcpConnectionProcessID,
tcpListenerConnectionsTimedOut,
tcpListenerConnectionsAccepted,
tcpListenerStartTime, tcpListenerProcessID }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The packet and octet counters specific to a TCP connection." "The packet and octet counters and other statistics specific
::= { tcpMIBGroups 5 } to a TCP connection or listener."
::= { tcpMIBGroups 6 }
tcpHCStatisticsGroup OBJECT-GROUP
OBJECTS { tcpConnectionHCInPackets, tcpConnectionHCOutPackets,
tcpConnectionHCInOctets, tcpConnectionHCOutOctets,
tcpListenerHCConnectionsTimedOut,
tcpListenerHCConnectionsAccepted }
STATUS current
DESCRIPTION
"The group of objects providing for statistics for listeners
or connections on high speed TCP implementations."
::= { tcpMIBGroups 7 }
END END
4. Open Issues 5. Open Issues
Why is tcpListenerRemoteAddressType = unknown better than
tcpListenerLocalAddressType = unknown and tcpListenerLocalAddress = ''h?
Then we could get rid of tcpListenerRemoteAddressType.
Is tcp*ProcessID OK? Should there be an OID pointer into a row of some
*Run* table?
Are the current per-connection byte/segment counters appropriate? Other Are the current per-connection byte/segment counters appropriate? Other
stats? [in optional conformance group] ConnSRTT? stats? [in optional conformance group] ConnSRTT?
More HC counters? More HC counters?
Seperate listening vs. established connections? 6. Acknowledgements
IPV6_V6ONLY / ??? : does the tcpConnectionTable need something? (Erik
said:
But for the different types of wildcard listeners it would make sense
to be able to capture the difference between:
IPv4-only - bound to INADDR_ANY
IPv6-only - bound to in6addr_any with the IPV6_V6ONLY socket
option set
both - bound to in6addr_any and the above not set
[the last 2 could probably be differentiated by the remote address AF
being Unknown or IPv6 -- which would require changing the DESCRIPTION]
5. Acknowledgements
This document contains a modified subset of RFC 1213 and updates RFC This document contains a modified subset of RFC 1213 and updates RFC
2012 and RFC 2452. 2012 and RFC 2452.
6. References 7. References
[2] Rose, M. and K. McCloghrie, "Management Information Base for Network [2] Rose, M. and K. McCloghrie, "Management Information Base for Network
Management of TCP/IP-based internets", RFC 1213, March 1991. Management of TCP/IP-based internets", RFC 1213, March 1991.
[3] K. McCloghrie, "SNMPv2 Management Information Base for the [3] K. McCloghrie, "SNMPv2 Management Information Base for the
Transmission Control Protocol using SMIv2", RFC 2012, November Transmission Control Protocol using SMIv2", RFC 2012, November
1996. 1996.
[4] Haskin, D. and S. Onishi, "IP Version 6 Management Information Base [4] Haskin, D. and S. Onishi, "IP Version 6 Management Information Base
for the Transmission Control Protocol", RFC 2452, December 1998. for the Transmission Control Protocol", RFC 2452, December 1998.
skipping to change at page 20, line 16 skipping to change at page 25, line 13
2573, April 1999. 2573, April 1999.
[21] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [21] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[22] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to [22] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to
Version 3 of the Internet-standard Network Management Framework", Version 3 of the Internet-standard Network Management Framework",
RFC 2570, April 1999. RFC 2570, April 1999.
7. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB that have a There are a number of management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create. Such objects may be MAX-ACCESS clause of read-write and/or read-create. Such objects may be
considered sensitive or vulnerable in some network environments. The considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
sensitive information. These are: sensitive information. These are:
skipping to change at page 21, line 7 skipping to change at page 26, line 4
control as to who on the secure network is allowed to access and GET/SET control as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB. (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the User- as provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model RFC 2574 [18] and the View-based Access Control based Security Model RFC 2574 [18] and the View-based Access Control
Model RFC 2575 [21] is recommended. Model RFC 2575 [21] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have access to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them. legitimate rights to indeed GET or SET (change/create/delete) them.
8. Editor's Address 9. Editor's Address
Bill Fenner Bill Fenner
AT&T Labs -- Research AT&T Labs -- Research
75 Willow Rd 75 Willow Rd
Menlo Park, CA 94025 Menlo Park, CA 94025
USA USA
Email: fenner@research.att.com Email: fenner@research.att.com
9. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
 End of changes. 43 change blocks. 
73 lines changed or deleted 314 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/