idnits 2.17.1 draft-ietf-sigtran-sctp-mib-06.txt: -(313): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1935): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1970): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2092): 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 8 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 44 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 180 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([RFC2851-update], [RFC2012-update]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 183 has weird spacing: '...ameters sct...' == Line 1970 has weird spacing: '...essType in co...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2012-update' is mentioned on line 61, but not defined ** Obsolete undefined reference: RFC 2012 (Obsoleted by RFC 4022) == Missing Reference: 'SNMPArch' is mentioned on line 134, but not defined == Missing Reference: 'SMIv1' is mentioned on line 139, but not defined == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 139, but not defined == Missing Reference: 'SNMPv1Traps' is mentioned on line 140, but not defined == Missing Reference: 'SMIv2' is mentioned on line 141, but not defined == Missing Reference: 'SNMPv2TC' is mentioned on line 141, but not defined == Missing Reference: 'SNMPv2Conf' is mentioned on line 142, but not defined == Missing Reference: 'SNMPv1' is mentioned on line 155, but not defined == Missing Reference: 'SNMPv2c' is mentioned on line 148, but not defined == Missing Reference: 'SNMPv2TM' is mentioned on line 150, but not defined == Missing Reference: 'SNMPv3MP' is mentioned on line 151, but not defined == Missing Reference: 'SNMPv3USM' is mentioned on line 151, but not defined == Missing Reference: 'SNMPv2PO' is mentioned on line 157, but not defined == Missing Reference: 'SNMPv3App' is mentioned on line 160, but not defined == Missing Reference: 'SNMPv3VACM' is mentioned on line 161, but not defined == Missing Reference: 'SCTP' is mentioned on line 977, but not defined == Unused Reference: 'MIBMPLS' is defined on line 1630, but no explicit reference was found in the text == Unused Reference: 'SecSNMP' is defined on line 1635, but no explicit reference was found in the text == Unused Reference: 'Cong' is defined on line 1638, but no explicit reference was found in the text == Unused Reference: 'RFC2012' is defined on line 1641, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 1648, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 1652, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 1656, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 1659, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1662, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1666, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1670, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 1674, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 1677, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 1681, but no explicit reference was found in the text == Unused Reference: 'RFC2452' is defined on line 1685, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 1688, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 1696, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1700, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1707, but no explicit reference was found in the text == Unused Reference: 'RFC2786' is defined on line 1720, but no explicit reference was found in the text == Unused Reference: 'TADDRESS' is defined on line 1725, but no explicit reference was found in the text == Unused Reference: 'TCPMIB' is defined on line 1729, but no explicit reference was found in the text == Unused Reference: 'UDPMIB' is defined on line 1733, but no explicit reference was found in the text == Unused Reference: 'IPv6ARCH' is defined on line 1738, but no explicit reference was found in the text -- 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) -- Duplicate reference: draft-ietf-ops-rfc2851-update, mentioned in 'RFC2786', was also mentioned in 'RFC2851-update'. == Outdated reference: A later version (-05) exists of draft-ietf-ops-taddress-mib-01 -- Possible downref: Normative reference to a draft: ref. 'TCPMIB' -- Possible downref: Normative reference to a draft: ref. 'UDPMIB' == Outdated reference: A later version (-04) exists of draft-ietf-ipngwg-scoping-arch-02 -- Possible downref: Normative reference to a draft: ref. 'IPv6ARCH' Summary: 21 errors (**), 0 flaws (~~), 49 warnings (==), 9 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: June 2002 Ericsson 6 December, 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 if DeleteTCB should be removed 55 - Decide under which object identifier branch of the SNMP tree, 56 SCTP will be placed (value obtained when submitted to the IETF 57 editor). 59 - Update references to [RFC2851-update] 61 - Update references to [RFC2012-update] 63 TABLE OF CONTENTS 65 Open Issues.........................................................2 66 1. Introduction.....................................................3 67 1.1 Abbreviations...................................................3 68 2. The SNMP Framework...............................................3 69 3. MIB Structure....................................................4 70 3.1 SCTP Parameters.................................................5 71 3.1.1 Protocol General Variables....................................5 72 3.1.2 MIB Tables....................................................5 73 3.1.2.1 Association Table..........................................6 74 3.1.2.2 Reverse Lookup Table.......................................8 75 3.2 SCTP Statistics.................................................9 76 3.3 Conformance.....................................................9 77 4. Definitions......................................................9 78 5. References......................................................35 79 6. Security Consideration..........................................38 80 7. Acknowledgments.................................................38 81 8. Authors' Addresses..............................................39 82 9. Revision History................................................39 83 9.1 Changes from ........................39 84 9.2 Changes from ..............39 85 9.3 Changes from ..............41 86 9.3 Changes from ..............42 87 9.4 Changes from ..............42 88 9.5 Changes from ..............43 89 9.6 Changes from ..............44 91 1. Introduction 93 This memo defines the Management Information Base (MIB) module which 94 describes managed objects for implementations of the SCTP. 96 The document starts with a brief description of the SNMP framework 97 and continues with the MIB explanation and security consideration 98 among others. 100 The managed objects in this MIB module have been based on RFC 2012 101 update: "Management Information Base for the Transmission Control 102 Protocol (TCP)" [draft-ietf-ipngwg-rfc2012-update-01.txt], work in 103 progress, and the RFC 2851 update "Textual Conventions for Internet 104 Network Addresses" [draft-ietf-ops-rfc2851-update-06.txt], work in 105 progress. 107 Terms related to the SCTP architecture are explained in [sctp]. Other 108 specific abbreviations are listed below. 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 112 document are to be interpreted as described in RFC 2119 [RFC2119]. 114 1.1 Abbreviations 116 DNS - Domain Name System 117 IANA - Internet Assigned Numbers Authority 118 ICANN - Internet Corporation for Assigned Names and Numbers 119 IETF - Internet Engineering Task Force 120 IP - Internet Protocol 121 MIB - Management Information Base 122 RFC - Request For Comment 123 RTO - Retransmission Time Out 124 SCTP - Stream Control Transmission Protocol 125 SMI - Structure of Management Information 126 SNMP - Simple Network Management Protocol 127 TCB - Transmission Control Block 128 TCP - Transmission Control Protocol 130 2. The SNMP Framework 131 The SNMP Management Framework presently consists of five major 132 components: 134 - An overall architecture, described in RFC 2571 [SNMPArch]. 136 - Mechanisms for describing and naming objects and events for the 137 purpose of management. The first version of this Structure of 138 Management Information (SMI) is called SMIv1 and described in 139 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 140 [SNMPv1Traps]. The second version, called SMIv2, is described 141 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 142 [SNMPv2Conf]. 144 - Message protocols for transferring management information. The 145 first version of the SNMP message protocol is called SNMPv1 and 146 described in RFC 1157 [SNMPv1]. A second version of the SNMP 147 message protocol, which is not an Internet standards track 148 protocol, is called SNMPv2c and described in RFC 1901 [SNMPv2c] 149 and RFC 1906 [SNMPv2TM]. The third version of the message 150 protocol is called SNMPv3 and described in RFC 1906 [SNMPv2TM], 151 RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 153 - Protocol operations for accessing management information. The 154 first set of protocol operations and associated PDU formats is 155 described in RFC 1157 [SNMPv1]. A second set of protocol 156 operations and associated PDU formats is described in RFC 1905 157 [SNMPv2PO]. 159 - A set of fundamental applications described in RFC 2273 160 [SNMPv3App] and the view-based access control mechanism 161 described in RFC 2575 [SNMPv3VACM]. 163 Managed objects are accessed via a virtual information store, termed 164 the Management Information Base or MIB. Objects in the MIB are 165 defined using the mechanisms defined in the SMI. This memo specifies 166 a MIB module that is compliant to the SMIv2. A MIB conforming to the 167 SMIv1 can be produced through the appropriate translations. The 168 resulting translated MIB must be semantically equivalent, except 169 where objects or events are omitted because no translation is 170 possible (use of Counter64). Some machine-readable information in 171 SMIv2 will be converted into textual descriptions in SMIv1 during the 172 translation process. However, this loss of machine-readable 173 information is not considered to change the semantics of the MIB. 175 3. MIB Structure 177 The MIB is structured in the following way: 179 sctpMIB 180 / \ 181 sctp sctpMIBConformance 182 / \ 183 sctpParameters sctpStats 185 where: 186 - sctpParameters, contains layer general variables, tables to 187 store association-related information, Statistics per 188 association and lookup tables. 190 - sctpStats, all the general SCTP layer statistics are defined 191 under this branch. Check out [sctp] for counters meaning. 192 - SCTP state related statistics 193 - traffic measurements statistics 194 - other statistics, mainly general counters 196 3.1 SCTP Parameters 198 3.1.1 Protocol General Variables 200 The first section of the MIB contains the general variables of the 201 SCTP protocol. Maximum, minimum, initial values, and values by 202 default are listed here. 204 SCTP RTO mechanism definition is based on the TCP MIB [RFC2012- 205 update]. In SCTP protocol, only options 'other' and 'vanj' are valid 206 since SCTP protocol defines Van Jacobson's algorithm as the one to 207 be used to calculate RTO. 'Other' is left for future use. 209 3.1.2 MIB Tables 211 There are several tables included in the SCTP MIB. The first group 212 deals with the Association variables and is composed of a main and 213 two extended tables. The second group is a bunch of tables used for 214 the reverse lookup. 216 It is NOT possible to create rows in any table (sctpAssocTable, 217 sctpAssocLocalAddressTable, sctpRemAddressTable and Reverse Lookup 218 tables). 220 It is NOT possible to delete rows in any table except in 221 sctpAssocTable under the particular conditions explained below. 223 3.1.2.1 Association Table 225 These are the main tables in the MIB where all the associationrelated 226 information is stored per association basis. They are structured 227 according to expanded tables. The main table is called sctpAssocTable 228 and is indexed by sctpAssocId (the association identification) that 229 is a value that uniquely identifies an association. The MIB does not 230 restrict which value must be written here. It can be the tag value, 231 the TCB creation time, or any other value the implementers decide. 233 The sctpAssoc index is also shared by two more tables: 234 - sctpAssocLocalAddressTable: to store the local IP address/(- 235 es). 236 - sctpAssocRemAddressTable: to store the remote addresses and the 237 per-remote-address((-es)-related information. 239 Note: The following representation is a conceptual mode of describing 240 the relationship between the tables in this MIB. Note that the real 241 relationship of the tables is by sharing an index, so tables are not 242 truly within tables. Every entry is explained when defining the 243 corresponding objects in the MIB. 245 sctpAssocTable 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 | sctpAssocId (index) / ... | 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | sctpAssocRemHostName \ ... | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | sctpAssocLocalPort / ... | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | sctpAssocRemPort \ ... | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | sctpAssocRemPrimaryAddressType / ... | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 257 | sctpAssocRemPrimaryAddress \ ... | 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 259 | sctpAssocHeartBeatTimer / ...| 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 | sctpAssocState \ ... | 262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 263 | sctpAssocInStreams / ... | 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 265 | sctpAssocOutStreams \ ... | 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | sctpAssocMaxRetr / ... | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | sctpAssocPrimaryProcess \ ...| 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | sctpAssocT1expireds / ... | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 | sctpAssocT2expireds \ ... | 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 | sctpAssocRtxChunks / ... | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | sctpAssocStartTime \ ... | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 | sctpAssocLocalAddressTable | 280 | | 281 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 282 | | sctpAssocLocalAddressType(index) \ ... | | 283 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 284 | | sctpAssocLocalAddress (index) \ ... | | 285 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 286 | | sctpAssocLocalAddressStartTime \ ... | | 287 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 288 | | 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 290 | sctpAssocRemAddressTable | 291 | | 292 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 293 | | sctpAssocRemAddressType (index) \ ... | | 294 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 295 | | sctpAssocRemAddress (index) \ ... | | 296 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 297 | | sctpAssocRemAddressStatus \ ... | | 298 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 299 | | sctpAssocRemAddressHBFlag \ ... | | 300 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-++-+| | 301 | | sctpAssocRemAddressRTO \ ... | | 302 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 303 | | sctpAssocRemAddressMaxPathRtx \ ... | | 304 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 305 | | sctpAssocRemAddressRtx \ ... | | 306 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 307 | | sctpAssocRemAddressStartTime \ ... | | 308 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 309 | | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 Both sctpAssocLocalAddressTable and sctpAssocRemAddressTable are 313 indexed by addresses. �Address� and �AddressType� use the syntax 314 InetAddress and InetAddressType defined in the Textual Conventions 315 for Internet Network Address [RFC2851-update]. In the general case 316 this syntax is valid for IPv4, IPv6 and DNS but only the first two 317 options will be valid for this MIB. 319 The IP addresses that the MIB supports are defined in the [RFC2851- 320 update]: global and non-global (either with a zone index or not) IPv4 321 addresses, global and non-global (either with a zone index or not) 322 IPv6 addresses. 324 DNS value is not used to identify an IP address since it is only 325 valid during initialization (once this stage is finished, both sides 326 only use IP addresses). 328 To keep the name of the remote peer (when provided by the peer at 329 initialization time), an entry has been created in the sctpAssocTable 330 (sctpAssocRemHostName). When no DNS name is provided, endpoint, this 331 value will be NULL. Otherwise, the received DNS name will be stored 332 here. 334 If it is required to abort an existing association, the value 335 deleteTCB has to be written in the variable sctpAssocState. That is 336 the only way to delete rows in any of the mentioned tables. 338 3.1.2.2 Reverse Lookup Table 340 There are five reverse lookup tables to help management applications 341 to efficiently access conceptual rows in other tables. This is the 342 way for not performing expensive tree walks through large number of 343 associations. All of these tables are optional. 345 The defined reversed lookup tables allow performing a lookup using 346 the following variables: 348 - Local Port: It allows finding the associations in which the 349 local endpoint is using the specified local port. 350 - Remote Port: It allows finding the associations in which the 351 remote endpoint is using the specified remote port. 352 - Remote Host Name: It allows finding the associations that have 353 defined the specified host name as remote endpoint. 354 - Remote Primary IP Address: It allows finding the associations 355 that have defined the specified remote IP address as primary. 356 - Remote IP address: List of all the associations that have the 357 specified IP address belonging to the set of remote addresses. 359 As an example the picture below shows the table to look up by remote 360 port. 362 sctpLookupRemPortTable 363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 | sctpAssocRemPort (index) / ... | 365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 | sctpAssocId (index) \ ... | 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 | sctpLookupRemPortStartTime / ... | 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 All the lookup tables contains a timestamp (referred as StartTime) to 372 indicate when a row in the table was created. 374 It is not possible to either create or delete rows in these tables. 376 3.2 SCTP Statistics 378 3.2.1 Statistics for traffic Measurements 380 It has been specified statistics related to the whole SCTP layer. 381 Statistics related to a specific association, or local/remote IP 382 addresses are defined inside its concerned table. 384 3.2.2 State-Related Statistics 386 These measures are based in the TCP model, but adapted to the SCTP 387 states. They store the number of succeeded association attempts, how 388 many associations have been initiated by the local or the remote SCTP 389 layer, or just the number of associations terminated in a graceful 390 (by means of SHUTDOWN procedure) or ungraceful way (by means of CLOSE 391 procedure). 393 3.2.3 Other Statistics 395 There is a statistic related to the SCTP packets, i.e., the number 396 of out of the blue packets received by the local host. The remainder 397 statistics are based on the data unit of SCTP: the chunk. In this 398 way, the whole picture of the SCTP layer is covered. 400 3.3 Conformance 402 The conformance section points out as optional the statistics either 403 general for the whole SCTP layer and per association or remote IP 404 address. 406 Also, IP address will take the format of IPv4 and IPv6 addresses (not 407 scoped). DNS name will not be accepted either (since names will be 408 stored � if present � in the sctpRemoteHostName variable). 410 4. Definitions 411 SCTP-MIB DEFINITIONS ::= BEGIN 413 IMPORTS 414 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32, 415 Counter32, Counter64 416 FROM SNMPv2-SMI -- RFC2578 417 TimeStamp 418 FROM SNMPv2-TC -- RFC2579 419 MODULE-COMPLIANCE, OBJECT-GROUP 420 FROM SNMPv2-CONF -- RFC2580 421 InetAddressType, InetAddress, InetPortNumber 422 FROM INET-ADDRESS-MIB -- RFC2851-update 423 ; 425 -- RFC2851 is being update. Needed to update the import clause 426 -- as well as other references to RFC2851 to include all the 427 -- textual conventions defined in the new RFC2851-update 429 sctpMIB MODULE-IDENTITY 430 LAST-UPDATED "200111280000Z" -- 28th December 2001 431 ORGANIZATION "IETF SIGTRAN Working Group" 432 CONTACT-INFO 433 " Maria-Carmen Belinchon-Vergara 434 Jose-Javier Pastor-Balbas 436 Postal: Ericsson Espana S. A. 437 Ombu street 3, 4th floor 438 28045 Madrid 439 Spain 441 Phones: +34 91 339 3535 442 +34 91 339 3819 444 Emails: Maria.C.Belinchon@ericsson.com 445 J.Javier.Pastor@ericsson.com" 446 DESCRIPTION 447 "The MIB module for managing an SCTP implementation." 448 ::= { xxxx } -- IANA needs to choose this value 449 -- when sent to the RFC editor 451 -- the SCTP base variables group 453 sctp OBJECT IDENTIFIER ::= { sctpMIB 1 } 454 sctpParameter OBJECT IDENTIFIER ::= { sctp 1 } 455 sctpStats OBJECT IDENTIFIER ::= { sctp 2 } 457 -- PROTOCOL GENERAL VARIABLES 458 -- ************************** 460 sctpRtoAlgorithm OBJECT-TYPE 461 SYNTAX INTEGER { 462 other(1), -- Other new one. Future use 463 vanj(2) -- Van Jacobson's algorithm 464 } 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The algorithm used to determine the timeout value (T3-rtx) 469 used for re-transmitting unacknowledged chunks." 471 ::= { sctpParameter 1 } 473 sctpRtoMin OBJECT-TYPE 474 SYNTAX Unsigned32 475 UNITS "milliseconds" 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The minimum value permitted by a SCTP implementation for the 480 retransmission timeout, measured in milliseconds. More 481 refined semantics for objects of this type depend upon the 482 algorithm used to determine the retransmission timeout. 483 Minimum recommended value is 1000 milliseconds. Some telephony 484 applications could require less than 1 second." 486 ::= { sctpParameter 2 } 488 sctpRtoMax OBJECT-TYPE 489 SYNTAX Unsigned32 490 UNITS "milliseconds" 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The maximum value permitted by a SCTP implementation for the 495 retransmission timeout, measured in milliseconds. More 496 refined semantics for objects of this type depend upon the 497 algorithm used to determine the retransmission timeout. 498 Recommended value is 60000 milliseconds." 500 ::= { sctpParameter 3 } 502 sctpRtoInitial OBJECT-TYPE 503 SYNTAX Unsigned32 504 UNITS "milliseconds" 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "Initial value for the Retransmission timer. Recommended value 509 is 3000 milliseconds." 511 ::= { sctpParameter 4 } 513 sctpMaxAssoc OBJECT-TYPE 514 SYNTAX Integer32 515 MAX-ACCESS read-only 516 STATUS current 517 DESCRIPTION 518 "The limit on the total number of SCTP associations the entity 519 can support. In entities where the maximum number of 520 associations is dynamic, this object should contain the value 521 -1." 523 ::= { sctpParameter 5 } 525 sctpValCookieLife OBJECT-TYPE 526 SYNTAX Unsigned32 527 UNITS "milliseconds" 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "Valid cookie life in the 4-way start-up handshake procedure. 532 Recommended value: 60000 milliseconds." 534 ::= { sctpParameter 6 } 536 sctpMaxInitRetr OBJECT-TYPE 537 SYNTAX Unsigned32 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The maximum number of retransmissions at the start-up phase 542 (INIT and COOKIE ECHO chunks). Recommended value: 8 attempts." 544 ::= { sctpParameter 7 } 546 -- SCTP ASSOCIATION DESCRIPTION PARAMETERS 547 -- *************************************** 549 -- the SCTP Association TABLE 550 -- ************************** 552 -- The SCTP association table contains information about each 553 -- association in which the local endpoint is involved. 555 sctpAssocTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF SctpAssocEntry 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "A table containing SCTP association-specific information." 562 ::= { sctpParameter 8 } 564 sctpAssocEntry OBJECT-TYPE 565 SYNTAX SctpAssocEntry 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "General common variables and statistics for the whole 570 association." 571 INDEX { sctpAssocId } 573 ::= { sctpAssocTable 1 } 575 SctpAssocEntry ::= SEQUENCE { 576 sctpAssocId Unsigned32, 577 sctpAssocRemHostName OCTET STRING, 578 sctpAssocLocalPort InetPortNumber, 579 sctpAssocRemPort InetPortNumber, 580 sctpAssocRemPrimaryAddressType InetAddressType, 581 sctpAssocRemPrimaryAddress InetAddress, 582 sctpAssocHeartBeatTimer Unsigned32, 583 sctpAssocState INTEGER, 584 sctpAssocInStreams Unsigned32, 585 sctpAssocOutStreams Unsigned32, 586 sctpAssocMaxRetr Unsigned32, 587 sctpAssocPrimaryProcess Unsigned32, 588 sctpAssocT1expireds Counter32, -- Statistic 589 sctpAssocT2expireds Counter32, -- Statistic 590 sctpAssocRtxChunks Counter32, -- Statistic 591 sctpAssocStartTime TimeStamp 592 } 594 sctpAssocId OBJECT-TYPE 595 SYNTAX Unsigned32 596 MAX-ACCESS not-accessible 597 STATUS current 598 DESCRIPTION 599 "Association Identification. Value identifying the association 600 (typically the Initiate Verification Tag). 602 Value zero is reserved to indicate no association." 604 ::= { sctpAssocEntry 1 } 606 sctpAssocRemHostName OBJECT-TYPE 607 SYNTAX OCTET STRING (SIZE(0..255)) 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "Peer's DNS name. If no DNS domain name was received at init 612 time (embedded in the INIT or INIT-ACK chunk) from the peer, 613 this entry will be meaningless, therefore it will contain a 614 zero-length string value. Otherwise, the remote host name 615 received at init time will be stored." 617 ::= { sctpAssocEntry 2 } 619 sctpAssocLocalPort OBJECT-TYPE 620 SYNTAX InetPortNumber (1..65535) 621 MAX-ACCESS read-only 622 STATUS current 623 DESCRIPTION 624 "Local SCTP port number used for this association.." 626 ::= { sctpAssocEntry 3 } 628 sctpAssocRemPort OBJECT-TYPE 629 SYNTAX InetPortNumber (1..65535) 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "Remote SCTP port number used for this association." 635 ::= { sctpAssocEntry 4 } 637 sctpAssocRemPrimaryAddressType OBJECT-TYPE 638 SYNTAX InetAddressType 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "Internet type of primary destination IP address. They are 643 interpreted according to the RFC2851-update. 645 The unknown (0) value MUST be used if the value of the 646 corresponding InetAddress object is a zero-length string (when 647 the endpoint does still not determined the Primary Address). 648 It may also be used for error conditions (IP address different 649 from IPv4 or IPv6). 651 This value will be filled in after the INIT or INIT ACK chunks 652 have been received and the primary path is selected by SCTP. 653 Until this occurs, the type will be unknown." 655 ::= { sctpAssocEntry 5 } 657 sctpAssocRemPrimaryAddress OBJECT-TYPE 658 SYNTAX InetAddress 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "Primary destination IP address. An InetAddress value is 663 always interpreted within the context of an InetAddressType 664 value. 666 This value will be filled in after INIT or INIT ACK chunks 667 have been received and the primary path is selected by SCTP. 668 Until this occurs, the type will be zero-length string." 670 ::= { sctpAssocEntry 6 } 672 sctpAssocHeartBeatTimer OBJECT-TYPE 673 SYNTAX Unsigned32 674 UNITS "milliseconds" 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "The current heartbeat time-out. The recommended default value 679 is 30000 milliseconds." 681 ::= { sctpAssocEntry 7 } 683 sctpAssocState OBJECT-TYPE 684 SYNTAX INTEGER { 685 closed(1), 686 cookieWait(2), 687 cookieEchoed(3), 688 established(4), 689 shutdownPending(5), 690 shutdownSent(6), 691 shutdownReceived(7), 692 shutdownAckSent(8), 693 deleteTCB(9) 694 } 695 MAX-ACCESS read-write 696 STATUS current 697 DESCRIPTION 698 "The state of this SCTP association. 700 As in TCP, deleteTCB is the only value that may be set by a 701 management station. Accordingly, it is appropriate for an 702 agent to return a 'badValue' response if a management station 703 attempts to set this object to any other value. 704 If a management station sets this object to the value 705 deleteTCB(9), then this has the effect of deleting the TCB (as 706 defined in SCTP) of the corresponding association on the 707 managed node, resulting in immediate termination of the 708 association. 710 As an implementation-specific option, an ABORT chunk may be 711 sent from the managed node to the other SCTP endpoint." 713 ::= { sctpAssocEntry 8 } 715 sctpAssocInStreams OBJECT-TYPE 716 SYNTAX Unsigned32 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "Inbound Streams according to the negotiation at association 721 start up. This parameter has to be read-only by the manager." 723 ::= { sctpAssocEntry 9 } 725 sctpAssocOutStreams OBJECT-TYPE 726 SYNTAX Unsigned32 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "Outbound Streams according to the negotiation at association 731 start up. This parameter has to be read-only by the manager." 733 ::= { sctpAssocEntry 10 } 735 sctpAssocMaxRetr OBJECT-TYPE 736 SYNTAX Unsigned32 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "The maximum number of data retransmissions in the association 741 context. This value is specific for each association and the 742 upper layer can change it calling the appropriate primitives. 743 This value has to be smaller than the addition of all the 744 maximum number for all the paths 745 (sctpAssocRemAddressMaxPathRtx). 746 Recommended value: 10 attempts." 748 ::= { sctpAssocEntry 11 } 750 sctpAssocPrimaryProcess OBJECT-TYPE 751 SYNTAX Unsigned32 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The number identifies the system level process which 756 holds primary responsibility of the SCTP association. 757 Wherever possible, this should be the system's native 758 unique identification number. The special value 0 can 759 be used to indicate that no primary process is known. 761 Note that the value of this object can be used as a 762 pointer into the swRunTable of the HOST-RESOURCES-MIB 763 (if the value is smaller than 2147483647) or into the 764 sysApplElmtRunTable of the SYSAPPL-MIB." 766 ::= { sctpAssocEntry 12 } 768 -- Association Statistics 770 sctpAssocT1expireds OBJECT-TYPE 771 SYNTAX Counter32 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "Number of times that T1 timer expired (timer for sending 776 either INIT or COOKIE-ECHO chunks and receiving an 777 acknowledgment)." 779 ::= { sctpAssocEntry 13 } 781 sctpAssocT2expireds OBJECT-TYPE 782 SYNTAX Counter32 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "Number of times that T2-shutdown timer expired (shutdown 787 timer)." 789 ::= { sctpAssocEntry 14 } 791 sctpAssocRtxChunks OBJECT-TYPE 792 SYNTAX Counter32 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "Number of data chunks retransmitted to the peer in the 797 current association." 799 ::= { sctpAssocEntry 15 } 801 sctpAssocStartTime OBJECT-TYPE 802 SYNTAX TimeStamp 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "The value of SysUpTime at the time that this row was 807 created." 809 ::= { sctpAssocEntry 16 } 811 -- Expanded tables: Including Multi-home feature 813 -- Local Address TABLE 814 -- ******************* 816 sctpAssocLocalAddressTable OBJECT-TYPE 817 SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry 818 MAX-ACCESS not-accessible 819 STATUS current 820 DESCRIPTION 821 "Expanded table of sctpAssocTable based on the AssocId index. 822 This table shows data related to each local IP address which 823 is used by this association." 825 ::= { sctpParameter 9 } 827 sctpAssocLocalAddressEntry OBJECT-TYPE 828 SYNTAX SctpAssocLocalAddressEntry 829 MAX-ACCESS not-accessible 830 STATUS current 831 DESCRIPTION 832 "Local information about the available addresses." 833 INDEX { sctpAssocId, -- shared index 834 sctpAssocLocalAddressType, 835 sctpAssocLocalAddress } 837 ::= { sctpAssocLocalAddressTable 1 } 839 SctpAssocLocalAddressEntry ::= SEQUENCE { 840 sctpAssocLocalAddressType InetAddressType, 841 sctpAssocLocalAddress InetAddress, 842 sctpAssocLocalAddressStartTime TimeStamp 843 } 845 sctpAssocLocalAddressType OBJECT-TYPE 846 SYNTAX InetAddressType 847 MAX-ACCESS not-accessible 848 STATUS current 849 DESCRIPTION 850 "Internet type of local IP address used for this association. 851 They are interpreted according to the RFC2851-update. 853 The unknown (0) value MUST be used if the value of the 854 corresponding InetAddress object is a zero-length string (when 855 the endpoint does still not determined the address(-es)). It 856 may also be used for error conditions (IP address different 857 from IPv4 or IPv6). 859 This value will be filled in after the INIT or INIT ACK chunks 860 have been received. Until this occurs, the type will be 861 unknown." 863 ::= { sctpAssocLocalAddressEntry 1 } 865 sctpAssocLocalAddress OBJECT-TYPE 866 SYNTAX InetAddress (SIZE(1..36)) 867 MAX-ACCESS not-accessible 868 STATUS current 869 DESCRIPTION 870 "The value of a local IP address available for this 871 association. An InetAddress value is always interpreted within 872 the context of an InetAddressType value. If SCTP is using a 873 DNS name, the mapping to IP address/-es will be done at 874 reception of INIT or INIT_ACK chunks. Until this occurs, it 875 will contain a zero value. 877 The sctpAssocRemAddress may not be empty due to the SIZE 878 restriction." 880 ::= { sctpAssocLocalAddressEntry 2 } 882 sctpAssocLocalAddressStartTime OBJECT-TYPE 883 SYNTAX TimeStamp 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "The value of SysUpTime at the time that this row was 888 created." 890 ::= { sctpAssocLocalAddressEntry 3 } 892 -- Remote Addresses TABLE 893 -- ********************** 895 sctpAssocRemAddressTable OBJECT-TYPE 896 SYNTAX SEQUENCE OF SctpAssocRemAddressEntry 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "Expanded table of sctpAssocTable based on the AssocId index. 901 This table shows data related to each remote peer IP address 902 which is used by this association." 904 ::= { sctpParameter 10 } 906 sctpAssocRemAddressEntry OBJECT-TYPE 907 SYNTAX SctpAssocRemAddressEntry 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "Information about the most important variables for every 912 remote IP address " 913 INDEX { sctpAssocId, -- shared index 914 sctpAssocRemAddressType, 915 sctpAssocRemAddress } 917 ::= { sctpAssocRemAddressTable 1 } 919 SctpAssocRemAddressEntry ::= SEQUENCE { 920 sctpAssocRemAddressType InetAddressType, 921 sctpAssocRemAddress InetAddress, 922 sctpAssocRemAddressStatus INTEGER, 923 sctpAssocRemAddressHBFlag INTEGER, 924 sctpAssocRemAddressRTO Unsigned32, 925 sctpAssocRemAddressMaxPathRtx Unsigned32, 926 sctpAssocRemAddressRtx Counter32, -- Statistic 927 sctpAssocRemAddressStartTime TimeStamp 928 } 930 sctpAssocRemAddressType OBJECT-TYPE 931 SYNTAX InetAddressType 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "Internet type of a remote IP address available for this 936 association. They are interpreted according to the RFC2851- 937 update. 939 The unknown (0) value MUST be used if the value of the 940 corresponding InetAddress object is a zero-length string (when 941 the endpoint does still not determined the Primary Address). 942 It may also be used for error conditions (IP address different 943 from IPv4 or IPv6). 945 This value will be filled in after the INIT or INIT ACK chunks 946 have been received. Until this occurs, the type will be 947 unknown." 949 ::= { sctpAssocRemAddressEntry 1 } 951 sctpAssocRemAddress OBJECT-TYPE 952 SYNTAX InetAddress (SIZE(1..36)) 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "The value of a remote IP address available for this 957 association. An InetAddress value is always interpreted within 958 the context of an InetAddressType value. If SCTP is using a 959 DNS name, the mapping to IP address/-es will be done at 960 reception of INIT or INIT_ACK chunks. Until this occurs, it 961 will contain a zero value. 963 The sctpAssocRemAddress may not be empty due to the SIZE 964 restriction." 966 ::= { sctpAssocRemAddressEntry 2 } 968 sctpAssocRemAddressStatus OBJECT-TYPE 969 SYNTAX INTEGER { 970 active(0), 971 inactive(1) 972 } 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "The current status of the remote transport address, according 977 to [SCTP]. 978 Active means that the threshold of no answer received from 979 this IP address has not been reached. Inactive means that 980 either no heartbeat was received from this address, or any 981 other message, reaching the threshold defined by the 982 protocol." 984 ::= { sctpAssocRemAddressEntry 3 } 986 sctpAssocRemAddressHBFlag OBJECT-TYPE 987 SYNTAX INTEGER { 988 active(0), 989 inactive(1) 990 } 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "The optional Heartbeat associated to one destination 995 transport address could be active or not (value equal to 0 or 996 1, respectively). 998 An active destination transport address is the one considered 999 available by a peer endpoint for receiving SCTP packets, as it 1000 is described in [sctp]." 1002 ::= { sctpAssocRemAddressEntry 4 } 1004 sctpAssocRemAddressRTO OBJECT-TYPE -- T3-rtx- Timer 1005 SYNTAX Unsigned32 1006 UNITS "milliseconds" 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "The current Retransmission Timeout. T3-rtx timer as defined 1011 in the protocol SCTP." 1013 ::= { sctpAssocRemAddressEntry 5 } 1015 sctpAssocRemAddressMaxPathRtx OBJECT-TYPE 1016 SYNTAX Unsigned32 1017 MAX-ACCESS read-only 1018 STATUS current 1019 DESCRIPTION 1020 "Maximum number of DATA chunks retransmissions allowed to a 1021 remote IP address before it is considered inactive, as defined 1022 in [sctp]. Recommended value 5 attempts." 1024 ::= { sctpAssocRemAddressEntry 6 } 1026 -- Remote Address Statistic 1028 sctpAssocRemAddressRtx OBJECT-TYPE 1029 SYNTAX Counter32 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "Number of DATA chunks retransmissions as defined in [sctp]." 1035 ::= { sctpAssocRemAddressEntry 7 } 1037 sctpAssocRemAddressStartTime OBJECT-TYPE 1038 SYNTAX TimeStamp 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "The value of SysUpTime at the time that this row was 1043 created." 1045 ::= { sctpAssocRemAddressEntry 8 } 1047 -- ASSOCIATION INVERSE TABLE 1048 -- ************************* 1050 -- BY LOCAL PORT 1052 sctpLookupLocalPortTable OBJECT-TYPE 1053 SYNTAX SEQUENCE OF SctpLookupLocalPortEntry 1054 MAX-ACCESS not-accessible 1055 STATUS current 1056 DESCRIPTION 1057 "With the use of this table, a list of associations which are 1058 using the specified local port can be got" 1060 ::= { sctpParameter 11 } 1062 sctpLookupLocalPortEntry OBJECT-TYPE 1063 SYNTAX SctpLookupLocalPortEntry 1064 MAX-ACCESS not-accessible 1065 STATUS current 1066 DESCRIPTION 1067 "This table is indexed by local port and association ID. 1068 Specifying a local port, we would get a list of the 1069 associations whose local port is the one specified" 1071 INDEX { sctpAssocLocalPort, 1072 sctpAssocId } 1074 ::= { sctpLookupLocalPortTable 1 } 1076 SctpLookupLocalPortEntry::= SEQUENCE { 1077 sctpLookupLocalPortStartTime TimeStamp 1078 } 1080 sctpLookupLocalPortStartTime OBJECT-TYPE 1081 SYNTAX TimeStamp 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "The value of SysUpTime at the time that this row was 1086 created." 1088 ::= { sctpLookupLocalPortEntry 1 } 1090 -- BY REMOTE PORT 1092 sctpLookupRemPortTable OBJECT-TYPE 1093 SYNTAX SEQUENCE OF SctpLookupRemPortEntry 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "With the use of this table, a list of associations which are 1098 using the specified remote port can be got" 1100 ::= { sctpParameter 12 } 1102 sctpLookupRemPortEntry OBJECT-TYPE 1103 SYNTAX SctpLookupRemPortEntry 1104 MAX-ACCESS not-accessible 1105 STATUS current 1106 DESCRIPTION 1107 "This table is indexed by remote port and association ID. 1108 Specifying a remote port we would get a list of the 1109 associations whose local port is the one specified " 1111 INDEX { sctpAssocRemPort, 1112 sctpAssocId } 1114 ::= { sctpLookupRemPortTable 1 } 1116 SctpLookupRemPortEntry::= SEQUENCE { 1117 sctpLookupRemPortStartTime TimeStamp 1118 } 1120 sctpLookupRemPortStartTime OBJECT-TYPE 1121 SYNTAX TimeStamp 1122 MAX-ACCESS read-only 1123 STATUS current 1124 DESCRIPTION 1125 "The value of SysUpTime at the time that this row was 1126 created." 1128 ::= { sctpLookupRemPortEntry 1 } 1130 -- BY REMOTE HOST NAME 1132 sctpLookupRemHostNameTable OBJECT-TYPE 1133 SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "With the use of this table, a list of associations with that 1138 particular host can be got" 1140 ::= { sctpParameter 13 } 1142 sctpLookupRemHostNameEntry OBJECT-TYPE 1143 SYNTAX SctpLookupRemHostNameEntry 1144 MAX-ACCESS not-accessible 1145 STATUS current 1146 DESCRIPTION 1147 "This table is indexed by remote host name and association ID. 1148 Specifying a host name we would get a list of the associations 1149 specifying that host name as the remote one" 1151 INDEX { sctpAssocRemHostName, 1152 sctpAssocId } 1154 ::= { sctpLookupRemHostNameTable 1 } 1156 SctpLookupRemHostNameEntry::= SEQUENCE { 1157 sctpLookupRemHostNameStartTime TimeStamp 1158 } 1160 sctpLookupRemHostNameStartTime OBJECT-TYPE 1161 SYNTAX TimeStamp 1162 MAX-ACCESS read-only 1163 STATUS current 1164 DESCRIPTION 1165 "The value of SysUpTime at the time that this row was 1166 created." 1168 ::= { sctpLookupRemHostNameEntry 1 } 1170 -- BY REMOTE PRIMARY IP ADDRESS 1172 sctpLookupRemPrimIPAddrTable OBJECT-TYPE 1173 SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry 1174 MAX-ACCESS not-accessible 1175 STATUS current 1176 DESCRIPTION 1177 "With the use of this table, it can be got a list of 1178 associations that have that the specified IP address as 1179 primary within the remote set of active addresses " 1181 ::= { sctpParameter 14 } 1183 sctpLookupRemPrimIPAddrEntry OBJECT-TYPE 1184 SYNTAX SctpLookupRemPrimIPAddrEntry 1185 MAX-ACCESS not-accessible 1186 STATUS current 1187 DESCRIPTION 1188 "This table is indexed by primary address and association ID. 1189 Specifying a primary address, we would get a list of the 1190 associations that have the specified remote IP address marked 1191 as primary. " 1193 INDEX { sctpAssocRemPrimaryAddressType, 1194 sctpAssocRemPrimaryAddress, 1195 sctpAssocId } 1197 ::= { sctpLookupRemPrimIPAddrTable 1 } 1199 SctpLookupRemPrimIPAddrEntry::= SEQUENCE { 1200 sctpLookupRemPrimIPAddrStartTime TimeStamp 1201 } 1203 sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE 1204 SYNTAX TimeStamp 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "The value of SysUpTime at the time that this row was 1209 created." 1211 ::= { sctpLookupRemPrimIPAddrEntry 1 } 1213 -- BY REMOTE IP ADDRESS 1215 sctpLookupRemIPAddrTable OBJECT-TYPE 1216 SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry 1217 MAX-ACCESS not-accessible 1218 STATUS current 1219 DESCRIPTION 1220 "With the use of this table, a list of associations that have 1221 the specified IP address as one of the remote ones can be got" 1223 ::= { sctpParameter 15 } 1225 sctpLookupRemIPAddrEntry OBJECT-TYPE 1226 SYNTAX SctpLookupRemIPAddrEntry 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "This table is indexed by a remote IP address and association 1231 ID. Specifying an IP address we would get a list of the 1232 associations that have the specified IP address included 1233 within the set of remote IP addresses" 1235 INDEX { sctpAssocRemAddressType, 1236 sctpAssocRemAddress, 1237 sctpAssocId } 1239 ::= { sctpLookupRemIPAddrTable 1 } 1241 SctpLookupRemIPAddrEntry::= SEQUENCE { 1242 sctpLookupRemIPAddrStartTime TimeStamp 1243 } 1245 sctpLookupRemIPAddrStartTime OBJECT-TYPE 1246 SYNTAX TimeStamp 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "The value of SysUpTime at the time that this row was 1251 created." 1253 ::= { sctpLookupRemIPAddrEntry 1 } 1255 -- 4.1 Conformance Information 1257 sctpMIBConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } 1258 sctpMIBCompliances OBJECT IDENTIFIER ::= { sctpMIBConformance 1 } 1259 sctpMIBGroups OBJECT IDENTIFIER ::= { sctpMIBConformance 2 } 1261 -- 4.1.1 Units of conformance 1263 -- 1264 -- MODULE GROUPS 1265 -- 1267 sctpParametersGroup OBJECT-GROUP 1268 OBJECTS { sctpRtoAlgorithm, 1269 sctpRtoMin, 1270 sctpRtoMax, 1271 sctpRtoInitial, 1272 sctpMaxAssoc, 1273 sctpValCookieLife, 1274 sctpMaxInitRetr 1275 } 1277 STATUS current 1278 DESCRIPTION 1279 "Common parameters for all the associations. They can usually 1280 be referred as configuration parameters" 1282 ::= { sctpMIBGroups 1 } 1284 sctpStatGroup OBJECT-GROUP 1285 OBJECTS {sctpCurrEstab, 1286 sctpActiveEstabs, 1287 sctpPassiveEstabs, 1288 sctpAborteds, 1289 sctpShutdowns, 1290 sctpOutOfBlues, 1291 sctpChecksumErrors, 1292 sctpOutCtrlChunks, 1293 sctpOutOrderChunks, 1294 sctpOutUnorderChunks, 1295 sctpInCtrlChunks, 1296 sctpInOrderChunks, 1297 sctpInUnorderChunks, 1298 sctpFragUsrMsgs, 1299 sctpReasmUsrMsgs, 1300 sctpOutSCTPPacks, 1301 sctpInSCTPPacks, 1302 sctpAssocRemAddressRtx 1303 } 1305 STATUS current 1306 DESCRIPTION 1307 "Statistics group. It includes the objects to control state 1308 changes in the SCTP protocol local layer and flow control 1309 statistics." 1311 ::= { sctpMIBGroups 2 } 1313 sctpAssocTableParametersGroup OBJECT-GROUP 1314 OBJECTS {sctpAssocRemHostName, 1315 sctpAssocLocalPort, 1316 sctpAssocRemPort, 1317 sctpAssocRemPrimaryAddressType, 1318 sctpAssocRemPrimaryAddress, 1319 sctpAssocHeartBeatTimer, 1320 sctpAssocState, 1321 sctpAssocInStreams, 1322 sctpAssocOutStreams, 1323 sctpAssocMaxRetr, 1324 sctpAssocPrimaryProcess, 1325 sctpAssocT1expireds, 1326 sctpAssocT2expireds, 1327 sctpAssocRtxChunks, 1328 sctpAssocStartTime, 1329 sctpAssocLocalAddressStartTime, 1330 sctpAssocRemAddressStatus, 1331 sctpAssocRemAddressHBFlag, 1332 sctpAssocRemAddressRTO, 1333 sctpAssocRemAddressMaxPathRtx, 1334 sctpAssocRemAddressStartTime 1335 } 1337 STATUS current 1338 DESCRIPTION 1339 "The SCTP group of objects to manage specific local and remote 1340 SCTP variables (local and remote tables). These variables 1341 include all the SCTP basic features." 1343 ::= { sctpMIBGroups 3 } 1345 sctpInverseGroup OBJECT-GROUP 1346 OBJECTS {sctpLookupLocalPortStartTime, 1347 sctpLookupRemPortStartTime, 1348 sctpLookupRemHostNameStartTime, 1349 sctpLookupRemPrimIPAddrStartTime, 1350 sctpLookupRemIPAddrStartTime 1352 } 1354 STATUS current 1355 DESCRIPTION 1356 "Objects used in the inverse lookup table." 1358 ::= { sctpMIBGroups 4 } 1360 -- STATE-RELATED STATISTICS 1362 sctpCurrEstab OBJECT-TYPE 1363 SYNTAX Gauge32 1364 MAX-ACCESS read-only 1365 STATUS current 1366 DESCRIPTION 1367 "The number of SCTP associations for which the current state 1368 is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." 1370 ::= { sctpStats 1 } 1372 sctpActiveEstabs OBJECT-TYPE 1373 SYNTAX Counter32 1374 MAX-ACCESS read-only 1375 STATUS current 1376 DESCRIPTION 1377 "The number of times that SCTP associations have made a direct 1378 transition to the ESTABLISHED state from the COOKIE-ECHOED 1379 state: COOKIE-ECHOED -> ESTABLISHED. The upper layer has 1380 initiated the association attempt." 1382 ::= { sctpStats 2 } 1384 sctpPassiveEstabs OBJECT-TYPE 1385 SYNTAX Counter32 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "The number of times that SCTP associations have made a direct 1390 transition to the ESTABLISHED state from the CLOSED state: 1391 CLOSED -> ESTABLISHED. The remote endpoint has initiated the 1392 association attempt." 1394 ::= { sctpStats 3 } 1396 sctpAborteds OBJECT-TYPE 1397 SYNTAX Counter32 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "The number of times that SCTP associations have made a direct 1402 transition to the CLOSED state from any state using the 1403 primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful 1404 termination of the association." 1406 ::= { sctpStats 4 } 1408 sctpShutdowns OBJECT-TYPE 1409 SYNTAX Counter32 1410 MAX-ACCESS read-only 1411 STATUS current 1412 DESCRIPTION 1413 "The number of times that SCTP associations have made a direct 1414 transition to the CLOSED state from either the SHUTDOWN-SENT 1415 state or the SHUTDOWN-ACK-SENT state. Graceful termination of 1416 the association." 1418 ::= { sctpStats 5 } 1420 -- OTHER LAYER STATISTICS 1422 sctpOutOfBlues OBJECT-TYPE 1423 SYNTAX Counter32 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "Number of out of the blue packets (SCTP packet correctly 1428 formed -right checksum- but the receiver is not able to 1429 identify the association to which this packet belongs) 1430 received by the host." 1432 ::= { sctpStats 6 } 1434 sctpChecksumErrors OBJECT-TYPE 1435 SYNTAX Counter32 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "Number of SCTP packets received from the peers with an 1440 invalid checksum." 1442 ::= { sctpStats 7 } 1444 sctpOutCtrlChunks OBJECT-TYPE 1445 SYNTAX Counter64 1446 MAX-ACCESS read-only 1447 STATUS current 1448 DESCRIPTION 1449 "Number of SCTP control chunks sent to the peers (no 1450 retransmissions included)." 1452 ::= { sctpStats 8 } 1454 sctpOutOrderChunks OBJECT-TYPE 1455 SYNTAX Counter64 1456 MAX-ACCESS read-only 1457 STATUS current 1458 DESCRIPTION 1459 "Number of SCTP ordered data chunks sent to the peers (no 1460 retransmissions included)." 1462 ::= { sctpStats 9 } 1464 sctpOutUnorderChunks OBJECT-TYPE 1465 SYNTAX Counter64 1466 MAX-ACCESS read-only 1467 STATUS current 1468 DESCRIPTION 1469 "Number of SCTP unordered chunks (data chunks in which the U 1470 bit is set to 1) sent to the peers (no retransmissions 1471 included)." 1473 ::= { sctpStats 10 } 1475 sctpInCtrlChunks OBJECT-TYPE 1476 SYNTAX Counter64 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "Number of SCTP control chunks received from the peers (no 1481 duplicated included)." 1483 ::= { sctpStats 11 } 1485 sctpInOrderChunks OBJECT-TYPE 1486 SYNTAX Counter64 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "Number of SCTP ordered data chunks received from the peers 1491 (no duplicated included)." 1493 ::= { sctpStats 12 } 1495 sctpInUnorderChunks OBJECT-TYPE 1496 SYNTAX Counter64 1497 MAX-ACCESS read-only 1498 STATUS current 1499 DESCRIPTION 1500 "Number of SCTP unordered chunks (data chunks in which the U 1501 bit is set to 1) received from the peers (no duplicated 1502 included)." 1504 ::= { sctpStats 13 } 1506 sctpFragUsrMsgs OBJECT-TYPE 1507 SYNTAX Counter64 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "Number of user messages that have to be fragmented because of 1512 the MTU." 1514 ::= { sctpStats 14 } 1516 sctpReasmUsrMsgs OBJECT-TYPE 1517 SYNTAX Counter64 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "Number of user messages reassembled." 1523 ::= { sctpStats 15 } 1525 sctpOutSCTPPacks OBJECT-TYPE 1526 SYNTAX Counter64 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "Number of SCTP packets sent to the peers." 1532 ::= { sctpStats 16 } 1534 sctpInSCTPPacks OBJECT-TYPE 1535 SYNTAX Counter64 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "Number of SCTP packets received from the peers." 1541 ::= { sctpStats 17 } 1543 -- 4.1.2 Compliance Statements 1545 -- 1546 -- MODULE COMPLIANCES 1547 -- 1549 sctpCompliance MODULE-COMPLIANCE 1550 STATUS current 1551 DESCRIPTION 1552 "The compliance statement for SNMPv3 entities which implement 1553 SCTP. 1555 The SCTP MIB specifies in this compliant implementation that 1556 only need to support IPv4/IPv6 addresses without a zone index, 1557 unknown type and DNS names. Support for IPv4/IPv6 addresses 1558 without zone indices is not required." 1560 MODULE -- this module 1562 MANDATORY-GROUPS { sctpParametersGroup, 1563 sctpAssocTableParametersGroup 1564 } 1566 GROUP sctpStatGroup 1567 DESCRIPTION 1568 "Group to cover all SCTP statistics. This will 1569 beimplemented when statistics are required." 1571 GROUP sctpInverseGroup 1572 DESCRIPTION 1573 "Objects used in inverse lookup tables. This should be 1574 implemented for easier lookups in the association tables, 1575 when it is required." 1577 OBJECT sctpAssocRemPrimaryAddressType 1578 SYNTAX InetAddressType { unknown(0), 1579 ipv4(1), 1580 ipv6(2) 1581 } 1582 DESCRIPTION 1583 "It is only required to have IPv4 and IPv6 addresses 1584 without zone indices. Unknown values must also be 1585 supported in case the IP address has a zero string length 1586 or an invalid/unknown format. 1588 The address with zone indices is required if an 1589 implementation can connect multiple zones." 1591 OBJECT sctpAssocLocalAddressType 1592 SYNTAX InetAddressType { unknown(0), 1593 ipv4(1), 1594 ipv6(2) 1595 } 1596 DESCRIPTION 1597 "It is only required to have IPv4 and IPv6 addresses 1598 without zone indices. Unknown values must also be 1599 supported in case the IP address has an invalid/unknown 1600 format. 1602 Addresses with zone indices are required if an 1603 implementation can connect multiple zones. " 1605 OBJECT sctpAssocRemAddressType 1606 SYNTAX InetAddressType { unknown(0), 1607 ipv4(1), 1608 ipv6(2) 1609 } 1610 DESCRIPTION 1611 "It is only required to have IPv4 and IPv6 addresses 1612 without zone indices. Unknown values must also be 1613 supported in case the IP address has an invalid/unknown 1614 format. 1616 Addresses with zone indices are required if an 1617 implementation can connect multiple zones. " 1619 ::= { sctpMIBCompliances 1 } 1621 END 1623 5. References 1625 [sctp] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J. 1626 Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. 1627 Paxson, "Stream Control Transmission Protocol", RFC 2960, 1628 October 2000. 1630 [MIBMPLS] Cucchiara et al. "Definnitions of Managed Objects for the 1631 Multiprotocol Label Switching, Label Distribution Protocol 1632 (LDP)", Internet Draf , January 1633 2000. 1635 [SecSNMP] Stallings, W., "SNMP3: A Security Enhancement for SNMP", 1636 IEEE Communication Surveys, Forth quarter 1998, Vol. 1 No. 1. 1638 [Cong] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1639 1988, Stanford, California. 1641 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1642 Transmission Control Protocol using SMIv2", RFC 2012, November 1643 1996. 1645 [RFC2571] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for 1646 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1648 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1649 Architecture for Describing SNMP Management Frameworks", RFC 1650 2571, April 1999. 1652 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1653 of Management Information for TCP/IP-based Internets", STD 16, 1654 RFC 1155, May 1990. 1656 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1657 16, RFC 1212, March 1991. 1659 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1660 SNMP", RFC 1215, March 1991. 1662 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1663 Rose, M., and S. Waldbusser, "Structure of Management 1664 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1666 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1667 Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", 1668 STD 58, RFC 2579, April 1999. 1670 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1671 Rose, M., and S. Waldbusser, "Conformance Statements for 1672 SMIv2", STD 58, RFC 2580, April 1999. 1674 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1675 Network Management Protocol", STD 15, RFC 1157, May 1990. 1677 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1678 "Introduction to Community-based SNMPv2", RFC 1901, January 1679 1996. 1681 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1682 "Transport Mappings for Version 2 of the Simple Network 1683 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1685 [RFC2452] M. Daniele, "IP Version 6 Management Information Base for 1686 the Transmission Control Protocol", RFC 2452, December 1998 1688 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1689 "Message Processing and Dispatching for the Simple Network 1690 Management Protocol (SNMP)", RFC 2572, April 1999. 1692 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1693 (USM) for version 3 of the Simple Network Management Protocol 1694 (SNMPv3)", RFC 2574, April 1999. 1696 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1697 "Protocol Operations for Version 2 of the Simple Network 1698 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1700 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1701 RFC 2573, April 1999. 1703 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1704 Access Control Model (VACM) for the Simple Network Management 1705 Protocol (SNMP)", RFC 2575, April 1999. 1707 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1708 "Introduction to Version 3 of the Internet-standard Network 1709 Management Framework", RFC 2570, April 1999. 1711 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1712 Requirement Levels", BCP 14, RFC 2119, Harvard University, 1713 March 1997 1715 [RFC2851-update] M. Daniele, B. Haberman, S. Routhier, J. 1716 Schoenwaelder, "Textual Conventions for Internet Network 1717 Addresses", draft-ietf-ops-rfc2851-update-06.txt, October 31, 1718 2001. Work in progress. 1720 [RFC2786] R. Frye,D. Levi ,S. Routhier, B. Wijnen , " Coexistence 1721 between Version 1, Version 2, and Version 3 of the Internet- 1722 standard Network Management Framework ", draft-ietf-ops- 1723 rfc2851-update-06.txt, DEcember 2000. 1725 [TADDRESS] M. Daniele , J. Schoenwaelder , "Textual Conventions for 1726 Transport Addresses", draft-ietf-ops-taddress-mib-01.txt, 1727 September 17, 2001. Work in progress. 1729 [TCPMIB] Management Information Base for the Transmission Control 1730 Protocol (TCP), draft-ietf-ipngwg-rfc2012-update-01.txt, 1731 November 2001. Work in progress. 1733 [UDPMIB] Bill Fenner, Brian Haberman, Keith McCloghrie, Juergen 1734 Schoenwalder, Dave Thaler, "Management Information Base for 1735 User Datagram Protocol (UDP)", draft-ietf-ipngwg-rfc2013- 1736 update-01.txt, November 2001. Work in progress. 1738 [IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, 1739 A. and B. Zill, "IPv6 Scoped Address Architecture", draft- 1740 ietf-ipngwg-scoping-arch-02.txt, September 2001. Work in 1741 progress. 1743 6. Security Consideration 1745 There is a management objects defined in this MIB that have a MAX- 1746 ACCESS clause of read-write (sctpAssocState), due to the deleteTCB 1747 state to allow to tear down the associations by the operator. Such 1748 object may be considered sensitive or vulnerable in some network 1749 environments. The support for SET operations in a non-secure 1750 environment without proper protection can have a negative effect on 1751 network operations. 1753 It is thus important to control even GET access to these objects and 1754 possibly to even encrypt the values of these object when sending them 1755 over the network via SNMP. Not all versions of SNMP provide features 1756 for such a secure environment. 1758 SNMPv1 by itself is not a secure environment. Even if security 1759 measures are taken (e.g., using IPSEC), there is no per-user control 1760 as to who (once an IPSEC association is established between hosts) is 1761 allowed to GET or SET the objects in this MIB 1763 It is recommended that the implementers consider the security 1764 features as provided by the SNMPv3 framework. Specifically, the use 1765 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1766 based Access Control Model RFC 2575 [RFC2575] is recommended. 1768 It is then a customer/user responsibility to ensure that the SNMP 1769 entity giving access to an instance of this MIB, is properly 1770 configured to give access to the objects only to those principals 1771 (users) that have legitimate rights to indeed GET or SET 1772 (change/create/delete) them. 1774 7. Acknowledgments 1776 The authors wish to thank David Partain, Ed Yarwood, John Linton and 1777 Shyamal Prasad for their invaluable comments. 1779 8. Authors' Addresses 1781 Javier Pastor-Balbas Tel: +34-91-339-3819 1782 Ericsson Espana S.A. eMail: J.Javier.Pastor@ericsson.com 1783 Network Communication Services 1784 Ombu 3, 4th floor 1785 Madrid, 28045 1786 Spain 1788 Maria-Carmen Belinchon Tel: +34-91-339-3535 1789 Ericsson Espana S.A. eMail: Maria.C.Belinchon@ericsson.com 1790 Network Communication Services 1791 Ombu 3, 4th floor 1792 Madrid, 28045 1793 Spain 1795 9. Revision History 1797 9.1 Changes from 1799 o Open issues updated 1801 o Section 2: Reference to RFC227x changed to RFC257x 1803 o Section 4: Inside the sctpRtoAlgorithm definition has been put 1804 "other" first rather than last. That way, it won't end up in the 1805 middle of things when new enumerations are added later. 1807 9.2 Changes from 1809 o Change of "Simple" word to "Stream" word in SCTP acronyms 1811 o Version of the MIB based on SCTPv10 1813 o Section 2: Update SNMP Framework to include the standard 1814 explanation 1816 o New Structure for the MIB: 1817 sctp 1818 \- sctpObjects 1819 \- sctpScalars 1820 \- sctpTables 1821 \- sctpMIBConformance 1823 o Section 4.1.2: Unit of Conformance updated (functional structure). 1825 o MAX-ACCESS clauses reviewed 1826 o The general statistics has been re-ordered, placed before the 1827 tables. 1829 o In SMIv2, indexes should be not-accessible (= the object type is a 1830 column in a table used as index and may not be used as an operand in 1831 any operation != SMIv1) (pp109-110 in []) 1833 o IPv6 compatible: 1834 - Change of Primary/Local/Remote addresses 1835 - PENDING: check "MODULE-COMPLIANCE" 1837 o Row Status included in AssocTable, AssocLocal and AssocRem to 1838 create, modify and delete rows in the tables. 1840 o SCTP general statistics changed from Counter32 to Counter64 since 1841 it supports more data changes. 1843 o sctpCurrEstab ("State-related variables and statistics" section) 1844 variable changed from Gauge32 to Counter32. 1846 o sctpAssocRemAddressT1expired and sctpAssocRemAddressT2expired have 1847 been removed from the remote table and added in the general 1848 association data since they are variables per association (not per IP 1849 address). 1851 o sctpAssocDropDatag statistic has been removed from the general 1852 association statistics since it had an ambiguous meaning. 1854 o Explained the meaning of the unordered chunks (chunks in which the 1855 U bit is set to 1) in sctpStatOutOfOrderSentChunks and 1856 sctpStatOutOfOrderRecChunks. 1858 o Added sctpChecksumErrorCounter to collect information about wrong 1859 checksums received from the peer. 1861 o Specify that sctpStatSentChunks and sctpStatRecChunks does not 1862 contain retransmission chunks. 1864 o Reword the Security Considerations chapter pointing out that IPsec 1865 does not secure the network but it provides end-to-end security over 1866 a network. 1868 o sctpAssocRemAddressRtxChunks replaced as a variable per 1869 association, meaning the number of chunks retransmited to the peer in 1870 the current association. 1872 o sctpHeartBeatMisses and sctpMaxRetr have been replaced from the 1873 general SCTP statistics to the remote IP address table 1874 (sctpHeartBeatMisses) and in the association table (sctpMaxRetr). 1876 o Specify that the retransmissions in the general SCTP statistics 1877 include control plus data chunks. 1879 o Included heartbeat timer for remote IP address. 1881 o Removed sctpAssocRemAddressHeartBeatMisses variable from the remote 1882 IP address table. 1884 o Removed sctpAssocRemAddressT3expired variable from the remote IP 1885 address table. 1887 o Updated variables to the new SCTP states defined in v10. 1889 9.3 Changes from 1891 o sctpRtoMin - stray "." outside the double-quotes in the DESCRIPTION 1892 clause. 1894 o sctpRtoMax - stray "." outside the double-quotes in the DESCRIPTION 1895 clause. 1897 o sctpAssocRemHostName - the type OCTECT STRING should be OCTET 1898 STRING. 1900 o sctpAssocRemPrimaryAddress - the DESCRIPTION clause is missing its 1901 closing ouble-quote. 1903 o sctpConformance - this is defined as { sctpMIB 2 }, then never 1904 used; instead sctpMIBConformance (which is undefined) is used in the 1905 definition of sctpMIBGroups and sctpMIBCompliances. 1907 o Reworded the MIB organization 1909 o Removed maximum number of concurrent associations 1911 o In sctpMIBCompliance, removed a missing comma in MANDATORY-GROUPS. 1913 o In sctpAssocTablesVariablesGroup and sctpAssocStatGroup, removed 1914 extra commas at end of OBJECTS list. 1916 o sctpAssocInStreams. ACCESS changed from read-create to read-only. 1918 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1919 changed from per remote IP address to per association. 1921 o Comment on sctpAssocRemAddressHBTimer specifies now that the 1922 manager can change it. 1924 o ACCESS on sctpAssocRemAddressHBTimer changed from read-only to 1925 read-write. 1927 o ACCESS on sctpAssocRemAddressRetransCount changed from read-write 1928 to read-only. 1930 o Move sctpStatChecksumErrorCounter from general statistics to per 1931 association. 1933 o sctpMaxInStreams � It�s a sctp-user feature. 1935 o sctpStatRetransChunks � It�s more useful to have this statistic in 1936 a association basis 1938 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1939 have been created again instead of per association in order to follow 1940 the draft. If some implementations want to have the same value for 1941 all the associations they have, they should set all the variables in 1942 the different remote addresses to the same value. 1944 9.3 Changes from 1946 o Deleting all the RowStatus Structure. Associated text rewording in 1947 Tables section. 1949 o Variable StartTime added in all the tables in order to specify the 1950 creation time. 1952 o Adding the Association reverse lookup table for easier management. 1953 Associated text rewording in tables section. 1955 o Remove sctpInitialT1 and sctpInitialT2, since these values are 1956 equal to RTO. 1958 o Change of the Heartbeats to a per-association basis 1960 o Conformance up-to-date with all of this. 1962 9.4 Changes from 1964 Main changes are due to the alignment with the TCP and UDP MIBs and 1965 the inclusion of new lookup tables. 1966 o Convert MIB to a read-only 1968 o Counters ends with �s� 1970 o Include �unknown� as an option for InetAddressType in conformance 1972 o Terminology fix: CLOSED state, unordered chunks instead of out-of- 1973 order, .. 1975 o HBFlag changed to per remote address 1977 o ChecksumErrors out of the AssocTable and hangs from Scalars 1979 o Update Ports from Unsigned32 to InetPortNumber according to 1980 RFC2851-update 1982 o Rework inverse tables: five new lookup tables 1984 o Remove INTEGER32 and change it to UNSIGNED32 1986 o Replace Counter32 by Counter64 1988 o Split Sent and Received chunks per association into control, 1989 ordered and unordered chunks 1991 9.5 Changes from 1993 Changes due to the IETF-51 meeting and requests from the mailing 1994 list. 1995 o Typo errors 1997 o Objects renumbering 1999 o All counters to Counter32 to be backward compatible, not to waste 2000 memory. Operators needing more than 32 bits will do it by 2001 augmentations. 2003 o Limit the number of IP address size when index 2005 o Specify that a port number with value zero means unknown port 2006 number according to the RFC2851-update 2008 Changes due to the alignment with the RFC2851-update. 2010 o Include clarification text of the IP address types supported in the 2011 SCTP MIB. Chapter 3.1.2.1 (Association table) 2013 o Remote Primary IP address: Addition of the ipv4z an ipv6z types for 2014 non-globally IP addresses in which a scope identifier is needed. 2015 Addition of the scope of ipv6 type. All of them according to the 2016 RFC2851-update v04 2018 o InetAddressType for local and remote IP addresses: 2020 Limit UNKNOWN type only for unknown IP address format. Remove UNKNOWN 2021 type for zero-length value in the InetAddress since it will be never 2022 zero-length due to the size restriction (0..64) 2023 Addition of the ipv4z an ipv6z types for non-globally IP addresses in 2024 which a scope identifier is needed. Addition of the scope of ipv6 2025 type. All of them according to the RFC2851-update v04 2027 o Clarify when mapping DNS <-> IPaddress occurs with the remote IP 2028 addresses 2030 o Conformance: 2032 Description: Specify that the SCTP MIB only need to support IPv4/IPv6 2033 addresses without a zone index, unknown type and DNS names. Support 2034 for IPv4/IPv6 addresses with zone indices is not required. 2036 InetAddressType for primary, local and remote IP addresses: Clarify 2037 that the implementation is only required to support IPv4 and IPv6 2038 address types without zone indices. Clarify also that UNKONWN type is 2039 only used in case of local and remote addresses when invalid/unknown 2040 IP address format 2042 InetAddress value of primary, local and remote IP address: Removal of 2043 the InetAddress values supported. Limitation of the supported IP 2044 address types is already included in the InetAddressType 2046 o Revision of the RFC2851-update v05. Changes in this draft does not 2047 affect the SCTP MIB. 2049 9.6 Changes from 2051 Changes due to the IPv6mib Design Team and the Sigtran mailing list. 2053 o RFC2851-update v06 (changes) does not affect the SCTP MIB 2055 o Typo errors 2057 o Restructure the MIB organization (tree): 2058 sctp 2059 \- sctpParameters 2060 \- sctpStats 2062 o Modify conformance section according to the new MIB structure. 2063 Statistics and lookup tables will be optional 2065 o Clarify that the SCTP MIB is based on the TCP MIB update 2066 (RFC2012update) and the TCs for Internet Network Addresses 2067 (RFC2851update) � remove reference to RFC2452 2069 o Replace "Sent" by "out" and "Received" by "in" in statistics 2071 o Change the sctpAssocId to exclude the value zero. This allows other 2072 MIBs to reference associations and to use the value 0 to indicate no 2073 association 2074 o Clarify sctpRemHostName to be zero-length value when no remote host 2075 name was received at the initialization stage 2077 o Limit the range of local and remote ports to (1..65535). Value 0 2078 (unknown port number according to RFC2851-update) is not valid in 2079 SCTP associations since there is no way of having an assoc with an 2080 unknown local or remote port 2082 o sctpAssocRemPrimaryAddressType and sctpAssocRemPrimaryAddress value 2083 to be filled in with a zero length string until valid values are 2084 received in the INIT or INIT ACK chunk 2086 o sctpAssocRemAddress and sctpAssocLocalAddressIP size upper limit 2087 restriction to 36, as TCP MIB 2089 o Change to Counter64 those counters which may wrap in less than an 2090 hour 2092 o Change sctpMaxAssoc variable to Integer32 since value �1 is allowed 2093 for dynamic maximum number of associations 2095 o Added a new column in the association table to give a pointer to 2096 the primary system level process which holds the association 2097 endpoint(sctpAssocPrimaryProcess) 2099 o Specify in the security section, which object should be handled 2100 carefully for security reasons