idnits 2.17.1 draft-ietf-ipngwg-ipv6-udp-tcp-mib-01.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-26) 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 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 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. ** There are 4 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 18 has weird spacing: '... This docum...' == Line 19 has weird spacing: '...working docum...' == Line 20 has weird spacing: '...working group...' == Line 21 has weird spacing: '... groups may ...' == Line 25 has weird spacing: '...-Drafts may ...' == (34 more instances...) -- 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 (March 1997) is 9904 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: '2' is defined on line 653, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 673, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 676, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '4') ** Obsolete normative reference: RFC 1905 (ref. '5') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1573 (ref. '6') (Obsoleted by RFC 2233) ** Obsolete normative reference: RFC 1883 (ref. '7') (Obsoleted by RFC 2460) -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '9' Summary: 15 errors (**), 0 flaws (~~), 10 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft IPv6 MIB: UDP and TCP Groups March 1997 4 Management Information Base for IP Version 6: 5 UDP and TCP Groups 7 9 Mon Mar 24 09:49:16 EST 1997 11 Dimitry Haskin 12 Steve Onishi 14 Bay Networks, Inc. 16 Status of this Memo 18 This document is an Internet-Draft. Internet-Drafts are 19 working documents of the Internet Engineering Task Force 20 (IETF), its areas, and its working groups. Note that other 21 groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months. Internet-Drafts may be updated, replaced, or 26 obsoleted by other documents at any time. It is not 27 appropriate to use Internet-Drafts as reference material or to 28 cite them other than as a ``working draft'' or ``work in 29 progress.'' 31 To learn the current status of any Internet-Draft, please 32 check the ``1id-abstracts.txt'' listing contained in the 33 Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), 34 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 35 ds.internic.net (US East Coast), or ftp.isi.edu (US West 36 Coast). 38 Abstract 40 This document is one in the series of documents that define 41 various MIB object groups for IPv6. Specifically, the UDP and 42 TCP groups are defined in this document. 44 This memo defines an experimental portion of the Management 45 Information Base (MIB) for use with network management 46 protocols in the IPv6-based internets. 48 This document specifies a MIB module in a manner that is both 49 compliant to the SNMPv2 SMI, and semantically identical to the 50 peer SNMPv1 definitions. 52 Table of Contents 54 1. The SNMPv2 Network Management Framework ............. 3 55 1.1 Object Definitions ................................ 3 56 2. Overview ............................................ 4 57 3. The UDP Group ....................................... 5 58 4. The TCP Group ....................................... 9 59 5. Acknowledgments .................................... 18 60 6. References .......................................... 18 61 7. Security Considerations ............................. 19 62 8. Authors' Addresses................................... 19 64 1. The SNMPv2 Network Management Framework 66 The SNMPv2 Network Management Framework presently consists of 67 three major components. They are: 69 o the SMI, described in RFC 1902 [1] - the mechanisms used 70 for describing and naming objects for the purpose of 71 management. 73 o the MIB-II, described in RFC 1213/STD 17 [3] - the core 74 set of managed objects for the Internet suite of 75 protocols. 77 o RFC 1157 [4] and RFC 1905 [5] which define two versions 78 of the protocol used for network access to managed 79 objects. 81 The Framework permits new objects to be defined for the 82 purpose of experimentation and evaluation. 84 1.1. Object Definitions 86 Managed objects are accessed via a virtual information store, 87 termed the Management Information Base or MIB. Objects in the 88 MIB are defined using the subset of Abstract Syntax Notation 89 One (ASN.1) defined in the SMI. In particular, each object 90 type is named by an OBJECT IDENTIFIER, an administratively 91 assigned name. The object type together with an object 92 instance serves to uniquely identify a specific instantiation 93 of the object. For human convenience, we often use a textual 94 string, termed the descriptor, to refer to the object type. 96 2. Overview 98 This document is the one in the series of documents that 99 define various MIB object groups for IPv6. These groups are 100 the basic unit of conformance: if the semantics of a group is 101 applicable to an implementation, then it must implement all 102 objects in that group. For example, an implementation must 103 implement the TCP group if and only if it implements the TCP 104 over IPv6 protocol. 106 This document defines the UDP and TCP groups of the IPv6 MIB. 108 3. The UDP Group 110 IPV6-UDP-MIB DEFINITIONS ::= BEGIN 112 IMPORTS 113 MODULE-IDENTITY, OBJECT-TYPE, 114 Counter32, Unsigned32 FROM SNMPv2-SMI 115 ipv6, Ipv6Address FROM IPV6-TC 116 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 117 ipv6IfIndex FROM IPV6-MIB; -- [8] 119 ipv6UdpMIB MODULE-IDENTITY 120 LAST-UPDATED "9703222155Z" 121 ORGANIZATION "IETF IPv6 MIB Working Group" 122 CONTACT-INFO 123 " Dimitry Haskin 124 Postal: Bay Networks, Inc. 125 2 Federal St. 126 Billerica, MA 01821 127 US 129 Tel: +1-508-916-8124 130 E-mail: dhaskin@baynetworks.com 132 Steve Onishi 133 Postal: Bay Networks, Inc. 134 3 Federal Street 135 Billerica, MA 01821 136 US 138 Tel: +1-508-916-3816 139 E-mail: sonishi@baynetworks.com" 140 DESCRIPTION 141 "The MIB module for entities implementing UDP 142 over IPv6." 143 ::= { ipv6 3} 145 -- the UDP group 147 ipv6UdpMIBObjects OBJECT IDENTIFIER ::= { ipv6UdpMIB 1 } 148 ipv6UdpInDatagrams OBJECT-TYPE 149 SYNTAX Counter32 150 MAX-ACCESS read-only 151 STATUS current 152 DESCRIPTION 153 "The total number of UDP datagrams delivered to 154 UDP users." 155 ::= { ipv6UdpMIBObjects 1 } 157 ipv6UdpNoPorts OBJECT-TYPE 158 SYNTAX Counter32 159 MAX-ACCESS read-only 160 STATUS current 161 DESCRIPTION 162 "The total number of received UDP datagrams 163 for which there was no application at 164 the destination port." 165 ::= { ipv6UdpMIBObjects 2 } 167 ipv6UdpInErrors OBJECT-TYPE 168 SYNTAX Counter32 169 MAX-ACCESS read-only 170 STATUS current 171 DESCRIPTION 172 "The number of received UDP datagrams that 173 could not be delivered for reasons other 174 than the lack of an application at 175 the destination port." 176 ::= { ipv6UdpMIBObjects 3 } 178 ipv6UdpOutDatagrams OBJECT-TYPE 179 SYNTAX Counter32 180 MAX-ACCESS read-only 181 STATUS current 182 DESCRIPTION 183 "The total number of UDP datagrams sent 184 from this entity." 185 ::= { ipv6UdpMIBObjects 4 } 187 ipv6UdpTable OBJECT-TYPE 188 SYNTAX SEQUENCE OF Ipv6UdpEntry 189 MAX-ACCESS not-accessible 190 STATUS current 191 DESCRIPTION 192 "The UDP listener table contains information 193 about this entity's UDP end-points on which 194 a local application is currently accepting 195 datagrams." 196 ::= { ipv6UdpMIBObjects 5 } 198 ipv6UdpEntry OBJECT-TYPE 199 SYNTAX Ipv6UdpEntry 200 MAX-ACCESS not-accessible 201 STATUS current 202 DESCRIPTION 203 "Information about a particular current UDP 204 listener." 205 INDEX { ipv6IfIndex, 206 ipv6UdpLocalAddress, 207 ipv6UdpLocalPort } 208 ::= { ipv6UdpTable 1 } 210 Ipv6UdpEntry ::= SEQUENCE { 211 ipv6UdpLocalAddress Ipv6Address, 212 ipv6UdpLocalPort Unsigned32 213 } 215 ipv6UdpLocalAddress OBJECT-TYPE 216 SYNTAX Ipv6Address 217 MAX-ACCESS not-accessible 218 STATUS current 219 DESCRIPTION 220 "The local IPv6 address for this UDP listener. 221 In the case of a UDP listener which is willing 222 to accept datagrams for any IPv6 address 223 associated with the interface, the value ::0 224 is used." 225 ::= { ipv6UdpEntry 1 } 227 ipv6UdpLocalPort OBJECT-TYPE 228 SYNTAX Unsigned32 229 MAX-ACCESS read-only 230 STATUS current 231 DESCRIPTION 232 "The local port number for this UDP listener." 233 ::= { ipv6UdpEntry 2 } 235 -- conformance information 236 ipv6UdpConformance OBJECT IDENTIFIER ::= { ipv6UdpMIB 2 } 238 ipv6UdpCompliances OBJECT IDENTIFIER ::= { ipv6UdpConformance 1 } 239 ipv6UdpGroups OBJECT IDENTIFIER ::= { ipv6UdpConformance 2 } 241 -- compliance statements 243 ipv6UdpCompliance MODULE-COMPLIANCE 244 STATUS current 245 DESCRIPTION 246 "The compliance statement for SNMPv2 entities which 247 implement UDP over IPv6." 248 MODULE -- this module 249 GROUP ipv6UdpGroup 250 DESCRIPTION 251 "This group is mandatory for all entities 252 which implement UDP over IPv6." 253 ::= { ipv6UdpCompliances 1 } 255 ipv6UdpGroup OBJECT-GROUP 256 OBJECTS { 257 ipv6UdpInDatagrams, 258 ipv6UdpNoPorts, 259 ipv6UdpInErrors, 260 ipv6UdpOutDatagrams, 261 ipv6UdpLocalPort 262 } 263 STATUS current 264 DESCRIPTION 265 "The UDP group of objects providing information 266 specific to UDP over IPv6." 267 ::= { ipv6UdpGroups 1 } 269 END 271 4. The TCP Group 273 IPV6-TCP-MIB DEFINITIONS ::= BEGIN 275 IMPORTS 276 MODULE-IDENTITY, OBJECT-TYPE, 277 Unsigned32, Gauge32, Counter32, 278 Integer32 FROM SNMPv2-SMI 279 ipv6, Ipv6Address FROM IPV6-TC 280 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 281 ipv6IfIndex FROM IPV6-MIB; 283 ipv6TcpMIB MODULE-IDENTITY 284 LAST-UPDATED "9610042155Z" 285 ORGANIZATION "IETF IPv6 MIB Working Group" 286 CONTACT-INFO 287 " Dimitry Haskin 288 Postal: Bay Networks, Inc. 289 2 Federal St. 290 Billerica, MA 01821 291 US 293 Tel: +1-508-916-8124 294 E-mail: dhaskin@baynetworks.com 296 Steve Onishi 297 Postal: Bay Networks, Inc. 298 3 Federal Street 299 Billerica, MA 01821 300 US 302 Tel: +1-508-916-3816 303 E-mail: sonishi@baynetworks.com" 304 DESCRIPTION 305 "The MIB module for entities implementing TCP 306 over IPv6." 307 ::= { ipv6 4} 309 -- the TCPv6 group 311 ipv6TcpMIBObjects OBJECT IDENTIFIER ::= { ipv6TcpMIB 1 } 312 -- Note that instances of object types that represent 313 -- information about a particular TCP connection are 314 -- transient; they persist only as long as the connection 315 -- in question. 317 ipv6TcpRtoAlgorithm OBJECT-TYPE 318 SYNTAX INTEGER { 319 other(1), -- none of the following 321 constant(2), -- a constant rto 322 rsre(3), -- MIL-STD-1778, Appendix B 323 vanj(4) -- Van Jacobson's algorithm [9] 324 } 325 MAX-ACCESS read-only 326 STATUS current 327 DESCRIPTION 328 "The algorithm used to determine the timeout value 329 used for retransmitting unacknowledged octets." 330 ::= { ipv6TcpMIBObjects 1 } 332 ipv6TcpRtoMin OBJECT-TYPE 333 SYNTAX Unsigned32 334 UNITS "milliseconds" 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "The minimum value permitted by a TCP 339 implementation for the retransmission timeout, 340 measured in milliseconds. More refined semantics 341 for objects of this type depend upon the algorithm 342 used to determine the retransmission timeout. In 343 particular, when the timeout algorithm is rsre(3), 344 an object of this type has the semantics of the 345 LBOUND quantity described in RFC 793." 346 ::= { ipv6TcpMIBObjects 2 } 348 ipv6TcpRtoMax OBJECT-TYPE 349 SYNTAX Unsigned32 350 UNITS "milliseconds" 351 MAX-ACCESS read-only 352 STATUS current 353 DESCRIPTION 354 "The maximum value permitted by a TCP 355 implementation for the retransmission timeout, 356 measured in milliseconds. More refined semantics 357 for objects of this type depend upon the algorithm 358 used to determine the retransmission timeout. In 359 particular, when the timeout algorithm is rsre(3), 360 an object of this type has the semantics of the 361 UBOUND quantity described in RFC 793." 362 ::= { ipv6TcpMIBObjects 3 } 364 ipv6TcpMaxConn OBJECT-TYPE 365 SYNTAX Integer32 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "The limit on the total number of TCP connections 370 the entity can support. In entities where the 371 maximum number of connections is dynamic, this 372 object should contain the value -1." 373 ::= { ipv6TcpMIBObjects 4 } 375 ipv6TcpActiveOpens OBJECT-TYPE 376 SYNTAX Counter32 377 MAX-ACCESS read-only 378 STATUS current 379 DESCRIPTION 380 "The number of times TCP connections have made a 381 direct transition to the SYN-SENT state from the 382 CLOSED state." 383 ::= { ipv6TcpMIBObjects 5 } 385 ipv6TcpPassiveOpens OBJECT-TYPE 386 SYNTAX Counter32 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The number of times TCP connections have made a 391 direct transition to the SYN-RCVD state from the 392 LISTEN state." 393 ::= { ipv6TcpMIBObjects 6 } 395 ipv6TcpAttemptFails OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The number of times TCP connections have made a 401 direct transition to the CLOSED state from either 402 the SYN-SENT state or the SYN-RCVD state, plus the 403 number of times TCP connections have made a direct 404 transition to the LISTEN state from the SYN-RCVD 405 state." 406 ::= { ipv6TcpMIBObjects 7 } 408 ipv6TcpEstabResets OBJECT-TYPE 409 SYNTAX Counter32 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The number of times TCP connections have made a 414 direct transition to the CLOSED state from either 415 the ESTABLISHED state or the CLOSE-WAIT state." 416 ::= { ipv6TcpMIBObjects 8 } 418 ipv6TcpCurrEstab OBJECT-TYPE 419 SYNTAX Gauge32 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "The number of TCP connections for which the 424 current state is either ESTABLISHED or CLOSE- 425 WAIT." 426 ::= { ipv6TcpMIBObjects 9 } 428 ipv6TcpInSegs OBJECT-TYPE 429 SYNTAX Counter32 430 MAX-ACCESS read-only 431 STATUS current 432 DESCRIPTION 433 "The total number of segments received, including 434 those received in error. This count includes 435 segments received on currently established 436 connections." 437 ::= { ipv6TcpMIBObjects 10 } 439 ipv6TcpOutSegs OBJECT-TYPE 440 SYNTAX Counter32 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "The total number of segments sent, including 445 those on current connections but excluding those 446 containing only retransmitted octets." 448 ::= { ipv6TcpMIBObjects 11 } 450 ipv6TcpRetransSegs OBJECT-TYPE 451 SYNTAX Counter32 452 MAX-ACCESS read-only 453 STATUS current 454 DESCRIPTION 455 "The total number of segments retransmitted - that 456 is, the number of TCP segments transmitted 457 containing one or more previously transmitted 458 octets." 459 ::= { ipv6TcpMIBObjects 12 } 461 ipv6TcpInErrs OBJECT-TYPE 462 SYNTAX Counter32 463 MAX-ACCESS read-only 464 STATUS current 465 DESCRIPTION 466 "The total number of segments received in error 467 (e.g., bad TCP checksums)." 468 ::= { ipv6TcpMIBObjects 13 } 470 ipv6TcpOutRsts OBJECT-TYPE 471 SYNTAX Counter32 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "The number of TCP segments sent containing the 476 RST flag." 477 ::= { ipv6TcpMIBObjects 14 } 479 -- the TCPv6 Connection table 481 -- The TCPv6 connection table contains information 482 -- about this entity's existing TCPv6 connections. 484 ipv6TcpConnTable OBJECT-TYPE 485 SYNTAX SEQUENCE OF Ipv6TcpConnEntry 486 MAX-ACCESS not-accessible 487 STATUS current 488 DESCRIPTION 489 "A table containing TCP connection-specific 490 information." 491 ::= { ipv6TcpMIBObjects 15 } 493 ipv6TcpConnEntry OBJECT-TYPE 494 SYNTAX Ipv6TcpConnEntry 495 MAX-ACCESS not-accessible 496 STATUS current 497 DESCRIPTION 498 "Information about a particular current TCP 499 connection. An object of this type is transient, 500 in that it ceases to exist when (or soon after) 501 the connection makes the transition to the CLOSED 502 state." 503 INDEX { ipv6IfIndex, 504 ipv6TcpConnLocalAddress, 505 ipv6TcpConnLocalPort, 506 ipv6TcpConnRemAddress, 507 ipv6TcpConnRemPort } 508 ::= { ipv6TcpConnTable 1 } 510 Ipv6TcpConnEntry ::= 511 SEQUENCE { 512 ipv6TcpConnLocalAddress Ipv6Address, 513 ipv6TcpConnLocalPort INTEGER (0..65535), 514 ipv6TcpConnRemAddress Ipv6Address, 515 ipv6TcpConnRemPort INTEGER (0..65535), 516 ipv6TcpConnState INTEGER 517 } 519 ipv6TcpConnLocalAddress OBJECT-TYPE 520 SYNTAX Ipv6Address 521 MAX-ACCESS not-accessible 522 STATUS current 523 DESCRIPTION 524 "The local IPv6 address for this TCP connection. In 525 the case of a connection in the listen state which 526 is willing to accept connections for any IPv6 527 address associated with the interface, the value 528 ::0 is used." 529 ::= { ipv6TcpConnEntry 1 } 531 ipv6TcpConnLocalPort OBJECT-TYPE 532 SYNTAX INTEGER (0..65535) 533 MAX-ACCESS not-accessible 534 STATUS current 535 DESCRIPTION 536 "The local port number for this TCP connection." 537 ::= { ipv6TcpConnEntry 2 } 539 ipv6TcpConnRemAddress OBJECT-TYPE 540 SYNTAX Ipv6Address 541 MAX-ACCESS not-accessible 542 STATUS current 543 DESCRIPTION 544 "The remote IPv6 address for this TCP connection." 545 ::= { ipv6TcpConnEntry 3 } 547 ipv6TcpConnRemPort OBJECT-TYPE 548 SYNTAX INTEGER (0..65535) 549 MAX-ACCESS not-accessible 550 STATUS current 551 DESCRIPTION 552 "The remote port number for this TCP connection." 553 ::= { ipv6TcpConnEntry 4 } 555 ipv6TcpConnState OBJECT-TYPE 556 SYNTAX INTEGER { 557 closed(1), 558 listen(2), 559 synSent(3), 560 synReceived(4), 561 established(5), 562 finWait1(6), 563 finWait2(7), 564 closeWait(8), 565 lastAck(9), 566 closing(10), 567 timeWait(11), 568 deleteTCB(12) 569 } 570 MAX-ACCESS read-write 571 STATUS current 572 DESCRIPTION 573 "The state of this TCP connection. 575 The only value which may be set by a management 576 station is deleteTCB(12). Accordingly, it is 577 appropriate for an agent to return a `badValue' 578 response if a management station attempts to set 579 this object to any other value. 581 If a management station sets this object to the 582 value deleteTCB(12), then this has the effect of 583 deleting the TCB (as defined in RFC 793) of the 584 corresponding connection on the managed node, 585 resulting in immediate termination of the 586 connection. 588 As an implementation-specific option, a RST 589 segment may be sent from the managed node to the 590 other TCP endpoint (note however that RST segments 591 are not sent reliably)." 592 ::= { ipv6TcpConnEntry 5 } 594 -- conformance information 596 ipv6TcpConformance OBJECT IDENTIFIER ::= { ipv6TcpMIB 2 } 598 ipv6TcpCompliances OBJECT IDENTIFIER ::= { ipv6TcpConformance 1 } 599 ipv6TcpGroups OBJECT IDENTIFIER ::= { ipv6TcpConformance 2 } 601 -- compliance statements 603 ipv6TcpCompliance MODULE-COMPLIANCE 604 STATUS current 605 DESCRIPTION 606 "The compliance statement for SNMPv2 entities which 607 implement TCP over IPv6." 608 MODULE -- this module 609 GROUP ipv6TcpGroup 610 DESCRIPTION 611 "This group is mandatory for all entities 612 which implement TCP over IPv6." 613 ::= { ipv6TcpCompliances 1 } 615 ipv6TcpGroup OBJECT-GROUP 616 OBJECTS { 617 ipv6TcpRtoAlgorithm, 618 ipv6TcpRtoMin, 619 ipv6TcpRtoMax, 620 ipv6TcpMaxConn, 621 ipv6TcpActiveOpens, 622 ipv6TcpPassiveOpens, 623 ipv6TcpAttemptFails, 624 ipv6TcpEstabResets, 625 ipv6TcpCurrEstab, 626 ipv6TcpInSegs, 627 ipv6TcpOutSegs, 628 ipv6TcpRetransSegs, 629 ipv6TcpInErrs, 630 ipv6TcpOutRsts, 631 ipv6TcpConnState 632 } 633 STATUS current 634 DESCRIPTION 635 "The TCP group of objects providing information 636 specific to TCP over IPv6." 637 ::= { ipv6TcpGroups 1 } 639 END 641 5. Acknowledgments 643 This document borrows from MIB works produced by IETF for 644 IPv4-based internets. 646 6. References 648 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 649 and S. Waldbusser, "Structure of Management Information 650 for Version 2 of the Simple Network Management Protocol 651 (SNMPv2)", RFC 1902, January 1996. 653 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 654 and S. Waldbusser, "Textual Conventions for Version 2 of 655 the Simple Network Management Protocol (SNMPv2)", RFC 656 1903, January 1996. 658 [3] McCloghrie, K., and M. Rose, Editors, "Management 659 Information Base for Network Management of TCP/IP-based 660 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 661 Performance Systems International, March 1991. 663 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A 664 Simple Network Management Protocol (SNMP)", STD 15, RFC 665 1157, SNMP Research, Performance Systems International, 666 MIT Lab for Computer Science, May 1990. 668 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. 669 and S. Waldbusser, "Protocol Operations for Version 2 of 670 the Simple Network Management Protocol (SNMPv2)", RFC 671 1905, January 1996. 673 [6] McCloghrie, K. and F. Kastenholz, "Evolution of the 674 Interfaces Group of MIB-II" , RFC 1573, January 1994. 676 [7] Deering, S., and R. Hinden, "Internet Protocol, Version 6 677 (IPv6) Specification", RFC 1883, December 1995. 679 [8] Haskin, D., and S. Onishi, "Management Information Base 680 for IP Version 6: Textual Conventions and General Group", 681 Work in progress. 683 [9] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 684 1988, Stanford, California. 686 7. Security Considerations 688 Certain management information defined in this MIB may be 689 considered sensitive in some network environments. 691 Therefore, authentication of received SNMP requests and 692 controlled access to management information should be employed 693 in such environments. 695 8. Authors' Address 697 Dimitry Haskin 698 Bay Networks, Inc. 699 2 Federal Street 700 Billerica, MA 01821 701 email: dhaskin@baynetworks.com 703 Steve Onishi 704 Bay Networks, Inc. 705 3 Federal Street 706 Billerica, MA 01821 707 email: sonishi@baynetworks.com