From owner-ipcdn@terayon.com Sat Apr 1 08:48:13 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09462 for ; Sat, 1 Apr 2000 08:48:12 -0500 (EST) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id FAA23865 for ; Sat, 1 Apr 2000 05:48:09 -0800 (PST) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 1 Apr 2000 13:48:09 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id FAA25777; Sat, 1 Apr 2000 05:48:03 -0800 (PST) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id FAA23667 for ipcdn-outgoing; Sat, 1 Apr 2000 05:46:04 -0800 (PST) Message-Id: <4.3.1.2.20000401054229.00b52ea0@poptart> X-Sender: stjohns@poptart X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 01 Apr 2000 05:42:40 -0800 To: ipcdn@terayon.com, "ipcdn mailing list (E-mail)" From: "Mike St. Johns" Subject: Re: Diffie-Hellman USM Key MIB localized keys In-Reply-To: <4FA371B64BDAD2119CF40008C7D9ADB302B96B97@indyexch5.indy.tc e.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com Exactly correct. Mike At 09:33 AM 3/31/00, Yost William wrote: >The keys generated by using the usmDHKickstartTable are not supposed to be >localized to the snmpEngineID of the agent are they? I don't think they >are. I think the PKCS#5 V2 function is used to directly calculate the keys >and they are installed as is. > >Is that right? > >----------- William H. Yost, Thomson Consumer Electronics ------------ >. Home of RCA, GE, and Proscan (317) 587-4816 yostw@tce.com . >.There's 3 ways to do it: The DOCSIS way, The Right way, and My Way . From owner-ipcdn@terayon.com Mon Apr 10 01:19:43 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21657 for ; Mon, 10 Apr 2000 01:19:29 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id WAA06477 for ; Sun, 9 Apr 2000 22:19:24 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 10 Apr 2000 05:19:24 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id WAA17607; Sun, 9 Apr 2000 22:19:14 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id WAA13744 for ipcdn-outgoing; Sun, 9 Apr 2000 22:17:22 -0700 (PDT) Message-Id: <4.3.1.2.20000409220814.00cb7830@poptart> X-Sender: stjohns@poptart X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sun, 09 Apr 2000 22:15:18 -0700 To: ipcdn@terayon.com From: "Mike St. Johns" Subject: Bare MIB - Cable Device MIB Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_27504359==_" Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com --=====================_27504359==_ Content-Type: text/plain; charset="us-ascii"; format=flowed Attached is the revise CABLE-DEVICE-MIB. This includes changes to support both IPv6 and SNMPv3 as well as some text clean up where people identified ambiguities. Some comments: Where possible I've left existing objects alone and added new IPv6 objects. Where this did not make sense, the descriptions of the IPv6 objects are written to try and deal with backwards compatibility issues. For SNMPv3 - a number of tables and objects are being deprecated in favor of the standard MIBs. Specifically, docsDevNmAccess as well as a number of the event control tables are being deprecated. The MIB is not complete in its current form - its missing the revised compliance section modifications. If you run this through a mib compiler, use the flags which turn off compliance section checking. Once the body of the mib is in its final form, I'll complete the compliance objects and the ID text. Comments to the list - try and get them in by 1 May - silence implies consent. Mike --=====================_27504359==_ Content-Type: text/plain; charset="us-ascii" DOCS-CABLE-DEVICE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Unsigned32, Counter32, Integer32, zeroDotZero, mib-2 FROM SNMPv2-SMI RowStatus, RowPointer, DateAndTime, TruthValue FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB InterfaceIndexOrZero FROM IF-MIB; -- RFC2233 docsDev MODULE-IDENTITY LAST-UPDATED "MIB_DATE" -- TEXTUAL_DATE ORGANIZATION "IETF IPCDN Working Group" CONTACT-INFO " Michael StJohns Postal: @Home Network 425 Broadway Redwood City, CA 94063 U.S.A. Phone: +1 650 569 5368 E-mail: stjohns@corp.home.net" DESCRIPTION "This is the MIB Module for MCNS-compliant cable modems and cable-modem termination systems." REVISION "9810131935Z" DESCRIPTION "Modified by Mike StJohns to add/revise filtering, TOS support, software version information objects." ::= { mib-2 69 } docsDevMIBObjects OBJECT IDENTIFIER ::= { docsDev 1 } docsDevBase OBJECT IDENTIFIER ::= { docsDevMIBObjects 1 } -- Textual Conventions InterfaceSet TEXTUAL-CONVENTION STATUS current DESCRIPTION "This is a convenience object for setting the value of a bit set object which depicts a set of interfaces. Upon read this always returns other (1). Upon a valid set, this causes interface bit set object (as indicated in the object description which uses this syntax) in the same row to be set to a bit mask set consisting of the interfaces which match the class type represented by this object. allCpe - all interfaces which face the customer. allNetwork - all interfaces which do not face the customer - e.g. for a CM the HFC MAC interface. allCpeEthernet, allCpeUsb, allCpeFirewire - self-explanatory allExternal - all interfaces which have a external physical instantiation, e.g. CPE Ethernet, HFC MAC, PCI Bus allInternal - all interfaces which point towards either the devices own stack, or towards an application residing on the device self - the interface which points to the devices own stack all - all interfaces. application1-4 - a specific application residing on the CM or CMTS. The specific mapping of which values of this object map to which interfaces is out of scope for this document. Certain of these classes of interfaces may not exist on specific agents, in which case, setting this object to those values results in related interface bit set being set to an empty bit set. all, allCpe and allNetwork MUST be valid settings for this object on any compliant agent and MUST result in at least one interface bit being set in the related bit set." SYNTAX INTEGER { other (1), allCpe (2), allNetwork (3), allCpeEthernet (4), allCpeUsb (5), allCpeFirewire (6), allExternal (7), allInternal (8), all (9), application1 (10), application2 (11), application3 (12), application4 (13) } IpV4orV6Addr ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An IP V4 or V6 address expressed as an octet string. The zero length string is equal to both 0.0.0.0 and the IPv6 :0 address." SYNTAX OCTET STRING (SIZE (0 | 4 | 16)) -- -- For the following object, there is no concept in the -- RFI specification corresponding to a backup CMTS. The -- enumeration is provided here in case someone is able -- to define such a role or device. -- docsDevRole OBJECT-TYPE SYNTAX INTEGER { cm(1), cmtsActive(2), cmtsBackup(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Defines the current role of this device. cm (1) is a Cable Modem, cmtsActive(2) is a Cable Modem Termination System which is controlling the system of cable modems, and cmtsBackup(3) is a CMTS which is currently connected, but not controlling the system (not currently used). In general, if this device is a 'cm', its role will not change during operation or between reboots. If the device is a 'cmts' it may change between cmtsActive and cmtsBackup and back again during normal operation. NB: At this time, the DOCSIS standards do not support the concept of a backup CMTS, cmtsBackup is included for completeness." ::= { docsDevBase 1 } docsDevDateTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-write STATUS current DESCRIPTION "The current date and time, with optional timezone information. This is set at boot from the time server. If its impossible to set this from boot, this shall represent elapsed time from boot relative to the standard epoch (e.g. 1 Jan 1970 0000Z). In other words, if this agent has been up for 3 minuntes, and has been unable to set this object from the time server, this object will return 1 Jan 1970 0003Z." ::= { docsDevBase 2 } docsDevResetNow OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to true(1) causes the device to reset. Reading this object always returns false(2)." ::= { docsDevBase 3 } docsDevSerialNumber OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The manufacturer's serial number for this device." ::= { docsDevBase 4 } docsDevSTPControl OBJECT-TYPE SYNTAX INTEGER { stEnabled(1), noStFilterBpdu(2), noStPassBpdu(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls operation of the spanning tree protocol (as distinguished from transparent bridging). If set to stEnabled(1) then the spanning tree protocol is enabled, subject to bridging constraints. If noStFilterBpdu(2), then spanning tree is not active, and Bridge PDUs received are discarded. If noStPassBpdu(3) then spanning tree is not active and Bridge PDUs are transparently forwarded. Note that a device need not implement all of these options, but that noStFilterBpdu(2) is required." ::= { docsDevBase 5 } -- -- The following table provides one level of security for access -- to the device by network management stations. -- Note that access is also constrained by the -- community strings and any vendor-specific security. -- docsDevNmAccessTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevNmAccessEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This table controls access to SNMP objects by network management stations. If the table is empty, access to SNMP objects is unrestricted. This table exists only on SNMPv1 or v2c agents and does not exist on SNMPv3 agents. See the conformance section for details. Specifically, for v3 agents, the appropriate MIBs and security models apply in lieu of this table. This table is deprecated. Instead, use the SNMP coexistence MIBs from RFC2576, the TARGET and NOTIFICATION MIBs from the SNMP Applications RFC, and the VACM MIBs for SNMPv1 and V2C access. If SNMP-COMMUNITY-MIB is implemented AND populated, then this table and its entries are ignored for the purpose of determining v1 or v2c access. If the SNMP-COMMUNITY-MIB table has no entries, then this table has its normal access control meaning for v1 and v2c access." ::= { docsDevMIBObjects 2 } docsDevNmAccessEntry OBJECT-TYPE SYNTAX DocsDevNmAccessEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "An entry describing access to SNMP objects by a particular network management station. An entry in this table is not readable unless the management station has read-write permission (either implicit if the table is empty, or explicit through an entry in this table. Entries are ordered by docsDevNmAccessIndex. The first matching entry (e.g. matching IP address and community string) is used to derive access." INDEX { docsDevNmAccessIndex } ::= { docsDevNmAccessTable 1 } DocsDevNmAccessEntry ::= SEQUENCE { docsDevNmAccessIndex Integer32, docsDevNmAccessIp IpAddress, docsDevNmAccessIpMask IpAddress, docsDevNmAccessCommunity OCTET STRING, docsDevNmAccessControl INTEGER, docsDevNmAccessInterfaces OCTET STRING, docsDevNmAccessStatus RowStatus } docsDevNmAccessIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "Index used to order the application of access entries." ::= { docsDevNmAccessEntry 1 } docsDevNmAccessIp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The IP address (or subnet) of the network management station. The address 255.255.255.255 is defined to mean any NMS. If traps are enabled for this entry, then the value must be the address of a specific device." DEFVAL { 'ffffffff'h } ::= { docsDevNmAccessEntry 2 } docsDevNmAccessIpMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The IP subnet mask of the network management stations. If traps are enabled for this entry, then the value must be 255.255.255.255." DEFVAL { 'ffffffff'h } ::= { docsDevNmAccessEntry 3 } docsDevNmAccessCommunity OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..32)) MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The community string to be matched for access by this entry. If set to a zero length string then any community string will match. When read, this object SHOULD return a zero length string." DEFVAL { "public" } ::= { docsDevNmAccessEntry 4 } docsDevNmAccessControl OBJECT-TYPE SYNTAX INTEGER { none(1), read(2), readWrite(3), roWithTraps(4), rwWithTraps(5), trapsOnly(6) } MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Specifies the type of access allowed to this NMS. Setting this object to none(1) causes the table entry to be destroyed. Read(2) allows access by 'get' and 'get-next' PDUs. ReadWrite(3) allows access by 'set' as well. RoWithtraps(4), rwWithTraps(5), and trapsOnly(6) control distribution of Trap PDUs transmitted by this device." DEFVAL { read } ::= { docsDevNmAccessEntry 5 } -- The syntax of the following object was copied from RFC1493, -- dot1dStaticAllowedToGoTo. docsDevNmAccessInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Specifies the set of interfaces from which requests from this NMS will be accepted. Each octet within the value of this object specifies a set of eight interfaces, with the first octet specifying ports 1 through 8, the second octet specifying interfaces 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit represents the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in the set. Note that entries in this table apply only to link-layer interfaces (e.g., Ethernet and CATV MAC). Upstream and downstream channel interfaces must not be specified. The size of this object is the minimum required to represent all configured interfaces for this device." -- DEFVAL is the bitmask corresponding to all interfaces ::= { docsDevNmAccessEntry 6 } docsDevNmAccessStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Controls and reflects the status of rows in this table. Rows in this table may be created by either the create-and-go or create-and-wait paradigms. There is no restriction on changing values in a row of this table while the row is active." ::= { docsDevNmAccessEntry 7 } -- -- Procedures for using the following group are described in section -- 3.2.1 of the DOCSIS Radio Frequence Interface Specification -- docsDevSoftware OBJECT IDENTIFIER ::= { docsDevMIBObjects 3 } docsDevSwServer OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The address of the TFTP server used for software upgrades. If the TFTP server is unknown or is a V6 address, return 0.0.0.0. This entry is deprecated. See docsDevSwServerAddress for its replacement. This object is will have its value modified given a valid SET to docsDevSwServerAddress." ::= { docsDevSoftware 1 } docsDevSwFilename OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-write STATUS current DESCRIPTION "The file name of the software image to be loaded into this device. Unless set via SNMP, this is the file name specified by the provisioning server that corresponds to the software version that is desired for this device. If unknown, the string '(unknown)' is returned." ::= { docsDevSoftware 2 } docsDevSwAdminStatus OBJECT-TYPE SYNTAX INTEGER { upgradeFromMgt(1), allowProvisioningUpgrade(2), ignoreProvisioningUpgrade(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "If set to upgradeFromMgt(1), the device will initiate a TFTP software image download using docsDevSwFilename. After successfully receiving an image, the device will set its state to ignoreProvisioningUpgrade(3) and reboot. If the download process is interrupted by a reset or power failure, the device will load the previous image and, after re-initialization, continue to attempt loading the image specified in docsDevSwFilename. If set to allowProvisioningUpgrade(2), the device will use the software version information supplied by the provisioning server when next rebooting (this does not cause a reboot). When set to ignoreProvisioningUpgrade(3), the device will disregard software image upgrade information from the provisioning server. Note that reading this object can return upgradeFromMgt(1). This indicates that a software download is currently in progress, and that the device will reboot after successfully receiving an image. At initial startup, this object has the default value of allowProvisioningUpgrade(2)." ::= { docsDevSoftware 3 } docsDevSwOperStatus OBJECT-TYPE SYNTAX INTEGER { inProgress(1), completeFromProvisioning(2), completeFromMgt(3), failed(4), other(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "InProgress(1) indicates that a TFTP download is underway, either as a result of a version mismatch at provisioning or as a result of a upgradeFromMgt request. CompleteFromProvisioning(2) indicates that the last software upgrade was a result of version mismatch at provisioning. CompleteFromMgt(3) indicates that the last software upgrade was a result of setting docsDevSwAdminStatus to upgradeFromMgt. Failed(4) indicates that the last attempted download failed, ordinarily due to TFTP timeout." REFERENCE "DOCSIS Radio Frequency Interface Specification, Section 8.2, Downloading Cable Modem Operating Software." ::= { docsDevSoftware 4 } docsDevSwCurrentVers OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The software version currently operating in this device. This object should be in the syntax used by the individual vendor to identify software versions. Any CM MUST return a string descriptive of the current software load. For a CMTS, this object SHOULD contain either a human readable representation of the vendor specific designation of the software for the chassis, or of the software for the control processor. If neither of these is applicable, this MUST contain an empty string." ::= { docsDevSoftware 5 } docsDevSwServerAddress OBJECT-TYPE SYNTAX IpV4orV6Address MAX-ACCESS read-write STATUS current DESCRIPTION "The address of the TFTP server used for software upgrades. If the TFTP server is unknown, return the zero length address string (See the TextualConvention). If docsDevSwServer is also implemented in this agent, this object is tied to it. A set of this object to an IPv4 address will result in the value of docsDevSwServer also being set to that address. If this object is set to an IPv6 address, docsDevSwServer is set to 0.0.0.0. If docsDevSwServer is set, this object is also set to that value. Note that if both are set in the same action, the order of which one sets the other is undefined - so both should be the same value." ::= { docsDevSoftware 6 } -- -- The following group describes server access and parameters used for -- initial provisioning and bootstrapping. -- docsDevServer OBJECT IDENTIFIER ::= { docsDevMIBObjects 4 } docsDevServerBootState OBJECT-TYPE SYNTAX INTEGER { operational(1), disabled(2), waitingForDhcpOffer(3), waitingForDhcpResponse(4), waitingForTimeServer(5), waitingForTftp(6), refusedByCmts(7), forwardingDenied(8), other(9), unknown(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "If operational(1), the device has completed loading and processing of configuration parameters and the CMTS has completed the Registration exchange. If disabled(2) then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3) then a DHCP Discover has been transmitted and no offer has yet been received. If waitingForDhcpResponse(4) then a DHCP Request has been transmitted and no response has yet been received. If waitingForTimeServer(5) then a Time Request has been transmitted and no response has yet been received. If waitingForTftp(6) then a request to the TFTP parameter server has been made and no response received. If refusedByCmts(7) then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8) then the registration process completed, but the network access option in the received configuration file prohibits forwarding. " REFERENCE "DOCSIS Radio Frequency Interface Specification, Figure 7-1, CM Initialization Overview." ::= { docsDevServer 1 } docsDevServerDhcp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the DHCP server that assigned an IP address to this device. Returns 0.0.0.0 if DHCP was not used for IP address assignment, or if this agent was assigned an IPv6 address. Deprecated. This object is replaced by docsDevServerDhcpAddress" ::= { docsDevServer 2 } docsDevServerTime OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the Time server (RFC-868). Returns 0.0.0.0 if the time server IP address is unknown, or if the time server was an IPv6 server. Deprecated. This object is replaced by docsDevServerTimeAddress." ::= { docsDevServer 3 } docsDevServerTftp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the TFTP server responsible for downloading provisioning and configuration parameters to this device. Returns 0.0.0.0 if the TFTP server address is unknown or is an IPv6 address. Deprecated. This object is replaced by docsDevServerConfigTftpAddress." ::= { docsDevServer 4 } docsDevServerConfigFile OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the device configuration file read from the TFTP server. Returns an empty string if the configuration file name is unknown." ::= { docsDevServer 5 } docsDevServerDhcpAddress OBJECT-TYPE SYNTAX IpV4orV6Address MAX-ACCESS read-only STATUS current DESCRIPTION "The IP v4 or v6 address of the DHCP server that assigned an IP address to this device. Returns the zero length octet string if DHCP was not used for IP address assignment." ::= { docsDevServer 6 } docsDevServerTimeAddress OBJECT-TYPE SYNTAX Ip MAX-ACCESS read-only STATUS current DESCRIPTION "The IP V4 or V6 address of the Time server (RFC-868). Returns the zero length octet string if the time server IP address is unknown." ::= { docsDevServer 7 } docsDevServerConfigTftpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP V4 or V6 address of the TFTP server responsible for downloading provisioning and configuration parameters to this device. Returns the zero length octet string if the config server address is unknown." ::= { docsDevServer 8 } -- -- Event Reporting -- docsDevEvent OBJECT IDENTIFIER ::= { docsDevMIBObjects 5 } docsDevEvControl OBJECT-TYPE SYNTAX INTEGER { resetLog(1), useDefaultReporting(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to resetLog(1) empties the event log. All data is deleted. Setting it to useDefaultReporting(2) returns all event priorities to their factory-default reporting. Reading this object always returns useDefaultReporting(2)." ::= { docsDevEvent 1 } docsDevEvSyslog OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The IP address of the Syslog server. If 0.0.0.0, syslog transmission is either inhibited, or if docsDevEvSyslogAddress exists in this agent - may be an IPv6 device. Deprecated. See docsDevEvSyslogAddress" ::= { docsDevEvent 2 } docsDevEvThrottleAdminStatus OBJECT-TYPE SYNTAX INTEGER { unconstrained(1), maintainBelowThreshold(2), stopAtThreshold(3), inhibited(4) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "Controls the transmission of traps and syslog messages with respect to the trap pacing threshold. unconstrained(1) causes traps and syslog messages to be transmitted without regard to the threshold settings. maintainBelowThreshold(2) causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold. stopAtThreshold(3) causes trap transmission to cease at the threshold, and not resume until directed to do so. inhibited(4) causes all trap transmission and syslog messages to be suppressed. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. Writing to this object resets the thresholding state. At initial startup, this object has a default value of unconstrained(1). DEPRECATED: In favor of the SNMP-TARGET-MIB. Use those objects instead. See RFC2573 for details." ::= { docsDevEvent 3 } docsDevEvThrottleInhibited OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS deprecated DESCRIPTION "If true(1), trap and syslog transmission is currently inhibited due to thresholds and/or the current setting of docsDevEvThrottleAdminStatus. In addition, this is set to true(1) if transmission is inhibited due to no syslog (docsDevEvSyslog) or trap (docsDevNmAccessEntry) destinations having been set. Deprecated in favor of the SNMP-TARGET-MIB." ::= { docsDevEvent 4 } docsDevEvThrottleThreshold OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION "Number of trap/syslog events per docsDevEvThrottleInterval to be transmitted before throttling. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. At initial startup, this object returns 0." ::= { docsDevEvent 5 } docsDevEvThrottleInterval OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The interval over which the trap threshold applies. At initial startup, this object has a value of 1. Deprecated in favor of the SNMP-TARGET-MIB." ::= { docsDevEvent 6 } -- -- The following table controls the reporting of the various classes of -- events. -- docsDevEvControlTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevEvControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table allows control of the reporting of event classes. For each event priority, a combination of logging and reporting mechanisms may be chosen. The mapping of event types to priorities is vendor-dependent. Vendors may also choose to allow the user to control that mapping through proprietary means." ::= { docsDevEvent 7 } docsDevEvControlEntry OBJECT-TYPE SYNTAX DocsDevEvControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Allows configuration of the reporting mechanisms for a particular event priority." INDEX { docsDevEvPriority } ::= { docsDevEvControlTable 1 } DocsDevEvControlEntry ::= SEQUENCE { docsDevEvPriority INTEGER, docsDevEvReporting BITS } docsDevEvPriority OBJECT-TYPE SYNTAX INTEGER { emergency(1), alert(2), critical(3), error(4), warning(5), notice(6), information(7), debug(8) } MAX-ACCESS not-accessible STATUS current DESCRIPTION "The priority level that is controlled by this entry. These are ordered from most (emergency) to least (debug) critical. Each event with a CM or CMTS has a particular priority level associated with it (as defined by the vendor). During normal operation no event more critical than notice(6) should be generated. Events between warning and emergency should be generated at appropriate levels of problems (e.g. emergency when the box is about to crash)." ::= { docsDevEvControlEntry 1 } docsDevEvReporting OBJECT-TYPE SYNTAX BITS { local(0), traps(1), syslog(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Defines the action to be taken on occurrence of this event class. Implementations may not necessarily support all options for all event classes, but at minimum must allow traps and syslogging to be disabled. If the local(0) bit is set, then log to the internal log, if the traps(1) bit is set, then generate a trap, if the syslog(2) bit is set, then send a syslog message (assuming the syslog address is set)." ::= { docsDevEvControlEntry 2 } docsDevEventTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Contains a log of network and device events that may be of interest in fault isolation and troubleshooting." ::= { docsDevEvent 8 } docsDevEventEntry OBJECT-TYPE SYNTAX DocsDevEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a network or device event that may be of interest in fault isolation and troubleshooting. Multiple sequential identical events are represented by incrementing docsDevEvCounts and setting docsDevEvLastTime to the current time rather than creating multiple rows. Entries are created with the first occurrance of an event. docsDevEvControl can be used to clear the table. Individual events can not be deleted." INDEX { docsDevEvIndex } ::= { docsDevEventTable 1 } DocsDevEventEntry ::= SEQUENCE { docsDevEvIndex Integer32, docsDevEvFirstTime DateAndTime, docsDevEvLastTime DateAndTime, docsDevEvCounts Counter32, docsDevEvLevel INTEGER, docsDevEvId Unsigned32, docsDevEvText SnmpAdminString } docsDevEvIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Provides relative ordering of the objects in the event log. This object will always increase except when (a) the log is reset via docsDevEvControl, (b) the device reboots and does not implement non-volatile storage for this log, or (c) it reaches the value 2^31. The next entry for all the above cases is 1." ::= { docsDevEventEntry 1 } docsDevEvFirstTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of docsDevDateTime at the time this entry was created." ::= { docsDevEventEntry 2 } docsDevEvLastTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "If multiple events are reported via the same entry, the value of docsDevDateTime that the last event for this entry occurred, otherwise this should have the same value as docsDevEvFirstTime. " ::= { docsDevEventEntry 3 } docsDevEvCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of consecutive event instances reported by this entry. This starts at 1 with the creation of this row and increments by 1 for each subsequent duplicate event." ::= { docsDevEventEntry 4 } docsDevEvLevel OBJECT-TYPE SYNTAX INTEGER { emergency(1), alert(2), critical(3), error(4), warning(5), notice(6), information(7), debug(8) } MAX-ACCESS read-only STATUS current DESCRIPTION "The priority level of this event as defined by the vendor. These are ordered from most serious (emergency) to least serious (debug)." ::= { docsDevEventEntry 5 } -- -- Vendors will provide their own enumerations for the following. -- The interpretation of the enumeration is unambiguous for a -- particular value of the vendor's enterprise number in sysObjectID. -- docsDevEvId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "For this product, uniquely identifies the type of event that is reported by this entry." ::= { docsDevEventEntry 6 } docsDevEvText OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "Provides a human-readable description of the event, including all relevant context (interface numbers, etc.)." ::= { docsDevEventEntry 7 } docsDevEvSyslogAddress OBJECT-TYPE SYNTAX IpV4orV6Address MAX-ACCESS read-write STATUS current DESCRIPTION "The IP V4 or V6 address of the Syslog server. If the address of the server is set to any of the zero length string, the 0.0.0.0 V4 address or the 0: V6 address, syslog transmission is inhibited. By default at agent boot, this object returns the zero length string." ::= { docsDevEvent 9 } docsDevFilter OBJECT IDENTIFIER ::= { docsDevMIBObjects 6 } -- -- Link Level Control Filtering -- docsDevFilterLLCUnmatchedAction OBJECT-TYPE SYNTAX INTEGER { discard(1), accept(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "LLC (Link Level Control) filters can be defined on an inclusive or exclusive basis: CMs can be configured to forward only packets matching a set of layer three protocols, or to drop packets matching a set of layer three protocols. Typical use of these filters is to filter out possibly harmful (given the context of a large metropolitan LAN) protocols. If set to discard(1), any L2 packet which does not match at least one filter in the docsDevFilterLLCTable will be discarded. If set to accept(2), any L2 packet which does not match at least one filter in the docsDevFilterLLCTable will be accepted for further processing (e.g., bridging). In otherwords, if the packet does not match an entry in the table it takes this action, if it does match an entry in the table it takes the opposite of this action. At initial system startup, this object returns accept(2)." ::= { docsDevFilter 1 } docsDevFilterLLCTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterLLCEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of filters to apply to (bridged) LLC traffic. The filters in this table are applied to incoming traffic on the appropriate interface(s) prior to any further processing (e.g. before handing the packet off for level 3 processing, or for bridging). The specific action taken when no filter is matched is controlled by docsDevFilterLLCUnmatchedAction." ::= { docsDevFilter 2 } docsDevFilterLLCEntry OBJECT-TYPE SYNTAX DocsDevFilterLLCEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a single filter to apply to (bridged) LLC traffic received on a specified interface. " INDEX { docsDevFilterLLCIndex } ::= { docsDevFilterLLCTable 1 } DocsDevFilterLLCEntry ::= SEQUENCE { docsDevFilterLLCIndex Integer32, docsDevFilterLLCStatus RowStatus, docsDevFilterLLCIfIndex InterfaceIndexOrZero, docsDevFilterLLCProtocolType INTEGER, docsDevFilterLLCProtocol Integer32, docsDevFilterLLCMatches Counter32, docsDevFilterLLCInterfaces OCTET STRING, docsDevFilterLLCInterfaceSet InterfaceSet } docsDevFilterLLCIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index used for the identification of filters (note that LLC filter order is irrelevant)." ::= { docsDevFilterLLCEntry 1 } docsDevFilterLLCStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Controls and reflects the status of rows in this table. There is no restriction on changing any of the associated columns for this row while this object is set to active." ::= { docsDevFilterLLCEntry 2} docsDevFilterLLCIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another network interface. If the value is zero, the filter applies to all interfaces. In Cable Modems, the default value is the customer side interface. In Cable Modem Termination Systems, this object has to be specified to create a row in this table. DEPRECATED. If the docsDevFilterLLCInterfaces object exists in this agent and row, then the value of this object is ignored for purposes of filtering." ::= { docsDevFilterLLCEntry 3 } docsDevFilterLLCProtocolType OBJECT-TYPE SYNTAX INTEGER { ethertype(1), dsap(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The format of the value in docsDevFilterLLCProtocol: either a two-byte Ethernet Ethertype, or a one-byte 802.2 SAP value. EtherType(1) also applies to SNAP- encapsulated frames." DEFVAL { ethertype } ::= { docsDevFilterLLCEntry 4 } docsDevFilterLLCProtocol OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The layer three protocol for which this filter applies. The protocol value format depends on docsDevFilterLLCProtocolType. Note that for SNAP frames, etherType filtering is performed rather than DSAP=0xAA." DEFVAL { 0 } ::= { docsDevFilterLLCEntry 5 } docsDevFilterLLCMatches OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Counts the number of times this filter was matched." ::= { docsDevFilterLLCEntry 6 } docsDevFilterLLCInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the set of interfaces this filter applies to. Each octet within the value of this object specifies a set of eight interfaces, with the first octet spefifying interfaces 1 through 8, the second octet specifying interfaces 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit representst the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in this set. The actual mapping of physical interfaces to interface number is implementation dependent." ::= { docsDevFilterLLCEntry 7 } docsDevFilterLLCInterfaceSet OBJECT-TYPE SYNTAX InterfaceSet MAX-ACCESS read-create STATUS current DESCRIPTION "This is a convenience object for setting the value of docsDevFilterLLCInterfaces. Upon a valid set, this causes docsDevFilterLLCInterfaces in the same row to be set to a bit mask set consisting of the interfaces which match the class type represented by this object. Upon read, this returns 'other' by definition." DEFVAL { allCpe } ::= { docsDevFilterLLCEntry 8 } docsDevFilterIpDefault OBJECT-TYPE SYNTAX INTEGER { discard(1), accept(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The default behavior for (bridged) packets that do not match IP filters is defined by docsDevFilterIpDefault. If set to discard(1), all packets not matching an IP filter will be discarded. If set to accept(2), all packets not matching an IP filter will be accepted for further processing (e.g., bridging). At initial system startup, this object returns accept(2)." ::= { docsDevFilter 3 } docsDevFilterIpTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterIpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An ordered list of filters or classifiers to apply to IP traffic. Filter application is ordered by the filter index, rather than by a best match algorithm (Note that this implies that the filter table may have gaps in the index values). Packets which match no filters will have policy 0 in the docsDevFilterPolicyTable applied to them if it exists. Otherwise, Packets which match no filters are discarded or forwarded according to the setting of docsDevFilterIpDefault. Any IP packet can theoretically match multiple rows of this table. When considering a packet, the table is scanned in row index order (e.g. filter 10 is checked before filter 20). If the packet matches that filter (which means that it matches ALL criteria for that row), actions appropriate to docsDevFilterIpControl and docsDevFilterPolicyId are taken. If the packet was discarded processing is complete. If docsDevFilterIpContinue is set to true, the filter comparison continues with the next row in the table looking for additional matches. If the packet matches no filter in the table, the packet is accepted or dropped for further processing based on the setting of docsDevFilterIpDefault. If the packet is accepted, the actions specified by policy group 0 (e.g. the rows in docsDevFilterPolicyTable which have a value of 0 for docsDevFilterPolicyId) are taken if that policy group exists. Logically, this table is consulted twice during the processing of any IP packet - once upon its acceptance from the L2 entity, and once upon its transmission to the L2 entity. In actuality, for cable modems, IP filtering is generally the only IP processing done for transit traffic. This means that inbound and outbound filtering can generally be done at the same time with one pass through the filter table." ::= { docsDevFilter 4 } docsDevFilterIpEntry OBJECT-TYPE SYNTAX DocsDevFilterIpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a filter to apply to IP traffic received on a specified interface. All identity objects in this table (e.g. source and destination address/mask, protocol, source/dest port, TOS/mask, interface and direction) must match their respective fields in the packet for any given filter to match. To create an entry in this table, docsDevFilterIpIfIndex must be specified." INDEX { docsDevFilterIpIndex } ::= { docsDevFilterIpTable 1 } DocsDevFilterIpEntry ::= SEQUENCE { docsDevFilterIpIndex Integer32, docsDevFilterIpStatus RowStatus, docsDevFilterIpControl INTEGER, docsDevFilterIpIfIndex InterfaceIndexOrZero, docsDevFilterIpDirection INTEGER, docsDevFilterIpBroadcast TruthValue, docsDevFilterIpSaddr IpAddress, docsDevFilterIpSmask IpAddress, docsDevFilterIpDaddr IpAddress, docsDevFilterIpDmask IpAddress, docsDevFilterIpProtocol Integer32, docsDevFilterIpSourcePortLow Integer32, docsDevFilterIpSourcePortHigh Integer32, docsDevFilterIpDestPortLow Integer32, docsDevFilterIpDestPortHigh Integer32, docsDevFilterIpMatches Counter32, docsDevFilterIpTos OCTET STRING, docsDevFilterIpTosMask OCTET STRING, docsDevFilterIpContinue TruthValue, docsDevFilterIpPolicyId Integer32, docsDevFilterIpInterfaces OCTET STRING, docsDevFilterIpInterfaceSet INTEGER } docsDevFilterIpIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index used to order the application of filters. The filter with the lowest index is always applied first." ::= { docsDevFilterIpEntry 1 } docsDevFilterIpStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Controls and reflects the status of rows in this table. Specifying only this object (with the appropriate index) on a CM is sufficient to create a filter row which matches all inbound packets on the ethernet interface, and results in the packets being discarded. docsDevFilterIpIfIndex (at least) must be specified on a CMTS to create a row. Creation of the rows may be done via either create-and-wait or create-and-go, but the filter is not applied until this object is set to (or changes to) active. There is no restriction in changing any object in a row while this object is set to active." ::= { docsDevFilterIpEntry 2 } docsDevFilterIpControl OBJECT-TYPE SYNTAX INTEGER { discard(1), accept(2), policy(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "If set to discard(1), all packets matching this filter will be discarded and scanning of the remainder of the filter list will be aborted. If set to accept(2), all packets matching this filter will be accepted for further processing (e.g., bridging). If docsDevFilterIpContinue is set to true, see if there are other matches, otherwise done. If set to policy (3), execute the policy entries matched by docsDevIpFilterPolicyId in docsDevIpFilterPolicyTable. If is docsDevFilterIpContinue is set to true, continue scanning the table for other matches, otherwise done." DEFVAL { discard } ::= { docsDevFilterIpEntry 3 } docsDevFilterIpIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another interface. If the value is zero, the filter applies to all interfaces. Default value in Cable Modems is the index of the customer-side (e.g. ethernet) interface. In Cable Modem Termination Systems, this object MUST be specified to create a row in this table. DEPRECATED. If the docsDevFilterIpInterfaces object exists in this agent and row, then the value of this object is ignored for purposes of filtering AND this object need not be specified to create a row in this table." ::= { docsDevFilterIpEntry 4 } docsDevFilterIpDirection OBJECT-TYPE SYNTAX INTEGER { inbound(1), outbound(2), both(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Determines whether the filter is applied to inbound(1) traffic, outbound(2) traffic, or traffic in both(3) directions." DEFVAL { inbound } ::= { docsDevFilterIpEntry 5 } docsDevFilterIpBroadcast OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If set to true(1), the filter only applies to multicast and broadcast traffic. If set to false(2), the filter applies to all traffic." DEFVAL { false } ::= { docsDevFilterIpEntry 6 } docsDevFilterIpSaddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The source IP address, or portion thereof, that is to be matched for this filter. The source address is first masked (and'ed) against docsDevFilterIpSmask before being compared to this value. A value of 0 for this object and 0 for the mask matches all IP addresses." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 7 } docsDevFilterIpSmask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the source address prior to matching. This mask is not necessarily the same as a subnet mask, but 1's bits must be leftmost and contiguous." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 8 } docsDevFilterIpDaddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The destination IP address, or portion thereof, that is to be matched for this filter. The destination address is first masked (and'ed) against docsDevFilterIpDmask before being compared to this value. A value of 0 for this object and 0 for the mask matches all IP addresses." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 9 } docsDevFilterIpDmask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the destination address prior to matching. This mask is not necessarily the same as a subnet mask, but 1's bits must be leftmost and contiguous." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 10 } docsDevFilterIpProtocol OBJECT-TYPE SYNTAX Integer32 (0..256) MAX-ACCESS read-create STATUS current DESCRIPTION "The IP protocol value that is to be matched. For example: icmp is 1, tcp is 6, udp is 17. A value of 256 matches ANY protocol." DEFVAL { 256 } ::= { docsDevFilterIpEntry 11 } docsDevFilterIpSourcePortLow OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive lower bound of the transport-layer source port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 0 } ::= { docsDevFilterIpEntry 12 } docsDevFilterIpSourcePortHigh OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive upper bound of the transport-layer source port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 65535 } ::= { docsDevFilterIpEntry 13 } docsDevFilterIpDestPortLow OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive lower bound of the transport-layer destination port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 0 } ::= { docsDevFilterIpEntry 14 } docsDevFilterIpDestPortHigh OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive upper bound of the transport-layer destination port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 65535 } ::= { docsDevFilterIpEntry 15 } docsDevFilterIpMatches OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Counts the number of times this filter was matched. This object is initialized to 0 at boot, or at row creation, and is reset only upon reboot." ::= { docsDevFilterIpEntry 16 } docsDevFilterIpTos OBJECT-TYPE SYNTAX OCTET STRING ( SIZE (1)) MAX-ACCESS read-create STATUS current DESCRIPTION "This is the value to be matched to the packet's TOS (Type of Service) value (after the TOS value is AND'd with docsDevFilterIpTosMask). A value for this object of 0 and a mask of 0 matches all TOS values." DEFVAL { '00'h } ::= { docsDevFilterIpEntry 17 } docsDevFilterIpTosMask OBJECT-TYPE SYNTAX OCTET STRING ( SIZE (1) ) MAX-ACCESS read-create STATUS current DESCRIPTION "The mask to be applied to the packet's TOS value before matching." DEFVAL { '00'h } ::= { docsDevFilterIpEntry 18 } docsDevFilterIpContinue OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create -- STATUS current ??? STATUS deprecated DESCRIPTION "If this value is set to true, and docsDevFilterIpControl is anything but discard (1), continue scanning and applying policies." -- If this is deprecated, additional text will be added. DEFVAL { false } ::= { docsDevFilterIpEntry 19 } docsDevFilterIpPolicyId OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "This object points to an entry in docsDevFilterPolicyTable. If docsDevFilterIpControl is set to policy (3), execute all matching policies in docsDevFilterPolicyTable. If no matching policy exists, treat as if docsDevFilterIpControl were set to accept (1). If this object is set to the value of 0, there is no matching policy, and docsDevFilterPolicyTable MUST NOT be consulted." DEFVAL { 0 } ::= { docsDevFilterIpEntry 20 } docsDevFilterIpInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the set of interfaces this filter applies to. Each octet within the value of this object specifies a set of eight interfaces, with the first octet spefifying interfaces 1 through 8, the second octet specifying interfaces 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit representst the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in this set." ::= { docsDevFilterIpEntry 21 } docsDevFilterIpInterfaceSet OBJECT-TYPE SYNTAX InterfaceSet MAX-ACCESS read-create STATUS current DESCRIPTION "This is a convenience object for setting the value of docsDevFilterIpInterfaces. Upon read this always returns other (1). Upon a valid set, this causes docsDevFilterIpInterfaces in the same row to be set to a bit mask set consisting of the interfaces which match the class type represented by this object." DEFVAL { allCpe } ::= { docsDevFilterIpEntry 22 } -- -- docsDevFilterPolicyTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterPolicyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A Table which maps between a policy group ID and a set of policies to be applied. All rows with the same docsDevFilterPolicyId are part of the same policy group and are applied in the order in which they are in this table. docsDevFilterPolicyTable exists to allow multiple policy actions to be applied to any given classified packet. The policy actions are applied in index order For example: Index ID Type Action 1 1 TOS 1 9 5 TOS 1 12 1 IPSEC 3 This says that a packet which matches a filter with policy id 1, first has TOS policy 1 applied (which might set the TOS bits to enable a higher priority), and next has the IPSEC policy 3 applied (which may result in the packet being dumped into a secure VPN to a remote encryptor). Policy ID 0 is reserved for default actions and is applied only to packets which match no filters in docsDevIpFilterTable." ::= { docsDevFilter 5 } docsDevFilterPolicyEntry OBJECT-TYPE SYNTAX DocsDevFilterPolicyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the docsDevFilterPolicyTable. Entries are created by Network Management. To create an entry, docsDevFilterPolicyId and docsDevFilterPolicyAction must be specified." INDEX { docsDevFilterPolicyIndex } ::= { docsDevFilterPolicyTable 1 } DocsDevFilterPolicyEntry ::= SEQUENCE { docsDevFilterPolicyIndex Integer32, docsDevFilterPolicyId Integer32, docsDevFilterPolicyStatus RowStatus, docsDevFilterPolicyPtr RowPointer } docsDevFilterPolicyIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index value for the table." ::= { docsDevFilterPolicyEntry 1 } docsDevFilterPolicyId OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "Policy ID for this entry. A policy ID can apply to multiple rows of this table, all relevant policies are executed. Policy 0 (if populated) is applied to all packets which do not match any of the filters. N.B. If docsDevFilterIpPolicyId is set to 0, it DOES NOT match policy 0 of this table. " ::= { docsDevFilterPolicyEntry 2 } -- docsDevFilterPolicyType ::= { docsDevFilterPolicyEntry 3} Removed -- docsDevFilterPolicyAction ::= { docsDevFilterPolicyEntry 4 } removed docsDevFilterPolicyStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Object used to create an entry in this table." ::= { docsDevFilterPolicyEntry 5 } docsDevFilterPolicyPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This object points to a row in an applicable filter policy table. Currently, the only standard policy table is docsDevFilterTosTable. Per the textual convention, this object points to the first accessible object in the row. E.g. to point to a row in docsDevFilterTosTable with an index of 21, the value of this object would be the object identifier docsDevTosStatus.21. Vendors must adhere to the same convention when adding vendor specific policy table extensions. The default upon row creation is a null pointer which results in no policy action being taken." DEFVAL { zeroDotZero } ::= { docsDevFilterPolicyEntry 6 } -- -- TOS Policy action table -- docsDevFilterTosTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterTosEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table used to describe Type of Service (TOS) bits processing. This table is an adjunct to the docsDevFilterIpTable, and the docsDevFilterPolicy table. Entries in the latter table can point to specific rows in this (and other) tables and cause specific actions to be taken. This table permits the manipulation of the value of the Type of Service bits in the IP header of the matched packet as follows: Set the tosBits of the packet to (tosBits & docsDevFilterTosAndMask) | docsDevFilterTosOrMask This construct allows you to do a clear and set of all the TOS bits in a flexible manner." ::= { docsDevFilter 6 } docsDevFilterTosEntry OBJECT-TYPE SYNTAX DocsDevFilterTosEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A TOS policy entry." INDEX { docsDevFilterTosIndex } ::= { docsDevFilterTosTable 1 } DocsDevFilterTosEntry ::= SEQUENCE { docsDevFilterTosIndex Integer32, docsDevFilterTosStatus RowStatus, docsDevFilterTosAndMask OCTET STRING (SIZE (1)), docsDevFilterTosOrMask OCTET STRING (SIZE (1)) } docsDevFilterTosIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The unique index for this row. There are no ordering requirements for this table and any valid index may be specified." ::= { docsDevFilterTosEntry 1 } docsDevFilterTosStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The object used to create and delete entries in this table. A row created by specifying just this object results in a row which specifies no change to the TOS bits. A row may be created using either the create-and-go or create-and-wait paradigms. There is no restriction on the ability to change values in this row while the row is active." ::= { docsDevFilterTosEntry 2 } docsDevFilterTosAndMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1)) MAX-ACCESS read-create STATUS current DESCRIPTION "This value is bitwise AND'd with the matched packet's TOS bits." DEFVAL { 'ff'h } ::= { docsDevFilterTosEntry 3 } docsDevFilterTosOrMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1)) MAX-ACCESS read-create STATUS current DESCRIPTION "After bitwise AND'ing with the above bits, the packet's TOS bits are bitwise OR'd with these bits, and the packet's TOS BITS are set to that value." DEFVAL { '00'h } ::= { docsDevFilterTosEntry 4 } docsDevFilterIpV6AuxTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterIpV6AuxEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table augments docsDevIpFilterTable with objects that allow filtering of IPv6 packets." ::= { docsDevFilter 7 } docsDevFilterIpV6AuxEntry OBJECT-TYPE SYNTAX DocsDevFilterIpV6AuxEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This augments the existing objects in docsDevFilterIpEntry, but by default the objects in this entry have not effect on filtering as docsDevFilterIpType defaults to ipv4 upon row creation." AUGMENTS {docsDevIpFilterEntry } ::= {docsDevFilterIpV6AuxTable 1 } DocsDevFilterIpV6AuxEntry ::= SEQUENCE { docsDevFilterIpType INTEGER, docsDevFilterIpV6Saddr IpV6Address, docsDevFilterIpV6Smask IpV6Address, docsDevFilterIpV6Daddr IpV6Address, docsDevFilterIpV6Dmask IpV6Address } docsDevFilterIpType OBJECT-TYPE SYNTAX INTEGER { ipv4(1), ipv6(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object controls whether this filter entry refers to IP v4 or v6 type packets. If this object is ipv4, then the IpAddress objects docsDevFilterEntry apply, otherwise if this object is ipv6 then the remaining objects in this entry apply." DEFVAL { ipv4 } ::= { docsDevFilterIpV6AuxEntry 1} docsDevFilterIpV6Saddr OBJECT-TYPE SYNTAX IpV6Address MAX-ACCESS read-create STATUS current DESCRIPTION "The source address IPv6 address or portion thereof that is to be matched for this filter. The packet's source address is first masked (and'ed) aginst docsDevFilterIpV6Smask before being compared to this value. A value of of zero for this object and for the mask matches all IPv6 addresses." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 2 } docsDevFilterIpV6Smask OBJECT-TYPE SYNTAX IpV6Address MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the packet's source address prior to matching. The mask is not necessarily the same as a subnet mask, the the 1's bits must be leftmost and contiguous." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 3 } docsDevFilterIpV6Daddr OBJECT-TYPE SYNTAX IpV6Address MAX-ACCESS read-create STATUS current DESCRIPTION "The destination address IPv6 address or portion thereof that is to be matched for this filter. The packet's source address is first masked (and'ed) aginst docsDevFilterIpV6Dmask before being compared to this value. A value of of zero for this object and for the mask matches all IPv6 addresses." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 4 } docsDevFilterIpV6Dmask OBJECT-TYPE SYNTAX IpV6Address MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the packet's destination address prior to matching. The mask is not necessarily the same as a subnet mask, the the 1's bits must be leftmost and contiguous." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 5 } -- -- CPE IP Management and anti spoofing group. Only implemented on -- Cable Modems. -- docsDevCpe OBJECT IDENTIFIER ::= { docsDevMIBObjects 7} docsDevCpeEnroll OBJECT-TYPE SYNTAX INTEGER { none(1), any(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the population of docsDevFilterCpeTable. If set to none, the filters must be set manually. If set to any, the CM wiretaps the packets originating from the ethernet and enrolls up to docsDevCpeIpMax addresses based on the source IPv4 or v6 addresses of those packets. At initial system startup, default value for this object is any(2)." ::= { docsDevCpe 1 } docsDevCpeIpMax OBJECT-TYPE SYNTAX Integer32 (-1..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the maximum number of CPEs allowed to be learned behind this device. If set to zero, any number of CPEs may connect up to the maximum permitted for the device. If set to -1, no filtering is done on CPE source addresses, and no entries are made in the docsDevFilterCpeTable via learning. If an attempt is made to set this to a number greater than that permitted for the device, it is set to that maximum. At initial system startup, default value for this object is -1." ::= { docsDevCpe 2 } docsDevCpeTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevCpeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the IP addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to automatically add learned addresses." ::= { docsDevCpe 3 } docsDevCpeEntry OBJECT-TYPE SYNTAX DocsDevCpeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the docsDevFilterCpeTable. There is one entry for each IP CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored, otherwise: Upon receipt of an IP packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table, but docsDevCpeEnroll is set to any and the sum of the table sizes of docsDevCpeTable and docsDevCpeV6Table is less than docsDevCpeIpMax, the address is added to the table and packet processing continues. Otherwise, the packet is dropped. The filtering actions specified by this table occur after any LLC filtering (docsDevFilterLLCTable), but prior to any IP filtering (docsDevFilterIpTable, docsDevNmAccessTable)." INDEX { docsDevCpeIp } ::= {docsDevCpeTable 1 } DocsDevCpeEntry ::= SEQUENCE { docsDevCpeIp IpAddress, docsDevCpeSource INTEGER, docsDevCpeStatus RowStatus } docsDevCpeIp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP address to which this entry applies. N.B. Neither the all zeros or all ones addresses may be used as the value of this object." ::= { docsDevCpeEntry 1 } docsDevCpeSource OBJECT-TYPE SYNTAX INTEGER { other(1), manual(2), learned(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object describes how this entry was created. If the value is manual(2), this row was created by a network management action (either configuration, or SNMP set). If set to learned(3), then it was found via looking at the source IP address of a received packet." ::= { docsDevCpeEntry 2 } docsDevCpeStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Standard object to manipulate rows. To create a row in this table, you only need to specify this object. Management stations SHOULD use the create-and-go mechanism for creating rows in this table." ::= { docsDevCpeEntry 3 } docsDevCpeV6Table OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevCpeV6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the IP V6 addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to automatically add learned addresses. This table exactly mirrors docsDevCpeTable and applies only to IPv6 addresses." ::= { docsDevCpe 4 } docsDevCpeV6Entry OBJECT-TYPE SYNTAX DocsDevCpeV6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the docsDevFilterCpeTable. There is one entry for each IP V6 CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored, otherwise: Upon receipt of an IPv6 packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table, but docsDevCpeEnroll is set to any and the sum of the table sizes for docsDevCpeTable and docsDevCpeV6Tble is less than docsDevCpeIpMax, the address is added to the table and packet processing continues. Otherwise, the packet is dropped. The filtering actions specified by this table occur after any LLC filtering (docsDevFilterLLCTable), but prior to any IP filtering (docsDevFilterIpTable, docsDevNmAccessTable)." INDEX { docsDevCpeV6Ip } ::= {docsDevCpeTable 1 } DocsDevCpeV6Entry ::= SEQUENCE { docsDevCpeV6Ip IpAddress, docsDevCpeV6Source INTEGER, docsDevCpeV6Status RowStatus } docsDevCpeV6Ip OBJECT-TYPE SYNTAX IpV6Address MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP address to which this entry applies. N.B. Neither the all zeros or all ones addresses may be used as values for this object." ::= { docsDevCpeV6Entry 1 } docsDevCpeV6Source OBJECT-TYPE SYNTAX INTEGER { other(1), manual(2), learned(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object describes how this entry was created. If the value is manual(2), this row was created by a network management action (either configuration, or SNMP set). If set to learned(3), then it was found via looking at the source IP address of a received packet." ::= { docsDevCpeV6Entry 2 } docsDevCpeV6Status OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Standard object to manipulate rows. To create a row in this table, you only need to specify this object. Management stations SHOULD use the create-and-go mechanism for creating rows in this table." ::= { docsDevCpeV6Entry 3 } -- -- Placeholder for notifications/traps. -- docsDevNotification OBJECT IDENTIFIER ::= { docsDev 2 } -- -- Conformance definitions -- docsDevConformance OBJECT IDENTIFIER ::= { docsDev 3 } docsDevGroups OBJECT IDENTIFIER ::= { docsDevConformance 1 } docsDevCompliances OBJECT IDENTIFIER ::= { docsDevConformance 2 } docsDevBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for MCNS Cable Modems and Cable Modem Termination Systems." MODULE -- docsDev -- conditionally mandatory groups GROUP docsDevBaseGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems." GROUP docsDevEventGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems." GROUP docsDevFilterGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems." GROUP docsDevNmAccessGroup DESCRIPTION "This group is only implemented in devices which do not implement SNMPv3 User Security Model. It SHOULD NOT be implemented by SNMPv3 conformant devices. For devices which do not implement SNMPv3 or later, this group is Mandatory in Cable Modems and is optional in Cable Modem Termination Systems." GROUP docsDevServerGroup DESCRIPTION "This group is implemented only in Cable Modems and is not implemented in Cable Modem Termination Systems." GROUP docsDevSoftwareGroup DESCRIPTION "This group is Mandatory in Cable Modems and optional in Cable Modem Termination Systems." GROUP docsDevCpeGroup DESCRIPTION "This group is Mandatory in Cable Modems, and is not implemented in Cable Modem Termination Systems. A similar capability for CMTS devices may be proposed later after study." OBJECT docsDevSTPControl MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support noStFilterBpdu(2)." OBJECT docsDevEvReporting MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support local(0)." OBJECT docsDevFilterLLCInterfaceSet WRITE-SYNTAX INTEGER { allCpe(2), allNetwork (3), allCpeEthernet (4), allCpeUsb (5), allCpeFirewire (6), allExternal (7), allInternal (8), all (9), application1 (10), application2 (11), application3 (12), application4 (13) } DESCRIPTION "'other' is a return value only and may not be SET." OBJECT docsDevFilterIpInterfaceSet WRITE-SYNTAX INTEGER { allCpe(2), allNetwork (3), allCpeEthernet (4), allCpeUsb (5), allCpeFirewire (6), allExternal (7), allInternal (8), all (9), application1 (10), application2 (11), application3 (12), application4 (13) } DESCRIPTION "'other' is a return value only and may not be SET." ::= { docsDevCompliances 1 } docsDevBaseGroup OBJECT-GROUP OBJECTS { docsDevRole, docsDevDateTime, docsDevResetNow, docsDevSerialNumber, docsDevSTPControl } STATUS current DESCRIPTION "A collection of objects providing device status and control." ::= { docsDevGroups 1 } docsDevNmAccessGroup OBJECT-GROUP OBJECTS { docsDevNmAccessIp, docsDevNmAccessIpMask, docsDevNmAccessCommunity, docsDevNmAccessControl, docsDevNmAccessInterfaces, docsDevNmAccessStatus } STATUS current DESCRIPTION "A collection of objects for controlling access to SNMP objects." ::= { docsDevGroups 2 } docsDevSoftwareGroup OBJECT-GROUP OBJECTS { docsDevSwServer, docsDevSwFilename, docsDevSwAdminStatus, docsDevSwOperStatus, docsDevSwCurrentVers } STATUS current DESCRIPTION "A collection of objects for controlling software downloads." ::= { docsDevGroups 3 } docsDevServerGroup OBJECT-GROUP OBJECTS { docsDevServerBootState, docsDevServerDhcp, docsDevServerTime, docsDevServerTftp, docsDevServerConfigFile } STATUS current DESCRIPTION "A collection of objects providing status about server provisioning." ::= { docsDevGroups 4 } docsDevEventGroup OBJECT-GROUP OBJECTS { docsDevEvControl, docsDevEvSyslog, docsDevEvThrottleAdminStatus, docsDevEvThrottleInhibited, docsDevEvThrottleThreshold, docsDevEvThrottleInterval, docsDevEvReporting, docsDevEvFirstTime, docsDevEvLastTime, docsDevEvCounts, docsDevEvLevel, docsDevEvId, docsDevEvText } STATUS current DESCRIPTION "A collection of objects used to control and monitor events." ::= { docsDevGroups 5 } docsDevFilterGroup OBJECT-GROUP OBJECTS { docsDevFilterLLCUnmatchedAction, docsDevFilterIpDefault, docsDevFilterLLCStatus, -- docsDevFilterLLCIfIndex, docsDevFilterLLCProtocolType, docsDevFilterLLCProtocol, docsDevFilterLLCMatches, docsDevFilterLLCInterfaces, docsDevFilterLLCInterfaceSet, docsDevFilterIpControl, -- docsDevFilterIpIfIndex, docsDevFilterIpStatus, docsDevFilterIpDirection, docsDevFilterIpBroadcast, docsDevFilterIpSaddr, docsDevFilterIpSmask, docsDevFilterIpDaddr, docsDevFilterIpDmask, docsDevFilterIpProtocol, docsDevFilterIpSourcePortLow, docsDevFilterIpSourcePortHigh, docsDevFilterIpDestPortLow, docsDevFilterIpDestPortHigh, docsDevFilterIpMatches, docsDevFilterIpInterfaces, docsDevFilterIpInterfaceSet, docsDevFilterIpTos, docsDevFilterIpTosMask, docsDevFilterIpContinue, docsDevFilterIpPolicyId, docsDevFilterPolicyId, docsDevFilterPolicyStatus, docsDevFilterPolicyPtr, docsDevFilterTosStatus, docsDevFilterTosAndMask, docsDevFilterTosOrMask } STATUS current DESCRIPTION "A collection of objects to specify filters at link layer and IP layer." ::= { docsDevGroups 6 } docsDevCpeGroup OBJECT-GROUP OBJECTS { docsDevCpeEnroll, docsDevCpeIpMax, docsDevCpeSource, docsDevCpeStatus } STATUS current DESCRIPTION "A collection of objects used to control the number and specific values of IP addresses allowed for associated Customer Premises Equipment (CPE)." ::= { docsDevGroups 7 } docsDevFilterDeprecateGroup OBJECT-GROUP OBJECTS { docsDevFilterLLCIfIndex, docsDevFilterIpIfIndex } STATUS deprecated DESCRIPTION "These objects have been deprecated to deal with the redefinition of the CM as a multiple CPE device. They MAY be implemented, but will be removed in the next iteration of this MIB." ::= { docsDevGroups 8 } END --=====================_27504359==_-- From owner-ipcdn@terayon.com Mon Apr 10 03:01:40 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02543 for ; Mon, 10 Apr 2000 03:01:39 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id AAA07284 for ; Mon, 10 Apr 2000 00:01:36 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 10 Apr 2000 07:01:36 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id AAA18976; Mon, 10 Apr 2000 00:01:28 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id XAA14310 for ipcdn-outgoing; Sun, 9 Apr 2000 23:59:47 -0700 (PDT) Message-Id: <4.3.1.2.20000409235725.00c76560@poptart> X-Sender: stjohns@poptart X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sun, 09 Apr 2000 23:59:51 -0700 To: ipcdn@terayon.com From: "Mike St. Johns" Subject: BPI Draft - WG Last call complete. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com Having received no further comments on the BPI draft, I'm going to ask the area directors to forward the document to the IESG for publication as an RFC with status of Informational/Historical. That will close out further development on the BPI MIBs. The BPI+ development continues - I am going to be asking the area directors to assign MIB doctors to that draft momentarily. Mike From owner-ipcdn@terayon.com Mon Apr 10 03:03:27 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02579 for ; Mon, 10 Apr 2000 03:03:25 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id AAA07455 for ; Mon, 10 Apr 2000 00:03:24 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 10 Apr 2000 07:03:24 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id AAA19210; Mon, 10 Apr 2000 00:03:15 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id AAA14382 for ipcdn-outgoing; Mon, 10 Apr 2000 00:01:52 -0700 (PDT) Message-Id: <4.3.1.2.20000410000035.00baccc0@poptart> X-Sender: stjohns@poptart X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 10 Apr 2000 00:02:00 -0700 To: ipcdn@terayon.com From: "Mike St. Johns" Subject: Fwd: Minutes for IPCDN - 47th IETF Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com The following was submitted as the minutes for the IPCDN meeting at the IETF in Adelaide. Slides will be available with the proceedings. Mike >Date: Wed, 29 Mar 2000 23:15:31 -0800 >To: minutes@ietf.org >From: "Mike St. Johns" >Subject: Minutes for IPCDN - 47th IETF >Cc: narten@raleigh.ibm.com, nordmark@eng.sun.com > >Working group: IP Over Cable Data Networks (IPCDN) >Chair: Michael StJohns, Excite@Home > > >The working group met for about 90 minutes to review current work and to >resolve some issues related to the current standards track MIBs. > >The chair presented the proposed changes to RFC2669 and 2670 to bring them >into compliance with IPv6 and SNMPv3 requirements (see the attached >presentation). The working group has an action item to nominate specific >objects within the RF Interface MIB to become Counter64 by the end of next >week. The revisions will be posted as IDs within the next week after that. > >The chair proxied for Wilson Sawyer of Arris and presented a description >of the intent of the new subscriber management MIB. A new version has >been submitted to the ID editor and will go through WG last call two weeks >after its published. The chair will ask the area director to assign a MIB >doctor as part of the standards submission process. > >Rich Woundy discussed the current status of the BPI (Baseline Privacy) >MIB. After discussion, the working group agreed this should be submitted >as Informational/Historical as it documents a branch no longer being >developed, but which has been implemented. The BPI+ MIB has been >submitted as an internet draft and will be put through the WG last call >process within the next 3 weeks. > >At the last meeting, Rich and Andrew Valentine agreed to go off and >evaluate whether or not the EuroModem MIBs and the IPCDN MIBs could be >harmonized. Rich and Andrew presented their results and a discussion of >possible approches for harmonization. The working group agreed to accept >the EuroModem MIBs as work items and Andrew will resubmit the current IDs >as draft-ietf-ipcdn-... documents. The chair will submit a revised >charter within the next month which covers the EuroModem work. > >Rich gave a brief presentation on some work he's done in DHCP for third >parties to verify MAC/IP bindings. This work will not be added to the WGs >table, but will be submitted to the DHCP WG or area for advancement. The >WG will monitor the work and its applicability on CMs, but does not expect >an major effects on the WG's work. > >The chair led a brief discussion of other items on the charter. The Telco >Return MIB was submitted several years ago, but was allowed to lapse due >to lack of interest or implementation desire. Due to the renewed >interest, as well as more experience with Telco Return, the author will >resubmit the ID for WG discussion and possible adoption as a work >item. The QOS MIB is current, but there's been a lack of discussion or >interest in the MIB. The chair will try and rekindle discussion on the >MIB or drive it to closure or removal from consideration depending on WG >consensus. > From owner-ipcdn@terayon.com Mon Apr 10 09:37:24 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11049 for ; Mon, 10 Apr 2000 09:37:22 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id GAA10969; Mon, 10 Apr 2000 06:36:09 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 10 Apr 2000 13:36:09 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id GAA24582; Mon, 10 Apr 2000 06:36:08 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id GAA16488 for ipcdn-outgoing; Mon, 10 Apr 2000 06:33:40 -0700 (PDT) Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96BDC@indyexch5.indy.tce.com> From: Yost William To: "'ipcdn@terayon.com'" Subject: RE: Bare MIB - Cable Device MIB Date: Mon, 10 Apr 2000 08:33:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com It's not clear for a V1/V2 agent when you use docsDevNmAccessTable to determine where to send traps and when you use the Notification MIB. It is clear that you don't use docsDevNmAccessTable for access control if there are entries in the Community MIB. The Notification MIB does not provide the trap rate limiting control that docsDevEvThrottle... objects do. The Notification MIB tells which types of traps each trap receiver wants to receive but not how many per minute to limit them to. ----------- William H. Yost, Thomson Consumer Electronics ------------ . Home of RCA, GE, and Proscan (317) 587-4816 yostw@tce.com . .There's 3 ways to do it: The DOCSIS way, The Right way, and My Way . -----Original Message----- From: Mike St. Johns [mailto:stjohns@corp.home.net] Sent: Monday, April 10, 2000 12:15 AM To: ipcdn@terayon.com Subject: Bare MIB - Cable Device MIB Attached is the revise CABLE-DEVICE-MIB. This includes changes to support both IPv6 and SNMPv3 as well as some text clean up where people identified ambiguities. Some comments: Where possible I've left existing objects alone and added new IPv6 objects. Where this did not make sense, the descriptions of the IPv6 objects are written to try and deal with backwards compatibility issues. For SNMPv3 - a number of tables and objects are being deprecated in favor of the standard MIBs. Specifically, docsDevNmAccess as well as a number of the event control tables are being deprecated. The MIB is not complete in its current form - its missing the revised compliance section modifications. If you run this through a mib compiler, use the flags which turn off compliance section checking. Once the body of the mib is in its final form, I'll complete the compliance objects and the ID text. Comments to the list - try and get them in by 1 May - silence implies consent. Mike From owner-ipcdn@terayon.com Mon Apr 10 13:16:57 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25714 for ; Mon, 10 Apr 2000 13:16:55 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id KAA14643 for ; Mon, 10 Apr 2000 10:16:54 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 10 Apr 2000 17:16:53 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id KAA02583; Mon, 10 Apr 2000 10:16:49 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id KAA19307 for ipcdn-outgoing; Mon, 10 Apr 2000 10:15:05 -0700 (PDT) Message-Id: <200004101715.KAA28015@lock.eos.home.net> X-Mailer: exmh version 2.0delta 6/3/97 To: ipcdn@terayon.com Subject: Re: Bare MIB - Cable Device MIB In-reply-to: Your message of Mon, 10 Apr 2000 08:33:48 -0500. <4FA371B64BDAD2119CF40008C7D9ADB302B96BDC@indyexch5.indy.tce.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Apr 2000 10:15:16 -0700 From: "Mike StJohns" Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com OK - I'll add text. If there are no entries in the TARGET MIB, you continue to use the docsDevNmAccess table for trap location. Let me mull the exact approach over for a few hours. For the event stuff... *sigh* - I mis-read the notifications MIB - specifically the objects on retry interval/times. Two choices here - either restore the event throttling stuff to the state it is in the current mib, or add a table augmenting the target table for a per destination throttling ability. Comments? Mike > It's not clear for a V1/V2 agent when you use docsDevNmAccessTable to > determine where to send traps and when you use the Notification MIB. It is > clear that you don't use docsDevNmAccessTable for access control if there > are entries in the Community MIB. > > The Notification MIB does not provide the trap rate limiting control that > docsDevEvThrottle... objects do. The Notification MIB tells which types of > traps each trap receiver wants to receive but not how many per minute to > limit them to. > > ----------- William H. Yost, Thomson Consumer Electronics ------------ > . Home of RCA, GE, and Proscan (317) 587-4816 yostw@tce.com . > .There's 3 ways to do it: The DOCSIS way, The Right way, and My Way . > > > -----Original Message----- > From: Mike St. Johns [mailto:stjohns@corp.home.net] > Sent: Monday, April 10, 2000 12:15 AM > To: ipcdn@terayon.com > Subject: Bare MIB - Cable Device MIB > > > > Attached is the revise CABLE-DEVICE-MIB. This includes changes to support > both IPv6 and SNMPv3 as well as some text clean up where people identified > ambiguities. > > Some comments: Where possible I've left existing objects alone and added > new IPv6 objects. Where this did not make sense, the descriptions of the > IPv6 objects are written to try and deal with backwards compatibility > issues. > > For SNMPv3 - a number of tables and objects are being deprecated in favor > of the standard MIBs. Specifically, docsDevNmAccess as well as a number of > the event control tables are being deprecated. > > > The MIB is not complete in its current form - its missing the revised > compliance section modifications. If you run this through a mib compiler, > use the flags which turn off compliance section checking. Once the body of > the mib is in its final form, I'll complete the compliance objects and the > ID text. > > Comments to the list - try and get them in by 1 May - silence implies > consent. > > > Mike From owner-ipcdn@terayon.com Mon Apr 10 13:29:49 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26413 for ; Mon, 10 Apr 2000 13:29:46 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id KAA15041 for ; Mon, 10 Apr 2000 10:29:43 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 10 Apr 2000 17:29:43 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id KAA03462; Mon, 10 Apr 2000 10:29:37 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id KAA19681 for ipcdn-outgoing; Mon, 10 Apr 2000 10:27:52 -0700 (PDT) Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96BE2@indyexch5.indy.tce.com> From: Yost William To: "'ipcdn@terayon.com'" Subject: RE: Bare MIB - Cable Device MIB Date: Mon, 10 Apr 2000 12:29:02 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com I don't understand why the writers of the Notification MIB didn't add trap throttling in the first place. Are there any comments from those writers or people associated with maintaining the SNMP V3 RFC's as to if they are possibly considering adding this feature soon anyway? If so, you could just use the Notification MIB and get rid of the docsDevEvThrottle... MIB objects. ----------- William H. Yost, Thomson Consumer Electronics ------------ . Home of RCA, GE, and Proscan (317) 587-4816 yostw@tce.com . .There's 3 ways to do it: The DOCSIS way, The Right way, and My Way . -----Original Message----- From: Mike StJohns [mailto:stjohns@corp.home.net] Sent: Monday, April 10, 2000 12:15 PM To: ipcdn@terayon.com Subject: Re: Bare MIB - Cable Device MIB OK - I'll add text. If there are no entries in the TARGET MIB, you continue to use the docsDevNmAccess table for trap location. Let me mull the exact approach over for a few hours. For the event stuff... *sigh* - I mis-read the notifications MIB - specifically the objects on retry interval/times. Two choices here - either restore the event throttling stuff to the state it is in the current mib, or add a table augmenting the target table for a per destination throttling ability. Comments? Mike > It's not clear for a V1/V2 agent when you use docsDevNmAccessTable to > determine where to send traps and when you use the Notification MIB. It is > clear that you don't use docsDevNmAccessTable for access control if there > are entries in the Community MIB. > > The Notification MIB does not provide the trap rate limiting control that > docsDevEvThrottle... objects do. The Notification MIB tells which types of > traps each trap receiver wants to receive but not how many per minute to > limit them to. > > ----------- William H. Yost, Thomson Consumer Electronics ------------ > . Home of RCA, GE, and Proscan (317) 587-4816 yostw@tce.com . > .There's 3 ways to do it: The DOCSIS way, The Right way, and My Way . > > > -----Original Message----- > From: Mike St. Johns [mailto:stjohns@corp.home.net] > Sent: Monday, April 10, 2000 12:15 AM > To: ipcdn@terayon.com > Subject: Bare MIB - Cable Device MIB > > > > Attached is the revise CABLE-DEVICE-MIB. This includes changes to support > both IPv6 and SNMPv3 as well as some text clean up where people identified > ambiguities. > > Some comments: Where possible I've left existing objects alone and added > new IPv6 objects. Where this did not make sense, the descriptions of the > IPv6 objects are written to try and deal with backwards compatibility > issues. > > For SNMPv3 - a number of tables and objects are being deprecated in favor > of the standard MIBs. Specifically, docsDevNmAccess as well as a number of > the event control tables are being deprecated. > > > The MIB is not complete in its current form - its missing the revised > compliance section modifications. If you run this through a mib compiler, > use the flags which turn off compliance section checking. Once the body of > the mib is in its final form, I'll complete the compliance objects and the > ID text. > > Comments to the list - try and get them in by 1 May - silence implies > consent. > > > Mike From owner-ipcdn@terayon.com Mon Apr 10 15:26:31 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01028 for ; Mon, 10 Apr 2000 15:26:30 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id MAA17267; Mon, 10 Apr 2000 12:19:02 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 10 Apr 2000 19:19:02 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id MAA09346; Mon, 10 Apr 2000 12:19:01 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id MAA21656 for ipcdn-outgoing; Mon, 10 Apr 2000 12:16:35 -0700 (PDT) Date: Mon, 10 Apr 2000 12:16:56 -0700 (PDT) From: Arash Khaghani Message-Id: <200004101916.MAA04044@jazz.com21.com> To: ipcdn@terayon.com Subject: RE: Bare MIB - Cable Device MIB Cc: arash@jazz.com21.com X-Sun-Charset: US-ASCII Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com I would also agree that NOTIFICATION MIB is the place for trottling traps, if nothing else for better cohesion and robustness of code. Barring this option, I would suggest keeping the docsDevEvThrottle* tables we've currently implemented and incorporated into SNMP V1, V2C and/or V3 instead of augmenting the NOTIFICATION or TARGET MIBS. Again, I would opt for redefining the NOTIFICATION MIB to include trottling but could this be done in a timely manner so as not to have an impact on the DOCSIS schedule? To what extent would this impact DOCSIS vendor's implementation efforts? --Arash K. > From owner-ipcdn@terayon.com Mon Apr 10 10:27:32 2000 > From: Yost William > To: "'ipcdn@terayon.com'" > Subject: RE: Bare MIB - Cable Device MIB > Date: Mon, 10 Apr 2000 12:29:02 -0500 > MIME-Version: 1.0 > > I don't understand why the writers of the Notification MIB didn't add trap > throttling in the first place. Are there any comments from those writers or > people associated with maintaining the SNMP V3 RFC's as to if they are > possibly considering adding this feature soon anyway? If so, you could just > use the Notification MIB and get rid of the docsDevEvThrottle... MIB > objects. > > ----------- William H. Yost, Thomson Consumer Electronics ------------ > . Home of RCA, GE, and Proscan (317) 587-4816 yostw@tce.com . > .There's 3 ways to do it: The DOCSIS way, The Right way, and My Way . > > > -----Original Message----- > From: Mike StJohns [mailto:stjohns@corp.home.net] > Sent: Monday, April 10, 2000 12:15 PM > To: ipcdn@terayon.com > Subject: Re: Bare MIB - Cable Device MIB > > > > OK - I'll add text. If there are no entries in the TARGET MIB, you continue > > to use the docsDevNmAccess table for trap location. Let me mull the exact > approach over for a few hours. > > For the event stuff... *sigh* - I mis-read the notifications MIB - > specifically the objects on retry interval/times. Two choices here - either > > restore the event throttling stuff to the state it is in the current mib, or > > add a table augmenting the target table for a per destination throttling > ability. Comments? > > Mike > > > > It's not clear for a V1/V2 agent when you use docsDevNmAccessTable to > > determine where to send traps and when you use the Notification MIB. It > is > > clear that you don't use docsDevNmAccessTable for access control if there > > are entries in the Community MIB. > > > > The Notification MIB does not provide the trap rate limiting control that > > docsDevEvThrottle... objects do. The Notification MIB tells which types > of > > traps each trap receiver wants to receive but not how many per minute to > > limit them to. > > > > ----------- William H. Yost, Thomson Consumer Electronics ------------ > > . Home of RCA, GE, and Proscan (317) 587-4816 yostw@tce.com . > > .There's 3 ways to do it: The DOCSIS way, The Right way, and My Way . > > > > > > -----Original Message----- > > From: Mike St. Johns [mailto:stjohns@corp.home.net] > > Sent: Monday, April 10, 2000 12:15 AM > > To: ipcdn@terayon.com > > Subject: Bare MIB - Cable Device MIB > > > > > > > > Attached is the revise CABLE-DEVICE-MIB. This includes changes to support > > > both IPv6 and SNMPv3 as well as some text clean up where people identified > > > ambiguities. > > > > Some comments: Where possible I've left existing objects alone and added > > new IPv6 objects. Where this did not make sense, the descriptions of the > > IPv6 objects are written to try and deal with backwards compatibility > > issues. > > > > For SNMPv3 - a number of tables and objects are being deprecated in favor > > of the standard MIBs. Specifically, docsDevNmAccess as well as a number > of > > the event control tables are being deprecated. > > > > > > The MIB is not complete in its current form - its missing the revised > > compliance section modifications. If you run this through a mib compiler, > > > use the flags which turn off compliance section checking. Once the body > of > > the mib is in its final form, I'll complete the compliance objects and the > > > ID text. > > > > Comments to the list - try and get them in by 1 May - silence implies > > consent. > > > > > > Mike > > From owner-ipcdn@terayon.com Thu Apr 13 14:32:34 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10542 for ; Thu, 13 Apr 2000 14:32:33 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id LAA07248 for ; Thu, 13 Apr 2000 11:32:30 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 13 Apr 2000 18:32:30 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id LAA08801; Thu, 13 Apr 2000 11:32:22 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id LAA00268 for ipcdn-outgoing; Thu, 13 Apr 2000 11:29:58 -0700 (PDT) X-Server-Uuid: cda7734f-06b2-11d3-bc59-00805fbb2b22 Message-ID: From: "Siripunkaw, Pak" To: "'ipcdn@terayon.com'" Subject: Testing.. Please do not reply Date: Thu, 13 Apr 2000 14:29:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) X-WSS-ID: 14E8CD8196919-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com Content-Transfer-Encoding: 7bit From owner-ipcdn@terayon.com Tue Apr 18 10:51:06 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05527 for ; Tue, 18 Apr 2000 10:51:03 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id HAA01850; Tue, 18 Apr 2000 07:45:13 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 18 Apr 2000 14:45:13 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id HAA23220; Tue, 18 Apr 2000 07:45:12 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id HAA12008 for ipcdn-outgoing; Tue, 18 Apr 2000 07:41:48 -0700 (PDT) X-Server-Uuid: cda7734f-06b2-11d3-bc59-00805fbb2b22 Message-ID: From: "Siripunkaw, Pak" To: "'ipcdn@terayon.com'" cc: "Field, Brian" Subject: Comments on new CD MIB (in relation to RFC-2576, Target and notif ication MIBs) Date: Tue, 18 Apr 2000 10:41:13 -0400 Importance: low X-Priority: 5 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) X-WSS-ID: 14E2AB831181410-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com Content-Transfer-Encoding: 7bit Comments on new CD MIB (in relation to RFC-2576, Target and notification MIBs) (By Pak Siripunkaw and Bill Yost) Motivation of the comments: It is getting too complicated to determine what controls access to the modem (docsDevNmAccessTable or SNMP V3 Tables) and where traps are sent (docsDevNmAccessTable or SNMP V3 Tables). This should be determined by which mode (SNMP V1/V2c mode versus SNMP V3 Mode) the modem is in instead of whether or not docsDevNmAccessTable is empty or not. 1.) If the configuration file does not contain TLV34.1 and 34.2, then the CM operates in v1/v2c mode: During the CM registration: * Before the setting of docsDevNmAccessTable, CM MUST only allow RO access from any SNMPv1/v2c manager. CM does not allow any access from SNMPv3 manager. * docsDevNmAccessTable entries are set to control SNMP Access and trap target * Any entries made to the Community MIB, Target and Notification MIB will be ignored After the CM registration: * docsDevNmAccessTable control SNMP Access and trap target * Community MIB, Target and notification MIB, and other SNMPv3 related MIB are not accessible by any SNMP manager 2.) If the configuration file does contain TLV34.1 and 34.2, then the CM operates in v3 mode with v1/v2c coexistence: During the CM registration and while SNMP V3 initial user keys are being calculated: * Before the setting of the Community MIB, CM MUST only allow RO access from any SNMPv1/v2 manager. CM does not allow any access from SNMPv3 manager * Community MIB, Target and notification MIB, and other SNMPv3 related MIB are not accessible by any SNMP manager * Community MIB entries are set to control SNMP Access. Target and notification MIB entries are set to control SNMP trap target. * Any entries made to the docsDevNmAccessTable will be ignored. After the Registration is complete and SNMPv3 initialization has completed: * Community MIB control the translation of SNMPv1/v2c packets' community strings into security name which select entries in the VACM mib * USM table controls SNMPv3 packets * docsDevNmAccessTable is not accessible by any NMS stations 3.) Two new config file elements to ease filling in SNMP V3 tables during registration: a. Defining a Trap Receiver in the Configuration file A config file element named V3TrapReceiver can be defined to define a trap receiver in V3 mode. This element specifies a Network Management Station that will receive traps from the modem when it is in V3 mode. Up to 10 of these elements may be included in the configuration file. Here is the format of this element: Definition of fields of V3TrapReceiver Element All multi-byte fields have the most significant bytes first in the field. Field Bytes Description IP Address 4 IP Address of the trap receiver Port 2 UDP Port number of the trap receiver (Normally you would use the standard value 162) Trap type 2 Determines the type of trap sent by the modem (1) 1 = SNMP V1 trap in an SNMP V1 packet 2 = SNMP V2 trap in an SNMP V2 packet 3 = SNMP inform in an SNMP V2 packet 4 = SNMP V2 trap in an SNMP V3 packet 5 = SNMP inform in an SNMP V3 packet Timeout 2 Timeout, in milliseconds used for sending inform Retries 2 Number of retries beyond the first transmission of informs. Filter length 2 n = Number of 4 byte components in the Filter OID (value = n) 0 means the Filter OID is the root of the entire MIB tree supported by the modem. All traps will be sent to the trap receiver. Filter OID 4*n Each 4 bytes is a component of the Object Identifier of the root of the Trap Filter Sub-Tree (2) (1) Trap Type: The community String for traps in SNMP V1 and V2 packets will be "public". The Security Name in traps and informs in SNMP V3 packets will be "@config". All V3 packet traps will be of Security Level noAuthNoPriv. (2) Filter OID: SNMP V3 allows the specification of which Trap OID's are to be sent to a trap receiver. The filter OID in the config element specifies the OID of the root of a trap filter sub-tree. All Traps with a Trap OID contained in this trap filter sub-tree will be sent to the trap receiver. b. Config file Element to replicate the docsDevNmAccessTable into the SNMP V3 tables This config file element has no parameters included with it. It merely directs the modem to examine the contents of the docsDevNmAccessTable after registration is complete and make appropriate entries in the snmpCommunityTable, snmpTargetAddrTable, snmpTargetAddrExtTable, snmpTargetParamsTable, snmpNotifyTable, usmUserTable, vacmSecurityToGroupTable, vacmAccessTable. The entries that are made will provide the equivalent SNMP v1/v2C access control and SNMP v1 trap receivers as specified in the docsDevNmAccessTable. This element only takes effect if the modem is put into SNMP V3 mode. After taking effect, the docsDevNmAccessTable will not be accessible and will have no control over the modem from that point forward. This allows operators to set up these SNMP V3 table entries in a much more convenient and familiar way. The exact entries made in these tables are not specified here, but must be made so that when these tables are used as specified in the SNMP V3 RFC's, the effect is the same as if docsDevNmAccessTable had been used instead. The docsDevNmAccessInterfaces column will be treated as if set to allow access from all interfaces since the SNMP V3 tables do not allow limiting access on a per interface basis. 4.) General comments for NmAccessTable: docsDevNmAccessIP/docsDevNmAccessIpMask. If we are going to continue to support NmAccessTable, then the description of this object on how to setup to allow any NMS needs to be changed. The correct rule for this access control is the following : If ((NmAccessIP AND NmAccessIpMask)) == ((SrcIpAddr AND NmAccessIpMask)) Permit the access from SrcIpAddr Else Do NOT permit the access from SrcIpAddr So to allow any NMS the Ipmast MUST be 0.0.0.0 and IP can be 0.0.0.0 or any IP There has to be a clear statement to make sure that Trap can only be sent to a specific device. 5.) Need to add DocsDevNmAccessTrapVersion to control the trap version when the CM is in v1/v2c and NmAccess is being used. This object is being proposed by the OSSI 1.1 document. 6.) If NmaccessTable is being used, docsDevNmAccessInterfaces object does not have the same capability as the IpfilterInterfaces and LLCfilterInterfaces. Why don't make it the same? 7.) Trap throttling and limiting control MUST be done from the objects in CD-MIB. This is a cleaner way to do this. From owner-ipcdn@terayon.com Wed Apr 19 18:33:16 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15378 for ; Wed, 19 Apr 2000 18:33:14 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id PAA26224; Wed, 19 Apr 2000 15:27:49 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 19 Apr 2000 22:27:49 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id PAA11196; Wed, 19 Apr 2000 15:27:48 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id PAA00738 for ipcdn-outgoing; Wed, 19 Apr 2000 15:24:31 -0700 (PDT) Message-ID: <38FE3233.4DC1F3D9@cisco.com> Date: Wed, 19 Apr 2000 15:24:51 -0700 From: apalmer Organization: Cisco Systems X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: stjohns@corp.home.net, ipcdn@terayon.com Subject: EuroDocsis References: <4.3.1.2.20000410000035.00baccc0@poptart> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com Content-Transfer-Encoding: 7bit Mike, Since we are cleaning up the mibs :), I would like to propose that we enhance the RFC2670 to include the requirements from EuroDOCSIS. Here are the two additional enhancements that were suggested: 1) New interleave: docsIfDownChannelInterleave OBJECT-TYPE SYNTAX INTEGER { unknown(1), other(2), taps8Increment16(3), taps16Increment8(4), taps32Increment4(5), taps64Increment2(6), taps128Increment1(7), taps12increment17(8) } MAX-ACCESS read-write STATUS current DESCRIPTION "The Forward Error Correction (FEC) interleaving used for this downstream channel. Values are defined as follows: taps8Increment16(3): protection 5.9/4.1 usec, latency .22/.15 msec taps16Increment8(4): protection 12/8.2 usec, latency .48/.33 msec taps32Increment4(5): protection 24/16 usec, latency .98/.68 msec taps64Increment2(6): protection 47/33 usec, latency 2/1.4 msec taps128Increment1(7): protection 95/66 usec, latency 4/2.8 msec taps12increment17(8): protection 18/14 usec, latency 0.43/0.32 msec If the interface is down, this object either returns the configured value (CMTS), the most current value (CM), or the value of unknown(1). The value of other(2) is returned if the interleave is known but not defined in the above list. See the associated conformance object for write conditions and limitations. See the reference for the FEC configuration described by the setting of this object." REFERENCE "DOCSIS Radio Frequency Interface Specification, Section 4.3.2." ::= { docsIfDownstreamChannelEntry 5 } 2.2 docsIfDownChannelAnnex This object is implemented to differ for the different implementations of the downstream. docsIfDownChannelAnnex OBJECT-TYPE SYNTAX INTEGER { unknown(1), other(2), annexA(3), annexB(4), annexC(5), } MAX-ACCESS read-only Thanks, Azlina