idnits 2.17.1 draft-ietf-ipv6-rfc2012-update-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 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 abstract seems to contain references ([RFC793]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 514: '...e been obsoleted. It MUST not be used....' RFC 2119 keyword, line 1089: '...It is RECOMMENDED that implementers co...' RFC 2119 keyword, line 1095: '... Instead, it is RECOMMENDED to deploy...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: -- { tcp 16 } was used to represent the ipv6TcpConnTable in RFC 2452, -- which has since been obsoleted. It MUST not be used. -- 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.) -- The document date (June 2003) is 7614 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3291' is defined on line 1025, but no explicit reference was found in the text == Unused Reference: 'RFC2452' is defined on line 1039, but no explicit reference was found in the text ** Obsolete normative reference: RFC 793 (Obsoleted by RFC 9293) ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Obsolete informational reference (is this intentional?): RFC 2012 (Obsoleted by RFC 4022) -- Obsolete informational reference (is this intentional?): RFC 2452 (Obsoleted by RFC 4022, RFC 8096) Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPv6 MIB Revision Design Team Bill Fenner 2 INTERNET-DRAFT AT&T Research 3 Expires: December 2003 Keith McCloghrie 4 Rajiv Raghunarayan (Editor) 5 Cisco Systems 6 Juergen Schoenwalder 7 TU Braunschweig 8 June 2003 10 Management Information Base 11 for the Transmission Control Protocol (TCP) 12 draft-ietf-ipv6-rfc2012-update-03.txt 14 Status of this Document 16 This document is an Internet-Draft and is in full conformance with all 17 provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering Task 20 Force (IETF), its areas, and its working groups. Note that other 21 groups may also distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference material 26 or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This document is a product of the IPv6 MIB Revision Design Team. 35 Comments should be addressed to the editor/authors or the mailing 36 list at ipng@sunroof.eng.sun.com. 38 Copyright Notice 40 Copyright (C) The Internet Society (2001). All Rights Reserved. 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols in the Internet community. 46 In particular, it describes managed objects used for implementations 47 of the Transmission Control Protocol (TCP) [RFC793] in an IP version 48 independent manner. 50 Table of Contents 52 1. The Internet-Standard Management Framework . . . . . . . . . . 2 53 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . 2 54 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 55 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 7 56 5. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . 22 57 6. Normative References. . . . . . . . . . . . . . . . . . . . . . 22 58 7. Informative References. . . . . . . . . . . . . . . . . . . . . 22 59 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 23 60 9. Editor's Address. . . . . . . . . . . . . . . . . . . . . . . . 24 61 10. Authors. . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 62 11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 25 64 1. The Internet-Standard Management Framework 66 For a detailed overview of the documents that describe the current 67 Internet-Standard Management Framework, please refer to section 7 of 68 RFC 3410 [RFC3410]. 70 Managed objects are accessed via a virtual information store, termed 71 the Management Information Base or MIB. MIB objects are generally 72 accessed through the Simple Network Management Protocol (SNMP). 73 Objects in the MIB are defined using the mechanisms defined in the 74 Structure of Management Information (SMI). This memo specifies a 75 MIB module that is compliant to the SMIv2, which is described in 76 STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, 77 RFC 2580 [RFC2580]. 79 2. Revision History 81 Changes from draft-ietf-ipv6-rfc2012-update-02.txt: 83 16th June 2003 85 Added tcpHCInSegs and tcpHCOutSegs back to the mib, in order to 86 have the 64-bit counters along with the 32-bit counters. 88 Changes from draft-ietf-ipv6-rfc2012-update-01.txt: 90 23rd February 2003 92 Changes in this version mainly concentrate on reducing this mib 93 to a bare minimum update of RFC 2012, enough to satisfy the 94 needs of IPv6. The actual modifications are listed below. 96 Scalars tcpHCInSegs and tcpHCOutSegs dropped. 98 Objects dropped from the tcpConnectionTable include 99 tcpConnectionInSegs, tcpConnectionOutSegs, 100 tcpConnectionInOctets, tcpConnectionOutOctets, 101 tcpConnectionHCInSegs, tcpConnectionHCOutSegs, 102 tcpConnectionHCInOctets, tcpConnectionHCOutOctets, 103 tcpConnectionAge and tcpConnectionId. 105 Objects dropped from tcpListenerTable include 106 tcpListenerTimeOuts, tcpListenerEstablished and tcpListenerAge. 108 Updated compliance statements to reflect the aforementioned 109 changes. 111 Changes from draft-ietf-ipv6-rfc2012-update-00.txt: 113 4th November 2002 115 Replaced the tcpConnectionStartTime and tcpListenerStartTime 116 objects with tcpConnectionAge and tcpListenerAge respectively. 118 Added tcpConnectionRemAddressType as an auxiliary object into 119 the tcpConnectionTable. 121 Added new object, tcpConnectionId, to provide a link into the 122 TCP-ESTATS-MIB. 124 Included tcpConnectionAge and tcpConnectionProcess into the 125 tcpConnectionGroup. 127 Included tcpListenerAge and tcpListenerProcess into the 128 tcpListenerGroup. 130 tcpListenerGroup added to the mandatory list for compliance. 132 Changes from draft-ietf-ipngwg-rfc2012-update-01.txt: 134 27 June 2002 136 Replaced all occurrences of the term packets to segments, to be 137 consistent with the TCP specification. 139 Added limits to tcpRtoMin, tcpRtoMax and tcpMaxConn. 141 Added the scalar, tcpListenerTableLastChange. 143 Updated the description of tcpConnectionLocalAddress - removed 144 reference to 'listen' state. 146 Updated the description tcpConnection*Octets to explicitly 147 indicate whether the count includes the TCP header octets. 149 Updated the description of tcpConnectionStartTime and 150 tcpListenerStartTime - added clarifying text. 152 Renamed tcpConnectionProcessID to tcpConnectionProcess. 154 Updated the description of tcpListenerTable. 156 Updated the description of tcpListenerLocalAddressType to include 157 unknown (0) as a valid value. 159 Updated the description of tcpListenerLocalAddress - the value 160 ''h (zero-length octet-string) represents the case wherein an 161 application is will to accept connections for any IP interface 162 associated with the node. 164 Removed tcpListenerRemAddressType. 166 Removed tcpListenerHCConnectionsTimedOut and 167 tcpListenerHCConnectionsAccepted. Added them to open issues, to 168 be added iff deemed required after discussions. 170 Renamed tcpListenerConnectionsAccepted to tcpListenerEstablished 171 and tcpListenerConnectionsTimedOut to tcpListenerTimeOuts. 173 Renamed tcpListenerProcessID to tcpListenerProcess. 175 Updated compliance statement for the object tcpConnectionState - 176 support for the value 'deleteTCB (12)' deemed optional. 178 Added RFC 2790 and RFC 2287 to the References section. 180 Updated Contact-Info and Editor's address. 182 Added Authors section. 184 Changes from draft-ietf-ipngwg-rfc2012-update-00.txt: 186 14 November 2001 188 Added HC versions of connection counters. 190 Added Listener table, with counters for accepted and timed out 191 connection attempts. 193 Added tcp{Connection,Listener}ProcessID to index into SYSAPPL-MIB 194 or HOST-RESOURCES-MIB. 196 Removed tcpConnectionRemAddrType, it must be the same as 197 tcpConnectionLocalAddrType. 199 Changes from draft-ops-rfc2012-update-00.txt 201 12 Jul 2001 203 Turned into IPNG WG document 205 Added tcpCountersGroup for per-connection counters 207 Changes from first draft posted to v6mib mailing list: 209 23 Feb 2001 211 Made threshold for HC packet counters 1Mpps 213 Added copyright statements and table of contents 215 21 Feb 2001 -- Juergen's changes 217 Renamed tcpInetConn* to tcpConnection* 219 Updated Conformance info 221 Added missing tcpConnectionState and tcpConnState objects to 222 SEQUENCEs 224 6 Feb 2001 226 Removed v6-only objects. 228 Renamed inetTcp* to tcpInet* 230 Added SIZE restriction to InetAddress index objects. (36 = 231 32-byte addresses plus 4-byte scope, but it's just a strawman) 233 Used InetPortNumber TC from updated INET-ADDRESS-MIB 235 Updated compliance statements. 237 Added Keith to authors 239 Added open issues section. 241 Changes from RFC 2012 243 Deprecated tcpConnTable 245 Added tcpConnectionTable 247 3. Overview 249 The current TCP-MIB defined in this memo consists of two tables an 250 a group of scalars: 252 - The tcp group of scalars reports parameters and statistics of a 253 TCP protocol engine. 255 - The tcpConnectionTable provides access to status information for 256 all TCP connections handled by a TCP protocol engine. In addition 257 the table also reports identification of the operating system 258 level processes which handle the TCP connections. 260 - The tcpListenerTable provides access to information about all TCP 261 listening endpoints known by a TCP protocol engine. And similar 262 to the case of the connection table, the tcpListenerTable also 263 reports the identification of the operating system level 264 processes which handle this listening TCP endpoint. 266 3.1 Relationship to Other MIBs 268 This section discusses the relationship of this TCP-MIB module to 269 other MIB modules. 271 3.1.1 Relationship to RFC1213-MIB 273 TCP related MIB objects were originally defined as part of the 274 RFC1213-MIB defined in RFC 1213 [RFC1213]. The TCP related objects 275 of the RFC1213-MIB were later copied into a separate MIB module and 276 published in RFC 2012 [RFC2012] in SMIv2 format. 278 The previous versions of the TCP-MIB both defined the tcpConnTable, 279 which has been deprecated for basically two reasons: 281 (1) The tcpConnTable only supports IPv4. 283 The current approach in the IETF is to write IP version neutral 284 MIBs rather than having different definitions for various 285 version of IP. This reduces the amount of overhead when new 286 objects are introduced since there is only one place to add 287 them. Hence, the approach taken in RFC 2452 of having separate 288 tables is not continued. 290 (2) The tcpConnTable mixes listening endpoints with connections. 292 It turns out that connections tend to have a different behaviour 293 and management access pattern compared to listening endpoints. 294 Splitting the original tcpConnTable into two tables thus allows 295 to add specific status and statistic objects for listening 296 endpoints and connections. 298 3.1.2 Relationship to IPV6-TCP-MIB 300 The IPV6-TCP-MIB defined in RFC 2452 has been moved to Historic 301 since the approach of having separate IP version specific tables is 302 not followed anymore. Implementation of RFC 2452 is thus not 303 suggested anymore. 305 3.1.3 Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB 307 The tcpConnectionTable and the tcpListenerTable report the 308 identification of the operating system level process which handles 309 a connection or a listening endpoint. The value is reported as an 310 Unsigned32 which is expected to be the same as the hrSWRunIndex of 311 the HOST-RESOURCES-MIB [RFC2790] (if the value is smaller than 312 2147483647) or the sysApplElmtRunIndex of the SYSAPPL-MIB [RFC2287]. 313 This allows managment applications to identify the TCP connections 314 that belong to an operating system level process which has proven 315 to be valuable in operational environments. 317 4. Definitions 319 TCP-MIB DEFINITIONS ::= BEGIN 321 IMPORTS 322 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, 323 Gauge32, Counter32, Counter64, IpAddress, mib-2 324 FROM SNMPv2-SMI 325 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 326 InetAddress, InetAddressType, 327 InetPortNumber FROM INET-ADDRESS-MIB; 329 tcpMIB MODULE-IDENTITY 330 LAST-UPDATED "200306160000Z" 331 ORGANIZATION "IETF IPv6 MIB Revision Team" 332 CONTACT-INFO 333 "Rajiv Raghunarayan (editor) 335 Cisco Systems Inc. 336 170 West Tasman Drive 337 San Jose, CA 95134 339 Phone: +1 408 853 9612 340 Email: " 341 DESCRIPTION 342 "The MIB module for managing TCP implementations." 343 REVISION "200306160000Z" 344 DESCRIPTION 345 "IP version neutral revision, published as RFC XXXX." 346 REVISION "9411010000Z" 347 DESCRIPTION 348 "Initial SMIv2 version, published as RFC 2012." 350 REVISION "9103310000Z" 351 DESCRIPTION 352 "The initial revision of this MIB module was part of 353 MIB-II." 354 ::= { mib-2 49 } 356 -- the TCP base variables group 358 tcp OBJECT IDENTIFIER ::= { mib-2 6 } 360 -- Scalars 362 tcpRtoAlgorithm OBJECT-TYPE 363 SYNTAX INTEGER { 364 other(1), -- none of the following 365 constant(2), -- a constant rto 366 rsre(3), -- MIL-STD-1778, Appendix B 367 vanj(4) -- Van Jacobson's algorithm [VANJ] 368 } 369 MAX-ACCESS read-only 370 STATUS current 371 DESCRIPTION 372 "The algorithm used to determine the timeout value used for 373 retransmitting unacknowledged octets." 374 ::= { tcp 1 } 376 tcpRtoMin OBJECT-TYPE 377 SYNTAX Integer32 (0..2147483647) 378 UNITS "milliseconds" 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The minimum value permitted by a TCP implementation for the 383 retransmission timeout, measured in milliseconds. More 384 refined semantics for objects of this type depend upon the 385 algorithm used to determine the retransmission timeout. In 386 particular, when the timeout algorithm is rsre(3), an 387 object of this type has the semantics of the LBOUND 388 quantity described in RFC 793." 389 ::= { tcp 2 } 391 tcpRtoMax OBJECT-TYPE 392 SYNTAX Integer32 (0..2147483647) 393 UNITS "milliseconds" 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "The maximum value permitted by a TCP implementation for the 398 retransmission timeout, measured in milliseconds. More 399 refined semantics for objects of this type depend upon the 400 algorithm used to determine the retransmission timeout. In 401 particular, when the timeout algorithm is rsre(3), an 402 object of this type has the semantics of the UBOUND 403 quantity described in RFC 793." 404 ::= { tcp 3 } 406 tcpMaxConn OBJECT-TYPE 407 SYNTAX Integer32 (-1 | 0..2147483647) 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The limit on the total number of TCP connections the entity 412 can support. In entities where the maximum number of 413 connections is dynamic, this object should contain the 414 value -1." 415 ::= { tcp 4 } 417 tcpActiveOpens OBJECT-TYPE 418 SYNTAX Counter32 419 MAX-ACCESS read-only 420 STATUS current 421 DESCRIPTION 422 "The number of times TCP connections have made a direct 423 transition to the SYN-SENT state from the CLOSED state." 424 ::= { tcp 5 } 426 tcpPassiveOpens OBJECT-TYPE 427 SYNTAX Counter32 428 MAX-ACCESS read-only 429 STATUS current 430 DESCRIPTION 431 "The number of times TCP connections have made a direct 432 transition to the SYN-RCVD state from the LISTEN state." 433 ::= { tcp 6 } 435 tcpAttemptFails OBJECT-TYPE 436 SYNTAX Counter32 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The number of times TCP connections have made a direct 441 transition to the CLOSED state from either the SYN-SENT 442 state or the SYN-RCVD state, plus the number of times TCP 443 connections have made a direct transition to the LISTEN 444 state from the SYN-RCVD state." 445 ::= { tcp 7 } 447 tcpEstabResets OBJECT-TYPE 448 SYNTAX Counter32 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The number of times TCP connections have made a direct 453 transition to the CLOSED state from either the ESTABLISHED 454 state or the CLOSE-WAIT state." 455 ::= { tcp 8 } 457 tcpCurrEstab OBJECT-TYPE 458 SYNTAX Gauge32 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The number of TCP connections for which the current state 463 is either ESTABLISHED or CLOSE-WAIT." 464 ::= { tcp 9 } 466 tcpInSegs OBJECT-TYPE 467 SYNTAX Counter32 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The total number of segments received, including those 472 received in error. This count includes segments received 473 on currently established connections." 474 ::= { tcp 10 } 476 tcpOutSegs OBJECT-TYPE 477 SYNTAX Counter32 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION 481 "The total number of segments sent, including those on 482 current connections but excluding those containing only 483 retransmitted octets." 484 ::= { tcp 11 } 486 tcpRetransSegs OBJECT-TYPE 487 SYNTAX Counter32 488 MAX-ACCESS read-only 489 STATUS current 490 DESCRIPTION 491 "The total number of segments retransmitted - that is, the 492 number of TCP segments transmitted containing one or more 493 previously transmitted octets." 494 ::= { tcp 12 } 496 tcpInErrs OBJECT-TYPE 497 SYNTAX Counter32 498 MAX-ACCESS read-only 499 STATUS current 500 DESCRIPTION 501 "The total number of segments received in error (e.g., bad 502 TCP checksums)." 503 ::= { tcp 14 } 505 tcpOutRsts OBJECT-TYPE 506 SYNTAX Counter32 507 MAX-ACCESS read-only 508 STATUS current 509 DESCRIPTION 510 "The number of TCP segments sent containing the RST flag." 511 ::= { tcp 15 } 513 -- { tcp 16 } was used to represent the ipv6TcpConnTable in RFC 2452, 514 -- which has since been obsoleted. It MUST not be used. 516 tcpHCInSegs OBJECT-TYPE 517 SYNTAX Counter64 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The total number of segments received, including those 522 received in error. This count includes segments received 523 on currently established connections. This object is 524 the 64-bit equivalent of tcpInSegs." 525 ::= { tcp 17 } 527 tcpHCOutSegs OBJECT-TYPE 528 SYNTAX Counter64 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "The total number of segments sent, including those on 533 current connections but excluding those containing only 534 retransmitted octets. This object is the 64-bit 535 equivalent of tcpOutSegs." 536 ::= { tcp 18 } 538 -- The TCP Connection table 540 tcpConnectionTable OBJECT-TYPE 541 SYNTAX SEQUENCE OF TcpConnectionEntry 542 MAX-ACCESS not-accessible 543 STATUS current 544 DESCRIPTION 545 "A table containing information about existing TCP 546 connections. Note that unlike earlier TCP MIBs, there 547 is a seperate table for connections in the LISTEN state." 548 ::= { tcp 19 } 550 tcpConnectionEntry OBJECT-TYPE 551 SYNTAX TcpConnectionEntry 552 MAX-ACCESS not-accessible 553 STATUS current 554 DESCRIPTION 555 "A conceptual row of the tcpConnectionTable containing 556 information about a particular current TCP connection. 557 Each row of this table is transient, in that it ceases to 558 exist when (or soon after) the connection makes the 559 transition to the CLOSED state." 560 INDEX { tcpConnectionLocalAddressType, 561 tcpConnectionLocalAddress, 562 tcpConnectionLocalPort, 563 tcpConnectionRemAddressType, 564 tcpConnectionRemAddress, 565 tcpConnectionRemPort } 566 ::= { tcpConnectionTable 1 } 568 TcpConnectionEntry ::= SEQUENCE { 569 tcpConnectionLocalAddressType InetAddressType, 570 tcpConnectionLocalAddress InetAddress, 571 tcpConnectionLocalPort InetPortNumber, 572 tcpConnectionRemAddressType InetAddressType, 573 tcpConnectionRemAddress InetAddress, 574 tcpConnectionRemPort InetPortNumber, 575 tcpConnectionState INTEGER, 576 tcpConnectionProcess Unsigned32 577 } 579 tcpConnectionLocalAddressType OBJECT-TYPE 580 SYNTAX InetAddressType 581 MAX-ACCESS not-accessible 582 STATUS current 583 DESCRIPTION 584 "The address type of tcpConnectionLocalAddress. Only IPv4, 585 IPv4z, IPv6 and IPv6z address types are expected." 586 ::= { tcpConnectionEntry 1 } 588 tcpConnectionLocalAddress OBJECT-TYPE 589 SYNTAX InetAddress (SIZE(0..36)) 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "The local IP address for this TCP connection." 594 ::= { tcpConnectionEntry 2 } 596 tcpConnectionLocalPort OBJECT-TYPE 597 SYNTAX InetPortNumber 598 MAX-ACCESS not-accessible 599 STATUS current 600 DESCRIPTION 601 "The local port number for this TCP connection." 602 ::= { tcpConnectionEntry 3 } 604 tcpConnectionRemAddressType OBJECT-TYPE 605 SYNTAX InetAddressType 606 MAX-ACCESS not-accessible 607 STATUS current 608 DESCRIPTION 609 "The address type of tcpConnectionRemAddress. Only IPv4, 610 IPv4z, IPv6 and IPv6z address types are expected." 611 ::= { tcpConnectionEntry 4 } 613 tcpConnectionRemAddress OBJECT-TYPE 614 SYNTAX InetAddress (SIZE(0..36)) 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "The remote IP address for this TCP connection." 619 ::= { tcpConnectionEntry 5 } 621 tcpConnectionRemPort OBJECT-TYPE 622 SYNTAX InetPortNumber 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "The remote port number for this TCP connection." 627 ::= { tcpConnectionEntry 6 } 629 tcpConnectionState OBJECT-TYPE 630 SYNTAX INTEGER { 631 closed(1), 632 listen(2), -- do we need this here??? 633 synSent(3), 634 synReceived(4), 635 established(5), 636 finWait1(6), 637 finWait2(7), 638 closeWait(8), 639 lastAck(9), 640 closing(10), 641 timeWait(11), 642 deleteTCB(12) 643 } 644 MAX-ACCESS read-write 645 STATUS current 646 DESCRIPTION 647 "The state of this TCP connection. 649 The value listen(2) is included only for parallelism to the 650 old tcpConnTable, and should not be used. A connection in 651 LISTEN state should be present in the tcpListenerTable. 653 The only value which may be set by a management station is 654 deleteTCB(12). Accordingly, it is appropriate for an agent 655 to return a `badValue' response if a management station 656 attempts to set this object to any other value. 658 If a management station sets this object to the value 659 deleteTCB(12), then this has the effect of deleting the TCB 660 (as defined in RFC 793) of the corresponding connection on 661 the managed node, resulting in immediate termination of the 662 connection. 664 As an implementation-specific option, a RST segment may be 665 sent from the managed node to the other TCP endpoint (note 666 however that RST segments are not sent reliably)." 667 ::= { tcpConnectionEntry 7 } 669 tcpConnectionProcess OBJECT-TYPE 670 SYNTAX Unsigned32 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The system's process ID for the process associated with 675 this connection, or zero if there is no such process. This 676 value is expected to be the same as HOST-RESOURCES-MIB:: 677 hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some 678 row in the appropriate tables." 679 ::= { tcpConnectionEntry 8 } 681 -- The TCP Listener table 683 tcpListenerTable OBJECT-TYPE 684 SYNTAX SEQUENCE OF TcpListenerEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "A table containing information about TCP listeners. A 689 listening application can be represented in three 690 possible ways: 692 1. An application that is willing to accept both IPv4 and 693 IPv6 datagrams is represented by 694 tcpListenerLocalAddressType of unknown (0) and 695 tcpListenerLocalAddress of ''h (a zero-length 696 octet-string). 698 2. An application which is willing to accept only IPv4 or 699 IPv6 datagrams is represented by a 700 tcpListenerLocalAddressType of the appropriate address 701 type and tcpListenerLocalAddress of ''h (a zero-length 702 octet-string). 704 3. An application which is a listening for data destined 705 only to a specific IP address, but from any remote 706 system, is represented by a tcpListenerLocalAddressType 707 of an appropriate address type, with 708 tcpListenerLocalAddress the specific local address. 710 NOTE: that address type in this table represents the 711 address type used for the communication, irrespective 712 of the higher-layer abstraction. For example, an 713 application using IPv6 'sockets' to communicate via 714 IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would 715 use InetAddressType ipv4(1))." 716 ::= { tcp 20 } 718 tcpListenerEntry OBJECT-TYPE 719 SYNTAX TcpListenerEntry 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "A conceptual row of the tcpListenerTable containing 724 information about a particular TCP listener." 725 INDEX { tcpListenerLocalAddressType, 726 tcpListenerLocalAddress, 727 tcpListenerLocalPort } 728 ::= { tcpListenerTable 1 } 730 TcpListenerEntry ::= SEQUENCE { 731 tcpListenerLocalAddressType InetAddressType, 732 tcpListenerLocalAddress InetAddress, 733 tcpListenerLocalPort InetPortNumber, 734 tcpListenerProcess Unsigned32 735 } 737 tcpListenerLocalAddressType OBJECT-TYPE 738 SYNTAX InetAddressType 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "The address type of tcpListenerLocalAddress. Only IPv4, 743 IPv4z, IPv6 and IPv6z address types are expected, or 744 unknown (0) if connection initiation to all local IP 745 addresses are accepted. " 746 ::= { tcpListenerEntry 1 } 748 tcpListenerLocalAddress OBJECT-TYPE 749 SYNTAX InetAddress (SIZE(0..36)) 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "The local IP address for this TCP connection. In the case 754 of a listener which is willing to accept connections for 755 any IP interface associated with the node, a value of ''h 756 (zero-length octet-string) is used." 757 ::= { tcpListenerEntry 2 } 759 tcpListenerLocalPort OBJECT-TYPE 760 SYNTAX InetPortNumber 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "The local port number for this TCP connection." 765 ::= { tcpListenerEntry 3 } 767 tcpListenerProcess OBJECT-TYPE 768 SYNTAX Unsigned32 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "The system's process ID for the process associated with 773 this listener, or zero if there is no such process. This 774 value is expected to be the same as HOST-RESOURCES-MIB:: 775 hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some 776 row in the appropriate tables." 777 ::= { tcpListenerEntry 4 } 779 -- The deprecated TCP Connection table 781 tcpConnTable OBJECT-TYPE 782 SYNTAX SEQUENCE OF TcpConnEntry 783 MAX-ACCESS not-accessible 784 STATUS deprecated 785 DESCRIPTION 786 "A table containing information about existing IPv4-specific 787 TCP connections or listeners. This table has been 788 deprecated in favor of the version neutral 789 tcpConnectionTable." 790 ::= { tcp 13 } 792 tcpConnEntry OBJECT-TYPE 793 SYNTAX TcpConnEntry 794 MAX-ACCESS not-accessible 795 STATUS deprecated 796 DESCRIPTION 797 "A conceptual row of the tcpConnTable containing information 798 about a particular current IPv4 TCP connection. Each row 799 of this table is transient, in that it ceases to exist when 800 (or soon after) the connection makes the transition to the 801 CLOSED state." 802 INDEX { tcpConnLocalAddress, 803 tcpConnLocalPort, 804 tcpConnRemAddress, 805 tcpConnRemPort } 806 ::= { tcpConnTable 1 } 808 TcpConnEntry ::= SEQUENCE { 809 tcpConnState INTEGER, 810 tcpConnLocalAddress IpAddress, 811 tcpConnLocalPort Integer32, 812 tcpConnRemAddress IpAddress, 813 tcpConnRemPort Integer32 814 } 816 tcpConnState OBJECT-TYPE 817 SYNTAX INTEGER { 818 closed(1), 819 listen(2), 820 synSent(3), 821 synReceived(4), 822 established(5), 823 finWait1(6), 824 finWait2(7), 825 closeWait(8), 826 lastAck(9), 827 closing(10), 828 timeWait(11), 829 deleteTCB(12) 830 } 831 MAX-ACCESS read-write 832 STATUS deprecated 833 DESCRIPTION 834 "The state of this TCP connection. 836 The only value which may be set by a management station is 837 deleteTCB(12). Accordingly, it is appropriate for an agent 838 to return a `badValue' response if a management station 839 attempts to set this object to any other value. 841 If a management station sets this object to the value 842 deleteTCB(12), then this has the effect of deleting the TCB 843 (as defined in RFC 793) of the corresponding connection on 844 the managed node, resulting in immediate termination of the 845 connection. 847 As an implementation-specific option, a RST segment may be 848 sent from the managed node to the other TCP endpoint (note 849 however that RST segments are not sent reliably)." 850 ::= { tcpConnEntry 1 } 852 tcpConnLocalAddress OBJECT-TYPE 853 SYNTAX IpAddress 854 MAX-ACCESS read-only 855 STATUS deprecated 856 DESCRIPTION 857 "The local IP address for this TCP connection. In the case 858 of a connection in the listen state which is willing to 859 accept connections for any IP interface associated with the 860 node, the value 0.0.0.0 is used." 861 ::= { tcpConnEntry 2 } 863 tcpConnLocalPort OBJECT-TYPE 864 SYNTAX Integer32 (0..65535) 865 MAX-ACCESS read-only 866 STATUS deprecated 867 DESCRIPTION 868 "The local port number for this TCP connection." 869 ::= { tcpConnEntry 3 } 871 tcpConnRemAddress OBJECT-TYPE 872 SYNTAX IpAddress 873 MAX-ACCESS read-only 874 STATUS deprecated 875 DESCRIPTION 876 "The remote IP address for this TCP connection." 877 ::= { tcpConnEntry 4 } 879 tcpConnRemPort OBJECT-TYPE 880 SYNTAX Integer32 (0..65535) 881 MAX-ACCESS read-only 882 STATUS deprecated 883 DESCRIPTION 884 "The remote port number for this TCP connection." 885 ::= { tcpConnEntry 5 } 887 -- conformance information 889 tcpMIBConformance OBJECT IDENTIFIER ::= { tcpMIB 2 } 891 tcpMIBCompliances OBJECT IDENTIFIER ::= { tcpMIBConformance 1 } 892 tcpMIBGroups OBJECT IDENTIFIER ::= { tcpMIBConformance 2 } 893 -- compliance statements 895 tcpMIBCompliance2 MODULE-COMPLIANCE 896 STATUS current 897 DESCRIPTION 898 "The compliance statement for systems which implement TCP." 899 MODULE -- this module 900 MANDATORY-GROUPS { tcpBaseGroup, tcpConnectionGroup, 901 tcpListenerGroup } 902 GROUP tcpHCGroup 903 DESCRIPTION 904 "This group is mandatory for those systems which are capable 905 of receiving or transmitting more than 1 million TCP 906 segments per second. 1 million segments per second will 907 cause a Counter32 to wrap in just over an hour." 908 OBJECT tcpConnectionState 909 SYNTAX INTEGER { closed(1), listen(2), synSent(3), 910 synReceived(4), established(5), 911 finWait1(6), finWait2(7), closeWait(8), 912 lastAck(9), closing(10), timeWait(11) } 913 MIN-ACCESS read-only 914 DESCRIPTION 915 "Write access is not required, nor is support for the value 916 deleteTCB (12)." 917 ::= { tcpMIBCompliances 2 } 919 tcpMIBCompliance MODULE-COMPLIANCE 920 STATUS deprecated 921 DESCRIPTION 922 "The compliance statement for IPv4-only systems which 923 implement TCP. In order to be IP version independent, this 924 compliance statement is deprecated in favor of 925 tcpMIBCompliance2. However, agents are still encouraged 926 to implement these objects in order to interoperate with 927 the deployed base of managers." 928 MODULE -- this module 929 MANDATORY-GROUPS { tcpGroup } 930 OBJECT tcpConnState 931 MIN-ACCESS read-only 932 DESCRIPTION 933 "Write access is not required." 934 ::= { tcpMIBCompliances 1 } 936 -- units of conformance 938 tcpGroup OBJECT-GROUP 939 OBJECTS { tcpRtoAlgorithm, tcpRtoMin, tcpRtoMax, 940 tcpMaxConn, tcpActiveOpens, 941 tcpPassiveOpens, tcpAttemptFails, 942 tcpEstabResets, tcpCurrEstab, tcpInSegs, 943 tcpOutSegs, tcpRetransSegs, tcpConnState, 944 tcpConnLocalAddress, tcpConnLocalPort, 945 tcpConnRemAddress, tcpConnRemPort, 946 tcpInErrs, tcpOutRsts } 947 STATUS deprecated 948 DESCRIPTION 949 "The tcp group of objects providing for management of TCP 950 entities." 951 ::= { tcpMIBGroups 1 } 953 tcpBaseGroup OBJECT-GROUP 954 OBJECTS { tcpRtoAlgorithm, tcpRtoMin, tcpRtoMax, 955 tcpMaxConn, tcpActiveOpens, 956 tcpPassiveOpens, tcpAttemptFails, 957 tcpEstabResets, tcpCurrEstab, tcpInSegs, 958 tcpOutSegs, tcpRetransSegs, 959 tcpInErrs, tcpOutRsts } 960 STATUS current 961 DESCRIPTION 962 "The group of counters common to TCP entities." 963 ::= { tcpMIBGroups 2 } 965 tcpConnectionGroup OBJECT-GROUP 966 OBJECTS { tcpConnectionState, tcpConnectionProcess } 967 STATUS current 968 DESCRIPTION 969 "The group provides general information about TCP 970 connections." 971 ::= { tcpMIBGroups 3 } 973 tcpListenerGroup OBJECT-GROUP 974 OBJECTS { tcpListenerProcess } 975 STATUS current 976 DESCRIPTION 977 "This group has objects providing general information about 978 TCP listeners." 979 ::= { tcpMIBGroups 4 } 981 tcpHCGroup OBJECT-GROUP 982 OBJECTS { tcpHCInSegs, tcpHCOutSegs } 983 STATUS current 984 DESCRIPTION 985 "The group of objects providing for counters of high speed 986 TCP implementations." 987 ::= { tcpMIBGroups 5 } 989 END 991 5. Acknowledgements 993 This document contains a modified subset of RFC 1213 and updates RFC 994 2012 and RFC 2452. Acknowledgements are therefore due to the authors 995 and editors of these documents for their excellent work. Several 996 useful comments regarding usability and design were also received 997 from Kristine Adamson. The authors would like to like all these 998 people for their contribution to this effort. 1000 6. Normative References 1002 [RFC793] Postel, J., "Transmission Control Protocol - DARPA Internet 1003 Program Protocol Specification", STD 7, RFC 793, DARPA, 1004 September 1981. 1006 [RFC2287] Krupczak, C., Saperia, J., "Definitions of System-Level 1007 Managed Objects for Applications", RFC 2287, February 1998. 1009 [RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB", RFC 2790, 1010 March 2000. 1012 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1013 Rose, M. and S. Waldbusser, "Structure of Management 1014 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1015 1999. 1017 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1018 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 1019 STD 58, RFC 2579, April 1999. 1021 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1022 Rose, M. and S. Waldbusser, "Conformance Statements for 1023 SMIv2", STD 58, RFC 2580, April 1999. 1025 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and Schoenwaelder, 1026 J., "Textual Conventions for Internet Network Addresses", 1027 RFC 3291, May 2002. 1029 7. Informative References 1031 [RFC1213] Rose, M. and K. McCloghrie, "Management Information Base 1032 for Network Management of TCP/IP-based internets", RFC 1213, 1033 March 1991. 1035 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1036 Transmission Control Protocol using SMIv2", RFC 2012, 1037 November 1996. 1039 [RFC2452] Daniele, M., "IP Version 6 Management Information Base for 1040 the Transmission Control Protocol", RFC 2452, December 1998. 1042 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1043 "Introduction and Applicability Statements for Internet- 1044 Standard Management Framework", RFC 3410, December 2002. 1046 [VANJ] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1047 1988, Stanford, California. 1049 8. Security Considerations 1051 There are management objects defined in this MIB that have a 1052 MAX-ACCESS clause of read-write. Such objects may be considered 1053 sensitive or vulnerable in some network environments. The support 1054 for SET operations in a non-secure environment without proper 1055 protection can have a negative effect on network operations. 1056 These are the tables and objects and their sensitivity/vulnerability: 1058 o The tcpConnectionState and tcpConnState objects have a MAX-ACCESS 1059 clause of read-write, which allows termination of an arbitrary 1060 connection. Unauthorized access could cause a denial of service. 1062 Some of the readable objects in this MIB module (i.e., objects with a 1063 MAX-ACCESS other than not-accessible) may be considered sensitive or 1064 vulnerable in some network environments. It is thus important to 1065 control even GET and/or NOTIFY access to these objects and possibly 1066 to even encrypt the values of these objects when sending them over 1067 the network via SNMP. These are the tables and objects and their 1068 sensitivity/vulnerability: 1070 o The tcpConnectionTable and the tcpConnTable contain objects 1071 providing information on the active connections on the device, 1072 the status of these connections and the associated processes. 1073 This information may be used by an attacker to launch attacks 1074 against known/unknown weakness in certain protocols/applications. 1076 o The tcpListenerTable and the tcpConnTable contain objects providing 1077 information on listeners on an entity. For e.g. the 1078 tcpListenerLocalPort and tcpConnLocalPort objects can be used 1079 to identify what ports are open on the machine and can thus what 1080 attacks are likely to succeed, without the attacker having to run a 1081 port scanner. 1083 SNMP versions prior to SNMPv3 did not include adequate security. 1084 Even if the network itself is secure (for example by using IPSec), 1085 even then, there is no control as to who on the secure network is 1086 allowed to access and GET/SET (read/change/create/delete) the objects 1087 in this MIB module. 1089 It is RECOMMENDED that implementers consider the security features as 1090 provided by the SNMPv3 framework (see [RFC3410], section 8), 1091 including full support for the SNMPv3 cryptographic mechanisms (for 1092 authentication and privacy). 1094 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1095 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1096 enable cryptographic security. It is then a customer/operator 1097 responsibility to ensure that the SNMP entity giving access to an 1098 instance of this MIB module is properly configured to give access to 1099 the objects only to those principals (users) that have legitimate 1100 rights to indeed GET or SET (change/create/delete) them. 1102 9. Editor's Address 1104 Rajiv Raghunarayan 1105 Cisco Systems Inc. 1106 170 West Tasman Drive 1107 San Jose, CA 95134 1108 USA 1110 Email: raraghun@cisco.com 1112 10. Authors 1114 This document is an output of the IPv6 MIB revision team, and 1115 contributors to earlier versions of this document include: 1117 Bill Fenner, AT&T Labs -- Research 1118 Email: fenner@research.att.com 1120 Brian Haberman 1121 Email: bkhabs@nc.rr.com 1123 Shawn A. Routhier, Wind River 1124 Email: sar@epilogue.com 1126 Juergen Schoenwalder, TU Braunschweig 1127 Email: schoenw@ibr.cs.tu-bs.de 1129 Dave Thaler, Microsoft 1130 Email: dthaler@windows.microsoft 1132 This documents updates parts of the MIBs from several documents. RFC 1133 2012 has been the base document for these updations. RFC 2452 was 1134 the first document to define the managed objects for implementations 1135 of TCP over IPv6. 1137 RFC 2012: 1139 Keith McCloghrie, Cisco Systems (Editor) 1140 kzm@cisco.com 1142 RFC 2452: 1144 Mike Daniele, Compaq Computer Corporation 1145 daniele@zk3.dec.com 1147 11. Full Copyright Statement 1149 Copyright (C) The Internet Society (2002). All Rights Reserved. 1151 This document and translations of it may be copied and furnished to 1152 others, and derivative works that comment on or otherwise explain it or 1153 assist in its implementation may be prepared, copied, published and 1154 distributed, in whole or in part, without restriction of any kind, 1155 provided that the above copyright notice and this paragraph are 1156 included on all such copies and derivative works. However, this 1157 document itself may not be modified in any way, such as by removing the 1158 copyright notice or references to the Internet Society or other 1159 Internet organizations, except as needed for the purpose of developing 1160 Internet standards in which case the procedures for copyrights defined 1161 in the Internet Standards process must be followed, or as required to 1162 translate it into languages other than English. 1164 The limited permissions granted above are perpetual and will not be 1165 revoked by the Internet Society or its successors or assigns. 1167 This document and the information contained herein is provided on an 1168 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1169 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 1170 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 1171 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 1172 OR FITNESS FOR A PARTICULAR PURPOSE.