Internet-Draft A. Bhagwat draft-ietf-ipcdn-cable-gateway-qos-mib-00.txt E. Cardona Expires: December 2003 K. Luehrs CableLabs D. Jones YAS BBV June 2003 Cable Gateway Quality of Service (QoS) Management Information Base for CableHome compliant Residential Gateways Status of this Memo This document is an Internet-Draft and is subject to all provisions of Section 10 of RFC2026 [1]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Bhagwat, et. al. Expires - December 2003 [Page 1]
Internet-Draft CableHome Gateway QoS MIB June 2003 In particular, it defines a basic set of managed objects for SNMP- based management for prioritized Quality of Service functionality within a LAN, between a CableHome residential gateway device and CableHome compliant LAN host devices. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects is consistent with the SNMP framework and existing SNMP standards. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2]. Table of Contents 1. The Internet-Standard Management Framework.....................2 2. Glossary.......................................................3 2.1 CATV.......................................................3 2.2 CableHome Residential Gateway..............................3 2.3 Portal Services............................................3 2.4 Boundary Point (BP)........................................3 2.5 Application Identifiers....................................3 3. Overview.......................................................4 3.1 Structure of the MIB.......................................4 3.2 Management Requirements....................................5 4. MIB Definitions................................................5 5. Acknowlegements...............................................15 6. Formal Syntax.................................................16 7. Security Considerations.......................................16 8. Normative References..........................................16 9. Informative References........................................18 10. Intellectual Property........................................18 11. AuthorÆs Addresses...........................................19 12. Full Copyright Statement.....................................20 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [12]. Bhagwat, et. al. Expires - December 2003 [Page 2]
Internet-Draft CableHome Gateway QoS MIB June 2003 Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [7], STD 58, RFC 2579 [8] and STD 58, RFC 2580 [9]. 2. Glossary The terms in this document are derived either from normal cable system usage, from normal residential gateway operation, or from the documents associated with the CableHome Specifications [21] & [22]. 2.1 CATV Originally "Community Antenna Television", now used to refer to any cable or hybrid fiber and cable system used to deliver video signals to a community. 2.2 CableHome Residential Gateway A CableHome Residential gateway passes data traffic between the cable operator's broadband data network (the Wide Area Network, WAN) and the Local Area Network (LAN) in the cable data service subscriber's residence or business. In addition to passing traffic between the WAN and LAN, the CableHome Residential Gateway provides several services including a DHCP client and a DHCP server (RFC2131) [23], a TFTP server (RFC1350) [24], management services as enabled by SNMPv1/v2c/v3 agent compliant with the RFCs listed in Section 1, and security services including stateful packet inspection firewall functionality and software code image verification using techniques. 2.3 Portal Services A logical element aggregating the set of CableHome-specified functionality in a CableHome compliant cable gateway device. 2.4 Boundary Point (BP) A logical element aggregating the set of CableHome-specified functionality in a CableHome compliant LAN host device (LAN IP Device). 2.5 Application Identifiers The port number assigned by the Internet Assigned Numbers Authority (IANA) to an application, used by CableHome-specified elements to identify an application. Bhagwat, et. al. Expires - December 2003 [Page 3]
Internet-Draft CableHome Gateway QoS MIB June 2003 3. Overview This MIB entity supports basic traffic prioritization and queuing for CableHome compliant devices. The MIB is derived from the CableHome 1.1 specification [22]. Support for traffic prioritization and queuing is provided through four tables. These tables and their use is summarized below and described in detail in the CableHome 1.1 specification [22]. Applications running on CableHome compliant devices are identified with their IANA-assigned UDP/TCP port number. Service providers have the ability to configure the priority for any application by associating a priority number with the port number in a table implemented in the cable gateway device (Application Priority Master Table). When CableHome compliant LAN host devices acquire a network address lease, they communicate to the cable gateway device the list of applications implemented on the LAN host. This information is recorded in two other tables in the cable gateway device (BP Application Priority Table and Destination Priority Table). Portal Services functions refer to the Application Priority Master Table and reply to the LAN host device(s) with the priority assigned to their applications. The cable gateway device maintains a queue for each LAN interface, and each interface supports a particular number of priority levels. A fourth table, the PS Interface Attributes Table, maintains this information. 3.1 Structure of the MIB This MIB entity contains one group: The cabhPriorityQosGroup group contains the mechanisms needed for CableHome compliant cable gateway devices and LAN hosts to identify and communicate applications needing prioritized queuing and media access. The cabhPriortyQosGroup contains the following tables: cabhPriorityQosMasterTable Allows the service provider to provision the residential gateway with a list of supported applications and a priority value for each. The Portal Services refers to this table when acting as a proxy for the service provider, to provide application priorities to Boundary Point elements. Bhagwat, et. al. Expires - December 2003 [Page 4]
Internet-Draft CableHome Gateway QoS MIB June 2003 cabhPriorityQosBpTable Contains the list of application identifiers for each BP element in the LAN. These values are acquired by the PS during the BP Discovery process as described in [22]. cabhPriorityQosBpDestTable Contains a list of destination IP addresses for each BP, each of which can be provisioned for a special priority for a specified application. Applications are identified by their IANA-assigned port number. cabhPriorityQosPsIfAttribTable Identifies the number of queues and the number of media access priorities for each LAN interface. LAN interfaces are identified by their ifIndex. 3.2 Management Requirements In addition to the explicit requirements in this specification, the Cable Gateway MUST support all applicable CableHome and IETF requirements and MIB objects. 4. MIB Definitions CABH-IETF-QOS-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, mib-2 FROM SNMPv2-SMI TimeStamp, TruthValue, RowStatus FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF InetPortNumber, InetAddressType, InetAddress FROM INET-ADDRESS-MIB ifIndex FROM IF-MIB; Bhagwat, et. al. Expires - December 2003 [Page 5]
Internet-Draft CableHome Gateway QoS MIB June 2003 cabhQosMib MODULE-IDENTITY LAST-UPDATED "200306210000Z" -- Jun 21, 2003 ORGANIZATION "IETF IPCDN Working Group" CONTACT-INFO "Kevin Luehrs Postal: Cable Television Laboratories, Inc. 400 Centennial Parkway Louisville, Colorado 80027-1266 U.S.A. Phone: +1 303-661-9100 Fax: +1 303-661-9199 E-mail: k.luehrs@cablelabs.com; mibs@cablelabs.com IETF IPCDN Working Group General Discussion: ipcdn@ietf.org Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn Co-chairs: Richard Woundy, Richard_Woundy@cable.comcast.com Jean-Francois Mule, jf.mule@cablelabs.com" DESCRIPTION "This MIB module supplies parameters for the configuration and monitoring of CableHome prioritized QoS capability. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC xxxx; see the RFC itself for full legal notices." REVISION "200306210000Z" -- Jun 21, 2003 DESCRIPTION "Initial version, published as RFC xxxx." -- RFC editor to assign xxxx ::= { mib-2 xx } -- xx to be assigned by IANA -- Textual conventions cabhQosMibObjects OBJECT IDENTIFIER ::= { cabhQosMib 1} cabhPriorityQosMibObjects OBJECT IDENTIFIER ::= { cabhQosMibObjects 1 } cabhPriorityQosBase OBJECT IDENTIFIER ::= { cabhPriorityQosMibObjects 1 } cabhPriorityQosBp OBJECT IDENTIFIER ::= { cabhPriorityQosMibObjects 2 } cabhPriorityQosPs OBJECT IDENTIFIER ::= { cabhPriorityQosMibObjects 3 } -- future parametric QOS -- cabhParamQosMibObjects OBJECT IDENTIFIER ::= Bhagwat, et. al. Expires - December 2003 [Page 6]
Internet-Draft CableHome Gateway QoS MIB June 2003 -- { cabhQosMibObjects 2 } --================================================================ -- -- Application Priority Master Table -- -- The cabhPriorityQosMasterTable contains the list of -- application priorities provisioned by the cable operator. -- Applications are identified by the IANA "well-known" port -- numbers assigned to them. -- --================================================================ cabhPriorityQosMasterTable OBJECT-TYPE SYNTAX SEQUENCE OF CabhPriorityQosMasterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a list of mappings for Application IDs to Default CableHome Priorities." ::= { cabhPriorityQosBase 1 } cabhPriorityQosMasterEntry OBJECT-TYPE SYNTAX CabhPriorityQosMasterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry for mapping Application IDs to Default CableHome Priorities." INDEX { cabhPriorityQosMasterApplicationId } ::= { cabhPriorityQosMasterTable 1 } CabhPriorityQosMasterEntry ::= SEQUENCE { cabhPriorityQosMasterApplicationId Unsigned32, cabhPriorityQosMasterDefaultCHPriority Unsigned32, cabhPriorityQosMasterRowStatus RowStatus } cabhPriorityQosMasterApplicationId OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IANA well-known port number identifying an application." ::= { cabhPriorityQosMasterEntry 1 } cabhPriorityQosMasterDefaultCHPriority OBJECT-TYPE SYNTAX Unsigned32 (0..7) Bhagwat, et. al. Expires - December 2003 [Page 7]
Internet-Draft CableHome Gateway QoS MIB June 2003 MAX-ACCESS read-create STATUS current DESCRIPTION "The PriorityQos priority assigned to the application." ::= { cabhPriorityQosMasterEntry 2 } cabhPriorityQosMasterRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The Row Status interlock for creation and deletion of row entries. Specifying only this object (with the appropriate index) on a PS is sufficient to create a row with default values. There is no restrictions to change the value of cabhPriorityQosMasterDefaultCHPriority in a row while this object is set to active." ::= { cabhPriorityQosMasterEntry 3 } -- =============================================================== -- -- SetToFactory Object -- -- This object is used to clear some of the QoS MIB tables -- -- =============================================================== cabhPriorityQosSetToFactory OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "When this object is set to true(1), the PS MUST clear all the entries in the cabhPriorityQosBpTable and cabhPriorityQosBpDestTable. Reading this object always returns false(2)." ::= { cabhPriorityQosBase 2 } cabhPriorityQosLastSetToFactory OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when cabhPriorityQosSetToFactory was last set to true. Zero if never reset." ::= { cabhPriorityQosBase 3 } Bhagwat, et. al. Expires - December 2003 [Page 8]
Internet-Draft CableHome Gateway QoS MIB June 2003 --=============================================================== -- -- BP Application Priority Table -- -- The cabhPriorityQosBpTable contains the list of -- BPs, the applications implemented on each, and the priority -- assigned to each application. -- --=============================================================== cabhPriorityQosBpTable OBJECT-TYPE SYNTAX SEQUENCE OF CabhPriorityQosBpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the priorities for each of the discovered CableHome Host (BP) applications and related data." ::= {cabhPriorityQosBp 1} cabhPriorityQosBpEntry OBJECT-TYPE SYNTAX CabhPriorityQosBpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "List of applications entries. Implementors need to be aware that if the size of cabhPriorityQosBpIpAddr exceeds 113 octets then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3." INDEX { cabhPriorityQosMasterApplicationId, cabhPriorityQosBpIpAddrType, cabhPriorityQosBpIpAddr } ::= { cabhPriorityQosBpTable 1 } CabhPriorityQosBpEntry ::= SEQUENCE { cabhPriorityQosBpIpAddrType InetAddressType, cabhPriorityQosBpIpAddr InetAddress, cabhPriorityQosBpApplicationId Unsigned32, cabhPriorityQosBpDefaultCHPriority Unsigned32, cabhPriorityQosBpIndex Unsigned32 } cabhPriorityQosBpIpAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of the IP address assigned to a particular BP Bhagwat, et. al. Expires - December 2003 [Page 9]
Internet-Draft CableHome Gateway QoS MIB June 2003 element." ::= { cabhPriorityQosBpEntry 1 } cabhPriorityQosBpIpAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address assigned to a particular BP element." ::= { cabhPriorityQosBpEntry 2 } cabhPriorityQosBpApplicationId OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The IANA well-known port number assigned to a particular application implemented on the CableHome Host device in which this BP resides." ::= { cabhPriorityQosBpEntry 3 } cabhPriorityQosBpDefaultCHPriority OBJECT-TYPE SYNTAX Unsigned32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "The PriorityQos priority assigned to a particular application implemented on CableHome Host device in which this BP resides. The PS populates this entry according to the Application Priority Master Table." ::= { cabhPriorityQosBpEntry 4 } cabhPriorityQosBpIndex OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The unique identifier for a particular row in the BP Application Priority Table. This identifier is used as an index into the 'nested' Destination Priority Table." ::= { cabhPriorityQosBpEntry 5 } --=============================================================== -- -- Destination Priority Table -- -- The cabhPriorityQosDestListTable contains the list of Bhagwat, et. al. Expires - December 2003 [Page 10]
Internet-Draft CableHome Gateway QoS MIB June 2003 -- provisioned destinations (IP address and port number) to -- which a BP can send traffic with a special PriorityQos -- priority. Any application listed in the BP Application -- Priority Table can be provisioned with a Destination -- Priority Table. -- --=============================================================== cabhPriorityQosBpDestTable OBJECT-TYPE SYNTAX SEQUENCE OF CabhPriorityQosBpDestEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the priorities based on destination IP address and port number. It is indexed with a unique identifier for rows in the BP Application Priority Table." ::= {cabhPriorityQosBp 2} cabhPriorityQosBpDestEntry OBJECT-TYPE SYNTAX CabhPriorityQosBpDestEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "List of Destination IP addresses and port numbers for an application to which special PriorityQos priority is provisioned. Implementors need to be aware that if the size of cabhPriorityQosBpIpAddr exceeds 112 octets then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3." INDEX { cabhPriorityQosMasterApplicationId, cabhPriorityQosBpIpAddrType, cabhPriorityQosBpIpAddr, cabhPriorityQosBpDestIndex } ::= { cabhPriorityQosBpDestTable 1 } CabhPriorityQosBpDestEntry ::= SEQUENCE { cabhPriorityQosBpDestIndex Unsigned32, cabhPriorityQosBpDestIpAddrType InetAddressType, cabhPriorityQosBpDestIpAddr InetAddress, cabhPriorityQosBpDestPort InetPortNumber, cabhPriorityQosBpDestIpPortPriority Unsigned32 } cabhPriorityQosBpDestIndex OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS not-accessible Bhagwat, et. al. Expires - December 2003 [Page 11]
Internet-Draft CableHome Gateway QoS MIB June 2003 STATUS current DESCRIPTION "The locally unique index into the Destination Priority Table." ::= { cabhPriorityQosBpDestEntry 1 } cabhPriorityQosBpDestIpAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of the Destination IP Address." ::= { cabhPriorityQosBpDestEntry 2 } cabhPriorityQosBpDestIpAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The Destination IP address of the LAN IP Device of an application to which special PriorityQos priority is assigned." ::= { cabhPriorityQosBpDestEntry 3 } cabhPriorityQosBpDestPort OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-only STATUS current DESCRIPTION "The port number of an application to which special PriorityQos priority is assigned." ::= { cabhPriorityQosBpDestEntry 4 } cabhPriorityQosBpDestIpPortPriority OBJECT-TYPE SYNTAX Unsigned32 (1..8) MAX-ACCESS read-only STATUS current DESCRIPTION "The PriorityQos priority assigned to a particular application in another LAN IP Device." ::= { cabhPriorityQosBpDestEntry 5 } --=============================================================== -- -- PS Interface Attributes Table -- -- The cabhPriorityQosPsIfAttribTable contains the number of -- media access priorities and number of queues associated with -- each LAN interface in the Residential Gateway. Bhagwat, et. al. Expires - December 2003 [Page 12]
Internet-Draft CableHome Gateway QoS MIB June 2003 -- --=============================================================== cabhPriorityQosPsIfAttribTable OBJECT-TYPE SYNTAX SEQUENCE OF CabhPriorityQosPsIfAttribEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the number of media access priorities and number of queues associated with each LAN interface in the Residential Gateway." ::= { cabhPriorityQosPs 1 } cabhPriorityQosPsIfAttribEntry OBJECT-TYPE SYNTAX CabhPriorityQosPsIfAttribEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Number of media access priorities and number of queues for each LAN interface in the Residential Gateway. This table applies only to interfaces through which data flows." INDEX { ifIndex } ::= { cabhPriorityQosPsIfAttribTable 1 } CabhPriorityQosPsIfAttribEntry ::= SEQUENCE { cabhPriorityQosPsIfAttribIfNumPriorities Unsigned32, cabhPriorityQosPsIfAttribIfNumQueues Unsigned32 } cabhPriorityQosPsIfAttribIfNumPriorities OBJECT-TYPE SYNTAX Unsigned32 (1..8) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of media access priorities supported by this LAN interface." ::= { cabhPriorityQosPsIfAttribEntry 1 } cabhPriorityQosPsIfAttribIfNumQueues OBJECT-TYPE SYNTAX Unsigned32 (1..8) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of queues associated with this LAN interface." ::= { cabhPriorityQosPsIfAttribEntry 2 } -- Placeholder for notifications/traps. Bhagwat, et. al. Expires - December 2003 [Page 13]
Internet-Draft CableHome Gateway QoS MIB June 2003 -- cabhQosNotification OBJECT IDENTIFIER ::= { cabhQosMib 2 } cabhPriorityQosNotification OBJECT IDENTIFIER ::= { cabhQosNotification 1 } -- -- Conformance definitions -- cabhQosConformance OBJECT IDENTIFIER ::= { cabhQosMib 3 } cabhPriorityQosConformance OBJECT IDENTIFIER ::= { cabhQosConformance 1 } cabhPriorityQosGroups OBJECT IDENTIFIER ::= { cabhPriorityQosConformance 1 } cabhPriorityQosCompliances OBJECT IDENTIFIER ::= { cabhPriorityQosConformance 2 } -- ================== -- compliance statements cabhPriorityQosCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for devices that implement CableHome 1.1 PriorityQos capability." MODULE --cabhPriorityQosMib -- unconditionally mandatory groups MANDATORY-GROUPS { cabhPriorityQosGroup } OBJECT cabhPriorityQosBpIpAddrType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses." OBJECT cabhPriorityQosBpIpAddr SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses." OBJECT cabhPriorityQosBpDestIpAddrType Bhagwat, et. al. Expires - December 2003 [Page 14]
Internet-Draft CableHome Gateway QoS MIB June 2003 SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses." OBJECT cabhPriorityQosBpDestIpAddr SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses." ::= { cabhPriorityQosCompliances 1} cabhPriorityQosGroup OBJECT-GROUP OBJECTS { cabhPriorityQosMasterDefaultCHPriority, cabhPriorityQosMasterRowStatus, cabhPriorityQosSetToFactory, cabhPriorityQosLastSetToFactory, cabhPriorityQosBpIpAddrType, cabhPriorityQosBpIpAddr, cabhPriorityQosBpApplicationId, cabhPriorityQosBpDefaultCHPriority, cabhPriorityQosBpIndex, cabhPriorityQosBpDestIpAddrType, cabhPriorityQosBpDestIpAddr, cabhPriorityQosBpDestPort, cabhPriorityQosBpDestIpPortPriority, cabhPriorityQosPsIfAttribIfNumPriorities, cabhPriorityQosPsIfAttribIfNumQueues } STATUS current DESCRIPTION "Group of objects for CableHome Application Priority MIB." ::= { cabhPriorityQosGroups 1 } END 5. Acknowlegements Stephen Palm - Broadcom Diego Mazzola - Texas Instruments James Hinsey - Broadcom Funding for the RFC Editor function is currently provided by the Internet Society. Bhagwat, et. al. Expires - December 2003 [Page 15]
Internet-Draft CableHome Gateway QoS MIB June 2003 6. Formal Syntax The following syntax specification uses the augmented Backus-Naur Form (BNF) as described in RFC-2234 [3]. 7. Security Considerations There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. It is thus important to control even GET access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 8. Normative References 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 Bhagwat, et. al. Expires - December 2003 [Page 16]
Internet-Draft CableHome Gateway QoS MIB June 2003 3 Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, Internet Mail Consortium and Demon Internet Ltd., November 1997 4 Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 5 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. 6 Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. 7 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of Management Information for Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 8 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. 9 McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. 10 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. 11 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 12 Case, J., Mundy, R., Partain, D, and B. Stewart, "Introduction and Applicability Statements for Internet Standard Management Framework", RFC 3410, December 2002. 13 Harrington D., Presuhn R. and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", RFC 3411, December 2002. 14 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 3412, December 2002. 15 Levi, D., Meyer, P., and B. Stewart, ôSimple Network Management Protocol (SNMP) Applications", RFC 3413, December 2002. 16 Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 3414, December 2002. Bhagwat, et. al. Expires - December 2003 [Page 17]
Internet-Draft CableHome Gateway QoS MIB June 2003 17 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 3415, December 2002. 18 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMPv2)", RFC 3416, Decemeber 2002. 19 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for the Simple Network Management Protocol (SNMPv2)", RFC 3417, December 2002. 20 Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", RFC 3418, December 2002. 21 Cable Television Laboratories, ôCableHome 1.0 Specificationö, CH- SP-I02-020920, September 2002, http://www.cablelabs.com/projects/cablehome/specifications. 22 Cable Television Laboratories, ôCableHome 1.1 Specificationö, CH- SP-D01-03xxxx, March 2003. 9. Informative References 23 Droms, R., ôDynamic Host Configuration Protocolö, RFC 2131, March 1997. 24 Sollins, K., ô The TFTP Protocol (Revision 2)ö, RFC 1350, July 1992. 25 Harrington, R., Presuhn, R., and B. Wijnen, ôAn Architecture for Describing SNMP Management Frameworksö, RFC 2571, April 1999. 26 Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, ôTextual Contentions for Internet Network Addressesö, May 2002. 10. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it Bhagwat, et. al. Expires - December 2003 [Page 18]
Internet-Draft CableHome Gateway QoS MIB June 2003 has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 11. AuthorÆs Addresses Amol Bhagwat Cable Television Laboratories 400 Centennial Parkway Louisville, CO 80027 Phone: +1 303.661.9100 Email: a.bhagwat@cablelabs.com Eduardo Cardona Cable Television Laboratories 400 Centennial Parkway Louisville, CO 80027 Phone: +1 303.661.9100 Email: e.cardona@cablelabs.com Kevin Luehrs Cable Television Laboratories 400 Centennial Parkway Louisville, CO 80027 Phone: +1 303.661.9100 Email: k.luehrs@cablelabs.com Doug Jones YAS Broadband Ventures 300 Brickstone Square Andover, MA 01810 Phone: +1 303.661.3823 Email: doug@yas.com Bhagwat, et. al. Expires - December 2003 [Page 19]
Internet-Draft CableHome Gateway QoS MIB June 2003 12. Full Copyright Statement Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Bhagwat, et. al. Expires - December 2003 [Page 20]
