idnits 2.17.1 draft-ietf-rohc-mib-rtp-09.txt: 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 Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1131 has weird spacing: '...returns the r...' == Line 1133 has weird spacing: '... of the assoc...' == Line 2525 has weird spacing: '...for the purpo...' -- 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 (January 2004) is 7397 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: 'RFC2119' is mentioned on line 87, but not defined == Unused Reference: 'RFC3411' is defined on line 2447, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 2451, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3242 (Obsoleted by RFC 4362) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCXXXX' Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft J. Quittek 2 Document: draft-ietf-rohc-mib-rtp-09.txt M. Stiemerling 3 Expires: July 2004 NEC 4 H. Hartenstein 5 University of Karlsruhe 6 January 2004 8 Definitions of Managed Objects for Robust Header Compression 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC 2026. Internet-Drafts are 15 working documents of the Internet Engineering Task Force (IETF), its 16 areas, and its working groups. Note that other groups may also 17 distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html 30 Distribution of this document is unlimited. 32 Copyright Notice 34 Copyright (C) The Internet Society (2004). All Rights Reserved. 36 Abstract 38 This memo defines a portion of the Management Information Base (MIB) 39 for use with network management protocols in the Internet community. 40 In particular, it describes a set of managed objects that allow 41 monitoring of running instances of RObust Header Compression (ROHC). 42 The managed objects defined in this memo are grouped into three MIB 43 modules. The ROHC-MIB module defines managed objects shared by all 44 ROHC profiles, the ROHC-UNCOMPRESSED-MIB module defines managed 45 objects specific to the ROHC uncompressed profile, the ROHC-RTP-MIB 46 module defines managed objects specific to the ROHC RTP (Real-Time 47 Transport Protocol) profile, the ROHC UDP (User Datagram Protocol) 48 profile, the ROHC ESP (Encapsulating Security Payload) profile, and 49 the ROHC LLA (Link Layer Assisted) profile. 51 Table of Contents 53 1. Introduction ................................................ 2 54 2. The Internet-Standard Management Framework .................. 2 55 3. Overview .................................................... 3 56 4. Structure of the MIB modules ................................ 3 57 4.1. The ROHC-MIB module ..................................... 4 58 4.1.1. rohcChannelTable .................................... 5 59 4.1.2. rohcInstanceTable ................................... 5 60 4.1.3. rohcProfileTable .................................... 6 61 4.1.4. rohcContextTable .................................... 7 62 4.2. The ROHC-UNCOMPRESSED-MIB module ........................ 8 63 4.2.1. rohcUncmprContextTable .............................. 8 64 4.3. The ROHC-RTP-MIB module ................................. 8 65 4.3.1. rohcRtpContextTable ................................. 8 66 4.3.2. rohcPacketSizeTable ................................. 8 67 5. Definitions ................................................. 9 68 6. Security Considerations ..................................... 49 69 7. Acknowledgements ............................................ 50 70 8. Normative References ........................................ 50 71 9. Informative References ...................................... 51 72 10. Authors' Addresses ......................................... 51 73 11. IPR Notices ................................................ 52 74 12. Full Copyright Statement ................................... 52 76 1. Introduction 78 This memo defines a portion of the Management Information Base (MIB) 79 for use with network management protocols in the Internet community. 80 In particular, it describes a set of managed objects that allow 81 monitoring of running instances of robust header compression. 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 85 "OPTIONAL" in this document are to be interpreted as described in RFC 86 2119 [RFC2119]. 88 2. The Internet-Standard Management Framework 90 For a detailed overview of the documents that describe the current 91 Internet-Standard Management Framework, please refer to section 7 of 92 RFC 3410 [RFC3410]. 94 Managed objects are accessed via a virtual information store, termed 95 the Management Information Base or MIB. MIB objects are generally 96 accessed through the Simple Network Management Protocol (SNMP). 97 Objects in the MIB are defined using the mechanisms defined in the 98 Structure of Management Information (SMI). This memo specifies a MIB 99 module that is compliant to the SMIv2, which is described in STD 58, 100 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 101 [RFC2580]. 103 3. Overview 105 This section describes the basic model of RObust Header Compression 106 (ROHC, [RFC3095]) used when developing the MIB modules for ROHC 107 described in the following sections. 109 ROHC presents a framework for IP header compression that allows 110 flexible adjustment of compression efficiency versus robustness 111 against channel errors depending on the underlying channel 112 characteristics. 114 ROHC introduces header compressors/decompressors at the end-points 115 (interfaces) of (wireless) channels on which packets with compressed 116 headers are transferred. ROHC exploits the temporal redundancy in 117 successive packet headers of a packet flow by storing non-changing 118 fields of the headers as well as reference values of predictably 119 changing fields as context information. When the context information 120 for a packet flow is also established at the decompressor, only 121 delta-information and unpredictably changing header fields have to be 122 sent over the channel. 124 This document specifies MIB modules in order to provide a means for 125 managing ROHC implementations via SNMP and within the IETF management 126 framework. The objects defined support configuration management, 127 fault management and performance monitoring. 129 For configuration management implementation parameters (see Section 130 6.3. of [RFC3095]) and configuration parameters (including the ones 131 specified in Section 5.1.1 of [RFC3095] and in Section 5.1.1 of 132 [RFC3242]) can be verified by using the MIB modules specified below. 134 For fault management compressor/decompressor state and mode can be 135 checked. 137 For performance management a set of statistics is provided including 138 the number of flows that have used ROHC, the current and long term 139 compression ratio, the number of reinitializations and the number of 140 packets sent or received with different header types. 142 4. Structure of the MIB modules 144 This section presents the structure of the MIB modules that are 145 specified in Section 5. Basically, the MIB is structured according 146 to the ROHC architecture described in [RFCXXXX]. 148 ROHC is an evolving technology. [RFC3095] specifies the header 149 compression framework and four profiles: uncompressed, RTP, UDP, and 150 ESP (Real-Time Transport Protocol, User Datagram Protocol, 151 Encapsulating Security Payload). [RFC3242] specifies a profile with 152 additional link layer assistance called LLA (Link Layer Assisted). A 153 profile for compression of TCP (Transmission Control Protocol) flows 154 is under development within the ROHC working group and SCTP (Stream 155 Control Transmission Protocol) compression is being discussed as 156 potential next candidate. Therefore, the managed objects defined 157 below are structured into three MIB modules: the general ROHC-MIB 158 module and the profile-specific ROHC-UNCOMPRESSED-MIB and ROHC-RTP- 159 MIB modules. This flexible approach allows to support future 160 profiles each by its own profile-specific module. 162 The ROHC-MIB module defines properties of information on ROHC 163 instances, ROHC channels, ROHC profiles, and ROHC compressor and 164 decompressor contexts. All managed objects in this module are 165 assumed to be shared by all profiles. 167 The ROHC-UNCOMPRESSED-MIB module extends the ROHC-MIB by managed 168 objects that are specific to the ROHC uncompressed profile 0x0000 169 defined in [RFC3095]. The ROHC-RTP-MIB module extends the ROHC-MIB 170 by managed objects that are specific to the three profiles defined in 171 [RFC3095] (ROHC RTP profile 0x0001, ROHC UDP profile 0x0002, and ROHC 172 ESP profile 0x0003), and to the ROHC LLA profile 0x0005 defined in 173 [RFC3242]. An analysis of these profiles showed that they are 174 tightly related and can share most of the managed objects in the 175 ROHC-UNCOMPRESSED-MIB module. Therefore, a joint module for all of 176 them was preferred to individual modules. 178 The number of managed objects in the ROHC-UNCOMPRESSED-MIB Module and 179 the ROHC-RTP-MIB Module is rather small. They contain context state 180 and context mode, and profile-specific context statistics. It is 181 assumed that MIB modules for future profiles, such as TCP and SCTP, 182 will be similarly small and easy to design. 184 4.1. The ROHC-MIB module 186 The ROHC-MIB module defines managed objects that are expected to be 187 useful for all current and future ROHC profiles. Objects in the ROHC- 188 MIB module are arranged into four tables: the rohcChannelTable, the 189 rohcInstanceTable, the rohcProfileTable, and the rohcContextTable. 190 The managed objects in the first three tables are rather static 191 (except for provided statistics), while the objects in the 192 rohcContextTable are more dynamic. 194 All tables are indexed by the IP interface number and by a numeric 195 channel identifier. The channel identifier is used for channels to 196 which compressors and decompressors are attached (called ROHC 197 channels in [RFCXXXX]), as well as for dedicated feedback channels 198 (called ROHC feedback channels in [RFCXXXX]). Compressor and 199 decompressor instances are further indexed by their type (either 200 compressor or decompressor). Contexts are indexed by the same index 201 as their corresponding instance and their individual context 202 identifier (CID). 204 4.1.1. rohcChannelTable 206 The rohcChannelTable lists all channels used by ROHC instances for 207 transferring compressed packets and/or for giving feedback from the 208 decompressor to the compressor. Listed channels are either ROHC 209 channels or feedback channels as defined in [RFCXXXX]. The channels 210 are listed per IP interface. 212 The information per channel in the rohcChannelTable includes 214 o the channel ID, 216 o the channel type, either 'notIn&Use', 'rohc', or 217 'dedicatedFeedback', 219 o the channel for which feedback is provided by this channel (if 220 applicable), 222 o a string for describing the channel, and 224 o the status of the channel being either 'enabled' or 'disabled'. 226 4.1.2. rohcInstanceTable 228 The rohcInstanceTable defines properties of ROHC compressor instances 229 and ROHC decompressor instances. 231 As described in [RFCXXXX], an instance is associated with exactly one 232 channel and only one instance can be associated with the same 233 channel. Therefore, the same index consisting of ifIndex and 234 rohcChannelID could have been used for both tables. But when 235 accessing the rohcInstanceTable (and the rohcContextTable that shares 236 a part of its index with the rohcInstanceTable) there are many cases 237 where either a compressor contexts or a decompressor contexts are of 238 interest. Therefore, the rohcInstanceType indicating either a 239 compressor or a decompressor was added to the table's index. This 240 allows listing all compressors without accessing any decompressor. 241 Note that still the combination of ifIndex and rohcChannelID uniquely 242 identifies an instance. It is always possible to directly identify 243 and access the channel corresponding to a given instance. 245 The set of instance properties in the rochInstanceTable includes 247 o the vendor of the implementation, version number and 248 description, 250 o the channels used for compressed packets and for feedback, 252 o implementation and configuration properties including clock 253 resolution, maximum context identifier number (MAX_CID), the 254 LARGE_CIDS flag, and the Maximum Reconstructed Reception Unit 255 (MRRU), 257 o the storage time for contexts created by this instance, 259 o the status of the instance (operational or not). 261 Optionally, the rohcInstanceTable also contains instance statistics 262 including 264 o the total number of compressed flows, 266 o the current number of compressed flows, 268 o the total number of packets passing this instance 270 o the total number of static Initialization and Refreshs (IRs) 271 passing this instance 273 o the total number of dynamic Initialization and Refreshs (IR- 274 DYNs) passing this instance, and 276 o the total compression ratio achieved on the channel. 278 Instances are listed per IP interface. 280 4.1.3. rohcProfileTable 282 The rohcProfileTable lists available profiles per instance including 283 information on 285 o the profile number, 287 o the vendor and version number, and 289 o a string describing the profile. 291 o a flag indicating whether or not using this profile has been 292 negotiated with the corresponding (de)compressor. 294 4.1.4. rohcContextTable 296 The rohcContextTable lists compressor contexts or decompressor 297 contexts per instance and context identifier (CID). Each row of this 298 table represents a context. If a new context is created, also a new 299 row in this table is created. After expiration or termination of a 300 context, the row will continue to exist until the context's storage 301 time expires or until the CID is re-used. Then the row will be 302 deleted. 304 For each context, the following attributes are listed: 306 o the type of context ('compressor' or 'decompressor'), also used 307 as part of the table index, 309 o the CID, 311 o the state of the CID ('unused', 'active', 'expired', or 312 'terminated'), also used as part of the table index, 314 o the used profile, 316 o in case of a decompressor: the decompressor depth, and 318 o the storage time. 320 Optionally, context statistics is provided including 322 o activation and deactivation time of the context, 324 o the number of packets sent or received, respectively, 326 o the numbers of IRs and IR-DYNs sent or received, respectively, 328 o the number of feedbacks sent or received, respectively, 330 o in case of a decompressor context: the numbers of decompressor 331 failures and repairs, 333 o the total compression ratio of all packets passing this context, 335 o the total compression ratio of all packet headers compressed in 336 this context, 338 o the mean compressed packet size of all packets passing this 339 context, 341 o the mean header size of all compressed headers passing this 342 context, 344 o the compression ratio of the last 16 packets passing this 345 context, 347 o the compression ratio of the last 16 packet headers compressed 348 in this context, 350 o the mean compressed packet size of the last 16 packets passing 351 this context, 353 o the mean header size of the last 16 compressed headers passing 354 this context. 356 4.2. The ROHC-UNCOMPRESSED-MIB module 358 The ROHC-UNCOMPRESSED-MIB module defines managed objects that are 359 specific to ROHC uncompressed profile (0x0000) specified in 360 [RFC3095]. 362 4.2.1. rohcUncmprContextTable 364 The rohcUncmprContextTable extends the rohcContextTable. It provides 365 information on state and mode of the compressor for profile 0x0000. 366 Optionally, it also provides a counter of ACK feedbacks sent or 367 received by the context, respectively. 369 4.3. The ROHC-RTP-MIB module 371 The ROHC-RTP-MIB module defines managed objects that are specific to 372 three profiles specified in [RFC3095] (ROHC RTP profile 0x0001, ROHC 373 UDP profile 0x0002, and ROHC ESP profile 0x0003) and to the ROHC LLA 374 profile 0x0005 specified in [RFC3242]. The ROHC-RTP-MIB contains two 375 tables, the rohcRtpContextTable and the rohcRtpPacketSizeTable. 377 4.3.1. rohcRtpContextTable 379 The rohcRtpContextTable extends the rohcContextTable. It provides 380 information on context state and context mode for profiles 0x0001 - 381 0x0003 and 0x0005. For compressor contexts it optionally contains 382 managed object containing the numbers of allowed and used packet 383 sizes. As futher option, counters of the numbers of ACKs, NACKs, and 384 SNACKs in this context are specified. 386 4.3.2. rohcPacketSizeTable 388 The optional rohcPacketSizeTable lists per compressor context the 389 allowed packet sizes for profiles ROHC RTP, ROHC UDP, ROHC ESP, or 390 the preferred packet sizes for ROHC LLA, respectively. Allowed 391 packet sizes are marked if they are used. For preferred packet sizes, 392 it is indicated whether the preferred size applies to NHP only, to 393 RHP only or to all packets. 395 5. Definitions 397 ROHC-MIB DEFINITIONS ::= BEGIN 399 IMPORTS 400 MODULE-IDENTITY, OBJECT-TYPE, 401 Unsigned32, Counter32, mib-2 402 FROM SNMPv2-SMI -- RFC2578 404 TEXTUAL-CONVENTION, TruthValue, 405 TimeInterval, DateAndTime 406 FROM SNMPv2-TC -- RFC2579 408 MODULE-COMPLIANCE, OBJECT-GROUP 409 FROM SNMPv2-CONF -- RFC2580 411 SnmpAdminString 412 FROM SNMP-FRAMEWORK-MIB -- RFC3411 414 ifIndex 415 FROM IF-MIB; -- RFC2863 417 rohcMIB MODULE-IDENTITY 418 LAST-UPDATED "200401040101Z" -- January 04, 2004 419 ORGANIZATION "IETF Robust Header Compression Working Group" 420 CONTACT-INFO 421 "WG charter: 422 http://www.ietf.org/html.charters/rohc-charter.html 424 Mailing Lists: 425 General Discussion: rohc@ietf.org 426 To Subscribe: rohc-request@ietf.org 427 In Body: subscribe your_email_address 429 Editor: 430 Juergen Quittek 431 NEC Europe Ltd. 432 Network Laboratories 433 Kurfuersten-Anlage 36 434 69221 Heidelberg 435 Germany 436 Tel: +49 6221 90511-15 437 Email: quittek@ccrle.nec.de" 438 DESCRIPTION 439 "This MIB module defines a set of basic objects for 440 monitoring and configuring robust header compression. 441 The module covers information about running instances 442 of ROHC (compressors or decompressors) at IP interfaces. 444 Information about compressor contexts and decompressor 445 contexts has different structure for different profiles. 446 Therefore it is not provided by this MIB module, but by 447 individual modules for different profiles. 449 Copyright (C) The Internet Society (2004). This version 450 of this MIB module is part of RFC yyyy; see the RFC 451 itself for full legal notices." 452 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 454 REVISION "200401040101Z" -- January 04, 2004 455 DESCRIPTION "Initial version, published as RFC yyyy." 456 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 458 ::= { mib-2 XXX } 459 -- XXX to be assigned by IANA. 461 RohcChannelIdentifier ::= TEXTUAL-CONVENTION 462 DISPLAY-HINT "d" 463 STATUS current 464 DESCRIPTION 465 "A number identifying a channel. 466 The value of 0 must not be used as identifier 467 of an existing channel." 468 SYNTAX Unsigned32 (1..4294967295) 470 RohcChannelIdentifierOrZero ::= TEXTUAL-CONVENTION 471 DISPLAY-HINT "d" 472 STATUS current 473 DESCRIPTION 474 "A number identifying a channel. 475 The value of 0 is indicates that 476 no channel is identified." 477 SYNTAX Unsigned32 (0..4294967295) 479 RohcCompressionRatio ::= TEXTUAL-CONVENTION 480 DISPLAY-HINT "d" 481 STATUS current 482 DESCRIPTION 483 "A number indicating a compression ratio over 484 a set of bytes. The value is defined as 485 1000 * bytes(compressed) / bytes(original) 486 rounded to the next integer value. 488 Note that compressed sets of bytes can be larger 489 than the corresponding uncompressed ones. 490 Therefore, the number can be greater than 1000." 491 SYNTAX Unsigned32 493 -- 494 -- The groups defined within this MIB module: 496 -- 498 rohcObjects OBJECT IDENTIFIER ::= { rohcMIB 1 } 499 rohcConformance OBJECT IDENTIFIER ::= { rohcMIB 2 } 501 -- 502 -- The ROHC Instance group lists properties of ROHC 503 -- instances in the rohcInstanceTable, about the channels used 504 -- by the instances in the rohcChanneltable and about the profiles 505 -- available at the instances in the rohcProfileTable. 506 -- 508 rohcInstanceObjects OBJECT IDENTIFIER ::= { rohcObjects 1 } 510 -- 511 -- Channel Table 512 -- 513 -- Listing all channels used for ROHC data channel 514 -- and/or as feedback channel. 515 -- 517 rohcChannelTable OBJECT-TYPE 518 SYNTAX SEQUENCE OF RohcChannelEntry 519 MAX-ACCESS not-accessible 520 STATUS current 521 DESCRIPTION 522 "This table lists and describes all ROHC channels 523 per interface." 524 ::= { rohcInstanceObjects 1 } 526 rohcChannelEntry OBJECT-TYPE 527 SYNTAX RohcChannelEntry 528 MAX-ACCESS not-accessible 529 STATUS current 530 DESCRIPTION 531 "An entry describing a particular script. Every script that 532 is stored in non-volatile memory is required to appear in 533 this script table. 535 Note, that the rohcChannelID identifies the channel 536 uniquely. The ifIndex is part of the index of this table 537 just in order to allow addressing channels per interface." 538 INDEX { ifIndex, rohcChannelID } 539 ::= { rohcChannelTable 1 } 541 RohcChannelEntry ::= SEQUENCE { 542 rohcChannelID RohcChannelIdentifier, 543 rohcChannelType INTEGER, 544 rohcChannelFeedbackFor RohcChannelIdentifierOrZero, 545 rohcChannelDescr SnmpAdminString, 546 rohcChannelStatus INTEGER 547 } 549 rohcChannelID OBJECT-TYPE 550 SYNTAX RohcChannelIdentifier 551 MAX-ACCESS not-accessible 552 STATUS current 553 DESCRIPTION 554 "The locally arbitrary, but unique identifier associated 555 with this channel. The value is REQUIRED to be unique 556 per ROHC MIB implementation independent of the associated 557 interface. 559 The value is REQUIRED to remain constant at least from one 560 re-initialization of the entity's network management system 561 to the next re-initialization. It is RECOMMENDED that the 562 value persist across such re-initializations." 563 REFERENCE 564 "RFC 3095, Section 5.1.1" 565 ::= { rohcChannelEntry 2 } 567 rohcChannelType OBJECT-TYPE 568 SYNTAX INTEGER { 569 notInUse(1), 570 rohc(2), 571 dedicatedFeedback(3) 572 } 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "Type of usage of the channel. A channel might be currently 577 not in use for ROHC or feedback, it might be in use as 578 a ROHC channel carrying packets and optional piggy-backed 579 feedback, or it might be used as a dedicated feedback 580 channel exclusively carrying feedback." 581 ::= { rohcChannelEntry 3 } 583 rohcChannelFeedbackFor OBJECT-TYPE 584 SYNTAX RohcChannelIdentifierOrZero 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "The index of another channel of this interface for which 589 the channel serves as feedback channel. 591 If no feedback information is transferred on this channel, 592 then the value of this ID is 0. If the channel type is set 593 to notInUse(1), then the value of this object must be 0. 594 If the channel type is rohc(2) and the value of this object 595 is a valid channel ID, then feedback information is 596 piggy-backed on the ROHC channel. If the channel type is 597 dedicatedFeedback(3), then feedback is transferred on this 598 channel and the value of this object MUST be different from 599 0 and MUST identify an existing ROHC channel." 600 REFERENCE 601 "RFC 3095, Section 5.1.1" 602 ::= { rohcChannelEntry 4 } 604 rohcChannelDescr OBJECT-TYPE 605 SYNTAX SnmpAdminString 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "A textual description of the channel." 610 ::= { rohcChannelEntry 5 } 612 rohcChannelStatus OBJECT-TYPE 613 SYNTAX INTEGER { 614 enabled(1), 615 disabled(2) 616 } 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION 620 "Status of the channel." 621 ::= { rohcChannelEntry 6 } 623 -- 624 -- Instances of ROHC 625 -- 626 -- This table lists properties of running instances of ROHC 627 -- compressors and decompressors at the managed node. 628 -- 630 rohcInstanceTable OBJECT-TYPE 631 SYNTAX SEQUENCE OF RohcInstanceEntry 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "This table lists properties of running instances 636 of robust header compressors and decompressors 637 at IP interfaces. It is indexed by interface number, 638 the type of instance (compressor or decompressor), 639 and and the ID of the channel used by the instance as 640 ROHC channel. 642 Note that the rohcChannelID uniquely identifies an 643 instance. The ifIndex and rohcInstanceType are part 644 of the index, because it simplifies accessing instances 645 per interface and for addressing either compressors or 646 decompressors only." 647 ::= { rohcInstanceObjects 2 } 649 rohcInstanceEntry OBJECT-TYPE 650 SYNTAX RohcInstanceEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "An entry describing a particular instance 655 of a robust header compressor or decompressor." 656 INDEX { ifIndex, rohcInstanceType, rohcChannelID } 657 ::= { rohcInstanceTable 1 } 659 RohcInstanceEntry ::= SEQUENCE { 660 rohcInstanceType INTEGER, 661 rohcInstanceFBChannelID RohcChannelIdentifierOrZero, 662 rohcInstanceVendor OBJECT IDENTIFIER, 663 rohcInstanceVersion SnmpAdminString, 664 rohcInstanceDescr SnmpAdminString, 665 rohcInstanceClockRes Unsigned32, 666 rohcInstanceMaxCID Unsigned32, 667 rohcInstanceLargeCIDs TruthValue, 668 rohcInstanceMRRU Unsigned32, 669 rohcInstanceContextStorageTime TimeInterval, 670 rohcInstanceStatus INTEGER, 671 rohcInstanceContextsTotal Counter32, 672 rohcInstanceContextsCurrent Unsigned32, 673 rohcInstancePackets Counter32, 674 rohcInstanceIRs Counter32, 675 rohcInstanceIRDYNs Counter32, 676 rohcInstanceFeedbacks Counter32, 677 rohcInstanceCompressionRatio RohcCompressionRatio 678 } 680 rohcInstanceType OBJECT-TYPE 681 SYNTAX INTEGER { 682 compressor(1), 683 decompressor(2) 684 } 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "Type of the instance of ROHC. It is either a 689 compressor instance or a decompressor instance." 690 ::= { rohcInstanceEntry 2 } 692 rohcInstanceFBChannelID OBJECT-TYPE 693 SYNTAX RohcChannelIdentifierOrZero 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "Identifier of the channel used for feedback. 698 If no feedback channel is used, the value of 699 this object is 0 ." 700 REFERENCE 701 "RFC 3095, Section 5.1.1" 702 ::= { rohcInstanceEntry 4 } 704 rohcInstanceVendor OBJECT-TYPE 705 SYNTAX OBJECT IDENTIFIER 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "An object identifer that identifies the vendor who 710 provides the implementation of robust header description. 711 This object identifer SHALL point to the object identifier 712 directly below the enterprise object identifier 713 {1 3 6 1 4 1} allocated for the vendor. The value must be 714 the object identifier {0 0} if the vendor is not known." 715 ::= { rohcInstanceEntry 5 } 717 rohcInstanceVersion OBJECT-TYPE 718 SYNTAX SnmpAdminString (SIZE (0..32)) 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The version number of the implementation of robust header 723 compression. The zero-length string shall be used if the 724 implementation does not have a version number. 726 It is suggested that the version number consist of one or 727 more decimal numbers separated by dots, where the first 728 number is called the major version number." 729 ::= { rohcInstanceEntry 6 } 731 rohcInstanceDescr OBJECT-TYPE 732 SYNTAX SnmpAdminString 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "A textual description of the implementation." 737 ::= { rohcInstanceEntry 7 } 739 rohcInstanceClockRes OBJECT-TYPE 740 SYNTAX Unsigned32 741 UNITS "milliseconds" 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 "This object indicates the system clock resolution in 746 units of milliseconds. A zero (0) value means that there 747 is no clock available." 748 ::= { rohcInstanceEntry 8 } 750 rohcInstanceMaxCID OBJECT-TYPE 751 SYNTAX Unsigned32 (1..16383) 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The highest context ID number to be used by the 756 compressor. Note that this parameter is not coupled to, 757 but in effect further constrained by, 758 rohcChannelLargeCIDs." 759 REFERENCE 760 "RFC 3095, Section 5.1.1" 761 ::= { rohcInstanceEntry 9 } 763 rohcInstanceLargeCIDs OBJECT-TYPE 764 SYNTAX TruthValue 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "When retrieved, this boolean object returns false if 769 the short CID representation (0 bytes or 1 prefix byte, 770 covering CID 0 to 15) is used; it returns true, if the 771 embedded CID representation (1 or 2 embedded CID bytes 772 covering CID 0 to 16383) is used." 773 REFERENCE 774 "RFC 3095, Section 5.1.1" 775 ::= { rohcInstanceEntry 10 } 777 rohcInstanceMRRU OBJECT-TYPE 778 SYNTAX Unsigned32 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "Maximum reconstructed reception unit. This is the 783 size of the largest reconstructed unit in octets that 784 the decompressor is expected to reassemble from 785 segments (see RFC 3095, Section 5.2.5). Note that this 786 size includes the CRC. If MRRU is negotiated to be 0, 787 no segment headers are allowed on the channel." 788 REFERENCE 789 "RFC 3095, Section 5.1.1" 790 ::= { rohcInstanceEntry 11 } 792 rohcInstanceContextStorageTime OBJECT-TYPE 793 SYNTAX TimeInterval 794 UNITS "centi-seconds" 795 MAX-ACCESS read-write 796 STATUS current 797 DESCRIPTION 798 "This object indicates the default maximum amount of time 799 information on a context belonging to this instance is kept 800 as entry in the rohcContextTable after the context is 801 expired or terminated. The value of this object is used 802 to initialize rohcContexStorageTime object when a new 803 context is created. 804 Changing the value of an rohcInstanceContextStorageTime 805 instance does not affect any entry of the rohcContextTable 806 created previously. 807 ROHC-MIB implementations SHOULD store the set value of this 808 object persistently." 809 DEFVAL { 360000 } 810 ::= { rohcInstanceEntry 12 } 812 rohcInstanceStatus OBJECT-TYPE 813 SYNTAX INTEGER { 814 enabled(1), 815 disabled(2) 816 } 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "Status of the instance of ROHC." 821 ::= { rohcInstanceEntry 13 } 823 rohcInstanceContextsTotal OBJECT-TYPE 824 SYNTAX Counter32 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "Counter of all contexts created by this instance. 830 Discontinuities in the value of this counter can 831 occur at re-initialization of the management 832 system, and at other times as indicated by the 833 value of ifCounterDiscontinuityTime." 834 ::= { rohcInstanceEntry 14 } 836 rohcInstanceContextsCurrent OBJECT-TYPE 837 SYNTAX Unsigned32 838 MAX-ACCESS read-only 839 STATUS current 840 DESCRIPTION 841 "Number of currently active contexts created by this 842 instance." 843 ::= { rohcInstanceEntry 15 } 845 rohcInstancePackets OBJECT-TYPE 846 SYNTAX Counter32 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "Counter of all packets passing this instance. 852 Discontinuities in the value of this counter can 853 occur at re-initialization of the management 854 system, and at other times as indicated by the 855 value of ifCounterDiscontinuityTime." 856 ::= { rohcInstanceEntry 16 } 858 rohcInstanceIRs OBJECT-TYPE 859 SYNTAX Counter32 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "The number of all IR packets that are either sent 864 or received by this instance. 866 Discontinuities in the value of this counter can 867 occur at re-initialization of the management 868 system, and at other times as indicated by the 869 value of ifCounterDiscontinuityTime." 870 REFERENCE 871 "RFC 3095, Section 5.7.7.1" 872 ::= { rohcInstanceEntry 17 } 874 rohcInstanceIRDYNs OBJECT-TYPE 875 SYNTAX Counter32 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The number of all IR-DYN packets that are either sent 880 or received by this instance. 882 Discontinuities in the value of this counter can 883 occur at re-initialization of the management 884 system, and at other times as indicated by the 885 value of ifCounterDiscontinuityTime." 886 REFERENCE 887 "RFC 3095, Section 5.7.7.2" 888 ::= { rohcInstanceEntry 18 } 890 rohcInstanceFeedbacks OBJECT-TYPE 891 SYNTAX Counter32 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "The number of all feedbacks that are either sent 896 or received by this instance. 898 Discontinuities in the value of this counter can 899 occur at re-initialization of the management 900 system, and at other times as indicated by the 901 value of ifCounterDiscontinuityTime." 902 ::= { rohcInstanceEntry 19 } 904 rohcInstanceCompressionRatio OBJECT-TYPE 905 SYNTAX RohcCompressionRatio 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "This object indicates the compression ratio so far over all 910 packets on the channel served by this instance. The 911 compression is computed over all bytes of the IP packets 912 including the IP header but excluding all lower layer 913 headers." 914 ::= { rohcInstanceEntry 20 } 916 -- 917 -- Profile Table 918 -- 920 rohcProfileTable OBJECT-TYPE 921 SYNTAX SEQUENCE OF RohcProfileEntry 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "This table lists a set of profiles supported by the 926 instance." 927 REFERENCE 928 "RFC 3095, Section 5.1.1" 929 ::= { rohcInstanceObjects 3 } 931 rohcProfileEntry OBJECT-TYPE 932 SYNTAX RohcProfileEntry 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "An entry describing a particular profile supported by 937 the instance. It is indexed by the rohcChannelID 938 identifying the instance and by the rohcProfile." 939 INDEX { rohcChannelID, rohcProfile } 940 ::= { rohcProfileTable 1 } 942 RohcProfileEntry ::= SEQUENCE { 943 rohcProfile Unsigned32, 944 rohcProfileVendor OBJECT IDENTIFIER, 945 rohcProfileVersion SnmpAdminString, 946 rohcProfileDescr SnmpAdminString, 947 rohcProfileNegotiated TruthValue 948 } 950 rohcProfile OBJECT-TYPE 951 SYNTAX Unsigned32 (0..65535) 952 MAX-ACCESS not-accessible 953 STATUS current 954 DESCRIPTION 955 "Identifier of a profile supported. For a listing of 956 possible profile values, see the IANA registry for 957 'RObust Header Compression (ROHC) Profile Identifiers' 958 at http://www.iana.org/assignments/rohc-pro-ids" 959 ::= { rohcProfileEntry 2 } 961 rohcProfileVendor OBJECT-TYPE 962 SYNTAX OBJECT IDENTIFIER 963 MAX-ACCESS read-only 964 STATUS current 965 DESCRIPTION 966 "An object identifer that identifies the vendor who 967 provides the implementation of robust header description. 968 This object identifer SHALL point to the object identifier 969 directly below the enterprise object identifier 970 {1 3 6 1 4 1} allocated for the vendor. The value must be 971 the object identifier {0 0} if the vendor is not known." 972 ::= { rohcProfileEntry 3 } 974 rohcProfileVersion OBJECT-TYPE 975 SYNTAX SnmpAdminString (SIZE (0..32)) 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "The version number of the implementation of robust header 980 compression. The zero-length string shall be used if the 981 implementation does not have a version number. 983 It is suggested that the version number consist of one or 984 more decimal numbers separated by dots, where the first 985 number is called the major version number." 986 ::= { rohcProfileEntry 4 } 988 rohcProfileDescr OBJECT-TYPE 989 SYNTAX SnmpAdminString 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "A textual description of the implementation." 994 ::= { rohcProfileEntry 5 } 996 rohcProfileNegotiated OBJECT-TYPE 997 SYNTAX TruthValue 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "When retrieved, this boolean object returns true 1002 if the profile has been negotiated to be used at 1003 the instance, i.e. is supported also be the 1004 corresponding compressor/decompressor." 1005 ::= { rohcProfileEntry 6 } 1007 -- 1008 -- Context Table 1009 -- 1011 rohcContextTable OBJECT-TYPE 1012 SYNTAX SEQUENCE OF RohcContextEntry 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "This table lists and describes all compressor contexts 1017 per instance." 1018 ::= { rohcObjects 2 } 1020 rohcContextEntry OBJECT-TYPE 1021 SYNTAX RohcContextEntry 1022 MAX-ACCESS not-accessible 1023 STATUS current 1024 DESCRIPTION 1025 "An entry describing a particular compressor context." 1026 INDEX { 1027 rohcChannelID, 1028 rohcContextCID 1029 } 1030 ::= { rohcContextTable 1 } 1032 RohcContextEntry ::= SEQUENCE { 1033 rohcContextCID Unsigned32, 1034 rohcContextCIDState INTEGER, 1035 rohcContextProfile Unsigned32, 1036 rohcContextDecompressorDepth Unsigned32, 1037 rohcContextStorageTime TimeInterval, 1038 rohcContextActivationTime DateAndTime, 1039 rohcContextDeactivationTime DateAndTime, 1040 rohcContextPackets Counter32, 1041 rohcContextIRs Counter32, 1042 rohcContextIRDYNs Counter32, 1043 rohcContextFeedbacks Counter32, 1044 rohcContextDecompressorFailures Counter32, 1045 rohcContextDecompressorRepairs Counter32, 1046 rohcContextAllPacketsRatio RohcCompressionRatio, 1047 rohcContextAllHeadersRatio RohcCompressionRatio, 1048 rohcContextAllPacketsMeanSize Unsigned32, 1049 rohcContextAllHeadersMeanSize Unsigned32, 1050 rohcContextLastPacketsRatio RohcCompressionRatio, 1051 rohcContextLastHeadersRatio RohcCompressionRatio, 1052 rohcContextLastPacketsMeanSize Unsigned32, 1053 rohcContextLastHeadersMeanSize Unsigned32 1054 } 1056 rohcContextCID OBJECT-TYPE 1057 SYNTAX Unsigned32 (0..16383) 1058 MAX-ACCESS not-accessible 1059 STATUS current 1060 DESCRIPTION 1061 "The context identifier (CID) of this context." 1062 REFERENCE 1063 "RFC 3095, Sections 5.1.1 and 5.1.3" 1064 ::= { rohcContextEntry 2 } 1066 rohcContextCIDState OBJECT-TYPE 1067 SYNTAX INTEGER { 1068 unused(1), 1069 active(2), 1070 expired(3), 1071 terminated(4) 1072 } 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "State of the CID. When a CID is assigned to a context, 1077 its state changes from `unused' to `active'. The active 1078 context may stop operation due to some explicit 1079 signalling or after observing no packet for some specified 1080 time. In the first case then the CID state changes to 1081 `terminated', in the latter case it changes to `expired'. 1082 If the CID is re-used again for another context, the 1083 state changes back to `active'." 1084 ::= { rohcContextEntry 3 } 1086 rohcContextProfile OBJECT-TYPE 1087 SYNTAX Unsigned32 (0..65535) 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "Identifier of the profile for this context. 1092 The profile is identified by its index in the 1093 rohcProfileTable for this instance. There MUST exist a 1094 corresponding entry in the rohcProfileTable using the 1095 value of rohcContextProfile as second part of the index 1096 (and using the same rohcChannelID as first part of the 1097 index)." 1098 ::= { rohcContextEntry 4 } 1100 rohcContextDecompressorDepth OBJECT-TYPE 1101 SYNTAX Unsigned32 1102 MAX-ACCESS read-only 1103 STATUS current 1104 DESCRIPTION 1105 "This object indicates whether reverse decompression, for 1106 example as described in RFC 3095, Section 6.1, is used 1107 on this channel or not, and if used, to what extent. 1109 Its value is only valid for decompressor contexts, i.e. 1110 if rohcInstanceType has the value decompressor(2). For 1111 compressor contexts where rohcInstanceType has the value 1112 compressor(1), the value of this object is irrelavant 1113 and MUST be set to zero (0). 1115 The value of the reverse decompression depth indicates 1116 the maximum number of packets that are buffered, and thus 1117 possibly be reverse decompressed by the decompressor. 1118 A zero (0) value means that reverse decompression is not 1119 used." 1120 ::= { rohcContextEntry 5 } 1122 rohcContextStorageTime OBJECT-TYPE 1123 SYNTAX TimeInterval 1124 UNITS "centi-seconds" 1125 MAX-ACCESS read-write 1126 STATUS current 1127 DESCRIPTION 1128 "The value of this object specifies how long this row 1129 can exist in the rohcContextTable after the 1130 rohcContextCIDState switched to expired(3) or 1131 terminated(4). This object returns the remaining time 1132 that the row may exist before it is aged out. The object 1133 is initialized with the value of the associated 1134 rohcContextStorageTime object. After expiration or 1135 termination of the context, the value of this object ticks 1136 backwards. The entry in the rohcContextTable is destroyed 1137 when the value reaches 0. 1139 The value of this object may be set in order to increase or 1140 reduce the remaining time that the row may exist. Setting 1141 the value to 0 will destroy this entry as soon as the 1142 rochContextCIDState has the value expired(3) or 1143 terminated(4). 1145 Note that there is no guarantee that the row is stored as 1146 long as this object indicates. In case of limited CID 1147 space, the instance may re-use a CID before the storage 1148 time of the corresponding row in rohcContextTable reaches 1149 the value of 0. In this case the information stored in this 1150 row is not anymore available." 1151 ::= { rohcContextEntry 6 } 1153 rohcContextActivationTime OBJECT-TYPE 1154 SYNTAX DateAndTime 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The date and time when the context started to be able to 1159 compress packets or decompress packets, respectively. 1160 The value '0000000000000000'H is returned if the context 1161 has not been activated yet." 1162 DEFVAL { '0000000000000000'H } 1163 ::= { rohcContextEntry 7 } 1165 rohcContextDeactivationTime OBJECT-TYPE 1166 SYNTAX DateAndTime 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "The date and time when the context stopped being able to 1171 compress packets or decompress packest, respectively, 1172 because it expired or was terminated for other reasons. 1173 The value '0000000000000000'H is returned if the context 1174 has not been deactivated yet." 1175 DEFVAL { '0000000000000000'H } 1176 ::= { rohcContextEntry 8 } 1178 rohcContextPackets OBJECT-TYPE 1179 SYNTAX Counter32 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "The number of all packets passing this context. 1185 Discontinuities in the value of this counter can 1186 occur at re-initialization of the management 1187 system, and at other times as indicated by the 1188 value of ifCounterDiscontinuityTime. For checking 1189 ifCounterDiscontinuityTime, the interface index is 1190 required. It can be determined by reading the 1191 rohcChannelTable." 1192 ::= { rohcContextEntry 9 } 1194 rohcContextIRs OBJECT-TYPE 1195 SYNTAX Counter32 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "The number of all IR packets sent or received, 1200 respectively, by this context. 1202 Discontinuities in the value of this counter can 1203 occur at re-initialization of the management 1204 system, and at other times as indicated by the 1205 value of ifCounterDiscontinuityTime. For checking 1206 ifCounterDiscontinuityTime, the interface index is 1207 required. It can be determined by reading the 1208 rohcChannelTable." 1209 REFERENCE 1210 "RFC 3095, Section 5.7.7.1" 1211 ::= { rohcContextEntry 10 } 1213 rohcContextIRDYNs OBJECT-TYPE 1214 SYNTAX Counter32 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "The number of all IR-DYN packets sent or received, 1219 respectively, by this context. 1221 Discontinuities in the value of this counter can 1222 occur at re-initialization of the management 1223 system, and at other times as indicated by the 1224 value of ifCounterDiscontinuityTime. For checking 1225 ifCounterDiscontinuityTime, the interface index is 1226 required. It can be determined by reading the 1227 rohcChannelTable." 1228 REFERENCE 1229 "RFC 3095, Section 5.7.7.2" 1230 ::= { rohcContextEntry 11 } 1232 rohcContextFeedbacks OBJECT-TYPE 1233 SYNTAX Counter32 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "The number of all feedbacks sent or received, 1238 respectively, by this context. 1240 Discontinuities in the value of this counter can 1241 occur at re-initialization of the management 1242 system, and at other times as indicated by the 1243 value of ifCounterDiscontinuityTime. For checking 1244 ifCounterDiscontinuityTime, the interface index is 1245 required. It can be determined by reading the 1246 rohcChannelTable." 1247 ::= { rohcContextEntry 12 } 1249 rohcContextDecompressorFailures OBJECT-TYPE 1250 SYNTAX Counter32 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "The number of all decompressor failures so far in this 1255 context. The number is only valid for decompressor 1256 contexts, i.e. if rohcInstanceType has the value 1257 decompressor(2). 1259 Discontinuities in the value of this counter can 1260 occur at re-initialization of the management 1261 system, and at other times as indicated by the 1262 value of ifCounterDiscontinuityTime. For checking 1263 ifCounterDiscontinuityTime, the interface index is 1264 required. It can be determined by reading the 1265 rohcChannelTable." 1266 ::= { rohcContextEntry 13 } 1268 rohcContextDecompressorRepairs OBJECT-TYPE 1269 SYNTAX Counter32 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The number of all context repairs so far in this 1274 context. The number is only valid for decompressor 1275 contexts, i.e. if rohcInstanceType has the value 1276 decompressor(2). 1278 Discontinuities in the value of this counter can 1279 occur at re-initialization of the management 1280 system, and at other times as indicated by the 1281 value of ifCounterDiscontinuityTime. For checking 1282 ifCounterDiscontinuityTime, the interface index is 1283 required. It can be determined by reading the 1284 rohcChannelTable." 1285 ::= { rohcContextEntry 14 } 1287 rohcContextAllPacketsRatio OBJECT-TYPE 1288 SYNTAX RohcCompressionRatio 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "This object indicates the compression ratio so far over all 1293 packets passing this context. The compression is computed 1294 over all bytes of the IP packets including the IP header 1295 but excluding all lower layer headers." 1297 ::= { rohcContextEntry 15 } 1299 rohcContextAllHeadersRatio OBJECT-TYPE 1300 SYNTAX RohcCompressionRatio 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "This object indicates the compression ratio so far over all 1305 packet headers passing this context. The compression is 1306 computed over all bytes of all headers that are subject to 1307 compression for the used profile." 1308 ::= { rohcContextEntry 16 } 1310 rohcContextAllPacketsMeanSize OBJECT-TYPE 1311 SYNTAX Unsigned32 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "This object indicates the mean compressed packet size 1316 of all packets passing this context. The packet size 1317 includes the IP header and payload but excludes all lower 1318 layer headers. The mean value is given in byte rounded 1319 to the next integer value." 1320 ::= { rohcContextEntry 17 } 1322 rohcContextAllHeadersMeanSize OBJECT-TYPE 1323 SYNTAX Unsigned32 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "This object indicates the mean compressed packet header size 1328 of all packets passing this context. The packet header size 1329 is the sum of the size of all headers of a packet that are 1330 subject to compression for the used profile. The mean value 1331 is given in byte rounded to the next integer value." 1332 ::= { rohcContextEntry 18 } 1334 rohcContextLastPacketsRatio OBJECT-TYPE 1335 SYNTAX RohcCompressionRatio 1336 MAX-ACCESS read-only 1337 STATUS current 1338 DESCRIPTION 1339 "This object indicates the compression ratio 1340 concerning the last 16 packets passing this context 1341 or concerning all packets passing this context 1342 if they are less than 16, so far. The compression is 1343 computed over all bytes of the IP packets including the IP 1344 header but excluding all lower layer headers." 1345 ::= { rohcContextEntry 19 } 1347 rohcContextLastHeadersRatio OBJECT-TYPE 1348 SYNTAX RohcCompressionRatio 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "This object indicates the compression ratio concerning the 1353 headers of the last 16 packets passing this context or 1354 concerning the headers of all packets passing this context 1355 if they are less than 16, so far. The compression is 1356 computed over all bytes of all headers that are subject to 1357 compression for the used profile." 1358 ::= { rohcContextEntry 20 } 1360 rohcContextLastPacketsMeanSize OBJECT-TYPE 1361 SYNTAX Unsigned32 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 "This object indicates the mean compressed packet size 1366 concerning the last 16 packets passing this context or 1367 concerning all packets passing this context if they are 1368 less than 16, so far. The packet size includes the IP 1369 header and payload but excludes all lower layer headers. 1370 The mean value is given in byte rounded to the next 1371 integer value." 1372 ::= { rohcContextEntry 21 } 1374 rohcContextLastHeadersMeanSize OBJECT-TYPE 1375 SYNTAX Unsigned32 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "This object indicates the mean compressed packet header size 1380 concerning the last 16 packets passing this context or 1381 concerning all packets passing this context if they are 1382 less than 16, so far. The packet header size is the sum of 1383 the size of all headers of a packet that are subject to 1384 compression for the used profile. The mean value is given 1385 in byte rounded to the next integer value." 1386 ::= { rohcContextEntry 22 } 1388 -- 1389 -- conformance information 1390 -- 1392 rohcCompliances OBJECT IDENTIFIER ::= { rohcConformance 1 } 1393 rohcGroups OBJECT IDENTIFIER ::= { rohcConformance 2 } 1395 -- 1396 -- compliance statements 1397 -- 1399 rohcCompliance MODULE-COMPLIANCE 1400 STATUS current 1401 DESCRIPTION 1402 "The compliance statement for SNMP entities that implement 1403 the ROHC-MIB. 1405 Note that compliance with this compliance 1406 statement requires compliance with the 1407 ifCompliance3 MODULE-COMPLIANCE statement of the 1408 IF-MIB (RFC2863)." 1409 MODULE -- this module 1410 MANDATORY-GROUPS { 1411 rohcInstanceGroup, rohcContextGroup 1412 } 1413 GROUP rohcStatisticsGroup 1414 DESCRIPTION 1415 "A compliant implementation does not have to implement 1416 the rohcStatisticsGroup." 1417 GROUP rohcTimerGroup 1418 DESCRIPTION 1419 "A compliant implementation does not have to implement 1420 the rohcTimerGroup." 1421 OBJECT rohcInstanceContextStorageTime 1422 MIN-ACCESS read-only 1423 DESCRIPTION 1424 "A compliant implementation does not have to support changing 1425 the value of object rohcInstanceContextStorageTime." 1426 OBJECT rohcContextStorageTime 1427 MIN-ACCESS read-only 1428 DESCRIPTION 1429 "A compliant implementation does not have to support changing 1430 the value of object rohcContextStorageTime." 1431 GROUP rohcContextStatisticsGroup 1432 DESCRIPTION 1433 "A compliant implementation does not have to implement 1434 the rohcContextStatisticsGroup." 1435 ::= { rohcCompliances 1 } 1437 rohcInstanceGroup OBJECT-GROUP 1438 OBJECTS { 1439 rohcChannelType, 1440 rohcChannelFeedbackFor, 1441 rohcChannelDescr, 1442 rohcChannelStatus, 1443 rohcInstanceFBChannelID, 1444 rohcInstanceVendor, 1445 rohcInstanceVersion, 1446 rohcInstanceDescr, 1447 rohcInstanceClockRes, 1448 rohcInstanceMaxCID, 1449 rohcInstanceLargeCIDs, 1450 rohcInstanceMRRU, 1451 rohcInstanceStatus, 1452 rohcProfileVendor, 1453 rohcProfileVersion, 1454 rohcProfileDescr, 1455 rohcProfileNegotiated 1456 } 1457 STATUS current 1458 DESCRIPTION 1459 "A collection of objects providing information about 1460 ROHC instances, used channels and available profiles." 1461 ::= { rohcGroups 2 } 1463 rohcStatisticsGroup OBJECT-GROUP 1464 OBJECTS { 1465 rohcInstanceContextsTotal, 1466 rohcInstanceContextsCurrent, 1467 rohcInstancePackets, 1468 rohcInstanceIRs, 1469 rohcInstanceIRDYNs, 1470 rohcInstanceFeedbacks, 1471 rohcInstanceCompressionRatio 1472 } 1473 STATUS current 1474 DESCRIPTION 1475 "A collection of objects providing ROHC statistics." 1476 ::= { rohcGroups 4 } 1478 rohcContextGroup OBJECT-GROUP 1479 OBJECTS { 1480 rohcContextCIDState, 1481 rohcContextProfile, 1482 rohcContextDecompressorDepth 1483 } 1484 STATUS current 1485 DESCRIPTION 1486 "A collection of objects providing information about 1487 ROHC compressor contexts and decompressor contexts." 1488 ::= { rohcGroups 5 } 1490 rohcTimerGroup OBJECT-GROUP 1491 OBJECTS { 1492 rohcInstanceContextStorageTime, 1493 rohcContextStorageTime, 1494 rohcContextActivationTime, 1495 rohcContextDeactivationTime 1497 } 1498 STATUS current 1499 DESCRIPTION 1500 "A collection of objects providing statistical information 1501 about ROHC compressor contexts and decompressor contexts." 1502 ::= { rohcGroups 6 } 1504 rohcContextStatisticsGroup OBJECT-GROUP 1505 OBJECTS { 1506 rohcContextPackets, 1507 rohcContextIRs, 1508 rohcContextIRDYNs, 1509 rohcContextFeedbacks, 1510 rohcContextDecompressorFailures, 1511 rohcContextDecompressorRepairs, 1512 rohcContextAllPacketsRatio, 1513 rohcContextAllHeadersRatio, 1514 rohcContextAllPacketsMeanSize, 1515 rohcContextAllHeadersMeanSize, 1516 rohcContextLastPacketsRatio, 1517 rohcContextLastHeadersRatio, 1518 rohcContextLastPacketsMeanSize, 1519 rohcContextLastHeadersMeanSize 1520 } 1521 STATUS current 1522 DESCRIPTION 1523 "A collection of objects providing statistical information 1524 about ROHC compressor contexts and decompressor contexts." 1525 ::= { rohcGroups 7 } 1527 END 1528 ROHC-UNCOMPRESSED-MIB DEFINITIONS ::= BEGIN 1530 IMPORTS 1531 MODULE-IDENTITY, OBJECT-TYPE, Counter32, mib-2 1532 FROM SNMPv2-SMI -- RFC2578 1534 MODULE-COMPLIANCE, OBJECT-GROUP 1535 FROM SNMPv2-CONF -- RFC2580 1537 rohcChannelID, rohcContextCID 1538 FROM ROHC-MIB; 1540 rohcUncmprMIB MODULE-IDENTITY 1541 LAST-UPDATED "200401040102Z" -- January 04, 2004 1542 ORGANIZATION "IETF Robust Header Compression Working Group" 1543 CONTACT-INFO 1544 "WG charter: 1545 http://www.ietf.org/html.charters/rohc-charter.html 1547 Mailing Lists: 1548 General Discussion: rohc@ietf.org 1549 To Subscribe: rohc-request@ietf.org 1550 In Body: subscribe your_email_address 1552 Editor: 1553 Juergen Quittek 1554 NEC Europe Ltd. 1555 Network Laboratories 1556 Kurfuersten-Anlage 36 1557 69221 Heidelberg 1558 Germany 1559 Tel: +49 6221 90511-15 1560 Email: quittek@ccrle.nec.de" 1561 DESCRIPTION 1562 "This MIB module defines a set of objects for monitoring 1563 and configuring RObust Header Compression (ROHC). 1564 The objects are specific to ROHC uncompressed 1565 (profile 0x0000). 1567 Copyright (C) The Internet Society (2004). This version 1568 of this MIB module is part of RFC yyyy; see the RFC 1569 itself for full legal notices." 1570 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 1572 REVISION "200401040102Z" -- January 04, 2004 1573 DESCRIPTION "Initial version, published as RFC yyyy." 1574 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 1576 ::= { mib-2 XXXX } 1577 -- XXXX to be assigned by IANA. 1579 -- 1580 -- The groups defined within this MIB module: 1581 -- 1583 rohcUncmprObjects OBJECT IDENTIFIER ::= { rohcUncmprMIB 1 } 1584 rohcUncmprConformance OBJECT IDENTIFIER ::= { rohcUncmprMIB 2 } 1586 -- 1587 -- Context Table 1588 -- 1589 -- The rohcUncmprContextTable lists all contexts per interface 1590 -- and instance. It extends the rohcContextTable. 1591 -- 1593 rohcUncmprContextTable OBJECT-TYPE 1594 SYNTAX SEQUENCE OF RohcUncmprContextEntry 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "This table lists and describes ROHC uncompressed profile 1599 specific properties of compressor contexts and 1600 decompressor contexts. It extends the rohcContextTable 1601 of the ROHC-MIB module." 1602 ::= { rohcUncmprObjects 1 } 1604 rohcUncmprContextEntry OBJECT-TYPE 1605 SYNTAX RohcUncmprContextEntry 1606 MAX-ACCESS not-accessible 1607 STATUS current 1608 DESCRIPTION 1609 "An entry describing a particular context." 1610 INDEX { 1611 rohcChannelID, 1612 rohcContextCID 1613 } 1614 ::= { rohcUncmprContextTable 1 } 1616 RohcUncmprContextEntry ::= SEQUENCE { 1617 rohcUncmprContextState INTEGER, 1618 rohcUncmprContextMode INTEGER, 1619 rohcUncmprContextACKs Counter32 1620 } 1622 rohcUncmprContextState OBJECT-TYPE 1623 SYNTAX INTEGER { 1624 initAndRefresh(1), 1625 normal(2), 1626 noContext(3), 1627 fullContext(4) 1628 } 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "State of the context. States initAndRefresh(1) and normal(2) 1634 are states of compressor contexts, states noContext(3) 1635 and fullContext(4) are states of decompressor contexts." 1636 REFERENCE 1637 "RFC 3095, Section 5.10.3" 1638 ::= { rohcUncmprContextEntry 3 } 1640 rohcUncmprContextMode OBJECT-TYPE 1641 SYNTAX INTEGER { 1642 unidirectional(1), 1643 bidirectional(2) 1644 } 1645 MAX-ACCESS read-only 1646 STATUS current 1647 DESCRIPTION 1648 "Mode of the context." 1649 REFERENCE 1650 "RFC 3095, Section 5.10.3" 1651 ::= { rohcUncmprContextEntry 4 } 1653 rohcUncmprContextACKs OBJECT-TYPE 1654 SYNTAX Counter32 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "The number of all positive feedbacks (ACK) sent or 1659 received in this context, respectively. 1661 Discontinuities in the value of this counter can 1662 occur at re-initialization of the management 1663 system, and at other times as indicated by the 1664 value of ifCounterDiscontinuityTime. For checking 1665 ifCounterDiscontinuityTime, the interface index is 1666 required. It can be determined by reading the 1667 rohcChannelTable of the ROHC-MIB." 1668 REFERENCE 1669 "RFC 3095, Section 5.2.1" 1670 ::= { rohcUncmprContextEntry 5 } 1672 -- 1673 -- conformance information 1674 -- 1676 rohcUncmprCompliances OBJECT IDENTIFIER 1677 ::= { rohcUncmprConformance 1 } 1678 rohcUncmprGroups OBJECT IDENTIFIER 1679 ::= { rohcUncmprConformance 2 } 1681 -- 1682 -- compliance statements 1683 -- 1685 rohcUncmprCompliance MODULE-COMPLIANCE 1686 STATUS current 1687 DESCRIPTION 1688 "The compliance statement for SNMP entities that implement 1689 the ROHC-UNCOMPRESSED-MIB. 1691 Note that compliance with this compliance 1692 statement requires compliance with the 1693 rohcCompliance MODULE-COMPLIANCE statement of the 1694 ROHC-MIB and with the ifCompliance3 MODULE-COMPLIANCE 1695 statement of the IF-MIB (RFC2863)." 1696 MODULE -- this module 1697 MANDATORY-GROUPS { 1698 rohcUncmprContextGroup 1699 } 1700 GROUP rohcUncmprStatisticsGroup 1701 DESCRIPTION 1702 "A compliant implementation does not have to implement 1703 the rohcUncmprStatisticsGroup." 1704 ::= { rohcUncmprCompliances 1 } 1706 rohcUncmprContextGroup OBJECT-GROUP 1707 OBJECTS { 1708 rohcUncmprContextState, 1709 rohcUncmprContextMode 1710 } 1711 STATUS current 1712 DESCRIPTION 1713 "A collection of objects providing information about 1714 ROHC uncompressed compressors and decompressors." 1715 ::= { rohcUncmprGroups 1 } 1717 rohcUncmprStatisticsGroup OBJECT-GROUP 1718 OBJECTS { 1719 rohcUncmprContextACKs 1720 } 1721 STATUS current 1722 DESCRIPTION 1723 "An object providing context statistics." 1724 ::= { rohcUncmprGroups 2 } 1726 END 1727 ROHC-RTP-MIB DEFINITIONS ::= BEGIN 1729 IMPORTS 1730 MODULE-IDENTITY, OBJECT-TYPE, 1731 Unsigned32, Counter32, mib-2 1732 FROM SNMPv2-SMI -- RFC2578 1734 TruthValue 1735 FROM SNMPv2-TC -- RFC2579 1737 MODULE-COMPLIANCE, OBJECT-GROUP 1738 FROM SNMPv2-CONF -- RFC2580 1740 rohcChannelID, rohcContextCID 1741 FROM ROHC-MIB; -- RFCyyyy 1742 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 1744 rohcRtpMIB MODULE-IDENTITY 1745 LAST-UPDATED "200401040103Z" -- January 04, 2004 1746 ORGANIZATION "IETF Robust Header Compression Working Group" 1747 CONTACT-INFO 1748 "WG charter: 1749 http://www.ietf.org/html.charters/rohc-charter.html 1751 Mailing Lists: 1752 General Discussion: rohc@ietf.org 1753 To Subscribe: rohc-request@ietf.org 1754 In Body: subscribe your_email_address 1756 Editor: 1757 Juergen Quittek 1758 NEC Europe Ltd. 1759 Network Laboratories 1760 Kurfuersten-Anlage 36 1761 69221 Heidelberg 1762 Germany 1763 Tel: +49 6221 90511-15 1764 Email: quittek@ccrle.nec.de" 1765 DESCRIPTION 1766 "This MIB module defines a set of objects for monitoring 1767 and configuring RObust Header Compression (ROHC). 1768 The objects are specific to ROHC RTP (profile 0x0001), 1769 ROHC UDP (profile 0x0002), and ROHC ESP (profile 0x0003) 1770 defined in RFC 3095 and for the ROHC LLA profile (profile 1771 0x0005) defined in RFC 3242. 1773 Copyright (C) The Internet Society (2004). This version 1774 of this MIB module is part of RFC yyyy; see the RFC 1775 itself for full legal notices." 1776 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 1777 REVISION "200401040103Z" -- January 04, 2004 1778 DESCRIPTION "Initial version, published as RFC yyyy." 1779 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 1781 ::= { mib-2 XXXXX } 1782 -- XXXXX to be assigned by IANA. 1784 -- 1785 -- The groups defined within this MIB module: 1786 -- 1788 rohcRtpObjects OBJECT IDENTIFIER ::= { rohcRtpMIB 1 } 1789 rohcRtpConformance OBJECT IDENTIFIER ::= { rohcRtpMIB 2 } 1791 -- 1792 -- Context Table 1793 -- 1794 -- The rohcRtpContextTable lists all contexts per interface 1795 -- and instance. It extends the rohcContextTable. 1796 -- 1798 rohcRtpContextTable OBJECT-TYPE 1799 SYNTAX SEQUENCE OF RohcRtpContextEntry 1800 MAX-ACCESS not-accessible 1801 STATUS current 1802 DESCRIPTION 1803 "This table lists and describes RTP profile specific 1804 properties of compressor contexts and decompressor 1805 contexts. It extends the rohcContextTable of the 1806 ROHC-MIB module." 1807 ::= { rohcRtpObjects 1 } 1809 rohcRtpContextEntry OBJECT-TYPE 1810 SYNTAX RohcRtpContextEntry 1811 MAX-ACCESS not-accessible 1812 STATUS current 1813 DESCRIPTION 1814 "An entry describing a particular context." 1815 INDEX { 1816 rohcChannelID, 1817 rohcContextCID 1818 } 1819 ::= { rohcRtpContextTable 1 } 1821 RohcRtpContextEntry ::= SEQUENCE { 1822 rohcRtpContextState INTEGER, 1823 rohcRtpContextMode INTEGER, 1824 rohcRtpContextAlwaysPad TruthValue, 1825 rohcRtpContextLargePktsAllowed TruthValue, 1826 rohcRtpContextVerifyPeriod Unsigned32, 1827 rohcRtpContextSizesAllowed Unsigned32, 1828 rohcRtpContextSizesUsed Unsigned32, 1829 rohcRtpContextACKs Counter32, 1830 rohcRtpContextNACKs Counter32, 1831 rohcRtpContextSNACKs Counter32, 1832 rohcRtpContextNHPs Counter32, 1833 rohcRtpContextCSPs Counter32, 1834 rohcRtpContextCCPs Counter32, 1835 rohcRtpContextPktsLostPhysical Counter32, 1836 rohcRtpContextPktsLostPreLink Counter32 1837 } 1839 rohcRtpContextState OBJECT-TYPE 1840 SYNTAX INTEGER { 1841 initAndRefresh(1), 1842 firstOrder(2), 1843 secondOrder(3), 1844 noContext(4), 1845 staticContext(5), 1846 fullContext(6) 1847 } 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "State of the context as defined in RFC 3095. States 1852 initAndRefresh(1), firstOrder(2), and secondOrder(3) 1853 are states of compressor contexts, states noContext(4), 1854 staticContext(5) and fullContext(6) are states of 1855 decompressor contexts." 1856 REFERENCE 1857 "RFC 3095" 1858 ::= { rohcRtpContextEntry 3 } 1860 rohcRtpContextMode OBJECT-TYPE 1861 SYNTAX INTEGER { 1862 unidirectional(1), 1863 optimistic(2), 1864 reliable(3) 1865 } 1866 MAX-ACCESS read-only 1867 STATUS current 1868 DESCRIPTION 1869 "Mode of the context." 1870 REFERENCE 1871 "RFC 3095, Section 4.4" 1872 ::= { rohcRtpContextEntry 4 } 1874 rohcRtpContextAlwaysPad OBJECT-TYPE 1875 SYNTAX TruthValue 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "Boolean, only applicable to compressor contexts using the 1880 LLA profile. If its value is true, the compressor must 1881 pad every RHP packet with a minimum of one octet ROHC 1882 padding. 1884 The value of this object is only valid for LLA profiles, 1885 i.e. if the corresponding rohcProfile has a value of 1886 0x0005. If the corresponding rohcProfile has a value 1887 other than 0x0005, then this object MUST NOT be 1888 instantiated." 1889 REFERENCE 1890 "RFC 3242, Section 5.1.1" 1891 DEFVAL { false } 1892 ::= { rohcRtpContextEntry 5 } 1894 rohcRtpContextLargePktsAllowed OBJECT-TYPE 1895 SYNTAX TruthValue 1896 MAX-ACCESS read-only 1897 STATUS current 1898 DESCRIPTION 1899 "Boolean, only applicable to compressor contexts using the 1900 LLA profile. It specifies how to handle packets that do 1901 not fit any of the preferred packet sizes specified. If 1902 its value is true, the compressor must deliver the larger 1903 packet as-is and must not use segmentation. If it is set 1904 to false, the ROHC segmentation scheme must be used to 1905 split the packet into two or more segments, and each 1906 segment must further be padded to fit one of the preferred 1907 packet sizes. 1909 The value of this object is only valid for LLA profiles, 1910 i.e. if the corresponding rohcProfile has a value of 1911 0x0005. If the corresponding rohcProfile has a value 1912 other than 0x0005, then this object MUST NOT be 1913 instantiated." 1914 REFERENCE 1915 "RFC 3242, Section 5.1.1" 1916 DEFVAL { true } 1917 ::= { rohcRtpContextEntry 6 } 1919 rohcRtpContextVerifyPeriod OBJECT-TYPE 1920 SYNTAX Unsigned32 1921 MAX-ACCESS read-only 1922 STATUS current 1923 DESCRIPTION 1924 "This object is only applicable to compressor contexts 1925 using the LLA profile. It specifies the minimum frequency 1926 with which a packet validating the context must be sent. 1928 This tells the compressor that a packet containing a CRC 1929 field must be sent at least once every N packets, where N 1930 is the value of the object. A value of 0 indicates that 1931 periodical verifications are disabled. 1933 The value of this object is only valid for LLA profiles, 1934 i.e. if the corresponding rohcProfile has a value of 1935 0x0005. If the corresponding rohcProfile has a value 1936 other than 0x0005, then this object MUST NOT be 1937 instantiated." 1938 REFERENCE 1939 "RFC 3242, Section 5.1.1" 1940 DEFVAL { 0 } 1941 ::= { rohcRtpContextEntry 7 } 1943 rohcRtpContextSizesAllowed OBJECT-TYPE 1944 SYNTAX Unsigned32 (1..4294967295) 1945 MAX-ACCESS read-only 1946 STATUS current 1947 DESCRIPTION 1948 "The value of this object is only valid for decompressor 1949 contexts, i.e. if rohcInstanceType of the corresponding 1950 rohcContextEntry has the value decompressor(2). For 1951 compressor contexts where rohcInstanceType has the value 1952 compressor(1), this object MUST NOT be instantiated. 1954 This object contains the number of different packet sizes 1955 that may be used in the context." 1956 REFERENCE 1957 "RFC 3095, Section 6.3.1" 1958 ::= { rohcRtpContextEntry 8 } 1960 rohcRtpContextSizesUsed OBJECT-TYPE 1961 SYNTAX Unsigned32 (1..4294967295) 1962 MAX-ACCESS read-only 1963 STATUS current 1964 DESCRIPTION 1965 "The value of this object is only valid for decompressor 1966 contexts, i.e. if rohcInstanceType of the corresponding 1967 rohcContextEntry has the value decompressor(2). For 1968 compressor contexts where rohcInstanceType has the value 1969 compressor(1), this object MUST NOT be instantiated. 1971 This object contains the number of different packet sizes 1972 that are used in the context." 1973 REFERENCE 1974 "RFC 3095, Section 6.3.1" 1975 ::= { rohcRtpContextEntry 9 } 1977 rohcRtpContextACKs OBJECT-TYPE 1978 SYNTAX Counter32 1979 MAX-ACCESS read-only 1980 STATUS current 1981 DESCRIPTION 1982 "The number of all positive feedbacks (ACK) sent or 1983 received in this context, respectively. 1985 Discontinuities in the value of this counter can 1986 occur at re-initialization of the management 1987 system, and at other times as indicated by the 1988 value of ifCounterDiscontinuityTime. For checking 1989 ifCounterDiscontinuityTime, the interface index is 1990 required. It can be determined by reading the 1991 rohcChannelTable of the ROHC-MIB." 1992 REFERENCE 1993 "RFC 3095, Section 5.2.1." 1994 ::= { rohcRtpContextEntry 10 } 1996 rohcRtpContextNACKs OBJECT-TYPE 1997 SYNTAX Counter32 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "The number of all dynamic negative feedbacks (ACK) sent 2002 or received in this context, respectively. 2004 Discontinuities in the value of this counter can 2005 occur at re-initialization of the management 2006 system, and at other times as indicated by the 2007 value of ifCounterDiscontinuityTime. For checking 2008 ifCounterDiscontinuityTime, the interface index is 2009 required. It can be determined by reading the 2010 rohcChannelTable of the ROHC-MIB." 2011 REFERENCE 2012 "RFC 3095, Section 5.2.1." 2013 ::= { rohcRtpContextEntry 11 } 2015 rohcRtpContextSNACKs OBJECT-TYPE 2016 SYNTAX Counter32 2017 MAX-ACCESS read-only 2018 STATUS current 2019 DESCRIPTION 2020 "The number of all static negative feedbacks (ACK) sent 2021 or received in this context, respectively. 2023 Discontinuities in the value of this counter can 2024 occur at re-initialization of the management 2025 system, and at other times as indicated by the 2026 value of ifCounterDiscontinuityTime. For checking 2027 ifCounterDiscontinuityTime, the interface index is 2028 required. It can be determined by reading the 2029 rohcChannelTable of the ROHC-MIB." 2030 REFERENCE 2031 "RFC 3095, Section 5.2.1." 2032 ::= { rohcRtpContextEntry 12 } 2034 rohcRtpContextNHPs OBJECT-TYPE 2035 SYNTAX Counter32 2036 MAX-ACCESS read-only 2037 STATUS current 2038 DESCRIPTION 2039 "This object is only applicable to contexts using the 2040 LLA profile. It contains the number of all no-header 2041 packets (NHP) sent or received in this context, 2042 respectively. 2044 Discontinuities in the value of this counter can 2045 occur at re-initialization of the management 2046 system, and at other times as indicated by the 2047 value of ifCounterDiscontinuityTime. For checking 2048 ifCounterDiscontinuityTime, the interface index is 2049 required. It can be determined by reading the 2050 rohcChannelTable of the ROHC-MIB. 2052 The value of this object is only valid for LLA profiles, 2053 i.e. if the corresponding rohcProfile has a value of 2054 0x0005. If the corresponding rohcProfile has a value 2055 other than 0x0005, then this object MUST NOT be 2056 instantiated." 2057 REFERENCE 2058 "RFC 3242, Section 4.1.1." 2059 ::= { rohcRtpContextEntry 13 } 2061 rohcRtpContextCSPs OBJECT-TYPE 2062 SYNTAX Counter32 2063 MAX-ACCESS read-only 2064 STATUS current 2065 DESCRIPTION 2066 "This object is only applicable to contexts using the 2067 LLA profile. It contains the number of all context 2068 synchronization packets (CSP) sent or received in this 2069 context, respectively. 2071 Discontinuities in the value of this counter can 2072 occur at re-initialization of the management 2073 system, and at other times as indicated by the 2074 value of ifCounterDiscontinuityTime. For checking 2075 ifCounterDiscontinuityTime, the interface index is 2076 required. It can be determined by reading the 2077 rohcChannelTable of the ROHC-MIB. 2079 The value of this object is only valid for LLA profiles, 2080 i.e. if the corresponding rohcProfile has a value of 2081 0x0005. If the corresponding rohcProfile has a value 2082 other than 0x0005, then this object MUST NOT be 2083 instantiated." 2084 REFERENCE 2085 "RFC 3242, Section 4.1.2." 2086 ::= { rohcRtpContextEntry 14 } 2088 rohcRtpContextCCPs OBJECT-TYPE 2089 SYNTAX Counter32 2090 MAX-ACCESS read-only 2091 STATUS current 2092 DESCRIPTION 2093 "This object is only applicable to contexts using the 2094 LLA profile. It contains the number of all context check 2095 packets (CCP) sent or received in this context, 2096 respectively. 2098 Discontinuities in the value of this counter can 2099 occur at re-initialization of the management 2100 system, and at other times as indicated by the 2101 value of ifCounterDiscontinuityTime. For checking 2102 ifCounterDiscontinuityTime, the interface index is 2103 required. It can be determined by reading the 2104 rohcChannelTable of the ROHC-MIB. 2106 The value of this object is only valid for LLA profiles, 2107 i.e. if the corresponding rohcProfile has a value of 2108 0x0005. If the corresponding rohcProfile has a value 2109 other than 0x0005, then this object MUST NOT be 2110 instantiated." 2111 REFERENCE 2112 "RFC 3242, Section 4.1.3." 2113 ::= { rohcRtpContextEntry 15 } 2115 rohcRtpContextPktsLostPhysical OBJECT-TYPE 2116 SYNTAX Counter32 2117 MAX-ACCESS read-only 2118 STATUS current 2119 DESCRIPTION 2120 "This object is only applicable to decompressor contexts 2121 using the LLA profile. It contains the number of physical 2122 packet losses on the link between compressor and 2123 decompressor, that have been indicated to the decompressor. 2125 Discontinuities in the value of this counter can 2126 occur at re-initialization of the management 2127 system, and at other times as indicated by the 2128 value of ifCounterDiscontinuityTime. For checking 2129 ifCounterDiscontinuityTime, the interface index is 2130 required. It can be determined by reading the 2131 rohcChannelTable of the ROHC-MIB. 2133 The value of this object is only valid for LLA profiles, 2134 i.e. if the corresponding rohcProfile has a value of 2135 0x0005. If the corresponding rohcProfile has a value 2136 other than 0x0005, then this object MUST NOT be 2137 instantiated." 2138 REFERENCE 2139 "RFC 3242, Section 5.1.2." 2140 ::= { rohcRtpContextEntry 16 } 2142 rohcRtpContextPktsLostPreLink OBJECT-TYPE 2143 SYNTAX Counter32 2144 MAX-ACCESS read-only 2145 STATUS current 2146 DESCRIPTION 2147 "This object is only applicable to decompressor contexts 2148 using the LLA profile. It contains the number of pre-link 2149 packet losses on the link between compressor and 2150 decompressor, that have been indicated to the decompressor. 2152 Discontinuities in the value of this counter can 2153 occur at re-initialization of the management 2154 system, and at other times as indicated by the 2155 value of ifCounterDiscontinuityTime. For checking 2156 ifCounterDiscontinuityTime, the interface index is 2157 required. It can be determined by reading the 2158 rohcChannelTable of the ROHC-MIB. 2160 The value of this object is only valid for LLA profiles, 2161 i.e. if the corresponding rohcProfile has a value of 2162 0x0005. If the corresponding rohcProfile has a value 2163 other than 0x0005, then this object MUST NOT be 2164 instantiated." 2165 REFERENCE 2166 "RFC 3242, Section 5.1.2." 2167 ::= { rohcRtpContextEntry 17 } 2169 -- 2170 -- Packet Sizes Table 2171 -- 2172 -- The rohcPacketSizeTable lists allowed, preferred, and used 2173 -- packet sizes per compressor context. 2175 rohcRtpPacketSizeTable OBJECT-TYPE 2176 SYNTAX SEQUENCE OF RohcRtpPacketSizeEntry 2177 MAX-ACCESS not-accessible 2178 STATUS current 2179 DESCRIPTION 2180 "This table lists all allowed, preferred, and used packet 2181 sizes per compressor context and channel. 2183 Note, that the sizes table represents implementation 2184 parameters that are suggested by RFC 3095 and/or RFC 3242, 2185 but that are not mandatory." 2186 ::= { rohcRtpObjects 2 } 2188 rohcRtpPacketSizeEntry OBJECT-TYPE 2189 SYNTAX RohcRtpPacketSizeEntry 2190 MAX-ACCESS not-accessible 2191 STATUS current 2192 DESCRIPTION 2193 "An entry of a particular packet size." 2194 INDEX { 2195 rohcChannelID, 2196 rohcContextCID, 2197 rohcRtpPacketSize 2198 } 2199 ::= { rohcRtpPacketSizeTable 1 } 2201 RohcRtpPacketSizeEntry ::= SEQUENCE { 2202 rohcRtpPacketSize Unsigned32, 2203 rohcRtpPacketSizePreferred TruthValue, 2204 rohcRtpPacketSizeUsed TruthValue, 2205 rohcRtpPacketSizeRestrictedType INTEGER 2206 } 2208 rohcRtpPacketSize OBJECT-TYPE 2209 SYNTAX Unsigned32 (1..4294967295) 2210 MAX-ACCESS not-accessible 2211 STATUS current 2212 DESCRIPTION 2213 "A packet size used as index." 2214 ::= { rohcRtpPacketSizeEntry 3 } 2216 rohcRtpPacketSizePreferred OBJECT-TYPE 2217 SYNTAX TruthValue 2218 MAX-ACCESS read-only 2219 STATUS current 2220 DESCRIPTION 2221 "This object is only applicable to compressor contexts 2222 using the LLA profile. When retrieved, it will have 2223 the value true(1) if the packet size is preferred. 2224 Otherwise, its value will be false(2). 2226 The value of this object is only valid for LLA profiles, 2227 i.e. if the corresponding rohcProfile has a value of 2228 0x0005. If the corresponding rohcProfile has a value 2229 other than 0x0005, then this object MUST NOT be 2230 instantiated." 2231 REFERENCE 2232 "RFC 3242, Section 5.1.1" 2233 ::= { rohcRtpPacketSizeEntry 4 } 2235 rohcRtpPacketSizeUsed OBJECT-TYPE 2236 SYNTAX TruthValue 2237 MAX-ACCESS read-only 2238 STATUS current 2239 DESCRIPTION 2240 "This object is only applicable to compressor contexts 2241 using the UDP, RTP, or ESP profile. When retrieved, 2242 it will have the value true(1) if the packet size is 2243 used. Otherwise, its value will be false(2). 2245 The value of this object is only valid for UDP, RTP, 2246 and ESP profiles, i.e. if the corresponding rohcProfile 2247 has a value of either 0x0001, 0x0002 or 0x0003. If 2248 the corresponding rohcProfile has a value other than 2249 0x0001, 0x0002 or 0x0003, then this object MUST NOT be 2250 instantiated." 2251 REFERENCE 2252 "RFC 3095, Section 6.3.1" 2253 ::= { rohcRtpPacketSizeEntry 5 } 2255 rohcRtpPacketSizeRestrictedType OBJECT-TYPE 2256 SYNTAX INTEGER { 2257 nhpOnly(1), 2258 rhpOnly(2), 2259 noRestrictions(3) 2260 } 2261 MAX-ACCESS read-only 2262 STATUS current 2263 DESCRIPTION 2264 "This object is only applicable to preferred packet 2265 sizes of compressor contexts using the LLA profile. 2266 When retrieved, it will indicate whether the packet 2267 size is preferred for NHP only, for RHP only, or 2268 for both of them. 2270 The value of this object is only valid for LLA profiles, 2271 i.e. if the corresponding rohcProfile has a value of 2272 0x0005. If the corresponding rohcProfile has a value 2273 other than 0x0005, then this object MUST NOT be 2274 instantiated." 2275 REFERENCE 2276 "RFC 3242, Section 5.1.1" 2277 ::= { rohcRtpPacketSizeEntry 6 } 2279 -- 2280 -- conformance information 2281 -- 2283 rohcRtpCompliances OBJECT IDENTIFIER ::= { rohcRtpConformance 1 } 2284 rohcRtpGroups OBJECT IDENTIFIER ::= { rohcRtpConformance 2 } 2286 -- 2287 -- compliance statements 2288 -- 2290 rohcRtpCompliance MODULE-COMPLIANCE 2291 STATUS current 2292 DESCRIPTION 2293 "The compliance statement for SNMP entities that implement 2294 the ROHC-RTP-MIB. 2296 Note that compliance with this compliance 2297 statement requires compliance with the 2298 rohcCompliance MODULE-COMPLIANCE statement of the 2299 ROHC-MIB and with the ifCompliance3 MODULE-COMPLIANCE 2300 statement of the IF-MIB (RFC2863)." 2301 MODULE -- this module 2302 MANDATORY-GROUPS { 2303 rohcRtpContextGroup 2304 } 2305 GROUP rohcRtpPacketSizesGroup 2306 DESCRIPTION 2307 "A compliant implementation does not have to implement 2308 the rohcRtpPacketSizesGroup." 2309 GROUP rohcRtpStatisticsGroup 2310 DESCRIPTION 2311 "A compliant implementation does not have to implement 2312 the rohcRtpStatisticsGroup." 2313 ::= { rohcRtpCompliances 1 } 2315 rohcRtpContextGroup OBJECT-GROUP 2316 OBJECTS { 2317 rohcRtpContextState, 2318 rohcRtpContextMode, 2319 rohcRtpContextAlwaysPad, 2320 rohcRtpContextLargePktsAllowed, 2321 rohcRtpContextVerifyPeriod 2322 } 2323 STATUS current 2324 DESCRIPTION 2325 "A collection of objects providing information about 2326 ROHC RTP compressors and decompressors." 2327 ::= { rohcRtpGroups 1 } 2329 rohcRtpPacketSizesGroup OBJECT-GROUP 2330 OBJECTS { 2331 rohcRtpContextSizesAllowed, 2332 rohcRtpContextSizesUsed, 2333 rohcRtpPacketSizePreferred, 2334 rohcRtpPacketSizeUsed, 2335 rohcRtpPacketSizeRestrictedType 2336 } 2337 STATUS current 2338 DESCRIPTION 2339 "A collection of objects providing information about 2340 allowed and used packet sizes at a ROHC RTP compressor." 2341 ::= { rohcRtpGroups 2 } 2343 rohcRtpStatisticsGroup OBJECT-GROUP 2344 OBJECTS { 2345 rohcRtpContextACKs, 2346 rohcRtpContextNACKs, 2347 rohcRtpContextSNACKs, 2348 rohcRtpContextNHPs, 2349 rohcRtpContextCSPs, 2350 rohcRtpContextCCPs, 2351 rohcRtpContextPktsLostPhysical, 2352 rohcRtpContextPktsLostPreLink 2353 } 2354 STATUS current 2355 DESCRIPTION 2356 "A collection of objects providing ROHC compressor and 2357 decompressor statistics." 2358 ::= { rohcRtpGroups 3 } 2360 END 2362 6. Security Considerations 2364 The managed objects defined by the ROHC-MIB module, the ROHC- 2365 UNCOMPRESSED-MIB module and the ROHC-RTP-MIB module do not have a 2366 MAX-ACCESS value of read-write and/or read-create except 2367 rohcInstanceContextStorageTime and rohcContextStorageTime, both of 2368 which have a MAX-ACCESS value of read-write. These objects determine 2369 how long context information is stored after its termination. 2370 Unauthorized access to these objects can have one of two negative 2371 effects. If they are set to a value lower than required, e.g. to 2372 zero, then context information about past contexts might get lost. 2373 If they are set to a very high value, then context information will 2374 not be deleted and memory consumption of the agent implementation 2375 might become very high. However, unauthorized access to these 2376 objects cannot cause harm to existing ROHC connections nor can it 2377 allow manipulation of running instances of ROHC in a malicious way. 2379 Another security issue is unauthorized access to readable objects in 2380 the MIB modules for getting information about existing communication 2381 sessions. It is thus important to control even GET and/or NOTIFY 2382 access to these objects and possibly to even encrypt the values of 2383 these objects when sending them over the network via SNMP. However, 2384 the only information that might be disclosed is the use of channels. 2385 Users and their addresses are not visible in the MIB. This 2386 information can only be mis-used in conjunction with the mis-use of 2387 further information. 2389 SNMP versions prior to SNMPv3 did not include adequate security. 2390 Even if the network itself is secure (for example by using IPSec), 2391 even then, there is no control as to who on the secure network is 2392 allowed to access and GET/SET (read/change/create/delete) the objects 2393 in this MIB module. 2395 It is RECOMMENDED that implementers consider the security features as 2396 provided by the SNMPv3 framework (see [RFC3410], section 8), 2397 including full support for the SNMPv3 cryptographic mechanisms (for 2398 authentication and privacy). 2400 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2401 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2402 enable cryptographic security. It is then a customer/operator 2403 responsibility to ensure that the SNMP entity giving access to an 2404 instance of this MIB module is properly configured to give access to 2405 the objects only to those principals (users) that have legitimate 2406 rights to indeed GET or SET (change/create/delete) them. 2408 7. Acknowledgements 2410 Many thanks to Lars-Erik Jonsson and Mark West for their guidance 2411 through the ROHC world and to Ghyslain Pelletier for explaining how 2412 the ROHC LLA profile works. Further thanks to Frank Strauss for his 2413 advice on tricky SMI issues. Special thanks to Mike Heard who acted 2414 as MIB doctor. He studied every tiny detail, raised a long list of 2415 issues and helped to significantly improve this document. 2417 8. Normative References 2419 [RFC3095] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H., 2420 Hannu, H., Jonsson, L., Hakenberg, R., Koren, T., Le, K., 2421 Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, 2422 T., Yoshimura, T. and H. Zheng, "RObust Header Compression 2423 (ROHC): Framework and four profiles: RTP, UDP, ESP, and 2424 uncompressed", RFC 3095, July 2001. 2426 [RFC3242] Jonsson, L., and G. Pelletier, "RObust Header Compression 2427 (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP", RFC 2428 3242, April 2002. 2430 [RFCXXXX] L. Jonsson, "RObust Header Compression (ROHC): Terminology 2431 and Channel Mapping Examples", RFC XXXX, YYYYmonth 2004, 2432 . 2434 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2435 Rose, M. and S. Waldbusser, "Structure of Management 2436 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2437 1999. 2439 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2440 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 2441 STD 58, RFC 2579, April 1999. 2443 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2444 Rose, M. and S. Waldbusser, "Conformance Statements for 2445 SMIv2", STD 58, RFC 2580, April 1999. 2447 [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture 2448 for Describing Simple Network Management Protocol (SNMP) 2449 Management Frameworks", STD 62, RFC 3411, December 2002. 2451 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2452 MIB", RFC 2863, June 2000. 2454 9. Informative References 2456 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2457 "Introduction and Applicability Statements for Internet- 2458 Standard Management Framework", RFC 3410, December 2002. 2460 10. Authors' Addresses 2462 Juergen Quittek 2463 NEC Europe Ltd. 2464 Network Laboratories 2465 Kurfuersten-Anlage 36 2466 69115 Heidelberg 2467 Germany 2469 Phone: +49 6221 90511-15 2470 EMail: quittek@netlab.nec.de 2472 Martin Stiemerling 2473 NEC Europe Ltd. 2474 Network Laboratories 2475 Kurfuersten-Anlage 36 2476 69115 Heidelberg 2477 Germany 2479 Phone: +49 6221 90511-13 2480 Email: stiemerling@netlab.nec.de 2482 Hannes Hartenstein 2483 University of Karlsruhe 2484 Computing Center and Institute of Telematics 2485 76128 Karlsruhe 2486 Germany 2488 Phone: +49 721 608 8104 2489 E-mail: hartenstein@rz.uni-karlsruhe.de 2491 11. IPR Notices 2493 The IETF takes no position regarding the validity or scope of any 2494 intellectual property or other rights that might be claimed to 2495 pertain to the implementation or use of the technology described in 2496 this document or the extent to which any license under such rights 2497 might or might not be available; neither does it represent that it 2498 has made any effort to identify any such rights. Information on the 2499 IETF's procedures with respect to rights in standards-track and 2500 standards-related documentation can be found in BCP-11. Copies of 2501 claims of rights made available for publication and any assurances of 2502 licenses to be made available, or the result of an attempt made to 2503 obtain a general license or permission for the use of such 2504 proprietary rights by implementors or users of this specification can 2505 be obtained from the IETF Secretariat. 2507 The IETF invites any interested party to bring to its attention any 2508 copyrights, patents or patent applications, or other proprietary 2509 rights which may cover technology that may be required to practice 2510 this standard. Please address the information to the IETF Executive 2511 Director. 2513 12. Full Copyright Statement 2515 Copyright (C) The Internet Society (2004). All Rights Reserved. 2517 This document and translations of it may be copied and furnished to 2518 others, and derivative works that comment on or otherwise explain it 2519 or assist in its implmentation may be prepared, copied, published and 2520 distributed, in whole or in part, without restriction of any kind, 2521 provided that the above copyright notice and this paragraph are 2522 included on all such copies and derivative works. However, this 2523 document itself may not be modified in any way, such as by removing 2524 the copyright notice or references to the Internet Society or other 2525 Internet organizations, except as needed for the purpose of 2526 developing Internet standards in which case the procedures for 2527 copyrights defined in the Internet Standards process must be 2528 followed, or as required to translate it into languages other than 2529 English. 2531 The limited permissions granted above are perpetual and will not be 2532 revoked by the Internet Society or its successors or assigns. 2534 This document and the information contained herein is provided on an 2535 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2536 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2537 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2538 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2539 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.