idnits 2.17.1 draft-ietf-sigtran-sctp-mib-07.txt: -(370): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1673): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2004): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2038): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(2162): 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 10 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 46 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 187 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 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2038 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: 'RFC1902' is mentioned on line 142, but not defined ** Obsolete undefined reference: RFC 1902 (Obsoleted by RFC 2578) == Missing Reference: 'RFC1903' is mentioned on line 142, but not defined ** Obsolete undefined reference: RFC 1903 (Obsoleted by RFC 2579) == Missing Reference: 'RFC1904' is mentioned on line 143, but not defined ** Obsolete undefined reference: RFC 1904 (Obsoleted by RFC 2580) == Missing Reference: 'RFC2272' is mentioned on line 151, but not defined ** Obsolete undefined reference: RFC 2272 (Obsoleted by RFC 2572) == Missing Reference: 'RFC2273' is mentioned on line 158, but not defined ** Obsolete undefined reference: RFC 2273 (Obsoleted by RFC 2573) == 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: 'RFC2452' is defined on line 1739, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1742, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 1749, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1753, but no explicit reference was found in the text == Unused Reference: 'RFC2576' is defined on line 1764, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1768, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1772, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1776, but no explicit reference was found in the text == Unused Reference: 'RFC2576-update' is defined on line 1780, but no explicit reference was found in the text == Unused Reference: 'IPv6ARCH' is defined on line 1793, but no explicit reference was found in the text == Unused Reference: 'UDPMIB' is defined on line 1806, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2960 (Obsoleted by RFC 4960) -- Possible downref: Non-RFC (?) normative reference: ref. 'SecSNMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'Cong' ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2012 (Obsoleted by RFC 4022) ** Obsolete normative reference: RFC 2452 (Obsoleted by RFC 4022, RFC 8096) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2576 (Obsoleted by RFC 3584) == Outdated reference: A later version (-04) exists of draft-ietf-snmpv3-coex-v2-01 == Outdated reference: A later version (-04) exists of draft-ietf-ipngwg-scoping-arch-03 -- Possible downref: Normative reference to a draft: ref. 'IPv6ARCH' == 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' Summary: 28 errors (**), 0 flaws (~~), 27 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Pastor 3 INTERNET-DRAFT M. Belinchon 4 Expires: August 2002 Ericsson 6 February, 2002 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 should be placed. This value will be obtained when 57 submitted to the IETF queue. 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 Objets.....................................................5 71 3.1.1 SCTP Statistics...............................................5 72 3.1.2 SCTP Parameters...............................................6 73 3.1.3 MIB Tables....................................................6 74 3.1.3.1 Association Table..........................................7 75 3.1.3.2 Reverse Lookup Table.......................................9 76 3.2 Conformance....................................................10 77 4. Definitions.....................................................10 78 5. Compiling Notes.................................................36 79 6. References......................................................36 80 7. Security Consideration..........................................39 81 8. Acknowledgments.................................................40 82 9. Authors' Addresses..............................................40 83 10. Revision History...............................................40 84 10.1 Changes from .......................40 85 10.2 Changes from .............40 86 10.3 Changes from .............42 87 10.3 Changes from .............43 88 10.4 Changes from .............43 89 10.5 Changes from .............44 90 10.6 Changes from .............45 91 10.7 Changes from .............46 93 1. Introduction 95 This memo defines the Management Information Base (MIB) module which 96 describes managed objects for implementations of the SCTP. 98 The document starts with a brief description of the SNMP framework 99 and continues with the MIB explanation and security consideration 100 among others. 102 The managed objects in this MIB module have been based on [RFC2012] 103 update: "Management Information Base for the Transmission Control 104 Protocol (TCP)" [TCPMIB], work in progress, and the RFC 2851 update 105 "Textual Conventions for Internet Network Addresses" [TADDRESS], work 106 in progress. 108 Terms related to the SCTP architecture are explained in [RFC2960]. 109 Other specific abbreviations are listed below. 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in [RFC2119]. 115 1.1 Abbreviations 117 DNS - Domain Name System 118 IANA - Internet Assigned Numbers Authority 119 ICANN - Internet Corporation for Assigned Names and Numbers 120 IETF - Internet Engineering Task Force 121 IP - Internet Protocol 122 MIB - Management Information Base 123 RFC - Request For Comment 124 RTO - Retransmission Time Out 125 SCTP - Stream Control Transmission Protocol 126 SMI - Structure of Management Information 127 SNMP - Simple Network Management Protocol 128 TCB - Transmission Control Block 129 TCP - Transmission Control Protocol 131 2. The SNMP Framework 133 The SNMP Management Framework presently consists of five major 134 components: 136 - An overall architecture, described in [RFC2571]. 138 - Mechanisms for describing and naming objects and events for the 139 purpose of management. The first version of this Structure of 140 Management Information (SMI) is called SMIv1 and described in 141 [RFC1155] , [RFC1212] and [RFC1215]. The second version, 142 called SMIv2, is described in [RFC1902], [RFC1903] and 143 [RFC1904]. 145 - Message protocols for transferring management information. The 146 first version of the SNMP message protocol is called SNMPv1 and 147 described in [RFC1157]. A second version of the SNMP message 148 protocol, which is not an Internet standards track protocol, is 149 called SNMPv2c and described in [RFC1901] and [RFC1906]. The 150 third version of the message protocol is called SNMPv3 and 151 described in [RFC1906], [RFC2272] and [RFC2574]. 153 - Protocol operations for accessing management information. The 154 first set of protocol operations and associated PDU formats is 155 described in [RFC1157]. A second set of protocol operations 156 and associated PDU formats is described in [RFC1905]. 158 - A set of fundamental applications described in [RFC2273] and 159 the view-based access control mechanism described in [RFC2575]. 161 Managed objects are accessed via a virtual information store, termed 162 the Management Information Base or MIB. Objects in the MIB are 163 defined using the mechanisms defined in the SMI. This memo specifies 164 a MIB module that is compliant to the SMIv2. A MIB conforming to the 165 SMIv1 can be produced through the appropriate translations. The 166 resulting translated MIB must be semantically equivalent, except 167 where objects or events are omitted because no translation is 168 possible (use of Counter64). Some machine-readable information in 169 SMIv2 will be converted into textual descriptions in SMIv1 during the 170 translation process. However, this loss of machine-readable 171 information is not considered to change the semantics of the MIB. 173 3. MIB Structure 175 This chapter will explain the main objects this MIB defines. A 176 detailed view of the MIB structure with the OID values is below. 178 MIB-2 {1 3 6 1 2 2} 179 +--(xxx)sctpMIB 180 | 181 +--(1) sctpObjects 182 | | 183 | +--(1) sctpStats 184 | | | 185 | | +-- 186 | | 187 | +--(2)sctpParameters 188 | | | 189 | | +-- 190 | | 191 | +--(3) sctpAssocTable 192 | | 193 | +--(4) sctpAssocLocalAddressTable 194 | | 195 | +--(5) sctpAssocRemAddressTable 196 | | 197 | +--(6) sctpLookupLocalPortTable 198 | | 199 | +--(7) sctpLookupRemPortTable 200 | | 201 | +--(8) sctpLookupRemHostNameTable 202 | | 203 | +--(9) sctpLookupRemPrimIPAddrTable 204 | | 205 | +--(10) sctpLookupRemIPAddrTable 206 | 207 | 208 +--(2)sctpConformance 209 | 210 +--(1) sctpCompliances 211 | | 212 | +--(1) sctpCompliance 213 | 214 +--(2) sctpGroups 215 | 216 +--(1) sctpParametersGroup 217 | 218 +--(2) sctpStatGroup 219 | 220 +--(3) sctpAssocTableParametersGroup 221 | 222 +--(4) sctpInverseGroup 224 The main groups are further explained along the MIB definition. 226 3.1 SCTP Objets 228 This branch contains the SCTP statistics and general parameters (both 229 of them scalars) and the SCTP MIB tables. 231 3.1.1 SCTP Statistics 232 SCTP MIB includes both Counter32 and Counter64 to deal with 233 statistics. Counter64 has been applied to those counters, which are 234 likely to wrap around in less than one hour, according to [RFC2863]. 236 In addition Gauge32 is also used. 238 3.1.1.1 State-Related Statistics 240 These measures are based in the TCP model, but adapted to the SCTP 241 states. They store the number of succeeded association attempts, how 242 many associations have been initiated by the local or the remote SCTP 243 layer, or just the number of associations terminated in a graceful 244 (by means of SHUTDOWN procedure) or ungraceful way (by means of CLOSE 245 procedure). 247 3.1.1.2 Statistics for traffic Measurements 249 It has been specified statistics related to the whole SCTP layer. 250 There are, e.g., statistics related to either SCTP packets or SCTP 251 chunks. 253 Statistics related to a specific association, or local/remote IP 254 addresses are defined inside its concerned table. 256 3.1.2 SCTP Parameters 258 This section of the MIB contains the general variables of the 259 SCTP protocol. Maximum, minimum, initial values, and values by 260 default are listed here. 262 SCTP RTO mechanism definition is based on the TCP MIB [RFC2012- 263 update]. In SCTP protocol, only options 'other' and 'vanj' are valid 264 since SCTP protocol defines Van Jacobson's algorithm as the one to 265 be used to calculate RTO. 'Other' is left for future use. 267 3.1.3 MIB Tables 269 There are several tables included in the SCTP MIB. The first group 270 deals with the Association variables and is composed of a main and 271 two extended tables. The second group is a bunch of tables used for 272 the reverse lookup. 274 It is NOT possible to create rows in any table (sctpAssocTable, 275 sctpAssocLocalAddressTable, sctpRemAddressTable and Reverse Lookup 276 tables). 278 It is NOT possible to delete rows in any table except in 279 sctpAssocTable under the particular conditions explained below. 281 3.1.3.1 Association Table 283 This is the main MIB table, where all the association related 284 information is stored per association basis. It is structured 285 according to expanded tables. The main table is called sctpAssocTable 286 and is indexed by sctpAssocId (the association identification) that 287 is a value that uniquely identifies an association. The MIB does not 288 restrict which value must be written here. It can be the tag value, 289 the TCB creation time, or any other value the implementers decide. 291 The sctpAssoc index is also shared by two more tables: 292 - sctpAssocLocalAddressTable: to store the local IP address(-es). 293 - sctpAssocRemAddressTable: to store the remote addresses and the 294 per-remote-address(-es)related information. 296 Note: The following representation is a conceptual mode of describing 297 the relationship between the tables in this MIB. Note that the real 298 relationship of the tables is by sharing an index, so tables are not 299 truly within tables. Every entry is explained when defining the 300 corresponding objects in the MIB. 302 sctpAssocTable 303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 | sctpAssocId (index) / ... | 305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 306 | sctpAssocRemHostName \ ... | 307 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 308 | sctpAssocLocalPort / ... | 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 | sctpAssocRemPort \ ... | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | sctpAssocRemPrimaryAddressType / ... | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | sctpAssocRemPrimaryAddress \ ... | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | sctpAssocHeartBeatTimer / ...| 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | sctpAssocState \ ... | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 | sctpAssocInStreams / ... | 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 | sctpAssocOutStreams \ ... | 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 | sctpAssocMaxRetr / ... | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | sctpAssocPrimaryProcess \ ...| 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | sctpAssocT1expireds / ... | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | sctpAssocT2expireds \ ... | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | sctpAssocRtxChunks / ... | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | sctpAssocStartTime \ ... | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | sctpAssocLocalAddressTable | 337 | | 338 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 339 | | sctpAssocLocalAddressType(index) \ ... | | 340 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 341 | | sctpAssocLocalAddress (index) \ ... | | 342 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 343 | | sctpAssocLocalAddressStartTime \ ... | | 344 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 345 | | 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | sctpAssocRemAddressTable | 348 | | 349 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 350 | | sctpAssocRemAddressType (index) \ ... | | 351 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 352 | | sctpAssocRemAddress (index) \ ... | | 353 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 354 | | sctpAssocRemAddressStatus \ ... | | 355 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 356 | | sctpAssocRemAddressHBFlag \ ... | | 357 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-++-+| | 358 | | sctpAssocRemAddressRTO \ ... | | 359 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 360 | | sctpAssocRemAddressMaxPathRtx \ ... | | 361 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 362 | | sctpAssocRemAddressRtx \ ... | | 363 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 364 | | sctpAssocRemAddressStartTime \ ... | | 365 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 366 | | 367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 369 Both sctpAssocLocalAddressTable and sctpAssocRemAddressTable are 370 indexed by addresses. �Address� and �AddressType� use the syntax 371 InetAddress and InetAddressType defined in the Textual Conventions 372 for Internet Network Address [RFC2851-update]. In the general case 373 this syntax is valid for IPv4, IPv6 and DNS but only the first two 374 options will be valid in this MIB. 376 The IP addresses that the MIB supports are defined in the [RFC2851- 377 update]: global and non-global (either with a zone index or not) IPv4 378 addresses, global and non-global (either with a zone index or not) 379 IPv6 addresses. 381 DNS value is not used to identify an IP address since it is only 382 valid during initialization (once this stage is finished, both sides 383 only use IP addresses). 385 To keep the name of the remote peer (when provided by the peer at 386 initialization time), an entry has been created in the sctpAssocTable 387 (sctpAssocRemHostName). When no DNS name is provided by the remote 388 endpoint, this value will be NULL (zero-length string). Otherwise, 389 the received DNS name will be stored here. 391 If it is required to abort an existing association, the value 392 deleteTCB has to be written in the variable sctpAssocState. That is 393 the only way to delete rows in any of the mentioned tables. 395 3.1.3.2 Reverse Lookup Table 397 There are five reverse lookup tables to help management applications 398 to efficiently access conceptual rows in other tables. This is the 399 way for not performing expensive tree walks through large number of 400 associations. All of these tables are optional. 402 The defined reversed lookup tables allow performing a lookup using 403 the following variables: 405 - Local Port: It allows finding the associations in which the 406 local endpoint is using the specified local port. 407 - Remote Port: It allows finding the associations in which the 408 remote endpoint is using the specified remote port. 409 - Remote Host Name: It allows finding the associations that have 410 defined the specified host name as remote endpoint. 411 - Remote Primary IP Address: It allows finding the associations 412 that have defined the specified remote IP address as primary. 413 - Remote IP address: List of all the associations that have the 414 specified IP address belonging to the set of remote addresses. 416 As an example the picture below shows the table to look up by remote 417 port. 419 sctpLookupRemPortTable 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | sctpAssocRemPort (index) / ... | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | sctpAssocId (index) \ ... | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | sctpLookupRemPortStartTime / ... | 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 428 All the lookup tables contains a timestamp (referred as StartTime) to 429 indicate when a row in the table was created. 431 It is not possible to either create or delete rows in these tables. 433 3.2 Conformance 435 The conformance section points out as optional the statistics either 436 general for the whole SCTP layer and per association or remote IP 437 address. 439 Also, IP address will take the format of IPv4 and IPv6 addresses (not 440 scoped). DNS name will not be accepted either (since names will be 441 stored � if present � in the sctpRemoteHostName variable). 443 4. Definitions 445 SCTP-MIB DEFINITIONS ::= BEGIN 447 IMPORTS 448 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Gauge32, 449 Counter32, Counter64 450 FROM SNMPv2-SMI -- RFC2578 451 TimeStamp 452 FROM SNMPv2-TC -- RFC2579 453 MODULE-COMPLIANCE, OBJECT-GROUP 454 FROM SNMPv2-CONF -- RFC2580 455 InetAddressType, InetAddress, InetPortNumber 456 FROM INET-ADDRESS-MIB -- RFC2851-update 457 ; 459 -- RFC2851 is being update. Needed to update the import clause 460 -- as well as other references to RFC2851 to include all the 461 -- textual conventions defined in the new RFC2851-update 463 sctpMIB MODULE-IDENTITY 464 LAST-UPDATED "200202060000Z" -- 06th February 2002 465 ORGANIZATION "IETF SIGTRAN Working Group" 466 CONTACT-INFO 467 " Maria-Carmen Belinchon-Vergara 468 Jose-Javier Pastor-Balbas 470 Postal: Ericsson Espana S. A. 471 Ombu street 3, 4th floor 472 28045 Madrid 473 Spain 475 Phones: +34 91 339 3535 476 +34 91 339 3819 478 Emails: Maria.C.Belinchon@ericsson.com 479 J.Javier.Pastor@ericsson.com" 480 DESCRIPTION 481 "The MIB module for managing an SCTP implementation." 482 ::= { mib-2 xxxx } -- IANA needs to choose this value 483 -- when sent to the RFC editor 485 -- the SCTP base variables group 487 sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 } 489 sctpStats OBJECT IDENTIFIER ::= { sctpObjects 1 } 490 sctpParams OBJECT IDENTIFIER ::= { sctpObjects 2 } 492 -- STATISTICS 493 -- ********** 495 -- STATE-RELATED STATISTICS 497 sctpCurrEstab OBJECT-TYPE 498 SYNTAX Gauge32 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "The number of SCTP associations for which the current state 503 is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." 505 ::= { sctpStats 1 } 507 sctpActiveEstabs OBJECT-TYPE 508 SYNTAX Counter32 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The number of times that SCTP associations have made a direct 513 transition to the ESTABLISHED state from the COOKIE-ECHOED 514 state: COOKIE-ECHOED -> ESTABLISHED. The upper layer has 515 initiated the association attempt." 517 ::= { sctpStats 2 } 519 sctpPassiveEstabs OBJECT-TYPE 520 SYNTAX Counter32 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The number of times that SCTP associations have made a direct 525 transition to the ESTABLISHED state from the CLOSED state: 526 CLOSED -> ESTABLISHED. The remote endpoint has initiated the 527 association attempt." 529 ::= { sctpStats 3 } 531 sctpAborteds OBJECT-TYPE 532 SYNTAX Counter32 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "The number of times that SCTP associations have made a direct 537 transition to the CLOSED state from any state using the 538 primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful 539 termination of the association." 541 ::= { sctpStats 4 } 543 sctpShutdowns OBJECT-TYPE 544 SYNTAX Counter32 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION 548 "The number of times that SCTP associations have made a direct 549 transition to the CLOSED state from either the SHUTDOWN-SENT 550 state or the SHUTDOWN-ACK-SENT state. Graceful termination of 551 the association." 553 ::= { sctpStats 5 } 555 -- OTHER LAYER STATISTICS 557 sctpOutOfBlues OBJECT-TYPE 558 SYNTAX Counter32 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "Number of out of the blue packets (SCTP packet correctly 563 formed -right checksum- but the receiver is not able to 564 identify the association to which this packet belongs) 565 received by the host." 567 ::= { sctpStats 6 } 569 sctpChecksumErrors OBJECT-TYPE 570 SYNTAX Counter32 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "Number of SCTP packets received from the peers with an 575 invalid checksum." 577 ::= { sctpStats 7 } 579 sctpOutCtrlChunks OBJECT-TYPE 580 SYNTAX Counter64 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "Number of SCTP control chunks sent to the peers (no 585 retransmissions included)." 587 ::= { sctpStats 8 } 589 sctpOutOrderChunks OBJECT-TYPE 590 SYNTAX Counter64 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "Number of SCTP ordered data chunks sent to the peers (no 595 retransmissions included)." 597 ::= { sctpStats 9 } 599 sctpOutUnorderChunks OBJECT-TYPE 600 SYNTAX Counter64 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "Number of SCTP unordered chunks (data chunks in which the U 605 bit is set to 1) sent to the peers (no retransmissions 606 included)." 608 ::= { sctpStats 10 } 610 sctpInCtrlChunks OBJECT-TYPE 611 SYNTAX Counter64 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "Number of SCTP control chunks received from the peers (no 616 duplicated included)." 618 ::= { sctpStats 11 } 620 sctpInOrderChunks OBJECT-TYPE 621 SYNTAX Counter64 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "Number of SCTP ordered data chunks received from the peers 626 (no duplicated included)." 628 ::= { sctpStats 12 } 630 sctpInUnorderChunks OBJECT-TYPE 631 SYNTAX Counter64 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "Number of SCTP unordered chunks (data chunks in which the U 636 bit is set to 1) received from the peers (no duplicated 637 included)." 639 ::= { sctpStats 13 } 641 sctpFragUsrMsgs OBJECT-TYPE 642 SYNTAX Counter64 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "Number of user messages that have to be fragmented because of 647 the MTU." 649 ::= { sctpStats 14 } 651 sctpReasmUsrMsgs OBJECT-TYPE 652 SYNTAX Counter64 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "Number of user messages reassembled." 658 ::= { sctpStats 15 } 660 sctpOutSCTPPacks OBJECT-TYPE 661 SYNTAX Counter64 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "Number of SCTP packets sent to the peers." 667 ::= { sctpStats 16 } 669 sctpInSCTPPacks OBJECT-TYPE 670 SYNTAX Counter64 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "Number of SCTP packets received from the peers." 676 ::= { sctpStats 17 } 678 -- PROTOCOL GENERAL VARIABLES 679 -- ************************** 681 sctpRtoAlgorithm OBJECT-TYPE 682 SYNTAX INTEGER { 683 other(1), -- Other new one. Future use 684 vanj(2) -- Van Jacobson's algorithm 685 } 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION 689 "The algorithm used to determine the timeout value (T3-rtx) 690 used for re-transmitting unacknowledged chunks." 692 ::= { sctpParams 1 } 694 sctpRtoMin OBJECT-TYPE 695 SYNTAX Unsigned32 696 UNITS "milliseconds" 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "The minimum value permitted by a SCTP implementation for the 701 retransmission timeout, measured in milliseconds. More 702 refined semantics for objects of this type depend upon the 703 algorithm used to determine the retransmission timeout. 704 Minimum recommended value is 1000 milliseconds. Some telephony 705 applications could require less than 1 second." 707 ::= { sctpParams 2 } 709 sctpRtoMax OBJECT-TYPE 710 SYNTAX Unsigned32 711 UNITS "milliseconds" 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The maximum value permitted by a SCTP implementation for the 716 retransmission timeout, measured in milliseconds. More 717 refined semantics for objects of this type depend upon the 718 algorithm used to determine the retransmission timeout. 719 Recommended value is 60000 milliseconds." 721 ::= { sctpParams 3 } 723 sctpRtoInitial OBJECT-TYPE 724 SYNTAX Unsigned32 725 UNITS "milliseconds" 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "Initial value for the Retransmission timer. Recommended value 730 is 3000 milliseconds." 732 ::= { sctpParams 4 } 734 sctpMaxAssoc OBJECT-TYPE 735 SYNTAX Integer32 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION 739 "The limit on the total number of SCTP associations the entity 740 can support. In entities where the maximum number of 741 associations is dynamic, this object should contain the value 742 -1." 744 ::= { sctpParams 5 } 746 sctpValCookieLife OBJECT-TYPE 747 SYNTAX Unsigned32 748 UNITS "milliseconds" 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "Valid cookie life in the 4-way start-up handshake procedure. 753 Recommended value: 60000 milliseconds." 755 ::= { sctpParams 6 } 757 sctpMaxInitRetr OBJECT-TYPE 758 SYNTAX Unsigned32 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The maximum number of retransmissions at the start-up phase 763 (INIT and COOKIE ECHO chunks). Recommended value: 8 attempts." 765 ::= { sctpParams 7 } 767 -- TABLES 768 -- ****** 770 -- the SCTP Association TABLE 772 -- The SCTP association table contains information about each 773 -- association in which the local endpoint is involved. 775 sctpAssocTable OBJECT-TYPE 776 SYNTAX SEQUENCE OF SctpAssocEntry 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION 780 "A table containing SCTP association-specific information." 782 ::= { sctpObjects 3 } 784 sctpAssocEntry OBJECT-TYPE 785 SYNTAX SctpAssocEntry 786 MAX-ACCESS not-accessible 787 STATUS current 788 DESCRIPTION 789 "General common variables and statistics for the whole 790 association." 791 INDEX { sctpAssocId } 793 ::= { sctpAssocTable 1 } 795 SctpAssocEntry ::= SEQUENCE { 796 sctpAssocId Unsigned32, 797 sctpAssocRemHostName OCTET STRING, 798 sctpAssocLocalPort InetPortNumber, 799 sctpAssocRemPort InetPortNumber, 800 sctpAssocRemPrimaryAddressType InetAddressType, 801 sctpAssocRemPrimaryAddress InetAddress, 802 sctpAssocHeartBeatTimer Unsigned32, 803 sctpAssocState INTEGER, 804 sctpAssocInStreams Unsigned32, 805 sctpAssocOutStreams Unsigned32, 806 sctpAssocMaxRetr Unsigned32, 807 sctpAssocPrimaryProcess Unsigned32, 808 sctpAssocT1expireds Counter32, -- Statistic 809 sctpAssocT2expireds Counter32, -- Statistic 810 sctpAssocRtxChunks Counter32, -- Statistic 811 sctpAssocStartTime TimeStamp 812 } 814 sctpAssocId OBJECT-TYPE 815 SYNTAX Unsigned32 816 MAX-ACCESS not-accessible 817 STATUS current 818 DESCRIPTION 819 "Association Identification. Value identifying the association 820 (typically the Initiate Verification Tag). 822 Value zero is reserved to indicate no association." 824 ::= { sctpAssocEntry 1 } 826 sctpAssocRemHostName OBJECT-TYPE 827 SYNTAX OCTET STRING (SIZE(0..255)) 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "Peer's DNS name. If no DNS domain name was received at init 832 time (embedded in the INIT or INIT-ACK chunk) from the peer, 833 this entry will be meaningless, therefore it will contain a 834 zero-length string value. Otherwise, the remote host name 835 received at init time will be stored." 837 ::= { sctpAssocEntry 2 } 839 sctpAssocLocalPort OBJECT-TYPE 840 SYNTAX InetPortNumber (1..65535) 841 MAX-ACCESS read-only 842 STATUS current 843 DESCRIPTION 844 "Local SCTP port number used for this association.." 846 ::= { sctpAssocEntry 3 } 848 sctpAssocRemPort OBJECT-TYPE 849 SYNTAX InetPortNumber (1..65535) 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "Remote SCTP port number used for this association." 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. They are 863 interpreted according to the RFC2851-update. 865 The unknown (0) value MUST be used if the value of the 866 corresponding InetAddress object is a zero-length string (when 867 the endpoint does still not determined the Primary Address). 868 It may also be used for error conditions (IP address different 869 from IPv4 or IPv6). 871 This value will be filled in after the INIT or INIT ACK chunks 872 have been received and the primary path is selected by SCTP. 873 Until this occurs, the type will be unknown." 875 ::= { sctpAssocEntry 5 } 877 sctpAssocRemPrimaryAddress OBJECT-TYPE 878 SYNTAX InetAddress 879 MAX-ACCESS read-only 880 STATUS current 881 DESCRIPTION 882 "Primary destination IP address. An InetAddress value is 883 always interpreted within the context of an InetAddressType 884 value. 886 This value will be filled in after INIT or INIT ACK chunks 887 have been received and the primary path is selected by SCTP. 888 Until this occurs, the type will be zero-length string." 890 ::= { sctpAssocEntry 6 } 892 sctpAssocHeartBeatTimer OBJECT-TYPE 893 SYNTAX Unsigned32 894 UNITS "milliseconds" 895 MAX-ACCESS read-only 896 STATUS current 897 DESCRIPTION 898 "The current heartbeat time-out. The recommended default value 899 is 30000 milliseconds." 901 ::= { sctpAssocEntry 7 } 903 sctpAssocState OBJECT-TYPE 904 SYNTAX INTEGER { 905 closed(1), 906 cookieWait(2), 907 cookieEchoed(3), 908 established(4), 909 shutdownPending(5), 910 shutdownSent(6), 911 shutdownReceived(7), 912 shutdownAckSent(8), 913 deleteTCB(9) 914 } 915 MAX-ACCESS read-write 916 STATUS current 917 DESCRIPTION 918 "The state of this SCTP association. 920 As in TCP, deleteTCB is the only value that may be set by a 921 management station. Accordingly, it is appropriate for an 922 agent to return a 'badValue' response if a management station 923 attempts to set this object to any other value. 924 If a management station sets this object to the value 925 deleteTCB(9), then this has the effect of deleting the TCB (as 926 defined in SCTP) of the corresponding association on the 927 managed node, resulting in immediate termination of the 928 association. 930 As an implementation-specific option, an ABORT chunk may be 931 sent from the managed node to the other SCTP endpoint." 933 ::= { sctpAssocEntry 8 } 935 sctpAssocInStreams OBJECT-TYPE 936 SYNTAX Unsigned32 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "Inbound Streams according to the negotiation at association 941 start up. This parameter has to be read-only by the manager." 943 ::= { sctpAssocEntry 9 } 945 sctpAssocOutStreams OBJECT-TYPE 946 SYNTAX Unsigned32 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "Outbound Streams according to the negotiation at association 951 start up. This parameter has to be read-only by the manager." 953 ::= { sctpAssocEntry 10 } 955 sctpAssocMaxRetr OBJECT-TYPE 956 SYNTAX Unsigned32 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "The maximum number of data retransmissions in the association 961 context. This value is specific for each association and the 962 upper layer can change it calling the appropriate primitives. 963 This value has to be smaller than the addition of all the 964 maximum number for all the paths 965 (sctpAssocRemAddressMaxPathRtx). 966 Recommended value: 10 attempts." 968 ::= { sctpAssocEntry 11 } 970 sctpAssocPrimaryProcess OBJECT-TYPE 971 SYNTAX Unsigned32 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "The number identifies the system level process which 976 holds primary responsibility of the SCTP association. 977 Wherever possible, this should be the system's native 978 unique identification number. The special value 0 can 979 be used to indicate that no primary process is known. 981 Note that the value of this object can be used as a 982 pointer into the swRunTable of the HOST-RESOURCES-MIB 983 (if the value is smaller than 2147483647) or into the 984 sysApplElmtRunTable of the SYSAPPL-MIB." 986 ::= { sctpAssocEntry 12 } 988 -- Association Statistics 990 sctpAssocT1expireds OBJECT-TYPE 991 SYNTAX Counter32 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "Number of times that T1 timer expired (timer for sending 996 either INIT or COOKIE-ECHO chunks and receiving an 997 acknowledgment)." 999 ::= { sctpAssocEntry 13 } 1001 sctpAssocT2expireds OBJECT-TYPE 1002 SYNTAX Counter32 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "Number of times that T2-shutdown timer expired (shutdown 1007 timer)." 1009 ::= { sctpAssocEntry 14 } 1011 sctpAssocRtxChunks OBJECT-TYPE 1012 SYNTAX Counter32 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "Number of data chunks retransmitted to the peer in the 1017 current association." 1019 ::= { sctpAssocEntry 15 } 1021 sctpAssocStartTime OBJECT-TYPE 1022 SYNTAX TimeStamp 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "The value of SysUpTime at the time that this row was 1027 created." 1029 ::= { sctpAssocEntry 16 } 1031 -- Expanded tables: Including Multi-home feature 1033 -- Local Address TABLE 1034 -- ******************* 1036 sctpAssocLocalAddressTable OBJECT-TYPE 1037 SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry 1038 MAX-ACCESS not-accessible 1039 STATUS current 1040 DESCRIPTION 1041 "Expanded table of sctpAssocTable based on the AssocId index. 1042 This table shows data related to each local IP address which 1043 is used by this association." 1045 ::= { sctpObjects 4 } 1047 sctpAssocLocalAddressEntry OBJECT-TYPE 1048 SYNTAX SctpAssocLocalAddressEntry 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "Local information about the available addresses." 1053 INDEX { sctpAssocId, -- shared index 1054 sctpAssocLocalAddressType, 1055 sctpAssocLocalAddress } 1057 ::= { sctpAssocLocalAddressTable 1 } 1059 SctpAssocLocalAddressEntry ::= SEQUENCE { 1060 sctpAssocLocalAddressType InetAddressType, 1061 sctpAssocLocalAddress InetAddress, 1062 sctpAssocLocalAddressStartTime TimeStamp 1063 } 1065 sctpAssocLocalAddressType OBJECT-TYPE 1066 SYNTAX InetAddressType 1067 MAX-ACCESS not-accessible 1068 STATUS current 1069 DESCRIPTION 1070 "Internet type of local IP address used for this association. 1071 They are interpreted according to the RFC2851-update. 1073 The unknown (0) value MUST be used if the value of the 1074 corresponding InetAddress object is a zero-length string (when 1075 the endpoint does still not determined the address(-es)). It 1076 may also be used for error conditions (IP address different 1077 from IPv4 or IPv6). 1079 This value will be filled in after the INIT or INIT ACK chunks 1080 have been received. Until this occurs, the type will be 1081 unknown." 1083 ::= { sctpAssocLocalAddressEntry 1 } 1085 sctpAssocLocalAddress OBJECT-TYPE 1086 SYNTAX InetAddress (SIZE(1..36)) 1087 MAX-ACCESS not-accessible 1088 STATUS current 1089 DESCRIPTION 1090 "The value of a local IP address available for this 1091 association. An InetAddress value is always interpreted within 1092 the context of an InetAddressType value. If SCTP is using a 1093 DNS name, the mapping to IP address/-es will be done at 1094 reception of INIT or INIT_ACK chunks. Until this occurs, it 1095 will contain a zero value. 1097 The sctpAssocRemAddress may not be empty due to the SIZE 1098 restriction." 1100 ::= { sctpAssocLocalAddressEntry 2 } 1102 sctpAssocLocalAddressStartTime OBJECT-TYPE 1103 SYNTAX TimeStamp 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "The value of SysUpTime at the time that this row was 1108 created." 1110 ::= { sctpAssocLocalAddressEntry 3 } 1112 -- Remote Addresses TABLE 1113 -- ********************** 1115 sctpAssocRemAddressTable OBJECT-TYPE 1116 SYNTAX SEQUENCE OF SctpAssocRemAddressEntry 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "Expanded table of sctpAssocTable based on the AssocId index. 1121 This table shows data related to each remote peer IP address 1122 which is used by this association." 1124 ::= { sctpObjects 5 } 1126 sctpAssocRemAddressEntry OBJECT-TYPE 1127 SYNTAX SctpAssocRemAddressEntry 1128 MAX-ACCESS not-accessible 1129 STATUS current 1130 DESCRIPTION 1131 "Information about the most important variables for every 1132 remote IP address " 1133 INDEX { sctpAssocId, -- shared index 1134 sctpAssocRemAddressType, 1135 sctpAssocRemAddress } 1137 ::= { sctpAssocRemAddressTable 1 } 1139 SctpAssocRemAddressEntry ::= SEQUENCE { 1140 sctpAssocRemAddressType InetAddressType, 1141 sctpAssocRemAddress InetAddress, 1142 sctpAssocRemAddressStatus INTEGER, 1143 sctpAssocRemAddressHBFlag INTEGER, 1144 sctpAssocRemAddressRTO Unsigned32, 1145 sctpAssocRemAddressMaxPathRtx Unsigned32, 1146 sctpAssocRemAddressRtx Counter32, -- Statistic 1147 sctpAssocRemAddressStartTime TimeStamp 1148 } 1150 sctpAssocRemAddressType OBJECT-TYPE 1151 SYNTAX InetAddressType 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "Internet type of a remote IP address available for this 1156 association. They are interpreted according to the RFC2851- 1157 update. 1159 The unknown (0) value MUST be used if the value of the 1160 corresponding InetAddress object is a zero-length string (when 1161 the endpoint does still not determined the Primary Address). 1162 It may also be used for error conditions (IP address different 1163 from IPv4 or IPv6). 1165 This value will be filled in after the INIT or INIT ACK chunks 1166 have been received. Until this occurs, the type will be 1167 unknown." 1169 ::= { sctpAssocRemAddressEntry 1 } 1171 sctpAssocRemAddress OBJECT-TYPE 1172 SYNTAX InetAddress (SIZE(1..36)) 1173 MAX-ACCESS not-accessible 1174 STATUS current 1175 DESCRIPTION 1176 "The value of a remote IP address available for this 1177 association. An InetAddress value is always interpreted within 1178 the context of an InetAddressType value. If SCTP is using a 1179 DNS name, the mapping to IP address/-es will be done at 1180 reception of INIT or INIT_ACK chunks. Until this occurs, it 1181 will contain a zero value. 1183 The sctpAssocRemAddress may not be empty due to the SIZE 1184 restriction." 1186 ::= { sctpAssocRemAddressEntry 2 } 1188 sctpAssocRemAddressStatus OBJECT-TYPE 1189 SYNTAX INTEGER { 1190 active(0), 1191 inactive(1) 1192 } 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The current status of the remote transport address, according 1197 to [RFC2960]. 1198 Active means that the threshold of no answer received from 1199 this IP address has not been reached. Inactive means that 1200 either no heartbeat was received from this address, or any 1201 other message, reaching the threshold defined by the 1202 protocol." 1204 ::= { sctpAssocRemAddressEntry 3 } 1206 sctpAssocRemAddressHBFlag OBJECT-TYPE 1207 SYNTAX INTEGER { 1208 active(0), 1209 inactive(1) 1210 } 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "The optional Heartbeat associated to one destination 1215 transport address could be active or not (value equal to 0 or 1216 1, respectively). 1218 An active destination transport address is the one considered 1219 available by a peer endpoint for receiving SCTP packets, as it 1220 is described in [RFC2960]." 1222 ::= { sctpAssocRemAddressEntry 4 } 1224 sctpAssocRemAddressRTO OBJECT-TYPE -- T3-rtx- Timer 1225 SYNTAX Unsigned32 1226 UNITS "milliseconds" 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "The current Retransmission Timeout. T3-rtx timer as defined 1231 in the protocol SCTP." 1233 ::= { sctpAssocRemAddressEntry 5 } 1235 sctpAssocRemAddressMaxPathRtx OBJECT-TYPE 1236 SYNTAX Unsigned32 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "Maximum number of DATA chunks retransmissions allowed to a 1241 remote IP address before it is considered inactive, as defined 1242 in [RFC2960]. Recommended value 5 attempts." 1244 ::= { sctpAssocRemAddressEntry 6 } 1246 -- Remote Address Statistic 1248 sctpAssocRemAddressRtx OBJECT-TYPE 1249 SYNTAX Counter32 1250 MAX-ACCESS read-only 1251 STATUS current 1252 DESCRIPTION 1253 "Number of DATA chunks retransmissions as defined in 1254 [RFC2960]." 1256 ::= { sctpAssocRemAddressEntry 7 } 1258 sctpAssocRemAddressStartTime OBJECT-TYPE 1259 SYNTAX TimeStamp 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "The value of SysUpTime at the time that this row was 1264 created." 1266 ::= { sctpAssocRemAddressEntry 8 } 1268 -- ASSOCIATION INVERSE TABLE 1269 -- ************************* 1271 -- BY LOCAL PORT 1273 sctpLookupLocalPortTable OBJECT-TYPE 1274 SYNTAX SEQUENCE OF SctpLookupLocalPortEntry 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "With the use of this table, a list of associations which are 1279 using the specified local port can be got" 1281 ::= { sctpObjects 6 } 1283 sctpLookupLocalPortEntry OBJECT-TYPE 1284 SYNTAX SctpLookupLocalPortEntry 1285 MAX-ACCESS not-accessible 1286 STATUS current 1287 DESCRIPTION 1288 "This table is indexed by local port and association ID. 1289 Specifying a local port, we would get a list of the 1290 associations whose local port is the one specified" 1292 INDEX { sctpAssocLocalPort, 1293 sctpAssocId } 1295 ::= { sctpLookupLocalPortTable 1 } 1297 SctpLookupLocalPortEntry::= SEQUENCE { 1298 sctpLookupLocalPortStartTime TimeStamp 1299 } 1301 sctpLookupLocalPortStartTime OBJECT-TYPE 1302 SYNTAX TimeStamp 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "The value of SysUpTime at the time that this row was 1307 created." 1309 ::= { sctpLookupLocalPortEntry 1 } 1311 -- BY REMOTE PORT 1313 sctpLookupRemPortTable OBJECT-TYPE 1314 SYNTAX SEQUENCE OF SctpLookupRemPortEntry 1315 MAX-ACCESS not-accessible 1316 STATUS current 1317 DESCRIPTION 1318 "With the use of this table, a list of associations which are 1319 using the specified remote port can be got" 1321 ::= { sctpObjects 7 } 1323 sctpLookupRemPortEntry OBJECT-TYPE 1324 SYNTAX SctpLookupRemPortEntry 1325 MAX-ACCESS not-accessible 1326 STATUS current 1327 DESCRIPTION 1328 "This table is indexed by remote port and association ID. 1329 Specifying a remote port we would get a list of the 1330 associations whose local port is the one specified " 1332 INDEX { sctpAssocRemPort, 1333 sctpAssocId } 1335 ::= { sctpLookupRemPortTable 1 } 1337 SctpLookupRemPortEntry::= SEQUENCE { 1338 sctpLookupRemPortStartTime TimeStamp 1339 } 1341 sctpLookupRemPortStartTime OBJECT-TYPE 1342 SYNTAX TimeStamp 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The value of SysUpTime at the time that this row was 1347 created." 1349 ::= { sctpLookupRemPortEntry 1 } 1351 -- BY REMOTE HOST NAME 1353 sctpLookupRemHostNameTable OBJECT-TYPE 1354 SYNTAX SEQUENCE OF SctpLookupRemHostNameEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "With the use of this table, a list of associations with that 1359 particular host can be got" 1361 ::= { sctpObjects 8 } 1363 sctpLookupRemHostNameEntry OBJECT-TYPE 1364 SYNTAX SctpLookupRemHostNameEntry 1365 MAX-ACCESS not-accessible 1366 STATUS current 1367 DESCRIPTION 1368 "This table is indexed by remote host name and association ID. 1369 Specifying a host name we would get a list of the associations 1370 specifying that host name as the remote one" 1372 INDEX { sctpAssocRemHostName, 1373 sctpAssocId } 1375 ::= { sctpLookupRemHostNameTable 1 } 1377 SctpLookupRemHostNameEntry::= SEQUENCE { 1378 sctpLookupRemHostNameStartTime TimeStamp 1379 } 1381 sctpLookupRemHostNameStartTime OBJECT-TYPE 1382 SYNTAX TimeStamp 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "The value of SysUpTime at the time that this row was 1387 created." 1389 ::= { sctpLookupRemHostNameEntry 1 } 1391 -- BY REMOTE PRIMARY IP ADDRESS 1393 sctpLookupRemPrimIPAddrTable OBJECT-TYPE 1394 SYNTAX SEQUENCE OF SctpLookupRemPrimIPAddrEntry 1395 MAX-ACCESS not-accessible 1396 STATUS current 1397 DESCRIPTION 1398 "With the use of this table, it can be got a list of 1399 associations that have that the specified IP address as 1400 primary within the remote set of active addresses " 1402 ::= { sctpObjects 9 } 1404 sctpLookupRemPrimIPAddrEntry OBJECT-TYPE 1405 SYNTAX SctpLookupRemPrimIPAddrEntry 1406 MAX-ACCESS not-accessible 1407 STATUS current 1408 DESCRIPTION 1409 "This table is indexed by primary address and association ID. 1410 Specifying a primary address, we would get a list of the 1411 associations that have the specified remote IP address marked 1412 as primary. " 1414 INDEX { sctpAssocRemPrimaryAddressType, 1415 sctpAssocRemPrimaryAddress, 1416 sctpAssocId } 1418 ::= { sctpLookupRemPrimIPAddrTable 1 } 1420 SctpLookupRemPrimIPAddrEntry::= SEQUENCE { 1421 sctpLookupRemPrimIPAddrStartTime TimeStamp 1422 } 1424 sctpLookupRemPrimIPAddrStartTime OBJECT-TYPE 1425 SYNTAX TimeStamp 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "The value of SysUpTime at the time that this row was 1430 created." 1432 ::= { sctpLookupRemPrimIPAddrEntry 1 } 1434 -- BY REMOTE IP ADDRESS 1436 sctpLookupRemIPAddrTable OBJECT-TYPE 1437 SYNTAX SEQUENCE OF SctpLookupRemIPAddrEntry 1438 MAX-ACCESS not-accessible 1439 STATUS current 1440 DESCRIPTION 1441 "With the use of this table, a list of associations that have 1442 the specified IP address as one of the remote ones can be got" 1444 ::= { sctpObjects 10 } 1446 sctpLookupRemIPAddrEntry OBJECT-TYPE 1447 SYNTAX SctpLookupRemIPAddrEntry 1448 MAX-ACCESS not-accessible 1449 STATUS current 1450 DESCRIPTION 1451 "This table is indexed by a remote IP address and association 1452 ID. Specifying an IP address we would get a list of the 1453 associations that have the specified IP address included 1454 within the set of remote IP addresses" 1456 INDEX { sctpAssocRemAddressType, 1457 sctpAssocRemAddress, 1458 sctpAssocId } 1460 ::= { sctpLookupRemIPAddrTable 1 } 1462 SctpLookupRemIPAddrEntry::= SEQUENCE { 1463 sctpLookupRemIPAddrStartTime TimeStamp 1464 } 1466 sctpLookupRemIPAddrStartTime OBJECT-TYPE 1467 SYNTAX TimeStamp 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "The value of SysUpTime at the time that this row was 1472 created." 1474 ::= { sctpLookupRemIPAddrEntry 1 } 1476 -- 4.1 Conformance Information 1478 sctpConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } 1479 sctpCompliances OBJECT IDENTIFIER ::= { sctpConformance 1 } 1480 sctpGroups OBJECT IDENTIFIER ::= { sctpConformance 2 } 1482 -- 4.1.1 Units of conformance 1484 -- 1485 -- MODULE GROUPS 1486 -- 1488 sctpParamsGroup OBJECT-GROUP 1489 OBJECTS { sctpRtoAlgorithm, 1490 sctpRtoMin, 1491 sctpRtoMax, 1492 sctpRtoInitial, 1493 sctpMaxAssoc, 1494 sctpValCookieLife, 1495 sctpMaxInitRetr 1496 } 1498 STATUS current 1499 DESCRIPTION 1500 "Common parameters for all the associations. They can usually 1501 be referred as configuration parameters" 1503 ::= { sctpGroups 1 } 1505 sctpStatsGroup OBJECT-GROUP 1506 OBJECTS {sctpCurrEstab, 1507 sctpActiveEstabs, 1508 sctpPassiveEstabs, 1509 sctpAborteds, 1510 sctpShutdowns, 1511 sctpOutOfBlues, 1512 sctpChecksumErrors, 1513 sctpOutCtrlChunks, 1514 sctpOutOrderChunks, 1515 sctpOutUnorderChunks, 1516 sctpInCtrlChunks, 1517 sctpInOrderChunks, 1518 sctpInUnorderChunks, 1519 sctpFragUsrMsgs, 1520 sctpReasmUsrMsgs, 1521 sctpOutSCTPPacks, 1522 sctpInSCTPPacks, 1523 sctpAssocRemAddressRtx 1524 } 1526 STATUS current 1527 DESCRIPTION 1528 "Statistics group. It includes the objects to collect state 1529 changes in the SCTP protocol local layer and flow control 1530 statistics." 1532 ::= { sctpGroups 2 } 1534 sctpAssocTableParamsGroup OBJECT-GROUP 1535 OBJECTS {sctpAssocRemHostName, 1536 sctpAssocLocalPort, 1537 sctpAssocRemPort, 1538 sctpAssocRemPrimaryAddressType, 1539 sctpAssocRemPrimaryAddress, 1540 sctpAssocHeartBeatTimer, 1541 sctpAssocState, 1542 sctpAssocInStreams, 1543 sctpAssocOutStreams, 1544 sctpAssocMaxRetr, 1545 sctpAssocPrimaryProcess, 1546 sctpAssocT1expireds, 1547 sctpAssocT2expireds, 1548 sctpAssocRtxChunks, 1549 sctpAssocStartTime, 1550 sctpAssocLocalAddressStartTime, 1551 sctpAssocRemAddressStatus, 1552 sctpAssocRemAddressHBFlag, 1553 sctpAssocRemAddressRTO, 1554 sctpAssocRemAddressMaxPathRtx, 1555 sctpAssocRemAddressStartTime 1556 } 1558 STATUS current 1559 DESCRIPTION 1560 "The SCTP group of objects to manage specific local and remote 1561 SCTP variables (local and remote tables). These variables 1562 include all the SCTP basic features." 1564 ::= { sctpGroups 3 } 1566 sctpInverseGroup OBJECT-GROUP 1567 OBJECTS {sctpLookupLocalPortStartTime, 1568 sctpLookupRemPortStartTime, 1569 sctpLookupRemHostNameStartTime, 1570 sctpLookupRemPrimIPAddrStartTime, 1571 sctpLookupRemIPAddrStartTime 1572 } 1574 STATUS current 1575 DESCRIPTION 1576 "Objects used in the inverse lookup table." 1578 ::= { sctpGroups 4 } 1580 -- 4.1.2 Compliance Statements 1582 -- 1583 -- MODULE COMPLIANCES 1584 -- 1586 sctpCompliance MODULE-COMPLIANCE 1587 STATUS current 1588 DESCRIPTION 1589 "The compliance statement for SNMPv3 entities which implement 1590 SCTP. 1592 The SCTP MIB specifies in this compliant implementation that 1593 only need to support IPv4/IPv6 addresses without a zone index, 1594 unknown type and DNS names. Support for IPv4/IPv6 addresses 1595 without zone indices is not required." 1597 MODULE -- this module 1598 MANDATORY-GROUPS { sctpParamsGroup, 1599 sctpAssocTableParamsGroup 1600 } 1602 GROUP sctpStatsGroup 1603 DESCRIPTION 1604 "Group to cover all SCTP statistics. This will 1605 beimplemented when statistics are required." 1607 GROUP sctpInverseGroup 1608 DESCRIPTION 1609 "Objects used in inverse lookup tables. This should be 1610 implemented for easier lookups in the association tables, 1611 when it is required." 1613 OBJECT sctpAssocRemPrimaryAddressType 1614 SYNTAX InetAddressType { unknown(0), 1615 ipv4(1), 1616 ipv6(2) 1617 } 1618 DESCRIPTION 1619 "It is only required to have IPv4 and IPv6 addresses 1620 without zone indices. Unknown values must also be 1621 supported in case the IP address has a zero string length 1622 or an invalid/unknown format. 1624 The address with zone indices is required if an 1625 implementation can connect multiple zones." 1627 OBJECT sctpAssocLocalAddressType 1628 SYNTAX InetAddressType { unknown(0), 1629 ipv4(1), 1630 ipv6(2) 1631 } 1632 DESCRIPTION 1633 "It is only required to have IPv4 and IPv6 addresses 1634 without zone indices. Unknown values must also be 1635 supported in case the IP address has an invalid/unknown 1636 format. 1638 Addresses with zone indices are required if an 1639 implementation can connect multiple zones. " 1641 OBJECT sctpAssocRemAddressType 1642 SYNTAX InetAddressType { unknown(0), 1643 ipv4(1), 1644 ipv6(2) 1646 } 1647 DESCRIPTION 1648 "It is only required to have IPv4 and IPv6 addresses 1649 without zone indices. Unknown values must also be 1650 supported in case the IP address has an invalid/unknown 1651 format. 1653 Addresses with zone indices are required if an 1654 implementation can connect multiple zones. " 1656 ::= { sctpCompliances 1 } 1658 END 1660 5. Compiling Notes 1662 After compiling the MIB the following warnings can be got: 1664 @ index of row `sctpLookupRemHostNameEntry' can exceed OID size limit 1665 by 141 subidentifier(s) 1667 @ index of row `sctpLookupRemPrimIPAddrEntry' can exceed OID size 1668 limit by 142 subidentifier(s) 1670 These two come from the fact that sctpAssocRemPrimaryAddress has the 1671 default InetAddress size of (0..255) which exceeds OID size 1672 limitations. Introducing a size restriction on 1673 sctpAssocRemPrimaryAddress would make the warning go away � although 1674 it would be one of those more arbitrary restrictions. 1676 Some compilers can also show the following warnings: 1678 @ refined object `sctpAssocLocalAddressType' not listed in a 1679 mandatory or optional group 1681 @ refined object `sctpAssocRemAddressType' not listed in a mandatory 1682 or optional group 1684 The compliance statement refines these object which are not listed in 1685 one of the groups. The interesting thing is that you can't list them 1686 in one of the groups since the SMIv2 disallows to list not accessible 1687 objects. (It can actually be considered as a bug in SMIv2.) One 1688 solution would be to just put these two refinements into a 1689 DESCRIPTION clause or a comment. 1691 6. References 1693 [RFC2960] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J. 1694 Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. 1695 Paxson, "Stream Control Transmission Protocol", RFC 2960, 1696 October 2000. 1698 [sctpcheck] R. Stewart, J. Stone, D. Otis, "SCTP Checksum Change", 1699 January 18, 2002, draft-ietf-tsvwg-sctpcsum-02.txt 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 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1708 of Management Information for TCP/IP-based Internets", STD 16, 1709 RFC 1155, May 1990. 1711 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1712 Network Management Protocol", STD 15, RFC 1157, May 1990. 1714 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1715 16, RFC 1212, March 1991. 1717 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1718 SNMP", RFC 1215, March 1991. 1720 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1721 "Introduction to Community-based SNMPv2", RFC 1901, January 1722 1996. 1724 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1725 "Protocol Operations for Version 2 of the Simple Network 1726 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1728 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1729 "Transport Mappings for Version 2 of the Simple Network 1730 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1732 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1733 Transmission Control Protocol using SMIv2", RFC 2012, November 1734 1996. 1736 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1737 Requirement Levels", BCP 14, RFC 2119, Harvard University, 1738 March 1997 1739 [RFC2452] M. Daniele, "IP Version 6 Management Information Base for 1740 the Transmission Control Protocol", RFC 2452, December 1998 1742 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1743 "Introduction to Version 3 of the Internet-standard Network 1744 Management Framework", RFC 2570, April 1999. 1746 [RFC2571] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for 1747 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1749 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1750 "Message Processing and Dispatching for the Simple Network 1751 Management Protocol (SNMP)", RFC 2572, April 1999. 1753 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1754 RFC 2573, April 1999. 1756 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1757 (USM) for version 3 of the Simple Network Management Protocol 1758 (SNMPv3)", RFC 2574, April 1999. 1760 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1761 Access Control Model (VACM) for the Simple Network Management 1762 Protocol (SNMP)", RFC 2575, April 1999. 1764 [RFC2576] R.Frye, D. Levi, S. Routhier, B. Wijnen, �Coexistence 1765 between Version 1, Version 2, and Version 3 of the Internet- 1766 standard Network Management Framework", RFC 2576, March 2000. 1768 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1769 Rose, M., and S. Waldbusser, "Structure of Management 1770 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1772 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1773 Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", 1774 STD 58, RFC 2579, April 1999. 1776 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1777 Rose, M., and S. Waldbusser, "Conformance Statements for 1778 SMIv2", STD 58, RFC 2580, April 1999. 1780 [RFC2576-update] R. Frye,D. Levi ,S. Routhier, B. Wijnen , " 1781 Coexistence between Version 1, Version 2, and Version 3 of the 1782 Internet-standard Network Management Framework ", draft-ietf- 1783 snmpv3-coex-v2-01.txt, November 2001. 1785 [RFC2851-update] M. Daniele, B. Haberman, S. Routhier, J. 1786 Schoenwaelder, "Textual Conventions for Internet Network 1787 Addresses", draft-ietf-ops-rfc2851-update-06.txt, October 31, 1788 2001. Work in progress. 1790 [RFC2863] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB", 1791 June 2000 1793 [IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., 1794 Onoe, A. and B. Zill, "IPv6 Scoped Address Architecture", 1795 draft-ietf-ipngwg-scoping-arch-03.txt, November 2001. Work in 1796 progress. 1798 [TADDRESS] M. Daniele , J. Schoenwaelder , "Textual Conventions for 1799 Transport Addresses", draft-ietf-ops-taddress-mib-01.txt, 1800 September 17, 2001. Work in progress. 1802 [TCPMIB] Management Information Base for the Transmission Control 1803 Protocol (TCP), draft-ietf-ipngwg-rfc2012-update-01.txt, 1804 November 2001. Work in progress. 1806 [UDPMIB] Bill Fenner, Brian Haberman, Keith McCloghrie, Juergen 1807 Schoenwalder, Dave Thaler, "Management Information Base for 1808 User Datagram Protocol (UDP)", draft-ietf-ipngwg-rfc2013- 1809 update-01.txt, November 2001. Work in progress. 1811 7. Security Consideration 1813 The deleteTCB management object, defined in this MIB, has a MAX- 1814 ACCESS clause of read-write. This is because it allows operators to 1815 tear down the associations. Such object may be considered sensitive 1816 or vulnerable in some network environments. The support for SET 1817 operations in a non-secure environment without proper protection can 1818 have a negative effect on network operations. 1820 It is thus important to control even GET access to these objects and 1821 possibly to even encrypt the values of these object when sending them 1822 over the network via SNMP. Not all versions of SNMP provide features 1823 for such a secure environment. 1825 SNMPv1 by itself is not a secure environment. Even if security 1826 measures are taken (e.g., using IPSEC), there is no per-user control 1827 as to who (once an IPSEC association is established between hosts) is 1828 allowed to GET or SET the objects in this MIB 1830 It is recommended that the implementers consider the security 1831 features as provided by the SNMPv3 framework. Specifically, the use 1832 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1833 based Access Control Model RFC 2575 [RFC2575] is recommended. 1835 It is then a customer/user responsibility to ensure that the SNMP 1836 entity giving access to an instance of this MIB, is properly 1837 configured to give access to the objects only to those principals 1838 (users) that have legitimate rights to indeed GET or SET 1839 (change/create/delete) them. 1841 8. Acknowledgments 1843 The authors wish to thank Juergen Schoenwaelder, David Partain, Shawn 1844 A. Routhier, Ed Yarwood, John Linton, Shyamal Prasad Juan-Francisco 1845 Martin, Dave Thaler, and Bert Wijnen for their invaluable comments. 1847 9. Authors' Addresses 1849 Javier Pastor-Balbas Tel: +34-91-339-3819 1850 Ericsson Espana S.A. eMail: J.Javier.Pastor@ericsson.com 1851 Network Communication Services 1852 Ombu 3, 4th floor 1853 Madrid, 28045 1854 Spain 1856 Maria-Carmen Belinchon Tel: +34-91-339-3535 1857 Ericsson Espana S.A. eMail: Maria.C.Belinchon@ericsson.com 1858 Network Communication Services 1859 Ombu 3, 4th floor 1860 Madrid, 28045 1861 Spain 1863 10. Revision History 1865 10.1 Changes from 1867 o Open issues updated 1869 o Section 2: Reference to RFC227x changed to RFC257x 1871 o Section 4: Inside the sctpRtoAlgorithm definition has been put 1872 "other" first rather than last. That way, it won't end up in the 1873 middle of things when new enumerations are added later. 1875 10.2 Changes from 1877 o Change of "Simple" word to "Stream" word in SCTP acronyms 1879 o Version of the MIB based on SCTPv10 1881 o Section 2: Update SNMP Framework to include the standard 1882 explanation 1884 o New Structure for the MIB: 1885 sctp 1886 \- sctpObjects 1887 \- sctpScalars 1888 \- sctpTables 1889 \- sctpMIBConformance 1891 o Section 4.1.2: Unit of Conformance updated (functional structure). 1893 o MAX-ACCESS clauses reviewed 1895 o The general statistics has been re-ordered, placed before the 1896 tables. 1898 o In SMIv2, indexes should be not-accessible (= the object type is a 1899 column in a table used as index and may not be used as an operand in 1900 any operation != SMIv1) (pp109-110 in []) 1902 o IPv6 compatible: 1903 - Change of Primary/Local/Remote addresses 1904 - PENDING: check "MODULE-COMPLIANCE" 1906 o Row Status included in AssocTable, AssocLocal and AssocRem to 1907 create, modify and delete rows in the tables. 1909 o SCTP general statistics changed from Counter32 to Counter64 since 1910 it supports more data changes. 1912 o sctpCurrEstab ("State-related variables and statistics" section) 1913 variable changed from Gauge32 to Counter32. 1915 o sctpAssocRemAddressT1expired and sctpAssocRemAddressT2expired have 1916 been removed from the remote table and added in the general 1917 association data since they are variables per association (not per IP 1918 address). 1920 o sctpAssocDropDatag statistic has been removed from the general 1921 association statistics since it had an ambiguous meaning. 1923 o Explained the meaning of the unordered chunks (chunks in which the 1924 U bit is set to 1) in sctpStatOutOfOrderSentChunks and 1925 sctpStatOutOfOrderRecChunks. 1927 o Added sctpChecksumErrorCounter to collect information about wrong 1928 checksums received from the peer. 1930 o Specify that sctpStatSentChunks and sctpStatRecChunks does not 1931 contain retransmission chunks. 1933 o Reword the Security Considerations chapter pointing out that IPsec 1934 does not secure the network but it provides end-to-end security over 1935 a network. 1937 o sctpAssocRemAddressRtxChunks replaced as a variable per 1938 association, meaning the number of chunks retransmited to the peer in 1939 the current association. 1941 o sctpHeartBeatMisses and sctpMaxRetr have been replaced from the 1942 general SCTP statistics to the remote IP address table 1943 (sctpHeartBeatMisses) and in the association table (sctpMaxRetr). 1945 o Specify that the retransmissions in the general SCTP statistics 1946 include control plus data chunks. 1948 o Included heartbeat timer for remote IP address. 1950 o Removed sctpAssocRemAddressHeartBeatMisses variable from the remote 1951 IP address table. 1953 o Removed sctpAssocRemAddressT3expired variable from the remote IP 1954 address table. 1956 o Updated variables to the new SCTP states defined in v10. 1958 10.3 Changes from 1960 o sctpRtoMin - stray "." outside the double-quotes in the DESCRIPTION 1961 clause. 1963 o sctpRtoMax - stray "." outside the double-quotes in the DESCRIPTION 1964 clause. 1966 o sctpAssocRemHostName - the type OCTECT STRING should be OCTET 1967 STRING. 1969 o sctpAssocRemPrimaryAddress - the DESCRIPTION clause is missing its 1970 closing ouble-quote. 1972 o sctpConformance - this is defined as { sctpMIB 2 }, then never 1973 used; instead sctpMIBConformance (which is undefined) is used in the 1974 definition of sctpMIBGroups and sctpMIBCompliances. 1976 o Reworded the MIB organization 1978 o Removed maximum number of concurrent associations 1980 o In sctpMIBCompliance, removed a missing comma in MANDATORY-GROUPS. 1982 o In sctpAssocTablesVariablesGroup and sctpAssocStatGroup, removed 1983 extra commas at end of OBJECTS list. 1985 o sctpAssocInStreams. ACCESS changed from read-create to read-only. 1987 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1988 changed from per remote IP address to per association. 1990 o Comment on sctpAssocRemAddressHBTimer specifies now that the 1991 manager can change it. 1993 o ACCESS on sctpAssocRemAddressHBTimer changed from read-only to 1994 read-write. 1996 o ACCESS on sctpAssocRemAddressRetransCount changed from read-write 1997 to read-only. 1999 o Move sctpStatChecksumErrorCounter from general statistics to per 2000 association. 2002 o sctpMaxInStreams � It�s a sctp-user feature. 2004 o sctpStatRetransChunks � It�s more useful to have this statistic in 2005 a association basis 2007 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 2008 have been created again instead of per association in order to follow 2009 the draft. If some implementations want to have the same value for 2010 all the associations they have, they should set all the variables in 2011 the different remote addresses to the same value. 2013 10.3 Changes from 2015 o Deleting all the RowStatus Structure. Associated text rewording in 2016 Tables section. 2018 o Variable StartTime added in all the tables in order to specify the 2019 creation time. 2021 o Adding the Association reverse lookup table for easier management. 2022 Associated text rewording in tables section. 2024 o Remove sctpInitialT1 and sctpInitialT2, since these values are 2025 equal to RTO. 2027 o Change of the Heartbeats to a per-association basis 2029 o Conformance up-to-date with all of this. 2031 10.4 Changes from 2033 Main changes are due to the alignment with the TCP and UDP MIBs and 2034 the inclusion of new lookup tables. 2035 o Convert MIB to a read-only 2036 o Counters ends with �s� 2038 o Include �unknown� as an option for InetAddressType in conformance 2040 o Terminology fix: CLOSED state, unordered chunks instead of out-of- 2041 order, .. 2043 o HBFlag changed to per remote address 2045 o ChecksumErrors out of the AssocTable and hangs from Scalars 2047 o Update Ports from Unsigned32 to InetPortNumber according to 2048 RFC2851-update 2050 o Rework inverse tables: five new lookup tables 2052 o Remove INTEGER32 and change it to UNSIGNED32 2054 o Replace Counter32 by Counter64 2056 o Split Sent and Received chunks per association into control, 2057 ordered and unordered chunks 2059 10.5 Changes from 2061 Changes due to the IETF-51 meeting and requests from the mailing 2062 list. 2063 o Typo errors 2065 o Objects renumbering 2067 o All counters to Counter32 to be backward compatible, not to waste 2068 memory. Operators needing more than 32 bits will do it by 2069 augmentations. 2071 o Limit the number of IP address size when index 2073 o Specify that a port number with value zero means unknown port 2074 number according to the RFC2851-update 2076 Changes due to the alignment with the RFC2851-update. 2078 o Include clarification text of the IP address types supported in the 2079 SCTP MIB. Chapter 3.1.2.1 (Association table) 2081 o Remote Primary IP address: Addition of the ipv4z an ipv6z types for 2082 non-globally IP addresses in which a scope identifier is needed. 2084 Addition of the scope of ipv6 type. All of them according to the 2085 RFC2851-update v04 2087 o InetAddressType for local and remote IP addresses: 2089 Limit UNKNOWN type only for unknown IP address format. Remove UNKNOWN 2090 type for zero-length value in the InetAddress since it will be never 2091 zero-length due to the size restriction (0..64) 2093 Addition of the ipv4z an ipv6z types for non-globally IP addresses in 2094 which a scope identifier is needed. Addition of the scope of ipv6 2095 type. All of them according to the RFC2851-update v04 2097 o Clarify when mapping DNS <-> IPaddress occurs with the remote IP 2098 addresses 2100 o Conformance: 2102 Description: Specify that the SCTP MIB only need to support IPv4/IPv6 2103 addresses without a zone index, unknown type and DNS names. Support 2104 for IPv4/IPv6 addresses with zone indices is not required. 2106 InetAddressType for primary, local and remote IP addresses: Clarify 2107 that the implementation is only required to support IPv4 and IPv6 2108 address types without zone indices. Clarify also that UNKONWN type is 2109 only used in case of local and remote addresses when invalid/unknown 2110 IP address format 2112 InetAddress value of primary, local and remote IP address: Removal of 2113 the InetAddress values supported. Limitation of the supported IP 2114 address types is already included in the InetAddressType 2116 o Revision of the RFC2851-update v05. Changes in this draft does not 2117 affect the SCTP MIB. 2119 10.6 Changes from 2121 Changes due to the IPv6mib Design Team and the Sigtran mailing list. 2123 o RFC2851-update v06 (changes) does not affect the SCTP MIB 2125 o Typo errors 2127 o Restructure the MIB organization (tree): 2128 sctp 2129 \- sctpParameters 2130 \- sctpStats 2132 o Modify conformance section according to the new MIB structure. 2133 Statistics and lookup tables will be optional 2134 o Clarify that the SCTP MIB is based on the TCP MIB update 2135 (RFC2012update) and the TCs for Internet Network Addresses 2136 (RFC2851update) � remove reference to RFC2452 2138 o Replace "Sent" by "out" and "Received" by "in" in statistics 2140 o Change the sctpAssocId to exclude the value zero. This allows other 2141 MIBs to reference associations and to use the value 0 to indicate no 2142 association 2144 o Clarify sctpRemHostName to be zero-length value when no remote host 2145 name was received at the initialization stage 2147 o Limit the range of local and remote ports to (1..65535). Value 0 2148 (unknown port number according to RFC2851-update) is not valid in 2149 SCTP associations since there is no way of having an assoc with an 2150 unknown local or remote port 2152 o sctpAssocRemPrimaryAddressType and sctpAssocRemPrimaryAddress value 2153 to be filled in with a zero length string until valid values are 2154 received in the INIT or INIT ACK chunk 2156 o sctpAssocRemAddress and sctpAssocLocalAddressIP size upper limit 2157 restriction to 36, as TCP MIB 2159 o Change to Counter64 those counters which may wrap in less than an 2160 hour 2162 o Change sctpMaxAssoc variable to Integer32 since value �1 is allowed 2163 for dynamic maximum number of associations 2165 o Added a new column in the association table to give a pointer to 2166 the primary system level process which holds the association 2167 endpoint(sctpAssocPrimaryProcess) 2169 o Specify in the security section, which object should be handled 2170 carefully for security reasons 2172 10.7 Changes from 2174 o Change of the variable structure to: 2176 MIB-2 {1 3 6 1 2 2} 2177 +--(xxx)sctpMIB 2178 | 2179 +--(1) sctpObjects 2180 | | 2181 | +--(1) sctpStats 2182 | | | 2183 | | +-- 2184 | | 2185 | +--(2)sctpParameters 2186 | | | 2187 | | +-- 2188 | | 2189 | +--(3) sctpAssocTable 2190 | | 2191 | +--(4) sctpAssocLocalAddressTable 2192 | | 2193 | +--(5) sctpAssocRemAddressTable 2194 | | 2195 | +--(6) sctpLookupLocalPortTable 2196 | | 2197 | +--(7) sctpLookupRemPortTable 2198 | | 2199 | +--(8) sctpLookupRemHostNameTable 2200 | | 2201 | +--(9) sctpLookupRemPrimIPAddrTable 2202 | | 2203 | +--(10) sctpLookupRemIPAddrTable 2204 | 2205 | 2206 +--(2)sctpConformance 2207 | 2208 +--(1) sctpCompliances 2209 | | 2210 | +-sctpCompliance 2211 | 2212 +--(2) sctpGroups 2213 | 2214 +--(1) sctpParametersGroup 2215 | 2216 +--(2) sctpStatGroup 2217 | 2218 +--(3) sctpAssocTableParametersGroup 2219 | 2220 +--(4) sctpInverseGroup 2222 o New chapter for compilation notes created 2224 o References ordered and updated