idnits 2.17.1 draft-ietf-sigtran-sctp-mib-08.txt: -(1689): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2022): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2057): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2179): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2279): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding 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: ---------------------------------------------------------------------------- ** 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? == There are 9 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 48 longer pages, the longest (page 23) being 67 lines 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.) ** There are 115 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([RFC2012-update]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2057 has weird spacing: '...essType in co...' == Line 2284 has weird spacing: '... object sctpA...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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) == Missing Reference: 'RFC2012-update' is mentioned on line 57, but not defined ** Obsolete undefined reference: RFC 2012 (Obsoleted by RFC 4022) == Missing Reference: 'RFC2119' is mentioned on line 115, but not defined == Missing Reference: 'RFC1902' is mentioned on line 142, but not defined ** Obsolete undefined reference: RFC 1902 (Obsoleted by RFC 2578) == Missing Reference: 'RFC1903' is mentioned on line 142, but not defined ** Obsolete undefined reference: RFC 1903 (Obsoleted by RFC 2579) == Missing Reference: 'RFC1904' is mentioned on line 143, but not defined ** Obsolete undefined reference: RFC 1904 (Obsoleted by RFC 2580) == Missing Reference: 'RFC2272' is mentioned on line 151, but not defined ** Obsolete undefined reference: RFC 2272 (Obsoleted by RFC 2572) == Missing Reference: 'RFC2273' is mentioned on line 158, but not defined ** Obsolete undefined reference: RFC 2273 (Obsoleted by RFC 2573) == Missing Reference: 'RFC2863' is mentioned on line 232, but not defined == Missing Reference: 'RFC 3291' is mentioned on line 385, but not defined ** Obsolete undefined reference: RFC 3291 (Obsoleted by RFC 4001) == Unused Reference: 'RFC2572' is defined on line 1720, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1724, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1735, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1739, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1743, but no explicit reference was found in the text == Unused Reference: 'SecSNMP' is defined on line 1749, but no explicit reference was found in the text == Unused Reference: 'Cong' is defined on line 1752, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1776, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 1780, but no explicit reference was found in the text == Unused Reference: 'IPv6ARCH' is defined on line 1783, but no explicit reference was found in the text == Unused Reference: 'UDPMIB' is defined on line 1797, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2960 (Obsoleted by RFC 4960) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) -- Obsolete informational reference (is this intentional?): RFC 2012 (Obsoleted by RFC 4022) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 3291 (Obsoleted by RFC 4001) == Outdated reference: A later version (-05) exists of draft-ietf-ops-taddress-mib-03 == Outdated reference: A later version (-06) exists of draft-ietf-ipv6-rfc2012-update-00 == Outdated reference: A later version (-04) exists of draft-ietf-ipv6-rfc2013-update-00 Summary: 21 errors (**), 0 flaws (~~), 31 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Pastor 3 INTERNET-DRAFT M. Belinchon 4 Expires: May 2003 Ericsson 6 November, 2002 8 Stream Control Transmission Protocol 9 Management Information Base 10 12 Status of this memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that other 19 groups may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or cite them other than as "work in progress". 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/lid-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 This document is an individual submission to the IETF. Comments 33 should be directed to the authors. 35 Abstract 37 The Stream Control Transmission Protocol (SCTP) is a reliable 38 transport protocol operating on top of a connectionless packet 39 network such as IP, designed to transport PSTN signaling messages 40 over the connectionless packet network, but is capable of broader 41 applications. 43 This memo defines the Management Information Base (MIB) module which 44 describes the minimum amount of objects needed to manage the 45 implementation of the SCTP. 47 Open Issues 49 - Remove this section. 51 - Remove Revision History 53 - Decide under which object identifier branch of the SNMP tree, 54 SCTP should be placed. This value will be obtained when 55 submitted to the IETF queue. 57 - Update references to [RFC2012-update] 59 - Syntax of sctpAssocRemHostName 61 TABLE OF CONTENTS 63 Open Issues.........................................................2 64 1. Introduction.....................................................3 65 1.1 Abbreviations...................................................3 66 2. The SNMP Framework...............................................3 67 3. MIB Structure....................................................4 68 3.1 SCTP Objets.....................................................5 69 3.1.1 SCTP Statistics...............................................5 70 3.1.2 SCTP Parameters...............................................6 71 3.1.3 MIB Tables....................................................6 72 3.1.3.1 Association Table..........................................7 73 3.1.3.2 Reverse Lookup Table.......................................9 74 3.2 Conformance....................................................10 75 4. Definitions.....................................................11 76 5. Compiling Notes.................................................36 77 6. References......................................................37 78 6.1 Normative References...........................................37 79 6.1 Informative References.........................................38 80 7. Security Consideration..........................................39 81 8. Acknowledgments.................................................40 82 9. Authors' Addresses..............................................40 83 10. Revision History...............................................41 84 10.1 Changes from .......................41 85 10.2 Changes from .............41 86 10.3 Changes from .............43 87 10.3 Changes from .............44 88 10.4 Changes from .............44 89 10.5 Changes from .............45 90 10.6 Changes from .............46 91 10.7 Changes from .............47 92 10.8 Changes from .............48 94 1. Introduction 96 This memo defines the Management Information Base (MIB) module which 97 describes managed objects for implementations of the SCTP. 99 The document starts with a brief description of the SNMP framework 100 and continues with the MIB explanation and security consideration 101 among others. 103 The managed objects in this MIB module have been based on [RFC2012] 104 update: "Management Information Base for the Transmission Control 105 Protocol (TCP)" [TCPMIB], work in progress, and the RFC 3291 "Textual 106 Conventions for Internet Network Addresses" [TADDRESS], work in 107 progress. 109 Terms related to the SCTP architecture are explained in [RFC2960]. 110 Other specific abbreviations are listed below. 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 114 document are to be interpreted as described in [RFC2119]. 116 1.1 Abbreviations 118 DNS - Domain Name System 119 IANA - Internet Assigned Numbers Authority 120 IETF - Internet Engineering Task Force 121 IP - Internet Protocol 122 MIB - Management Information Base 123 RFC - Request For Comment 124 RTO - Retransmission Time Out 125 SCTP - Stream Control Transmission Protocol 126 SMI - Structure of Management Information 127 SNMP - Simple Network Management Protocol 128 TCB - Transmission Control Block 129 TCP - Transmission Control Protocol 131 2. The SNMP Framework 133 The SNMP Management Framework presently consists of five major 134 components: 136 - An overall architecture, described in [RFC2571]. 138 - Mechanisms for describing and naming objects and events for the 139 purpose of management. The first version of this Structure of 140 Management Information (SMI) is called SMIv1 and described in 141 [RFC1155] , [RFC1212] and [RFC1215]. The second version, 142 called SMIv2, is described in [RFC1902], [RFC1903] and 143 [RFC1904]. 145 - Message protocols for transferring management information. The 146 first version of the SNMP message protocol is called SNMPv1 and 147 described in [RFC1157]. A second version of the SNMP message 148 protocol, which is not an Internet standards track protocol, is 149 called SNMPv2c and described in [RFC1901] and [RFC1906]. The 150 third version of the message protocol is called SNMPv3 and 151 described in [RFC1906], [RFC2272] and [RFC2574]. 153 - Protocol operations for accessing management information. The 154 first set of protocol operations and associated PDU formats is 155 described in [RFC1157]. A second set of protocol operations 156 and associated PDU formats is described in [RFC1905]. 158 - A set of fundamental applications described in [RFC2273] and 159 the view-based access control mechanism described in [RFC2575]. 161 Managed objects are accessed via a virtual information store, termed 162 the Management Information Base or MIB. Objects in the MIB are 163 defined using the mechanisms defined in the SMI. This memo specifies 164 a MIB module that is compliant to the SMIv2. A MIB conforming to the 165 SMIv1 can be produced through the appropriate translations. The 166 resulting translated MIB must be semantically equivalent, except 167 where objects or events are omitted because no translation is 168 possible (use of Counter64). Some machine-readable information in 169 SMIv2 will be converted into textual descriptions in SMIv1 during the 170 translation process. However, this loss of machine-readable 171 information is not considered to change the semantics of the MIB. 173 3. MIB Structure 175 This chapter will explain the main objects this MIB defines. A 176 detailed view of the MIB structure with the OID values is below. 178 MIB-2 {1 3 6 1 2 2} 179 +--(xxx)sctpMIB 180 | 181 +--(1) sctpObjects 182 | | 183 | +--(1) sctpStats 184 | | | 185 | | +-- 186 | | 187 | +--(2)sctpParameters 188 | | | 189 | | +-- 190 | | 191 | +--(3) sctpAssocTable 192 | | 193 | +--(4) sctpAssocLocalAddressTable 194 | | 195 | +--(5) sctpAssocRemAddressTable 196 | | 197 | +--(6) sctpLookupLocalPortTable 198 | | 199 | +--(7) sctpLookupRemPortTable 200 | | 201 | +--(8) sctpLookupRemHostNameTable 202 | | 203 | +--(9) sctpLookupRemPrimIPAddrTable 204 | | 205 | +--(10) sctpLookupRemIPAddrTable 206 | 207 | 208 +--(2)sctpConformance 209 | 210 +--(1) sctpCompliances 211 | | 212 | +--(1) sctpCompliance 213 | 214 +--(2) sctpGroups 215 | 216 +--(1) sctpLayerParamsGroup 217 | 218 +--(2) sctpStatsGroup 219 | 220 +--(3) sctpPerAssocParamsGroup 222 The main groups are further explained along the MIB definition. 224 3.1 SCTP Objets 226 This branch contains the SCTP statistics and general parameters (both 227 of them scalars) and the SCTP MIB tables. 229 3.1.1 SCTP Statistics 230 SCTP MIB includes both Counter32 and Counter64 to deal with 231 statistics. Counter64 has been applied to those counters, which are 232 likely to wrap around in less than one hour, according to [RFC2863]. 234 In addition Gauge32 is also used. 236 3.1.1.1 State-Related Statistics 238 These measures are based in the TCP model, but adapted to the SCTP 239 states. They store the number of succeeded association attempts, how 240 many associations have been initiated by the local or the remote SCTP 241 layer, or just the number of associations terminated in a graceful 242 (by means of SHUTDOWN procedure) or ungraceful way (by means of CLOSE 243 procedure). 245 3.1.1.2 Statistics for traffic Measurements 247 It has been specified statistics related to the whole SCTP layer. 248 There are, e.g., statistics related to either SCTP packets or SCTP 249 chunks. 251 Statistics related to a specific association, or local/remote IP 252 addresses are defined inside its concerned table. 254 3.1.2 SCTP Parameters 256 This section of the MIB contains the general variables of the 257 SCTP protocol. Maximum, minimum, initial values, and values by 258 default are listed here. 260 SCTP RTO mechanism definition is based on the TCP MIB [RFC2012- 261 update]. In SCTP protocol, only options 'other' and 'vanj' are valid 262 since SCTP protocol defines Van Jacobson's algorithm as the one to 263 be used to calculate RTO. 'Other' is left for future use. 265 3.1.3 MIB Tables 267 There are several tables included in the SCTP MIB. The first group 268 deals with the Association variables and is composed of a main and 269 two extended tables. The second group is a bunch of tables used for 270 the reverse lookup. 272 It is NOT possible to create rows in any table (sctpAssocTable, 273 sctpAssocLocalAddressTable, sctpRemAddressTable and Reverse Lookup 274 tables). 276 It is NOT possible to delete rows in any table except in 277 sctpAssocTable under the particular conditions explained below. 279 3.1.3.1 Association Table 281 This is the main MIB table, where all the association related 282 information is stored per association basis. It is structured 283 according to expanded tables. The main table is called sctpAssocTable 284 and is indexed by sctpAssocId (the association identification) that 285 is a value that uniquely identifies an association. The MIB does not 286 restrict which value must be written here,, however it must be unique 287 within the table. 289 The sctpAssoc index is also shared by two more tables: 290 - sctpAssocLocalAddressTable: to store the local IP address(-es). 291 - sctpAssocRemAddressTable: to store the remote addresses and the 292 per-remote-address(-es)related information. 294 Entries in the sctpAssocTable are created when trying to establish 295 the association, i.e., when sending the COOKIE-ECHO message 296 (originating side) or the COOKIE-ACK message (server side). At this 297 point, i.e., at established state, all entry fields are filled in 298 with valid values. 300 Note: The following representation is a conceptual mode of describing 301 the relationship between the tables in this MIB. Note that the real 302 relationship of the tables is by sharing an index, so tables are not 303 truly within tables. Every entry is explained when defining the 304 corresponding objects in the MIB. 306 MIB-2 {1 3 6 1 2 2} 307 +--(xxx)sctpMIB 308 | 309 +--(1) sctpObjects 310 | | 311 . . 312 . . 313 | 314 +--(3) sctpAssocTable 315 | | 316 | +--(1) sctpAssocId (index) 317 | | 318 | +--(1) sctpAssocRemHostName 319 | | 320 | +--(1) sctpAssocLocalPort 321 | | 322 | +--(1) sctpAssocRemPort 323 | | 324 | +--(1) sctpAssocRemPrimaryAddressType 325 | | 326 | +--(1) sctpAssocRemPrimaryAddress 327 | | 328 | +--(1) sctpAssocHeartBeatInterval 329 | | 330 | +--(1) sctpAssocState 331 | | 332 | +--(1) sctpAssocInStreams 333 | | 334 | +--(1) sctpAssocOutStreams 335 | | 336 | +--(1) sctpAssocMaxRetr 337 | | 338 | +--(1) sctpAssocPrimaryProcess 339 | | 340 | +--(1) sctpAssocT1expireds 341 | | 342 | +--(1) sctpAssocT2expireds 343 | | 344 | +--(1) sctpAssocRtxChunks 345 | | 346 | +--(1) sctpAssocStartTime 347 | | 348 | +--(1) sctpAssocDiscontinuityTime 349 | 350 | 351 +--(4) sctpAssocLocalAddressTable 352 | | 353 | |-- sctpAssocId (shared index) 354 | | 355 | +--(1) sctpAssocLocalAddressType(index) 356 | | 357 | +--(1) sctpAssocLocalAddress (index) 358 | | 359 | +--(1) sctpAssocLocalAddressStartTime 360 | 361 | 362 +--(5) sctpAssocRemAddressTable 363 | | 364 | |-- sctpAssocId (shared index) 365 | | 366 | +--(1) sctpAssocRemAddressType (index) 367 . | 368 . +--(1) sctpAssocRemAddress (index) 369 . | 370 +--(1) sctpAssocRemAddressActive 371 | 372 +--(1) sctpAssocRemAddressHBActive 373 | 374 +--(1) sctpAssocRemAddressRTO 375 | 376 +--(1) sctpAssocRemAddressMaxPathRtx 377 | 378 +--(1) sctpAssocRemAddressRtx 379 | 380 +--(1) sctpAssocRemAddressStartTime 382 Both sctpAssocLocalAddressTable and sctpAssocRemAddressTable are 383 indexed by addresses. 'Address' and 'AddressType' use the syntax 384 InetAddress and InetAddressType defined in the Textual Conventions 385 for Internet Network Address [RFC 3291]. In the general case this 386 syntax is valid for Unknown IP addresses, IPv4, IPv6, non-global 387 IPv4, non-global IPv6 address and DNS, but only the IPv4 and IPv6 388 address options will be allowed in this MIB. 390 The sctpAssocLocalAddressTable table will have as many entries as 391 local IP addresses have been defined. The sctpAssocRemAddressTable 392 table will contain as many entries as remote IP addresses are known 393 to reach the peer. For multihoming concept see reference [RFC2960]. 395 DNS value is not used to identify an IP address since it is only 396 valid during initialization (once this stage is finished, both sides 397 only use IP addresses). 399 To keep the name of the remote peer (when provided by the peer at 400 initialization time), an entry has been created in the sctpAssocTable 401 (sctpAssocRemHostName). When no DNS name is provided by the remote 402 endpoint, this value will be NULL (zero-length string). Otherwise, 403 the received DNS name will be stored here. 405 If it is required to abort an existing association, the value 406 deleteTCB has to be written in the variable sctpAssocState. That is 407 the only way to delete rows in any of the mentioned tables. 409 3.1.3.2 Reverse Lookup Table 411 There are five reverse lookup tables to help management applications 412 to efficiently access conceptual rows in other tables. This is the 413 way for not performing expensive tree walks through large number of 414 associations. 416 All of these tables are optional. In case of implementing them, any 417 entry must be created after the main table (sctpAssocTable) concerned 418 entry has been created. This ensures that the field indexing the 419 lookup table exists. 421 The defined reversed lookup tables allow performing a lookup using 422 the following variables: 424 - Local Port: It allows a management application to find out all 425 the associations that use a specific local port 426 - Remote Port: It allows a management application to find out all 427 the associations that use a specific remote port 428 - Remote Host Name: It allows a management application to find 429 out all the associations to a specific host name. 430 - Remote Primary IP Address: It allows a management application 431 to find out all the associations that use a specific remote IP 432 address as primary. 433 - Remote IP address: a management application to find out all the 434 associations that use a specific remote IP address. 436 As an example the picture below shows the table to look up by local 437 port. 439 MIB-2 {1 3 6 1 2 2} 440 +--(xxx)sctpMIB 441 | 442 +--(1) sctpObjects 443 | | 444 . . 445 . . 446 | | 447 | +--(6) sctpLookupLocalPortTable 448 | | | 449 . . +--(1) sctpAssocLocalPort (index) 450 . . | 451 +--(2) sctpAssocId (index) 452 | 453 +--(3) sctpAssocState 455 All the lookup tables contains the sctpAssocState object. This allows 456 getting the three objects in an easier way. 458 It is not possible to either create or delete rows in these tables. 460 3.2 Conformance 462 The conformance section recommends as optional the general SCTP 463 statistics and those per association or remote IP address statistics. 465 Also, IP address will take the format of IPv4 and IPv6 addresses (not 466 scoped). DNS name will not be accepted either (since names will be 467 stored � if present � in the sctpRemoteHostName variable). 469 4. Definitions 471 SCTP-MIB DEFINITIONS ::= BEGIN 473 IMPORTS 474 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32, 475 Counter32, Counter64, mib-2 476 FROM SNMPv2-SMI -- RFC2578 477 TimeStamp, TruthValue 478 FROM SNMPv2-TC -- RFC2579 479 MODULE-COMPLIANCE, OBJECT-GROUP 480 FROM SNMPv2-CONF -- RFC2580 481 InetAddressType, InetAddress, InetPortNumber 482 FROM INET-ADDRESS-MIB -- RFC 3291 483 ; 485 sctpMIB MODULE-IDENTITY 486 LAST-UPDATED "200208290000Z" -- 29th August 2002 487 ORGANIZATION "IETF SIGTRAN Working Group" 488 CONTACT-INFO 489 " Maria-Carmen Belinchon-Vergara 490 Jose-Javier Pastor-Balbas 492 Postal: Ericsson Espana S. A. 493 C/ Retama 1 494 28045 Madrid 495 Spain 497 Phones: +34 91 339 3535 498 +34 91 339 3819 500 Emails: Maria.C.Belinchon@ericsson.com 501 J.Javier.Pastor@ericsson.com" 502 DESCRIPTION 503 "The MIB module for managing an SCTP implementation." 504 REVISION "200208290000Z" -- 29th August 2002 505 DESCRIPTION " Initial version, published as RFC XXXX" 506 -- RFC Editor to assign XXXX 507 ::= { mib-2 xxxx 300 } -- IANA to assign xxxx 509 -- the SCTP base variables group 511 sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 } 512 sctpStats OBJECT IDENTIFIER ::= { sctpObjects 1 } 513 sctpParams OBJECT IDENTIFIER ::= { sctpObjects 2 } 515 -- STATISTICS 516 -- ********** 518 -- STATE-RELATED STATISTICS 520 sctpCurrEstab OBJECT-TYPE 521 SYNTAX Gauge32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The number of SCTP associations for which the current state 526 is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." 528 ::= { sctpStats 1 } 530 sctpActiveEstabs OBJECT-TYPE 531 SYNTAX Counter32 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "The number of times that SCTP associations have made a direct 536 transition to the ESTABLISHED state from the COOKIE-ECHOED 537 state: COOKIE-ECHOED -> ESTABLISHED. The upper layer has 538 initiated the association attempt." 540 ::= { sctpStats 2 } 542 sctpPassiveEstabs OBJECT-TYPE 543 SYNTAX Counter32 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "The number of times that SCTP associations have made a direct 548 transition to the ESTABLISHED state from the CLOSED state: 549 CLOSED -> ESTABLISHED. The remote endpoint has initiated the 550 association attempt." 552 ::= { sctpStats 3 } 554 sctpAborteds OBJECT-TYPE 555 SYNTAX Counter32 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION 559 "The number of times that SCTP associations have made a direct 560 transition to the CLOSED state from any state using the 561 primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful 562 termination of the association." 564 ::= { sctpStats 4 } 566 sctpShutdowns OBJECT-TYPE 567 SYNTAX Counter32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The number of times that SCTP associations have made a direct 572 transition to the CLOSED state from either the SHUTDOWN-SENT 573 state or the SHUTDOWN-ACK-SENT state. Graceful termination of 574 the association." 576 ::= { sctpStats 5 } 578 -- OTHER LAYER STATISTICS 580 sctpOutOfBlues OBJECT-TYPE 581 SYNTAX Counter32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "Number of out of the blue packets (SCTP packet correctly 586 formed -right checksum- but the receiver is not able to 587 identify the association to which this packet belongs) 588 received by the host." 590 ::= { sctpStats 6 } 592 sctpChecksumErrors OBJECT-TYPE 593 SYNTAX Counter32 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "Number of SCTP packets received from the peers with an 598 invalid checksum." 600 ::= { sctpStats 7 } 602 sctpOutCtrlChunks OBJECT-TYPE 603 SYNTAX Counter64 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "Number of SCTP control chunks sent to the peers (no 608 retransmissions included)." 610 ::= { sctpStats 8 } 612 sctpOutOrderChunks OBJECT-TYPE 613 SYNTAX Counter64 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "Number of SCTP ordered data chunks sent to the peers (no 618 retransmissions included)." 620 ::= { sctpStats 9 } 622 sctpOutUnorderChunks OBJECT-TYPE 623 SYNTAX Counter64 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "Number of SCTP unordered chunks (data chunks in which the U 628 bit is set to 1) sent to the peers (no retransmissions 629 included)." 631 ::= { sctpStats 10 } 633 sctpInCtrlChunks OBJECT-TYPE 634 SYNTAX Counter64 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "Number of SCTP control chunks received from the peers (no 639 duplicated included)." 641 ::= { sctpStats 11 } 643 sctpInOrderChunks OBJECT-TYPE 644 SYNTAX Counter64 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "Number of SCTP ordered data chunks received from the peers 649 (no duplicated included)." 651 ::= { sctpStats 12 } 653 sctpInUnorderChunks OBJECT-TYPE 654 SYNTAX Counter64 655 MAX-ACCESS read-only 656 STATUS current 657 DESCRIPTION 658 "Number of SCTP unordered chunks (data chunks in which the U 659 bit is set to 1) received from the peers (no duplicated 660 included)." 662 ::= { sctpStats 13 } 664 sctpFragUsrMsgs OBJECT-TYPE 665 SYNTAX Counter64 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "Number of user messages that have to be fragmented because of 670 the MTU." 672 ::= { sctpStats 14 } 674 sctpReasmUsrMsgs OBJECT-TYPE 675 SYNTAX Counter64 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "Number of user messages reassembled." 681 ::= { sctpStats 15 } 683 sctpOutSCTPPacks OBJECT-TYPE 684 SYNTAX Counter64 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "Number of SCTP packets sent to the peers." 690 ::= { sctpStats 16 } 692 sctpInSCTPPacks OBJECT-TYPE 693 SYNTAX Counter64 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "Number of SCTP packets received from the peers." 699 ::= { sctpStats 17 } 701 -- PROTOCOL GENERAL VARIABLES 702 -- ************************** 704 sctpRtoAlgorithm OBJECT-TYPE 705 SYNTAX INTEGER { 706 other(1), -- Other new one. Future use 707 vanj(2) -- Van Jacobson's algorithm 708 } 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "The algorithm used to determine the timeout value (T3-rtx) 713 used for re-transmitting unacknowledged chunks." 715 ::= { sctpParams 1 } 717 sctpRtoMin OBJECT-TYPE 718 SYNTAX Unsigned32 719 UNITS "milliseconds" 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "The minimum value permitted by a SCTP implementation for the 724 retransmission timeout, measured in milliseconds. More 725 refined semantics for objects of this type depend upon the 726 algorithm used to determine the retransmission timeout. 727 The recommended value is 1000 milliseconds as per [RFC2960]. 728 Zero value means immediate re-transmission. 730 The value of this object has to be lower or equal than 731 stcpRtoMax's value." 733 ::= { sctpParams 2 } 735 sctpRtoMax OBJECT-TYPE 736 SYNTAX Unsigned32 737 UNITS "milliseconds" 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "The maximum value permitted by a SCTP implementation for the 742 retransmission timeout, measured in milliseconds. More 743 refined semantics for objects of this type depend upon the 744 algorithm used to determine the retransmission timeout. 745 Recommended value is 60000 milliseconds as per [RFC2960]. Zero 746 value means immediate re-transmission. 748 The value of this object has to be greater or equal than 749 stcpRtoMin's value." 751 ::= { sctpParams 3 } 753 sctpRtoInitial OBJECT-TYPE 754 SYNTAX Unsigned32 755 UNITS "milliseconds" 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "Initial value for the Retransmission timer. Recommended value 760 is 3000 milliseconds as per [RFC2960]. Zero value means 761 immediate re-transmission." 763 ::= { sctpParams 4 } 765 sctpMaxAssociations OBJECT-TYPE 766 SYNTAX Integer32 (-1 | 0..2147483647) 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "The limit on the total number of SCTP associations the entity 771 can support. In entities where the maximum number of 772 associations is dynamic, this object should contain the value 773 -1." 775 ::= { sctpParams 5 } 777 sctpValCookieLife OBJECT-TYPE 778 SYNTAX Unsigned32 779 UNITS "milliseconds" 780 MAX-ACCESS read-only 781 STATUS current 782 DESCRIPTION 783 "Valid cookie life in the 4-way start-up handshake procedure. 784 Recommended value: 60000 milliseconds." 786 ::= { sctpParams 6 } 788 sctpMaxInitRetr OBJECT-TYPE 789 SYNTAX Unsigned32 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "The maximum number of retransmissions at the start-up phase 794 (INIT and COOKIE ECHO chunks). Recommended value: 8 attempts." 796 ::= { sctpParams 7 } 798 -- TABLES 799 -- ****** 801 -- the SCTP Association TABLE 803 -- The SCTP association table contains information about each 804 -- association in which the local endpoint is involved. 806 sctpAssocTable OBJECT-TYPE 807 SYNTAX SEQUENCE OF SctpAssocEntry 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "A table containing SCTP association-specific information." 813 ::= { sctpObjects 3 } 815 sctpAssocEntry OBJECT-TYPE 816 SYNTAX SctpAssocEntry 817 MAX-ACCESS not-accessible 818 STATUS current 819 DESCRIPTION 820 "General common variables and statistics for the whole 821 association." 822 INDEX { sctpAssocId } 824 ::= { sctpAssocTable 1 } 826 SctpAssocEntry ::= SEQUENCE { 827 sctpAssocId Unsigned32, 828 sctpAssocRemHostName OCTET STRING, 829 sctpAssocLocalPort InetPortNumber, 830 sctpAssocRemPort InetPortNumber, 831 sctpAssocRemPrimaryAddressType InetAddressType, 832 sctpAssocRemPrimaryAddress InetAddress, 833 sctpAssocHeartBeatInterval Unsigned32, 834 sctpAssocState INTEGER, 835 sctpAssocInStreams Unsigned32, 836 sctpAssocOutStreams Unsigned32, 837 sctpAssocMaxRetr Unsigned32, 838 sctpAssocPrimaryProcess Unsigned32, 839 sctpAssocT1expireds Counter32, -- Statistic 840 sctpAssocT2expireds Counter32, -- Statistic 841 sctpAssocRtxChunks Counter32, -- Statistic 842 sctpAssocStartTime TimeStamp, 843 sctpAssocDiscontinuityTime TimeStamp 844 } 846 sctpAssocId OBJECT-TYPE 847 SYNTAX Unsigned32 (1..4294967295) 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "Association Identification. Value identifying the 852 association. The recommended option is to use the local 853 Initiate Tag, a.k.a. Verification Tag (see [RFC2960]). " 855 ::= { sctpAssocEntry 1 } 857 sctpAssocRemHostName OBJECT-TYPE 858 SYNTAX OCTET STRING (SIZE(0..115)) 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "Peer's DNS name. Currently only US ASCII format is the only 863 one allowed by DNS. But this object is open to include UTF-8 864 names if DNS evolve in this way. 866 If no DNS domain name was received at init time (embedded in 867 the INIT or INIT-ACK chunk) from the peer, this entry will be 868 meaningless, therefore it will contain a zero-length string 869 value. Otherwise, the remote host name received at init time 870 will be stored." 872 ::= { sctpAssocEntry 2 } 874 sctpAssocLocalPort OBJECT-TYPE 875 SYNTAX InetPortNumber (1..65535) 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "Local SCTP port number used for this association.." 881 ::= { sctpAssocEntry 3 } 883 sctpAssocRemPort OBJECT-TYPE 884 SYNTAX InetPortNumber (1..65535) 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "Remote SCTP port number used for this association." 890 ::= { sctpAssocEntry 4 } 892 sctpAssocRemPrimaryAddressType OBJECT-TYPE 893 SYNTAX InetAddressType 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "Internet type of primary remote IP address. 899 Only IPv4 and IPv6 addresses are expected." 901 ::= { sctpAssocEntry 5 } 903 sctpAssocRemPrimaryAddress OBJECT-TYPE 904 SYNTAX InetAddress 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "Primary remote IP address. The type of this address is 909 determined by the value of sctpAssocRemPrimaryAddressType. 911 The client side will know this value after INIT_ACK message 912 reception, the server side will know this value when sending 913 INIT ACK message. However, values will be filled in at 914 established state." 916 ::= { sctpAssocEntry 6 } 918 sctpAssocHeartBeatInterval OBJECT-TYPE 919 SYNTAX Unsigned32 920 UNITS "milliseconds" 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "The current heartbeat interval. The recommended default value 925 is 30000 milliseconds as per [RFC2960]. 927 Zero value means no HeartBeat, even when the concerned 928 sctpAssocRemAddressHBFlag object is active." 930 ::= { sctpAssocEntry 7 } 932 sctpAssocState OBJECT-TYPE 933 SYNTAX INTEGER { 934 closed(1), 935 cookieWait(2), 936 cookieEchoed(3), 937 established(4), 938 shutdownPending(5), 939 shutdownSent(6), 940 shutdownReceived(7), 941 shutdownAckSent(8), 942 deleteTCB(9) 943 } 944 MAX-ACCESS read-write 945 STATUS current 946 DESCRIPTION 947 "The state of this SCTP association. 949 As in TCP, deleteTCB is the only value that may be set by a 950 management station. If any other value is received, then the 951 agent must return a badValue error. 953 If a management station sets this object to the value 954 deleteTCB(9), then this has the effect of deleting the TCB (as 955 defined in SCTP) of the corresponding association on the 956 managed node, resulting in immediate termination of the 957 association. 959 A SET operation to the same(current) value is allowed. 961 As an implementation-specific option, an ABORT chunk may be 962 sent from the managed node to the other SCTP endpoint." 964 ::= { sctpAssocEntry 8 } 966 sctpAssocInStreams OBJECT-TYPE 967 SYNTAX Unsigned32 (1..65535) 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "Inbound Streams according to the negotiation at association 972 start up. " 974 ::= { sctpAssocEntry 9 } 976 sctpAssocOutStreams OBJECT-TYPE 977 SYNTAX Unsigned32 (1..65535) 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "Outbound Streams according to the negotiation at association 982 start up. " 984 ::= { sctpAssocEntry 10 } 986 sctpAssocMaxRetr OBJECT-TYPE 987 SYNTAX Unsigned32 988 MAX-ACCESS read-only 989 STATUS current 990 DESCRIPTION 991 "The maximum number of data retransmissions in the association 992 context. This value is specific for each association and the 993 upper layer can change it calling the appropriate primitives. 994 This value has to be smaller than the addition of all the 995 maximum number for all the paths 996 (sctpAssocRemAddressMaxPathRtx). 998 Recommended value: 10 attempts. 1000 Zero value means no retransmissions." 1002 ::= { sctpAssocEntry 11 } 1004 sctpAssocPrimaryProcess OBJECT-TYPE 1005 SYNTAX Unsigned32 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The number identifies the system level process which 1010 holds primary responsibility of the SCTP association. 1011 Wherever possible, this should be the system's native 1012 unique identification number. The special value 0 can 1013 be used to indicate that no primary process is known. 1015 Note that the value of this object can be used as a 1016 pointer into the swRunTable of the HOST-RESOURCES-MIB 1017 (if the value is smaller than 2147483647) or into the 1018 sysApplElmtRunTable of the SYSAPPL-MIB." 1020 ::= { sctpAssocEntry 12 } 1022 -- Association Statistics 1024 sctpAssocT1expireds OBJECT-TYPE 1025 SYNTAX Counter32 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION 1029 "Number of times that T1 timer expired (timer for sending 1030 either INIT or COOKIE-ECHO chunks and receiving an 1031 acknowledgment). 1033 Discontinuities in the value of this counter can occur at re- 1035 initialization of the management system, and at other times as 1037 indicated by the value of sctpAssocDiscontinuityTime." 1039 ::= { sctpAssocEntry 13 } 1041 sctpAssocT2expireds OBJECT-TYPE 1042 SYNTAX Counter32 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "Number of times that T2-shutdown timer expired (shutdown 1047 timer). 1049 Discontinuities in the value of this counter can occur at re- 1051 initialization of the management system, and at other times as 1053 indicated by the value of sctpAssocDiscontinuityTime." 1055 ::= { sctpAssocEntry 14 } 1057 sctpAssocRtxChunks OBJECT-TYPE 1058 SYNTAX Counter32 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "Number of data chunks retransmitted to the peer in the 1063 current association. 1065 Discontinuities in the value of this counter can occur at re- 1066 initialization of the management system, and at other times as 1067 indicated by the value of sctpAssocDiscontinuityTime." 1069 ::= { sctpAssocEntry 15 } 1071 sctpAssocStartTime OBJECT-TYPE 1072 SYNTAX TimeStamp 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "The value of SysUpTime at the time that this row association 1077 was established. The value of this object will be zero: 1078 - before the association enters the established state, or 1079 - if the established state was entered prior to the last 1080 re-initialization of the local network management 1081 subsystem." 1083 ::= { sctpAssocEntry 16 } 1085 sctpAssocDiscontinuityTime OBJECT-TYPE 1086 SYNTAX TimeStamp 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The value of sysUpTime on the most recent occasion at which 1091 any one or more of this sctp's counters suffered a 1092 discontinuity. The relevant counters are the specific 1093 instances associated with this interface of any Counter32 or 1094 Counter64 object contained in the sctpAssocTable or 1095 sctpXTable. If no such discontinuities have occurred since 1096 the last re-initialization of the local management subsystem, 1097 then this object contains a zero value. The inclusion of this 1098 object is recommended by [RFC2578]" 1100 ::= { sctpAssocEntry 17 } 1102 -- Expanded tables: Including Multi-home feature 1104 -- Local Address TABLE 1105 -- ******************* 1107 sctpAssocLocalAddressTable OBJECT-TYPE 1108 SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry 1109 MAX-ACCESS not-accessible 1110 STATUS current 1111 DESCRIPTION 1112 "Expanded table of sctpAssocTable based on the AssocId index. 1113 This table shows data related to each local IP address which 1114 is used by this association." 1116 ::= { sctpObjects 4 } 1118 sctpAssocLocalAddressEntry OBJECT-TYPE 1119 SYNTAX SctpAssocLocalAddressEntry 1120 MAX-ACCESS not-accessible 1121 STATUS current 1122 DESCRIPTION 1123 "Local information about the available addresses. There will 1124 be an entry for every local IP address defined for this 1125 association." 1127 INDEX { sctpAssocId, -- shared index 1128 sctpAssocLocalAddressType, 1129 sctpAssocLocalAddress } 1131 ::= { sctpAssocLocalAddressTable 1 } 1133 SctpAssocLocalAddressEntry ::= SEQUENCE { 1134 sctpAssocLocalAddressType InetAddressType, 1135 sctpAssocLocalAddress InetAddress, 1136 sctpAssocLocalAddressStartTime TimeStamp 1137 } 1139 sctpAssocLocalAddressType OBJECT-TYPE 1140 SYNTAX InetAddressType 1141 MAX-ACCESS not-accessible 1142 STATUS current 1143 DESCRIPTION 1144 "Internet type of local IP address used for this association. 1146 Only IPv4 and IPv6 addresses are expected." 1148 ::= { sctpAssocLocalAddressEntry 1 } 1150 sctpAssocLocalAddress OBJECT-TYPE 1151 SYNTAX InetAddress (SIZE(1..36)) 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "The value of a local IP address available for this 1156 association. The type of this address is determined by the 1157 value of sctpAssocLocalAddressType. " 1159 ::= { sctpAssocLocalAddressEntry 2 } 1161 sctpAssocLocalAddressStartTime OBJECT-TYPE 1162 SYNTAX TimeStamp 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "The value of SysUpTime at the time that this row was 1167 created." 1169 ::= { sctpAssocLocalAddressEntry 3 } 1171 -- Remote Addresses TABLE 1172 -- ********************** 1174 sctpAssocRemAddressTable OBJECT-TYPE 1175 SYNTAX SEQUENCE OF SctpAssocRemAddressEntry 1176 MAX-ACCESS not-accessible 1177 STATUS current 1178 DESCRIPTION 1179 "Expanded table of sctpAssocTable based on the AssocId index. 1180 This table shows data related to each remote peer IP address 1181 which is used by this association." 1183 ::= { sctpObjects 5 } 1185 sctpAssocRemAddressEntry OBJECT-TYPE 1186 SYNTAX SctpAssocRemAddressEntry 1187 MAX-ACCESS not-accessible 1188 STATUS current 1189 DESCRIPTION 1190 "Information about the most important variables for every 1191 remote IP address. There will be an entry for every remote IP 1192 address defined for this association." 1193 INDEX { sctpAssocId, -- shared index 1194 sctpAssocRemAddressType, 1195 sctpAssocRemAddress } 1197 ::= { sctpAssocRemAddressTable 1 } 1199 SctpAssocRemAddressEntry ::= SEQUENCE { 1200 sctpAssocRemAddressType InetAddressType, 1201 sctpAssocRemAddress InetAddress, 1202 sctpAssocRemAddressActive TruthValue, 1203 sctpAssocRemAddressHBActive INTEGER, 1204 sctpAssocRemAddressRTO Unsigned32, 1205 sctpAssocRemAddressMaxPathRtx Unsigned32, 1206 sctpAssocRemAddressRtx Counter32, -- Statistic 1207 sctpAssocRemAddressStartTime TimeStamp 1208 } 1210 sctpAssocRemAddressType OBJECT-TYPE 1211 SYNTAX InetAddressType 1212 MAX-ACCESS not-accessible 1213 STATUS current 1214 DESCRIPTION 1215 "Internet type of a remote IP address available for this 1216 association. 1218 Only IPv4 and IPv6 addresses are expected." 1220 ::= { sctpAssocRemAddressEntry 1 } 1222 sctpAssocRemAddress OBJECT-TYPE 1223 SYNTAX InetAddress (SIZE(1..36)) 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "The value of a remote IP address available for this 1228 association. The type of this address is determined by the 1229 value of sctpAssocLocalAddressType. " 1231 ::= { sctpAssocRemAddressEntry 2 } 1233 sctpAssocRemAddressActive OBJECT-TYPE 1234 SYNTAX TruthValue 1235 MAX-ACCESS read-only 1236 STATUS current 1237 DESCRIPTION 1238 "This object gives information about the reachability of this 1239 specific remote IP address. 1241 When the object is set to 'true' (1), the remote IP address is 1242 understood as Active. Active means that the threshold of no 1243 answers received from this IP address has not been reached. 1245 When the object is set to 'false' (2), the remote IP address 1246 in understood as Inactive. Inactive means that either no 1247 heartbeat or any other message was received from this address, 1248 reaching the threshold defined by the protocol." 1250 REFERENCE 1251 "The remote transport states are defined as Active and 1252 Inactive in the SCTP, [RFC2960]." 1254 ::= { sctpAssocRemAddressEntry 3 } 1256 sctpAssocRemAddressHBActive OBJECT-TYPE 1257 SYNTAX TruthValue 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "This object indicates whether the optional Heartbeat check 1262 associated to one destination transport address is activated 1263 or not (value equal to true or false, respectively). " 1265 ::= { sctpAssocRemAddressEntry 4 } 1267 sctpAssocRemAddressRTO OBJECT-TYPE -- T3-rtx- Timer 1268 SYNTAX Unsigned32 1269 UNITS "milliseconds" 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The current Retransmission Timeout. T3-rtx timer as defined 1274 in the protocol SCTP." 1276 ::= { sctpAssocRemAddressEntry 5 } 1278 sctpAssocRemAddressMaxPathRtx OBJECT-TYPE 1279 SYNTAX Unsigned32 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "Maximum number of DATA chunks retransmissions allowed to a 1284 remote IP address before it is considered inactive, as defined 1285 in [RFC2960]. Recommended value 5 attempts." 1287 ::= { sctpAssocRemAddressEntry 6 } 1289 -- Remote Address Statistic 1291 sctpAssocRemAddressRtx OBJECT-TYPE 1292 SYNTAX Counter32 1293 MAX-ACCESS read-only 1294 STATUS current 1295 DESCRIPTION 1296 "Number of DATA chunks retransmissions as defined in 1297 [RFC2960]. 1299 Discontinuities in the value of this counter can occur at re- 1300 initialization of the management system, and at other times as 1301 indicated by the value of sctpAssocDiscontinuityTime." 1303 ::= { sctpAssocRemAddressEntry 7 } 1305 sctpAssocRemAddressStartTime OBJECT-TYPE 1306 SYNTAX TimeStamp 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "The value of SysUpTime at the time that this row was 1311 created." 1313 ::= { sctpAssocRemAddressEntry 8 } 1315 -- ASSOCIATION INVERSE TABLE 1316 -- ************************* 1318 -- BY LOCAL PORT 1320 sctpLookupLocalPortTable OBJECT-TYPE 1321 SYNTAX SEQUENCE OF SctpLookupLocalPortEntry 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "With the use of this table, a list of associations which are 1326 using the specified local port can be got" 1328 ::= { sctpObjects 6 } 1330 sctpLookupLocalPortEntry OBJECT-TYPE 1331 SYNTAX SctpLookupLocalPortEntry 1332 MAX-ACCESS not-accessible 1333 STATUS current 1334 DESCRIPTION 1335 "This table is indexed by local port and association ID. 1336 Specifying a local port, we would get a list of the 1337 associations whose local port is the one specified" 1339 INDEX { sctpAssocLocalPort, 1340 sctpAssocId } 1342 ::= { sctpLookupLocalPortTable 1 } 1344 SctpLookupLocalPortEntry::= SEQUENCE { 1345 sctpLookupLocalPortStartTime TimeStamp 1346 } 1348 sctpLookupLocalPortStartTime OBJECT-TYPE 1349 SYNTAX TimeStamp 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "The value of SysUpTime at the time that this row was 1354 created." 1356 ::= { sctpLookupLocalPortEntry 1 } 1358 -- BY REMOTE PORT 1359 sctpLookupRemPortTable OBJECT-TYPE 1360 SYNTAX SEQUENCE OF SctpLookupRemPortEntry 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "With the use of this table, a list of associations which are 1365 using the specified remote port can be got" 1367 ::= { sctpObjects 7 } 1369 sctpLookupRemPortEntry OBJECT-TYPE 1370 SYNTAX SctpLookupRemPortEntry 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "This table is indexed by remote port and association ID. 1375 Specifying a remote port we would get a list of the 1376 associations whose local port is the one specified " 1378 INDEX { sctpAssocRemPort, 1379 sctpAssocId } 1381 ::= { sctpLookupRemPortTable 1 } 1383 SctpLookupRemPortEntry::= SEQUENCE { 1384 sctpLookupRemPortStartTime TimeStamp 1385 } 1387 sctpLookupRemPortStartTime OBJECT-TYPE 1388 SYNTAX TimeStamp 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "The value of SysUpTime at the time that this row was 1393 created." 1395 ::= { sctpLookupRemPortEntry 1 } 1397 -- BY REMOTE HOST NAME 1399 sctpLookupRemHostNameTable OBJECT-TYPE 1400 SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry 1401 MAX-ACCESS not-accessible 1402 STATUS current 1403 DESCRIPTION 1404 "With the use of this table, a list of associations with that 1405 particular host can be got" 1407 ::= { sctpObjects 8 } 1409 sctpLookupRemHostNameEntry OBJECT-TYPE 1410 SYNTAX SctpLookupRemHostNameEntry 1411 MAX-ACCESS not-accessible 1412 STATUS current 1413 DESCRIPTION 1414 "This table is indexed by remote host name and association ID. 1415 Specifying a host name we would get a list of the associations 1416 specifying that host name as the remote one" 1418 INDEX { sctpAssocRemHostName, 1419 sctpAssocId } 1421 ::= { sctpLookupRemHostNameTable 1 } 1423 SctpLookupRemHostNameEntry::= SEQUENCE { 1424 sctpLookupRemHostNameStartTime TimeStamp 1425 } 1427 sctpLookupRemHostNameStartTime OBJECT-TYPE 1428 SYNTAX TimeStamp 1429 MAX-ACCESS read-only 1430 STATUS current 1431 DESCRIPTION 1432 "The value of SysUpTime at the time that this row was 1433 created." 1435 ::= { sctpLookupRemHostNameEntry 1 } 1437 -- BY REMOTE PRIMARY IP ADDRESS 1439 sctpLookupRemPrimIPAddrTable OBJECT-TYPE 1440 SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry 1441 MAX-ACCESS not-accessible 1442 STATUS current 1443 DESCRIPTION 1444 "With the use of this table, it can be got a list of 1445 associations that have that the specified IP address as 1446 primary within the remote set of active addresses " 1448 ::= { sctpObjects 9 } 1450 sctpLookupRemPrimIPAddrEntry OBJECT-TYPE 1451 SYNTAX SctpLookupRemPrimIPAddrEntry 1452 MAX-ACCESS not-accessible 1453 STATUS current 1454 DESCRIPTION 1455 "This table is indexed by primary address and association ID. 1456 Specifying a primary address, we would get a list of the 1457 associations that have the specified remote IP address marked 1458 as primary. " 1460 INDEX { sctpAssocRemPrimaryAddressType, 1461 sctpAssocRemPrimaryAddress, 1462 sctpAssocId } 1464 ::= { sctpLookupRemPrimIPAddrTable 1 } 1466 SctpLookupRemPrimIPAddrEntry::= SEQUENCE { 1467 sctpLookupRemPrimIPAddrStartTime TimeStamp 1468 } 1470 sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE 1471 SYNTAX TimeStamp 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "The value of SysUpTime at the time that this row was 1476 created." 1478 ::= { sctpLookupRemPrimIPAddrEntry 1 } 1480 -- BY REMOTE IP ADDRESS 1482 sctpLookupRemIPAddrTable OBJECT-TYPE 1483 SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry 1484 MAX-ACCESS not-accessible 1485 STATUS current 1486 DESCRIPTION 1487 "With the use of this table, a list of associations that have 1488 the specified IP address as one of the remote ones can be got" 1490 ::= { sctpObjects 10 } 1492 sctpLookupRemIPAddrEntry OBJECT-TYPE 1493 SYNTAX SctpLookupRemIPAddrEntry 1494 MAX-ACCESS not-accessible 1495 STATUS current 1496 DESCRIPTION 1497 "This table is indexed by a remote IP address and association 1498 ID. Specifying an IP address we would get a list of the 1499 associations that have the specified IP address included 1500 within the set of remote IP addresses" 1502 INDEX { sctpAssocRemAddressType, 1503 sctpAssocRemAddress, 1504 sctpAssocId } 1506 ::= { sctpLookupRemIPAddrTable 1 } 1508 SctpLookupRemIPAddrEntry::= SEQUENCE { 1509 sctpLookupRemIPAddrStartTime TimeStamp 1510 } 1512 sctpLookupRemIPAddrStartTime OBJECT-TYPE 1513 SYNTAX TimeStamp 1514 MAX-ACCESS read-only 1515 STATUS current 1516 DESCRIPTION 1517 "The value of SysUpTime at the time that this row was 1518 created." 1520 ::= { sctpLookupRemIPAddrEntry 1 } 1522 -- 4.1 Conformance Information 1524 sctpConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } 1525 sctpCompliances OBJECT IDENTIFIER ::= { sctpConformance 1 } 1526 sctpGroups OBJECT IDENTIFIER ::= { sctpConformance 2 } 1528 -- 4.1.1 Units of conformance 1530 -- 1531 -- MODULE GROUPS 1532 -- 1534 sctpLayerParamsGroup OBJECT-GROUP 1535 OBJECTS { sctpRtoAlgorithm, 1536 sctpRtoMin, 1537 sctpRtoMax, 1538 sctpRtoInitial, 1539 sctpMaxAssociations, 1540 sctpValCookieLife, 1541 sctpMaxInitRetr 1543 } 1545 STATUS current 1546 DESCRIPTION 1547 "Common parameters for the SCTP layer, i.e. for all the 1548 associations. They can usually be referred as configuration 1549 parameters." 1551 ::= { sctpGroups 1 } 1553 sctpStatsGroup OBJECT-GROUP 1554 OBJECTS {sctpCurrEstab, 1555 sctpActiveEstabs, 1556 sctpPassiveEstabs, 1557 sctpAborteds, 1558 sctpShutdowns, 1559 sctpOutOfBlues, 1560 sctpChecksumErrors, 1561 sctpOutCtrlChunks, 1562 sctpOutOrderChunks, 1563 sctpOutUnorderChunks, 1564 sctpInCtrlChunks, 1565 sctpInOrderChunks, 1566 sctpInUnorderChunks, 1567 sctpFragUsrMsgs, 1568 sctpReasmUsrMsgs, 1569 sctpOutSCTPPacks, 1570 sctpInSCTPPacks, 1571 sctpAssocT1expireds, 1572 sctpAssocT2expireds, 1573 sctpAssocRtxChunks, 1574 sctpAssocRemAddressRtx 1575 } 1577 STATUS current 1578 DESCRIPTION 1579 "Statistics group. It includes the objects to collect state 1580 changes in the SCTP protocol local layer and flow control 1581 statistics. Also per-association statistics are included." 1583 ::= { sctpGroups 2 } 1585 sctpPerAssocParamsGroup OBJECT-GROUP 1586 OBJECTS {sctpAssocRemHostName, 1587 sctpAssocLocalPort, 1588 sctpAssocRemPort, 1589 sctpAssocRemPrimaryAddressType, 1590 sctpAssocRemPrimaryAddress, 1591 sctpAssocHeartBeatInterval, 1592 sctpAssocState, 1593 sctpAssocInStreams, 1594 sctpAssocOutStreams, 1595 sctpAssocMaxRetr, 1596 sctpAssocPrimaryProcess, 1597 sctpAssocStartTime, 1598 sctpAssocDiscontinuityTime, 1599 sctpAssocLocalAddressStartTime, 1600 sctpAssocRemAddressActive, 1601 sctpAssocRemAddressHBActive, 1602 sctpAssocRemAddressRTO, 1603 sctpAssocRemAddressMaxPathRtx, 1604 sctpAssocRemAddressStartTime 1605 } 1607 STATUS current 1608 DESCRIPTION 1609 "The SCTP group of objects to manage per-association 1610 parameters. These variables include all the SCTP basic 1611 features." 1613 ::= { sctpGroups 3 } 1615 sctpInverseGroup OBJECT-GROUP 1616 OBJECTS {sctpLookupLocalPortStartTime, 1617 sctpLookupRemPortStartTime, 1618 sctpLookupRemHostNameStartTime, 1619 sctpLookupRemPrimIPAddrStartTime, 1620 sctpLookupRemIPAddrStartTime 1621 } 1623 STATUS current 1624 DESCRIPTION 1625 "Objects used in the inverse lookup table." 1627 ::= { sctpGroups 4 } 1629 -- 4.1.2 Compliance Statements 1631 -- 1632 -- MODULE COMPLIANCES 1633 -- 1635 sctpCompliance MODULE-COMPLIANCE 1636 STATUS current 1637 DESCRIPTION 1638 "The compliance statement for SNMP entities which implement 1639 SCTP. " 1641 MODULE -- this module 1643 MANDATORY-GROUPS { sctpLayerParamsGroup, 1644 sctpPerAssocParamsGroup, 1645 sctpStatsGroup 1646 } 1647 GROUP sctpInverseGroup 1648 DESCRIPTION 1649 "Objects used in inverse lookup tables. This should be 1650 implemented for easier lookups in the association tables, 1651 when it is required." 1653 OBJECT sctpAssocRemPrimaryAddressType 1654 SYNTAX InetAddressType { ipv4(1), 1655 ipv6(2) 1656 } 1657 DESCRIPTION 1658 "It is only required to have IPv4 and IPv6 addresses 1659 without zone indices. 1661 The address with zone indices is required if an 1662 implementation can connect multiple zones." 1664 OBJECT sctpAssocRemPrimaryAddress 1665 SYNTAX InetAddress (SIZE(4|16)) 1666 DESCRIPTION 1667 "An implementation is only required to support globally 1668 unique IPv4 and globally unique IPv6 addresses." 1670 OBJECT sctpAssocState 1671 WRITE-SYNTAX INTEGER { deleteTCB(9) } 1672 DESCRIPTION 1673 "Only the deletedTCB(9) object's value can be written" 1675 ::= { sctpCompliances 1 } 1677 END 1679 5. Compiling Notes 1681 After compiling the MIB the following warning can be got: 1683 @ index of row `sctpLookupRemPrimIPAddrEntry' can exceed OID size 1684 limit by 141 subidentifier(s) 1686 This comes from the fact that sctpAssocRemPrimaryAddress has the 1687 default InetAddress size of (0..255) which exceeds OID size 1688 limitations. Introducing a size restriction on 1689 sctpAssocRemPrimaryAddress would make the warning go away � although 1690 it would be one of those more arbitrary restrictions. 1692 6. References 1694 6.1 Normative References 1696 [RFC2960] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J. 1697 Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. 1698 Paxson, "Stream Control Transmission Protocol", October 2000. 1700 [sctpcheck] R. Stewart, J. Stone, D. Otis, "SCTP Checksum Change", 1701 January 18, 2002, draft-ietf-tsvwg-sctpcsum-07.txt, work in 1702 progress 1704 [sctpImplem] R. Stewart, L. Ong, I. Arias-Rodriguez, A. Caro, M. 1705 Tuexen, "Stream Control Transmission Protocol (SCTP) 1706 Implementers Guide", January 18, 2002, draft-ietf-tsvwg- 1707 sctpimpguide-06.txt, work in progress 1709 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1710 "Protocol Operations for Version 2 of the Simple Network 1711 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1713 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1714 "Transport Mappings for Version 2 of the Simple Network 1715 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1717 [RFC2571] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for 1718 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1720 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1721 "Message Processing and Dispatching for the Simple Network 1722 Management Protocol (SNMP)", RFC 2572, April 1999. 1724 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1725 RFC 2573, April 1999. 1727 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1728 (USM) for version 3 of the Simple Network Management Protocol 1729 (SNMPv3)", RFC 2574, April 1999. 1731 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1732 Access Control Model (VACM) for the Simple Network Management 1733 Protocol (SNMP)", RFC 2575, April 1999. 1735 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1736 Rose, M., and S. Waldbusser, "Structure of Management 1737 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1739 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1740 Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", 1741 STD 58, RFC 2579, April 1999. 1743 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1744 Rose, M., and S. Waldbusser, "Conformance Statements for 1745 SMIv2", STD 58, RFC 2580, April 1999. 1747 6.1 Informative References 1749 [SecSNMP] Stallings, W., "SNMP3: A Security Enhancement for SNMP", 1750 IEEE Communication Surveys, Forth quarter 1998, Vol. 1 No. 1. 1752 [Cong] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1753 1988, Stanford, California. 1755 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1756 of Management Information for TCP/IP-based Internets", STD 16, 1757 RFC 1155, May 1990. 1759 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1760 Network Management Protocol", STD 15, RFC 1157, May 1990. 1762 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1763 16, RFC 1212, March 1991. 1765 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1766 SNMP", RFC 1215, March 1991. 1768 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1769 "Introduction to Community-based SNMPv2", RFC 1901, January 1770 1996. 1772 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1773 Transmission Control Protocol using SMIv2", RFC 2012, November 1774 1996. 1776 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1777 "Introduction to Version 3 of the Internet-standard Network 1778 Management Framework", RFC 2570, April 1999. 1780 [RFC3291] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder, 1781 "Textual Conventions for Internet Network Addresses", May 2002. 1783 [IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, 1784 A. and B. Zill, "IPv6 Scoped Address Architecture", draft- 1785 ietf-ipngwg-scoping-arch-04.txt, December 2002. Work in 1786 progress. 1788 [TADDRESS] M. Daniele , J. Schoenwaelder , "Textual Conventions for 1789 Transport Addresses", draft-ietf-ops-taddress-mib-03.txt, July 1790 22, 2002. Work in progress. 1792 [TCPMIB] Bill Fenner, Keith McCloghrie, Rajiv Raghunarayan, Juergen 1793 Schoenwalder, "Management Information Base for the Transmission 1794 Control Protocol (TCP) ", draft-ietf-ipv6-rfc2012-update-00.txt 1795 , June 2002. Work in progress. 1797 [UDPMIB] Bill Fenner, "Management Information Base for User Datagram 1798 Protocol (UDP draft-ietf-ipv6-rfc2013-update-00.txt, June 2002. 1799 Work in progress. 1801 7. Full Copyright Statement 1803 Copyright (C) The Internet Society (2002). All Rights Reserved. 1804 This document and translations of it may be copied and furnished to 1805 others, and derivative works that comment on or otherwise explain it 1806 or assist in its implementation may be prepared, copied, published 1807 and distributed, in whole or in part, without restriction of any 1808 kind, provided that the above copyright notice and this paragraph are 1809 included on all such copies and derivative works. However, this 1810 document itself may not be modified in any way, such as by removing 1811 the copyright notice or references to the Internet Society or other 1812 Internet organizations, except as needed for the purpose of 1813 developing Internet standards in which case the procedures for 1814 copyrights defined in the Internet Standards process must be 1815 followed, or as required to translate it into languages other than 1816 English. 1818 The limited permissions granted above are perpetual and will not be 1819 revoked by the Internet Society or its successors or assigns. 1821 This document and the information contained herein is provided on an 1822 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1823 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1824 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1825 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1826 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1828 8. Security Consideration 1829 The deleteTCB management object, defined in this MIB, has a MAX- 1830 ACCESS clause of read-write. This is because it allows operators to 1831 tear down the associations. Such object may be considered sensitive 1832 or vulnerable in some network environments. The support for SET 1833 operations in a non-secure environment without proper protection can 1834 have a negative effect on network operations. 1836 It is thus important to control even GET access to these objects and 1837 possibly to even encrypt the values of these object when sending them 1838 over the network via SNMP. Not all versions of SNMP provide features 1839 for such a secure environment. 1841 SNMPv1 by itself is not a secure environment. Even if security 1842 measures are taken (e.g., using IPSEC), there is no per-user control 1843 as to who (once an IPSEC association is established between hosts) is 1844 allowed to GET or SET the objects in this MIB 1846 It is recommended that the implementers consider the security 1847 features as provided by the SNMPv3 framework. Specifically, the use 1848 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1849 based Access Control Model RFC 2575 [RFC2575] is recommended. 1851 It is then a customer/user responsibility to ensure that the SNMP 1852 entity giving access to an instance of this MIB, is properly 1853 configured to give access to the objects only to those principals 1854 (users) that have legitimate rights to indeed GET or SET 1855 (change/create/delete) them. 1857 8. Acknowledgments 1859 The authors wish to thank Juergen Schoenwaelder, David Partain, Shawn 1860 A. Routhier, Ed Yarwood, John Linton, Shyamal Prasad Juan-Francisco 1861 Martin, Dave Thaler, and Bert Wijnen for their invaluable comments. 1863 9. Authors' Addresses 1865 Javier Pastor-Balbas Tel: +34-91-339-3819 1866 Ericsson Espana S.A. eMail: J.Javier.Pastor@ericsson.com 1867 Network Communication Services 1868 Ombu 3, 4th floor 1869 Madrid, 28045 1870 Spain 1872 Maria-Carmen Belinchon Tel: +34-91-339-3535 1873 Ericsson Espana S.A. eMail: Maria.C.Belinchon@ericsson.com 1874 Network Communication Services 1875 Ombu 3, 4th floor 1876 Madrid, 28045 1877 Spain 1879 10. Revision History 1881 RFC-Editor to remove this section before publication as RFC. 1883 10.1 Changes from 1885 o Open issues updated 1887 o Section 2: Reference to RFC227x changed to RFC257x 1889 o Section 4: Inside the sctpRtoAlgorithm definition has been put 1890 "other" first rather than last. That way, it won't end up in the 1891 middle of things when new enumerations are added later. 1893 10.2 Changes from 1895 o Change of "Simple" word to "Stream" word in SCTP acronyms 1897 o Version of the MIB based on SCTPv10 1899 o Section 2: Update SNMP Framework to include the standard 1900 explanation 1902 o New Structure for the MIB: 1903 sctp 1904 \- sctpObjects 1905 \- sctpScalars 1906 \- sctpTables 1907 \- sctpMIBConformance 1909 o Section 4.1.2: Unit of Conformance updated (functional structure). 1911 o MAX-ACCESS clauses reviewed 1913 o The general statistics has been re-ordered, placed before the 1914 tables. 1916 o In SMIv2, indexes should be not-accessible (= the object type is a 1917 column in a table used as index and may not be used as an operand in 1918 any operation != SMIv1) (pp109-110 in []) 1920 o IPv6 compatible: 1921 - Change of Primary/Local/Remote addresses 1922 - PENDING: check "MODULE-COMPLIANCE" 1924 o Row Status included in AssocTable, AssocLocal and AssocRem to 1925 create, modify and delete rows in the tables. 1927 o SCTP general statistics changed from Counter32 to Counter64 since 1928 it supports more data changes. 1930 o sctpCurrEstab ("State-related variables and statistics" section) 1931 variable changed from Gauge32 to Counter32. 1933 o sctpAssocRemAddressT1expired and sctpAssocRemAddressT2expired have 1934 been removed from the remote table and added in the general 1935 association data since they are variables per association (not per IP 1936 address). 1938 o sctpAssocDropDatag statistic has been removed from the general 1939 association statistics since it had an ambiguous meaning. 1941 o Explained the meaning of the unordered chunks (chunks in which the 1942 U bit is set to 1) in sctpStatOutOfOrderSentChunks and 1943 sctpStatOutOfOrderRecChunks. 1945 o Added sctpChecksumErrorCounter to collect information about wrong 1946 checksums received from the peer. 1948 o Specify that sctpStatSentChunks and sctpStatRecChunks does not 1949 contain retransmission chunks. 1951 o Reword the Security Considerations chapter pointing out that IPsec 1952 does not secure the network but it provides end-to-end security over 1953 a network. 1955 o sctpAssocRemAddressRtxChunks replaced as a variable per 1956 association, meaning the number of chunks retransmited to the peer in 1957 the current association. 1959 o sctpHeartBeatMisses and sctpMaxRetr have been replaced from the 1960 general SCTP statistics to the remote IP address table 1961 (sctpHeartBeatMisses) and in the association table (sctpMaxRetr). 1963 o Specify that the retransmissions in the general SCTP statistics 1964 include control plus data chunks. 1966 o Included heartbeat timer for remote IP address. 1968 o Removed sctpAssocRemAddressHeartBeatMisses variable from the remote 1969 IP address table. 1971 o Removed sctpAssocRemAddressT3expired variable from the remote IP 1972 address table. 1974 o Updated variables to the new SCTP states defined in v10. 1976 10.3 Changes from 1978 o sctpRtoMin - stray "." outside the double-quotes in the DESCRIPTION 1979 clause. 1981 o sctpRtoMax - stray "." outside the double-quotes in the DESCRIPTION 1982 clause. 1984 o sctpAssocRemHostName - the type OCTECT STRING should be OCTET 1985 STRING. 1987 o sctpAssocRemPrimaryAddress - the DESCRIPTION clause is missing its 1988 closing ouble-quote. 1990 o sctpConformance - this is defined as { sctpMIB 2 }, then never 1991 used; instead sctpMIBConformance (which is undefined) is used in the 1992 definition of sctpMIBGroups and sctpMIBCompliances. 1994 o Reworded the MIB organization 1996 o Removed maximum number of concurrent associations 1998 o In sctpMIBCompliance, removed a missing comma in MANDATORY-GROUPS. 2000 o In sctpAssocTablesVariablesGroup and sctpAssocStatGroup, removed 2001 extra commas at end of OBJECTS list. 2003 o sctpAssocInStreams. ACCESS changed from read-create to read-only. 2005 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 2006 changed from per remote IP address to per association. 2008 o Comment on sctpAssocRemAddressHBTimer specifies now that the 2009 manager can change it. 2011 o ACCESS on sctpAssocRemAddressHBTimer changed from read-only to 2012 read-write. 2014 o ACCESS on sctpAssocRemAddressRetransCount changed from read-write 2015 to read-only. 2017 o Move sctpStatChecksumErrorCounter from general statistics to per 2018 association. 2020 o sctpMaxInStreams � It�s a sctp-user feature. 2022 o sctpStatRetransChunks � It�s more useful to have this statistic in 2023 a association basis 2025 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 2026 have been created again instead of per association in order to follow 2027 the draft. If some implementations want to have the same value for 2028 all the associations they have, they should set all the variables in 2029 the different remote addresses to the same value. 2031 10.3 Changes from 2033 o Deleting all the RowStatus Structure. Associated text rewording in 2034 Tables section. 2036 o Variable StartTime added in all the tables in order to specify the 2037 creation time. 2039 o Adding the Association reverse lookup table for easier management. 2040 Associated text rewording in tables section. 2042 o Remove sctpInitialT1 and sctpInitialT2, since these values are 2043 equal to RTO. 2045 o Change of the Heartbeats to a per-association basis 2047 o Conformance up-to-date with all of this. 2049 10.4 Changes from 2051 Main changes are due to the alignment with the TCP and UDP MIBs and 2052 the inclusion of new lookup tables. 2053 o Convert MIB to a read-only 2055 o Counters ends with �s� 2057 o Include �unknown� as an option for InetAddressType in conformance 2059 o Terminology fix: CLOSED state, unordered chunks instead of out-of- 2060 order, .. 2062 o HBFlag changed to per remote address 2064 o ChecksumErrors out of the AssocTable and hangs from Scalars 2066 o Update Ports from Unsigned32 to InetPortNumber according to 2067 RFC2851-update 2069 o Rework inverse tables: five new lookup tables 2071 o Remove INTEGER32 and change it to UNSIGNED32 2073 o Replace Counter32 by Counter64 2074 o Split Sent and Received chunks per association into control, 2075 ordered and unordered chunks 2077 10.5 Changes from 2079 Changes due to the IETF-51 meeting and requests from the mailing 2080 list. 2081 o Typo errors 2083 o Objects renumbering 2085 o All counters to Counter32 to be backward compatible, not to waste 2086 memory. Operators needing more than 32 bits will do it by 2087 augmentations. 2089 o Limit the number of IP address size when index 2091 o Specify that a port number with value zero means unknown port 2092 number according to the RFC2851-update 2094 Changes due to the alignment with the RFC2851-update. 2096 o Include clarification text of the IP address types supported in the 2097 SCTP MIB. Chapter 3.1.2.1 (Association table) 2099 o Remote Primary IP address: Addition of the ipv4z an ipv6z types for 2100 non-globally IP addresses in which a scope identifier is needed. 2101 Addition of the scope of ipv6 type. All of them according to the 2102 RFC2851-update v04 2104 o InetAddressType for local and remote IP addresses: 2106 Limit UNKNOWN type only for unknown IP address format. Remove UNKNOWN 2107 type for zero-length value in the InetAddress since it will be never 2108 zero-length due to the size restriction (0..64) 2110 Addition of the ipv4z an ipv6z types for non-globally IP addresses in 2111 which a scope identifier is needed. Addition of the scope of ipv6 2112 type. All of them according to the RFC2851-update v04 2114 o Clarify when mapping DNS <-> IPaddress occurs with the remote IP 2115 addresses 2117 o Conformance: 2119 Description: Specify that the SCTP MIB only need to support IPv4/IPv6 2120 addresses without a zone index, unknown type and DNS names. Support 2121 for IPv4/IPv6 addresses with zone indices is not required. 2123 InetAddressType for primary, local and remote IP addresses: Clarify 2124 that the implementation is only required to support IPv4 and IPv6 2125 address types without zone indices. Clarify also that UNKONWN type is 2126 only used in case of local and remote addresses when invalid/unknown 2127 IP address format 2129 InetAddress value of primary, local and remote IP address: Removal of 2130 the InetAddress values supported. Limitation of the supported IP 2131 address types is already included in the InetAddressType 2133 o Revision of the RFC2851-update v05. Changes in this draft does not 2134 affect the SCTP MIB. 2136 10.6 Changes from 2138 Changes due to the IPv6mib Design Team and the Sigtran mailing list. 2140 o RFC2851-update v06 (changes) does not affect the SCTP MIB 2142 o Typo errors 2144 o Restructure the MIB organization (tree): 2145 sctp 2146 \- sctpParameters 2147 \- sctpStats 2149 o Modify conformance section according to the new MIB structure. 2150 Statistics and lookup tables will be optional 2152 o Clarify that the SCTP MIB is based on the TCP MIB update 2153 (RFC2012update) and the TCs for Internet Network Addresses 2154 (RFC2851update) � remove reference to RFC2452 2156 o Replace "Sent" by "out" and "Received" by "in" in statistics 2158 o Change the sctpAssocId to exclude the value zero. This allows other 2159 MIBs to reference associations and to use the value 0 to indicate no 2160 association 2162 o Clarify sctpRemHostName to be zero-length value when no remote host 2163 name was received at the initialization stage 2165 o Limit the range of local and remote ports to (1..65535). Value 0 2166 (unknown port number according to RFC2851-update) is not valid in 2167 SCTP associations since there is no way of having an assoc with an 2168 unknown local or remote port 2170 o sctpAssocRemPrimaryAddressType and sctpAssocRemPrimaryAddress value 2171 to be filled in with a zero length string until valid values are 2172 received in the INIT or INIT ACK chunk 2173 o sctpAssocRemAddress and sctpAssocLocalAddressIP size upper limit 2174 restriction to 36, as TCP MIB 2176 o Change to Counter64 those counters which may wrap in less than an 2177 hour 2179 o Change sctpMaxAssoc variable to Integer32 since value �1 is allowed 2180 for dynamic maximum number of associations 2182 o Added a new column in the association table to give a pointer to 2183 the primary system level process which holds the association 2184 endpoint(sctpAssocPrimaryProcess) 2186 o Specify in the security section, which object should be handled 2187 carefully for security reasons 2189 10.7 Changes from 2191 o Change of the variable structure to: 2193 MIB-2 {1 3 6 1 2 2} 2194 +--(xxx)sctpMIB 2195 | 2196 +--(1) sctpObjects 2197 | | 2198 | +--(1) sctpStats 2199 | | | 2200 | | +-- 2201 | | 2202 | +--(2)sctpParameters 2203 | | | 2204 | | +-- 2205 | | 2206 | +--(3) sctpAssocTable 2207 | | 2208 | +--(4) sctpAssocLocalAddressTable 2209 | | 2210 | +--(5) sctpAssocRemAddressTable 2211 | | 2212 | +--(6) sctpLookupLocalPortTable 2213 | | 2214 | +--(7) sctpLookupRemPortTable 2215 | | 2216 | +--(8) sctpLookupRemHostNameTable 2217 | | 2218 | +--(9) sctpLookupRemPrimIPAddrTable 2219 | | 2220 | +--(10) sctpLookupRemIPAddrTable 2221 | 2222 | 2223 +--(2)sctpConformance 2224 | 2225 +--(1) sctpCompliances 2226 | | 2227 | +-sctpCompliance 2228 | 2229 +--(2) sctpGroups 2230 | 2231 +--(1) sctpParametersGroup 2232 | 2233 +--(2) sctpStatGroup 2234 | 2235 +--(3) sctpAssocTableParametersGroup 2236 | 2237 +--(4) sctpInverseGroup 2239 o New chapter for compilation notes created 2241 o References ordered and updated 2243 10.8 Changes from 2245 Changes due to the TSV WG, Sigtran technical advisor and O&M A-Ds 2246 review. 2248 o Typo errors 2250 o Include a REVISION clause in the MODULE-IDENTITY macro 2252 o Included a discontinuity timer object for sctpAssocTable. Such is 2253 needed as per RFC2978, sect 7.1.6 and sect 7.1.10 2255 o Define which objects allow to have a zero value and specify in 2256 which cases. 2258 o Eliminate zero value in indexes. 2260 o sctpAssocRemHostName is OCTET STRING and it will be interpreted 2261 under the DNS criteria. 2263 o Eliminated redundant information from RFC 3291 2265 o Only IPv4 and IPv6 addresses are expected 2267 o Accept a SET for a value that is exactly the same as the 2268 current value (a NO-OP). Comment added to show this. 2270 o Tables are created with values from INIT and INIT ACK SCTP 2271 messages. All values are present when rows are created. 2273 o Use of TruthValue for IP addresses state and Heart Beat. 2275 o Reword of Lookup tables description 2277 o Lookup Tables. Place Associatio State instead of Stamp Time object 2279 o Removed �unknown� type from addresses. They will be always known, 2280 otherwise row will not be created. 2282 o Same restriction added for the the Address itself 2284 o For the object sctpAssocState, formally indicated that only one 2285 enum (deleteTCB) is writable 2287 o SNMP boiler plate (Sect 2) changed. 2289 o IPR section added as per RFC2026 Sect 10. 2291 o Removed Tag value identifier as possible value inside AssocId 2292 object.