2.4.8 IP over Cable Data Network (ipcdn)


In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       http://www.ipcdn.org/ -- Additional IPCDN Web Page
NOTE: This charter is a snapshot of the 58th IETF Meeting in Minneapolis, Minnesota USA. It may now be out-of-date.

Last Modified: 2003-10-16

Chair(s):
Richard Woundy <Richard_Woundy@cable.comcast.com>
Jean-Francois Mule <jf.mule@cablelabs.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Mailing Lists:
General Discussion: ipcdn@ietf.org
To Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
Description of Working Group:
The IETF IPCDN Working Group develops and standardizes MIBs for IP-capable data-over-cable systems, for example cable modems, multimedia terminal adapters and associated cable-data equipment in a cable headend. These MIBs cover not only cable data interfaces, but also management of cable-data equipment and systems.

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.

Related groups:

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.

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.

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.

Goals and Milestones:
  
  
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
Aug 03  Submit DOCSIS Subscriber Management MIB to IESG for consideration as a Standards Track RFC
Sep 03  Submit DOCSIS 1.1 QoS MIB to IESG for consideration as a Standards Track RFC
Sep 03  Submit DOCSIS BPI+ MIB to IESG for consideration as a Standards Track RFC
Sep 03  Submit updated DOCSIS RF MIB to IESG for consideration as a Standards Track RFC (Proposed Standard)
Sep 03  Submit updated DOCSIS Cable Device MIB to IESG for consideration as a Standards Track RFC
Sep 03  Submit DOCSIS Event Notification MIB to IESG for consideration as a Standards Track RFC
Sep 03  Submit PacketCable/IPCableCom MTA device MIB to IESG for consideration as a Standards Track RFC
Sep 03  Submit PacketCable/IPCableCom MTA signaling MIB to IESG for consideration as a Standards Track RFC
Nov 03  Submit PacketCable/IPCableCom MTA event MIB to IESG for consideration as a Standards Track RFC
Nov 03  Submit Cablehome MIB for managing residential gateway or home router device to IESG for consideration as Standards Track RFC
Nov 03  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
Nov 03  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
Nov 03  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
Nov 03  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
Feb 04  Revaluate charter and milestones or conclude wg
Internet-Drafts:
  • - draft-ietf-ipcdn-qos-mib-09.txt
  • - draft-ietf-ipcdn-igmp-mib-04.txt
  • - draft-ietf-ipcdn-subscriber-mib-13.txt
  • - draft-ietf-ipcdn-bpiplus-mib-12.txt
  • - draft-ietf-ipcdn-device-mibv2-06.txt
  • - draft-ietf-ipcdn-docs-rfmibv2-08.txt
  • - draft-ietf-ipcdn-pktc-signaling-02.txt
  • - draft-ietf-ipcdn-pktc-mtamib-02.txt
  • - draft-ietf-ipcdn-cable-gateway-addressing-mib-00.txt
  • - draft-ietf-ipcdn-cable-gateway-device-mib-00.txt
  • - draft-ietf-ipcdn-cable-gateway-qos-mib-00.txt
  • - draft-ietf-ipcdn-cable-gateway-config-mib-00.txt
  • - draft-ietf-ipcdn-cable-gateway-security-mib-00.txt
  • - draft-ietf-ipcdn-cable-gateway-tools-mib-00.txt
  • Request For Comments:
    RFCStatusTitle
    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

    Current Meeting Report

    IETF IPCDN Meeting
    Minneapolis, Minnesota
    Tuesday November 11, 2003


    Reported by Azlina Ahmad (azlina@cisco.com) and Greg Nakanishi (gnakanishi@motorola.com)
    Summary by Jean-Francois Mule' (jfm@cablelabs.com)
    Edited by Richard Woundy (richard_woundy@cable.comcast.com)

    WG Meeting Summary

    The IPCDN WG met to discuss the progress of various MIB documents, especially the DOCSIS and PacketCable/IPCablecom submissions. 13 I-D updates were submitted in between the meetings. We briefly covered the rechartering of the WG under the Ops area in August and the updated milestones.

    On the DOCSIS MIB front, we went over the open & closed issues on the main drafts including RF MIB v2 draft 08, DOCSIS Cable Device MIB v2 draft 6, Subscriber Mgmt MIB draft 13, DOCSIS BPI+ MIB draft 12 and DOCSIS QoS MIB draft 9. On the DOCSIS QoS MIB, we discussed the issue of the DOCSIS use of TOS byte vs. DSCP with Randy Presuhn and Bert Wijnen during the meeting and agreed on a proposed resolution path which is to complement the limited statement of applicability we already have by adding a mapping and send the text to Bert.

    We also reviewed the status of the PacketCable/IPCablecom MIB Updates (MTA MIB draft 2, Signaling MIB draft 2, Management Event MIB draft 2) and the next steps (MIB doctor review).

    Finally, we went over the comment Randy Presuhn had made re: the ping MIB and the CableHome Remote Diagnostic Tools MIB and agreed on the next step which is for CableLabs to proposed a compliance statement against the ping mib in order to reuse that mib at a maximum.

    Total meeting time was one hour.

    Administration

    There were a number of draft updates (13) for the WG since the last IETF meeting in Vienna, but there have been no updates for the CableHome MIBs.

    The WG discussed the co-chairs' proposal for making realistic WG deadlines for the existing drafts. This requires more input from the WG.

    Due to the expiration of the draft, and after discussions with the current authors, the co-chairs have concluded that the DOCSIS Event Notification MIB needs new author(s). WG participants asked if there were outstanding comments on the Event Notification MIB; there have been some comments from some reviewers that need to be addressed.

    DOCSIS RFIv2 MIB (replacing RFC2670)

    David Raftus, who introduced most of the DOCSIS 2.0 related content in this internet-draft and produced seven revisions, has voluntarily relinquished his draft editing duties. Eduardo Cardono (CableLabs) has agreed to take over this draft, and prepare it for IESG submission. Eduardo submitted version 8 of the draft prior to the Minneapolis meeting, resolving a number of WG open issues with the draft. See the IPCDN WG presentation slides for more details.

    This internet-draft is considered high priority by the WG with regards to IESG approval, since many other IPCDN internet-drafts make reference to it. A draft version 9 is already underway, and will address the three technical issues (ifAdminStatus, interface cloning process, and Security Considerations update) raised in the meeting. See the IPCDN WG presentation slides for more details.

    Cable Device MIB (replacing RFC2669)

    Richard Woundy included a number of changes in version 6 of the internet-draft, particularly in adopting the DiffServ MIB for IP filtering, and subsequently deprecating the IPv4-only and IP ToS filtering tables and objects. Other editorial changes were also made to the draft.

    A WG participant asked if implementors could choose between implementing the DiffServ MIB objects or the legacy RFC 2669 IPv4/ToS objects. Bert Wijnen explained that "deprecation" means that new implementations must implement the DiffServ MIB objects -- although new implementations may implement the legacy deprecated objects as well, for backward compatibility.

    The WG discussed the impact of changing the upper bound on the size of docsDevSwFilename. The current size restriction is 64 octets, but there is a desire to increase the maximum size to 128 octets (or more). A WG participant pointed out that a proper current SNMP agent implementation must perform a size check for the Set operation, so there should be no adverse impacts to current implementations.

    The direction of the WG is to increase the upper bound on the size of docsDevSwFilename, without defining a new MIB object. The change in syntax to docsDevSwFilename should be reflected in the compliance statements for RFC 2669 in this MIB.

    Subscriber Management MIB

    Wilson Sawyer incorporated minor changes in version 13 of the internet-draft, mostly in response to MIB doctor reviews by Bert Wijnen and Harrie Hazewinkel. See the IPCDN WG presentation slides for more details. The WG agrees that this draft is ready for submission to the IESG.

    BPI+ MIB

    Eduardo Cardona submitted version 12 of the internet-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 WG agrees that this draft is ready for submission to the IESG.

    DOCSIS QOS MIB

    Michael Patrick and William Murwin submitted version 9 of the internet-draft, resolving WG open issues with the draft. See the IPCDN WG presentation slides for more details.

    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.

    The objects in question include: docsQosPktClassIpTosLow, docsQosPktClassIpTosHigh, docsQosPktClassIpTosMask, docsQosParamSetTosAndMask, and docsQosParamSetTosOrMask. Bert observed that all of these MIB objects are read-only. Randy Presuhn made the comment that these objects should not pose a problem as long as the conversion from the IP TOS octet to a DSCP value is well documented in the internet-draft. He observed that this level of documentation is not in the draft yet and probably should be added.

    The WG agreed on the following resolution to the IP TOS octet concerns.

  • Add text to section 4 to state the mapping from the TOS octet value to the DSCP value.
  • Add similar text to the DESCRIPTION clauses of the appropriate MIB objects, so that when the MIB is extracted from the RFC, the information about IP TOS is still there.
  • Note: After the WG meeting, Richard Woundy observed that docsQosServiceClassTosAndMask and docsQosServiceClassTosOrMask are IP TOS-related MIB objects that are read-create objects in the MIB. The WG needs to confirm that the Area Director guidance above is still applicable for this draft.

    There were no comments on the other QoS MIB changes for version 9. The WG agrees that after addressing the IP TOS-related issues above, then this draft is ready for WG last-call, and then submission to the IESG.

    PacketCable/IPCableCom MTA MIB

    Eugene Nechamkin and Jean-Francois Mule incorporated changes in version 2 of the internet-draft, to address comments from an initial MIB doctor review, and from the WG last-call.

    In the month since the draft was submitted, there have been very few comments. The first MIB doctor (Mike Heard) doesn't have time at the moment to finish the review. The co-chairs need to remind Bert Wijnen to help find a new MIB doctor to complete the review of this draft.

    PacketCable/IPCableCom NCS Signaling MIB

    Gordon Beacham, Satish Kumar, and Sumanth Channabasappa submitted version 2 of the internet-draft, to address comments from the WG last-call. This draft has had no MIB doctor review yet.

    ETSI and CableLabs have been collaborating closely on the NCS Signaling MIB. Jean-Francois asked about when should formal comments be solicited by ETSI and ITU -- before or after the MIB doctor review? The next ITU SG9 face-to-face meeting is in January. Bert responded that it would be preferable to get a MIB doctor review before the SG9 meeting; Jean-Francois should ping Bert prior to the meeting.

    PacketCable/IPCableCom Management Event MIB

    Wim De Ketelaere and Eugene Nechamkin submitted version 2 of the internet-draft, to address known comments from ETSI and the IPCDN mailing list. The recent changes included aligning the SYSLOG precedence values with the DOCSIS Cable Device MIB and the SYSLOG MIB. A previous draft labelled as version 2 was never posted to the IETF.

    This draft is ready for a MIB doctor review.

    CableHome MIBs

    There have been no new submissions of the CableHome MIB internet-drafts since the last IETF. There have been few comments, except for comments from Randy Presuhn, which are discussed below.

    Randy asked why CableHome does not re-use the remote diagnostic tool work from the DISMAN WG. In particular, he asked whether a compliance statement could be developed to include objects from the Ping MIB, rather than defining a new MIB.

    The DISMAN WG is looking to promote the Ping MIB from Proposed Standard to Draft Standard status. This might permit an opportunity for DISMAN to specify new Ping MIB object or conformance groups, that make it easier to leverage in external MIBs, such as the CableHome MIBs.

    Separately, CableLabs has analyzed the Ping MIB; the analysis has discovered an 80% overlap (for similar objects). The CableHome Tools MIB only permits one test at a time, whereas the Ping MIB permits multiple tests at a time.

    The CableHome MIB authors have agreed to work on incorporating Ping MIB compliance statements for feedback from the DISMAN WG soon.

    IPCDN Next Steps

    The co-chairs believed that the DOCSIS RFIv2 MIB and the Cable Device MIB can be finished by December, if MIB doctors have the time to review (and if the authors cooperate through submissions and responses).

    The co-chairs will review plans for promoting, finalizing, and reviewing current IPCDN MIBs. They will look for serious commitments from authors to make sure the WG meets revised milestones.

    Co-chairs:

    Richard Woundy <Richard_Woundy@cable.comcast.com>
    Jean-Francois Mule' <jf.mule@cablelabs.com>

    Slides

    Agenda