1 / 6

IPCDN Cable Device MIB Update February 13, 2003

This update from February 13, 2003, by Richard Woundy of Comcast Cable, outlines modifications to the Cable Device Management Information Base (MIB). Changes include removing the InterfaceSet textual convention, reverting to RFC 2669 standards, updating the VACM MIB augmentation, clarifying NM access tables, emphasizing backward compatibility, streamlining TFTP/HTTP software download, and deprecating outdated objects. Additional editorial changes and clarifications are made for improved MIB functionality. Review and approval from the working group are needed for VACM extension matters. Next steps involve finalizing the VACM extension and potentially initiating a WG last call.

easterm
Download Presentation

IPCDN Cable Device MIB Update February 13, 2003

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPCDN Cable Device MIB UpdateFebruary 13, 2003 Richard Woundy Comcast Cable

  2. Recent MIB Changes • Removed the InterfaceSet textual convention • Reverted back to the docsDevFilterLLCIfIndex and docsDevFilterIpIfIndex objects from RFC 2669 • Modified the VACM MIB augmentation to use new docsDevVacmAccessIfIndex object • Clarified aspects of the docsDevNmAccessTable • Clarified the relationship to SNMP Coexistence • Emphasized backward compatibility in the docsDevNmAccessGroupV2 compliance • Simplified the TFTP/HTTP software download mechanisms • Deprecated docsDevEvThrottleInhibited in favor of docsDevEvThrottleThresholdExceeded • Made the docsDevCpe tables optional

  3. Single New Object for TFTP/HTTP Download docsDevSwServerTransportProtocol OBJECT-TYPE SYNTAX INTEGER { tftp(1), http(2) } MAX-ACCESS read-write STATUS current DESCRIPTION “This object specifies the transport protocol (TFTP or HTTP) to be used for software upgrades… The default value of this object is tftp.” ::= { docsDevSoftware 8 }

  4. Minor Editorial Changes • Added the docsDevVacmAccessExt group to the "Structure of the MIB" section • Replaced Integer32 with InetPortNumber SYNTAX for the port number objects in the IP Filter table • Added a MIB comment naming the OID for the old conformance statements • Modified the LAST-UPDATED and REVISION clauses • Fixed a number of minor MIB compiler errors, and updated MIB compliances

  5. Need WG Consensus on VACM Extension docsDevVacmAccessIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current 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(s). In Cable Modem Termination Systems, this object has to be specified to create a row in this table. Note that according to the DOCSIS OSSIv1.1 specification [OSSI1.1], ifIndex '1' means that this row applies to all CPE (customer-facing) interfaces.” ::= { docsDevVacmAccessExtEntry 1 }

  6. Next Steps • Resolve VACM extension issue • Begin WG last-call?

More Related