idnits 2.17.1 draft-ietf-ipcdn-cable-gateway-qos-mib-00.txt: -(823): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(827): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(832): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 10 instances of lines with non-ascii characters in the document. == 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 an Authors' Addresses Section. ** The abstract seems to contain references ([5], [6], [7]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 285 has weird spacing: '...numbers assig...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (June 2003) is 7620 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 section? '1' on line 19 looks like a reference -- Missing reference section? '5' on line 51 looks like a reference -- Missing reference section? '6' on line 51 looks like a reference -- Missing reference section? '7' on line 94 looks like a reference -- Missing reference section? '2' on line 59 looks like a reference -- Missing reference section? '12' on line 86 looks like a reference -- Missing reference section? '8' on line 94 looks like a reference -- Missing reference section? '9' on line 94 looks like a reference -- Missing reference section? '21' on line 100 looks like a reference -- Missing reference section? '22' on line 183 looks like a reference -- Missing reference section? '23' on line 115 looks like a reference -- Missing reference section? '24' on line 116 looks like a reference -- Missing reference section? '3' on line 715 looks like a reference -- Missing reference section? 'RFC3410' on line 738 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft A. Bhagwat 3 draft-ietf-ipcdn-cable-gateway-qos-mib-00.txt E. Cardona 4 Expires: December 2003 K. Luehrs 5 CableLabs 7 D. Jones 8 YAS BBV 10 June 2003 12 Cable Gateway Quality of Service (QoS) Management Information Base 13 for CableHome compliant Residential Gateways 15 Status of this Memo 17 This document is an Internet-Draft and is subject to all provisions 18 of Section 10 of RFC2026 [1]. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 Copyright Notice 38 Copyright (C) The Internet Society (2003). All Rights Reserved. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in the Internet community. 45 In particular, it defines a basic set of managed objects for SNMP- 46 based management for prioritized Quality of Service functionality 47 within a LAN, between a CableHome residential gateway device and 48 CableHome compliant LAN host devices. 50 This memo specifies a MIB module in a manner that is compliant to the 51 SNMP SMIv2 [5][6][7]. The set of objects is consistent with the SNMP 52 framework and existing SNMP standards. 54 Conventions used in this document 56 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 57 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 58 document are to be interpreted as described in RFC-2119 [2]. 60 Table of Contents 62 1. The Internet-Standard Management Framework.....................2 63 2. Glossary.......................................................3 64 2.1 CATV.......................................................3 65 2.2 CableHome Residential Gateway..............................3 66 2.3 Portal Services............................................3 67 2.4 Boundary Point (BP)........................................3 68 2.5 Application Identifiers....................................3 69 3. Overview.......................................................4 70 3.1 Structure of the MIB.......................................4 71 3.2 Management Requirements....................................5 72 4. MIB Definitions................................................5 73 5. Acknowlegements...............................................15 74 6. Formal Syntax.................................................16 75 7. Security Considerations.......................................16 76 8. Normative References..........................................16 77 9. Informative References........................................18 78 10. Intellectual Property........................................18 79 11. Author�s Addresses...........................................19 80 12. Full Copyright Statement.....................................20 82 1. The Internet-Standard Management Framework 84 For a detailed overview of the documents that describe the current 85 Internet-Standard Management Framework, please refer to section 7 of 86 RFC 3410 [12]. 88 Managed objects are accessed via a virtual information store, termed 89 the Management Information Base or MIB. MIB objects are generally 90 accessed through the Simple Network Management Protocol (SNMP). 91 Objects in the MIB are defined using the mechanisms defined in the 92 Structure of Management Information (SMI). This memo specifies a MIB 93 module that is compliant to the SMIv2, which is described in STD 58, 94 RFC 2578 [7], STD 58, RFC 2579 [8] and STD 58, RFC 2580 [9]. 96 2. Glossary 98 The terms in this document are derived either from normal cable 99 system usage, from normal residential gateway operation, or from the 100 documents associated with the CableHome Specifications [21] & [22]. 102 2.1 CATV 104 Originally "Community Antenna Television", now used to refer to any 105 cable or hybrid fiber and cable system used to deliver video signals 106 to a community. 108 2.2 CableHome Residential Gateway 110 A CableHome Residential gateway passes data traffic between the cable 111 operator's broadband data network (the Wide Area Network, WAN) and 112 the Local Area Network (LAN) in the cable data service subscriber's 113 residence or business. In addition to passing traffic between the WAN 114 and LAN, the CableHome Residential Gateway provides several services 115 including a DHCP client and a DHCP server (RFC2131) [23], a TFTP 116 server (RFC1350) [24], management services as enabled by 117 SNMPv1/v2c/v3 agent compliant with the RFCs listed in Section 1, and 118 security services including stateful packet inspection firewall 119 functionality and software code image verification using techniques. 121 2.3 Portal Services 123 A logical element aggregating the set of CableHome-specified 124 functionality in a CableHome compliant cable gateway device. 126 2.4 Boundary Point (BP) 127 A logical element aggregating the set of CableHome-specified 128 functionality in a CableHome compliant LAN host device (LAN IP 129 Device). 131 2.5 Application Identifiers 132 The port number assigned by the Internet Assigned Numbers Authority 133 (IANA) to an application, used by CableHome-specified elements to 134 identify an application. 136 3. Overview 138 This MIB entity supports basic traffic prioritization and queuing for 139 CableHome compliant devices. The MIB is derived from the CableHome 140 1.1 specification [22]. Support for traffic prioritization and 141 queuing is provided through four tables. These tables and their use 142 is summarized below and described in detail in the CableHome 1.1 143 specification [22]. 145 Applications running on CableHome compliant devices are identified 146 with their IANA-assigned UDP/TCP port number. Service providers have 147 the ability to configure the priority for any application by 148 associating a priority number with the port number in a table 149 implemented in the cable gateway device (Application Priority Master 150 Table). When CableHome compliant LAN host devices acquire a network 151 address lease, they communicate to the cable gateway device the list 152 of applications implemented on the LAN host. This information is 153 recorded in two other tables in the cable gateway device (BP 154 Application Priority Table and Destination Priority Table). Portal 155 Services functions refer to the Application Priority Master Table and 156 reply to the LAN host device(s) with the priority assigned to their 157 applications. 159 The cable gateway device maintains a queue for each LAN interface, 160 and each interface supports a particular number of priority levels. A 161 fourth table, the PS Interface Attributes Table, maintains this 162 information. 164 3.1 Structure of the MIB 166 This MIB entity contains one group: 168 The cabhPriorityQosGroup group contains the mechanisms needed for 169 CableHome compliant cable gateway devices and LAN hosts to identify 170 and communicate applications needing prioritized queuing and media 171 access. The cabhPriortyQosGroup contains the following tables: 173 cabhPriorityQosMasterTable 174 Allows the service provider to provision the residential gateway with 175 a list of supported applications and a priority value for each. The 176 Portal Services refers to this table when acting as a proxy for the 177 service provider, to provide application priorities to Boundary Point 178 elements. 180 cabhPriorityQosBpTable 181 Contains the list of application identifiers for each BP element in 182 the LAN. These values are acquired by the PS during the BP Discovery 183 process as described in [22]. 185 cabhPriorityQosBpDestTable 186 Contains a list of destination IP addresses for each BP, each of 187 which can be provisioned for a special priority for a specified 188 application. Applications are identified by their IANA-assigned port 189 number. 191 cabhPriorityQosPsIfAttribTable 192 Identifies the number of queues and the number of media access 193 priorities for each LAN interface. LAN interfaces are identified by 194 their ifIndex. 196 3.2 Management Requirements 198 In addition to the explicit requirements in this specification, the 199 Cable Gateway MUST support all applicable CableHome and IETF 200 requirements and MIB objects. 202 4. MIB Definitions 204 CABH-IETF-QOS-MIB DEFINITIONS ::= BEGIN 206 IMPORTS 207 MODULE-IDENTITY, 208 OBJECT-TYPE, 209 Unsigned32, 210 mib-2 211 FROM SNMPv2-SMI 213 TimeStamp, 214 TruthValue, 215 RowStatus FROM SNMPv2-TC 217 OBJECT-GROUP, 218 MODULE-COMPLIANCE FROM SNMPv2-CONF 220 InetPortNumber, 221 InetAddressType, 222 InetAddress FROM INET-ADDRESS-MIB 224 ifIndex FROM IF-MIB; 226 cabhQosMib MODULE-IDENTITY 227 LAST-UPDATED "200306210000Z" -- Jun 21, 2003 228 ORGANIZATION "IETF IPCDN Working Group" 229 CONTACT-INFO 230 "Kevin Luehrs 231 Postal: Cable Television Laboratories, Inc. 232 400 Centennial Parkway 233 Louisville, Colorado 80027-1266 234 U.S.A. 235 Phone: +1 303-661-9100 236 Fax: +1 303-661-9199 237 E-mail: k.luehrs@cablelabs.com; mibs@cablelabs.com 239 IETF IPCDN Working Group 240 General Discussion: ipcdn@ietf.org 241 Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn 242 Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn 243 Co-chairs: Richard Woundy, 244 Richard_Woundy@cable.comcast.com 245 Jean-Francois Mule, jf.mule@cablelabs.com" 247 DESCRIPTION 248 "This MIB module supplies parameters for the 249 configuration and monitoring of CableHome 250 prioritized QoS capability. 252 Copyright (C) The Internet Society (2003). This version 253 of this MIB module is part of RFC xxxx; see the RFC 254 itself for full legal notices." 255 REVISION "200306210000Z" -- Jun 21, 2003 256 DESCRIPTION 257 "Initial version, published as RFC xxxx." 258 -- RFC editor to assign xxxx 259 ::= { mib-2 xx } 260 -- xx to be assigned by IANA 262 -- Textual conventions 264 cabhQosMibObjects OBJECT IDENTIFIER ::= { cabhQosMib 1} 265 cabhPriorityQosMibObjects OBJECT IDENTIFIER ::= 266 { cabhQosMibObjects 1 } 267 cabhPriorityQosBase OBJECT IDENTIFIER ::= 268 { cabhPriorityQosMibObjects 1 } 269 cabhPriorityQosBp OBJECT IDENTIFIER ::= 270 { cabhPriorityQosMibObjects 2 } 271 cabhPriorityQosPs OBJECT IDENTIFIER ::= 272 { cabhPriorityQosMibObjects 3 } 274 -- future parametric QOS 275 -- cabhParamQosMibObjects OBJECT IDENTIFIER ::= 276 -- { cabhQosMibObjects 2 } 278 --================================================================ 279 -- 280 -- Application Priority Master Table 281 -- 282 -- The cabhPriorityQosMasterTable contains the list of 283 -- application priorities provisioned by the cable operator. 284 -- Applications are identified by the IANA "well-known" port 285 -- numbers assigned to them. 286 -- 287 --================================================================ 288 cabhPriorityQosMasterTable OBJECT-TYPE 289 SYNTAX SEQUENCE OF CabhPriorityQosMasterEntry 290 MAX-ACCESS not-accessible 291 STATUS current 292 DESCRIPTION 293 "This table contains a list of mappings for Application 294 IDs to Default CableHome Priorities." 295 ::= { cabhPriorityQosBase 1 } 297 cabhPriorityQosMasterEntry OBJECT-TYPE 298 SYNTAX CabhPriorityQosMasterEntry 299 MAX-ACCESS not-accessible 300 STATUS current 301 DESCRIPTION 302 "An entry for mapping Application IDs to Default 303 CableHome Priorities." 304 INDEX { cabhPriorityQosMasterApplicationId } 305 ::= { cabhPriorityQosMasterTable 1 } 307 CabhPriorityQosMasterEntry ::= SEQUENCE { 308 cabhPriorityQosMasterApplicationId Unsigned32, 309 cabhPriorityQosMasterDefaultCHPriority Unsigned32, 310 cabhPriorityQosMasterRowStatus RowStatus 311 } 313 cabhPriorityQosMasterApplicationId OBJECT-TYPE 314 SYNTAX Unsigned32 (1..65535) 315 MAX-ACCESS not-accessible 316 STATUS current 317 DESCRIPTION 318 "The IANA well-known port number identifying an 319 application." 320 ::= { cabhPriorityQosMasterEntry 1 } 322 cabhPriorityQosMasterDefaultCHPriority OBJECT-TYPE 323 SYNTAX Unsigned32 (0..7) 324 MAX-ACCESS read-create 325 STATUS current 326 DESCRIPTION 327 "The PriorityQos priority assigned to the application." 328 ::= { cabhPriorityQosMasterEntry 2 } 330 cabhPriorityQosMasterRowStatus OBJECT-TYPE 331 SYNTAX RowStatus 332 MAX-ACCESS read-create 333 STATUS current 334 DESCRIPTION 335 "The Row Status interlock for creation and deletion of 336 row entries. Specifying only this object (with the 337 appropriate index) on a PS is sufficient to create a row 338 with default values. There is no restrictions to change 339 the value of cabhPriorityQosMasterDefaultCHPriority in a 340 row while this object is set to active." 341 ::= { cabhPriorityQosMasterEntry 3 } 343 -- =============================================================== 344 -- 345 -- SetToFactory Object 346 -- 347 -- This object is used to clear some of the QoS MIB tables 348 -- 349 -- =============================================================== 351 cabhPriorityQosSetToFactory OBJECT-TYPE 352 SYNTAX TruthValue 353 MAX-ACCESS read-write 354 STATUS current 355 DESCRIPTION 356 "When this object is set to true(1), the PS MUST clear 357 all the entries in the cabhPriorityQosBpTable and 358 cabhPriorityQosBpDestTable. Reading this object always 359 returns false(2)." 360 ::= { cabhPriorityQosBase 2 } 362 cabhPriorityQosLastSetToFactory OBJECT-TYPE 363 SYNTAX TimeStamp 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The value of sysUpTime when cabhPriorityQosSetToFactory 368 was last set to true. Zero if never reset." 369 ::= { cabhPriorityQosBase 3 } 371 --=============================================================== 372 -- 373 -- BP Application Priority Table 374 -- 375 -- The cabhPriorityQosBpTable contains the list of 376 -- BPs, the applications implemented on each, and the priority 377 -- assigned to each application. 378 -- 379 --=============================================================== 381 cabhPriorityQosBpTable OBJECT-TYPE 382 SYNTAX SEQUENCE OF CabhPriorityQosBpEntry 383 MAX-ACCESS not-accessible 384 STATUS current 385 DESCRIPTION 386 "This table contains the priorities for each of the 387 discovered CableHome Host (BP) applications and related 388 data." 389 ::= {cabhPriorityQosBp 1} 391 cabhPriorityQosBpEntry OBJECT-TYPE 392 SYNTAX CabhPriorityQosBpEntry 393 MAX-ACCESS not-accessible 394 STATUS current 395 DESCRIPTION 396 "List of applications entries. 398 Implementors need to be aware that if the size 399 of cabhPriorityQosBpIpAddr exceeds 113 octets then OIDs 400 of column instances in this table will have more 401 than 128 sub-identifiers and cannot be accessed 402 using SNMPv1, SNMPv2c, or SNMPv3." 403 INDEX { cabhPriorityQosMasterApplicationId, 404 cabhPriorityQosBpIpAddrType, cabhPriorityQosBpIpAddr } 405 ::= { cabhPriorityQosBpTable 1 } 407 CabhPriorityQosBpEntry ::= SEQUENCE { 408 cabhPriorityQosBpIpAddrType InetAddressType, 409 cabhPriorityQosBpIpAddr InetAddress, 410 cabhPriorityQosBpApplicationId Unsigned32, 411 cabhPriorityQosBpDefaultCHPriority Unsigned32, 412 cabhPriorityQosBpIndex Unsigned32 413 } 415 cabhPriorityQosBpIpAddrType OBJECT-TYPE 416 SYNTAX InetAddressType 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "The type of the IP address assigned to a particular BP 421 element." 422 ::= { cabhPriorityQosBpEntry 1 } 424 cabhPriorityQosBpIpAddr OBJECT-TYPE 425 SYNTAX InetAddress 426 MAX-ACCESS read-only 427 STATUS current 428 DESCRIPTION 429 "The IP address assigned to a particular BP element." 430 ::= { cabhPriorityQosBpEntry 2 } 432 cabhPriorityQosBpApplicationId OBJECT-TYPE 433 SYNTAX Unsigned32 (1..65535) 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "The IANA well-known port number assigned to a particular 438 application implemented on the CableHome Host device in 439 which this BP resides." 440 ::= { cabhPriorityQosBpEntry 3 } 442 cabhPriorityQosBpDefaultCHPriority OBJECT-TYPE 443 SYNTAX Unsigned32 (0..7) 444 MAX-ACCESS read-only 445 STATUS current 446 DESCRIPTION 447 "The PriorityQos priority assigned to a particular 448 application implemented on CableHome Host device in which 449 this BP resides. The PS populates this entry according to 450 the Application Priority Master Table." 451 ::= { cabhPriorityQosBpEntry 4 } 453 cabhPriorityQosBpIndex OBJECT-TYPE 454 SYNTAX Unsigned32 (1..65535) 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The unique identifier for a particular row in the BP 459 Application Priority Table. This identifier is used as 460 an index into the 'nested' Destination Priority Table." 461 ::= { cabhPriorityQosBpEntry 5 } 463 --=============================================================== 464 -- 465 -- Destination Priority Table 466 -- 467 -- The cabhPriorityQosDestListTable contains the list of 468 -- provisioned destinations (IP address and port number) to 469 -- which a BP can send traffic with a special PriorityQos 470 -- priority. Any application listed in the BP Application 471 -- Priority Table can be provisioned with a Destination 472 -- Priority Table. 473 -- 474 --=============================================================== 476 cabhPriorityQosBpDestTable OBJECT-TYPE 477 SYNTAX SEQUENCE OF CabhPriorityQosBpDestEntry 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "This table contains the priorities based on destination 482 IP address and port number. It is indexed with a unique 483 identifier for rows in the BP Application Priority 484 Table." 485 ::= {cabhPriorityQosBp 2} 487 cabhPriorityQosBpDestEntry OBJECT-TYPE 488 SYNTAX CabhPriorityQosBpDestEntry 489 MAX-ACCESS not-accessible 490 STATUS current 491 DESCRIPTION 492 "List of Destination IP addresses and port numbers 493 for an application to which special PriorityQos 494 priority is provisioned. 496 Implementors need to be aware that if the size 497 of cabhPriorityQosBpIpAddr exceeds 112 octets then OIDs 498 of column instances in this table will have more 499 than 128 sub-identifiers and cannot be accessed 500 using SNMPv1, SNMPv2c, or SNMPv3." 501 INDEX { cabhPriorityQosMasterApplicationId, 502 cabhPriorityQosBpIpAddrType, 503 cabhPriorityQosBpIpAddr, 504 cabhPriorityQosBpDestIndex } 505 ::= { cabhPriorityQosBpDestTable 1 } 507 CabhPriorityQosBpDestEntry ::= SEQUENCE { 508 cabhPriorityQosBpDestIndex Unsigned32, 509 cabhPriorityQosBpDestIpAddrType InetAddressType, 510 cabhPriorityQosBpDestIpAddr InetAddress, 511 cabhPriorityQosBpDestPort InetPortNumber, 512 cabhPriorityQosBpDestIpPortPriority Unsigned32 513 } 515 cabhPriorityQosBpDestIndex OBJECT-TYPE 516 SYNTAX Unsigned32 (1..65535) 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "The locally unique index into the Destination 521 Priority Table." 522 ::= { cabhPriorityQosBpDestEntry 1 } 524 cabhPriorityQosBpDestIpAddrType OBJECT-TYPE 525 SYNTAX InetAddressType 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "The type of the Destination IP Address." 530 ::= { cabhPriorityQosBpDestEntry 2 } 532 cabhPriorityQosBpDestIpAddr OBJECT-TYPE 533 SYNTAX InetAddress 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "The Destination IP address of the LAN IP Device of an 538 application to which special PriorityQos priority is 539 assigned." 540 ::= { cabhPriorityQosBpDestEntry 3 } 542 cabhPriorityQosBpDestPort OBJECT-TYPE 543 SYNTAX InetPortNumber 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "The port number of an application to which special 548 PriorityQos priority is assigned." 549 ::= { cabhPriorityQosBpDestEntry 4 } 551 cabhPriorityQosBpDestIpPortPriority OBJECT-TYPE 552 SYNTAX Unsigned32 (1..8) 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "The PriorityQos priority assigned to a particular 557 application in another LAN IP Device." 558 ::= { cabhPriorityQosBpDestEntry 5 } 560 --=============================================================== 561 -- 562 -- PS Interface Attributes Table 563 -- 564 -- The cabhPriorityQosPsIfAttribTable contains the number of 565 -- media access priorities and number of queues associated with 566 -- each LAN interface in the Residential Gateway. 568 -- 569 --=============================================================== 571 cabhPriorityQosPsIfAttribTable OBJECT-TYPE 572 SYNTAX SEQUENCE OF CabhPriorityQosPsIfAttribEntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "This table contains the number of media access 577 priorities and number of queues associated with each 578 LAN interface in the Residential Gateway." 579 ::= { cabhPriorityQosPs 1 } 581 cabhPriorityQosPsIfAttribEntry OBJECT-TYPE 582 SYNTAX CabhPriorityQosPsIfAttribEntry 583 MAX-ACCESS not-accessible 584 STATUS current 585 DESCRIPTION 586 "Number of media access priorities and number of queues 587 for each LAN interface in the Residential Gateway. This 588 table applies only to interfaces through which data 589 flows." 590 INDEX { ifIndex } 591 ::= { cabhPriorityQosPsIfAttribTable 1 } 593 CabhPriorityQosPsIfAttribEntry ::= SEQUENCE { 594 cabhPriorityQosPsIfAttribIfNumPriorities Unsigned32, 595 cabhPriorityQosPsIfAttribIfNumQueues Unsigned32 596 } 598 cabhPriorityQosPsIfAttribIfNumPriorities OBJECT-TYPE 599 SYNTAX Unsigned32 (1..8) 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "The number of media access priorities supported by 604 this LAN interface." 605 ::= { cabhPriorityQosPsIfAttribEntry 1 } 607 cabhPriorityQosPsIfAttribIfNumQueues OBJECT-TYPE 608 SYNTAX Unsigned32 (1..8) 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "The number of queues associated with this LAN 613 interface." 614 ::= { cabhPriorityQosPsIfAttribEntry 2 } 616 -- Placeholder for notifications/traps. 618 -- 620 cabhQosNotification OBJECT IDENTIFIER ::= { cabhQosMib 2 } 621 cabhPriorityQosNotification OBJECT IDENTIFIER ::= 622 { cabhQosNotification 1 } 624 -- 625 -- Conformance definitions 626 -- 627 cabhQosConformance OBJECT IDENTIFIER ::= { cabhQosMib 3 } 628 cabhPriorityQosConformance OBJECT IDENTIFIER ::= 629 { cabhQosConformance 1 } 630 cabhPriorityQosGroups OBJECT IDENTIFIER ::= 631 { cabhPriorityQosConformance 1 } 632 cabhPriorityQosCompliances OBJECT IDENTIFIER ::= 633 { cabhPriorityQosConformance 2 } 635 -- ================== 637 -- compliance statements 639 cabhPriorityQosCompliance MODULE-COMPLIANCE 640 STATUS current 641 DESCRIPTION 642 "The compliance statement for devices that implement 643 CableHome 1.1 PriorityQos capability." 644 MODULE --cabhPriorityQosMib 646 -- unconditionally mandatory groups 648 MANDATORY-GROUPS { 649 cabhPriorityQosGroup 650 } 652 OBJECT cabhPriorityQosBpIpAddrType 653 SYNTAX InetAddressType { ipv4(1) } 654 DESCRIPTION 655 "An implementation is only required to support IPv4 656 addresses." 658 OBJECT cabhPriorityQosBpIpAddr 659 SYNTAX InetAddress (SIZE(4)) 660 DESCRIPTION 661 "An implementation is only required to support IPv4 662 addresses." 664 OBJECT cabhPriorityQosBpDestIpAddrType 665 SYNTAX InetAddressType { ipv4(1) } 666 DESCRIPTION 667 "An implementation is only required to support IPv4 668 addresses." 670 OBJECT cabhPriorityQosBpDestIpAddr 671 SYNTAX InetAddress (SIZE(4)) 672 DESCRIPTION 673 "An implementation is only required to support IPv4 674 addresses." 676 ::= { cabhPriorityQosCompliances 1} 678 cabhPriorityQosGroup OBJECT-GROUP 679 OBJECTS { 680 cabhPriorityQosMasterDefaultCHPriority, 681 cabhPriorityQosMasterRowStatus, 682 cabhPriorityQosSetToFactory, 683 cabhPriorityQosLastSetToFactory, 684 cabhPriorityQosBpIpAddrType, 685 cabhPriorityQosBpIpAddr, 686 cabhPriorityQosBpApplicationId, 687 cabhPriorityQosBpDefaultCHPriority, 688 cabhPriorityQosBpIndex, 689 cabhPriorityQosBpDestIpAddrType, 690 cabhPriorityQosBpDestIpAddr, 691 cabhPriorityQosBpDestPort, 692 cabhPriorityQosBpDestIpPortPriority, 693 cabhPriorityQosPsIfAttribIfNumPriorities, 694 cabhPriorityQosPsIfAttribIfNumQueues 695 } 696 STATUS current 697 DESCRIPTION 698 "Group of objects for CableHome Application Priority 699 MIB." 700 ::= { cabhPriorityQosGroups 1 } 701 END 703 5. Acknowlegements 705 Stephen Palm - Broadcom 706 Diego Mazzola - Texas Instruments 707 James Hinsey - Broadcom 709 Funding for the RFC Editor function is currently provided by the 710 Internet Society. 712 6. Formal Syntax 714 The following syntax specification uses the augmented Backus-Naur 715 Form (BNF) as described in RFC-2234 [3]. 717 7. Security Considerations 719 There are a number of management objects defined in this MIB that 720 have a MAX-ACCESS clause of read-write and/or read-create. Such 721 objects may be considered sensitive or vulnerable in some network 722 environments. The support for SET operations in a non-secure 723 environment without proper protection can have a negative effect on 724 network operations. 726 It is thus important to control even GET access to these objects and 727 possibly to even encrypt the values of these objects when sending 728 them over the network via SNMP. Not all versions of SNMP provide 729 features for such a secure environment. 731 SNMP versions prior to SNMPv3 did not include adequate security. 732 Even if the network itself is secure (for example by using IPSec), 733 even then, there is no control as to who on the secure network is 734 allowed to access and GET/SET (read/change/create/delete) the objects 735 in this MIB module. 737 It is RECOMMENDED that implementers consider the security features as 738 provided by the SNMPv3 framework (see [RFC3410], section 8), 739 including full support for the SNMPv3 cryptographic mechanisms (for 740 authentication and privacy). 742 Further, deployment of SNMP versions prior to SNMPv3 is NOT 743 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 744 enable cryptographic security. It is then a customer/operator 745 responsibility to ensure that the SNMP entity giving access to an 746 instance of this MIB module, is properly configured to give access to 747 the objects only to those principals (users) that have legitimate 748 rights to indeed GET or SET (change/create/delete) them. 750 8. Normative References 752 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 753 9, RFC 2026, October 1996. 755 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement 756 Levels", BCP 14, RFC 2119, March 1997 758 3 Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax 759 Specifications: ABNF", RFC 2234, Internet Mail Consortium and 760 Demon Internet Ltd., November 1997 762 4 Rose, M. and K. McCloghrie, "Structure and Identification of 763 Management Information for TCP/IP-based Internets", STD 16, RFC 764 1155, May 1990. 766 5 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 767 1212, March 1991. 769 6 Rose, M., "A Convention for Defining Traps for use with the SNMP", 770 RFC 1215, March 1991. 772 7 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of 773 Management Information for Version 2 (SMIv2)", STD 58, RFC 2578, 774 April 1999. 776 8 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual 777 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 779 9 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance 780 Statements for SMIv2", STD 58, RFC 2580, April 1999. 782 10 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 783 Management Protocol", STD 15, RFC 1157, May 1990. 785 11 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 786 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 788 12 Case, J., Mundy, R., Partain, D, and B. Stewart, "Introduction and 789 Applicability Statements for Internet Standard Management 790 Framework", RFC 3410, December 2002. 792 13 Harrington D., Presuhn R. and B. Wijnen, "An Architecture for 793 Describing Simple Network Management Protocol (SNMP) Management 794 Frameworks", RFC 3411, December 2002. 796 14 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 797 Processing and Dispatching for the Simple Network Management 798 Protocol (SNMP)", RFC 3412, December 2002. 800 15 Levi, D., Meyer, P., and B. Stewart, �Simple Network Management 801 Protocol (SNMP) Applications", RFC 3413, December 2002. 803 16 Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for 804 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 805 3414, December 2002. 807 17 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 808 Control Model (VACM) for the Simple Network Management Protocol 809 (SNMP)", RFC 3415, December 2002. 811 18 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 812 "Version 2 of the Protocol Operations for the Simple Network 813 Management Protocol (SNMPv2)", RFC 3416, Decemeber 2002. 815 19 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 816 "Transport Mappings for the Simple Network Management Protocol 817 (SNMPv2)", RFC 3417, December 2002. 819 20 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 820 "Management Information Base (MIB) for the Simple Network 821 Management Protocol (SNMP)", RFC 3418, December 2002. 823 21 Cable Television Laboratories, �CableHome 1.0 Specification�, CH- 824 SP-I02-020920, September 2002, 825 http://www.cablelabs.com/projects/cablehome/specifications. 827 22 Cable Television Laboratories, �CableHome 1.1 Specification�, CH- 828 SP-D01-03xxxx, March 2003. 830 9. Informative References 832 23 Droms, R., �Dynamic Host Configuration Protocol�, RFC 2131, March 833 1997. 835 24 Sollins, K., � The TFTP Protocol (Revision 2)�, RFC 1350, July 836 1992. 838 25 Harrington, R., Presuhn, R., and B. Wijnen, �An Architecture for 839 Describing SNMP Management Frameworks�, RFC 2571, April 1999. 841 26 Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, 842 �Textual Contentions for Internet Network Addresses�, May 2002. 844 10. Intellectual Property 846 The IETF takes no position regarding the validity or scope of any 847 intellectual property or other rights that might be claimed to 848 pertain to the implementation or use of the technology described in 849 this document or the extent to which any license under such rights 850 might or might not be available; neither does it represent that it 851 has made any effort to identify any such rights. Information on the 852 IETF's procedures with respect to rights in standards-track and 853 standards-related documentation can be found in BCP-11. Copies of 854 claims of rights made available for publication and any assurances of 855 licenses to be made available, or the result of an attempt made to 856 obtain a general license or permission for the use of such 857 proprietary rights by implementers or users of this specification can 858 be obtained from the IETF Secretariat. 860 The IETF invites any interested party to bring to its attention any 861 copyrights, patents or patent applications, or other proprietary 862 rights which may cover technology that may be required to practice 863 this standard. Please address the information to the IETF Executive 864 Director. 866 11. Author�s Addresses 868 Amol Bhagwat 869 Cable Television Laboratories 870 400 Centennial Parkway 871 Louisville, CO 80027 872 Phone: +1 303.661.9100 873 Email: a.bhagwat@cablelabs.com 875 Eduardo Cardona 876 Cable Television Laboratories 877 400 Centennial Parkway 878 Louisville, CO 80027 879 Phone: +1 303.661.9100 880 Email: e.cardona@cablelabs.com 882 Kevin Luehrs 883 Cable Television Laboratories 884 400 Centennial Parkway 885 Louisville, CO 80027 886 Phone: +1 303.661.9100 887 Email: k.luehrs@cablelabs.com 889 Doug Jones 890 YAS Broadband Ventures 891 300 Brickstone Square 892 Andover, MA 01810 893 Phone: +1 303.661.3823 894 Email: doug@yas.com 896 12. Full Copyright Statement 898 Copyright (C) The Internet Society (2003). All Rights Reserved. 900 This document and translations of it may be copied and furnished to 901 others, and derivative works that comment on or otherwise explain it 902 or assist in its implementation may be prepared, copied, published 903 and distributed, in whole or in part, without restriction of any 904 kind, provided that the above copyright notice and this paragraph are 905 included on all such copies and derivative works. However, this 906 document itself may not be modified in any way, such as by removing 907 the copyright notice or references to the Internet Society or other 908 Internet organizations, except as needed for the purpose of 909 developing Internet standards in which case the procedures for 910 copyrights defined in the Internet Standards process must be 911 followed, or as required to translate it into languages other than 912 English. 914 The limited permissions granted above are perpetual and will not be 915 revoked by the Internet Society or its successors or assigns. 917 This document and the information contained herein is provided on an 918 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 919 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 920 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 921 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 922 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.