idnits 2.17.1 draft-ietf-sigtran-sctp-mib-02.txt: -(1651): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 35 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 159 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([SIGAS]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 173 has weird spacing: '...Scalars sctp...' == Line 617 has weird spacing: '...eceived by th...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 1, 2000) is 8575 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 2012' is mentioned on line 94, but not defined ** Obsolete undefined reference: RFC 2012 (Obsoleted by RFC 4022) == Missing Reference: 'RFC 2452' is mentioned on line 95, 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 97 == Missing Reference: 'SNMPArch' is mentioned on line 124, but not defined == Missing Reference: 'SMIv1' is mentioned on line 129, but not defined == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 129, but not defined == Missing Reference: 'SNMPv1Traps' is mentioned on line 130, but not defined == Missing Reference: 'SMIv2' is mentioned on line 131, but not defined == Missing Reference: 'SNMPv2TC' is mentioned on line 131, but not defined == Missing Reference: 'SNMPv2Conf' is mentioned on line 132, but not defined == Missing Reference: 'SNMPv1' is mentioned on line 145, but not defined == Missing Reference: 'SNMPv2c' is mentioned on line 138, but not defined == Missing Reference: 'SNMPv2TM' is mentioned on line 140, but not defined == Missing Reference: 'SNMPv3MP' is mentioned on line 141, but not defined == Missing Reference: 'SNMPv3USM' is mentioned on line 141, but not defined == Missing Reference: 'SNMPv2PO' is mentioned on line 147, but not defined == Missing Reference: 'SNMPv3App' is mentioned on line 150, but not defined == Missing Reference: 'SNMPv3VACM' is mentioned on line 151, but not defined == Missing Reference: 'ConvSMIv2' is mentioned on line 282, but not defined == Missing Reference: 'SCTP' is mentioned on line 1099, but not defined == Unused Reference: 'MIBMPLS' is defined on line 1353, but no explicit reference was found in the text == Unused Reference: 'SecSNMP' is defined on line 1358, but no explicit reference was found in the text == Unused Reference: 'Cong' is defined on line 1361, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 1368, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 1372, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 1376, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 1379, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1382, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1386, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1390, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 1394, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 1397, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 1401, but no explicit reference was found in the text == Unused Reference: 'RFC2452' is defined on line 1405, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 1408, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 1416, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1420, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1427, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'SIGAS' -- Possible downref: Non-RFC (?) normative reference: ref. 'MIBMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'SecSNMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'Cong' ** Obsolete normative reference: RFC 2012 (Obsoleted by RFC 4022) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2452 (Obsoleted by RFC 4022, RFC 8096) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) Summary: 23 errors (**), 0 flaws (~~), 43 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Pastor 3 INTERNET-DRAFT M. Belinchon 4 Expires: May 2001 Ericsson 6 November 1, 2000 8 Stream Control Transmission Protocol 9 Management Information Base using SMIv2 10 12 Status of this memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that other 19 groups may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or cite them other than as "work in progress". 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/lid-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 This document is an individual submission to the IETF. Comments 33 should be directed to the authors. 35 Abstract 37 The Stream Control Transmission Protocol (SCTP) is a reliable 38 transport protocol operating on top of a connectionless packet 39 network such as IP, designed to transport PSTN signaling messages 40 over the connectionless packet network, but is capable of broader 41 applications. 43 This memo defines the Management Information Base (MIB) module which 44 describes the minimum amount of objects needed to manage the 45 implementation of the SCTP. 47 Open Issues 49 - Remove this section. 51 - Remove Revision History 53 - Decide under which object identifier branch of the SNMP tree, 54 SCTP will be placed (value obtained when submitted to the IETF 55 editor). 57 - Update references to drafts [SIGAS]. 59 TABLE OF CONTENTS 61 Open Issues.........................................................2 62 1. Introduction.....................................................3 63 1.1 Abbreviations...................................................3 64 2. The SNMP Framework...............................................3 65 3. Structure of the MIB.............................................4 66 3.1 Objects........................................................5 67 3.1.1 Scalars......................................................5 68 3.1.2 Association Tables...........................................6 69 3.2 Conformance.....................................................9 70 3.2.1 Groups........................................................9 71 3.2.2 Compliance....................................................9 72 4. Definitions......................................................9 73 5. References.....................................................29 74 6. Security Consideration..........................................31 75 7. Acknowledgments.................................................32 76 8. Authors' Addresses..............................................32 77 9. Revision History................................................32 78 9.1 Changes from ........................32 79 9.2 Changes from ..............32 80 9.3 Changes from ..............34 81 9.2 Changes from ..............35 83 1. Introduction 85 This memo defines the Management Information Base (MIB) module which 86 describes managed objects for implementations of the SCTP. 88 The document starts with a brief description of the SNMP framework 89 and continues with the MIB explanation and security consideration 90 among others. 92 The managed objects in this MIB module have been based on RFC 2012: 93 "SNMPv2 Management Information Base for the Transmission Control 94 Protocol using SMIv2" [RFC 2012] and "IP Version 6 Management 95 Information Base for the Transmission Control Protocol" [RFC 2452]. 97 Terms related to the SCTP architecture are explained in [1]. Other 98 specific abbreviations are listed below. 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119 [RFC2119]. 104 1.1 Abbreviations 106 DNS - Domain Name System 107 IANA - Internet Assigned Numbers Authority 108 IETF - Internet Engineering Task Force 109 IP - Internet Protocol 110 MIB - Management Information Base 111 RFC - Request For Comment 112 RTO - Retransmission Time Out 113 SCTP - Stream Control Transmission Protocol 114 SMI - Structure of Management Information 115 SNMP - Simple Network Management Protocol 116 TCB - Transmission Control Block 117 TCP - Transmission Control Protocol 119 2. The SNMP Framework 121 The SNMP Management Framework presently consists of five major 122 components: 124 - An overall architecture, described in RFC 2271 [SNMPArch]. 126 - Mechanisms for describing and naming objects and events for the 127 purpose of management. The first version of this Structure of 128 Management Information (SMI) is called SMIv1 and described in 129 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 130 [SNMPv1Traps]. The second version, called SMIv2, is described 131 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 132 [SNMPv2Conf]. 134 - Message protocols for transferring management information. The 135 first version of the SNMP message protocol is called SNMPv1 nd 136 described in RFC 1157 [SNMPv1]. A second version of the SNMP 137 message protocol, which is not an Internet standards track 138 protocol, is called SNMPv2c and described in RFC 1901 [SNMPv2c] 139 and RFC 1906 [SNMPv2TM]. The third version of the message 140 protocol is called SNMPv3 and described in RFC 1906 [SNMPv2TM], 141 RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 143 - Protocol operations for accessing management information. The 144 first set of protocol operations and associated PDU formats is 145 described in RFC 1157 [SNMPv1]. A second set of protocol 146 operations and associated PDU formats is described in RFC 1905 147 [SNMPv2PO]. 149 - A set of fundamental applications described in RFC 2273 150 [SNMPv3App] and the view-based access control mechanism 151 described in RFC 2575 [SNMPv3VACM]. 153 Managed objects are accessed via a virtual information store, termed 154 the Management Information Base or MIB. Objects in the MIB are 155 defined using the mechanisms defined in the SMI. This memo specifies 156 a MIB module that is compliant to the SMIv2. A MIB conforming to the 157 SMIv1 can be produced through the appropriate translations. The 158 resulting translated MIB must be semantically equivalent, except 159 where objects or events are omitted because no translation is 160 possible (use of Counter64). Some machine-readable information in 161 SMIv2 will be converted into textual descriptions in SMIv1 during the 162 translation process. However, this loss of machine-readable 163 information is not considered to change the semantics of the MIB. 165 3. Structure of the MIB 167 The MIB is structured in the following way: 169 sctpMib 170 / \ 171 sctpObjects sctpConformance 172 / \ / \ 173 sctpScalars sctpTables sctpGroups sctpCompliances 174 | 175 sctpCompliance 177 where: 178 - sctpObjects, all the SCTP objects are defined under this 179 branch. 181 - sctpScalars, containing only scalars values. It can be split 182 into: 184 - General variables, listing the main SCTP variables. 186 - Statistics for traffic measurements. 187 - SCTP state related statistics 188 - other statistics 190 - sctpTables, to hold data from each association together with 191 the main statistics (per association or transport address). 192 Local and remote tables are included into the general 193 association table to allow multiples IP addresses in order 194 to support the multi-home feature. 196 - sctpConformance, for the Unit of Conformance. 198 - sctpGroups, SCTP MIB variables have been grouped according 199 to their function and the context they belong to (general 200 variables, variables/statistics per association, variables 201 per local IP address and variables/statistics per remote IP 202 address). 204 - sctpCompliances, Minimal list of objects in the SCTP MIB 205 module that an agent developer must implement. 207 3.1 Objects 209 3.1.1 Scalars 211 3.1.1.1 Protocol General Variables 213 The first section of the MIB contains the general variables of the 214 SCTP protocol. Maximum, minimum, values by default and initial values 215 are listed here. 217 Based on the TCP MIB [RFC2012], SCTP RTO mechanism is defined in the 218 same way. In SCTP protocol, only options 'other' and 'vanj' remain 219 because SCTP protocol defines Van Jacobson's algorithm as the one to 220 be used to calculate RTO. 'Other' is left for future use ('rsre' 221 algorithm was eliminated because MIL-STD-1778 is Cancelled-No 222 Superseding Document according to the Military Standard library and 223 'constant' option doesn't fulfill the SCTP protocol description). 225 3.1.1.2 Statistics for traffic Measurements 226 Statistics included here are related to the whole SCTP layer. 227 Statistics related to a specific association, or local/remote IP 228 addresses are defined inside its concerned table. 230 3.1.1.2.1 State-Related Statistics 232 These measures are based in the TCP model, but adapted to the SCTP 233 states. They store the number of succeeded association attempts, how 234 many associations have been initiated by the local or the remote SCTP 235 layer, or just the number of associations terminated in a graceful 236 (by means of SHUTDOWN procedure) or ungraceful way (by means of CLOSE 237 procedure). 239 3.1.1.2.2 Other Statistics 241 There is an statistic related to the SCTP packets, i.e., the number 242 of out of the blue packets received by the local host. The remainder 243 statistics are based on the data unit of SCTP: the chunk. In this 244 way, the whole picture of the SCTP layer is covered. 246 3.1.2 Association Tables 248 The part of the MIB to define each association is structured 249 according to a expanded table. There is a main table (called 250 association table), indexed by the association identification. The 251 association identification is a value to identify in a unique way an 252 association. 254 The MIB does not restrict which value must be written here. It can be 255 the tag value, or the TCB creation time, or any other value the 256 implementer decides. 258 This main table contains common information for a given association 259 and two other tables inside: 261 a) Table for local IP addresses information: This table stores 262 information related to the local IP address/-es reserved for the 263 association. It's indexed by the local IP address. 265 b) Table for remote IP addresses information: This table stores 266 information related to the remote IP address/-es reserved for the 267 association. It's indexed by the remote IP addresses. 269 Note that the IP address indexing the tables is valid for IPv4, IPv6 270 and DNS. Therefore, IP address is defined by the Internet address 271 type and the value of the IP address, according to the Textual 272 Conventions for Internet Network Address [RFC2851]. 274 However, DNS value is not being used to identify an IP address since 275 it is only valid during initialization (once this stage is finished, 276 both sides only use IP addresses). To keep the name of the remote 277 peer, an entry has been created in the association table 278 (sctpAssocRemHostName). When no DNS name is provided by the remote 279 endpoint at init time, this value will be NULL. Otherwise, the 280 received DNS name will be stored. 282 The variable RowStatus [ConvSMIv2] allows creating and deleting rows 283 in the tables. In the association table, creation of entries will be 284 performed after creating the TCB in both sides of the association. In 285 the local and remote tables, creation of entries will be performed 286 after the association table creation or when new IP addresses are 287 added to the association (it this feature is enabled in 288 the SCTP protocol). 290 After deleting the TCB, the local and remote table will be deleted, 291 and then the association table. Also, it is possible to delete 292 entries in the local and remote table when IP addresses are removed 293 from the association context by the SCTP layer (if this feature is 294 enabled). 296 EDITORS NOTE: The main purpose of the MIB and the access policy have 297 to be agreed amongst the WG folks. 298 - Only providing statistics and status information about 299 associations? 300 - Allow configuration of associations too? 301 - When to perform creation and deletion of entries in tables? 302 A good input will be given by the TCP MIB editors. 304 sctpAssocTable 305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 306 | sctpAssocId (index) / ... | 307 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 308 | sctpAssocRemHostName \ ... | 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 | sctpAssocLocalSCTPPort / ... | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | sctpAssocRemSCTPPort \ ... | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | sctpAssocRemPrimaryAddressType / ... | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | sctpAssocRemPrimaryAddress \ ... | 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | sctpAssocState / ... | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 | sctpAssocInStreams \ ... | 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 | sctpAssocOutStreams / ... | 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 | sctpAssocMaxRetr \ ... | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | sctpAssocT1expired / ... | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | sctpAssocT2expired \ ... | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | sctpAssocRtxChunks / ... | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | sctpAssocChecksumErrorCounter \ ... | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | sctpAssocRowStatus / ... | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | \ ... | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | sctpAssocLocalAddressTable | 339 | | 340 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 341 | | sctpAssocLocalAddressIPType(index) \ ... | | 342 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 343 | | sctpAssocLocalAddressIP (index) \ ... | | 344 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 345 | | sctpAssocLocalAddressRowStatus \ ... | | 346 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 347 | | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | sctpAssocRemAddressTable | 350 | | 351 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 352 | | sctpAssocRemAddressIPType (index) \ ... | | 353 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 354 | | sctpAssocRemAddressIP (index) \ ... | | 355 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 356 | | sctpAssocRemAddressStatus \ ... | | 357 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 358 | | sctpAssocRemAddressRTO \ ... | | 359 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 360 | | sctpAssocRemAddressHeartBeatFlag \ ... | | 361 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 362 | | sctpAssocRemAddressHeartBeatTimer \ ... | | 363 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 364 | | sctpAssocRemAddressPathMaxRx \ ... | | 365 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 366 | | sctpAssocRemAddressRetransCount \ ... | | 367 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 368 | | sctpAssocRemAddressRowStatus \ ... | | 369 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-/+-+-+-+ | 370 | | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 Every entry is explained when defining the MIB. 374 3.2 Conformance 376 3.2.1 Groups 378 This section includes all the variables defined in the MIB grouped by 379 function(variables or statistics) and context (SCTP general 380 parameters, 381 association context, local IP address context or remote IP address 382 context). 383 Therefore following groups have been created: 385 - General variables for the SCTP layer. 386 - General statistics for the states of the SCTP layer. 387 - General statistics for the SCTP layer. 388 - Variables and statistics per association, and variables per 389 local and remote IP address. 390 - Statistics per remote IP address. 392 -- QUIZAS LA 4A PODRIA DIVIDIRSE.HAY MUCHOS CONCEPTOS MEZCLADOS 394 3.2.2 Compliance 396 Requirements of the SCTP MIB to be implemented. 398 4. Definitions 400 SCTP-MIB DEFINITIONS ::= BEGIN 402 IMPORTS 403 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, Counter64, 404 mib-2 405 FROM SNMPv2-SMI -- RFC2578 406 MODULE-COMPLIANCE, OBJECT-GROUP 407 FROM SNMPv2-CONF -- RFC2580 408 RowStatus 409 FROM SNMPv2-TC -- RFC2579 410 InetAddressType, InetAddress 411 FROM INET-ADDRESS-MIB -- RFC2851 412 ; 414 sctpMIB MODULE-IDENTITY 415 LAST-UPDATED "200011060000Z" 416 ORGANIZATION "IETF SIGTRAN Working Group" 417 CONTACT-INFO 418 " Maria-Carmen Belinchon-Vergara 419 Jose-Javier Pastor-Balbas 421 Postal: Ericsson Espana S. A. 422 C/Retama 7 423 28045 Madrid 424 Spain 426 Phones: +34 91 339 3535 427 +34 91 339 3819 429 Emails: Maria.C.Belinchon@ericsson.com 430 J.Javier.Pastor@ericsson.com" 431 DESCRIPTION 432 "The MIB module for managing SCTP implementation." 433 REVISION 434 "200011060000Z" 435 DESCRIPTION 436 "MIB module developed for the SIGTRAN IETF group. Based on 437 SCTP, RFC2960" 438 ::= { xxxx } -- IANA needs to choose this value 439 -- when sent to the RFC editor 441 -- Top-level structure of the MIB 443 sctpObjects OBJECT IDENTIFIER ::= { sctpMIB 1 } 444 sctpConformance OBJECT IDENTIFIER ::= { sctpMIB 2 } 446 sctpScalars OBJECT IDENTIFIER ::= { sctpObjects 1 } 447 sctpTables OBJECT IDENTIFIER ::= { sctpObjects 2 } 449 -- PROTOCOL GENERAL VARIABLES 450 -- ************************** 452 sctpRtoAlgorithm OBJECT-TYPE 453 SYNTAX INTEGER { 454 other(1), -- Other new one. Future use 455 vanj(2) -- Van Jacobson's algorithm 456 } 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The algorithm used to determine the timeout value (T3-rtx) 461 used for re-transmitting unacknowledged chunks." 463 ::= { sctpScalars 1 } 465 sctpRtoMin OBJECT-TYPE 466 SYNTAX Unsigned32 467 UNITS "milliseconds" 468 MAX-ACCESS read-write 469 STATUS current 470 DESCRIPTION 471 "The minimum value permitted by a SCTP implementation for the 472 retransmission timeout, measured in milliseconds. More 473 refined semantics for objects of this type depend upon the 474 algorithm used to determine the retransmission timeout. 475 Minimum recommended value is 1000 milliseconds. Some telephony 476 applications could require less than 1 second, see [SIGAS] for 477 further information." 479 ::= { sctpScalars 2 } 481 sctpRtoMax OBJECT-TYPE 482 SYNTAX Unsigned32 483 UNITS "milliseconds" 484 MAX-ACCESS read-write 485 STATUS current 486 DESCRIPTION 487 "The maximum value permitted by a SCTP implementation for the 488 retransmission timeout, measured in milliseconds. More 489 refined semantics for objects of this type depend upon the 490 algorithm used to determine the retransmission timeout. 491 Recommended value is 60000 milliseconds." 493 ::= { sctpScalars 3 } 495 sctpRtoInitial OBJECT-TYPE 496 SYNTAX Unsigned32 497 UNITS "milliseconds" 498 MAX-ACCESS read-write 499 STATUS current 500 DESCRIPTION 501 "Initial value for the Retransmission timer. Recommended value 502 is 3000 milliseconds." 504 ::= { sctpScalars 4 } 506 sctpValCookieLife OBJECT-TYPE 507 SYNTAX Unsigned32 508 UNITS "milliseconds" 509 MAX-ACCESS read-write 510 STATUS current 511 DESCRIPTION 512 "Valid cookie life in the 4-way start-up handshake procedure. 513 Recommended value: 60000 milliseconds." 515 ::= { sctpScalars 5 } 517 sctpMaxInitRetr OBJECT-TYPE 518 SYNTAX Unsigned32 519 MAX-ACCESS read-write 520 STATUS current 521 DESCRIPTION 522 "The maximum number of retransmissions at the start-up phase 523 (INIT and COOKIE ECHO chunks). Recommended value: 8 attempts." 525 ::= { sctpScalars 6 } 527 sctpInitialT1 OBJECT-TYPE 528 SYNTAX Unsigned32 529 UNITS "milliseconds" 530 MAX-ACCESS read-write 531 STATUS current 532 DESCRIPTION 533 "Initial value for the Start-up T1 timer." 535 ::= { sctpScalars 7 } 537 sctpInitialT2 OBJECT-TYPE 538 SYNTAX Unsigned32 539 UNITS "milliseconds" 540 MAX-ACCESS read-write 541 STATUS current 542 DESCRIPTION 543 "Initial value for the Shutdown T2-shutdown timer." 545 ::= { sctpScalars 8 } 547 -- STATE-RELATED STATISTICS 549 sctpCurrEstab OBJECT-TYPE 550 SYNTAX Counter32 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "The number of SCTP associations for which the current state 555 is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING." 557 ::= { sctpScalars 9 } 559 sctpActiveEstab OBJECT-TYPE 560 SYNTAX Counter32 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION 564 "The number of times that SCTP associations have made a direct 565 transition to the ESTABLISH state from the COOKIE-ECHOED 566 state: COOKIE-ECHOED -> ESTABLISHED. The upper layer has 567 initiated the association attempt." 569 ::= { sctpScalars 10 } 571 sctpPassiveEstab OBJECT-TYPE 572 SYNTAX Counter32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The number of times that SCTP associations have made a direct 577 transition to the ESTABLISHED state from the CLOSED state: 578 CLOSED -> ESTABLISHED. The remote endpoint has initiated the 579 association attempt." 581 ::= { sctpScalars 11 } 583 sctpAborted OBJECT-TYPE 584 SYNTAX Counter32 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "The number of times that SCTP associations have made a direct 589 transition to the CLOSED state from any state using the 590 primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful 591 termination of the association." 593 ::= { sctpScalars 12 } 595 sctpShutdowns 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 CLOSE state from either the SHUTDOWN-SENT 602 state or the SHUTDOWN-ACK-SENT state. Graceful termination of 603 the association." 605 ::= { sctpScalars 13 } 607 -- OTHER LAYER STATISTICS 609 sctpStatOutOfBlue OBJECT-TYPE 610 SYNTAX Counter64 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "Number of out of the blue packets (SCTP packet correctly 615 formed -right checksum- but the receiver is not able to 616 identify the association to which this packet belongs) 617 received by the host." 619 ::= { sctpScalars 14 } 621 sctpStatSentChunks OBJECT-TYPE 622 SYNTAX Counter64 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "Number of SCTP control and data chunks, sent to the peers (no 627 retransmissions included)." 629 ::= { sctpScalars 15 } 631 sctpStatRecChunks OBJECT-TYPE 632 SYNTAX Counter64 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "Number of SCTP control and data chunks, received from the 637 peers (no retransmissions included)." 639 ::= { sctpScalars 16 } 641 sctpStatOutOfOrderSentChunks OBJECT-TYPE 642 SYNTAX Counter64 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "Number of unordered chunks (data chunks in which the U bit is 647 set to 1) sent to the peers." 649 ::= { sctpScalars 17 } 651 sctpStatOutOfOrderRecChunks OBJECT-TYPE 652 SYNTAX Counter64 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "Number of unordered chunks (data chunks in which the U bit is 657 set to 1) received from the peers." 659 ::= { sctpScalars 18 } 661 sctpStatFragmentedUsrMessages OBJECT-TYPE 662 SYNTAX Counter64 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "Number of user messages that have to be fragmented because of 667 the MTU." 669 ::= { sctpScalars 19 } 671 sctpStatReassembledUsrMessages OBJECT-TYPE 672 SYNTAX Counter64 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION 676 "Number of user messages reassembled." 678 ::= { sctpScalars 20 } 680 -- SCTP ASSOCIATION DESCRIPTION PARAMETERS 681 -- *************************************** 683 -- the SCTP Association TABLE 684 -- ************************** 686 -- The SCTP association table contains information about each 687 -- association that the local endpoint is taking part. 689 sctpAssocTable OBJECT-TYPE 690 SYNTAX SEQUENCE OF SctpAssocEntry 691 MAX-ACCESS not-accessible 692 STATUS current 693 DESCRIPTION 694 "A table containing SCTP association-specific information." 696 ::= { sctpTables 1 } 698 sctpAssocEntry OBJECT-TYPE 699 SYNTAX SctpAssocEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "General common variables and statistics for the whole 704 association." 705 INDEX { sctpAssocId } 707 ::= { sctpAssocTable 1 } 709 SctpAssocEntry ::= SEQUENCE { 710 sctpAssocId Unsigned32, 711 sctpAssocRemHostName OCTET STRING, 712 sctpAssocLocalSCTPPort Unsigned32, 713 sctpAssocRemSCTPPort Unsigned32, 714 sctpAssocRemPrimaryAddressType InetAddressType, 715 sctpAssocRemPrimaryAddress InetAddress, 716 sctpAssocState INTEGER, 717 sctpAssocInStreams Unsigned32, 718 sctpAssocOutStreams Unsigned32, 719 sctpAssocMaxRetr Unsigned32, 720 sctpAssocT1expired Counter32, -- Statistic 721 sctpAssocT2expired Counter32, -- Statistic 722 sctpAssocRtxChunks Counter32, -- Statistic 723 sctpAssocChecksumErrorCounter Counter64, -- Statistic 724 sctpAssocRowStatus RowStatus 725 } 727 sctpAssocId OBJECT-TYPE 728 SYNTAX Unsigned32 729 MAX-ACCESS not-accessible 730 STATUS current 731 DESCRIPTION 732 "Association Identification. Value identifying the association 733 (typically the Initiate Verification Tag)." 735 ::= { sctpAssocEntry 1 } 737 sctpAssocRemHostName OBJECT-TYPE 738 SYNTAX OCTET STRING (SIZE(0..255)) 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "Peer's DNS name. If no DNS domain name was received at init 743 time (embedded in the INIT or INIT-ACK chunk) from the peer, 744 this entry will be meaningless, therefore it will contain a 745 NULL value. Otherwise, the remote host name received at init 746 time will be stored." 748 ::= { sctpAssocEntry 2 } 750 sctpAssocLocalSCTPPort OBJECT-TYPE 751 SYNTAX Unsigned32 752 MAX-ACCESS read-create 753 STATUS current 754 DESCRIPTION 755 "Local SCTP port number used for this association." 757 ::= { sctpAssocEntry 3 } 759 sctpAssocRemSCTPPort OBJECT-TYPE 760 SYNTAX Unsigned32 761 MAX-ACCESS read-create 762 STATUS current 763 DESCRIPTION 764 "Remote SCTP port number used for this association." 766 ::= { sctpAssocEntry 4 } 768 sctpAssocRemPrimaryAddressType OBJECT-TYPE 769 SYNTAX InetAddressType 770 MAX-ACCESS read-create 771 STATUS current 772 DESCRIPTION 773 "Internet type of primary destination IP address. 774 - unknown (0) An unknown address type. This value MUST be 775 used if the value of the corresponding InetAddress object 776 is a zero-length string. It may also be used to indicate an 777 IP address different from IPv4 or IPv6. This value is used 778 in this MIB for error conditions. 780 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 781 textual convention [RFC2851]. 783 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 784 textual convention [RFC2851]." 786 ::= { sctpAssocEntry 5 } 788 sctpAssocRemPrimaryAddress OBJECT-TYPE 789 SYNTAX InetAddress 790 MAX-ACCESS read-create 791 STATUS current 792 DESCRIPTION 793 "Primary destination IP address. An InetAddress value is 794 always interpreted within the context of an InetAddressType 795 value. This value will be filled in after INIT or INIT ACK 796 messages have been received (when the primary path is selected 797 by SCTP)." 799 ::= { sctpAssocEntry 6 } 801 sctpAssocState OBJECT-TYPE 802 SYNTAX INTEGER { 803 closed(1), 804 cookieWait(2), 805 cookieEchoed(3), 806 established(4), 807 shutdownPending(5), 808 shutdownSent(6), 809 shutdownReceived(7), 810 shutdownAckSent(8), 811 deleteTCB(9) 812 } 813 MAX-ACCESS read-create 814 STATUS current 815 DESCRIPTION 816 "The state of this SCTP association. 817 As in TCP, the only value which may be set by a management 818 station is deleteTCB. Accordingly, it is appropriate for 819 an agent to return a 'badValue' response if a management 820 station attempts to set this object to any other value. 821 If a management station sets this object to the value 822 deleteTCB(9), then this has the effect of deleting the TCB 823 (as defined in SCTP) of the corresponding association on 824 the managed node, resulting in immediate termination of the 825 association. 826 As an implementation-specific option, an ABORT chunk may be 827 sent from the managed node to the other SCTP endpoint." 829 ::= { sctpAssocEntry 7 } 831 sctpAssocInStreams OBJECT-TYPE 832 SYNTAX Unsigned32 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "Inbound Streams according to the negotiation at association 837 start up. This parameter has to be read-only by the manager." 839 ::= { sctpAssocEntry 8 } 841 sctpAssocOutStreams OBJECT-TYPE 842 SYNTAX Unsigned32 843 MAX-ACCESS read-only 844 STATUS current 845 DESCRIPTION 846 "Outbound Streams according to the negotiation at association 847 start up. This parameter has to be read-only by the manager." 849 ::= { sctpAssocEntry 9 } 851 sctpAssocMaxRetr OBJECT-TYPE 852 SYNTAX Unsigned32 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "The maximum number of data retransmissions. This value is 857 specific for each association and the upper layer can be able 858 to change it calling the appropiate primitives. This value has 859 to be smaller than the addition of all the maximum number for 860 all the paths (sctpAssocRemAddressMaxPathRetrans). 861 Recommended value: 10 attempts." 863 ::= { sctpAssocEntry 10 } 865 -- Association Statistics 867 sctpAssocT1expired OBJECT-TYPE 868 SYNTAX Counter32 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "Number of times that T1 timer expired (timer for sending 873 either INIT or COOKIE-ECHO chunks and receiving an 874 acknowledgment)." 876 ::= { sctpAssocEntry 11 } 878 sctpAssocT2expired OBJECT-TYPE 879 SYNTAX Counter32 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "Number of times that T2-shutdown timer expired (shutdown 884 timer)." 886 ::= { sctpAssocEntry 12 } 888 sctpAssocRtxChunks OBJECT-TYPE 889 SYNTAX Counter32 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "Number of data chunks retransmitted to the peer in the 894 current association." 896 ::= { sctpAssocEntry 13 } 898 sctpAssocChecksumErrorCounter OBJECT-TYPE 899 SYNTAX Counter64 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "Number of SCTP packets received from the peers with an 904 invalid checksum." 906 ::= { sctpAssocEntry 14 } 908 sctpAssocRowStatus OBJECT-TYPE 909 SYNTAX RowStatus 910 MAX-ACCESS read-create 911 STATUS current 912 DESCRIPTION 913 "An object that allows entries in this table to be created and 914 deleted using the RowStatus convention. 916 A row in this table will be created after creating the TCB 917 in both sides of the association. The creation of this row 918 implies the creation of at least another row (depending on 919 the number of local and remote addresses) in the tables 920 sctpAssocLocalAddressTable and sctpAssocRemAddressTable. 922 A row is deleted in sctpAssocTable when an association turns 923 down (i.e., when the TCB is deleted according to [sctp] in 924 both sides of the association). The deletion of a row in 925 sctpAssocTable implies the deletion of the tables related 926 to this association (sctpAssocLocalAddressTable and 927 sctpAssocRemAddressTable). 928 Also, a row is deleted in sctpAssocTable when a set operation 929 is received from the manager with destroy option." 931 ::= { sctpAssocEntry 15 } 933 -- Expanded tables: Including Multi-home feature 934 -- Local Address TABLE 935 -- ******************* 937 sctpAssocLocalAddressTable OBJECT-TYPE 938 SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry 939 MAX-ACCESS not-accessible 940 STATUS current 941 DESCRIPTION 942 "Expanded table of sctpAssocTable based on the AssocId index. 943 It shows several interesting data for each local address which 944 takes part in this association." 946 ::= { sctpTables 2 } 948 sctpAssocLocalAddressEntry OBJECT-TYPE 949 SYNTAX SctpAssocLocalAddressEntry 950 MAX-ACCESS not-accessible 951 STATUS current 952 DESCRIPTION 953 "Local information about the available addresses." 954 INDEX { sctpAssocId, -- shared index 955 sctpAssocLocalAddressIPType, 956 sctpAssocLocalAddressIP } 958 ::= { sctpAssocLocalAddressTable 1 } 960 SctpAssocLocalAddressEntry ::= SEQUENCE { 961 sctpAssocLocalAddressIPType InetAddressType, 962 sctpAssocLocalAddressIP InetAddress, 963 sctpAssocLocalAddressRowStatus RowStatus 964 } 966 sctpAssocLocalAddressIPType OBJECT-TYPE 967 SYNTAX InetAddressType 968 MAX-ACCESS not-accessible 969 STATUS current 970 DESCRIPTION 971 "Internet type of local IP address used for this association. 972 - unknown (0) An unknown address type. This value MUST be 973 used if the value of the corresponding InetAddress object 974 is a zero-length string. It may also be used to indicate an 975 IP address different from IPv4 or IPv6. This value is used 976 in this MIB for error conditions. 978 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 979 textual convention [RFC2851]. 981 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 982 textual convention [RFC2851]." 984 ::= { sctpAssocLocalAddressEntry 1 } 986 sctpAssocLocalAddressIP OBJECT-TYPE 987 SYNTAX InetAddress 988 MAX-ACCESS not-accessible 989 STATUS current 990 DESCRIPTION 991 "The value of a local IP address available for this 992 association. An InetAddress value is always interpreted within 993 the context of an InetAddressType value. If SCTP are using DNS 994 names, the mapping to IP address-es will be done at reception 995 of INIT or INIT_ACK messages." 997 ::= { sctpAssocLocalAddressEntry 2 } 999 sctpAssocLocalAddressRowStatus OBJECT-TYPE 1000 SYNTAX RowStatus 1001 MAX-ACCESS read-create 1002 STATUS current 1003 DESCRIPTION 1004 "An object that allows entries in this table to be created and 1005 deleted using the RowStatus convention. 1006 A row in this table will be created per local IP address 1007 defined for this association. The creation takes part when a 1008 new row in the sctpAssocTable is created or when a new IP 1009 address is added in the local interface (if this function is 1010 enabled by the SCTP layer). 1011 A row in this table will be deleted per local IP address 1012 reserved for the association when the corresponding row in 1013 sctpAssocTable is deleted or when an IP address is removed 1014 from the local interface (if this function is enabled by the 1015 SCTP layer)." 1017 ::= { sctpAssocLocalAddressEntry 3 } 1019 -- Remote Addresses TABLE 1020 -- ********************** 1022 sctpAssocRemAddressTable OBJECT-TYPE 1023 SYNTAX SEQUENCE OF SctpAssocRemAddressEntry 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "Expanded table of sctpAssocTable based on the AssocId index. 1028 It shows several interesting data for each remote peer IP 1029 address which is used in this association." 1031 ::= { sctpTables 3 } 1033 sctpAssocRemAddressEntry OBJECT-TYPE 1034 SYNTAX SctpAssocRemAddressEntry 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "Information about THE most important variables for every 1039 remote IP address " 1040 INDEX { sctpAssocId, -- shared index 1041 sctpAssocRemAddressIPType, 1042 sctpAssocRemAddressIP } 1044 ::= { sctpAssocRemAddressTable 1 } 1046 SctpAssocRemAddressEntry ::= SEQUENCE { 1047 sctpAssocRemAddressIPType InetAddressType, 1048 sctpAssocRemAddressIP InetAddress, 1049 sctpAssocRemAddressStatus INTEGER, 1050 sctpAssocRemAddressRTO Unsigned32, 1051 sctpAssocRemAddressHeartBeatFlag INTEGER, 1052 sctpAssocRemAddressHeartBeatTimer Unsigned32, 1053 sctpAssocRemAddressMaxPathRetrans Unsigned32, 1054 sctpAssocRemAddressRetransCount Counter64, -- Statistic 1055 sctpAssocRemAddressRowStatus RowStatus 1056 } 1058 sctpAssocRemAddressIPType OBJECT-TYPE 1059 SYNTAX InetAddressType 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "Internet type of a remote IP address available for this 1064 association. 1065 - unknown (0) An unknown address type. This value MUST be 1066 used if the value of the corresponding InetAddress object 1067 is a zero-length string. It may also be used to indicate an 1068 IP address different from IPv4 or IPv6. This value is used 1069 in this MIB for error conditions. 1071 - ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 1072 textual convention [RFC2851]. 1074 - ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 1075 textual convention [RFC2851]." 1077 ::= { sctpAssocRemAddressEntry 1 } 1079 sctpAssocRemAddressIP OBJECT-TYPE 1080 SYNTAX InetAddress 1081 MAX-ACCESS not-accessible 1082 STATUS current 1083 DESCRIPTION 1084 "The value of a remote IP address available for this 1085 association. An InetAddress value is always interpreted within 1086 the context of an InetAddressType value." 1088 ::= { sctpAssocRemAddressEntry 2 } 1090 sctpAssocRemAddressStatus OBJECT-TYPE 1091 SYNTAX INTEGER { 1092 active(0), 1093 inactive(1) 1094 } 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "The current status of the remote transport address, according 1099 to [SCTP]. 1100 Active means that the threshold of no answer received from 1101 this IP address has not been reached. Inactive means that 1102 either no heartbeat was received from this address, or any 1103 other message, reaching the threshold defined by the 1104 protocol." 1106 ::= { sctpAssocRemAddressEntry 3 } 1108 sctpAssocRemAddressRTO OBJECT-TYPE -- T3-rtx- Timer 1109 SYNTAX Unsigned32 1110 UNITS "milliseconds" 1111 MAX-ACCESS read-only 1112 STATUS current 1113 DESCRIPTION 1114 "The current Retransmision Time-Out. T3-rtx timer as defined 1115 in the protocol SCTP." 1117 ::= { sctpAssocRemAddressEntry 4 } 1119 sctpAssocRemAddressHeartBeatFlag OBJECT-TYPE 1120 SYNTAX INTEGER { 1121 active(0), 1122 inactive(1) 1123 } 1124 MAX-ACCESS read-create 1125 STATUS current 1126 DESCRIPTION 1127 "The optional Heartbeat associated to one destination 1128 transport address could be active or not (value equal to 1 or 1129 0, respectively). 1131 An active destination transport address is the one considered 1132 available by a peer endpoint for receiving SCTP packets, as it 1133 is described in [sctp]." 1135 ::= { sctpAssocRemAddressEntry 5 } 1137 sctpAssocRemAddressHeartBeatTimer OBJECT-TYPE 1138 SYNTAX Unsigned32 1139 UNITS "milliseconds" 1140 MAX-ACCESS read-create 1141 STATUS current 1142 DESCRIPTION 1143 "The current heartbeat time-out. The recommended default value 1144 is 30000 milliseconds." 1146 ::= { sctpAssocRemAddressEntry 6 } 1148 sctpAssocRemAddressMaxPathRetrans OBJECT-TYPE 1149 SYNTAX Unsigned32 1150 MAX-ACCESS read-create 1151 STATUS current 1152 DESCRIPTION 1153 "Maximum number of DATA retransmissions allowed to a remote IP 1154 address before it is considered inactive, as defined in 1155 [sctp]. Recommended value 5 attempts." 1157 ::= { sctpAssocRemAddressEntry 7 } 1159 -- Remote Address Statistic 1161 sctpAssocRemAddressRetransCount OBJECT-TYPE 1162 SYNTAX Counter64 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "Number of DATA retransmissions as defined in [sctp]." 1168 ::= { sctpAssocRemAddressEntry 8 } 1170 sctpAssocRemAddressRowStatus OBJECT-TYPE 1171 SYNTAX RowStatus 1172 MAX-ACCESS read-create 1173 STATUS current 1174 DESCRIPTION 1175 "An object that allows entries in this table to be created and 1176 deleted using the RowStatus convention. 1178 A row in this table will be created per remote IP address 1179 defined for this association. The creation takes part when a 1180 new row in the sctpAssocTable is created or when a new IP 1181 address is added in the remote interface (if this function is 1182 enabled by the SCTP layer). 1184 A row in this table will be deleted per remote IP address 1185 reserved for the association when the corresponding row in 1186 sctpAssocTable is deleted or when an IP address is removed 1187 from the local interface (if this function is enabled by the 1188 SCTP layer)." 1190 ::= { sctpAssocRemAddressEntry 9 } 1192 -- 4.1 Conformance Information 1194 sctpGroups OBJECT IDENTIFIER ::= { sctpConformance 1 } 1195 sctpCompliances OBJECT IDENTIFIER ::= { sctpConformance 2 } 1197 -- 4.1.1 Compliance Statements 1199 sctpCompliance MODULE-COMPLIANCE 1200 STATUS current 1201 DESCRIPTION 1202 "The compliance statement for SNMPv3 entities which implement 1203 SCTP." 1205 MODULE -- this module 1207 MANDATORY-GROUPS { sctpGeneralVariablesGroup, 1208 sctpAssocTablesVariablesGroup 1209 } 1211 GROUP sctpStateStatGroup 1212 DESCRIPTION 1213 "The sctp group of objects to control state changes in 1214 the SCTP protocol." 1216 GROUP sctpOtherStatGroup 1217 DESCRIPTION 1218 "The sctp group of objects providing for management of 1219 SCTP general statistics." 1221 GROUP sctpAssocStatGroup 1222 DESCRIPTION 1223 "The sctp group of objects to manage SCTP statistics 1224 related to the remote endpoint." 1226 OBJECT sctpAssocRemPrimaryAddressType 1227 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1228 DESCRIPTION 1229 "It is only required to have IPv4 and IPv6 addresses to 1230 be stored since the use of the host names is limited to 1231 first stage, when the association is being established." 1233 OBJECT sctpAssocRemPrimaryAddress 1234 SYNTAX InetAddress (SIZE(4|16)) 1235 DESCRIPTION 1236 "It is only required to support IPv4 and unique IPv6 1237 addresses." 1239 OBJECT sctpAssocLocalAddressIPType 1240 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1241 DESCRIPTION 1242 "It is only required to have IPv4 and IPv6 addresses to 1243 be stored since the use of the host names is limited to 1244 first stage, when the association is being established." 1246 OBJECT sctpAssocLocalAddressIP 1247 SYNTAX InetAddress (SIZE(4|16)) 1248 DESCRIPTION 1249 "It is only required to support IPv4 and unique IPv6 1250 addresses." 1252 OBJECT sctpAssocRemAddressIPType 1253 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1254 DESCRIPTION 1255 "It is only required to have IPv4 and IPv6 addresses to 1256 be stored since the use of the host names is limited to 1257 first stage, when the association is being established." 1259 OBJECT sctpAssocRemAddressIP 1260 SYNTAX InetAddress (SIZE(4|16)) 1261 DESCRIPTION 1262 "It is only required to support IPv4 and unique IPv6 1263 addresses." 1265 ::= { sctpCompliances 1 } 1267 -- 4.1.2 Units of conformance 1269 sctpGeneralVariablesGroup OBJECT-GROUP 1270 OBJECTS { sctpRtoAlgorithm, sctpRtoMin, sctpRtoMax, 1271 sctpRtoInitial, sctpValCookieLife, sctpMaxInitRetr, 1272 sctpInitialT1, sctpInitialT2 1273 } 1274 STATUS current 1275 DESCRIPTION 1276 "The sctp group of objects providing for management of SCTP 1277 entities. Common parameters for the protocol." 1279 ::= { sctpGroups 1 } 1281 sctpStateStatGroup OBJECT-GROUP 1282 OBJECTS {sctpCurrEstab, sctpActiveEstab, sctpPassiveEstab, 1283 sctpAborted, sctpShutdowns 1284 } 1285 STATUS current 1286 DESCRIPTION 1287 "The sctp group of objects to control state changes in the 1288 SCTP protocol." 1290 ::= { sctpGroups 2 } 1292 sctpOtherStatGroup OBJECT-GROUP 1293 OBJECTS {sctpStatOutOfBlue, sctpStatSentChunks, 1294 sctpStatRecChunks, sctpStatOutOfOrderSentChunks, 1295 sctpStatOutOfOrderRecChunks, 1296 sctpStatFragmentedUsrMessages, 1297 sctpStatReassembledUsrMessages 1298 } 1299 STATUS current 1300 DESCRIPTION 1301 "The sctp group of objects providing for management of SCTP 1302 general statistics." 1304 ::= { sctpGroups 3 } 1306 sctpAssocTablesVariablesGroup OBJECT-GROUP 1307 OBJECTS {sctpAssocId, sctpAssocRemHostName, 1308 sctpAssocLocalSCTPPort, sctpAssocRemSCTPPort, 1309 sctpAssocRemPrimaryAddressType, 1310 sctpAssocRemPrimaryAddress, sctpAssocState, 1311 sctpAssocInStreams, sctpAssocOutStreams, 1312 sctpAssocMaxRetr, sctpAssocT1expired, 1313 sctpAssocT2expired, sctpAssocRtxChunks, 1314 sctpAssocChecksumErrorCounter, sctpAssocRowStatus, 1315 sctpAssocLocalAddressIPType,sctpAssocLocalAddressIP, 1316 sctpAssocLocalAddressRowStatus, 1317 sctpAssocRemAddressIPType, sctpAssocRemAddressIP, 1318 sctpAssocRemAddressStatus, sctpAssocRemAddressRTO, 1319 sctpAssocRemAddressHeartBeatFlag, 1320 sctpAssocRemAddressHeartBeatTimer, 1321 sctpAssocRemAddressMaxPathRetrans, 1322 sctpAssocRemAddressRowStatus 1323 } 1324 STATUS current 1325 DESCRIPTION 1326 "The sctp group of objects to manage specific local and remote 1327 SCTP variables (local and remote tables)." 1329 ::= { sctpGroups 4 } 1331 sctpAssocStatGroup OBJECT-GROUP 1332 OBJECTS {sctpAssocRemAddressRetransCount 1333 } 1334 STATUS current 1335 DESCRIPTION 1336 "The sctp group of objects to manage SCTP statistics related 1337 to the remote endpoint." 1339 ::= { sctpGroups 5 } 1341 END 1343 5. References 1345 [sctp] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J. 1346 Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. 1347 Paxson, "Stream Control Transmission Protocol", RFC 2960, 1348 October 2000. 1350 [SIGAS] "Telephony Signaling Transport over SCTP Applicability 1351 Statement". Work in progress. 1353 [MIBMPLS] Cucchiara et al. "Definnitions of Managed Objects for the 1354 Multiprotocol Label Switching, Label Distribution Protocol 1355 (LDP)", Internet Draf , January 1356 2000. 1358 [SecSNMP] Stallings, W., "SNMP3: A Security Enhancement for SNMP", 1359 IEEE Communication Surveys, Forth quarter 1998, Vol. 1 No. 1. 1361 [Cong] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1362 1988, Stanford, California. 1364 [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the 1365 Transmission Control Protocol using SMIv2", RFC 2012, November 1366 1996. 1368 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1369 Architecture for Describing SNMP Management Frameworks", RFC 1370 2571, April 1999. 1372 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1373 of Management Information for TCP/IP-based Internets", STD 16, 1374 RFC 1155, May 1990. 1376 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1377 16, RFC 1212, March 1991. 1379 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1380 SNMP", RFC 1215, March 1991. 1382 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1383 Rose, M., and S. Waldbusser, "Structure of Management 1384 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1386 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1387 Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", 1388 STD 58, RFC 2579, April 1999. 1390 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1391 Rose, M., and S. Waldbusser, "Conformance Statements for 1392 SMIv2", STD 58, RFC 2580, April 1999. 1394 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1395 Network Management Protocol", STD 15, RFC 1157, May 1990. 1397 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1398 "Introduction to Community-based SNMPv2", RFC 1901, January 1399 1996. 1401 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1402 "Transport Mappings for Version 2 of the Simple Network 1403 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1405 [RFC2452] M. Daniele, "IP Version 6 Management Information Base for 1406 the Transmission Control Protocol", RFC 2452, December 1998 1408 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1409 "Message Processing and Dispatching for the Simple Network 1410 Management Protocol (SNMP)", RFC 2572, April 1999. 1412 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1413 (USM) for version 3 of the Simple Network Management Protocol 1414 (SNMPv3)", RFC 2574, April 1999. 1416 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1417 "Protocol Operations for Version 2 of the Simple Network 1418 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1420 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1421 RFC 2573, April 1999. 1423 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1424 Access Control Model (VACM) for the Simple Network Management 1425 Protocol (SNMP)", RFC 2575, April 1999. 1427 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1428 "Introduction to Version 3 of the Internet-standard Network 1429 Management Framework", RFC 2570, April 1999. 1431 [RFC2851] Textual Conventions for Internet Network Addresses ,RFC 1432 2851, June 2000. 1434 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1435 Requirement Levels", BCP 14, RFC 2119, Harvard University, 1436 March 1997 1438 6. Security Consideration 1440 There are a number of management objects defined in this MIB that 1441 have a MAX-ACCESS clause of read-write and/or read-create. Such 1442 objects may be considered sensitive or vulnerable in some network 1443 environments. The support for SET operations in a non-secure 1444 environment without proper protection can have a negative effect on 1445 network operations. 1447 It is thus important to control even GET access to these objects and 1448 possibly to even encrypt the values of these object when sending them 1449 over the network via SNMP. Not all versions of SNMP provide features 1450 for such a secure environment. 1452 SNMPv1 by itself is not a secure environment. Even if security 1453 measures are taken (e.g., using IPSEC), there is no per-user control 1454 as to who (once an IPSEC association is established between hosts) is 1455 allowed to GET or SET the objects in this MIB 1457 It is recommended that the implementers consider the security 1458 features as provided by the SNMPv3 framework. Specifically, the use 1459 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1460 based Access Control Model RFC 2575 [RFC2575] is recommended. 1462 It is then a customer/user responsibility to ensure that the SNMP 1463 entity giving access to an instance of this MIB, is properly 1464 configured to give access to the objects only to those principals 1465 (users) that have legitimate rights to indeed GET or SET 1466 (change/create/delete) them. 1468 7. Acknowledgments 1470 The authors wish to thank David Partain, Ed Yarwood and Shyamal 1471 Prasad for their invaluable comments. 1473 8. Authors' Addresses 1475 Javier Pastor Tel: +34-91-339-3819 1476 Ericsson Espana S.A. eMail: J.Javier.Pastor@ericsson.com 1477 Network Communication Services 1478 Retama 7, 5th floor 1479 Madrid, 28045 1480 Spain 1482 Maria-Carmen Belinchon Tel: +34-91-339-3535 1483 Ericsson Espana S.A. eMail: Maria.C.Belinchon@ericsson.com 1484 Network Communication Services 1485 Retama 7, 5th floor 1486 Madrid, 28045 1487 Spain 1489 9. Revision History 1491 9.1 Changes from 1493 o Open issues updated 1495 o Section 2: Reference to RFC227x changed to RFC257x 1497 o Section 4: Inside the sctpRtoAlgorithm definition has been put 1498 "other" first 1499 rather than last. That way, it won't end up in the middle of things 1500 when new 1501 enumerations are added later. 1503 9.2 Changes from 1505 o Change of "Simple" word to "Stream" word in SCTP acronyms 1507 o Version of the MIB based on SCTPv10 1508 o Section 2: Update SNMP Framework to include the standard 1509 explanation 1511 o New Structure for the MIB: 1512 sctpMIB 1513 \- sctpObjects 1514 \- sctpScalars 1515 \- sctpTables 1516 \- sctpConformance 1518 o Section 4.1.2: Unit of Conformance updated (functional structure). 1520 o MAX-ACCESS clauses reviewed 1522 o The general statistics has been re-ordered, placed before the 1523 tables. 1525 o In SMIv2, indexes should be not-accessible (= the object type is a 1526 column in a table used as index and may not be used as an operand in 1527 any 1528 operation != SMIv1) (pp109-110 in []) 1530 o IPv6 compatible: 1531 - Change of Primary/Local/Remote addresses 1532 - PENDING: check "MODULE-COMPLIANCE" 1534 o Row Status included in AssocTable, AssocLocal and AssocRem to 1535 create, 1536 modify and delete rows in the tables. 1538 o SCTP general statistics changed from Counter32 to Counter64 since 1539 it supports 1540 more data changes. 1542 o sctpCurrEstab ("State-related variables and statistics" section) 1543 variable 1544 changed from Gauge32 to Counter32. 1546 o sctpAssocRemAddressT1expired and sctpAssocRemAddressT2expired have 1547 been 1548 removed from the remote table and added in the general association 1549 data 1550 since they are variables per association (not per IP address). 1552 o sctpAssocDropDatag statistic has been removed from the general 1553 association 1554 statistics since it had an ambiguous meaning. 1556 o Explained the meaning of the unordered chunks (chunks in which the 1557 U bit is 1558 set to 1) in sctpStatOutOfOrderSentChunks and 1559 sctpStatOutOfOrderRecChunks. 1561 o Added sctpChecksumErrorCounter to collect information about wrong 1562 checksums 1563 received from the peer. 1565 o Specify that sctpStatSentChunks and sctpStatRecChunks does not 1566 contain 1567 retransmission chunks. 1569 o Reword the Security Considerations chapter pointing out that IPsec 1570 does 1571 not secure the network but it provides end-to-end security over a 1572 network. 1574 o sctpAssocRemAddressRtxChunks replaced as a variable per 1575 association, 1576 meaning the number of chunks retransmited to the peer in the current 1577 association. 1579 o sctpHeartBeatMisses and sctpMaxRetr have been replaced from the 1580 general 1581 SCTP statistics to the remote IP address table (sctpHeartBeatMisses) 1582 and 1583 in the association table (sctpMaxRetr). 1585 o Specify that the retransmissions in the general SCTP statistics 1586 include 1587 control plus data chunks. 1589 o Included heartbeat timer for remote IP address. 1591 o Removed sctpAssocRemAddressHeartBeatMisses variable from the remote 1592 IP 1593 address table. 1595 o Removed sctpAssocRemAddressT3expired variable from the remote IP 1596 address table. 1598 o Updated variables to the new SCTP states defined in v10. 1600 9.3 Changes from 1602 o sctpRtoMin - stray "." outside the double-quotes in the DESCRIPTION 1603 clause. 1605 o sctpRtoMax - stray "." outside the double-quotes in the DESCRIPTION 1606 clause. 1608 o sctpAssocRemHostName - the type OCTECT STRING should be OCTET 1609 STRING. 1611 o sctpAssocRemPrimaryAddress - the DESCRIPTION clause is missing its 1612 closing 1613 double-quote. 1615 o sctpConformance - this is defined as { sctpMIB 2 }, then never 1616 used; instead 1617 sctpMIBConformance (which is undefined) is used in the definition of 1618 sctpMIBGroups 1619 and sctpMIBCompliances. 1621 o Reworded the MIB organization 1623 o Removed maximum number of concurrent associations 1625 o In sctpMIBCompliance, removed a missing comma in MANDATORY-GROUPS. 1627 o In sctpAssocTablesVariablesGroup and sctpAssocStatGroup, removed 1628 extra commas at end of OBJECTS list. 1630 o sctpAssocInStreams. ACCESS changed from read-create to read-only. 1632 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1633 changed from per remote IP address to per association. 1635 o Comment on sctpAssocRemAddressHBTimer specifies now that the 1636 manager can change it. 1638 o ACCESS on sctpAssocRemAddressHBTimer changed from read-only to 1639 read-write. 1641 o ACCESS on sctpAssocRemAddressRetransCount changed from read-write 1642 to read-only. 1644 o Move sctpStatChecksumErrorCounter from general statistics to per 1645 association. 1647 9.2 Changes from 1649 o sctpMaxInStreams � It�s a sctp-user feature. 1651 o sctpStatRetransChunks � It�s more useful to have this statistic in 1652 a association basis 1654 o sctpAssocRemAddressHeartBeatFlag and sctpAssocRemAddressHBTimer 1655 have been created again instead of per association in order to follow 1656 the draft. If some implementations want to have the same value for 1657 all the associations they have, they should set all the variables in 1658 the different remote addresses to the same value.