idnits 2.17.1 draft-ietf-sigtran-sctp-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1505 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 90 instances of too long lines in the document, the longest one being 32 characters in excess of 72. ** There are 240 instances of lines with control characters in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 691: '... unknown address type. This value MUST...' RFC 2119 keyword, line 893: '... unknown address type. This value MUST...' RFC 2119 keyword, line 977: '... unknown address type. This value MUST...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 545 has weird spacing: '...eceived by th...' -- 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) -- Looks like a reference, but probably isn't: '2' on line 84 -- Looks like a reference, but probably isn't: '1' on line 86 == Missing Reference: 'SNMPArch' is mentioned on line 101, but not defined == Missing Reference: 'SMIv1' is mentioned on line 106, but not defined == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 106, but not defined == Missing Reference: 'SNMPv1Traps' is mentioned on line 107, but not defined == Missing Reference: 'SMIv2' is mentioned on line 108, but not defined == Missing Reference: 'SNMPv2TC' is mentioned on line 108, but not defined == Missing Reference: 'SNMPv2Conf' is mentioned on line 109, but not defined == Missing Reference: 'SNMPv1' is mentioned on line 122, but not defined == Missing Reference: 'SNMPv2c' is mentioned on line 116, but not defined == Missing Reference: 'SNMPv2TM' is mentioned on line 118, but not defined == Missing Reference: 'SNMPv3MP' is mentioned on line 118, but not defined == Missing Reference: 'SNMPv3USM' is mentioned on line 118, but not defined == Missing Reference: 'SNMPv2PO' is mentioned on line 124, but not defined == Missing Reference: 'SNMPv3App' is mentioned on line 127, but not defined == Missing Reference: 'SNMPv3VACM' is mentioned on line 128, but not defined == Missing Reference: 'ConvSMIv2' is mentioned on line 261, but not defined == Unused Reference: 'MIBMPLS' is defined on line 1238, but no explicit reference was found in the text == Unused Reference: 'SecSNMP' is defined on line 1243, but no explicit reference was found in the text == Unused Reference: 'Cong' is defined on line 1247, but no explicit reference was found in the text == Unused Reference: 'RFC2012' is defined on line 1250, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 1254, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 1258, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 1262, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 1265, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1268, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1273, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1277, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 1281, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 1284, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 1288, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 1292, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 1300, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1304, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1311, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ConvIETF' -- Possible downref: Non-RFC (?) normative reference: ref. 'MIBMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'SecSNMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'Cong' ** Obsolete normative reference: RFC 2012 (Obsoleted by RFC 4022) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 20 errors (**), 0 flaws (~~), 37 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group J. Pastor 2 INTERNET-DRAFT M. Belinchon 3 Ericsson 5 expires in six months June 07,2000 7 Stream Control Transmission Protocol 8 Management Information Base using SMIv2 9 11 Status of This Memo 13 This document is an Internet-Draft and is in full conformance with all 14 provisions of Section 10 of RFC 2026. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, 16 and its working groups. Note that other groups may also distribute 17 working documents as Internet-Drafts. 19 The list of current Internet-Drafts can be accessed at 20 http://www.ietf.org/ietf/1id-abstracts.txt 22 The list of Internet-Draft Shadow Directories can be accessed at 23 http://www.ietf.org/shadow.html. 25 Abstract 27 The Stream Control Transmission Protocol (SCTP) a reliable transport 28 protocol operating on top of a connectionless packet network such as 29 IP, designed to transport PSTN signaling messages over the connectionless 30 packet network, but is capable of broader applications. 32 This memo defines the Management Information Base (MIB) module which 33 describes managed objects for implementation of the SCTP. 35 Open Issues 37 - Remove this section. 39 - Remove Revision History 41 - Decide under which object identifier branch of the SNMP tree, SCTP 42 will be placed (value obtained when submitted to the IETF editor). 44 - The MIB cannot be compiled because new textual convention for 45 Internet Network Address (draft-ops-endpoint-mib-08.txt) is work 46 in progress, not an RFC. 48 - Update references to drafts. 50 - Format draft accoring to the IETF rules. 52 Table of Contents 54 1. Introduction ................................................ 55 1.1 Abbreviations .............................................. 56 2. The SNMP framework .......................................... 57 3. Structure of the MIB ........................................ 58 3.1 Protocol General Variables ................................. 59 3.2 Statistics for Traffic Measurements ........................ 60 3.2.1 State-Related Statistics ................................. 61 3.2.2 Other Statistics ......................................... 62 3.3 Association Tables ......................................... 63 4. Definitions ................................................. 64 4.1 Conformance Information .................................... 65 4.1.1 Compliance Statements .................................... 66 4.1.2 Units of Conformance ..................................... 67 5. References .................................................. 68 6. Security Considerations ..................................... 69 7. Acknowledgements ............................................ 70 8. Authors' Addresses .......................................... 71 9. Revision History ............................................ 73 1. Introduction 75 This memo defines the Management Information Base (MIB) module which 76 describes managed objects for implementations of the SCTP. 78 The document starts with a brief description of the SNMP framework and 79 continues with the MIB explanation and security consideration among 80 others. 82 The managed objects in this MIB module have been based on RFC 2012: 83 "SNMPv2 Management Information Base for the Transmission Control 84 Protocol using SMIv2" [2]. 86 Terms related to the SCTP architecture are explained in [1]. Other 87 especific abbreviations are listed below. 89 1.1 Abbreviations 91 MIB - Management Information Base 92 SCTP - Stream Control Transmission Protocol 93 SMI - Structure of Management Information 94 SNMP - Simple Network Management Protocol 96 2. The SNMP Framework 98 The SNMP Management Framework presently consists of five major 99 components: 101 - An overall architecture, described in RFC 2271 [SNMPArch]. 103 - Mechanisms for describing and naming objects and events for the 104 purpose of management. The first version of this Structure of 105 Management Information (SMI) is called SMIv1 and described in 106 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 107 [SNMPv1Traps]. The second version, called SMIv2, is described 108 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 109 [SNMPv2Conf]. 111 - Message protocols for transferring management information. The 112 first version of the SNMP message protocol is called SNMPv1 113 and described in RFC 1157 [SNMPv1]. A second version of the 114 SNMP message protocol, which is not an Internet standards 115 track protocol, is called SNMPv2c and described in RFC 1901 116 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 117 message protocol is called SNMPv3 and described in RFC 1906 118 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 120 - Protocol operations for accessing management information. The 121 first set of protocol operations and associated PDU formats is 122 described in RFC 1157 [SNMPv1]. A second set of protocol 123 operations and associated PDU formats is described in RFC 1905 124 [SNMPv2PO]. 126 - A set of fundamental applications described in RFC 2273 127 [SNMPv3App] and the view-based access control mechanism 128 described in RFC 2575 [SNMPv3VACM]. 130 Managed objects are accessed via a virtual information store, 131 termed the Management Information Base or MIB. Objects in the MIB 132 are defined using the mechanisms defined in the SMI. This memo 133 specifies a MIB module that is compliant to the SMIv2. A MIB 134 conforming to the SMIv1 can be produced through the appropriate 135 translations. The resulting translated MIB must be semantically 136 equivalent, except where objects or events are omitted because no 137 translation is possible (use of Counter64). Some machine-readable 138 information in SMIv2 will be converted into textual descriptions 139 in SMIv1 during the translation process. However, this loss of 140 machine-readable information is not considered to change the 141 semantics of the MIB. 143 3. Structure of the MIB 145 The MIB is structured in the following way: 147 sctpMib 148 / \ 149 sctpObjects sctpConformance 150 / \ 151 sctpScalars sctpTables 153 where the following sections are described : 154 - sctpObjects, where all the SCTP objects are defined under 155 this branch. 157 - sctpScalars, where scalars values are placed. It is 158 divided in: 160 - General variables, where the main SCTP initial 161 variables are listed. 163 - Statistics for traffic measurements. 164 - state related 165 - other statistics 167 - sctpTables, to hold data from each association 168 together with the main statistics (per association or 169 transport address). Local and remote tables are included 170 into the general association table to allow multiples 171 IP addresses in order to support the multihome feature. 173 - sctpConformance, for the Unit of Conformance. 175 3.1 Scalars 177 3.1.1 Protocol General Variables 179 The first section of the MIB contains the general variables for the 180 SCTP protocol. Parameters as the RTO related variables, streams, timers 181 and heartbeat are described. Maximum and Minimum values can be found here. 183 SCTP RTO mechanism is the same as defined in TCP. So, the variable is 184 based on the one defined in RFC 2012. In SCTP protocol, only options 185 'other' and 'vanj' remain because SCTP protocol defines Van Jacobson's 186 algorithm as the one to be used to calculate RTO. 'Other' is left for 187 future use ('rsre' algorithm was eliminated because MIL-STD-1778 is 188 Cancelled-No Superseding Document according to the Military Standard 189 library and 'constant' option doesn't fulfill the SCTP protocol 190 description). 192 Cookies and heartbeat values have been added acording to the SCTP 193 protocol. 195 Timers for initialization and shutdown procedures have been included, 196 so the operator can check them and take the proper actions when 197 required. 199 Since SCTP is based on the transmission through streams, it's 200 interesting to know the maximum number of streams allowed in a given 201 association. The number of used streams will be negotiated at 202 initialization time. 204 3.1.2 Statistics for traffic Measurements 206 3.1.2.1 State-Related Statistics 208 These measures are considered important and are also based in the TCP 209 model, but adapted to the SCTP states. They allow to check how easy is 210 to init an association, how many association connection attempts become 211 established associations or how many associations terminate, amongst others. 213 3.1.2.2 Other Statistics 215 Other statistics are specified based on the data unit of SCTP: the chunk. 216 In this way, we have the whole picture of the bytes flow. 217 Also, there are statistics related to the SCTP packets. I.e., the number 218 of out of the blue packets received by the host (SCTP packets correctly formed, 219 i.e. rigth checksum, whose receiver is not able to identify the association to 220 which this packet belongs). And the number of SCTP packets received with an 221 invalid checksum. 223 3.2 Association Tables 225 The part of the MIB to define each association is structured 226 according to a expanded table. There is a main table, indexed by the 227 association identification. This main table contains information 228 common for a given association (association id, SCTP user ports, primary 229 address, negotiated number of inbound/outbound streams, retransmited 230 chunks and statistics). 231 This main table (for the association) contains two other tables : 233 a) Table for local IP address/-ess information: 234 This table stores information related to the local IP 235 address/-ess reserved for the association. It's indexed by 236 the IP address/-ess. 238 b) Table for remote IP address/-ess information: 239 This table stores information related to the remote IP 240 address/-ess reserved for the association. It's indexed by 241 the IP addresses. It includes statistics, heartbeat issues, 242 retransmissions counters and the state of the reachibility 243 of the referenced IP address. 245 Note that the IP address indexing the tables is valid for IPv4, IPv6 and 246 DNS [ConvIETF]. Therefore, IP address is defined by the Internet address 247 type and the value of the IP address, according to the Textual Conventions 248 for Internet Network Address. 250 However, DNS value is not being used to identify an IP address since it is 251 only valid during initialization (once init is finished, both sides only use 252 IP addresses). To keep the name of the remote peer, an entry has been created 253 (sctpAssocRemHostName) in the association table. When no DNS name is 254 provided by the remote endpoint at init time, this value will be NULL. 255 Otherwise, the received DNS name will be stored. 257 The variable RowStatus allows creating and deleting rows in the table. 258 Creation will be performed after the four handshake protocol at association 259 start up phase (when the association is considered established). Deletion 260 will be performed when the association is terminated either in a graceful 261 or ungraceful way [ConvSMIv2]. 263 sctpAssocTable 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 265 | sctpAssocId (index) / ... | 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | sctpAssocRemHostName \ ... | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | sctpAssocLocalSCTPPort / ... | 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | sctpAssocRemSCTPPort \ ... | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 | sctpAssocRemPrimaryAddressType / ... | 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 | sctpAssocRemAddressPrimary \ ... | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | sctpAssocState / ... | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 | sctpAssocInStreams \ ... | 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 281 | sctpAssocOutStreams / ... | 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 | sctpAssocT1expired \ ... | 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 | sctpAssocT2expired / ... | 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 | sctpAssocRtxChunks \ ... | 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | sctpAssocRowStatus / ... | 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 | sctpAssocLocalAddressTable \ | 292 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 293 | | sctpAssocLocalAddressIPType(index)\ ...| \ ... | 294 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 295 | | sctpAssocLocalAddressIP (index) \ ...| \ ... | 296 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 297 | | sctpAssocLocalAddressRowStatus \ ...| \ ... | 298 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | sctpAssocRemAddressTable \ | 301 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 302 | | sctpAssocRemAddressIPType (index) \ ...| \ | 303 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 304 | | sctpAssocRemAddressIP (index) \ ...| \ | 305 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 306 | | sctpAssocRemAddressStatus \ ...| \ | 307 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 308 | | sctpAssocRemAddressRTO \ ...| \ | 309 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 310 | | sctpAssocRemAddressHeartBeatFlag \ ...| \ | 311 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 312 | | sctpAssocRemAddressRetransCount \ ...| \ | 313 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 314 | | sctpAssocRemAddressPathMaxRx \ ...| \ | 315 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 316 | | sctpAssocRemAddressHBTimer \ ...| \ | 317 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 318 | | sctpAssocRemAddressT3expired \ ...| \ | 319 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 320 | | sctpAssocRemAddressRowStatus \ ...| \ | 321 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+ / | 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 Every entry is explained when defining the MIB. 326 4. Definitions 328 SCTP-MIB DEFINITIONS ::= BEGIN 330 IMPORTS 331 MODULE-IDENTITY, OBJECT-TYPE, INTEGER, Integer32, Unsigned32, 332 Counter32, Counter64, Gauge32, mib-2 333 FROM SNMPv2-SMI 334 MODULE-COMPLIANCE, OBJECT-GROUP 335 FROM SNMPv2-CONF 336 TEXTUAL-CONVENTION, RowStatus, InetAddressType, InetAddress 337 FROM SNMPv2-CONF 338 ; 340 sctpMIB MODULE-IDENTITY 341 LAST-UPDATED "0004300000Z" 342 ORGANIZATION "IETF SIGTRAN Working Group" 343 CONTACT-INFO 344 " Maria-Carmen Belinchon-Vergara 345 Jose-Javier Pastor-Balbas 347 Postal: Ericsson Espana S. A. 348 C/Retama 7 349 28045 Madrid 350 Spain 352 Phones: +34 91 339 3535 353 +34 91 339 3819 355 Emails: Maria.C.Belinchon@ericsson.com 356 J.Javier.Pastor@ericsson.com" 357 DESCRIPTION 358 "The MIB module for managing SCTP implementation." 359 REVISION "00007030000Z" 360 DESCRIPTION 361 "MIB module developed for the SIGTRAN IETF group. Based on SCTPv10" 362 ::= { xxxx } -- IANA needs to choose this value 363 -- when sent to the RFC editor 365 -- Top-level structure of the MIB 367 sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 } 368 sctpConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } 370 sctpScalars OBJECT IDENTIFIER ::= { sctpObjects 1 } 371 sctpTables OBJECT IDENTIFIER ::= { sctpObjects 2 } 373 -- PROTOCOL GENERAL VARIABLES 374 -- ************************** 376 sctpRtoAlgorithm OBJECT-TYPE 377 SYNTAX INTEGER { 378 other(1) -- Other new one. Future use 379 vanj(2), -- Van Jacobson's algorithm 381 } 382 MAX-ACCESS read-only 383 STATUS current 384 DESCRIPTION 385 "The algorithm used to determine the timeout value used for 386 retransmitting unacknowledged chunks" 387 ::= { sctpScalars 1 } 389 sctpRtoMin OBJECT-TYPE 390 SYNTAX Unsigned32 391 UNITS "milliseconds" 392 MAX-ACCESS read-write 393 STATUS current 394 DESCRIPTION 395 "The minimum value permitted by a SCTP implementation for the 396 retransmission timeout, measured in milliseconds. More 397 refined semantics for objects of this type depend upon the 398 algorithm used to determine the retransmission timeout. 399 Recommended value is 1000 milliseconds". 401 ::= { sctpScalars 2 } 403 sctpRtoMax OBJECT-TYPE 404 SYNTAX Unsigned32 405 UNITS "milliseconds" 406 MAX-ACCESS read-write 407 STATUS current 408 DESCRIPTION 409 "The maximum value permitted by a SCTP implementation for the 410 retransmission timeout, measured in milliseconds. More 411 refined semantics for objects of this type depend upon the 412 algorithm used to determine the retransmission timeout. 413 Recommended value is 60000 milliseconds". 414 ::= { sctpScalars 3 } 416 sctpRtoInitial OBJECT-TYPE 417 SYNTAX Unsigned32 418 UNITS "milliseconds" 419 MAX-ACCESS read-write 420 STATUS current 421 DESCRIPTION 422 "Initial value for the Retransmission timer. Recommended 423 value is 3000 milliseconds" 424 ::= { sctpScalars 4 } 426 sctpValCookieLife OBJECT-TYPE 427 SYNTAX Unsigned32 428 UNITS "milliseconds" 429 MAX-ACCESS read-write 430 STATUS current 431 DESCRIPTION 432 "Valid cookie life in the 4-way start-up handshake procedure. 433 Recommended value: 5000 milliseconds" 434 ::= { sctpScalars 5 } 436 sctpMaxInitRetr OBJECT-TYPE 437 SYNTAX Unsigned32 438 MAX-ACCESS read-write 439 STATUS current 440 DESCRIPTION 441 "The maximum number of retransmissions at the start-up phase. 442 Recommended value: 8 attempts" 443 ::= { sctpScalars 8 } 445 sctpInitialT1 OBJECT-TYPE 446 SYNTAX Unsigned32 447 UNITS "milliseconds" 448 MAX-ACCESS read-write 449 STATUS current 450 DESCRIPTION 451 "Initial value for the Start-up-T1 timer." 452 ::= { sctpScalars 9 } 454 sctpInitialT2 OBJECT-TYPE 455 SYNTAX Unsigned32 456 UNITS "milliseconds" 457 MAX-ACCESS read-write 458 STATUS current 459 DESCRIPTION 460 "Initial value for the Shutdown-T2 timer." 461 ::= { sctpScalars 10 } 463 sctpMaxInStreams OBJECT-TYPE 464 SYNTAX Unsigned32 465 MAX-ACCESS read-write 466 STATUS current 467 DESCRIPTION 468 "The maximum number of inbound streams that an SCTP 469 implementation allows. This value will be used to 470 negotiate at start-up phase the outbound streams number." 471 ::= { sctpScalars 11 } 473 sctpMaxAssoc OBJECT-TYPE 474 SYNTAX Unsigned32 475 MAX-ACCESS read-write 476 STATUS current 477 DESCRIPTION 478 "The maximum total number of associations that an SCTP 479 implementation allows including all possible hosts to connect to." 480 ::= { sctpScalars 12 } 482 -- STATE-RELATED STATISTICS 484 sctpCurrEstab OBJECT-TYPE 485 SYNTAX Counter32 486 MAX-ACCESS read-only 487 STATUS current 488 DESCRIPTION 489 "The number of SCTP associations for which the current state 490 is either ESTABLISHED or SHUTDOWN-RECEIVED." 491 ::= { sctpScalars 13 } 493 sctpActiveEstab OBJECT-TYPE 494 SYNTAX Counter32 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "The number of times that SCTP associations have made a direct 499 transition to the ESTABLISH state from the COOKIE-ECHOED state: 500 COOKIE-ECHOED -> ESTABLISHED. This upper layer has been the starter 501 of the communication." 502 ::= { sctpScalars 14 } 504 sctpPassiveEstab OBJECT-TYPE 505 SYNTAX Counter32 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "The number of times that SCTP associations have made a direct 510 transition to the ESTABLISHED state from the CLOSED state: 511 CLOSED -> ESTABLISHED. This means that the peer has 512 started the dialogue" 513 ::= { sctpScalars 15 } 515 sctpAborted OBJECT-TYPE 516 SYNTAX Counter32 517 MAX-ACCESS read-only 518 STATUS current 519 DESCRIPTION 520 "The number of times that SCTP associations have made a direct 521 transition to the CLOSED state from any state using the 522 primitive 'ABORT': AnyState --Abort--> CLOSED." 523 ::= { sctpScalars 16 } 525 sctpShutdowns OBJECT-TYPE 526 SYNTAX Counter32 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "The number of times that SCTP associations have made a direct 531 transition to the CLOSE state from either the SHUTDOWN- 532 SENT state or the SHUTDOWN-ACK-SENT state." 533 ::= { sctpScalars 17 } 535 -- OTHER LAYER STATISTICS 537 sctpStatAssocOutOfBlue OBJECT-TYPE 538 SYNTAX Counter64 539 MAX-ACCESS read-only 540 STATUS current 541 DESCRIPTION 542 "Number of out of the blue packets (SCTP packet correctly 543 formed -rigth checksum- but the receiver is not able to 544 identify the association to which this packet belongs) 545 received by the host." 546 ::= { sctpScalars 18 } 548 sctpStatSentChunks OBJECT-TYPE 549 SYNTAX Counter64 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "Number of SCTP chunks, control and data chunks, sent to the peers (no retransmissions 554 included)." 555 ::= { sctpScalars 19 } 557 sctpStatRecChunks OBJECT-TYPE 558 SYNTAX Counter64 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "Number of SCTP chunks, control and data chunks, received from the peers (no retransmissions 563 included)." 564 ::= { sctpScalars 20 } 566 sctpStatRetransChunks OBJECT-TYPE 567 SYNTAX Counter64 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "Number of SCTP chunks, control and data chunks, retransmited to the peers." 572 ::= { sctpScalars 21 } 574 sctpStatOutOfOrderSentChunks OBJECT-TYPE 575 SYNTAX Counter64 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 "Number of unordered chunks (chunks in which the U bit 580 is set to 1) sent to the peers." 581 ::= { sctpScalars 22 } 583 sctpStatOutOfOrderRecChunks OBJECT-TYPE 584 SYNTAX Counter64 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "Number of unordered chunks (chunks in which the U bit 589 is set to 1) received from the peers." 590 ::= { sctpScalars 23 } 592 sctpStatChecksumErrorCounter OBJECT-TYPE 593 SYNTAX Counter64 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "Number of SCTP packets received from the peers with an invalid 598 checksum." 599 ::= { sctpScalars 24 } 601 -- SCTP ASSOCIATION DESCRIPTION PARAMETERS 602 -- *************************************** 604 -- the SCTP Association TABLE 605 -- ************************** 607 -- The SCTP association table contains information about each 608 -- association that the local endpoint has established. 610 sctpAssocTable OBJECT-TYPE 611 SYNTAX SEQUENCE OF SctpAssocEntry 612 MAX-ACCESS not-accessible 613 STATUS current 614 DESCRIPTION 615 "A table containing SCTP association-specific information." 616 ::= { sctpTables 1 } 618 sctpAssocEntry OBJECT-TYPE 619 SYNTAX SctpAssocEntry 620 MAX-ACCESS not-accessible 621 STATUS current 622 DESCRIPTION 623 "General common variables and statistics for the whole 624 association" 625 INDEX { sctpAssocId } 626 ::= { sctpAssocTable 1 } 628 SctpAssocEntry ::= SEQUENCE { 629 sctpAssocId Unsigned32, 630 sctpAssocRemHostName OCTECT STRING, 631 sctpAssocLocalSCTPPort Integer32, 632 sctpAssocRemSCTPPort Integer32, 633 sctpAssocRemPrimaryAddressType InetAddressType, 634 sctpAssocRemPrimaryAddress InetAddress, 635 sctpAssocState INTEGER, 636 sctpAssocInStreams Unsigned32, 637 sctpAssocOutStreams Unsigned32, 638 sctpAssocMaxRetr Unsigned32, 639 sctpAssocT1expired Counter32, -- Statistic 640 sctpAssocT2expired Counter32, -- Statistic 641 sctpAssocRtxChunks Counter32, -- Statistic 642 sctpAssocRowStatus RowStatus 643 } 645 sctpAssocId OBJECT-TYPE 646 SYNTAX Unsigned32 647 MAX-ACCESS not-accessible 648 STATUS current 649 DESCRIPTION 650 "Association Identification. Value identifying the association 651 (tipically the Initiate Verification Tag)." 652 ::= { sctpAssocEntry 1 } 654 sctpAssocRemHostName OBJECT-TYPE 655 SYNTAX OCTECT STRING (SIZE(0..255)) 656 MAX-ACCESS read-create 657 STATUS current 658 DESCRIPTION 659 "Peer's DNS name. 660 If no DNS domain name was received at init time from the peer, 661 this entry will be meaningless, therefore it will store a NULL 662 value. 663 Otherwise, the remote host name received at init time will be 664 stored." 665 ::= { sctpAssocEntry 2 } 667 sctpAssocLocalSCTPPort OBJECT-TYPE 668 SYNTAX Integer32(0..65535) 669 MAX-ACCESS read-create 670 STATUS current 671 DESCRIPTION 672 "Local Port number used for this association." 673 ::= { sctpAssocEntry 3 } 675 sctpAssocRemSCTPPort OBJECT-TYPE 676 SYNTAX Integer32(0..65535) 677 MAX-ACCESS read-create 678 STATUS current 679 DESCRIPTION 680 "The destination SCTP port number used to communicate with 681 the remote peer for this association. Each value is defined 682 by the IANA organization." 683 ::= { sctpAssocEntry 4 } 685 sctpAssocRemPrimaryAddressType OBJECT-TYPE 686 SYNTAX InetAddressType 687 MAX-ACCESS read-create 688 STATUS current 689 DESCRIPTION 690 "Internet type of primary destination IP address. 691 unknown (0) An unknown address type. This value MUST 692 be used if the value of the corresponding 693 InetAddress object is a zero-length string. 694 It may also be used to indicate an IP address 695 which is not one of the formats defined below. 696 This value is used in this MIB for error conditions. 698 ipv4 (1) An IPv4 address as defined by the InetAddressIPv4 699 textual convention. 701 ipv6 (2) An IPv6 address as defined by the InetAddressIPv6 702 textual convention." 704 ::= { sctpAssocEntry 5 } 706 sctpAssocRemPrimaryAddress OBJECT-TYPE 707 SYNTAX InetAddress 708 MAX-ACCESS read-create 709 STATUS current 710 DESCRIPTION 711 "Primary destination IP address. 712 An InetAddress value is always interpreted within the 713 context of an InetAddressType value. 714 This value will be filled in after INIT or INIT ACK messages 715 have been received (when the primary path is selected by SCTP). 717 ::= { sctpAssocEntry 6 } 719 sctpAssocState OBJECT-TYPE 720 SYNTAX INTEGER { 721 closed(1), 722 cookieWait(2), 723 cookieEchoed(3), 724 established(4), 725 shutdownPending(5), 726 shutdownSent(6), 727 shutdownReceived(7), 728 shutdownAckSent(8), 729 deleteTCB(9) 730 } 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "The state of this SCTP association. 736 As in TCP, the only value which may be set by a management 737 station is deleteTCB. Accordingly, it is appropriate for 738 an agent to return a 'badValue' response if a management 739 station attempts to set this object to any other value. 741 If a management station sets this object to the value 742 deleteTCB(9), then this has the effect of deleting the TCB 743 (as defined in SCTP) of the corresponding association on 744 the managed node, resulting in immediate termination of the 745 association. 747 As an implementation-specific option, an ABORT chunk may be 748 sent from the managed node to the other SCTP endpoint." 749 ::= { sctpAssocEntry 7 } 751 sctpAssocInStreams OBJECT-TYPE 752 SYNTAX Unsigned32 753 MAX-ACCESS read-create 754 STATUS current 755 DESCRIPTION 756 "Inbound Streams according to the negotiation at association 757 start up. This parameter has to be read-only by the manager. 759 If the local application acts as the server, the sctpAssoc table 760 will be created when the COOKIE chunk arrives, at the same 761 time the association becomes ESTABLISHED. 763 If the local node acts as the client, this table will be 764 created just before sending the INIT chunk. At that time, 765 there is no fixed value for this parameter as the negotiation 766 has not taken part. Initial value is set and modified locally 767 to the negotiated one at the same time the association becomes 768 ESTABLISHED or when the INIT_ACK chunk is received." 770 ::= { sctpAssocEntry 8 } 772 sctpAssocOutStreams OBJECT-TYPE 773 SYNTAX Unsigned32 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "Outbound Streams according to the negotiation at association 778 start up. This parameter has to be read-only by the manager. 780 When the local application acts as the server, the sctpAssoc table 781 will be created when the COOKIE chunk arrives, at the same 782 time the association becomes ESTABLISHED. 784 If the local node acts as the client, this table will be 785 created just before sending the INIT chunk. At that time, 786 there is no fixed value for this parameter as the negotiation 787 has not taken part. Initial value is set and modified locally 788 to the negotiated one at the same time the association becomes 789 ESTABLISHED or when the INIT_ACK chunk is received." 791 ::= { sctpAssocEntry 9 } 793 sctpAssocMaxRetr OBJECT-TYPE 794 SYNTAX Unsigned32 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 798 "The maximum number of retransmissions for data sending. 799 Recommended value: 10 attempts. 801 This value is specific for each association and the upper layer 802 can be able to change it calling the appropiates primitives." 803 ::= { sctpAssocEntry 10 } 805 -- Association Statistics 807 sctpAssocT1expired OBJECT-TYPE 808 SYNTAX Counter32 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION 812 "Number of times that T1 timer expired (timer for sending 813 INIT message and receiving an acknowledgment)." 814 ::= { sctpAssocEntry 11} 816 sctpAssocT2expired OBJECT-TYPE 817 SYNTAX Counter32 818 MAX-ACCESS read-only 819 STATUS current 820 DESCRIPTION 821 "Number of times that T2 timer expired (shutdown timer)." 822 ::= { sctpAssocEntry 12} 824 sctpAssocRtxChunks OBJECT-TYPE 825 SYNTAX Counter32 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "Number of control and data chunks retransmited to the peer 830 in the current association." 831 ::= { sctpAssocEntry 13} 833 sctpAssocRowStatus OBJECT-TYPE 834 SYNTAX RowStatus 835 MAX-ACCESS read-create 836 STATUS current 837 DESCRIPTION 838 "An object that allows entries in this table to be created and 839 deleted using the RowStatus convention. 840 A row in this table will be created after the endpoint sends or 841 receives the COOKIE_ECHOED message, i.e., when the initialization 842 start-up phase is completed (the association is fully 843 established).The creation of this row implies the creation 844 of at least another row (depending on the number of local and 845 remote addresses) in the tables sctpAssocLocalAddressTable 846 and sctpAssocRemAddressTable. 847 A row is deleted in sctpAssocTable when an association turns 848 down. The deletion of a row in sctpAssocTable implies the 849 deletion of the tables related to this asociation 850 (sctpAssocLocalAddressTable and sctpAssocRemAddressTable). 851 Also, a row is deleted in sctpAssocTable when a set operation 852 is received from the manager with destroy option." 853 ::= { sctpAssocEntry 14 } 855 -- Expanded tables: Including Multihome feature 857 -- Local Address TABLE 858 -- ******************* 860 sctpAssocLocalAddressTable OBJECT-TYPE 861 SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry 862 MAX-ACCESS not-accessible 863 STATUS current 864 DESCRIPTION 865 "Expanded table of sctpAssocTable based on the AssocId index. 866 It shows different interesting data for each local 867 address which takes part in this association." 868 ::= { sctpTables 2 } 870 sctpAssocLocalAddressEntry OBJECT-TYPE 871 SYNTAX SctpAssocLocalAddressEntry 872 MAX-ACCESS not-accessible 873 STATUS current 874 DESCRIPTION 875 "Local information about the available addresses." 876 INDEX { sctpAssocId, -- shared index 877 sctpAssocLocalAddressIPType, 878 sctpAssocLocalAddressIP } 879 ::= { sctpAssocLocalAddressTable 1 } 881 SctpAssocLocalAddressEntry ::= SEQUENCE { 882 sctpAssocLocalAddressIPType InetAddressType, 883 sctpAssocLocalAddressIP InetAddress, 884 sctpAssocLocalAddressRowStatus RowStatus 885 } 887 sctpAssocLocalAddressIPType OBJECT-TYPE 888 SYNTAX InetAddressType 889 MAX-ACCESS not-accessible 890 STATUS current 891 DESCRIPTION 892 "The type of a local IP address available for this association. 893 unknown (0) An unknown address type. This value MUST 894 be used if the value of the corresponding 895 InetAddress object is a zero-length string. 896 It may also be used to indicate an IP address 897 which is not one of the formats defined below. 898 This value is used in this MIB for error conditions. 900 ipv4 (1) An IPv4 address as defined by the InetAddressIPv4 901 textual convention. 903 ipv6 (2) An IPv6 address as defined by the InetAddressIPv6 904 textual convention." 906 ::= { sctpAssocLocalAddressEntry 1 } 908 sctpAssocLocalAddressIP OBJECT-TYPE 909 SYNTAX InetAddress 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "The value of a local IP address available for this association. 914 An InetAddress value is always interpreted within the 915 context of an InetAddressType value 916 If SCTP are using DNS names, the mapping to IP address/-ess 917 will be done at reception of INIT or INIT_ACK messages." 918 ::= { sctpAssocLocalAddressEntry 2 } 920 sctpAssocLocalAddressRowStatus OBJECT-TYPE 921 SYNTAX RowStatus 922 MAX-ACCESS read-create 923 STATUS current 924 DESCRIPTION 925 "An object that allows entries in this table to be created and 926 deleted using the RowStatus convention. 927 A row in this table will be created per local IP address to be 928 used in this association. The creation takes part when 929 a new row in the sctpAssocTable is created. 930 A row in this table will be deleted per local IP address used 931 in this association when the corresponding row in sctpAssocTable 932 is deleted." 933 ::= { sctpAssocLocalAddressEntry 3 } 935 -- Remote Addresses TABLE 936 -- ********************** 938 sctpAssocRemAddressTable OBJECT-TYPE 939 SYNTAX SEQUENCE OF SctpAssocRemAddressEntry 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "Expanded table of sctpAssocTable based on the AssocId index 944 It shows different interesting data for each remote peer IP 945 address which is used in this association." 946 ::= { sctpTables 3 } 948 sctpAssocRemAddressEntry OBJECT-TYPE 949 SYNTAX SctpAssocRemAddressEntry 950 MAX-ACCESS not-accessible 951 STATUS current 952 DESCRIPTION 953 "Information about the remote IP address most important variables" 954 INDEX { sctpAssocId, -- shared index 955 sctpAssocRemAddressIPType, 956 sctpAssocRemAddressIP } 957 ::= { sctpAssocRemAddressTable 1 } 959 SctpAssocRemAddressEntry ::= SEQUENCE { 960 sctpAssocRemAddressIPType InetAddressType, 961 sctpAssocRemAddressIP InetAddress, 962 sctpAssocRemAddressStatus INTEGER, 963 sctpAssocRemAddressRTO Unsigned32, 964 sctpAssocRemAddressHeartBeatFlag INTEGER, 965 sctpAssocRemAddressHBTimer Unsigned32, 966 sctpAssocRemAddressRetransCount Counter64, 967 sctpAssocRemAddressMaxPathRetrans Counter64, 968 sctpAssocRemAddressRowStatus RowStatus 969 } 971 sctpAssocRemAddressIPType OBJECT-TYPE 972 SYNTAX InetAddressType 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "The type of a remote IP address available for this association. 977 unknown (0) An unknown address type. This value MUST 978 be used if the value of the corresponding 979 InetAddress object is a zero-length string. 980 It may also be used to indicate an IP address 981 which is not one of the formats defined below. 982 This value is used in this MIB for error conditions. 984 ipv4 (1) An IPv4 address as defined by the InetAddressIPv4 985 textual convention. 987 ipv6 (2) An IPv6 address as defined by the InetAddressIPv6 988 textual convention." 989 ::= { sctpAssocRemAddressEntry 1 } 991 sctpAssocRemAddressIP OBJECT-TYPE 992 SYNTAX InetAddress 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "The value of a remote IP address available for this association. 997 An InetAddress value is always interpreted within the 998 context of an InetAddressType value." 999 ::= { sctpAssocRemAddressEntry 2 } 1001 sctpAssocRemAddressStatus OBJECT-TYPE 1002 SYNTAX INTEGER { 1003 active(0), 1004 inactive(1) 1005 } 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The current status of the remote transport address. Active means 1010 that the threshold of no anwer received from this IP address has 1011 not been reached. Inactive means that either no heartbeat was 1012 received from this address, or any other message, reaching 1013 the threshold defined by the protocol." 1014 ::= { sctpAssocRemAddressEntry 3 } 1016 sctpAssocRemAddressRTO OBJECT-TYPE -- T3-Rtx Timer 1017 SYNTAX Unsigned32 1018 UNITS "milliseconds" 1019 MAX-ACCESS read-only 1020 STATUS current 1021 DESCRIPTION 1022 "The current Retransmision Time-Out. Timer T3 as defined 1023 in the protocol SCTP." 1024 ::= { sctpAssocRemAddressEntry 4 } 1026 sctpAssocRemAddressHeartBeatFlag OBJECT-TYPE 1027 SYNTAX INTEGER { 1028 active(0), 1029 inactive(1) 1030 } 1031 MAX-ACCESS read-write 1032 STATUS current 1033 DESCRIPTION 1034 "The optional Heartbeat associated to one destination 1035 transport address could be actived or not (value equal to 1036 1 or 0, respectively). 1038 An active destination transport address is is a transport 1039 address on a peer endpoint which a transmitting endpoint 1040 considers available for receiving user messages, as it is 1041 described in [sctp]." 1042 ::= { sctpAssocRemAddressEntry 5 } 1044 sctpAssocRemAddressHBTimer OBJECT-TYPE 1045 SYNTAX Unsigned32 1046 UNITS "milliseconds" 1047 MAX-ACCESS read-only 1048 STATUS current 1049 DESCRIPTION 1050 "The current heartbeat time-out. The initial default value 1051 is RTO. It may be change by the user in a per address basis." 1052 ::= { sctpAssocRemAddressEntry 6 } 1054 -- Remote Address Statistics 1056 sctpAssocRemAddressRetransCount OBJECT-TYPE 1057 SYNTAX Counter64 1058 MAX-ACCESS read-write 1059 STATUS current 1060 DESCRIPTION 1061 "Number of retransmissions as defined in [sctp]." 1062 ::= { sctpAssocRemAddressEntry 7 } 1064 sctpAssocRemAddressMaxPathRetrans OBJECT-TYPE 1065 SYNTAX Unsigned32 1066 MAX-ACCESS read-write 1067 STATUS current 1068 DESCRIPTION 1069 "Maximum number of retransmissions allowed to a remote IP 1070 address before it is considered inactive, as defined in 1071 [sctp]." 1072 ::= { sctpAssocRemAddressEntry 8 } 1074 sctpAssocRemAddressRowStatus OBJECT-TYPE 1075 SYNTAX RowStatus 1076 MAX-ACCESS read-create 1077 STATUS current 1078 DESCRIPTION 1079 "An object that allows entries in this table to be created and 1080 deleted using the RowStatus conventionn. 1081 A row in this table will be created per remote IP address 1082 defined for the association when a row in sctpAssocTable 1083 is created. 1084 A row in this table will be deleted per remote IP address 1085 defined for the association when a row in sctpAssocTable 1086 is deleted." 1087 ::= { sctpAssocRemAddressEntry 9 } 1089 -- 4.1 Conformance Information 1091 sctpMIBGroups OBJECT IDENTIFIER ::= { sctpMIBConformance 1 } 1092 sctpMIBCompliances OBJECT IDENTIFIER ::= { sctpMIBConformance 2 } 1094 -- 4.1.1 Compliance Statements 1096 sctpMIBCompliance MODULE-COMPLIANCE 1097 STATUS current 1098 DESCRIPTION 1099 "The compliance statement for SNMPv3 entities which 1100 implement SCTP." 1101 MODULE -- this module 1102 MANDATORY-GROUPS { sctpGeneralVariablesGroup 1103 sctpAssocTablesVariablesGroup 1104 } 1105 GROUP sctpStateStatGroup 1106 DESCRIPTION 1107 "The sctp group of objects to control state changes in the SCTP 1108 protocol." 1110 GROUP sctpOtherStatGroup 1111 DESCRIPTION 1112 "The sctp group of objects providing for management of SCTP 1113 general statistics." 1115 GROUP sctpAssocStatGroup 1116 DESCRIPTION 1117 "The sctp group of objects to manage SCTP statistics related 1118 to the remote endpoint." 1120 OBJECT sctpAssocRemPrimaryAddressType OBJECT-TYPE 1121 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1122 DESCRIPTION 1123 "It is only required to have IPv4 and IPv6 addresses to be 1124 stored since the use of the host names is limited to first 1125 stage, when the association is being established." 1127 OBJECT sctpAssocRemPrimaryAddress OBJECT-TYPE 1128 SYNTAX InetAddress (SIZE(4|16)) 1129 DESCRIPTION 1130 "It is only required to support OPv4 and globally unique IPv6 1131 addresses." 1133 OBJECT sctpAssocLocalAddressIPType OBJECT-TYPE 1134 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1135 DESCRIPTION 1136 "It is only required to have IPv4 and IPv6 addresses to be 1137 stored since the use of the host names is limited to first 1138 stage, when the association is being established." 1140 OBJECT sctpAssocLocalAddressIP OBJECT-TYPE 1141 SYNTAX InetAddress (SIZE(4|16)) 1142 DESCRIPTION 1143 "It is only required to support IPv4 and globally unique IPv6 1144 addresses." 1146 OBJECT sctpAssocRemAddressIPType OBJECT-TYPE 1147 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1148 DESCRIPTION 1149 "It is only required to have IPv4 and IPv6 addresses to be 1150 stored since the use of the host names is limited to first 1151 stage, when the association is being established." 1153 OBJECT sctpAssocRemAddressIP OBJECT-TYPE 1154 SYNTAX InetAddress (SIZE(4|16)) 1155 DESCRIPTION 1156 "It is only required to support IPv4 and globally unique IPv6 1157 addresses." 1159 ::= { sctpMIBCompliances 1 } 1161 -- 4.1.2 Units of conformance 1163 sctpGeneralVariablesGroup OBJECT-GROUP 1164 OBJECTS { sctpRtoAlgorithm, sctpRtoMin, sctpRtoMax, sctpRtoInitial, 1165 sctpValCookieLife, sctpMaxInitRetr, sctpInitialT1, sctpInitialT2, 1166 sctpMaxInStreams, sctpMaxAssoc 1167 } 1168 STATUS current 1169 DESCRIPTION 1170 "The sctp group of objects providing for management of SCTP 1171 entities. Common parameters for the protocol." 1172 ::= { sctpMIBGroups 1 } 1174 sctpStateStatGroup OBJECT-GROUP 1175 OBJECTS { sctpCurrEstab, sctpActiveEstab, sctpPassiveEstab, sctpAborted, 1176 sctpShutdowns 1177 } 1178 STATUS current 1179 DESCRIPTION 1180 "The sctp group of objects to control state changes in the SCTP 1181 protocol." 1182 ::= { sctpMIBGroups 2 } 1184 sctpOtherStatGroup OBJECT-GROUP 1185 OBJECTS { sctpAssocOutOfBlue, sctpStatSentChunks, sctpStatRecChunks, 1186 sctpStatRetransChunks, sctpStatOutOfOrderSentChunks, 1187 sctpStatOutOfOrderRecChunks,sctpStatChecksumErrorCounter} 1188 STATUS current 1189 DESCRIPTION 1190 "The sctp group of objects providing for management of SCTP 1191 general statistics." 1192 ::= { sctpMIBGroups 3 } 1194 sctpAssocTablesVariablesGroup OBJECT-GROUP 1195 OBJECTS { sctpAssocId, sctpAssocRemHostName, sctpAssocLocalSCTPPort, 1196 sctpAssocRemSCTPPort, sctpAssocRemPrimaryAddressType, 1197 sctpAssocRemPrimaryAddress, sctpAssocState, 1198 sctpAssocInStreams, sctpAssocOutStreams, 1199 sctpAssocMaxRetr,sctpAssocT1expired, sctpAssocT2expired, 1200 sctpAssocRtxChunks, sctpAssocRowStatus, 1201 sctpAssocLocalAddressIPType,sctpAssocLocalAddressIP, 1202 sctpAssocLocalAddressRowStatus, 1203 sctpAssocRemAddressIPType, sctpAssocRemAddressIP, 1204 sctpAssocRemAddressStatus, sctpAssocRemAddressRTO, 1205 sctpAssocRemAddressHeartBeatFlag, 1206 sctpAssocRemAddressHBTimer, 1207 sctpAssocRemAddressRowStatus, 1208 } 1209 STATUS current 1210 DESCRIPTION 1211 "The sctp group of objects to manage specific local and remote 1212 SCTP variables (local and remote tables)." 1213 ::= { sctpMIBGroups 4 } 1215 sctpAssocStatGroup OBJECT-GROUP 1216 OBJECTS { sctpAssocRemAddressRetransCount, 1217 sctpAssocRemAddressMaxPathRetrans, 1218 } 1219 STATUS current 1220 DESCRIPTION 1221 "The sctp group of objects to manage SCTP statistics related 1222 to the remote endpoint." 1223 ::= { sctpMIBGroups 5 } 1225 END 1227 5. References 1229 [sctp] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J. 1230 Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, 1231 V. Paxson, "Stream Control Transmission Protocol", 1232 Internet Draft , 1233 February 2000. 1235 [ConvIETF] Textual Conventions for Internet Network Addresses , 1236 Internet Draft , April 2000. 1238 [MIBMPLS] Cucchiara et al. "Definnitions of Managed Objects for the 1239 Multiprotocol Label Switching, Label Distribution Protocol 1240 (LDP)", Internet Draf , 1241 January 2000. 1243 [SecSNMP] Stallings, W., "SNMP3: A Security Enhancement for SNMP", 1244 IEEE Communication Surveys, Forth quarter 1998, Vol. 1 1245 No. 1. 1247 [Cong] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1248 1988, Stanford, California. 1250 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1251 Transmission Control Protocol using SMIv2", RFC 2012, 1252 November 1996. 1254 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1255 for Describing SNMP Management Frameworks", RFC 2571, April 1256 1999. 1258 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1259 of Management Information for TCP/IP-based Internets", STD 1260 16, RFC 1155, May 1990. 1262 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1263 16, RFC 1212, March 1991. 1265 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1266 SNMP", RFC 1215, March 1991. 1268 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1269 Rose, M., and S. Waldbusser, "Structure of Management 1270 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1271 1999. 1273 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1274 Rose, M., and S. Waldbusser, "Textual Conventions for 1275 SMIv2", STD 58, RFC 2579, April 1999. 1277 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1278 Rose, M., and S. Waldbusser, "Conformance Statements for 1279 SMIv2", STD 58, RFC 2580, April 1999. 1281 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1282 Network Management Protocol", STD 15, RFC 1157, May 1990. 1284 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1285 "Introduction to Community-based SNMPv2", RFC 1901, January 1286 1996. 1288 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1289 "Transport Mappings for Version 2 of the Simple Network 1290 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1292 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1293 Processing and Dispatching for the Simple Network Management 1294 Protocol (SNMP)", RFC 2572, April 1999. 1296 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1297 (USM) for version 3 of the Simple Network Management 1298 Protocol (SNMPv3)", RFC 2574, April 1999. 1300 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1301 "Protocol Operations for Version 2 of the Simple Network 1302 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1304 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1305 RFC 2573, April 1999. 1307 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1308 Access Control Model (VACM) for the Simple Network 1309 Management Protocol (SNMP)", RFC 2575, April 1999. 1311 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1312 "Introduction to Version 3 of the Internet-standard Network 1313 Management Framework", RFC 2570, April 1999. 1315 6. Security Consideration 1317 There are a number of management objects defined in this MIB that have 1318 a MAX-ACCESS clause of read-write and/or read-create. Such objects may 1319 be considered sensitive or vulnerable in some network environments. The 1320 support for SET operations in a non-secure environment without proper 1321 protection can have a negative effect on network operations. 1323 It is thus important to control even GET access to these objects and 1324 possibly to even encrypt the values of these object when sending them 1325 over the network via SNMP. Not all versions of SNMP provide features 1326 for such a secure environment. 1328 SNMPv1 by itself is not a secure environment. Even if security measures 1329 are taken (e.g., using IPSEC), there is no per-user control as to who 1330 (once an IPSEC association is established between hosts) is allowed to 1331 GET or SET the objects in this MIB 1333 It is recommended that the implementers consider the security features 1334 as provided by the SNMPv3 framework. Specifically, the use of the 1335 User-based Security Model RFC 2574 [RFC2574] and the View-based Access 1336 Control Model RFC 2575 [RFC2575] is recommended. 1338 It is then a customer/user responsibility to ensure that the SNMP entity 1339 giving access to an instance of this MIB, is properly configured to give 1340 access to the objects only to those principals (users) that have 1341 legitimate rights to indeed GET or SET (change/create/delete) them. 1343 7. Acknowledgments 1345 The authors wish to thank David Partain for his invaluable comments. 1347 8. Authors' Addresses 1349 Javier Pastor Tel: +34-91-339-3819 1350 Ericsson Espana S. A. EMail: J.Javier.Pastor@ericsson.com 1351 Network Communication Services 1352 Retama 7, 5th floor 1353 Madrid, 28045 1354 Spain 1356 Maria-Carmen Belinchon Tel: +34-91-339-3535 1357 Ericsson Espana S. A. EMail: Maria.C.Belinchon@ericsson.com 1358 Network Communication Services 1359 Retama 7, 5th floor 1360 Madrid, 28045 1361 Spain 1363 9. Revision History 1365 9.1 Changes from 1367 o Open issues updated 1369 o Section 2: Reference to RFC227x changed to RFC257x 1371 o Section 4: Inside the sctpRtoAlgorithm definition has been put "other" first 1372 rather than last. That way, it won't end up in the middle of things when new 1373 enumerations are added later. 1375 9.2 Changes from 1377 o Change of "Simple" word to "Stream" word in SCTP acronyms 1379 o Version of the MIB based on SCTPv10 1381 o Section 2: Update SNMP Framework to include the standard explanation 1383 o New Structure for the MIB: 1384 sctpMIB 1385 \- sctpObjects 1386 \- sctpScalars 1387 \- sctpTables 1388 \- sctpConformance 1390 o Section 4.1.2: Unit of Conformance updated (functional structure). 1392 o MAX-ACCESS clauses reviewed 1394 o The general statistics has been re-ordered, placed before the tables. 1396 o In SMIv2, indexes should be not-accessible (= the object type is a 1397 column in a table used as index and may not be used as an operand in any 1398 operation != SMIv1) (pp109-110 in []) 1400 o IPv6 compatible: 1401 - Change of Primary/Local/Remote addresses 1402 - PENDING: check "MODULE-COMPLIANCE" 1404 o Row Status included in AssocTable, AssocLocal and AssocRem to create, 1405 modify and delete rows in the tables. 1407 o SCTP general statistics changed from Counter32 to Counter64 since it supports 1408 more data changes. 1410 o sctpCurrEstab ("State-related variables and statistics" section) variable 1411 changed from Gauge32 to Counter32. 1413 o sctpAssocRemAddressT1expired and sctpAssocRemAddressT2expired have been 1414 removed from the remote table and added in the general association data 1415 since they are variables per association (not per IP address). 1417 o sctpAssocDropDatag statistic has been removed from the general association 1418 statistics since it had an ambiguous meaning. 1420 o Explained the meaning of the unordered chunks (chunks in which the U bit is 1421 set to 1) in sctpStatOutOfOrderSentChunks and sctpStatOutOfOrderRecChunks. 1423 o Added sctpChecksumErrorCounter to collect information about wrong checksums 1424 received from the peer. 1426 o Specify that sctpStatSentChunks and sctpStatRecChunks does not contain 1427 retransmission chunks. 1429 o Reword the Security Considerations chapter pointing out that IPsec does 1430 not secure the network but it provides end-to-end security over a network. 1432 o sctpAssocRemAddressRtxChunks replaced as a variable per association, 1433 meaning the number of chunks retransmited to the peer in the current 1434 association. 1436 o sctpHeartBeatMisses and sctpMaxRetr have been replaced from the general 1437 SCTP statistics to the remote IP address table (sctpHeartBeatMisses) and 1438 in the association table (sctpMaxRetr). 1440 o Specify that the retransmissions in the general SCTP statistics include 1441 control plus data chunks. 1443 o Included heartbeat timer for remote IP address. 1445 o Removed sctpAssocRemAddressHeartBeatMisses variable from the remote IP 1446 address table. 1448 o Removed sctpAssocRemAddressT3expired variable from the remote IP 1449 address table. 1451 o Updated variables to the new SCTP states defined in v10.