idnits 2.17.1 draft-quittek-rohc-mib-00.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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 11 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1430 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 (November 2001) is 8188 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) ** 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 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) Summary: 16 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft J. Quittek 2 Document: draft-quittek-rohc-mib-00.txt H. Hartenstein 3 Expires: May 2002 M. Stiemerling 4 NEC Europe Ltd. 5 November 2001 7 Definitions of Managed Objects for Robus 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 (2001). 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. 43 Table of Contents 45 1 Introduction ................................................. 2 46 2 The SNMP Management Framework ................................ 2 47 3 Overview ..................................................... 3 48 4 Structure of the MIB ......................................... 4 49 4.1 The rohcIfGroup ............................................ 4 50 4.2 The rohcHeaderGroup ........................................ 4 51 4.3 The rohcChannelGroup ....................................... 5 52 4.4 The rohcCompressorGroup .................................... 5 53 4.5 The rohcDecompressorGroup .................................. 5 54 4.6 The rohcStatisticsGroup .................................... 5 55 5 Definitions .................................................. 6 56 6 Security Considerations ...................................... 26 57 7 References ................................................... 27 58 8 Authors' Addresses ........................................... 28 59 9 Full Copyright Statement ..................................... 30 61 1. Introduction 63 This memo defines a portion of the Management Information Base (MIB) 64 for use with network management protocols in the Internet community. 65 In particular, it describes a set of managed objects that allow 66 monitoring of running instances of robust header compression. 68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 70 document are to be interpreted as described in RFC 2119 [RFC2119]. 72 2. The SNMP Management Framework 74 The SNMP Management Framework presently consists of five major 75 components: 77 o An overall architecture, described in RFC 2571 [RFC2571]. 79 o Mechanisms for describing and naming objects and events for the 80 purpose of management. The first version of this Structure of 81 Management Information (SMI) is called SMIv1 and described in 82 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 83 1215 [RFC1215]. The second version, called SMIv2, is described 84 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 85 STD 58, RFC 2580 [RFC2580]. 87 o Message protocols for transferring management information. The 88 first version of the SNMP message protocol is called SNMPv1 and 89 described in STD 15, RFC 1157 [RFC1157]. A second version of 90 the SNMP message protocol, which is not an Internet standards 91 track protocol, is called SNMPv2c and described in RFC 1901 92 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 93 message protocol is called SNMPv3 and described in RFC 1906 94 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 96 o Protocol operations for accessing management information. The 97 first set of protocol operations and associated PDU formats is 98 described in STD 15, RFC 1157 [RFC1157]. A second set of 99 protocol operations and associated PDU formats is described in 100 RFC 1905 [RFC1905]. 102 o A set of fundamental applications described in RFC 2573 103 [RFC2573] and the view-based access control mechanism described 104 in RFC 2575 [RFC2575]. 106 A more detailed introduction to the current SNMP Management Framework 107 can be found in RFC 2570 [RFC2570]. 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. Objects in the MIB are 111 defined using the mechanisms defined in the SMI. 113 This memo specifies a MIB module that is compliant to the SMIv2. A 114 MIB conforming to the SMIv1 can be produced through the appropriate 115 translations. The resulting translated MIB must be semantically 116 equivalent, except where objects or events are omitted because no 117 translation is possible (use of Counter64). Some machine readable 118 information in SMIv2 will be converted into textual descriptions in 119 SMIv1 during the translation process. However, this loss of machine 120 readable information is not considered to change the semantics of the 121 MIB. 123 3. Overview 125 This section describes the basic model of RObust Header Compression 126 (ROHC, [RFC3095]) used in developing the ROHC MIB module. 128 ROHC presents a framework for IP header compression that allows 129 flexible adjustment of compression efficiency versus robustness 130 against channel errors depending on the underlying channel 131 characteristics. 133 ROHC introduces header compressors/decompressors at the end-points 134 (interfaces) of (wireless) channels on which ROHC header-compressed 135 packets flow. ROHC exploits the temporal redundancy in successive 136 packet headers of a packet flow by storing non-changing fields of the 137 headers as well as reference values of predictably changing fields as 138 context information. When the context information for a packet flow 139 is also established at the decompressor, only delta-information and 140 unpredictably changing header fields have to be sent over the 141 channel. Since the context information will change over time, the 142 decompressor's information on the context has to be kept 'in sync'. 143 In order to update contexts at the decompressor, various header types 144 can be used to efficiently transmit the information needed for the 145 update. 147 ROHC specifies three modes of operation: i) unidirectional mode where 148 the decompressor does not give feedback to the compressor, ii) 149 bidirectional reliable mode, and iii) bidirectional optimistic mode. 150 The control mechanisms that determine what header types are allowed 151 to be sent or to be decompressed are modeled as state machines. 152 Detection of residual bit errors or damaged contexts at the 153 decompressor as well as repair strategies are based on Cyclic 154 Redundancy Checks (CRC) included in the compressed headers. 156 This document specifies the ROHC MIB module in order to provide means 157 for managing ROHC implementation via SNMP and within the IETF 158 management framework. The objects defined support configuration 159 management, fault management and performance monitoring. 161 For configuration management implementation parameters (Section 6.3. 162 of RFC 3095) and configuration parameters (including the ones 163 specified in 5.1.1 of RFC 3095) can be verified by using the ROHC 164 MIB. 166 For fault management compressor/decompressor state and mode can be 167 checked and the compressor context can be reinitialized. 169 For performance management a set of statistics is provided including 170 the number of flows that have used ROHC, the current and long term 171 compression ratio, the number of reinitializations and the number of 172 packets sent or received with different header types. 174 4. Structure of the MIB 176 This section presents the structure of the MIB. The objects are 177 arranged into the following groups: 179 o interfaces group (rohcIfGroup) 181 o header group (rohcHeaderGroup) 183 o channel group (rohcChannelGroup) 185 o compressor group (rohcCompressorGroup) 187 o decompressor group (rohcDecompressorGroup) 188 o statistics group (rohcStatisticsGroup) 190 4.1. The rohcIfGroup 192 The rohcIfGroup consists of a single table listing all interfaces of 193 the managed node, on which robust header compression is available. 194 Different interfaces might use different versions of ROHC. This table 195 provides information about the vendor and version number of the ROHC 196 implementation per interface and of its common properties and current 197 status. 199 4.2. The rohcHeaderGroup 201 The rohcHeaderGroup consists of a single table listing per interface 202 all header types supported by this instance of robust header 203 compression. 205 4.3. The rohcChannelGroup 207 The rohcChannelGroup consists of two tables, the rohcChannelTable and 208 the rohcProfileTable. 210 The rohcChannelTable lists all channels per interface with their 211 general properties described in Section 5.1.1. of RFC 3095. 212 Furthermore, it includes counters for incoming and outgoing flows per 213 channel, which used ROHC. 215 The rohcProfileTable lists the set of profiles supported by the 216 decompressor. The profiles are listed by their number as described in 217 Section 5.1.2. of RFC 3095. 219 4.4. The rohcCompressorGroup 221 The rohcCompressorGroup consists of three tables, the 222 rohcCompressorTable, the rohcPacketSizeTable, and the 223 rohcPayloadSizeTable. 225 The rohcCompressorTable lists and describes all compressor contexts 226 per channel. The description includes context ID, state, mode, and 227 profile of the compressor contex as well as the number of allowed 228 packet sizes and the number of used packet sizes. A special object 229 called rohcCompressorReinit allows the network manager to 230 reinitialize the compressor context by setting the object. 232 The rohcPacketSizeTable lists all allowed packet sizes per compressor 233 context. Used packet sizes are marked. This table reflects the 234 information contained in parameters PACKET_SIZES_ALLOWED and 235 PACKET_SIZES_USED, as defined in RFC 3095, Section 6.3.1. 237 The rohcPayloadSizeTable reflects the information contained in 238 parameter PAYLOAD_SIZES, as defined in RFC 3095, Section 6.3.1. 240 4.5. The rohcDecompressorGroup 242 The rohcDecompressorGroup consists of a single table listing and 243 describing all decompressor contexts. The description includes 244 context ID, state, mode, and profile of the decompressor contex as 245 well as the depth of reverse compression. 247 4.6. The rohcStatisticsGroup 249 The rohcStatisticsGroup consists of three tables, the 250 rohcOutPacketCounterTable, the rohcInPacketCounterTable, and the 251 rohcErrorTable. The first two tables contain counters per context and 252 per header type for incoming and outgoing packets, repectively. The 253 rohcErrorTable contains counters for different error types. 255 Furthermore, some elements of the rohcCompressorTable and the 256 rohcDecompressorTable belong to the rohcStatisticsGroup. They contain 257 compression ratio indicatiors for each compressor context, packet 258 counters per context, and reinitialization counters. 260 5. Definitions 262 ROHC-MIB DEFINITIONS ::= BEGIN 264 IMPORTS 265 MODULE-IDENTITY, OBJECT-TYPE, 266 Integer32, experimental 267 FROM SNMPv2-SMI 269 TEXTUAL-CONVENTION, TimeInterval, TruthValue 270 FROM SNMPv2-TC 272 MODULE-COMPLIANCE, OBJECT-GROUP 273 FROM SNMPv2-CONF 275 SnmpAdminString 276 FROM SNMP-FRAMEWORK-MIB 278 ifIndex 279 FROM IF-MIB; 281 rohcMIB MODULE-IDENTITY 282 LAST-UPDATED "200111130837Z" 283 ORGANIZATION "IETF Robust Header Compression Working Group" 284 CONTACT-INFO 285 "Juergen Quittek 286 NEC Europe Ltd. 288 Network Laboratories 289 Adenauerplatz 6 290 69221 Heidelberg 291 Germany 292 Tel: +49 6221 90511-15 293 E-mail: quittek@ccrle.nec.de" 294 DESCRIPTION 295 "This MIB module defines a set of objects that for 296 monitoring and configuring robust header compression." 297 ::= { experimental 55555 } 298 -- Number to be requested from IANA. 55555 is just a placeholder. 300 RohcChannelIndex ::= TEXTUAL-CONVENTION 301 STATUS current 302 DESCRIPTION 303 "An index identifying a channel." 304 SYNTAX Integer32 (1..2147483647) 306 -- 307 -- The groups defined within this MIB module: 308 -- 310 rohcObjects OBJECT IDENTIFIER ::= { rohcMIB 1 } 311 rohcConformance OBJECT IDENTIFIER ::= { rohcMIB 2 } 313 -- 314 -- Interfaces supporting ROHC 315 -- 316 -- This group define a table which lists all running instances 317 -- of robust header compression per interface at the managed node. 318 -- Even if a single instance serves more than one interface, 319 -- it is listed for each interface. 320 -- 322 rohcIfTable OBJECT-TYPE 323 SYNTAX SEQUENCE OF RohcIfEntry 324 MAX-ACCESS not-accessible 325 STATUS current 326 DESCRIPTION 327 "This table lists running instance of robust header compression." 328 ::= { rohcObjects 1 } 330 rohcIfEntry OBJECT-TYPE 331 SYNTAX RohcIfEntry 332 MAX-ACCESS not-accessible 333 STATUS current 334 DESCRIPTION 335 "An entry describing a particular running instance 336 of robust header compression." 337 INDEX { ifIndex } 338 ::= { rohcIfTable 1 } 340 RohcIfEntry ::= SEQUENCE { 341 rohcIfVendor OBJECT IDENTIFIER, 342 rohcIfVersion SnmpAdminString, 343 rohcIfDescr SnmpAdminString, 344 rohcIfClockRes TimeInterval, 345 rohcIfStatus INTEGER 346 } 348 rohcIfVendor OBJECT-TYPE 349 SYNTAX OBJECT IDENTIFIER 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "An object identifer which identifies the vendor who 354 provides the implementation of robust header description. 355 This object identifer SHALL point to the object identifier 356 directly below the enterprise object identifier {1 3 6 1 4 1} 357 allocated for the vendor. The value must be the object 358 identifier {0 0} if the vendor is not known." 359 ::= { rohcIfEntry 2 } 361 rohcIfVersion OBJECT-TYPE 362 SYNTAX SnmpAdminString (SIZE (0..32)) 363 MAX-ACCESS read-only 364 STATUS current 365 DESCRIPTION 366 "The version number of the implementation of robust header 367 compression. The zero-length string shall be used if the 368 implementation does not have a version number. 370 It is suggested that the version number consist of one or 371 more decimal numbers separated by dots, where the first 372 number is called the major version number." 373 ::= { rohcIfEntry 3 } 375 rohcIfDescr OBJECT-TYPE 376 SYNTAX SnmpAdminString 377 MAX-ACCESS read-only 378 STATUS current 379 DESCRIPTION 380 "A textual description of the implementation." 381 ::= { rohcIfEntry 4 } 383 rohcIfClockRes OBJECT-TYPE 384 SYNTAX TimeInterval 385 UNITS "centi-seconds" 386 MAX-ACCESS read-only 387 STATUS current 388 DESCRIPTION 389 "This object indicates the system clock resolution in 390 units of centi-seconds. A zero (0) value means that there 391 is no clock available. Please note, that RFC 3095 defines 392 the clock resolution to be defined in milliseconds." 393 ::= { rohcIfEntry 5 } 395 rohcIfStatus OBJECT-TYPE 396 SYNTAX INTEGER { 397 enabled(1), 398 disabled(2) 399 } 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "Status of the implementation of ROHC at this interface." 404 ::= { rohcIfEntry 6 } 406 -- 407 -- Supported Headers. 408 -- 409 -- This group define a table which lists all header types 410 -- supported by this instance of robust header compression. 411 -- 413 rohcHeaderTable OBJECT-TYPE 414 SYNTAX SEQUENCE OF RohcHeaderEntry 415 MAX-ACCESS not-accessible 416 STATUS current 417 DESCRIPTION 418 "This table lists supported header types." 419 ::= { rohcObjects 2 } 421 rohcHeaderEntry OBJECT-TYPE 422 SYNTAX RohcHeaderEntry 423 MAX-ACCESS not-accessible 424 STATUS current 425 DESCRIPTION 426 "An entry describing a particular supported header type ." 427 INDEX { ifIndex, rohcHeaderIndex } 428 ::= { rohcHeaderTable 1 } 430 RohcHeaderEntry ::= SEQUENCE { 431 rohcHeaderIndex Integer32, 432 rohcHeaderString SnmpAdminString, 433 rohcHeaderDescr SnmpAdminString 434 } 436 rohcHeaderIndex OBJECT-TYPE 437 SYNTAX Integer32 (1..2147483647) 438 MAX-ACCESS not-accessible 439 STATUS current 440 DESCRIPTION 441 "The locally arbitrary, but unique identifier associated 442 with this supported header type. 444 The value is expected to remain constant at least from one 445 re-initialization of the entity's network management system 446 to the next re-initialization." 447 ::= { rohcHeaderEntry 2} 449 rohcHeaderString OBJECT-TYPE 450 SYNTAX SnmpAdminString (SIZE (0..32)) 451 -- length of 32 sufficient? 452 MAX-ACCESS read-only 453 STATUS current 454 DESCRIPTION 455 "The name of the header type or at least a string uniquely 456 identifying the header type." 457 ::= { rohcHeaderEntry 3 } 459 rohcHeaderDescr OBJECT-TYPE 460 SYNTAX SnmpAdminString 461 MAX-ACCESS read-only 462 STATUS current 463 DESCRIPTION 464 "A textual description of the header type." 465 ::= { rohcHeaderEntry 4 } 467 -- 468 -- Channels 469 -- 470 -- This group defines a table listing all channels for which 471 -- robust header compression is activated, and a table listing 472 -- all supported profiles per channel 473 -- 475 rohcChannelObjects OBJECT IDENTIFIER ::= { rohcObjects 3 } 477 rohcChannelTable OBJECT-TYPE 478 SYNTAX SEQUENCE OF RohcChannelEntry 479 MAX-ACCESS not-accessible 480 STATUS current 481 DESCRIPTION 482 "This table lists and describes all used channels per interface." 483 ::= { rohcChannelObjects 1 } 485 rohcChannelEntry OBJECT-TYPE 486 SYNTAX RohcChannelEntry 487 MAX-ACCESS not-accessible 488 STATUS current 489 DESCRIPTION 490 "An entry describing a particular script. Every script that 491 is stored in non-volatile memory is required to appear in 492 this script table." 493 INDEX { ifIndex, rohcChannelIndex } 494 ::= { rohcChannelTable 1 } 496 RohcChannelEntry ::= SEQUENCE { 497 rohcChannelIndex RohcChannelIndex, 498 rohcChannelMaxCID Integer32, 499 rohcChannelLargeCIDs TruthValue, 500 rohcChannelFeedbackFor RohcChannelIndex, 501 rohcChannelMRRU Integer32, 502 rohcChannelCompressedFlows Counter32, 503 rohcChannelDecompressedFlows Counter32 504 } 506 rohcChannelIndex OBJECT-TYPE 507 SYNTAX RohcChannelIndex 508 MAX-ACCESS not-accessible 509 STATUS current 510 DESCRIPTION 511 "The locally arbitrary, but unique identifier associated 512 with this channel. 514 The value is expected to remain constant at least from one 515 re-initialization of the entity's network management system 516 to the next re-initialization." 517 ::= { rohcChannelEntry 2 } 519 rohcChannelMaxCID OBJECT-TYPE 520 SYNTAX Integer32 (1..2147483647) 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The highest context ID number to be used by the compressor 525 as defined in RFC 3095, Section 5.1.1. Note that this 526 parameter is not coupled to, but in effect further 527 constrained by, rohcChannelLargeCIDs." 528 ::= { rohcChannelEntry 3 } 530 rohcChannelLargeCIDs OBJECT-TYPE 531 SYNTAX TruthValue 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "Boolean, as defined by RFC 3095, Section 5.1.1: if false, 536 the short CID representation (0 bytes or 1 prefix byte, 537 covering CID 0 to 15) is used; if true, the embedded CID 538 representation (1 or 2 embedded CID bytes covering CID 0 539 to 16383) is used." 540 ::= { rohcChannelEntry 4 } 542 rohcChannelFeedbackFor OBJECT-TYPE 543 SYNTAX RohcChannelIndex 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "The index of another channel of this interface for which 548 the channel serves as feedback channel, see RFC 3095, 549 Section 5.1.1." 550 ::= { rohcChannelEntry 5 } 552 rohcChannelMRRU OBJECT-TYPE 553 SYNTAX Integer32 (1..2147483647) 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "Maximum reconstructed reception unit according to RFC 3095, 558 Section 5.1.1. This is the size of the largest 559 reconstructed unit in octets that the decompressor is 560 expected to reassemble from segments (see RFC 3095, Section 561 5.2.5). Note that this size includes the CRC. If MRRU is 562 negotiated to be 0, no segment headers are allowed on the 563 channel." 564 ::= { rohcChannelEntry 6 } 566 rohcChannelCompressedFlows OBJECT-TYPE 567 SYNTAX Counter32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "counter of outgoing flows having used ROHC on this channel." 572 ::= { rohcChannelEntry 7 } 574 rohcChannelDecompressedFlows OBJECT-TYPE 575 SYNTAX Counter32 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 "counter of incoming flows having used ROHC on this channel." 580 ::= { rohcChannelEntry 8 } 582 -- 583 -- Profile Table 584 -- 586 rohcProfileTable OBJECT-TYPE 587 SYNTAX SEQUENCE OF RohcProfileEntry 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "This table lists a set of nonnegative integers as defined 592 in RFC 3095, Section 5.1.1. Each integer indicates a 593 profile supported by the decompressor. The compressor 594 MUST NOT compress using a profile not in this list." 595 ::= { rohcChannelObjects 2 } 597 rohcProfileEntry OBJECT-TYPE 598 SYNTAX RohcProfileEntry 599 MAX-ACCESS not-accessible 600 STATUS current 601 DESCRIPTION 602 "An entry describing a particular profile supported by 603 the decompressor. " 604 INDEX { ifIndex, rohcChannelIndex, rohcProfile } 605 ::= { rohcProfileTable 1 } 607 RohcProfileEntry ::= SEQUENCE { 608 rohcProfile Integer32 609 } 611 rohcProfile OBJECT-TYPE 612 SYNTAX Integer32 (0..2147483647) 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "Identifier of a profile supported by the decompressor, 617 as defined in RFC 3095, Section 5.1.1." 618 ::= { rohcProfileEntry 3 } 620 -- 621 -- Compressor contexts 622 -- 623 -- This group defines three tables: 624 -- 1. The rohcCompressorTable lists all compressor contexts per channel 625 -- and interface. 626 -- 2. The rohcPacketSizeTable lists all allowed packet sizes per 627 -- compressor context, channel, and interface. Used packet sizes are 628 -- marked. 629 -- 3. The rohcPayloadSizeTable lists all payload sizes that can be 630 -- expected. 631 -- 633 rohcCompressorObjects OBJECT IDENTIFIER ::= { rohcObjects 4 } 635 rohcCompressorTable OBJECT-TYPE 636 SYNTAX SEQUENCE OF RohcCompressorEntry 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "This table lists and describes all compressor contexts 641 per channel and interface." 642 ::= { rohcCompressorObjects 1 } 644 rohcCompressorEntry OBJECT-TYPE 645 SYNTAX RohcCompressorEntry 646 MAX-ACCESS not-accessible 647 STATUS current 648 DESCRIPTION 649 "An entry describing a particular compressor context." 650 INDEX { ifIndex, rohcChannelIndex, rohcCompressorCID } 651 ::= { rohcCompressorTable 1 } 653 RohcCompressorEntry ::= SEQUENCE { 654 rohcCompressorCID Integer32, 655 rohcCompressorState INTEGER, 656 rohcCompressorMode INTEGER, 657 rohcCompressorProfile Integer32, 658 rohcCompressorReinit TruthValue, 659 rohcCompressorSizesAllowed Integer32, 660 rohcCompressorSizesUsed Integer32, 661 rohcCompressorTotalRatio Integer32, 662 rohcCompressorCurrentRatio Integer32, 663 rohcCompressorOutPackets Counter32, 664 rohcCompressorInACKs Counter32, 665 rohcCompressorInNACKs Counter32, 666 rohcCompressorInSNACKs Counter32 667 } 669 rohcCompressorCID OBJECT-TYPE 670 SYNTAX Integer32 (0..2147483647) 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "The context identifier (CID) of this compressor 675 context as defined in RFC 3095, Section 5.1.3." 676 ::= { rohcCompressorEntry 3 } 678 rohcCompressorState OBJECT-TYPE 679 SYNTAX INTEGER { 680 ir(1), 681 fo(2), 682 so(3) 683 } 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "State of the compressor context as defined in RFC 3095, 688 Section 4.3.1." 689 ::= { rohcCompressorEntry 4 } 691 rohcCompressorMode OBJECT-TYPE 692 SYNTAX INTEGER { 693 u(1), 694 o(2), 695 r(3) 696 } 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "Mode of the compressor context as defined in RFC 3095, 701 Section 4.4." 702 ::= { rohcCompressorEntry 5 } 704 rohcCompressorProfile OBJECT-TYPE 705 SYNTAX Integer32 (0..2147483647) 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "Identifier of the profile for this compressor context. 710 The profile is identified by its index in the 711 rohcProfileTable for this channel." 712 ::= { rohcCompressorEntry 6 } 714 rohcCompressorReinit OBJECT-TYPE 715 SYNTAX TruthValue 716 MAX-ACCESS read-write 717 STATUS current 718 DESCRIPTION 719 "By setting this object to true(1), a context 720 reinitialization is triggered. 722 When retrieved, the value of this object will 723 always be false(2)." 724 ::= { rohcCompressorEntry 7 } 726 rohcCompressorSizesAllowed OBJECT-TYPE 727 SYNTAX Integer32 (1..2147483647) 728 MAX-ACCESS read-only 729 STATUS current 730 DESCRIPTION 731 "Number of different packet sizes the compressor 732 may use, as defined in RFC 3095, Section 6.3.1." 733 ::= { rohcCompressorEntry 8 } 735 rohcCompressorSizesUsed OBJECT-TYPE 736 SYNTAX Integer32 (1..2147483647) 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "Number of different packet sizes the compressor 741 uses, as defined in RFC 3095, Section 6.3.1." 742 ::= { rohcCompressorEntry 9 } 744 -- The remaining elements of the rohcCompressorEntry defined 745 -- below belong to the statistics group. 747 rohcCompressorTotalRatio OBJECT-TYPE 748 SYNTAX Integer32 (0..1000) 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "This object indicates the compression ratio so far of the 753 entire flow mapped to this compressor context. The value 754 is defined as 1000 * bytes(compressed) / bytes(original) 755 rounded to the next integer value." 756 ::= { rohcCompressorEntry 10 } 758 rohcCompressorCurrentRatio OBJECT-TYPE 759 SYNTAX Integer32 (0..1000) 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "This object indicates the compression ratio of the 764 flow mapped to this compressor context concerning the 765 last 16 packets or concerning all packets if they are 766 less than 16, so far. The value is defined as 767 1000 * bytes(compressed) / bytes(original) rounded to 768 the next integer value." 769 ::= { rohcCompressorEntry 11 } 771 rohcCompressorOutPackets OBJECT-TYPE 772 SYNTAX Counter32 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "The number of all packets sent so far in this 777 compressor context." 778 ::= { rohcCompressorEntry 12 } 780 rohcCompressorInACKs OBJECT-TYPE 781 SYNTAX Counter32 782 MAX-ACCESS read-only 783 STATUS current 784 DESCRIPTION 785 "The number of all received positive feedbacks (ACK) 786 from the decompressor in this compressor context, 787 as defined by RFC 3095, Section 5.2.1." 789 ::= { rohcCompressorEntry 13 } 791 rohcCompressorInNACKs OBJECT-TYPE 792 SYNTAX Counter32 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The number of all received dynamic negative feedbacks 797 (NACK) from the decompressor in this compressor 798 context, as defined by RFC 3095, Section 5.2.1." 799 ::= { rohcCompressorEntry 14 } 801 rohcCompressorInSNACKs OBJECT-TYPE 802 SYNTAX Counter32 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "The number of all received static negative feedbacks 807 (STATIC-NACK) from the decompressor in this compressor 808 context, as defined by RFC 3095, Section 5.2.1." 809 ::= { rohcCompressorEntry 15 } 811 -- 812 -- Packet Sizes Table 813 -- 815 rohcPacketSizeTable OBJECT-TYPE 816 SYNTAX SEQUENCE OF RohcPacketSizeEntry 817 MAX-ACCESS not-accessible 818 STATUS current 819 DESCRIPTION 820 "This table lists all allowed packet sizes per comprssor 821 context, channel, and interface. Used packet sizes are 822 marked." 823 ::= { rohcCompressorObjects 2 } 825 rohcPacketSizeEntry OBJECT-TYPE 826 SYNTAX RohcPacketSizeEntry 827 MAX-ACCESS not-accessible 828 STATUS current 829 DESCRIPTION 830 "An entry of a particular allowed packet size." 831 INDEX { ifIndex, rohcChannelIndex, rohcCompressorCID, rohcPacketSize } 832 ::= { rohcPacketSizeTable 1 } 834 RohcPacketSizeEntry ::= SEQUENCE { 835 rohcPacketSize Integer32, 836 rohcPacketSizeUsed TruthValue 837 } 838 rohcPacketSize OBJECT-TYPE 839 SYNTAX Integer32 (0..2147483647) 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "A packet size used as index." 844 ::= { rohcPacketSizeEntry 4 } 846 rohcPacketSizeUsed OBJECT-TYPE 847 SYNTAX TruthValue 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION 851 "When retrieved, this object will have the value 852 true(1) if the packet size is used by the compressor 853 context. Otherwise its value will be false(2), see 854 RFC 3095, Section 6.3.1." 855 ::= { rohcPacketSizeEntry 5 } 857 -- 858 -- Payload Sizes Table 859 -- 861 rohcPayloadSizeTable OBJECT-TYPE 862 SYNTAX SEQUENCE OF RohcPayloadSizeEntry 863 MAX-ACCESS not-accessible 864 STATUS current 865 DESCRIPTION 866 "This table lists all payload sizes that can be expected 867 as described in RFC 3095, Section 6.3.1." 868 ::= { rohcCompressorObjects 3 } 870 rohcPayloadSizeEntry OBJECT-TYPE 871 SYNTAX RohcPayloadSizeEntry 872 MAX-ACCESS not-accessible 873 STATUS current 874 DESCRIPTION 875 "An entry of a particular payload size." 876 INDEX { ifIndex, rohcChannelIndex, rohcCompressorCID, rohcPayloadSize } 877 ::= { rohcPayloadSizeTable 1 } 879 RohcPayloadSizeEntry ::= SEQUENCE { 880 rohcPayloadSize Integer32 881 } 883 rohcPayloadSize OBJECT-TYPE 884 SYNTAX Integer32 (0..2147483647) 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "A payload size used as index." 889 ::= { rohcPayloadSizeEntry 4 } 891 -- 892 -- Decompressor contexts 893 -- 894 -- This group defines a table which lists all decompressor contexts 895 -- per channel and interface. 896 -- 898 rohcDecompressorTable OBJECT-TYPE 899 SYNTAX SEQUENCE OF RohcDecompressorEntry 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION 903 "This table lists and describes all decompressor contexts 904 per channel and interface." 905 ::= { rohcObjects 5 } 907 rohcDecompressorEntry OBJECT-TYPE 908 SYNTAX RohcDecompressorEntry 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "An entry describing a particular decompressor context." 913 INDEX { ifIndex, rohcChannelIndex, rohcDecompressorCID } 914 ::= { rohcDecompressorTable 1 } 916 RohcDecompressorEntry ::= SEQUENCE { 917 rohcDecompressorCID Integer32, 918 rohcDecompressorState INTEGER, 919 rohcDecompressorMode INTEGER, 920 rohcDecompressorProfile Integer32, 921 rohcDecompressorDepth Integer32, 922 rohcDecompressorInPackets Counter32, 923 rohcDecompressorOutACKs Counter32, 924 rohcDecompressorOutNACKs Counter32, 925 rohcDecompressorOutSNACKs Counter32 926 } 928 rohcDecompressorCID OBJECT-TYPE 929 SYNTAX Integer32 (0..2147483647) 930 MAX-ACCESS not-accessible 931 STATUS current 932 DESCRIPTION 933 "The context identifier (CID) of this decompressor 934 context as defined in RFC 3095, Section 5.1.3." 935 ::= { rohcDecompressorEntry 3 } 937 rohcDecompressorState OBJECT-TYPE 938 SYNTAX INTEGER { 939 ir(1), 940 fo(2), 941 so(3) 942 } 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "State of the decompressor context as defined in RFC 3095, 947 Section 4.3.1." 948 ::= { rohcDecompressorEntry 4 } 950 rohcDecompressorMode OBJECT-TYPE 951 SYNTAX INTEGER { 952 u(1), 953 o(2), 954 r(3) 955 } 956 MAX-ACCESS read-only 957 STATUS current 958 DESCRIPTION 959 "Mode of the decompressor context as defined in RFC 3095, 960 Section 4.4." 961 ::= { rohcDecompressorEntry 5 } 963 rohcDecompressorProfile OBJECT-TYPE 964 SYNTAX Integer32 (0..2147483647) 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "Identifier of the profile for this decompressor context. 969 The profile is identified by its index in the 970 rohcProfileTable for this channel." 971 ::= { rohcDecompressorEntry 6 } 973 rohcDecompressorDepth OBJECT-TYPE 974 SYNTAX Integer32 (0..2147483647) 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "This object indicates whether reverse decompression 979 as described in RFC 3095, Section 6.1 should be used or 980 not, and if used, to what extent. For more details see 981 RFC 3095, Section 6.3.2." 982 ::= { rohcDecompressorEntry 7 } 984 -- The remaining elements of the rohcDecompressorEntry defined 985 -- below belong to the statistics group. 987 rohcDecompressorInPackets OBJECT-TYPE 988 SYNTAX Counter32 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The number of all packets sent so far in this 993 decompressor context." 994 ::= { rohcDecompressorEntry 8 } 996 rohcDecompressorOutACKs OBJECT-TYPE 997 SYNTAX Counter32 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The number of all sent positive feedbacks (ACK) 1002 from this decompressor context, 1003 as defined by RFC 3095, Section 5.2.1." 1004 ::= { rohcDecompressorEntry 9 } 1006 rohcDecompressorOutNACKs OBJECT-TYPE 1007 SYNTAX Counter32 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "The number of all sent dynamic negative feedbacks 1012 (NACK) from this decompressor 1013 context, as defined by RFC 3095, Section 5.2.1." 1014 ::= { rohcDecompressorEntry 10 } 1016 rohcDecompressorOutSNACKs OBJECT-TYPE 1017 SYNTAX Counter32 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "The number of all rsent static negative feedbacks 1022 (STATIC-NACK) from the decompressor 1023 context, as defined by RFC 3095, Section 5.2.1." 1024 ::= { rohcDecompressorEntry 11 } 1026 -- 1027 -- Statistics Group 1028 -- 1029 -- This group consists of two tables providing packet statistis 1030 -- information and some statisitics related elements of the compressors 1031 -- table and the decompressor table. 1032 -- 1034 rohcStatisticsObjects OBJECT IDENTIFIER ::= { rohcObjects 6 } 1036 -- 1037 -- Sent Packet Counter Table 1038 -- 1040 rohcOutPacketCounterTable OBJECT-TYPE 1041 SYNTAX SEQUENCE OF RohcOutPacketCounterEntry 1042 MAX-ACCESS not-accessible 1043 STATUS current 1044 DESCRIPTION 1045 "This table lists packet counters per header type, 1046 compressor context, channel and interface." 1047 ::= { rohcStatisticsObjects 1 } 1049 rohcOutPacketCounterEntry OBJECT-TYPE 1050 SYNTAX RohcOutPacketCounterEntry 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "An entry of a particular sent packet counter." 1055 INDEX { ifIndex, rohcChannelIndex, rohcCompressorCID, rohcHeaderIndex } 1056 ::= { rohcOutPacketCounterTable 1 } 1058 RohcOutPacketCounterEntry ::= SEQUENCE { 1059 rohcOutPacketCounter Counter32 1060 } 1062 rohcOutPacketCounter OBJECT-TYPE 1063 SYNTAX Counter32 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "A counter for sent packets of a particular header type." 1068 ::= { rohcOutPacketCounterEntry 5 } 1070 -- 1071 -- Received Packet Counter Table 1072 -- 1074 rohcInPacketCounterTable OBJECT-TYPE 1075 SYNTAX SEQUENCE OF RohcInPacketCounterEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "This table lists received packet counters per 1080 header type, compressor context, channel and 1081 interface." 1082 ::= { rohcStatisticsObjects 2 } 1084 rohcInPacketCounterEntry OBJECT-TYPE 1085 SYNTAX RohcInPacketCounterEntry 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "An entry of a particular received packet counter." 1090 INDEX { ifIndex, rohcChannelIndex, rohcDecompressorCID, rohcHeaderIndex } 1091 ::= { rohcInPacketCounterTable 1 } 1093 RohcInPacketCounterEntry ::= SEQUENCE { 1094 rohcInPacketCounter Counter32 1095 } 1097 rohcInPacketCounter OBJECT-TYPE 1098 SYNTAX Counter32 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "A counter for received packets of a particular header type." 1103 ::= { rohcInPacketCounterEntry 5 } 1105 -- 1106 -- CRC Error Counter Table 1107 -- 1109 rohcErrorTable OBJECT-TYPE 1110 SYNTAX SEQUENCE OF RohcErrorEntry 1111 MAX-ACCESS not-accessible 1112 STATUS current 1113 DESCRIPTION 1114 "This table lists error counters per error type, 1115 compressor context, channel and interface. Since 1116 error types are not uniquely defined in RFC 3095, 1117 Each error type contains next to the error counter 1118 a textual description of the type." 1119 ::= { rohcStatisticsObjects 3 } 1121 rohcErrorEntry OBJECT-TYPE 1122 SYNTAX RohcErrorEntry 1123 MAX-ACCESS not-accessible 1124 STATUS current 1125 DESCRIPTION 1126 "An entry of a particular received packet counter." 1127 INDEX { ifIndex, rohcChannelIndex, rohcDecompressorCID, rohcErrorIndex } 1128 ::= { rohcErrorTable 1 } 1130 RohcErrorEntry ::= SEQUENCE { 1131 rohcErrorIndex Integer32, 1132 rohcErrorDescr SnmpAdminString, 1133 rohcErrorCounter Counter32 1134 } 1136 rohcErrorIndex OBJECT-TYPE 1137 SYNTAX Integer32 (1..2147483647) 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "The locally arbitrary, but unique identifier associated 1142 with this error type. 1144 The value is expected to remain constant at least from one 1145 re-initialization of the entity's network management system 1146 to the next re-initialization." 1147 ::= { rohcErrorEntry 4 } 1149 rohcErrorDescr OBJECT-TYPE 1150 SYNTAX SnmpAdminString 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "A textual description of the error type." 1155 ::= { rohcErrorEntry 5 } 1157 rohcErrorCounter OBJECT-TYPE 1158 SYNTAX Counter32 1159 MAX-ACCESS read-only 1160 STATUS current 1161 DESCRIPTION 1162 "A counter for occurrences of this error type." 1163 ::= { rohcErrorEntry 6 } 1165 -- 1166 -- conformance information 1167 -- 1169 rohcCompliances OBJECT IDENTIFIER ::= { rohcConformance 1 } 1170 rohcGroups OBJECT IDENTIFIER ::= { rohcConformance 2 } 1172 -- 1173 -- compliance statements 1174 -- 1176 rohcCompliance MODULE-COMPLIANCE 1177 STATUS current 1178 DESCRIPTION 1179 "The compliance statement for SNMP entities which implement 1180 the ROHC MIB." 1181 MODULE -- this module 1182 MANDATORY-GROUPS { 1183 rohcIfGroup, rohcHeaderGroup, rohcChannelGroup, 1184 rohcCompressorGroup, rohcDecompressorGroup 1186 } 1187 GROUP rohcStatisticsGroup 1188 DESCRIPTION 1189 "A compliant implementation does not have to implement 1190 the rohcStatisticsGroup." 1191 OBJECT rohcCompressorReinit 1192 MIN-ACCESS not-accessible 1193 DESCRIPTION 1194 "A compliant implementation does not have to support 1195 re-initialization of contexts initiated via this SNMP." 1196 ::= { rohcCompliances 1 } 1198 rohcIfGroup OBJECT-GROUP 1199 OBJECTS { 1200 rohcIfVendor, 1201 rohcIfVersion, 1202 rohcIfDescr, 1203 rohcIfClockRes, 1204 rohcIfStatus 1205 } 1206 STATUS current 1207 DESCRIPTION 1208 "A collection of objects providing information about the 1209 network interfaces supporting ROHC." 1210 ::= { rohcGroups 1 } 1212 rohcHeaderGroup OBJECT-GROUP 1213 OBJECTS { 1214 rohcHeaderString, 1215 rohcHeaderDescr 1216 } 1217 STATUS current 1218 DESCRIPTION 1219 "A collection of objects providing information about 1220 supported ROHC headers." 1221 ::= { rohcGroups 2 } 1223 rohcChannelGroup OBJECT-GROUP 1224 OBJECTS { 1225 rohcChannelMaxCID, 1226 rohcChannelLargeCIDs, 1227 rohcChannelFeedbackFor, 1228 rohcChannelMRRU, 1229 rohcChannelCompressedFlows, 1230 rohcChannelDecompressedFlows, 1231 rohcProfile 1232 } 1233 STATUS current 1234 DESCRIPTION 1235 "A collection of objects providing information about 1236 supported ROHC headers." 1237 ::= { rohcGroups 3 } 1239 rohcCompressorGroup OBJECT-GROUP 1240 OBJECTS { 1241 rohcCompressorState, 1242 rohcCompressorMode, 1243 rohcCompressorProfile, 1244 rohcCompressorReinit, 1245 rohcCompressorSizesAllowed, 1246 rohcCompressorSizesUsed, 1247 rohcPacketSizeUsed, 1248 rohcPayloadSize 1249 } 1250 STATUS current 1251 DESCRIPTION 1252 "A collection of objects providing information about 1253 supported ROHC headers." 1254 ::= { rohcGroups 4 } 1256 rohcDecompressorGroup OBJECT-GROUP 1257 OBJECTS { 1258 rohcDecompressorState, 1259 rohcDecompressorMode, 1260 rohcDecompressorProfile, 1261 rohcDecompressorDepth 1262 } 1263 STATUS current 1264 DESCRIPTION 1265 "A collection of objects providing information about 1266 supported ROHC headers." 1267 ::= { rohcGroups 6 } 1269 rohcStatisticsGroup OBJECT-GROUP 1270 OBJECTS { 1271 rohcCompressorTotalRatio, 1272 rohcCompressorCurrentRatio, 1273 rohcCompressorOutPackets, 1274 rohcCompressorInACKs, 1275 rohcCompressorInNACKs, 1276 rohcCompressorInSNACKs, 1277 rohcDecompressorInPackets, 1278 rohcDecompressorOutACKs, 1279 rohcDecompressorOutNACKs, 1280 rohcDecompressorOutSNACKs, 1281 rohcOutPacketCounter, 1282 rohcInPacketCounter, 1283 rohcErrorDescr, 1284 rohcErrorCounter 1285 } 1286 STATUS current 1287 DESCRIPTION 1288 "A collection of objects providing information about 1289 supported ROHC headers." 1290 ::= { rohcGroups 7 } 1292 END 1294 6. Security Considerations 1296 The managed objects defined by the ROHC MIB are read-only with just 1297 one exception, the rohcCompressorReinit object. Therefore, 1298 unauthorized users getting access to the MIB via SNMP cannot cause 1299 harm to existing ROHC connections nor can they manipulate running 1300 instances of ROHC in a malicious way. The only effect they could 1301 achieve is reinitializing compressor contexts unnecessarily and 1302 thereby downgrading the performance. 1304 Another security issue is mis-use of he MIB for getting information 1305 about existing communication sessions. However, the only information 1306 that might be disclosed is the use of channels. Users and their 1307 addresses are not visible in the MIB. This information can only be 1308 mis-used in conjunction with the mis-use of further information. 1310 Although, the security risks arising from the ROHC MIB are not 1311 considered to be high, it is recommended for implementors and 1312 operators to apply the means for security offered by SNMPv3, 1313 particularly encryption of communication and the User-based Security 1314 Model described in [RFC2574]. 1316 7. References 1318 [RFC3095] Bormann, C., et al. "An RObust Header Compression (ROHC): 1319 Framework and four profiles: RTP, UDP, ESP, and uncompressed 1320 ", RFC 3095, July 2001. 1322 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1323 for Describing SNMP Management Frameworks", RFC 2571, April 1324 1999. 1326 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1327 of Management Information for TCP/IP-based Internets", STD 1328 16, RFC 1155, May 1990. 1330 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1331 16, RFC 1212, March 1991. 1333 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1334 SNMP", RFC 1215, March 1991. 1336 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1337 Rose, M., and S. Waldbusser, "Structure of Management 1338 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1339 1999. 1341 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1342 Rose, M., and S. Waldbusser, "Textual Conventions for 1343 SMIv2", STD 58, RFC 2579, April 1999. 1345 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1346 Rose, M., and S. Waldbusser, "Conformance Statements for 1347 SMIv2", STD 58, RFC 2580, April 1999. 1349 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1350 Network Management Protocol", STD 15, RFC 1157, May 1990. 1352 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1353 "Introduction to Community-based SNMPv2", RFC 1901, January 1354 1996. 1356 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1357 "Transport Mappings for Version 2 of the Simple Network 1358 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1360 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1361 Processing and Dispatching for the Simple Network Management 1362 Protocol (SNMP)", RFC 2572, April 1999. 1364 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1365 (USM) for version 3 of the Simple Network Management 1366 Protocol (SNMPv3)", RFC 2574, April 1999. 1368 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1369 "Protocol Operations for Version 2 of the Simple Network 1370 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1372 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1373 RFC 2573, April 1999. 1375 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1376 Access Control Model (VACM) for the Simple Network 1377 Management Protocol (SNMP)", RFC 2575, April 1999. 1379 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1380 "Introduction to Version 3 of the Internet-standard Network 1381 Management Framework", RFC 2570, April 1999. 1383 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1384 Requirement Levels", RFC 2119, March 1997. 1386 8. Authors' Addresses 1388 Juergen Quittek 1389 NEC Europe Ltd. 1390 Network Laboratories 1391 Adenauerplatz 6 1392 69115 Heidelberg 1393 Germany 1395 Phone: +49 6221 90511-15 1396 EMail: quittek@ccrle.nec.de 1398 Hannes Hartenstein 1399 NEC Europe Ltd. 1400 Network Laboratories 1401 Adenauerplatz 6 1402 69115 Heidelberg 1403 Germany 1405 Phone: +49 6221 13708-14 1406 Email: hannes.hartenstein@ccrle.nec.de 1408 Martin Stiemerling 1409 NEC Europe Ltd. 1410 Network Laboratories 1411 Adenauerplatz 6 1412 69115 Heidelberg 1413 Germany 1415 Phone: +49 6221 90511-13 1416 Email: stiemerling@ccrle.nec.de 1418 9. Full Copyright Statement 1420 Copyright (C) The Internet Society (2001). All Rights Reserved. 1422 This document and translations of it may be copied and furnished to 1423 others, and derivative works that comment on or otherwise explain it 1424 or assist in its implementation may be prepared, copied, published 1425 and distributed, in whole or in part, without restriction of any 1426 kind, provided that the above copyright notice and this paragraph are 1427 included on all such copies and derivative works. However, this 1428 document itself may not be modified in any way, such as by removing 1429 the copyright notice or references to the Internet Society or other 1430 Internet organizations, except as needed for the purpose of 1431 developing Internet standards in which case the procedures for 1432 copyrights defined in the Internet Standards process must be 1433 followed, or as required to translate it into languages other than 1434 English. 1436 The limited permissions granted above are perpetual and will not be 1437 revoked by the Internet Society or its successors or assigns. 1439 This document and the information contained herein is provided on an 1440 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1441 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1442 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1443 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1444 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.