idnits 2.17.1 draft-ietf-sigtran-sctp-mib-03.txt: -(1696): 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 2 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 36 longer pages, the longest (page 2) being 59 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 172 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([SIGAS]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 4 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 176 has weird spacing: '...Scalars sctp...' == Line 350 has weird spacing: '...ossible to cr...' == Line 613 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.) -- The document date (February 20, 2001) is 8465 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 2012' is mentioned on line 97, but not defined ** Obsolete undefined reference: RFC 2012 (Obsoleted by RFC 4022) == Missing Reference: 'RFC 2452' is mentioned on line 98, but not defined ** Obsolete undefined reference: RFC 2452 (Obsoleted by RFC 4022, RFC 8096) -- Looks like a reference, but probably isn't: '1' on line 100 == Missing Reference: 'SNMPArch' is mentioned on line 127, but not defined == Missing Reference: 'SMIv1' is mentioned on line 132, but not defined == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 132, but not defined == Missing Reference: 'SNMPv1Traps' is mentioned on line 133, but not defined == Missing Reference: 'SMIv2' is mentioned on line 134, but not defined == Missing Reference: 'SNMPv2TC' is mentioned on line 134, but not defined == Missing Reference: 'SNMPv2Conf' is mentioned on line 135, but not defined == Missing Reference: 'SNMPv1' is mentioned on line 148, but not defined == Missing Reference: 'SNMPv2c' is mentioned on line 141, but not defined == Missing Reference: 'SNMPv2TM' is mentioned on line 143, but not defined == Missing Reference: 'SNMPv3MP' is mentioned on line 144, but not defined == Missing Reference: 'SNMPv3USM' is mentioned on line 144, but not defined == Missing Reference: 'SNMPv2PO' is mentioned on line 150, but not defined == Missing Reference: 'SNMPv3App' is mentioned on line 153, but not defined == Missing Reference: 'SNMPv3VACM' is mentioned on line 154, but not defined == Missing Reference: 'SCTP' is mentioned on line 1151, but not defined == Unused Reference: 'MIBMPLS' is defined on line 1403, but no explicit reference was found in the text == Unused Reference: 'SecSNMP' is defined on line 1408, but no explicit reference was found in the text == Unused Reference: 'Cong' is defined on line 1411, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 1418, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 1422, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 1426, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 1429, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1432, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1436, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1440, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 1444, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 1447, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 1451, but no explicit reference was found in the text == Unused Reference: 'RFC2452' is defined on line 1455, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 1458, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 1466, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1470, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1477, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'SIGAS' -- 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 2452 (Obsoleted by RFC 4022, RFC 8096) ** 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) ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) Summary: 23 errors (**), 0 flaws (~~), 43 warnings (==), 7 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: August 2001 Ericsson 6 February 20, 2001 8 Stream Control Transmission Protocol 9 Management Information Base using SMIv2 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 will be placed (value obtained when submitted to the IETF 55 editor). 57 - Update references to drafts [SIGAS]. 59 TABLE OF CONTENTS 61 Open Issues.........................................................2 62 1. Introduction.....................................................3 63 1.1 Abbreviations...................................................3 64 2. The SNMP Framework...............................................3 65 3. Structure of the MIB.............................................4 66 3.1 Objects........................................................5 67 3.1.1 Scalars......................................................5 68 3.1.2 MIB Tables...................................................6 69 3.1.2.1 Association Table..........................................6 70 3.1.2.1.1 Local IP addresses Table..................................8 71 3.1.2.1.2 Remote IP addresses Table.................................8 72 3.2 Conformance.....................................................9 73 3.2.1 Groups........................................................9 74 3.2.2 Compliance....................................................9 75 4. Definitions......................................................9 76 5. References.....................................................30 77 6. Security Consideration..........................................32 78 7. Acknowledgments.................................................33 79 8. Authors' Addresses..............................................33 80 9. Revision History................................................33 81 9.1 Changes from ........................33 82 9.2 Changes from ..............33 83 9.3 Changes from ..............35 84 9.3 Changes from ..............37 86 1. Introduction 88 This memo defines the Management Information Base (MIB) module which 89 describes managed objects for implementations of the SCTP. 91 The document starts with a brief description of the SNMP framework 92 and continues with the MIB explanation and security consideration 93 among others. 95 The managed objects in this MIB module have been based on RFC 2012: 96 "SNMPv2 Management Information Base for the Transmission Control 97 Protocol using SMIv2" [RFC 2012] and "IP Version 6 Management 98 Information Base for the Transmission Control Protocol" [RFC 2452]. 100 Terms related to the SCTP architecture are explained in [1]. Other 101 specific abbreviations are listed below. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119 [RFC2119]. 107 1.1 Abbreviations 109 DNS - Domain Name System 110 IANA - Internet Assigned Numbers Authority 111 IETF - Internet Engineering Task Force 112 IP - Internet Protocol 113 MIB - Management Information Base 114 RFC - Request For Comment 115 RTO - Retransmission Time Out 116 SCTP - Stream Control Transmission Protocol 117 SMI - Structure of Management Information 118 SNMP - Simple Network Management Protocol 119 TCB - Transmission Control Block 120 TCP - Transmission Control Protocol 122 2. The SNMP Framework 124 The SNMP Management Framework presently consists of five major 125 components: 127 - An overall architecture, described in RFC 2271 [SNMPArch]. 129 - Mechanisms for describing and naming objects and events for the 130 purpose of management. The first version of this Structure of 131 Management Information (SMI) is called SMIv1 and described in 132 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 133 [SNMPv1Traps]. The second version, called SMIv2, is described 134 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 135 [SNMPv2Conf]. 137 - Message protocols for transferring management information. The 138 first version of the SNMP message protocol is called SNMPv1 nd 139 described in RFC 1157 [SNMPv1]. A second version of the SNMP 140 message protocol, which is not an Internet standards track 141 protocol, is called SNMPv2c and described in RFC 1901 [SNMPv2c] 142 and RFC 1906 [SNMPv2TM]. The third version of the message 143 protocol is called SNMPv3 and described in RFC 1906 [SNMPv2TM], 144 RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 146 - Protocol operations for accessing management information. The 147 first set of protocol operations and associated PDU formats is 148 described in RFC 1157 [SNMPv1]. A second set of protocol 149 operations and associated PDU formats is described in RFC 1905 150 [SNMPv2PO]. 152 - A set of fundamental applications described in RFC 2273 153 [SNMPv3App] and the view-based access control mechanism 154 described in RFC 2575 [SNMPv3VACM]. 156 Managed objects are accessed via a virtual information store, termed 157 the Management Information Base or MIB. Objects in the MIB are 158 defined using the mechanisms defined in the SMI. This memo specifies 159 a MIB module that is compliant to the SMIv2. A MIB conforming to the 160 SMIv1 can be produced through the appropriate translations. The 161 resulting translated MIB must be semantically equivalent, except 162 where objects or events are omitted because no translation is 163 possible (use of Counter64). Some machine-readable information in 164 SMIv2 will be converted into textual descriptions in SMIv1 during the 165 translation process. However, this loss of machine-readable 166 information is not considered to change the semantics of the MIB. 168 3. Structure of the MIB 170 The MIB is structured in the following way: 172 sctpMib 173 / \ 174 sctpObjects sctpConformance 175 / \ / \ 176 sctpScalars sctpTables sctpGroups sctpCompliances 177 | 178 sctpCompliance 180 where: 181 - sctpObjects, all the SCTP objects are defined under this 182 branch. 184 - sctpScalars, containing only scalars values. It can be split 185 into: 187 - General variables, listing the main SCTP variables. 189 - Statistics for traffic measurements. 190 - SCTP state related statistics 191 - other statistics 193 - sctpTables, to hold data from each association together with 194 the main statistics (per association or transport address). 195 Local and remote tables are included into the general 196 association table to allow multiples IP addresses in order 197 to support the multi-home feature. 199 - sctpConformance, for the Unit of Conformance. 201 - sctpGroups, SCTP MIB variables have been grouped according 202 to their function and the context they belong to (general 203 variables, variables/statistics per association, variables 204 per local IP address and variables/statistics per remote IP 205 address). 207 - sctpCompliances, Minimal list of objects in the SCTP MIB 208 module that an agent developer must implement. 210 3.1 Objects 212 3.1.1 Scalars 214 3.1.1.1 Protocol General Variables 216 The first section of the MIB contains the general variables of the 217 SCTP protocol. Maximum, minimum, values by default and initial values 218 are listed here. 220 Based on the TCP MIB [RFC2012], SCTP RTO mechanism is defined in the 221 same way. In SCTP protocol, only options 'other' and 'vanj' remain 222 because SCTP protocol defines Van Jacobson's algorithm as the one to 223 be used to calculate RTO. 'Other' is left for future use ('rsre' 224 algorithm was eliminated because MIL-STD-1778 is Cancelled-No 225 Superseding Document according to the Military Standard library and 226 'constant' option doesn't fulfill the SCTP protocol description). 228 3.1.1.2 Statistics for traffic Measurements 229 Statistics included here are related to the whole SCTP layer. 230 Statistics related to a specific association, or local/remote IP 231 addresses are defined inside its concerned table. 233 3.1.1.2.1 State-Related Statistics 235 These measures are based in the TCP model, but adapted to the SCTP 236 states. They store the number of succeeded association attempts, how 237 many associations have been initiated by the local or the remote SCTP 238 layer, or just the number of associations terminated in a graceful 239 (by means of SHUTDOWN procedure) or ungraceful way (by means of CLOSE 240 procedure). 242 3.1.1.2.2 Other Statistics 244 There is an statistic related to the SCTP packets, i.e., the number 245 of out of the blue packets received by the local host. The remainder 246 statistics are based on the data unit of SCTP: the chunk. In this 247 way, the whole picture of the SCTP layer is covered. 249 3.1.2 MIB Tables 251 3.1.2.1 Association Table 253 The part of the MIB to define each association is structured 254 according to a expanded table. There is a main table (called 255 association table, sctpAssocTable), indexed by the association 256 identification. The association identification is a value to identify 257 in a unique way an association. 259 The MIB does not restrict which value must be written here. It can be 260 the tag value, or the TCB creation time, or any other value the 261 implementor decides. 263 This main table contains common information for a given association 264 and two other tables inside: local IP addresses table 265 (sctpAssocLocalAddressTable), and remote IP addresses table 266 (sctpRemAddressTable). 268 sctpAssocTable 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | sctpAssocId (index) / ... | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 | sctpAssocRemHostName \ ... | 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 | sctpAssocLocalSCTPPort / ... | 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 276 | sctpAssocRemSCTPPort \ ... | 277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 278 | sctpAssocRemPrimaryAddressType / ... | 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 | sctpAssocRemPrimaryAddress \ ... | 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 | sctpAssocHeartBeatFlag / ...| 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | sctpAssocHeartBeatTimer \ ...| 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 | sctpAssocState / ... | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 | sctpAssocInStreams \ ... | 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 290 | sctpAssocOutStreams / ... | 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 | sctpAssocMaxRetr \ ... | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 | sctpAssocT1expired / ... | 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | sctpAssocT2expired \ ... | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 298 | sctpAssocRtxChunks / ... | 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | sctpAssocChecksumErrorCounter \ ... | 301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 302 | sctpAssocStartTime / ... | 303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 | sctpAssocLocalAddressTable | 305 | | 306 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 307 | | sctpAssocLocalAddressIPType(index) \ ... | | 308 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 309 | | sctpAssocLocalAddressIP (index) \ ... | | 310 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 311 | | sctpAssocLocalAddressStartTime \ ... | | 312 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 313 | | 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 | sctpAssocRemAddressTable | 316 | | 317 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 318 | | sctpAssocRemAddressIPType (index) \ ... | | 319 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 320 | | sctpAssocRemAddressIP (index) \ ... | | 321 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 322 | | sctpAssocRemAddressStatus \ ... | | 323 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 324 | | sctpAssocRemAddressRTO \ ... | | 325 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 326 | | sctpAssocRemAddressPathMaxRx \ ... | | 327 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 328 | | sctpAssocRemAddressRetransCount \ ... | | 329 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 330 | | sctpAssocRemAddressStartTime \ ... | | 331 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 332 | | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 Every entry is explained when defining the MIB. 337 Note that the IP address indexing the tables is valid for IPv4, IPv6 338 and DNS. Therefore, IP address is defined by the Internet address 339 type and the value of the IP address, according to the Textual 340 Conventions for Internet Network Address [RFC2851]. 342 However, DNS value is not being used to identify an IP address since 343 it is only valid during initialization (once this stage is finished, 344 both sides only use IP addresses). To keep the name of the remote 345 peer, an entry has been created in the association table 346 (sctpAssocRemHostName). When no DNS name is provided by the remote 347 endpoint at init time, this value will be NULL. Otherwise, the 348 received DNS name will be stored. 350 It is NOT possible to create rows in any table (sctpAssocTable, 351 sctpAssocLocalAddressTable, sctpRemAddressTable). 353 If it is required to abort an existing association, value deleteTCB 354 has to be written in the variable sctpAssocState. That is the only 355 way to delete rows in any of the mentioned tables. 357 3.1.2.1.1 Local IP addresses Table 359 Table for local IP addresses information. This table stores 360 information related to the local IP address/-es reserved for the 361 association. It's indexed by the local IP addresses. 363 3.1.2.1.2 Remote IP addresses Table 365 Table for remote IP addresses information. This table stores 366 information related to the remote IP address/-es reserved for the 367 association. It's indexed by the remote IP addresses. 369 3.1.2.2 Reverse Lookup Tables 371 There is also one reverse lookup table . This is an optional table to 372 help management applications efficiently access conceptual rows in 373 other tables. This is the way for not performing expensive tree walks 374 through large number of associations. 376 It is not possible to either create or delete rows in this table. 378 sctpInverseAssocTable 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 | sctpAssocRemSCTPPort (index) / ... | 381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 382 | sctpAssocLocalSCTPPort (index) \ ... | 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 | sctpAssocRemPrimaryAddressType (index) / ... | 385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 386 | sctpAssocRemPrimaryAddress (index) \ ... | 387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 388 | sctpAssocId (index) / ... | 389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 390 | sctpInverseAssocStartTime \ ... | 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 393 3.2 Conformance 395 3.2.1 Groups 397 This section includes all the variables defined in the MIB grouped by 398 function(variables or statistics) and context (SCTP general 399 parameters, 400 association context, local IP address context or remote IP address 401 context). 402 Therefore following groups have been created: 404 - General variables for the SCTP layer. 405 - General statistics for the states of the SCTP layer. 406 - General statistics for the SCTP layer. 407 - Variables and statistics per association, and variables per 408 local and remote IP address. 409 - Statistics per remote IP address. 411 3.2.2 Compliance 413 Requirements of the SCTP MIB to be implemented. 415 4. Definitions 417 SCTP-MIB DEFINITIONS ::= BEGIN 419 IMPORTS 420 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, Counter64 421 FROM SNMPv2-SMI -- RFC2578 422 TimeStamp 423 FROM SNMPv2-TC -- RFC2579 424 MODULE-COMPLIANCE, OBJECT-GROUP 425 FROM SNMPv2-CONF -- RFC2580 426 InetAddressType, InetAddress 427 FROM INET-ADDRESS-MIB -- RFC2851 428 ; 430 sctpMIB MODULE-IDENTITY 431 LAST-UPDATED "200102200000Z" -- 20th February 2001 432 ORGANIZATION "IETF SIGTRAN Working Group" 433 CONTACT-INFO 434 " Maria-Carmen Belinchon-Vergara 435 Jose-Javier Pastor-Balbas 437 Postal: Ericsson Espana S. A. 438 C/Retama 7 439 28045 Madrid 440 Spain 442 Phones: +34 91 339 3535 443 +34 91 339 3819 445 Emails: Maria.C.Belinchon@ericsson.com 446 J.Javier.Pastor@ericsson.com" 447 DESCRIPTION 448 "The MIB module for managing an SCTP implementation." 449 REVISION 450 "200102200000Z" -- 20th February 2001 451 DESCRIPTION 452 "MIB module developed for the SIGTRAN IETF group. Based on 453 SCTP, RFC2960" 454 ::= { xxxx } -- IANA needs to choose this value 455 -- when sent to the RFC editor 457 -- Top-level structure of the MIB 459 sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 } 460 sctpConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } 462 sctpScalars OBJECT IDENTIFIER ::= { sctpObjects 1 } 463 sctpTables OBJECT IDENTIFIER ::= { sctpObjects 2 } 465 -- PROTOCOL GENERAL VARIABLES 466 -- ************************** 468 sctpRtoAlgorithm OBJECT-TYPE 469 SYNTAX INTEGER { 470 other(1), -- Other new one. Future use 471 vanj(2) -- Van Jacobson's algorithm 472 } 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The algorithm used to determine the timeout value (T3-rtx) 477 used for re-transmitting unacknowledged chunks." 479 ::= { sctpScalars 1 } 481 sctpRtoMin OBJECT-TYPE 482 SYNTAX Unsigned32 483 UNITS "milliseconds" 484 MAX-ACCESS read-write 485 STATUS current 486 DESCRIPTION 487 "The minimum value permitted by a SCTP implementation for the 488 retransmission timeout, measured in milliseconds. More 489 refined semantics for objects of this type depend upon the 490 algorithm used to determine the retransmission timeout. 491 Minimum recommended value is 1000 milliseconds. Some telephony 492 applications could require less than 1 second, see [SIGAS] for 493 further information." 495 ::= { sctpScalars 2 } 497 sctpRtoMax OBJECT-TYPE 498 SYNTAX Unsigned32 499 UNITS "milliseconds" 500 MAX-ACCESS read-write 501 STATUS current 502 DESCRIPTION 503 "The maximum value permitted by a SCTP implementation for the 504 retransmission timeout, measured in milliseconds. More 505 refined semantics for objects of this type depend upon the 506 algorithm used to determine the retransmission timeout. 507 Recommended value is 60000 milliseconds." 509 ::= { sctpScalars 3 } 511 sctpRtoInitial OBJECT-TYPE 512 SYNTAX Unsigned32 513 UNITS "milliseconds" 514 MAX-ACCESS read-write 515 STATUS current 516 DESCRIPTION 517 "Initial value for the Retransmission timer. Recommended value 518 is 3000 milliseconds." 520 ::= { sctpScalars 4 } 522 sctpValCookieLife OBJECT-TYPE 523 SYNTAX Unsigned32 524 UNITS "milliseconds" 525 MAX-ACCESS read-write 526 STATUS current 527 DESCRIPTION 528 "Valid cookie life in the 4-way start-up handshake procedure. 529 Recommended value: 60000 milliseconds." 531 ::= { sctpScalars 5 } 533 sctpMaxInitRetr OBJECT-TYPE 534 SYNTAX Unsigned32 535 MAX-ACCESS read-write 536 STATUS current 537 DESCRIPTION 538 "The maximum number of retransmissions at the start-up phase 539 (INIT and COOKIE ECHO chunks). Recommended value: 8 attempts." 541 ::= { sctpScalars 6 } 543 -- STATE-RELATED STATISTICS 545 sctpCurrEstab OBJECT-TYPE 546 SYNTAX Counter32 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "The number of SCTP associations for which the current state 551 is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." 553 ::= { sctpScalars 7 } 555 sctpActiveEstab OBJECT-TYPE 556 SYNTAX Counter32 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The number of times that SCTP associations have made a direct 561 transition to the ESTABLISH state from the COOKIE-ECHOED 562 state: COOKIE-ECHOED -> ESTABLISHED. The upper layer has 563 initiated the association attempt." 565 ::= { sctpScalars 8 } 567 sctpPassiveEstab OBJECT-TYPE 568 SYNTAX Counter32 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The number of times that SCTP associations have made a direct 573 transition to the ESTABLISHED state from the CLOSED state: 574 CLOSED -> ESTABLISHED. The remote endpoint has initiated the 575 association attempt." 577 ::= { sctpScalars 9 } 579 sctpAborted OBJECT-TYPE 580 SYNTAX Counter32 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The number of times that SCTP associations have made a direct 585 transition to the CLOSED state from any state using the 586 primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful 587 termination of the association." 589 ::= { sctpScalars 10 } 591 sctpShutdowns OBJECT-TYPE 592 SYNTAX Counter32 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "The number of times that SCTP associations have made a direct 597 transition to the CLOSE state from either the SHUTDOWN-SENT 598 state or the SHUTDOWN-ACK-SENT state. Graceful termination of 599 the association." 601 ::= { sctpScalars 11 } 603 -- OTHER LAYER STATISTICS 605 sctpStatOutOfBlue OBJECT-TYPE 606 SYNTAX Counter64 607 MAX-ACCESS read-only 608 STATUS current 609 DESCRIPTION 610 "Number of out of the blue packets (SCTP packet correctly 611 formed -right checksum- but the receiver is not able to 612 identify the association to which this packet belongs) 613 received by the host." 615 ::= { sctpScalars 12 } 617 sctpStatSentChunks OBJECT-TYPE 618 SYNTAX Counter64 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "Number of SCTP control and data chunks, sent to the peers (no 623 retransmissions included)." 625 ::= { sctpScalars 13 } 627 sctpStatRecChunks OBJECT-TYPE 628 SYNTAX Counter64 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "Number of SCTP control and data chunks, received from the 633 peers (no retransmissions included)." 635 ::= { sctpScalars 14 } 637 sctpStatOutOfOrderSentChunks OBJECT-TYPE 638 SYNTAX Counter64 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "Number of unordered chunks (data chunks in which the U bit is 643 set to 1) sent to the peers." 645 ::= { sctpScalars 15 } 647 sctpStatOutOfOrderRecChunks OBJECT-TYPE 648 SYNTAX Counter64 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "Number of unordered chunks (data chunks in which the U bit is 653 set to 1) received from the peers." 655 ::= { sctpScalars 16 } 657 sctpStatFragmentedUsrMessages OBJECT-TYPE 658 SYNTAX Counter64 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "Number of user messages that have to be fragmented because of 663 the MTU." 665 ::= { sctpScalars 17 } 667 sctpStatReassembledUsrMessages OBJECT-TYPE 668 SYNTAX Counter64 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "Number of user messages reassembled." 674 ::= { sctpScalars 18 } 676 -- SCTP ASSOCIATION DESCRIPTION PARAMETERS 677 -- *************************************** 679 -- 680 -- ASSOCIATION INVERSE TABLE 681 -- 683 sctpInverseAssocTable OBJECT-TYPE 684 SYNTAX SEQUENCE OF SctpInverseAssocEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "Maps sctpAssocRemSCTPPort, sctpAssocLocalSCTPPort, 689 sctpAssocRemPrimaryAddressType, sctpAssocRemHostName and 690 sctpAssocRemPrimaryAddress, pairs to one or more sctpAssocId 691 values, each describing a row in the sctpAssocTable. This 692 makes it possible to retrieve the row in the sctpAssocTable 693 corresponding to a given association without having to walk 694 the entire (potentially large) table." 696 ::= { sctpTables 1 } 698 sctpInverseAssocEntry OBJECT-TYPE 699 SYNTAX SctpInverseAssocEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "Each table corresponds to exactly one entry in the 704 sctpAssocTable, i.e. the entry containing the tuple 705 sctpAssocRemSCTPPort, sctpAssocLocalPort, 706 sctpAssocRemPrimaryAddressType, sctpAssocRemPrimaryAddress, 707 sctpAssocRemHostName and sctpAssocId." 708 INDEX {sctpAssocRemSCTPPort, sctpAssocLocalSCTPPort, 709 sctpAssocRemPrimaryAddressType, 710 sctpAssocRemPrimaryAddress, 711 sctpAssocRemHostName, 712 sctpAssocId } 714 ::= { sctpInverseAssocTable 1 } 716 SctpInverseAssocEntry ::= SEQUENCE { 717 sctpInverseAssocStartTime TimeStamp 718 } 720 sctpInverseAssocStartTime OBJECT-TYPE 721 SYNTAX TimeStamp 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "The value of SysUpTime at the time that this row was 726 created." 728 ::= { sctpInverseAssocEntry 1 } 730 -- the SCTP Association TABLE 731 -- ************************** 733 -- The SCTP association table contains information about each 734 -- association that the local endpoint is taking part. 736 sctpAssocTable OBJECT-TYPE 737 SYNTAX SEQUENCE OF SctpAssocEntry 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "A table containing SCTP association-specific information." 743 ::= { sctpTables 2 } 745 sctpAssocEntry OBJECT-TYPE 746 SYNTAX SctpAssocEntry 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "General common variables and statistics for the whole 751 association." 752 INDEX { sctpAssocId } 754 ::= { sctpAssocTable 1 } 756 SctpAssocEntry ::= SEQUENCE { 757 sctpAssocId Unsigned32, 758 sctpAssocRemHostName OCTET STRING, 759 sctpAssocLocalSCTPPort Unsigned32, 760 sctpAssocRemSCTPPort Unsigned32, 761 sctpAssocRemPrimaryAddressType InetAddressType, 762 sctpAssocRemPrimaryAddress InetAddress, 763 sctpAssocHeartBeatFlag INTEGER, 764 sctpAssocHeartBeatTimer Unsigned32, 765 sctpAssocState INTEGER, 766 sctpAssocInStreams Unsigned32, 767 sctpAssocOutStreams Unsigned32, 768 sctpAssocMaxRetr Unsigned32, 769 sctpAssocT1expired Counter32, -- Statistic 770 sctpAssocT2expired Counter32, -- Statistic 771 sctpAssocRtxChunks Counter32, -- Statistic 772 sctpAssocChecksumErrorCounter Counter64, -- Statistic 773 sctpAssocStartTime TimeStamp 774 } 776 sctpAssocId OBJECT-TYPE 777 SYNTAX Unsigned32 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "Association Identification. Value identifying the association 782 (typically the Initiate Verification Tag)." 784 ::= { sctpAssocEntry 1 } 786 sctpAssocRemHostName OBJECT-TYPE 787 SYNTAX OCTET STRING (SIZE(0..255)) 788 MAX-ACCESS read-create 789 STATUS current 790 DESCRIPTION 791 "Peer's DNS name. If no DNS domain name was received at init 792 time (embedded in the INIT or INIT-ACK chunk) from the peer, 793 this entry will be meaningless, therefore it will contain a 794 NULL value. Otherwise, the remote host name received at init 795 time will be stored." 797 ::= { sctpAssocEntry 2 } 799 sctpAssocLocalSCTPPort OBJECT-TYPE 800 SYNTAX Unsigned32 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "Local SCTP port number used for this association." 806 ::= { sctpAssocEntry 3 } 808 sctpAssocRemSCTPPort OBJECT-TYPE 809 SYNTAX Unsigned32 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "Remote SCTP port number used for this association." 815 ::= { sctpAssocEntry 4 } 817 sctpAssocRemPrimaryAddressType OBJECT-TYPE 818 SYNTAX InetAddressType 819 MAX-ACCESS read-create 820 STATUS current 821 DESCRIPTION 822 "Internet type of primary destination IP address. 823 - unknown (0) An unknown address type. This value MUST be 824 used if the value of the corresponding InetAddress object 825 is a zero-length string. It may also be used to indicate an 826 IP address different from IPv4 or IPv6. This value is used 827 in this MIB for error conditions. 829 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 830 textual convention [RFC2851]. 832 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 833 textual convention [RFC2851]." 835 ::= { sctpAssocEntry 5 } 837 sctpAssocRemPrimaryAddress OBJECT-TYPE 838 SYNTAX InetAddress 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "Primary destination IP address. An InetAddress value is 843 always interpreted within the context of an InetAddressType 844 value. This value will be filled in after INIT or INIT ACK 845 messages have been received (when the primary path is selected 846 by SCTP)." 848 ::= { sctpAssocEntry 6 } 850 sctpAssocHeartBeatFlag OBJECT-TYPE 851 SYNTAX INTEGER { 852 active(0), 853 inactive(1) 854 } 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "The optional Heartbeat associated to one destination 859 transport address could be active or not (value equal to 1 or 860 0, respectively). 862 An active destination transport address is the one considered 863 available by a peer endpoint for receiving SCTP packets, as it 864 is described in [sctp]." 866 ::= { sctpAssocEntry 7 } 868 sctpAssocHeartBeatTimer OBJECT-TYPE 869 SYNTAX Unsigned32 870 UNITS "milliseconds" 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "The current heartbeat time-out. The recommended default value 875 is 30000 milliseconds." 877 ::= { sctpAssocEntry 8 } 879 sctpAssocState OBJECT-TYPE 880 SYNTAX INTEGER { 881 closed(1), 882 cookieWait(2), 883 cookieEchoed(3), 884 established(4), 885 shutdownPending(5), 886 shutdownSent(6), 887 shutdownReceived(7), 888 shutdownAckSent(8), 889 deleteTCB(9) 890 } 891 MAX-ACCESS read-create 892 STATUS current 893 DESCRIPTION 894 "The state of this SCTP association. 895 As in TCP, the only value which may be set by a management 896 station is deleteTCB. Accordingly, it is appropriate for an 897 agent to return a 'badValue' response if a management station 898 attempts to set this object to any other value. 899 If a management station sets this object to the value 900 deleteTCB(9), then this has the effect of deleting the TCB (as 901 defined in SCTP) of the corresponding association on the 902 managed node, resulting in immediate termination of the 903 association. 904 As an implementation-specific option, an ABORT chunk may be 905 sent from the managed node to the other SCTP endpoint." 907 ::= { sctpAssocEntry 9 } 909 sctpAssocInStreams OBJECT-TYPE 910 SYNTAX Unsigned32 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "Inbound Streams according to the negotiation at association 915 start up. This parameter has to be read-only by the manager." 917 ::= { sctpAssocEntry 10 } 919 sctpAssocOutStreams OBJECT-TYPE 920 SYNTAX Unsigned32 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "Outbound Streams according to the negotiation at association 925 start up. This parameter has to be read-only by the manager." 927 ::= { sctpAssocEntry 11 } 929 sctpAssocMaxRetr OBJECT-TYPE 930 SYNTAX Unsigned32 931 MAX-ACCESS read-create 932 STATUS current 933 DESCRIPTION 934 "The maximum number of data retransmissions. This value is 935 specific for each association and the upper layer can be able 936 to change it calling the appropiate primitives. This value has 937 to be smaller than the addition of all the maximum number for 938 all the paths (sctpAssocRemAddressMaxPathRetrans). 939 Recommended value: 10 attempts." 941 ::= { sctpAssocEntry 12 } 943 -- Association Statistics 945 sctpAssocT1expired OBJECT-TYPE 946 SYNTAX Counter32 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "Number of times that T1 timer expired (timer for sending 951 either INIT or COOKIE-ECHO chunks and receiving an 952 acknowledgment)." 954 ::= { sctpAssocEntry 13 } 956 sctpAssocT2expired OBJECT-TYPE 957 SYNTAX Counter32 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "Number of times that T2-shutdown timer expired (shutdown 962 timer)." 964 ::= { sctpAssocEntry 14 } 966 sctpAssocRtxChunks OBJECT-TYPE 967 SYNTAX Counter32 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "Number of data chunks retransmitted to the peer in the 972 current association." 974 ::= { sctpAssocEntry 15 } 976 sctpAssocChecksumErrorCounter OBJECT-TYPE 977 SYNTAX Counter64 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "Number of SCTP packets received from the peers with an 982 invalid checksum." 984 ::= { sctpAssocEntry 16 } 986 sctpAssocStartTime OBJECT-TYPE 987 SYNTAX TimeStamp 988 MAX-ACCESS read-only 989 STATUS current 990 DESCRIPTION 991 "The value of SysUpTime at the time that this row was 992 created." 994 ::= { sctpAssocEntry 17 } 996 -- Expanded tables: Including Multi-home feature 998 -- Local Address TABLE 999 -- ******************* 1001 sctpAssocLocalAddressTable OBJECT-TYPE 1002 SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry 1003 MAX-ACCESS not-accessible 1004 STATUS current 1005 DESCRIPTION 1006 "Expanded table of sctpAssocTable based on the AssocId index. 1007 It shows several interesting data for each local address which 1008 takes part in this association." 1010 ::= { sctpTables 3 } 1012 sctpAssocLocalAddressEntry OBJECT-TYPE 1013 SYNTAX SctpAssocLocalAddressEntry 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "Local information about the available addresses." 1018 INDEX { sctpAssocId, -- shared index 1019 sctpAssocLocalAddressIPType, 1020 sctpAssocLocalAddressIP } 1022 ::= { sctpAssocLocalAddressTable 1 } 1024 SctpAssocLocalAddressEntry ::= SEQUENCE { 1025 sctpAssocLocalAddressIPType InetAddressType, 1026 sctpAssocLocalAddressIP InetAddress, 1027 sctpAssocLocalAddressStartTime TimeStamp 1028 } 1030 sctpAssocLocalAddressIPType OBJECT-TYPE 1031 SYNTAX InetAddressType 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "Internet type of local IP address used for this association. 1036 - unknown (0) An unknown address type. This value MUST be 1037 used if the value of the corresponding InetAddress object 1038 is a zero-length string. It may also be used to indicate an 1039 IP address different from IPv4 or IPv6. This value is used 1040 in this MIB for error conditions. 1042 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 1043 textual convention [RFC2851]. 1045 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 1046 textual convention [RFC2851]." 1048 ::= { sctpAssocLocalAddressEntry 1 } 1050 sctpAssocLocalAddressIP OBJECT-TYPE 1051 SYNTAX InetAddress 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "The value of a local IP address available for this 1056 association. An InetAddress value is always interpreted within 1057 the context of an InetAddressType value. If SCTP are using DNS 1058 names, the mapping to IP address-es will be done at reception 1059 of INIT or INIT_ACK messages." 1061 ::= { sctpAssocLocalAddressEntry 2 } 1063 sctpAssocLocalAddressStartTime OBJECT-TYPE 1064 SYNTAX TimeStamp 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "The value of SysUpTime at the time that this row was 1069 created." 1071 ::= { sctpAssocLocalAddressEntry 3 } 1073 -- Remote Addresses TABLE 1074 -- ********************** 1076 sctpAssocRemAddressTable OBJECT-TYPE 1077 SYNTAX SEQUENCE OF SctpAssocRemAddressEntry 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "Expanded table of sctpAssocTable based on the AssocId index. 1082 It shows several interesting data for each remote peer IP 1083 address which is used in this association." 1085 ::= { sctpTables 4 } 1087 sctpAssocRemAddressEntry OBJECT-TYPE 1088 SYNTAX SctpAssocRemAddressEntry 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "Information about THE most important variables for every 1093 remote IP address " 1094 INDEX { sctpAssocId, -- shared index 1095 sctpAssocRemAddressIPType, 1096 sctpAssocRemAddressIP } 1098 ::= { sctpAssocRemAddressTable 1 } 1100 SctpAssocRemAddressEntry ::= SEQUENCE { 1101 sctpAssocRemAddressIPType InetAddressType, 1102 sctpAssocRemAddressIP InetAddress, 1103 sctpAssocRemAddressStatus INTEGER, 1104 sctpAssocRemAddressRTO Unsigned32, 1105 sctpAssocRemAddressMaxPathRetrans Unsigned32, 1106 sctpAssocRemAddressRetransCount Counter64, -- Statistic 1107 sctpAssocRemAddressStartTime TimeStamp 1108 } 1110 sctpAssocRemAddressIPType OBJECT-TYPE 1111 SYNTAX InetAddressType 1112 MAX-ACCESS not-accessible 1113 STATUS current 1114 DESCRIPTION 1115 "Internet type of a remote IP address available for this 1116 association. 1117 - unknown (0) An unknown address type. This value MUST be 1118 used if the value of the corresponding InetAddress object 1119 is a zero-length string. It may also be used to indicate an 1120 IP address different from IPv4 or IPv6. This value is used 1121 in this MIB for error conditions. 1123 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 1124 textual convention [RFC2851]. 1126 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 1127 textual convention [RFC2851]." 1129 ::= { sctpAssocRemAddressEntry 1 } 1131 sctpAssocRemAddressIP OBJECT-TYPE 1132 SYNTAX InetAddress 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "The value of a remote IP address available for this 1137 association. An InetAddress value is always interpreted within 1138 the context of an InetAddressType value." 1140 ::= { sctpAssocRemAddressEntry 2 } 1142 sctpAssocRemAddressStatus OBJECT-TYPE 1143 SYNTAX INTEGER { 1144 active(0), 1145 inactive(1) 1146 } 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "The current status of the remote transport address, according 1151 to [SCTP]. 1152 Active means that the threshold of no answer received from 1153 this IP address has not been reached. Inactive means that 1154 either no heartbeat was received from this address, or any 1155 other message, reaching the threshold defined by the 1156 protocol." 1158 ::= { sctpAssocRemAddressEntry 3 } 1160 sctpAssocRemAddressRTO OBJECT-TYPE -- T3-rtx- Timer 1161 SYNTAX Unsigned32 1162 UNITS "milliseconds" 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "The current Retransmision Time-Out. T3-rtx timer as defined 1167 in the protocol SCTP." 1169 ::= { sctpAssocRemAddressEntry 4 } 1171 sctpAssocRemAddressMaxPathRetrans OBJECT-TYPE 1172 SYNTAX Unsigned32 1173 MAX-ACCESS read-create 1174 STATUS current 1175 DESCRIPTION 1176 "Maximum number of DATA retransmissions allowed to a remote IP 1177 address before it is considered inactive, as defined in 1178 [sctp]. Recommended value 5 attempts." 1180 ::= { sctpAssocRemAddressEntry 5 } 1182 -- Remote Address Statistic 1184 sctpAssocRemAddressRetransCount OBJECT-TYPE 1185 SYNTAX Counter64 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1189 "Number of DATA retransmissions as defined in [sctp]." 1191 ::= { sctpAssocRemAddressEntry 6 } 1193 sctpAssocRemAddressStartTime OBJECT-TYPE 1194 SYNTAX TimeStamp 1195 MAX-ACCESS read-only 1196 STATUS current 1197 DESCRIPTION 1198 "The value of SysUpTime at the time that this row was 1199 created." 1201 ::= { sctpAssocRemAddressEntry 7 } 1203 -- 4.1 Conformance Information 1205 sctpGroups OBJECT IDENTIFIER ::= { sctpConformance 1 } 1206 sctpCompliances OBJECT IDENTIFIER ::= { sctpConformance 2 } 1208 -- 4.1.1 Units of conformance 1210 -- 1211 -- MODULE GROUPS 1212 -- 1214 sctpGeneralVariablesGroup OBJECT-GROUP 1215 OBJECTS { sctpRtoAlgorithm, 1216 sctpRtoMin, 1217 sctpRtoMax, 1218 sctpRtoInitial, 1219 sctpValCookieLife, 1220 sctpMaxInitRetr 1221 } 1222 STATUS current 1223 DESCRIPTION 1224 "Common parameters for all the associations. They can usually 1225 be referred as configuration parameters" 1227 ::= { sctpGroups 1 } 1229 sctpStateStatGroup OBJECT-GROUP 1230 OBJECTS {sctpCurrEstab, 1231 sctpActiveEstab, 1232 sctpPassiveEstab, 1233 sctpAborted, 1234 sctpShutdowns 1235 } 1236 STATUS current 1237 DESCRIPTION 1238 "The sctp group of objects to control state changes in the 1239 SCTP protocol local layer. They include the data for all the 1240 associations." 1242 ::= { sctpGroups 2 } 1244 sctpOtherStatGroup OBJECT-GROUP 1245 OBJECTS {sctpStatOutOfBlue, 1246 sctpStatSentChunks, 1247 sctpStatRecChunks, 1248 sctpStatOutOfOrderSentChunks, 1249 sctpStatOutOfOrderRecChunks, 1250 sctpStatFragmentedUsrMessages, 1251 sctpStatReassembledUsrMessages 1252 } 1253 STATUS current 1254 DESCRIPTION 1255 "The sctp group of objects providing for management of SCTP 1256 most common statistics for the local SCTP layer." 1258 ::= { sctpGroups 3 } 1260 sctpAssocTablesVariablesGroup OBJECT-GROUP 1261 OBJECTS {sctpAssocRemHostName, 1262 sctpAssocLocalSCTPPort, 1263 sctpAssocRemSCTPPort, 1264 sctpAssocRemPrimaryAddressType, 1265 sctpAssocRemPrimaryAddress, 1266 sctpAssocHeartBeatFlag, 1267 sctpAssocHeartBeatTimer, 1268 sctpAssocState, 1269 sctpAssocInStreams, 1270 sctpAssocOutStreams, 1271 sctpAssocMaxRetr, 1272 sctpAssocT1expired, 1273 sctpAssocT2expired, 1274 sctpAssocRtxChunks, 1275 sctpAssocChecksumErrorCounter, 1276 sctpAssocStartTime, 1277 sctpAssocLocalAddressStartTime, 1278 sctpAssocRemAddressStatus, 1279 sctpAssocRemAddressRTO, 1280 sctpAssocRemAddressMaxPathRetrans, 1281 sctpAssocRemAddressStartTime 1282 } 1283 STATUS current 1284 DESCRIPTION 1285 "The sctp group of objects to manage specific local and remote 1286 SCTP variables (local and remote tables). These variables 1287 include all the SCTP basic features." 1289 ::= { sctpGroups 4 } 1291 sctpAssocStatGroup OBJECT-GROUP 1292 OBJECTS {sctpAssocRemAddressRetransCount 1293 } 1294 STATUS current 1295 DESCRIPTION 1296 "The sctp group of objects to manage SCTP statistics related 1297 to the remote endpoint." 1299 ::= { sctpGroups 5 } 1301 sctpInverseGroup OBJECT-GROUP 1302 OBJECTS {sctpInverseAssocStartTime 1303 } 1304 STATUS current 1305 DESCRIPTION 1306 "Objects used in the inverse lookup table." 1308 ::= { sctpGroups 6 } 1310 -- 4.1.2 Compliance Statements 1312 -- 1313 -- MODULE COMPLIANCES 1314 -- 1316 sctpCompliance MODULE-COMPLIANCE 1317 STATUS current 1318 DESCRIPTION 1319 "The compliance statement for SNMPv3 entities which implement 1320 SCTP." 1322 MODULE -- this module 1324 MANDATORY-GROUPS { sctpGeneralVariablesGroup, 1325 sctpAssocTablesVariablesGroup 1326 } 1328 GROUP sctpStateStatGroup 1329 DESCRIPTION 1330 "The sctp group of objects to control state changes in 1331 the SCTP protocol." 1333 GROUP sctpOtherStatGroup 1334 DESCRIPTION 1335 "The sctp group of objects providing for management of 1336 SCTP general statistics." 1338 GROUP sctpAssocStatGroup 1339 DESCRIPTION 1340 "The sctp group of objects to manage SCTP statistics 1341 related to the remote endpoint." 1343 GROUP sctpInverseGroup 1344 DESCRIPTION 1345 "Objects used in inverse lookup tables. This should be 1346 implemented for easier lookups in the association 1347 tables." 1349 OBJECT sctpAssocRemPrimaryAddressType 1350 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1351 DESCRIPTION 1352 "It is only required to have IPv4 and IPv6 addresses to 1353 be stored since the use of the host names is limited to 1354 first stage, when the association is being established." 1356 OBJECT sctpAssocRemPrimaryAddress 1357 SYNTAX InetAddress (SIZE(4|16)) 1358 DESCRIPTION 1359 "It is only required to support IPv4 and unique IPv6 1360 addresses." 1362 OBJECT sctpAssocLocalAddressIPType 1363 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1364 DESCRIPTION 1365 "It is only required to have IPv4 and IPv6 addresses to 1366 be stored since the use of the host names is limited to 1367 first stage, when the association is being established." 1369 OBJECT sctpAssocLocalAddressIP 1370 SYNTAX InetAddress (SIZE(4|16)) 1371 DESCRIPTION 1372 "It is only required to support IPv4 and unique IPv6 1373 addresses." 1375 OBJECT sctpAssocRemAddressIPType 1376 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1377 DESCRIPTION 1378 "It is only required to have IPv4 and IPv6 addresses to 1379 be stored since the use of the host names is limited to 1380 first stage, when the association is being established." 1382 OBJECT sctpAssocRemAddressIP 1383 SYNTAX InetAddress (SIZE(4|16)) 1384 DESCRIPTION 1385 "It is only required to support IPv4 and unique IPv6 1386 addresses." 1388 ::= { sctpCompliances 1 } 1390 END 1392 5. References 1394 [sctp] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J. 1395 Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. 1396 Paxson, "Stream Control Transmission Protocol", RFC 2960, 1397 October 2000. 1399 [SIGAS] "Telephony Signaling Transport over SCTP Applicability 1400 Statement", . Work in progress. 1403 [MIBMPLS] Cucchiara et al. "Definnitions of Managed Objects for the 1404 Multiprotocol Label Switching, Label Distribution Protocol 1405 (LDP)", Internet Draf , January 1406 2000. 1408 [SecSNMP] Stallings, W., "SNMP3: A Security Enhancement for SNMP", 1409 IEEE Communication Surveys, Forth quarter 1998, Vol. 1 No. 1. 1411 [Cong] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1412 1988, Stanford, California. 1414 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1415 Transmission Control Protocol using SMIv2", RFC 2012, November 1416 1996. 1418 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1419 Architecture for Describing SNMP Management Frameworks", RFC 1420 2571, April 1999. 1422 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1423 of Management Information for TCP/IP-based Internets", STD 16, 1424 RFC 1155, May 1990. 1426 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1427 16, RFC 1212, March 1991. 1429 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1430 SNMP", RFC 1215, March 1991. 1432 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1433 Rose, M., and S. Waldbusser, "Structure of Management 1434 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1436 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1437 Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", 1438 STD 58, RFC 2579, April 1999. 1440 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1441 Rose, M., and S. Waldbusser, "Conformance Statements for 1442 SMIv2", STD 58, RFC 2580, April 1999. 1444 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1445 Network Management Protocol", STD 15, RFC 1157, May 1990. 1447 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1448 "Introduction to Community-based SNMPv2", RFC 1901, January 1449 1996. 1451 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1452 "Transport Mappings for Version 2 of the Simple Network 1453 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1455 [RFC2452] M. Daniele, "IP Version 6 Management Information Base for 1456 the Transmission Control Protocol", RFC 2452, December 1998 1458 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1459 "Message Processing and Dispatching for the Simple Network 1460 Management Protocol (SNMP)", RFC 2572, April 1999. 1462 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1463 (USM) for version 3 of the Simple Network Management Protocol 1464 (SNMPv3)", RFC 2574, April 1999. 1466 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1467 "Protocol Operations for Version 2 of the Simple Network 1468 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1470 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1471 RFC 2573, April 1999. 1473 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1474 Access Control Model (VACM) for the Simple Network Management 1475 Protocol (SNMP)", RFC 2575, April 1999. 1477 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1478 "Introduction to Version 3 of the Internet-standard Network 1479 Management Framework", RFC 2570, April 1999. 1481 [RFC2851] Textual Conventions for Internet Network Addresses ,RFC 1482 2851, June 2000. 1484 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1485 Requirement Levels", BCP 14, RFC 2119, Harvard University, 1486 March 1997 1488 6. Security Consideration 1490 There are a number of management objects defined in this MIB that 1491 have a MAX-ACCESS clause of read-write and/or read-create. Such 1492 objects may be considered sensitive or vulnerable in some network 1493 environments. The support for SET operations in a non-secure 1494 environment without proper protection can have a negative effect on 1495 network operations. 1497 It is thus important to control even GET access to these objects and 1498 possibly to even encrypt the values of these object when sending them 1499 over the network via SNMP. Not all versions of SNMP provide features 1500 for such a secure environment. 1502 SNMPv1 by itself is not a secure environment. Even if security 1503 measures are taken (e.g., using IPSEC), there is no per-user control 1504 as to who (once an IPSEC association is established between hosts) is 1505 allowed to GET or SET the objects in this MIB 1507 It is recommended that the implementers consider the security 1508 features as provided by the SNMPv3 framework. Specifically, the use 1509 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1510 based Access Control Model RFC 2575 [RFC2575] is recommended. 1512 It is then a customer/user responsibility to ensure that the SNMP 1513 entity giving access to an instance of this MIB, is properly 1514 configured to give access to the objects only to those principals 1515 (users) that have legitimate rights to indeed GET or SET 1516 (change/create/delete) them. 1518 7. Acknowledgments 1520 The authors wish to thank David Partain, Ed Yarwood and Shyamal 1521 Prasad for their invaluable comments. 1523 8. Authors' Addresses 1525 Javier Pastor Tel: +34-91-339-3819 1526 Ericsson Espana S.A. eMail: J.Javier.Pastor@ericsson.com 1527 Network Communication Services 1528 Retama 7, 5th floor 1529 Madrid, 28045 1530 Spain 1532 Maria-Carmen Belinchon Tel: +34-91-339-3535 1533 Ericsson Espana S.A. eMail: Maria.C.Belinchon@ericsson.com 1534 Network Communication Services 1535 Retama 7, 5th floor 1536 Madrid, 28045 1537 Spain 1539 9. Revision History 1541 9.1 Changes from 1543 o Open issues updated 1545 o Section 2: Reference to RFC227x changed to RFC257x 1547 o Section 4: Inside the sctpRtoAlgorithm definition has been put 1548 "other" first 1549 rather than last. That way, it won't end up in the middle of things 1550 when new 1551 enumerations are added later. 1553 9.2 Changes from 1555 o Change of "Simple" word to "Stream" word in SCTP acronyms 1556 o Version of the MIB based on SCTPv10 1558 o Section 2: Update SNMP Framework to include the standard 1559 explanation 1561 o New Structure for the MIB: 1562 sctpMIB 1563 \- sctpObjects 1564 \- sctpScalars 1565 \- sctpTables 1566 \- sctpConformance 1568 o Section 4.1.2: Unit of Conformance updated (functional structure). 1570 o MAX-ACCESS clauses reviewed 1572 o The general statistics has been re-ordered, placed before the 1573 tables. 1575 o In SMIv2, indexes should be not-accessible (= the object type is a 1576 column in a table used as index and may not be used as an operand in 1577 any 1578 operation != SMIv1) (pp109-110 in []) 1580 o IPv6 compatible: 1581 - Change of Primary/Local/Remote addresses 1582 - PENDING: check "MODULE-COMPLIANCE" 1584 o Row Status included in AssocTable, AssocLocal and AssocRem to 1585 create, 1586 modify and delete rows in the tables. 1588 o SCTP general statistics changed from Counter32 to Counter64 since 1589 it supports 1590 more data changes. 1592 o sctpCurrEstab ("State-related variables and statistics" section) 1593 variable 1594 changed from Gauge32 to Counter32. 1596 o sctpAssocRemAddressT1expired and sctpAssocRemAddressT2expired have 1597 been 1598 removed from the remote table and added in the general association 1599 data 1600 since they are variables per association (not per IP address). 1602 o sctpAssocDropDatag statistic has been removed from the general 1603 association 1604 statistics since it had an ambiguous meaning. 1606 o Explained the meaning of the unordered chunks (chunks in which the 1607 U bit is 1608 set to 1) in sctpStatOutOfOrderSentChunks and 1609 sctpStatOutOfOrderRecChunks. 1611 o Added sctpChecksumErrorCounter to collect information about wrong 1612 checksums 1613 received from the peer. 1615 o Specify that sctpStatSentChunks and sctpStatRecChunks does not 1616 contain 1617 retransmission chunks. 1619 o Reword the Security Considerations chapter pointing out that IPsec 1620 does 1621 not secure the network but it provides end-to-end security over a 1622 network. 1624 o sctpAssocRemAddressRtxChunks replaced as a variable per 1625 association, 1626 meaning the number of chunks retransmited to the peer in the current 1627 association. 1629 o sctpHeartBeatMisses and sctpMaxRetr have been replaced from the 1630 general 1631 SCTP statistics to the remote IP address table (sctpHeartBeatMisses) 1632 and 1633 in the association table (sctpMaxRetr). 1635 o Specify that the retransmissions in the general SCTP statistics 1636 include 1637 control plus data chunks. 1639 o Included heartbeat timer for remote IP address. 1641 o Removed sctpAssocRemAddressHeartBeatMisses variable from the remote 1642 IP 1643 address table. 1645 o Removed sctpAssocRemAddressT3expired variable from the remote IP 1646 address table. 1648 o Updated variables to the new SCTP states defined in v10. 1650 9.3 Changes from 1652 o sctpRtoMin - stray "." outside the double-quotes in the DESCRIPTION 1653 clause. 1655 o sctpRtoMax - stray "." outside the double-quotes in the DESCRIPTION 1656 clause. 1658 o sctpAssocRemHostName - the type OCTECT STRING should be OCTET 1659 STRING. 1661 o sctpAssocRemPrimaryAddress - the DESCRIPTION clause is missing its 1662 closing ouble-quote. 1664 o sctpConformance - this is defined as { sctpMIB 2 }, then never 1665 used; instead sctpMIBConformance (which is undefined) is used in the 1666 definition of sctpMIBGroups and sctpMIBCompliances. 1668 o Reworded the MIB organization 1670 o Removed maximum number of concurrent associations 1672 o In sctpMIBCompliance, removed a missing comma in MANDATORY-GROUPS. 1674 o In sctpAssocTablesVariablesGroup and sctpAssocStatGroup, removed 1675 extra commas at end of OBJECTS list. 1677 o sctpAssocInStreams. ACCESS changed from read-create to read-only. 1679 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1680 changed from per remote IP address to per association. 1682 o Comment on sctpAssocRemAddressHBTimer specifies now that the 1683 manager can change it. 1685 o ACCESS on sctpAssocRemAddressHBTimer changed from read-only to 1686 read-write. 1688 o ACCESS on sctpAssocRemAddressRetransCount changed from read-write 1689 to read-only. 1691 o Move sctpStatChecksumErrorCounter from general statistics to per 1692 association. 1694 o sctpMaxInStreams � It�s a sctp-user feature. 1696 o sctpStatRetransChunks � It�s more useful to have this statistic in 1697 a association basis 1699 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1700 have been created again instead of per association in order to follow 1701 the draft. If some implementations want to have the same value for 1702 all the associations they have, they should set all the variables in 1703 the different remote addresses to the same value. 1705 9.3 Changes from 1707 o Deleting all the RowStatus Structure. Associated text rewording in 1708 Tables section. 1710 o Variable StartTime added in all the tables in order to specify the 1711 creation time. 1713 o Adding the Association reverse lookup table for easier management. 1714 Associated text rewording in tables section. 1716 o Remove sctpInitialT1 and sctpInitialT2, since these values are 1717 equal to RTO. 1719 o Change of the Heartbeats to a per-association basis 1721 o Conformance up-to-date with all of this.