idnits 2.17.1 draft-ietf-sigtran-sctp-mib-05.txt: -(1992): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2027): 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 4 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 182 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]), 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 179 has weird spacing: '...Scalars sctp...' == Line 2027 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: 'RFC 2012' is mentioned on line 99, but not defined ** Obsolete undefined reference: RFC 2012 (Obsoleted by RFC 4022) == Missing Reference: 'RFC 2452' is mentioned on line 100, 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 102 == Missing Reference: 'SNMPArch' is mentioned on line 130, but not defined == Missing Reference: 'SMIv1' is mentioned on line 135, but not defined == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 135, but not defined == Missing Reference: 'SNMPv1Traps' is mentioned on line 136, but not defined == Missing Reference: 'SMIv2' is mentioned on line 137, but not defined == Missing Reference: 'SNMPv2TC' is mentioned on line 137, but not defined == Missing Reference: 'SNMPv2Conf' is mentioned on line 138, but not defined == Missing Reference: 'SNMPv1' is mentioned on line 151, but not defined == Missing Reference: 'SNMPv2c' is mentioned on line 144, but not defined == Missing Reference: 'SNMPv2TM' is mentioned on line 146, but not defined == Missing Reference: 'SNMPv3MP' is mentioned on line 147, but not defined == Missing Reference: 'SNMPv3USM' is mentioned on line 147, but not defined == Missing Reference: 'SNMPv2PO' is mentioned on line 153, but not defined == Missing Reference: 'SNMPv3App' is mentioned on line 156, but not defined == Missing Reference: 'SNMPv3VACM' is mentioned on line 157, but not defined == Missing Reference: 'SCTP' is mentioned on line 1207, but not defined == Unused Reference: 'MIBMPLS' is defined on line 1696, but no explicit reference was found in the text == Unused Reference: 'SecSNMP' is defined on line 1701, but no explicit reference was found in the text == Unused Reference: 'Cong' is defined on line 1704, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 1711, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 1715, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 1719, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 1722, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1725, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1729, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1733, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 1737, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 1740, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 1744, but no explicit reference was found in the text == Unused Reference: 'RFC2452' is defined on line 1748, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 1751, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 1759, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1763, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1770, but no explicit reference was found in the text == Unused Reference: 'TADDRESS' is defined on line 1783, but no explicit reference was found in the text == Unused Reference: 'TCPMIB' is defined on line 1787, but no explicit reference was found in the text == Unused Reference: 'UDPMIB' is defined on line 1791, but no explicit reference was found in the text == Unused Reference: 'IPv6ARCH' is defined on line 1796, 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) == Outdated reference: A later version (-06) exists of draft-ietf-ops-rfc2851-update-05 == Outdated reference: A later version (-05) exists of draft-ietf-ops-taddress-mib-01 == Outdated reference: A later version (-01) exists of draft-ietf-ipngwg-rfc2012-update-00 -- Possible downref: Normative reference to a draft: ref. 'TCPMIB' == Outdated reference: A later version (-01) exists of draft-ietf-ipngwg-rfc2013-update-00 -- 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: 22 errors (**), 0 flaws (~~), 51 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: April 2002 Ericsson 6 November, 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 [RFC2851-update] 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...................................................10 75 4. Definitions.....................................................10 76 5. References.....................................................36 77 6. Security Consideration..........................................39 78 7. Acknowledgments.................................................39 79 8. Authors' Addresses..............................................39 80 9. Revision History................................................40 81 9.1 Changes from ........................40 82 9.2 Changes from ..............40 83 9.3 Changes from ..............42 84 9.3 Changes from ..............43 85 9.4 Changes from ..............43 86 9.5 Changes from ..............44 88 1. Introduction 90 This memo defines the Management Information Base (MIB) module which 91 describes managed objects for implementations of the SCTP. 93 The document starts with a brief description of the SNMP framework 94 and continues with the MIB explanation and security consideration 95 among others. 97 The managed objects in this MIB module have been based on RFC 2012: 98 "SNMPv2 Management Information Base for the Transmission Control 99 Protocol using SMIv2" [RFC 2012] and "IP Version 6 Management 100 Information Base for the Transmission Control Protocol" [RFC 2452]. 102 Terms related to the SCTP architecture are explained in [1]. Other 103 specific abbreviations are listed below. 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in RFC 2119 [RFC2119]. 109 1.1 Abbreviations 111 DNS - Domain Name System 112 IANA - Internet Assigned Numbers Authority 113 ICANN - Internet Corporation for Assigned Names and Numbers 114 IETF - Internet Engineering Task Force 115 IP - Internet Protocol 116 MIB - Management Information Base 117 RFC - Request For Comment 118 RTO - Retransmission Time Out 119 SCTP - Stream Control Transmission Protocol 120 SMI - Structure of Management Information 121 SNMP - Simple Network Management Protocol 122 TCB - Transmission Control Block 123 TCP - Transmission Control Protocol 125 2. The SNMP Framework 127 The SNMP Management Framework presently consists of five major 128 components: 130 - An overall architecture, described in RFC 2271 [SNMPArch]. 132 - Mechanisms for describing and naming objects and events for the 133 purpose of management. The first version of this Structure of 134 Management Information (SMI) is called SMIv1 and described in 135 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 136 [SNMPv1Traps]. The second version, called SMIv2, is described 137 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 138 [SNMPv2Conf]. 140 - Message protocols for transferring management information. The 141 first version of the SNMP message protocol is called SNMPv1 and 142 described in RFC 1157 [SNMPv1]. A second version of the SNMP 143 message protocol, which is not an Internet standards track 144 protocol, is called SNMPv2c and described in RFC 1901 [SNMPv2c] 145 and RFC 1906 [SNMPv2TM]. The third version of the message 146 protocol is called SNMPv3 and described in RFC 1906 [SNMPv2TM], 147 RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 149 - Protocol operations for accessing management information. The 150 first set of protocol operations and associated PDU formats is 151 described in RFC 1157 [SNMPv1]. A second set of protocol 152 operations and associated PDU formats is described in RFC 1905 153 [SNMPv2PO]. 155 - A set of fundamental applications described in RFC 2273 156 [SNMPv3App] and the view-based access control mechanism 157 described in RFC 2575 [SNMPv3VACM]. 159 Managed objects are accessed via a virtual information store, termed 160 the Management Information Base or MIB. Objects in the MIB are 161 defined using the mechanisms defined in the SMI. This memo specifies 162 a MIB module that is compliant to the SMIv2. A MIB conforming to the 163 SMIv1 can be produced through the appropriate translations. The 164 resulting translated MIB must be semantically equivalent, except 165 where objects or events are omitted because no translation is 166 possible (use of Counter64). Some machine-readable information in 167 SMIv2 will be converted into textual descriptions in SMIv1 during the 168 translation process. However, this loss of machine-readable 169 information is not considered to change the semantics of the MIB. 171 3. Structure of the MIB 173 The MIB is structured in the following way: 175 sctpMib 176 / \ 177 sctpObjects sctpConformance 178 / \ / \ 179 sctpScalars sctpTables sctpGroups sctpCompliances 180 | 181 sctpCompliance 183 where: 184 - sctpObjects, all the SCTP objects are defined under this 185 branch. 187 - sctpScalars, containing only scalars values. It can be split 188 into: 190 - General variables, listing the main SCTP variables. 192 - Statistics for traffic measurements. 193 - SCTP state related statistics 194 - other statistics 196 - sctpTables, tables per association, per local and remote IP 197 address and lookup tables for an easy search. 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 a 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 an 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 implementers decide. 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 (sctpAssocRemAddressTable). 268 Note: The following representation is a conceptual mode of describing 269 the relationship between the tables in this MIB. Note that the real 270 relationship of the tables is by sharing an index, so tables are not 271 truly within tables. 273 sctpAssocTable 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 | sctpAssocId (index) / ... | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | sctpAssocRemHostName \ ... | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 | sctpAssocLocalSCTPPort / ... | 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 281 | sctpAssocRemSCTPPort \ ... | 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 | sctpAssocRemPrimaryAddressType / ... | 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 | sctpAssocRemPrimaryAddress \ ... | 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 | sctpAssocHeartBeatTimer / ...| 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | sctpAssocState \ ... | 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 | sctpAssocInStreams / ... | 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 293 | sctpAssocOutStreams \ ... | 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 | sctpAssocMaxRetr / ... | 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | sctpAssocT1expireds \ ... | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 | sctpAssocT2expireds / ... | 300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 301 | sctpAssocRtxChunks \ ... | 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 | sctpAssocStartTime / ... | 304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 305 | sctpAssocLocalAddressTable | 306 | | 307 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 308 | | sctpAssocLocalAddressIPType(index) \ ... | | 309 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 310 | | sctpAssocLocalAddressIP (index) \ ... | | 311 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 312 | | sctpAssocLocalAddressStartTime \ ... | | 313 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 314 | | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | sctpAssocRemAddressTable | 317 | | 318 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 319 | | sctpAssocRemAddressIPType (index) \ ... | | 320 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 321 | | sctpAssocRemAddressIP (index) \ ... | | 322 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 323 | | sctpAssocRemAddressStatus \ ... | | 324 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 325 | | sctpAssocRemAddressHBFlag \ ... | | 326 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-++-+| | 327 | | sctpAssocRemAddressRTO \ ... | | 328 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 329 | | sctpAssocRemAddressMaxPathRtx \ ... | | 330 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 331 | | sctpAssocRemAddressRtx \ ... | | 332 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 333 | | sctpAssocRemAddressStartTime \ ... | | 334 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 335 | | 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 Every entry is explained when defining the MIB. 340 Note that the IP address indexing the tables is valid for IPv4, IPv6 341 and DNS. Therefore, IP address is defined by the Internet address 342 type and the value of the IP address, according to the Textual 343 Conventions for Internet Network Address [RFC2851-update]. 345 The IP addresses that the MIB supports are defined in the [RFC2851- 346 update]: global and non-global (either with a zone index or not) IPv4 347 addresses, global and non-global (either with a zone index or not) 348 IPv6 addresses. 350 DNS value is not used to identify an IP address since it is only 351 valid during initialization (once this stage is finished, both sides 352 only use IP addresses). To keep the name of the remote peer, an entry 353 has been created in the association table (sctpAssocRemHostName). 354 When no DNS name is provided by the remote endpoint at initialization 355 time, this value will be NULL. Otherwise, the received DNS name will 356 be stored. 358 It is NOT possible creating rows in any table (sctpAssocTable, 359 sctpAssocLocalAddressTable, sctpRemAddressTable and Reverse Lookup 360 tables). 362 If it is required to abort an existing association, the value 363 deleteTCB has to be written in the variable sctpAssocState. That is 364 the only way to delete rows in any of the mentioned tables. 366 3.1.2.1.1 Local IP addresses Table 368 Table for local IP addresses information. This table stores 369 information related to the local IP address/-es reserved for the 370 association. It is indexed by the local IP addresses (and the shared 371 index sctpAssocId). 373 3.1.2.1.2 Remote IP addresses Table 374 Table for remote IP addresses information. This table stores 375 information related to the remote IP address/-es reserved for the 376 association. It is indexed by the remote IP addresses (and the shared 377 index sctpAssocId). 379 3.1.2.2 Reverse Lookup Tables 381 There are five reverse lookup tables. These tables are optional to 382 help management applications to efficiently access conceptual rows in 383 other tables. This is the way for not performing expensive tree walks 384 through large number of associations. 386 It is not possible to either create or delete rows in this table. 388 All the lookup tables contains a timestamp to indicate when a row in 389 the table was created. 391 Several tables have been created for this purpose: 393 - Local Port: It allows finding the associations in which the 394 local endpoint is using the specified local port. 395 - Remote Port: It allows finding the associations in which the 396 remote endpoint is using the specified remote port. 397 - Remote Host Name: It allows finding the associations that have 398 defined the specified host name as remote endpoint. 399 - Remote Primary IP Address: It allows finding the associations 400 that have defined the specified remote IP address as primary. 401 - Remote IP address: List of all the associations that have the 402 specified IP address belonging to the set of remote addresses. 404 As an example the picture below shows the table to look up by remote 405 port. 407 sctpLookupRemPortTable 408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 409 | sctpAssocRemSCTPPort (index) / ... | 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 | sctpAssocId (index) \ ... | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | sctpLookupRemPortStartTime / ... | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 416 3.2 Conformance 418 3.2.1 Groups 420 This section includes all the variables defined in the MIB grouped by 421 function (variables or statistics) and context (SCTP general 422 parameters, association context, local IP address context or remote 423 IP address context). 425 Therefore the following groups have been created: 427 - General variables for the SCTP layer. 428 - General statistics for the states of the SCTP layer. 429 - General statistics for the SCTP layer. 430 - Variables and statistics per association, and variables per 431 local and remote IP address. 432 - Statistics per remote IP address. 434 3.2.2 Compliance 436 Requirements of the SCTP MIB to be implemented. 438 4. Definitions 440 SCTP-MIB DEFINITIONS ::= BEGIN 442 IMPORTS 443 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Gauge32, Counter32 444 FROM SNMPv2-SMI -- RFC2578 445 TimeStamp 446 FROM SNMPv2-TC -- RFC2579 447 MODULE-COMPLIANCE, OBJECT-GROUP 448 FROM SNMPv2-CONF -- RFC2580 449 InetAddressType, InetAddress, InetPortNumber 450 FROM INET-ADDRESS-MIB -- RFC2851-update 451 ; 453 -- RFC2851 is being update. Needed to update the import clause 454 -- as well as other references to RFC2851 to include all the 455 -- textual conventions defined in the new RFC2851-update 457 sctpMIB MODULE-IDENTITY 458 LAST-UPDATED "200110170000Z" -- 17th October 2001 459 ORGANIZATION "IETF SIGTRAN Working Group" 460 CONTACT-INFO 461 " Maria-Carmen Belinchon-Vergara 462 Jose-Javier Pastor-Balbas 464 Postal: Ericsson Espana S. A. 465 Ombu street 3, 4th floor 466 28045 Madrid 467 Spain 469 Phones: +34 91 339 3535 470 +34 91 339 3819 472 Emails: Maria.C.Belinchon@ericsson.com 473 J.Javier.Pastor@ericsson.com" 474 DESCRIPTION 475 "The MIB module for managing an SCTP implementation." 476 REVISION 477 "200110170000Z" -- 17th October 2001 479 DESCRIPTION 480 "MIB module developed for the SIGTRAN IETF group. Based on 481 SCTP, RFC2960" 482 ::= { xxxx } -- IANA needs to choose this value 483 -- when sent to the RFC editor 485 -- Top-level structure of the MIB 487 sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 } 488 sctpConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } 490 sctpScalars OBJECT IDENTIFIER ::= { sctpObjects 1 } 491 sctpTables OBJECT IDENTIFIER ::= { sctpObjects 2 } 493 -- PROTOCOL GENERAL VARIABLES 494 -- ************************** 496 sctpRtoAlgorithm OBJECT-TYPE 497 SYNTAX INTEGER { 498 other(1), -- Other new one. Future use 499 vanj(2) -- Van Jacobson's algorithm 500 } 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The algorithm used to determine the timeout value (T3-rtx) 505 used for re-transmitting unacknowledged chunks." 507 ::= { sctpScalars 1 } 509 sctpRtoMin OBJECT-TYPE 510 SYNTAX Unsigned32 511 UNITS "milliseconds" 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The minimum value permitted by a SCTP implementation for the 516 retransmission timeout, measured in milliseconds. More 517 refined semantics for objects of this type depend upon the 518 algorithm used to determine the retransmission timeout. 520 Minimum recommended value is 1000 milliseconds. Some telephony 521 applications could require less than 1 second." 523 ::= { sctpScalars 2 } 525 sctpRtoMax OBJECT-TYPE 526 SYNTAX Unsigned32 527 UNITS "milliseconds" 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "The maximum value permitted by a SCTP implementation for the 532 retransmission timeout, measured in milliseconds. More 533 refined semantics for objects of this type depend upon the 534 algorithm used to determine the retransmission timeout. 535 Recommended value is 60000 milliseconds." 537 ::= { sctpScalars 3 } 539 sctpRtoInitial OBJECT-TYPE 540 SYNTAX Unsigned32 541 UNITS "milliseconds" 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "Initial value for the Retransmission timer. Recommended value 546 is 3000 milliseconds." 548 ::= { sctpScalars 4 } 550 sctpMaxAssoc OBJECT-TYPE 551 SYNTAX Unsigned32 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "The limit on the total number of SCTP associations the entity 556 can support. In entities where the maximum number of 557 associations is dynamic, this object should contain the value 558 -1." 560 ::= { sctpScalars 5 } 562 sctpValCookieLife OBJECT-TYPE 563 SYNTAX Unsigned32 564 UNITS "milliseconds" 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION 568 "Valid cookie life in the 4-way start-up handshake procedure. 569 Recommended value: 60000 milliseconds." 571 ::= { sctpScalars 6 } 573 sctpMaxInitRetr OBJECT-TYPE 574 SYNTAX Unsigned32 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The maximum number of retransmissions at the start-up phase 579 (INIT and COOKIE ECHO chunks). Recommended value: 8 attempts." 581 ::= { sctpScalars 7 } 583 -- STATE-RELATED STATISTICS 585 sctpCurrEstab OBJECT-TYPE 586 SYNTAX Gauge32 587 MAX-ACCESS read-only 588 STATUS current 589 DESCRIPTION 590 "The number of SCTP associations for which the current state 591 is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." 593 ::= { sctpScalars 8 } 595 sctpActiveEstabs OBJECT-TYPE 596 SYNTAX Counter32 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The number of times that SCTP associations have made a direct 601 transition to the ESTABLISHED state from the COOKIE-ECHOED 602 state: COOKIE-ECHOED -> ESTABLISHED. The upper layer has 603 initiated the association attempt." 605 ::= { sctpScalars 9 } 607 sctpPassiveEstabs OBJECT-TYPE 608 SYNTAX Counter32 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "The number of times that SCTP associations have made a direct 613 transition to the ESTABLISHED state from the CLOSED state: 614 CLOSED -> ESTABLISHED. The remote endpoint has initiated the 615 association attempt." 617 ::= { sctpScalars 10 } 619 sctpAborteds OBJECT-TYPE 620 SYNTAX Counter32 621 MAX-ACCESS read-only 622 STATUS current 623 DESCRIPTION 624 "The number of times that SCTP associations have made a direct 625 transition to the CLOSED state from any state using the 626 primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful 627 termination of the association." 629 ::= { sctpScalars 11 } 631 sctpShutdowns OBJECT-TYPE 632 SYNTAX Counter32 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The number of times that SCTP associations have made a direct 637 transition to the CLOSED state from either the SHUTDOWN-SENT 638 state or the SHUTDOWN-ACK-SENT state. Graceful termination of 639 the association." 641 ::= { sctpScalars 12 } 643 -- OTHER LAYER STATISTICS 645 sctpStatOutOfBlues OBJECT-TYPE 646 SYNTAX Counter32 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "Number of out of the blue packets (SCTP packet correctly 651 formed -right checksum- but the receiver is not able to 652 identify the association to which this packet belongs) 653 received by the host." 655 ::= { sctpScalars 13 } 657 sctpStatChecksumErrors OBJECT-TYPE 658 SYNTAX Counter32 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "Number of SCTP packets received from the peers with an 663 invalid checksum." 665 ::= { sctpScalars 14 } 666 sctpStatSentCtrlChunks OBJECT-TYPE 667 SYNTAX Counter32 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "Number of SCTP control chunks sent to the peers (no 672 retransmissions included)." 674 ::= { sctpScalars 15 } 676 sctpStatSentOrderChunks OBJECT-TYPE 677 SYNTAX Counter32 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "Number of SCTP ordered data chunks sent to the peers (no 682 retransmissions included)." 684 ::= { sctpScalars 16 } 686 sctpStatSentUnorderChunks OBJECT-TYPE 687 SYNTAX Counter32 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "Number of SCTP unordered chunks (data chunks in which the U 692 bit is set to 1) sent to the peers (no retransmissions 693 included)." 695 ::= { sctpScalars 17 } 697 sctpStatRecCtrlChunks OBJECT-TYPE 698 SYNTAX Counter32 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "Number of SCTP control chunks received from the peers (no 703 duplicated included)." 705 ::= { sctpScalars 18 } 707 sctpStatRecOrderChunks OBJECT-TYPE 708 SYNTAX Counter32 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "Number of SCTP ordered data chunks received from the peers 713 (no duplicated included)." 715 ::= { sctpScalars 19 } 717 sctpStatRecUnorderChunks OBJECT-TYPE 718 SYNTAX Counter32 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "Number of SCTP unordered chunks (data chunks in which the U 723 bit is set to 1) received from the peers (no duplicated 724 included)." 726 ::= { sctpScalars 20 } 728 sctpStatFragmentedUsrMessages OBJECT-TYPE 729 SYNTAX Counter32 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "Number of user messages that have to be fragmented because of 734 the MTU." 736 ::= { sctpScalars 21 } 738 sctpStatReassembledUsrMessages OBJECT-TYPE 739 SYNTAX Counter32 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "Number of user messages reassembled." 745 ::= { sctpScalars 22 } 747 sctpStatSentSCTPPacks OBJECT-TYPE 748 SYNTAX Counter32 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "Number of SCTP packets received from the peers." 754 ::= { sctpScalars 23 } 756 sctpStatRecSCTPPacks OBJECT-TYPE 757 SYNTAX Counter32 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "Number of SCTP packets received from the peers." 763 ::= { sctpScalars 24 } 765 -- SCTP ASSOCIATION DESCRIPTION PARAMETERS 766 -- *************************************** 768 -- the SCTP Association TABLE 769 -- ************************** 771 -- The SCTP association table contains information about each 772 -- association that the local endpoint is taking part. 774 sctpAssocTable OBJECT-TYPE 775 SYNTAX SEQUENCE OF SctpAssocEntry 776 MAX-ACCESS not-accessible 777 STATUS current 778 DESCRIPTION 779 "A table containing SCTP association-specific information." 781 ::= { sctpTables 1 } 783 sctpAssocEntry OBJECT-TYPE 784 SYNTAX SctpAssocEntry 785 MAX-ACCESS not-accessible 786 STATUS current 787 DESCRIPTION 788 "General common variables and statistics for the whole 789 association." 790 INDEX { sctpAssocId } 792 ::= { sctpAssocTable 1 } 794 SctpAssocEntry ::= SEQUENCE { 795 sctpAssocId Unsigned32, 796 sctpAssocRemHostName OCTET STRING, 797 sctpAssocLocalSCTPPort InetPortNumber, 798 sctpAssocRemSCTPPort InetPortNumber, 799 sctpAssocRemPrimaryAddressType InetAddressType, 800 sctpAssocRemPrimaryAddress InetAddress, 801 sctpAssocHeartBeatTimer Unsigned32, 802 sctpAssocState INTEGER, 803 sctpAssocInStreams Unsigned32, 804 sctpAssocOutStreams Unsigned32, 805 sctpAssocMaxRetr Unsigned32, 806 sctpAssocT1expireds Counter32, -- Statistic 807 sctpAssocT2expireds Counter32, -- Statistic 808 sctpAssocRtxChunks Counter32, -- Statistic 809 sctpAssocStartTime TimeStamp 810 } 812 sctpAssocId OBJECT-TYPE 813 SYNTAX Unsigned32 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "Association Identification. Value identifying the association 818 (typically the Initiate Verification Tag). 819 If the selected AssocID is the Initiate Verification Tag, this 820 value must not be zero." 822 ::= { sctpAssocEntry 1 } 824 sctpAssocRemHostName OBJECT-TYPE 825 SYNTAX OCTET STRING (SIZE(0..255)) 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "Peer's DNS name. If no DNS domain name was received at init 830 time (embedded in the INIT or INIT-ACK chunk) from the peer, 831 this entry will be meaningless, therefore it will contain a 832 NULL value. Otherwise, the remote host name received at init 833 time will be stored." 835 ::= { sctpAssocEntry 2 } 837 sctpAssocLocalSCTPPort OBJECT-TYPE 838 SYNTAX InetPortNumber 839 MAX-ACCESS read-only 840 STATUS current 841 DESCRIPTION 842 "Local SCTP port number used for this association. A zero 843 value means unknown according to the RFC-update." 845 ::= { sctpAssocEntry 3 } 847 sctpAssocRemSCTPPort OBJECT-TYPE 848 SYNTAX InetPortNumber 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "Remote SCTP port number used for this association. A zero 853 value means unknown according to the RFC2851-update." 855 ::= { sctpAssocEntry 4 } 857 sctpAssocRemPrimaryAddressType OBJECT-TYPE 858 SYNTAX InetAddressType 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "Internet type of primary destination IP address. 864 - unknown (0) An unknown address type. This value MUST be 865 used if the value of the corresponding InetAddress object 866 is a zero-length string. It may also be used to indicate an 867 IP address different from IPv4 or IPv6. This value is used 868 in this MIB for error conditions. 870 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 871 textual convention [RFC2851-update]. 873 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 874 textual convention [RFC2851-update]. It represents global 875 IPv6 addresses and non-global IPv6 addresses in case where 876 no zone index is needed. 878 - ipv4z(3): A non-global IPv4 address including a zone index 879 as defined by the InetAddressIPv4z textual convention 880 [RFC2851-update]. 882 - ipv6z(4): A non-global IPv6 address including a zone index 883 as defined by the InetAddressIPv6z textual convention 884 [RFC2851-update]. 886 This value will be filled in after the INIT or INIT ACK chunks 887 have been received (when the primary path is selected by 888 SCTP)." 890 ::= { sctpAssocEntry 5 } 892 sctpAssocRemPrimaryAddress OBJECT-TYPE 893 SYNTAX InetAddress 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "Primary destination IP address. An InetAddress value is 898 always interpreted within the context of an InetAddressType 899 value. 900 This value will be filled in after INIT or INIT ACK chunks 901 have been received (when the primary path is selected by 902 SCTP)." 904 ::= { sctpAssocEntry 6 } 906 sctpAssocHeartBeatTimer OBJECT-TYPE 907 SYNTAX Unsigned32 908 UNITS "milliseconds" 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION 912 "The current heartbeat time-out. The recommended default value 913 is 30000 milliseconds." 915 ::= { sctpAssocEntry 7 } 917 sctpAssocState OBJECT-TYPE 918 SYNTAX INTEGER { 919 closed(1), 920 cookieWait(2), 921 cookieEchoed(3), 922 established(4), 923 shutdownPending(5), 924 shutdownSent(6), 925 shutdownReceived(7), 926 shutdownAckSent(8), 927 deleteTCB(9) 928 } 929 MAX-ACCESS read-write 930 STATUS current 931 DESCRIPTION 932 "The state of this SCTP association. 933 As in TCP, deleteTCB is the only value that may be set by a 934 management station. Accordingly, it is appropriate for an 935 agent to return a 'badValue' response if a management station 936 attempts to set this object to any other value. 937 If a management station sets this object to the value 938 deleteTCB(9), then this has the effect of deleting the TCB (as 939 defined in SCTP) of the corresponding association on the 940 managed node, resulting in immediate termination of the 941 association. 942 As an implementation-specific option, an ABORT chunk may be 943 sent from the managed node to the other SCTP endpoint." 945 ::= { sctpAssocEntry 8 } 947 sctpAssocInStreams OBJECT-TYPE 948 SYNTAX Unsigned32 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "Inbound Streams according to the negotiation at association 953 start up. This parameter has to be read-only by the manager." 955 ::= { sctpAssocEntry 9 } 957 sctpAssocOutStreams OBJECT-TYPE 958 SYNTAX Unsigned32 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "Outbound Streams according to the negotiation at association 963 start up. This parameter has to be read-only by the manager." 965 ::= { sctpAssocEntry 10 } 967 sctpAssocMaxRetr OBJECT-TYPE 968 SYNTAX Unsigned32 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The maximum number of data retransmissions in the association 973 context. This value is specific for each association and the 974 upper layer can change it calling the appropriate primitives. 975 This value has to be smaller than the addition of all the 976 maximum number for all the paths 977 (sctpAssocRemAddressMaxPathRtx). 978 Recommended value: 10 attempts." 980 ::= { sctpAssocEntry 11 } 982 -- Association Statistics 984 sctpAssocT1expireds OBJECT-TYPE 985 SYNTAX Counter32 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION 989 "Number of times that T1 timer expired (timer for sending 990 either INIT or COOKIE-ECHO chunks and receiving an 991 acknowledgment)." 993 ::= { sctpAssocEntry 12 } 995 sctpAssocT2expireds OBJECT-TYPE 996 SYNTAX Counter32 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "Number of times that T2-shutdown timer expired (shutdown 1001 timer)." 1003 ::= { sctpAssocEntry 13 } 1005 sctpAssocRtxChunks OBJECT-TYPE 1006 SYNTAX Counter32 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "Number of data chunks retransmitted to the peer in the 1011 current association." 1013 ::= { sctpAssocEntry 14 } 1015 sctpAssocStartTime OBJECT-TYPE 1016 SYNTAX TimeStamp 1017 MAX-ACCESS read-only 1018 STATUS current 1019 DESCRIPTION 1020 "The value of SysUpTime at the time that this row was 1021 created." 1023 ::= { sctpAssocEntry 15 } 1025 -- Expanded tables: Including Multi-home feature 1027 -- Local Address TABLE 1028 -- ******************* 1030 sctpAssocLocalAddressTable OBJECT-TYPE 1031 SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "Expanded table of sctpAssocTable based on the AssocId index. 1036 This table shows data related to each local IP address which 1037 is used by this association." 1039 ::= { sctpTables 2 } 1041 sctpAssocLocalAddressEntry OBJECT-TYPE 1042 SYNTAX SctpAssocLocalAddressEntry 1043 MAX-ACCESS not-accessible 1044 STATUS current 1045 DESCRIPTION 1046 "Local information about the available addresses." 1047 INDEX { sctpAssocId, -- shared index 1048 sctpAssocLocalAddressIPType, 1049 sctpAssocLocalAddressIP } 1051 ::= { sctpAssocLocalAddressTable 1 } 1053 SctpAssocLocalAddressEntry ::= SEQUENCE { 1054 sctpAssocLocalAddressIPType InetAddressType, 1055 sctpAssocLocalAddressIP InetAddress, 1056 sctpAssocLocalAddressStartTime TimeStamp 1057 } 1059 sctpAssocLocalAddressIPType OBJECT-TYPE 1060 SYNTAX InetAddressType 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "Internet type of local IP address used for this association. 1066 - unknown (0) An unknown address type. This value MUST be 1067 used to indicate an IP address different from IPv4 or IPv6. 1068 This value is used in this MIB for error conditions. 1070 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 1071 textual convention [RFC2851-update]. 1073 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 1074 textual convention [RFC2851-update]. It represents global 1075 IPv6 addresses and non-global IPv6 addresses in case where 1076 no zone index is needed. 1078 - ipv4z(3): A non-global IPv4 address including a zone index 1079 as defined by the InetAddressIPv4z textual convention 1080 [RFC2851-update]. 1082 - ipv6z(4): A non-global IPv6 address including a zone index 1083 as defined by the InetAddressIPv6z textual convention 1084 [RFC2851-update]. " 1086 ::= { sctpAssocLocalAddressEntry 1 } 1088 sctpAssocLocalAddressIP OBJECT-TYPE 1089 SYNTAX InetAddress (SIZE(1..64)) 1090 MAX-ACCESS not-accessible 1091 STATUS current 1092 DESCRIPTION 1093 "The value of a local IP address available for this 1094 association. An InetAddress value is always interpreted within 1095 the context of an InetAddressType value. If SCTP is using a 1096 DNS name, the mapping to IP address/-es will be done at 1097 reception of INIT or INIT_ACK chunks. 1099 The sctpAssocRemAddressIP may not be empty due to the SIZE 1100 restriction." 1102 ::= { sctpAssocLocalAddressEntry 2 } 1104 sctpAssocLocalAddressStartTime OBJECT-TYPE 1105 SYNTAX TimeStamp 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "The value of SysUpTime at the time that this row was 1110 created." 1112 ::= { sctpAssocLocalAddressEntry 3 } 1114 -- Remote Addresses TABLE 1115 -- ********************** 1117 sctpAssocRemAddressTable OBJECT-TYPE 1118 SYNTAX SEQUENCE OF SctpAssocRemAddressEntry 1119 MAX-ACCESS not-accessible 1120 STATUS current 1121 DESCRIPTION 1122 "Expanded table of sctpAssocTable based on the AssocId index. 1123 This table shows data related to each remote peer IP address 1124 which is used by this association." 1126 ::= { sctpTables 3 } 1128 sctpAssocRemAddressEntry OBJECT-TYPE 1129 SYNTAX SctpAssocRemAddressEntry 1130 MAX-ACCESS not-accessible 1131 STATUS current 1132 DESCRIPTION 1133 "Information about the most important variables for every 1134 remote IP address " 1135 INDEX { sctpAssocId, -- shared index 1136 sctpAssocRemAddressIPType, 1137 sctpAssocRemAddressIP } 1139 ::= { sctpAssocRemAddressTable 1 } 1141 SctpAssocRemAddressEntry ::= SEQUENCE { 1142 sctpAssocRemAddressIPType InetAddressType, 1143 sctpAssocRemAddressIP InetAddress, 1144 sctpAssocRemAddressStatus INTEGER, 1145 sctpAssocRemAddressHBFlag INTEGER, 1146 sctpAssocRemAddressRTO Unsigned32, 1147 sctpAssocRemAddressMaxPathRtx Unsigned32, 1148 sctpAssocRemAddressRtx Counter32, -- Statistic 1149 sctpAssocRemAddressStartTime TimeStamp 1150 } 1152 sctpAssocRemAddressIPType OBJECT-TYPE 1153 SYNTAX InetAddressType 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "Internet type of a remote IP address available for this 1158 association. 1160 - unknown (0) An unknown address type. This value MUST be 1161 used to indicate an IP address different from IPv4 or IPv6. 1162 This value is used in this MIB for error conditions. 1164 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 1165 textual convention [RFC2851-update]. 1167 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 1168 textual convention [RFC2851-update]. It represents global 1169 IPv6 addresses and non-global IPv6 addresses in case where 1170 no zone index is needed. 1172 - ipv4z(3): A non-global IPv4 address including a zone index 1173 as defined by the InetAddressIPv4z textual convention 1174 [RFC2851-update]. 1176 - ipv6z(4): A non-global IPv6 address including a zone index 1177 as defined by the InetAddressIPv6z textual convention 1178 [RFC2851-update]. " 1180 ::= { sctpAssocRemAddressEntry 1 } 1182 sctpAssocRemAddressIP OBJECT-TYPE 1183 SYNTAX InetAddress (SIZE(1..64)) 1184 MAX-ACCESS not-accessible 1185 STATUS current 1186 DESCRIPTION 1187 "The value of a remote IP address available for this 1188 association. An InetAddress value is always interpreted within 1189 the context of an InetAddressType value. If SCTP is using a 1190 DNS name, the mapping to IP address/-es will be done at 1191 reception of INIT or INIT_ACK chunks 1193 The sctpAssocRemAddressIP may not be empty due to the SIZE 1194 restriction." 1196 ::= { sctpAssocRemAddressEntry 2 } 1198 sctpAssocRemAddressStatus OBJECT-TYPE 1199 SYNTAX INTEGER { 1200 active(0), 1201 inactive(1) 1202 } 1203 MAX-ACCESS read-only 1204 STATUS current 1205 DESCRIPTION 1206 "The current status of the remote transport address, according 1207 to [SCTP]. 1208 Active means that the threshold of no answer received from 1209 this IP address has not been reached. Inactive means that 1210 either no heartbeat was received from this address, or any 1211 other message, reaching the threshold defined by the 1212 protocol." 1214 ::= { sctpAssocRemAddressEntry 3 } 1216 sctpAssocRemAddressHBFlag OBJECT-TYPE 1217 SYNTAX INTEGER { 1218 active(0), 1219 inactive(1) 1220 } 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "The optional Heartbeat associated to one destination 1225 transport address could be active or not (value equal to 0 or 1226 1, respectively). 1228 An active destination transport address is the one considered 1229 available by a peer endpoint for receiving SCTP packets, as it 1230 is described in [sctp]." 1232 ::= { sctpAssocRemAddressEntry 4 } 1234 sctpAssocRemAddressRTO OBJECT-TYPE -- T3-rtx- Timer 1235 SYNTAX Unsigned32 1236 UNITS "milliseconds" 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "The current Retransmission Timeout. T3-rtx timer as defined 1241 in the protocol SCTP." 1243 ::= { sctpAssocRemAddressEntry 5 } 1245 sctpAssocRemAddressMaxPathRtx OBJECT-TYPE 1246 SYNTAX Unsigned32 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "Maximum number of DATA chunks retransmissions allowed to a 1251 remote IP address before it is considered inactive, as defined 1252 in [sctp]. Recommended value 5 attempts." 1254 ::= { sctpAssocRemAddressEntry 6 } 1256 -- Remote Address Statistic 1258 sctpAssocRemAddressRtx OBJECT-TYPE 1259 SYNTAX Counter32 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "Number of DATA chunks retransmissions as defined in [sctp]." 1265 ::= { sctpAssocRemAddressEntry 7 } 1267 sctpAssocRemAddressStartTime OBJECT-TYPE 1268 SYNTAX TimeStamp 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "The value of SysUpTime at the time that this row was 1273 created." 1275 ::= { sctpAssocRemAddressEntry 8 } 1277 -- ASSOCIATION INVERSE TABLE 1278 -- ************************* 1280 -- BY LOCAL PORT 1282 sctpLookupLocalPortTable OBJECT-TYPE 1283 SYNTAX SEQUENCE OF SctpLookupLocalPortEntry 1284 MAX-ACCESS not-accessible 1285 STATUS current 1286 DESCRIPTION 1287 "With the use of this table, a list of associations which are 1288 using the specified local port can be got" 1290 ::= { sctpTables 4 } 1292 sctpLookupLocalPortEntry OBJECT-TYPE 1293 SYNTAX SctpLookupLocalPortEntry 1294 MAX-ACCESS not-accessible 1295 STATUS current 1296 DESCRIPTION 1297 "This table is indexed by local port and association ID. 1298 Specifying a local port, we would get a list of the 1299 associations whose local port is the one specified" 1301 INDEX { sctpAssocLocalSCTPPort, 1302 sctpAssocId } 1304 ::= { sctpLookupLocalPortTable 1 } 1306 SctpLookupLocalPortEntry::= SEQUENCE { 1307 sctpLookupLocalPortStartTime TimeStamp 1308 } 1310 sctpLookupLocalPortStartTime OBJECT-TYPE 1311 SYNTAX TimeStamp 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "The value of SysUpTime at the time that this row was 1316 created." 1318 ::= { sctpLookupLocalPortEntry 1 } 1320 -- BY REMOTE PORT 1321 sctpLookupRemPortTable OBJECT-TYPE 1322 SYNTAX SEQUENCE OF SctpLookupRemPortEntry 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "With the use of this table, a list of associations which are 1327 using the specified remote port can be got" 1329 ::= { sctpTables 5 } 1331 sctpLookupRemPortEntry OBJECT-TYPE 1332 SYNTAX SctpLookupRemPortEntry 1333 MAX-ACCESS not-accessible 1334 STATUS current 1335 DESCRIPTION 1336 "This table is indexed by remote port and association ID. 1337 Specifying a remote port we would get a list of the 1338 associations whose local port is the one specified " 1340 INDEX { sctpAssocRemSCTPPort, 1341 sctpAssocId } 1343 ::= { sctpLookupRemPortTable 1 } 1345 SctpLookupRemPortEntry::= SEQUENCE { 1346 sctpLookupRemPortStartTime TimeStamp 1347 } 1349 sctpLookupRemPortStartTime OBJECT-TYPE 1350 SYNTAX TimeStamp 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The value of SysUpTime at the time that this row was 1355 created." 1357 ::= { sctpLookupRemPortEntry 1 } 1359 -- BY REMOTE HOST NAME 1361 sctpLookupRemHostNameTable OBJECT-TYPE 1362 SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry 1363 MAX-ACCESS not-accessible 1364 STATUS current 1365 DESCRIPTION 1366 "With the use of this table, a list of associations with that 1367 particular host can be got" 1369 ::= { sctpTables 6 } 1371 sctpLookupRemHostNameEntry OBJECT-TYPE 1372 SYNTAX SctpLookupRemHostNameEntry 1373 MAX-ACCESS not-accessible 1374 STATUS current 1375 DESCRIPTION 1376 "This table is indexed by remote host name and association ID. 1377 Specifying a host name we would get a list of the associations 1378 specifying that host name as the remote one" 1380 INDEX { sctpAssocRemHostName, 1381 sctpAssocId } 1383 ::= { sctpLookupRemHostNameTable 1 } 1385 SctpLookupRemHostNameEntry::= SEQUENCE { 1386 sctpLookupRemHostNameStartTime TimeStamp 1387 } 1389 sctpLookupRemHostNameStartTime OBJECT-TYPE 1390 SYNTAX TimeStamp 1391 MAX-ACCESS read-only 1392 STATUS current 1393 DESCRIPTION 1394 "The value of SysUpTime at the time that this row was 1395 created." 1397 ::= { sctpLookupRemHostNameEntry 1 } 1399 -- BY REMOTE PRIMARY IP ADDRESS 1401 sctpLookupRemPrimIPAddrTable OBJECT-TYPE 1402 SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry 1403 MAX-ACCESS not-accessible 1404 STATUS current 1405 DESCRIPTION 1406 "With the use of this table, it can be got a list of 1407 associations that have that the specified IP address as 1408 primary within the remote set of active addresses " 1410 ::= { sctpTables 7 } 1412 sctpLookupRemPrimIPAddrEntry OBJECT-TYPE 1413 SYNTAX SctpLookupRemPrimIPAddrEntry 1414 MAX-ACCESS not-accessible 1415 STATUS current 1416 DESCRIPTION 1417 "This table is indexed by primary address and association ID. 1418 Specifying a primary address, we would get a list of the 1419 associations that have the specified remote IP address marked 1420 as primary. " 1422 INDEX { sctpAssocRemPrimaryAddressType, 1423 sctpAssocRemPrimaryAddress, 1424 sctpAssocId } 1426 ::= { sctpLookupRemPrimIPAddrTable 1 } 1428 SctpLookupRemPrimIPAddrEntry::= SEQUENCE { 1429 sctpLookupRemPrimIPAddrStartTime TimeStamp 1430 } 1432 sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE 1433 SYNTAX TimeStamp 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "The value of SysUpTime at the time that this row was 1438 created." 1440 ::= { sctpLookupRemPrimIPAddrEntry 1 } 1442 -- BY REMOTE IP ADDRESS 1444 sctpLookupRemIPAddrTable OBJECT-TYPE 1445 SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry 1446 MAX-ACCESS not-accessible 1447 STATUS current 1448 DESCRIPTION 1449 "With the use of this table, a list of associations that have 1450 the specified IP address as one of the remote ones can be got" 1452 ::= { sctpTables 8 } 1454 sctpLookupRemIPAddrEntry OBJECT-TYPE 1455 SYNTAX SctpLookupRemIPAddrEntry 1456 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1459 "This table is indexed by a remote IP address and association 1460 ID. Specifying an IP address we would get a list of the 1461 associations that have the specified IP address included 1462 within the set of remote IP addresses" 1464 INDEX { sctpAssocRemAddressIPType, 1465 sctpAssocRemAddressIP, 1466 sctpAssocId } 1468 ::= { sctpLookupRemIPAddrTable 1 } 1470 SctpLookupRemIPAddrEntry::= SEQUENCE { 1471 sctpLookupRemIPAddrStartTime TimeStamp 1472 } 1474 sctpLookupRemIPAddrStartTime OBJECT-TYPE 1475 SYNTAX TimeStamp 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "The value of SysUpTime at the time that this row was 1480 created." 1482 ::= { sctpLookupRemIPAddrEntry 1 } 1484 -- 4.1 Conformance Information 1486 sctpGroups OBJECT IDENTIFIER ::= { sctpConformance 1 } 1487 sctpCompliances OBJECT IDENTIFIER ::= { sctpConformance 2 } 1489 -- 4.1.1 Units of conformance 1491 -- 1492 -- MODULE GROUPS 1493 -- 1495 sctpGeneralVariablesGroup OBJECT-GROUP 1496 OBJECTS { sctpRtoAlgorithm, 1497 sctpRtoMin, 1498 sctpRtoMax, 1499 sctpRtoInitial, 1500 sctpMaxAssoc, 1501 sctpValCookieLife, 1502 sctpMaxInitRetr 1503 } 1505 STATUS current 1506 DESCRIPTION 1507 "Common parameters for all the associations. They can usually 1508 be referred as configuration parameters" 1510 ::= { sctpGroups 1 } 1512 sctpStateStatGroup OBJECT-GROUP 1513 OBJECTS {sctpCurrEstab, 1514 sctpActiveEstabs, 1515 sctpPassiveEstabs, 1516 sctpAborteds, 1517 sctpShutdowns 1518 } 1520 STATUS current 1521 DESCRIPTION 1522 "The sctp group of objects to control state changes in the 1523 SCTP protocol local layer. They include the data for all the 1524 associations." 1526 ::= { sctpGroups 2 } 1528 sctpOtherStatGroup OBJECT-GROUP 1529 OBJECTS {sctpStatOutOfBlues, 1530 sctpStatChecksumErrors, 1531 sctpStatSentCtrlChunks, 1532 sctpStatSentOrderChunks, 1533 sctpStatSentUnorderChunks, 1534 sctpStatRecCtrlChunks, 1535 sctpStatRecOrderChunks, 1536 sctpStatRecUnorderChunks, 1537 sctpStatFragmentedUsrMessages, 1538 sctpStatReassembledUsrMessages, 1539 sctpStatSentSCTPPacks, 1540 sctpStatRecSCTPPacks 1541 } 1543 STATUS current 1544 DESCRIPTION 1545 "The sctp group of objects providing for management of SCTP 1546 most common statistics for the local SCTP layer." 1548 ::= { sctpGroups 3 } 1550 sctpAssocTablesVariablesGroup OBJECT-GROUP 1551 OBJECTS {sctpAssocRemHostName, 1552 sctpAssocLocalSCTPPort, 1553 sctpAssocRemSCTPPort, 1554 sctpAssocRemPrimaryAddressType, 1555 sctpAssocRemPrimaryAddress, 1556 sctpAssocHeartBeatTimer, 1557 sctpAssocState, 1558 sctpAssocInStreams, 1559 sctpAssocOutStreams, 1560 sctpAssocMaxRetr, 1561 sctpAssocT1expireds, 1562 sctpAssocT2expireds, 1563 sctpAssocRtxChunks, 1564 sctpAssocStartTime, 1565 sctpAssocLocalAddressStartTime, 1566 sctpAssocRemAddressStatus, 1567 sctpAssocRemAddressHBFlag, 1568 sctpAssocRemAddressRTO, sctpAssocRemAddressMaxPathRtx, 1569 sctpAssocRemAddressStartTime 1570 } 1572 STATUS current 1573 DESCRIPTION 1574 "The sctp group of objects to manage specific local and remote 1575 SCTP variables (local and remote tables). These variables 1576 include all the SCTP basic features." 1578 ::= { sctpGroups 4 } 1580 sctpAssocStatGroup OBJECT-GROUP 1581 OBJECTS {sctpAssocRemAddressRtx 1582 } 1584 STATUS current 1585 DESCRIPTION 1586 "The sctp group of objects to manage SCTP statistics related 1587 to the remote endpoint." 1589 ::= { sctpGroups 5 } 1591 sctpInverseGroup OBJECT-GROUP 1592 OBJECTS {sctpLookupLocalPortStartTime, 1593 sctpLookupRemPortStartTime, 1594 sctpLookupRemHostNameStartTime, 1595 sctpLookupRemPrimIPAddrStartTime, 1596 sctpLookupRemIPAddrStartTime 1597 } 1599 STATUS current 1600 DESCRIPTION 1601 "Objects used in the inverse lookup table." 1603 ::= { sctpGroups 6 } 1605 -- 4.1.2 Compliance Statements 1607 -- 1608 -- MODULE COMPLIANCES 1609 -- 1611 sctpCompliance MODULE-COMPLIANCE 1612 STATUS current 1613 DESCRIPTION 1614 "The compliance statement for SNMPv3 entities which implement 1615 SCTP. 1617 The SCTP MIB specifies in this compliant implementation that 1618 only need to support IPv4/IPv6 addresses without a zone index, 1619 unknown type and DNS names. Support for IPv4/IPv6 addresses 1620 without zone indices is not required." 1622 MODULE -- this module 1624 MANDATORY-GROUPS { sctpGeneralVariablesGroup, 1625 sctpAssocTablesVariablesGroup 1626 } 1628 GROUP sctpStateStatGroup 1629 DESCRIPTION 1630 "The sctp group of objects to control state changes in 1631 the SCTP protocol." 1633 GROUP sctpOtherStatGroup 1634 DESCRIPTION 1635 "The sctp group of objects providing for management of 1636 SCTP general statistics." 1638 GROUP sctpAssocStatGroup 1639 DESCRIPTION 1640 "The sctp group of objects to manage SCTP statistics 1641 related to the remote endpoint." 1643 GROUP sctpInverseGroup 1644 DESCRIPTION 1645 "Objects used in inverse lookup tables. This should be 1646 implemented for easier lookups in the association 1647 tables." 1649 OBJECT sctpAssocRemPrimaryAddressType 1650 SYNTAX InetAddressType { unknown(0), 1651 ipv4(1), 1652 ipv6(2), 1653 dns(16) 1654 } 1655 DESCRIPTION 1656 "It is only required to have IPv4 and IPv6 addresses 1657 without zone indices. Unknown values must also be 1658 supported in case the IP address has a zero string length 1659 or an invalid/unknown format." 1661 OBJECT sctpAssocLocalAddressIPType 1662 SYNTAX InetAddressType { unknown(0), 1663 ipv4(1), 1664 ipv6(2), 1665 dns(16) 1666 } 1667 DESCRIPTION 1668 "It is only required to have IPv4 and IPv6 addresses 1669 without zone indices. Unknown values must also be 1670 supported in case the IP address has an invalid/unknown 1671 format " 1673 OBJECT sctpAssocRemAddressIPType 1674 SYNTAX InetAddressType { unknown(0), 1675 ipv4(1), 1676 ipv6(2), 1677 dns(16) 1678 } 1679 DESCRIPTION 1680 "It is only required to have IPv4 and IPv6 addresses 1681 without zone indices. Unknown values must also be 1682 supported in case the IP address has an invalid/unknown 1683 format " 1685 ::= { sctpCompliances 1 } 1687 END 1689 5. References 1691 [sctp] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J. 1692 Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. 1693 Paxson, "Stream Control Transmission Protocol", RFC 2960, 1694 October 2000. 1696 [MIBMPLS] Cucchiara et al. "Definnitions of Managed Objects for the 1697 Multiprotocol Label Switching, Label Distribution Protocol 1698 (LDP)", Internet Draf , January 1699 2000. 1701 [SecSNMP] Stallings, W., "SNMP3: A Security Enhancement for SNMP", 1702 IEEE Communication Surveys, Forth quarter 1998, Vol. 1 No. 1. 1704 [Cong] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1705 1988, Stanford, California. 1707 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1708 Transmission Control Protocol using SMIv2", RFC 2012, November 1709 1996. 1711 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1712 Architecture for Describing SNMP Management Frameworks", RFC 1713 2571, April 1999. 1715 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1716 of Management Information for TCP/IP-based Internets", STD 16, 1717 RFC 1155, May 1990. 1719 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1720 16, RFC 1212, March 1991. 1722 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1723 SNMP", RFC 1215, March 1991. 1725 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1726 Rose, M., and S. Waldbusser, "Structure of Management 1727 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1729 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1730 Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", 1731 STD 58, RFC 2579, April 1999. 1733 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1734 Rose, M., and S. Waldbusser, "Conformance Statements for 1735 SMIv2", STD 58, RFC 2580, April 1999. 1737 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1738 Network Management Protocol", STD 15, RFC 1157, May 1990. 1740 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1741 "Introduction to Community-based SNMPv2", RFC 1901, January 1742 1996. 1744 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1745 "Transport Mappings for Version 2 of the Simple Network 1746 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1748 [RFC2452] M. Daniele, "IP Version 6 Management Information Base for 1749 the Transmission Control Protocol", RFC 2452, December 1998 1751 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1752 "Message Processing and Dispatching for the Simple Network 1753 Management Protocol (SNMP)", RFC 2572, April 1999. 1755 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1756 (USM) for version 3 of the Simple Network Management Protocol 1757 (SNMPv3)", RFC 2574, April 1999. 1759 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1760 "Protocol Operations for Version 2 of the Simple Network 1761 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1763 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1764 RFC 2573, April 1999. 1766 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1767 Access Control Model (VACM) for the Simple Network Management 1768 Protocol (SNMP)", RFC 2575, April 1999. 1770 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1771 "Introduction to Version 3 of the Internet-standard Network 1772 Management Framework", RFC 2570, April 1999. 1774 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1775 Requirement Levels", BCP 14, RFC 2119, Harvard University, 1776 March 1997 1778 [RFC2851-update] M. Daniele, B. Haberman, S. Routhier, J. 1779 Schoenwaelder, "Textual Conventions for Internet Network 1780 Addresses", draft-ietf-ops-rfc2851-update-05.txt, October 31, 1781 2001. Work in progress. 1783 [TADDRESS] M. Daniele , J. Schoenwaelder , "Textual Conventions for 1784 Transport Addresses", draft-ietf-ops-taddress-mib-01.txt, 1785 September 17, 2001. Work in progress. 1787 [TCPMIB] Management Information Base for the Transmission Control 1788 Protocol (TCP), draft-ietf-ipngwg-rfc2012-update-00.txt, July 1789 2001. Work in progress. 1791 [UDPMIB] Bill Fenner, Brian Haberman, Keith McCloghrie, Juergen 1792 Schoenwalder, Dave Thaler, "Management Information Base for 1793 User Datagram Protocol (UDP)", draft-ietf-ipngwg-rfc2013- 1794 update-00.txt, July 2001. Work in progress. 1796 [IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, 1797 A. and B. Zill, "IPv6 Scoped Address Architecture", draft- 1798 ietf-ipngwg-scoping-arch-02.txt, September 2001. Work in 1799 progress. 1801 6. Security Consideration 1803 There are a number of management objects defined in this MIB that 1804 have a MAX-ACCESS clause of read-write and/or read-create. Such 1805 objects may be considered sensitive or vulnerable in some network 1806 environments. The support for SET operations in a non-secure 1807 environment without proper protection can have a negative effect on 1808 network operations. 1810 It is thus important to control even GET access to these objects and 1811 possibly to even encrypt the values of these object when sending them 1812 over the network via SNMP. Not all versions of SNMP provide features 1813 for such a secure environment. 1815 SNMPv1 by itself is not a secure environment. Even if security 1816 measures are taken (e.g., using IPSEC), there is no per-user control 1817 as to who (once an IPSEC association is established between hosts) is 1818 allowed to GET or SET the objects in this MIB 1820 It is recommended that the implementers consider the security 1821 features as provided by the SNMPv3 framework. Specifically, the use 1822 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1823 based Access Control Model RFC 2575 [RFC2575] is recommended. 1825 It is then a customer/user responsibility to ensure that the SNMP 1826 entity giving access to an instance of this MIB, is properly 1827 configured to give access to the objects only to those principals 1828 (users) that have legitimate rights to indeed GET or SET 1829 (change/create/delete) them. 1831 7. Acknowledgments 1833 The authors wish to thank David Partain, Ed Yarwood and Shyamal 1834 Prasad for their invaluable comments. 1836 8. Authors' Addresses 1838 Javier Pastor-Balbas Tel: +34-91-339-3819 1839 Ericsson Espana S.A. eMail: J.Javier.Pastor@ericsson.com 1840 Network Communication Services 1841 Ombu 3, 4th floor 1842 Madrid, 28045 1843 Spain 1845 Maria-Carmen Belinchon Tel: +34-91-339-3535 1846 Ericsson Espana S.A. eMail: Maria.C.Belinchon@ericsson.com 1847 Network Communication Services 1848 Ombu 3, 4th floor 1849 Madrid, 28045 1850 Spain 1852 9. Revision History 1854 9.1 Changes from 1856 o Open issues updated 1858 o Section 2: Reference to RFC227x changed to RFC257x 1860 o Section 4: Inside the sctpRtoAlgorithm definition has been put 1861 "other" first rather than last. That way, it won't end up in the 1862 middle of things when new enumerations are added later. 1864 9.2 Changes from 1866 o Change of "Simple" word to "Stream" word in SCTP acronyms 1868 o Version of the MIB based on SCTPv10 1870 o Section 2: Update SNMP Framework to include the standard 1871 explanation 1873 o New Structure for the MIB: 1874 sctpMIB 1875 \- sctpObjects 1876 \- sctpScalars 1877 \- sctpTables 1878 \- sctpConformance 1880 o Section 4.1.2: Unit of Conformance updated (functional structure). 1882 o MAX-ACCESS clauses reviewed 1884 o The general statistics has been re-ordered, placed before the 1885 tables. 1887 o In SMIv2, indexes should be not-accessible (= the object type is a 1888 column in a table used as index and may not be used as an operand in 1889 any operation != SMIv1) (pp109-110 in []) 1890 o IPv6 compatible: 1891 - Change of Primary/Local/Remote addresses 1892 - PENDING: check "MODULE-COMPLIANCE" 1894 o Row Status included in AssocTable, AssocLocal and AssocRem to 1895 create, modify and delete rows in the tables. 1897 o SCTP general statistics changed from Counter32 to Counter64 since 1898 it supports more data changes. 1900 o sctpCurrEstab ("State-related variables and statistics" section) 1901 variable changed from Gauge32 to Counter32. 1903 o sctpAssocRemAddressT1expired and sctpAssocRemAddressT2expired have 1904 been removed from the remote table and added in the general 1905 association data since they are variables per association (not per IP 1906 address). 1908 o sctpAssocDropDatag statistic has been removed from the general 1909 association statistics since it had an ambiguous meaning. 1911 o Explained the meaning of the unordered chunks (chunks in which the 1912 U bit is set to 1) in sctpStatOutOfOrderSentChunks and 1913 sctpStatOutOfOrderRecChunks. 1915 o Added sctpChecksumErrorCounter to collect information about wrong 1916 checksums received from the peer. 1918 o Specify that sctpStatSentChunks and sctpStatRecChunks does not 1919 contain retransmission chunks. 1921 o Reword the Security Considerations chapter pointing out that IPsec 1922 does not secure the network but it provides end-to-end security over 1923 a network. 1925 o sctpAssocRemAddressRtxChunks replaced as a variable per 1926 association, meaning the number of chunks retransmited to the peer in 1927 the current association. 1929 o sctpHeartBeatMisses and sctpMaxRetr have been replaced from the 1930 general SCTP statistics to the remote IP address table 1931 (sctpHeartBeatMisses) and in the association table (sctpMaxRetr). 1933 o Specify that the retransmissions in the general SCTP statistics 1934 include control plus data chunks. 1936 o Included heartbeat timer for remote IP address. 1938 o Removed sctpAssocRemAddressHeartBeatMisses variable from the remote 1939 IP address table. 1941 o Removed sctpAssocRemAddressT3expired variable from the remote IP 1942 address table. 1944 o Updated variables to the new SCTP states defined in v10. 1946 9.3 Changes from 1948 o sctpRtoMin - stray "." outside the double-quotes in the DESCRIPTION 1949 clause. 1951 o sctpRtoMax - stray "." outside the double-quotes in the DESCRIPTION 1952 clause. 1954 o sctpAssocRemHostName - the type OCTECT STRING should be OCTET 1955 STRING. 1957 o sctpAssocRemPrimaryAddress - the DESCRIPTION clause is missing its 1958 closing ouble-quote. 1960 o sctpConformance - this is defined as { sctpMIB 2 }, then never 1961 used; instead sctpMIBConformance (which is undefined) is used in the 1962 definition of sctpMIBGroups and sctpMIBCompliances. 1964 o Reworded the MIB organization 1966 o Removed maximum number of concurrent associations 1968 o In sctpMIBCompliance, removed a missing comma in MANDATORY-GROUPS. 1970 o In sctpAssocTablesVariablesGroup and sctpAssocStatGroup, removed 1971 extra commas at end of OBJECTS list. 1973 o sctpAssocInStreams. ACCESS changed from read-create to read-only. 1975 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1976 changed from per remote IP address to per association. 1978 o Comment on sctpAssocRemAddressHBTimer specifies now that the 1979 manager can change it. 1981 o ACCESS on sctpAssocRemAddressHBTimer changed from read-only to 1982 read-write. 1984 o ACCESS on sctpAssocRemAddressRetransCount changed from read-write 1985 to read-only. 1987 o Move sctpStatChecksumErrorCounter from general statistics to per 1988 association. 1990 o sctpMaxInStreams � It�s a sctp-user feature. 1992 o sctpStatRetransChunks � It�s more useful to have this statistic in 1993 a association basis 1995 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1996 have been created again instead of per association in order to follow 1997 the draft. If some implementations want to have the same value for 1998 all the associations they have, they should set all the variables in 1999 the different remote addresses to the same value. 2001 9.3 Changes from 2003 o Deleting all the RowStatus Structure. Associated text rewording in 2004 Tables section. 2006 o Variable StartTime added in all the tables in order to specify the 2007 creation time. 2009 o Adding the Association reverse lookup table for easier management. 2010 Associated text rewording in tables section. 2012 o Remove sctpInitialT1 and sctpInitialT2, since these values are 2013 equal to RTO. 2015 o Change of the Heartbeats to a per-association basis 2017 o Conformance up-to-date with all of this. 2019 9.4 Changes from 2021 Main changes are due to the alignment with the TCP and UDP MIBs and 2022 the inclusion of new lookup tables. 2023 o Convert MIB to a read-only 2025 o Counters ends with �s� 2027 o Include �unknown� as an option for InetAddressType in conformance 2029 o Terminology fix: CLOSED state, unordered chunks instead of out-of- 2030 order, .. 2032 o HBFlag changed to per remote address 2034 o ChecksumErrors out of the AssocTable and hangs from Scalars 2036 o Update Ports from Unsigned32 to InetPortNumber according to 2037 RFC2851-update 2038 o Rework inverse tables: five new lookup tables 2040 o Remove INTEGER32 and change it to UNSIGNED32 2042 o Replace Counter32 by Counter64 2044 o Split Sent and Received chunks per association into control, 2045 ordered and unordered chunks 2047 9.5 Changes from 2049 Changes due to the IETF-51 meeting and requests from the mailing 2050 list. 2051 o Typo errors 2053 o Objects renumbering 2055 o All counters to Counter32 to be backward compatible, not to waste 2056 memory. Operators needing more than 32 bits will do it by 2057 augmentations. 2059 o Limit the number of IP address size when index 2061 o Specify that a port number with value zero means unknown port 2062 number according to the RFC2851-update 2064 Changes due to the alignment with the RFC2851-update. 2066 o Include clarification text of the IP address types supported in the 2067 SCTP MIB. Chapter 3.1.2.1 (Association table) 2069 o Remote Primary IP address: Addition of the ipv4z an ipv6z types for 2070 non-globally IP addresses in which a scope identifier is needed. 2071 Addition of the scope of ipv6 type. All of them according to the 2072 RFC2851-update v04 2074 o InetAddressType for local and remote IP addresses: 2076 Limit UNKNOWN type only for unknown IP address format. Remove UNKNOWN 2077 type for zero-length value in the InetAddress since it will be never 2078 zero-length due to the size restriction (0..64) 2080 Addition of the ipv4z an ipv6z types for non-globally IP addresses in 2081 which a scope identifier is needed. Addition of the scope of ipv6 2082 type. All of them according to the RFC2851-update v04 2084 o Clarify when mapping DNS <-> IPaddress occurs with the remote IP 2085 addresses 2086 o Conformance: 2088 Description: Specify that the SCTP MIB only need to support IPv4/IPv6 2089 addresses without a zone index, unknown type and DNS names. Support 2090 for IPv4/IPv6 addresses with zone indices is not required. 2092 InetAddressType for primary, local and remote IP addresses: Clarify 2093 that the implementation is only required to support IPv4 and IPv6 2094 address types without zone indices. Clarify also that UNKONWN type is 2095 only used in case of local and remote addresses when invalid/unknown 2096 IP address format 2098 InetAddress value of primary, local and remote IP address: Removal of 2099 the InetAddress values supported. Limitation of the supported IP 2100 address types is already included in the InetAddressType 2102 o Revision of the RFC2851-update v05. Changes in this draft does not 2103 affect the SCTP MIB.