Last Modified: 2004-07-23
The WG mailing list may be used discussion of Internet-related issues in data-over-cable equipment and systems. In the event of a particular new Internet technology issue arising in the cable-data context, the WG will identify whether that is best handled within the IETF or is best handled by another standards body. In the event that new IETF MIB work, the WG chairs can discuss additional WG work items with the AD. Such additions will have to go through normal re-charter process. If non-MIB work gets identified, such items are not normal work items for this IPCDN-MIB WG and must go through normal IETF new WG chartering process.
Standardization of MIBs for DOCSIS, PacketCable and CableHome systems are explicitly within the scope of the IPCDN Working Group.
The IPCDN WG will also keep informed on what other groups in the industry are doing as it relates to the efforts of this working group.
The WG will align its specifications with IPv6 and SNMP STD.
CableLabs (http://www.cablelabs.com/) is structured into projects. In its Cable Modem/DOCSIS project, CableLabs has produced three generations of data over cable specifications: DOCSIS 1.0, DOCSIS 1.1, and DOCSIS 2.0. In its PacketCable project, CableLabs has produced one generation of interface specifications for delivering real-time multimedia services over DOCSIS (http://www.packetcable.com/specifications/). Internationally, IPCablecom is the global name associated with the extensions & global standardization of PacketCable in ETSI & ITU-T SG9. In its CableHome project, CableLabs has produced one generation of interface specifications for extending manageability for customer care to the residential gateway or home router device connected to the Internet through a DOCSIS-compliant cable modem (http://www.cablelabs.com/projects/cablehome/).
DOCSIS 1.0 includes specifications for a bidirectional data-over-cable interface (RFI, or Radio Frequency Interface) and a data privacy service (BPI, or Baseline Privacy Interface). The key devices in a DOCSIS network are the Cable Modem (CM, the device at the subscriber premise) and the Cable Modem Termination System (CMTS, the device at the cable headend). For DOCSIS 1.0 systems, the IPCDN WG has published the Cable Device MIB (RFC 2669), the RF Interface MIB (RFC 2670), and the Baseline Privacy MIB (RFC 3083).
DOCSIS 1.1 extends the DOCSIS 1.0 specifications to support better quality of service parameters (RFIv1.1), to enable operation in European cable networks (EuroDOCSIS), and to authenticate modems and firmware images (BPI+). The IPCDN WG will update the Cable Device and Radio Frequency MIBs for DOCSIS 1.1, and repair flaws discovered in operational use. Other IPCDN WG documents will address the operational and management issues for new DOCSIS 1.1 functional components (e.g. BPI+), for subscriber device management, and for uniform event notification.
DOCSIS 2.0 enhances the DOCSIS 1.1 specifications at the physical layer, in particular to support two new physical layer encodings: S-CDMA and A-TDMA. The IPCDN WG will update the Radio Frequency MIB for DOCSIS 2.0.
PacketCable 1.0 is built on top of the DOCSIS 1.1 cable modem infrastructure and it includes a suite of interface specifications covering multimedia terminal adapter (MTA) device provisioning, voice over IP session signaling, QoS signaling based on IETF standards. The key systems in a PacketCable network are the multimedia terminal adapter (MTA), a Call Management Server (CMS), a PacketCable-compliant DOCSIS 1.1 CMTS, Media Gateway Controllers, Media Gateways along with back-office systems. In ITU-T SG-9 and ETSI AT, IPCableCom has standardized PacketCable to create a set of international standards.
CableHome 1.0 is a set of specifications for residential gateway or home router functionality standardizing methods for implementing address acquisition, device configuration and management, network address translation, event reporting, remote connectivity diagnostics, secure software download, firewall policy file download, firewall monitoring, management parameter access control and other residential gateway functionality. By standardizing these features, CableHome 1.0 specifications enable cable operators to deliver high-value, managed broadband services to their high-speed data service subscribers, through a DOCSIS cable modem.
The IPCDN WG will address issues related to network management, especially as they concern HFC access networks. It is expected that other services (i.e. RSVP, IPSEC, etc.) will operate mostly unmodified.
The specific work items include
-- DOCSIS, - publish MIB documents for: - subscriber device management on a DOCSIS 1.1 CMTS, - managing the quality of service parameters for a DOCSIS 1.1 device, - managing the Baseline Privacy Plus system for a DOCSIS 1.1 device, - uniform event notification on a DOCSIS 1.1 device, - revise MIB documents for: - DOCSIS 1.0 RF Interface MIB to support EuroDOCSIS parameters and DOCSIS 2.0 physical layer management, - the DOCSIS 1.0 Cable Device MIBs to address SNMPv3 and IPv6 compliance and interoperability issues,
-- IPCablecom & PacketCable - publish MIB documents for: - managing the device parameters of PacketCable/IPCableCom MTA devices, - managing the signaling parameters of PacketCable/IPCableCom MTA devices, - managing events for PacketCable/IPCablecom systems, -- CableHome - publish MIB documents for: - managing attributes of a residential gateway or home router device, - managing private address-to-public address mappings for a residential gateway or home router device, - managing the address lease acquistion client and the address lease server functionality of a residential gateway or home router device, - managing diagnostic utilities used to remotely test the connectivity between a residential gateway and privately-addressed LAN hosts, - managing firewall attributes, monitoring firewall attacks, and managing security certificates in a residential gateway or home router device, - managing QoS configuration in a residential gateway or home router device.
|Done||Post final I-D on Baseline Privacy MIB; Last call|
|Done||Post I-Ds revising RF and CM MIBs to support DOCSIS1.1 and for compliance with SNMPv3 and IPv6|
|Done||Submit Baseline Privacy MIB to IESG for publication as a Standards Track RFC|
|Done||Submit DOCSIS Subscriber Management MIB to IESG for consideration as a Standards Track RFC|
|Done||Submit DOCSIS 1.1 QoS MIB to IESG for consideration as a Standards Track RFC|
|Done||Submit DOCSIS BPI+ MIB to IESG for consideration as a Standards Track RFC|
|Sep 04||Submit updated DOCSIS RF MIB to IESG for consideration as a Standards Track RFC (Proposed Standard)|
|Sep 04||Submit updated DOCSIS Cable Device MIB to IESG for consideration as a Standards Track RFC|
|Sep 04||Submit DOCSIS Event Notification MIB to IESG for consideration as a Standards Track RFC|
|Sep 04||Submit PacketCable/IPCableCom MTA device MIB to IESG for consideration as a Standards Track RFC|
|Sep 04||Submit PacketCable/IPCableCom MTA signaling MIB to IESG for consideration as a Standards Track RFC|
|Sep 04||Submit PacketCable/IPCableCom MTA event MIB to IESG for consideration as a Standards Track RFC|
|Dec 04||Submit Cablehome MIB for managing residential gateway or home router device to IESG for consideration as Standards Track RFC|
|Dec 04||Submit Cablehome MIB for MIB for managing private address-to-public address mappings for a residential gateway or home router device to IESG for consideration as Standards Track RFC|
|Dec 04||Submit Cablehome MIB for managing the address lease acquistion client and the address lease server functionality of a residential gateway or home router device to IESG for consideration as Standards Track RFC|
|Dec 04||Submit Cablehome MIB for managing diagnostic utilities used to remotely test the connectivity between a residential gateway and privately-addressed LAN hosts to IESG for consideration as Standards Track RFC|
|Dec 04||Submit Cablehome MIB for managing firewall attributes,monitoring firewall attacks, and managing security certificates in a residential gateway or home router device to IESG for consideration as Standards Track RFC|
|Jan 05||Revaluate charter and milestones or conclude wg|
|RFC2669||PS||Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems|
|RFC2670||PS||Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces|
|RFC3083||I||Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems|
IETF IPCDN Meeting
The IPCDN WG met to discuss the progress of various MIB documents, especially the DOCSIS and PacketCable/IPCablecom submissions. We briefly covered the recently updated milestones of the WG, which was completed on July 23rd.
We noted that the DOCSIS Subscriber Management MIB and the DOCSIS BPI+ MIB drafts are in IETF Last Call, and the DOCSIS QoS MIB draft has completed WG last call and is in IESG review. Much of the meeting time were concerned with issues in the DOCSIS QoS MIB (usage of IP ToS versus DiffServ semantics), the DOCSIS BPI+ MIB (usage of ZeroBasedCounter32 versus Counter32 syntax), and the DOCSIS Event Notification MIB (whether the event level and event text objects should be included in each notification varbind). We also reviewed the status of the two PacketCable/IPCablecom MIB Updates (MTA MIB and NCS Signaling MIB), which are currently in WG last call and in MIB doctor review.
There is a desire by the WG to conclude all DOCSIS and PacketCable/IPCablecom MIB drafts by September 2004, and to conclude all CableHome MIB drafts by December 2004.
Total meeting time was one hour.
Since the last IPCDN meeting, the remaining open issue with this draft has been its reference to the IP TOS octet, rather than to the IP Differentiated Services field (DSfield). The rationale for this approach is that the DOCSIS specifications specifically refer to the IP ToS octet rather than the DSfield with respect to the objects in this MIB, and that it is critical for this MIB to model the DOCSIS device state accurately.
In the last IPCDN meeting, it was observed that the IP ToS MIB objects in question were all read-only objects, and the authors would add reasonable documentation for the conversion from the IP TOS octet to a DSCP value (see details from previous meeting minutes). After that meeting, it was observed that two MIB objects (docsQosServiceClassTosAndMask and docsQosServiceClassTosOrMask) were in fact read-create objects, and it was possible to set these objects to values that would accidentally overwrite the ECN bits in a packet header.
We proposed that these two MIB objects be re-defined as read-only, and that a new read-create object be defined to enable overwrite of the DSCP value in a packet header. The new MIB object would restrict the overwrite to the DS field only, would not permit overwrite of the ECN bits in the IP header, and would not permit masking of the DSCP value.
We need to obtain feedback on this proposal from the Internet Area Directors. Assuming positive feedback, we need to revise the DOCSIS QoS MIB draft accordingly, and submit draft 10 for IESG approval.
Eduardo Cardona published two drafts (-10 and -11) of the DOCSIS RFIv2 MIB, in response to comments from the IPCDN mailing list during WGLC. The summary of the mailing list comments and his responses are captured in the IPCDN WG presentation slides, and generated no further comment in the meeting.
Jean-Francois agreed to ping the mailing list to see if another WGLC is needed; otherwise this MIB will be submitted for IESG review.
Eduardo Cardona submitted version 13 of the BPI+ MIB draft, in particular to address issues raised in the Area Director review of the draft. See the IPCDN WG presentation slides for more details.
The two remaining issues for this draft are (1) the use of "mask" objects in the docsBpi2CmIpMulticastMapTable, and (2) the use of ZeroBasedCounter32 syntax instead of Counter32 syntax. Regarding the latter issue, the MIB doctor recommendation is to use Counter32 syntax, since it is very difficult to justify the use of ZeroBasedCounter32 syntax in most cases. In particular, if the lifetime of the counter object is less than the minimum wrap time for the counter, then zero-based counters don't make sense.
Eduardo is going to generate draft 14 to resolve these MIB doctor issues, and any issues raised by IETF Last Call.
Greg Nakanishi and Azlina Ahmad generated version 04 of the Event Notification MIB draft, after a long hiatus and author reassignment, and completed a MIB doctor review.
One issue was raised about whether the notification object varbind lists should include the event level and event text objects; it was unanimously agreed by participants at the meeting (and responses on the mailing list) that these two objects should be included.
Greg will generate draft 05 and we will begin WGLC as soon as possible.
Richard Woundy indicated that he was working on transferring the ownership of this draft to a new author, because the current draft expired in April 2004.
Eugene Nechamkin and Jean-Francois Mule generated versions 03 and 04 of the MTA MIB draft, to address comments from ETSI, CableLabs, and the IPCDN mailing list. Draft 04 is currently in WGLC. See the IPCDN WG presentation slides for more details.
Based on comments from the MIB doctor review and WGLC, Eugene and Jean-Francois will generate draft 05 and proceed to IESG review.
Gordon Beacham, Satish Kumar, and Sumanth Channabasappa submitted version 05 of the NCS Signaling MIB draft, to address feedback from ETSI. Draft 05 is currently in WGLC, and Randy Presuhn agreed during the IPCDN meeting to provide MIB doctor support. See the IPCDN WG presentation slides for more details.
Based on comments from the MIB doctor review and WGLC, Gordon, Satish, and Sumanth will generate draft 06 and proceed to IESG review.
Wim De Ketelaere and Eugene Nechamkin submitted version 03 of the Management Event MIB draft, but the draft was not discussed at the IPCDN meeting.
There have been no new submissions of the CableHome MIB internet-drafts since the last IETF, and they were not discussed at the IPCDN meeting. The WG will focus on CableHome MIB draft after September 2004, once the September milestones for DOCSIS and PacketCable/IPCableCom MIB internet-drafts have been completed.
The co-chairs will review plans for promoting, finalizing, and reviewing current IPCDN MIBs, with a focus on the DOCSIS and PacketCable/IPCableCom MIB internet-drafts. They will look for serious commitments from authors to make sure the WG meets revised milestones.
Richard Woundy <Richard_Woundy@cable.comcast.com>