Current Meeting Report

2.2.6 IP over Cable Data Network (ipcdn)

NOTE: This charter is a snapshot of the 52nd IETF Meeting in Salt Lake City, Utah USA. It may now be out-of-date. Last Modified: 22-Oct-01
A Goren <>
Andrew Valentine <>
Internet Area Director(s):
Thomas Narten <>
Erik Nordmark <>
Internet Area Advisor:
Thomas Narten <>
Mailing Lists:
To Subscribe:
Description of Working Group:
The IETF IPCDN Working Group develops and standardizes SNMP MIBs for IP-capable data-over-cable systems, for example cable modems and associated cable-data equipment in a Headend. These MIBs cover not only cable data interfaces, but also management of cable-data equipment and systems.

The WG is also a forum for 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 work is identified, such items MAY be added that to the WG's charter, subject to normal IETF processes. Standardisation of MIBs for the EuroModem cable modem is within the scope of the IPCDN Working Group. Harmonisation of EuroModem MIBs and DOCSIS MIBs is desirable and will be examined by the IPCDN WG.

The IPCDN WG will also keep informed on what other groups in the industry are doing as it relates to the work of this working group.

Related groups:

The IEEE 802.14 WG was chartered to specify the physical layer and data link layer protocols for the CATV Data Network. The IEEE has discontinued the IEEE 802.14 effort, so that group no longer exists.

DOCSIS has completed its 1.0 versions of Data over Cable standards and is in the process of refining these standards to add additional functionality and to repair any flaws discovered in operational use. The IPCDN WG will update the documents produced which track the 1.0 versions accordingly. These include the RF Interface MIB and the Cable Device MIB. In addition, the operational and management issues of multicast over a Cable Data Network will be addressed.

Work items:

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.

- a MIB for managing the Telephone Modem Return Path (Telco Return) for 1-way cable modems. (draft-ietf-ipcdn-tri-mib-01.txt)

- a MIB for managing the Baseline Privacy system for DOCSIS. (draft-ietf-ipcdn-bpi-mib-01.txt), (draft-ietf-ipcdn-bpiplus-mib-00.txt)

- a MIB for managing the Quality of Service parameters for a Cable Data Network. (draft-ietf-ipcdn-qos-mib-02.txt)

- a MIB for managing Multicast (IGMP) over a Cable Data Network. (draft-ietf-ipcdn-igmp-mib-00.txt)

- a MIB for CMTS based customer management (draft-ietf-ipcdn-subscriber-mib-00.txt)

- Revisions to the Proposed Standard RF and CM MIBs to address SNMPv3 and IPv6 compliance and interoperability issues.

Goals and Milestones:
Done   Post final I-D on Baseline Privacy MIB; Last call
Feb 00   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
Feb 00   Submit updated RF and CM MIBs to IESG with implementation statement for advancement to Draft Standard
Jun 00   Revaluate charter and milestones.
Request For Comments:
RFC2669PSCable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems
RFC2670PSRadio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces
RFC3083 Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems

Current Meeting Report

Salt Lake City, Utah USA
December 10, 2001

Reported by Jason Schnitzer (

WG Meeting Summary

Approximately 30 members of the IP over Cable Data Networks WG met at the Salt Lake City IETF on December 10, 2001. The WG discussed the status of its work items as well as the ongoing charter revision. Special attention was paid in the meeting to the new DOCSIS 2.0 specification and its impact on the DOCSIS RF MIB (RFC2670). Three internet-drafts completed working group last-call, and two internet-drafts started working group last-call at the meeting. Since the last IETF meeting, the WG has submitted five updates to existing internet-drafts. Total meeting time was about one hour.

Based on the WG discussion, the chairs will forward the draft "Application of the IGMP MIB to DOCSIS 1.1" <> to the IESG, followed shortly by the "DOCSIS QoS MIB" and "DOCSIS Subscriber Management MIB" drafts. The latter drafts have some small fixes to address minor concerns raised in last-call.

WG Status and Charter Revision

The working group quickly reviewed the overall status of work items in the working group. Three internet-drafts (Application of the IGMP MIB to DOCSIS 1.1, DOCSIS QoS MIB, and DOCSIS Subscriber Management MIB) completed working group last-calls by the date of the meeting, and two additional internet-drafts (DOCSIS RF MIB for DOCSIS 2.0, DOCSIS BPI+ MIB) started working group last-calls at the meeting.

The co-chairs have been formulating and proposing significant changes to the WG charter, with updated milestones. The charter is currently under evaluation by our Area Directors. There were no comments from the working group on these issues.

DOCSIS 2.0 and RFC2670 (RF Interface MIB)

The majority of the working group meeting focused on the DOCSIS 2.0 discussion. David Raftus and Aviv Goren presented the DOCSIS 2.0 technology, and reported on its impacts on the DOCSIS RF Interface MIB (RFC2670). There were a number of questions from the working group, but limited controversy. The following discussion items were noted:

1. The editors would like to change the permissible range of docsIfUpChannelActiveCodes, and exclude all non-primes. Is it too late to do this? Dave will follow up with mail to the IPCDN reflector.

2. A question surrounding the co-existence of IPv4/v6 in the CmtsCmStatusTable. What will this look like in a mixed v4/v6 network?

3. Dave discussed the co-existence strategy and the integration of the DOCS-IF-EXT-MIB originally from the DOCSIS Event Notification MIB, draft-ietf-ipcdn-docsisevent-mib-01.

The working group will attempt to resolve these issues during the last-call period, which started at this meeting.

DOCSIS Usage of RFC2933 MIB

The working group quickly reviewed the minor changes in draft-ietf-ipcdn-igmp-mib-03.txt, which were the result of comments from the working group last-call. There were no objections from the working group with respect to designation as an informational RFC.


The working group quickly reviewed draft-ietf-ipcdn-qos-mib-06.txt (in last-call), and the proposed response to the last-call comment about ambiguity in the counting of unclassified data packets. There were no objections from the working group.

DOCSIS Subscriber Management MIB

The working group quickly reviewed draft-ietf-ipcdn-subscriber-mib-04.txt (in last-call), and the proposed re-homing of the MIB for version -05 to prevent OID conflicts with previous versions of this MIB (version -02 has been deployed as part of DOCSIS 1.1 certification). There were no objections from the working group.


The working group quickly reviewed draft-ietf-ipcdn-bpiplus-mib-06.txt (in last-call), and reviewed two last-call issues: the mapping of BPI+ dynamic SAIDs to BPI static SAIDs, and the algorithm for choosing the matching row in docsBpi2CmtsIpMulticastMapTable. There were no objections from the working group.

Other MIBs (DOCSIS 1.1 Notifications, Cable Device MIB, Euromodem MIBs)

The working group reviewed the status of the Euromodem MIBs (need conversion to an appropriate archival form due to lack of implementation), the DOCSIS Event Notification MIB (resolve overlap with latest DOCSIS RF Interface MIB and get to last call), and the updated Cable Device MIB (resolve a number of technical issues). Some members of the working group had comments on the Cable Device MIB, but since the author was not present (he left the IETF meeting early due to a family emergency), these issues will be discussed on the IPCDN reflector.


RF Interface MIB Updates
Docsis 1.1 IGMP MIB Application Note
What Is DOCSIS 2.0 ...
Subscriber Management MIB
Other IPCDN Draft Updates