idnits 2.17.1 draft-ietf-snmpv2-tcp-ds-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' ** Obsolete normative reference: RFC 793 (ref. '3') (Obsoleted by RFC 9293) -- Possible downref: Non-RFC (?) normative reference: ref. '5' Summary: 11 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 SNMPv2 Management Information Base 2 for the Transmission Control Protocol 4 Fri Jun 30 23:59:59 1995 6 draft-ietf-snmpv2-tcp-ds-02.txt 8 Jeffrey D. Case 9 SNMP Research, Inc. 10 case@snmp.com 12 Keith McCloghrie 13 Cisco Systems, Inc. 14 kzm@cisco.com 16 Marshall T. Rose 17 Dover Beach Consulting, Inc. 18 mrose@dbc.mtview.ca.us 20 Steven Waldbusser 21 Carnegie Mellon University 22 waldbusser@cmu.edu 24 Status of this Memo 26 This document is an Internet-Draft. Internet-Drafts are working 27 documents of the Internet Engineering Task Force (IETF), its areas, and 28 its working groups. Note that other groups may also distribute working 29 documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet- Drafts as reference material 34 or to cite them other than as ``work in progress.'' 36 To learn the current status of any Internet-Draft, please check the 37 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 38 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 39 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 41 1. Introduction 43 A management system contains: several (potentially many) nodes, each 44 with a processing entity, termed an agent, which has access to 45 management instrumentation; at least one management station; and, a 46 management protocol, used to convey management information between the 47 agents and management stations. Operations of the protocol are carried 48 out under an administrative framework which defines authentication, 49 authorization, access control, and privacy policies. 51 Management stations execute management applications which monitor and 52 control managed elements. Managed elements are devices such as hosts, 53 routers, terminal servers, etc., which are monitored and controlled via 54 access to their management information. 56 Management information is viewed as a collection of managed objects, 57 residing in a virtual information store, termed the Management 58 Information Base (MIB). Collections of related objects are defined in 59 MIB modules. These modules are written using a subset of OSI's Abstract 60 Syntax Notation One (ASN.1) [1], termed the Structure of Management 61 Information (SMI) [2]. 63 This document is the MIB module which defines managed objects for 64 managing implementations of the Transmission Control Protocol (TCP) [3]. 66 The managed objects in this MIB module were originally defined using the 67 SNMPv1 framework as a part of MIB-II [4]. This document defines the 68 same objects for TCP using the SNMPv2 framework. 70 2. Definitions 72 TCP-MIB DEFINITIONS ::= BEGIN 74 IMPORTS 75 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Gauge32, 76 experimental, -- to be removed later 77 Counter32, IpAddress, mib-2 FROM SNMPv2-SMI 78 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 80 tcpMIB MODULE-IDENTITY 81 LAST-UPDATED "9411010000Z" 82 ORGANIZATION "IETF SNMPv2 Working Group" 83 CONTACT-INFO 84 " Keith McCloghrie 86 Postal: Cisco Systems, Inc. 87 170 West Tasman Drive 88 San Jose, CA 95134-1706 89 US 91 Phone: +1 408 526 5260 92 Email: kzm@cisco.com" 93 DESCRIPTION 94 "The MIB module for managing TCP implementations." 95 REVISION "9103310000Z" 96 DESCRIPTION 97 "The initial revision of this MIB module was part of MIB- 98 II." 99 -- to be assigned as {mib-2 xx} by IANA 100 ::= { experimental xx } 102 -- the TCP group 104 tcp OBJECT IDENTIFIER ::= { mib-2 6 } 106 tcpRtoAlgorithm OBJECT-TYPE 107 SYNTAX INTEGER { 108 other(1), -- none of the following 109 constant(2), -- a constant rto 110 rsre(3), -- MIL-STD-1778, Appendix B 111 vanj(4) -- Van Jacobson's algorithm [5] 112 } 113 MAX-ACCESS read-only 114 STATUS current 115 DESCRIPTION 116 "The algorithm used to determine the timeout value used for 117 retransmitting unacknowledged octets." 118 ::= { tcp 1 } 120 tcpRtoMin OBJECT-TYPE 121 SYNTAX Integer32 122 UNITS "milliseconds" 123 MAX-ACCESS read-only 124 STATUS current 125 DESCRIPTION 126 "The minimum value permitted by a TCP implementation for the 127 retransmission timeout, measured in milliseconds. More 128 refined semantics for objects of this type depend upon the 129 algorithm used to determine the retransmission timeout. In 130 particular, when the timeout algorithm is rsre(3), an object 131 of this type has the semantics of the LBOUND quantity 132 described in RFC 793." 133 ::= { tcp 2 } 135 tcpRtoMax OBJECT-TYPE 136 SYNTAX Integer32 137 UNITS "milliseconds" 138 MAX-ACCESS read-only 139 STATUS current 140 DESCRIPTION 141 "The maximum value permitted by a TCP implementation for the 142 retransmission timeout, measured in milliseconds. More 143 refined semantics for objects of this type depend upon the 144 algorithm used to determine the retransmission timeout. In 145 particular, when the timeout algorithm is rsre(3), an object 146 of this type has the semantics of the UBOUND quantity 147 described in RFC 793." 148 ::= { tcp 3 } 150 tcpMaxConn OBJECT-TYPE 151 SYNTAX Integer32 152 MAX-ACCESS read-only 153 STATUS current 154 DESCRIPTION 155 "The limit on the total number of TCP connections the entity 156 can support. In entities where the maximum number of 157 connections is dynamic, this object should contain the value 158 -1." 159 ::= { tcp 4 } 161 tcpActiveOpens OBJECT-TYPE 162 SYNTAX Counter32 163 MAX-ACCESS read-only 164 STATUS current 165 DESCRIPTION 166 "The number of times TCP connections have made a direct 167 transition to the SYN-SENT state from the CLOSED state." 168 ::= { tcp 5 } 170 tcpPassiveOpens OBJECT-TYPE 171 SYNTAX Counter32 172 MAX-ACCESS read-only 173 STATUS current 174 DESCRIPTION 175 "The number of times TCP connections have made a direct 176 transition to the SYN-RCVD state from the LISTEN state." 177 ::= { tcp 6 } 179 tcpAttemptFails OBJECT-TYPE 180 SYNTAX Counter32 181 MAX-ACCESS read-only 182 STATUS current 183 DESCRIPTION 184 "The number of times TCP connections have made a direct 185 transition to the CLOSED state from either the SYN-SENT 186 state or the SYN-RCVD state, plus the number of times TCP 187 connections have made a direct transition to the LISTEN 188 state from the SYN-RCVD state." 189 ::= { tcp 7 } 191 tcpEstabResets OBJECT-TYPE 192 SYNTAX Counter32 193 MAX-ACCESS read-only 194 STATUS current 195 DESCRIPTION 196 "The number of times TCP connections have made a direct 197 transition to the CLOSED state from either the ESTABLISHED 198 state or the CLOSE-WAIT state." 199 ::= { tcp 8 } 201 tcpCurrEstab OBJECT-TYPE 202 SYNTAX Gauge32 203 MAX-ACCESS read-only 204 STATUS current 205 DESCRIPTION 206 "The number of TCP connections for which the current state 207 is either ESTABLISHED or CLOSE- WAIT." 208 ::= { tcp 9 } 210 tcpInSegs OBJECT-TYPE 211 SYNTAX Counter32 212 MAX-ACCESS read-only 213 STATUS current 214 DESCRIPTION 215 "The total number of segments received, including those 216 received in error. This count includes segments received on 217 currently established connections." 218 ::= { tcp 10 } 220 tcpOutSegs OBJECT-TYPE 221 SYNTAX Counter32 222 MAX-ACCESS read-only 223 STATUS current 224 DESCRIPTION 225 "The total number of segments sent, including those on 226 current connections but excluding those containing only 227 retransmitted octets." 228 ::= { tcp 11 } 230 tcpRetransSegs OBJECT-TYPE 231 SYNTAX Counter32 232 MAX-ACCESS read-only 233 STATUS current 234 DESCRIPTION 235 "The total number of segments retransmitted - that is, the 236 number of TCP segments transmitted containing one or more 237 previously transmitted octets." 238 ::= { tcp 12 } 240 -- the TCP Connection table 242 -- The TCP connection table contains information about this 243 -- entity's existing TCP connections. 245 tcpConnTable OBJECT-TYPE 246 SYNTAX SEQUENCE OF TcpConnEntry 247 MAX-ACCESS not-accessible 248 STATUS current 249 DESCRIPTION 250 "A table containing TCP connection-specific information." 251 ::= { tcp 13 } 253 tcpConnEntry OBJECT-TYPE 254 SYNTAX TcpConnEntry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "A conceptual row of the tcpConnTable containing information 259 about a particular current TCP connection. Each row of this 260 table is transient, in that it ceases to exist when (or soon 261 after) the connection makes the transition to the CLOSED 262 state." 263 INDEX { tcpConnLocalAddress, 264 tcpConnLocalPort, 265 tcpConnRemAddress, 266 tcpConnRemPort } 267 ::= { tcpConnTable 1 } 269 TcpConnEntry ::= SEQUENCE { 270 tcpConnState INTEGER, 271 tcpConnLocalAddress IpAddress, 272 tcpConnLocalPort INTEGER, 273 tcpConnRemAddress IpAddress, 274 tcpConnRemPort INTEGER 275 } 277 tcpConnState OBJECT-TYPE 278 SYNTAX INTEGER { 279 closed(1), 280 listen(2), 281 synSent(3), 282 synReceived(4), 283 established(5), 284 finWait1(6), 285 finWait2(7), 286 closeWait(8), 287 lastAck(9), 288 closing(10), 289 timeWait(11), 290 deleteTCB(12) 291 } 292 MAX-ACCESS read-write 293 STATUS current 294 DESCRIPTION 295 "The state of this TCP connection. 297 The only value which may be set by a management station is 298 deleteTCB(12). Accordingly, it is appropriate for an agent 299 to return a `badValue' response if a management station 300 attempts to set this object to any other value. 302 If a management station sets this object to the value 303 deleteTCB(12), then this has the effect of deleting the TCB 304 (as defined in RFC 793) of the corresponding connection on 305 the managed node, resulting in immediate termination of the 306 connection. 308 As an implementation-specific option, a RST segment may be 309 sent from the managed node to the other TCP endpoint (note 310 however that RST segments are not sent reliably)." 311 ::= { tcpConnEntry 1 } 313 tcpConnLocalAddress OBJECT-TYPE 314 SYNTAX IpAddress 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The local IP address for this TCP connection. In the case 319 of a connection in the listen state which is willing to 320 accept connections for any IP interface associated with the 321 node, the value 0.0.0.0 is used." 322 ::= { tcpConnEntry 2 } 324 tcpConnLocalPort OBJECT-TYPE 325 SYNTAX INTEGER (0..65535) 326 MAX-ACCESS read-only 327 STATUS current 328 DESCRIPTION 329 "The local port number for this TCP connection." 330 ::= { tcpConnEntry 3 } 332 tcpConnRemAddress OBJECT-TYPE 333 SYNTAX IpAddress 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The remote IP address for this TCP connection." 338 ::= { tcpConnEntry 4 } 340 tcpConnRemPort OBJECT-TYPE 341 SYNTAX INTEGER (0..65535) 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The remote port number for this TCP connection." 346 ::= { tcpConnEntry 5 } 348 tcpInErrs OBJECT-TYPE 349 SYNTAX Counter32 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "The total number of segments received in error (e.g., bad 354 TCP checksums)." 355 ::= { tcp 14 } 357 tcpOutRsts OBJECT-TYPE 358 SYNTAX Counter32 359 MAX-ACCESS read-only 360 STATUS current 361 DESCRIPTION 362 "The number of TCP segments sent containing the RST flag." 363 ::= { tcp 15 } 365 -- conformance information 367 tcpMIBConformance OBJECT IDENTIFIER ::= { tcpMIB 2 } 369 tcpMIBCompliances OBJECT IDENTIFIER ::= { tcpMIBConformance 1 } 370 tcpMIBGroups OBJECT IDENTIFIER ::= { tcpMIBConformance 2 } 372 -- compliance statements 374 tcpMIBCompliance MODULE-COMPLIANCE 375 STATUS current 376 DESCRIPTION 377 "The compliance statement for SNMPv2 entities which 378 implement TCP." 379 MODULE -- this module 380 MANDATORY-GROUPS { tcpGroup 381 } 382 ::= { tcpMIBCompliances 1 } 384 -- units of conformance 386 tcpGroup OBJECT-GROUP 387 OBJECTS { tcpRtoAlgorithm, tcpRtoMin, tcpRtoMax, 388 tcpMaxConn, tcpActiveOpens, 389 tcpPassiveOpens, tcpAttemptFails, 390 tcpEstabResets, tcpCurrEstab, tcpInSegs, 391 tcpOutSegs, tcpRetransSegs, tcpConnState, 392 tcpConnLocalAddress, tcpConnLocalPort, 393 tcpConnRemAddress, tcpConnRemPort, 394 tcpInErrs, tcpOutRsts } 395 STATUS current 396 DESCRIPTION 397 "The tcp group of objects providing for management of TCP 398 entities." 399 ::= { tcpMIBGroups 1 } 401 END 402 3. Acknowledgements 404 This document contains a modified subset of RFC 1213. 406 4. References 408 [1] Information processing systems - Open Systems Interconnection - 409 Specification of Abstract Syntax Notation One (ASN.1), 410 International Organization for Standardization. International 411 Standard 8824, (December, 1987). 413 [2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure 414 of Management Information for version 2 of the Simple Network 415 Management Protocol (SNMPv2)", Internet Draft, SNMP Research, Inc., 416 Cisco Systems, Dover Beach Consulting, Inc., Carnegie Mellon 417 University, March 1995. 419 [3] Postel, J., "Transmission Control Protocol - DARPA Internet Program 420 Protocol Specification", STD 7, RFC 793, DARPA, September 1981. 422 [4] McCloghrie, K., and Rose, M., "Management Information Base for 423 Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 424 1213, March 1991. 426 [5] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1988, 427 Stanford, California. 429 5. Security Considerations 431 Security issues are not discussed in this memo. 433 6. Authors' Addresses 435 Jeffrey D. Case 436 SNMP Research, Inc. 437 3001 Kimberlin Heights Rd. 438 Knoxville, TN 37920-9716 439 US 441 Phone: +1 615 573 1434 442 Email: case@snmp.com 444 Keith McCloghrie 445 Cisco Systems, Inc. 446 170 West Tasman Drive 447 San Jose, CA 95134-1706 448 US 450 Phone: +1 408 526 5260 451 Email: kzm@cisco.com 453 Marshall T. Rose 454 Dover Beach Consulting, Inc. 455 420 Whisman Court 456 Mountain View, CA 94043-2186 457 US 459 Phone: +1 415 968 1052 460 Email: mrose@dbc.mtview.ca.us 462 Steven Waldbusser 463 Carnegie Mellon University 464 5000 Forbes Ave 465 Pittsburgh, PA 15213 466 US 468 Phone: +1 412 268 6628 469 Email: waldbusser@cmu.edu 471 Table of Contents 473 1 Introduction .................................................... 3 474 2 Definitions ..................................................... 4 475 2.1 The TCP Group ................................................. 5 476 2.2 Conformance Information ....................................... 11 477 2.2.1 Compliance Statements ....................................... 11 478 2.2.2 Units of Conformance ........................................ 11 479 3 Acknowledgements ................................................ 12 480 4 References ...................................................... 12 481 5 Security Considerations ......................................... 13 482 6 Authors' Addresses .............................................. 13