2.4.7 IP over Cable Data Network (ipcdn)

NOTE: This charter is a snapshot of the 61st IETF Meeting in Washington, DC USA. It may now be out-of-date.
In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional IPCDN Web Page

Last Modified: 2004-09-22

Chair(s):

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

Operations and Management Area Director(s):

Bert Wijnen <bwijnen@lucent.com>
David Kessens <david.kessens@nokia.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: http://www.ietf.org/mail-archive/web/ipcdn/index.html

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
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

Internet-Drafts:

  • draft-ietf-ipcdn-qos-mib-10.txt
  • draft-ietf-ipcdn-subscriber-mib-16.txt
  • draft-ietf-ipcdn-bpiplus-mib-14.txt
  • draft-ietf-ipcdn-docsisevent-mib-04.txt
  • draft-ietf-ipcdn-docs-rfmibv2-11.txt
  • draft-ietf-ipcdn-pktc-signaling-07.txt
  • draft-ietf-ipcdn-pktc-mtamib-05.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

    ~\My Documents\Standards\ietf\ipcdn\ipcdn meeting #61\ietf61-ipcdn-minutes_edited.txt.html
    IETF IPCDN Meeting Notes
    Washington D.C., USA
    Tuesday November 9, 2004
    
    Reported by Greg Nakanishi (gnakanishi@motorola.com)
    Edited by Jean-Francois Mule' (jfm@cablelabs.com)
    
    
    --- WG Meeting Summary
    --- ------------------
    Ten to fifteen attendees of the IP over Cable Data Networks WG met
    at the IETF meeting in Washington DC on November 9, 2004. Total
    meeting time was about one hour.
    
    The meeting materials are consolidated into 1 deck of slides and will
    be provided as part of the IETF proceedings. They are also posted at
    http://www.ipcdn.org/meetings.html
    
    We won't summarize the content of the meeting in details, please read
    the slides for the current wg item status.
    
    
    - Summary of decisions made and Action Items (AI)
    
      o WG Charter update
        We are close to finishing the following MIBs (WGLC passed, some
        have passed IETF Last Call, some are about to be in "publication
        requested status):
            - updated IPCDN DOCSIS RF MIB (Proposed Standard)
            - IPCDN DOCSIS Event Notification MIB (Proposed Standard)
            - PacketCable/IPCableCom MTA device MIB (Proposed Standard)
            - PacketCable/IPCableCom MTA signaling MIB (Proposed Standard)
    
        The WG charter should be revised to change the following
        milestones:
           - IPCDN PacketCable/IPCablecom Management Event MIB
             (draft 03 is expired, new target date required - Dec04? TBD)
           - IPCDN DOCSIS Cable Device MIB v2
             (draft06 is expired, new editor to be assigned, new target
              date TBD)
           - CableHome MIBs
             (IDs are expired, target completion date of Dec04 is unlikely
              to be met; new target date TBD).
    # AI: WG chairs to follow-up with AD Bert Wijnen to revise charter
    # once commitment is secured from ID authors & editors.
    
      o draft-ietf-ipcdn-subscriber-mib-16.txt
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscriber-mib-16.txt
        Status: RFC Editor Queue
        Draft 16 addressed all IESG comments; work concluded on this ID,
        awaiting publication. Many thanks to Wilson Sawyer for his
        continued work on this work item. No AI.
    
      o draft-ietf-ipcdn-qos-mib-10.txt
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-qos-mib-10.txt
        Status: IETF Last Call started on 2004-11-04; ended on 2004-11-21.
    # open issue: rooting of the MIB module under mib-2 need to be
    # addressed; wg chairs to resolve it after IETF Last Call.
    
      o draft-ietf-ipcdn-docsisevent-mib-04.txt
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docsisevent-mib-04.txt
        Status: AD Review
        ID draft 03 reviewed by MIB doctor Harrie.
    # AI: chairs to ping AD Bert after IETF to see if AD review is
    # complete. 
    # AI: Greg N to update the draft per last comments received from
    # AD and release draft 05 for IETF Last Call.
    
      o draft-ietf-ipcdn-docs-rfmibv2-11.txt
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-11.txt
    # AI: Eduardo to release draft 12 after IETF 61
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-12.txt
    # AI: chairs to follow-up on AD review
    
    
      o draft-ietf-ipcdn-bpiplus-mib-14.txt
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-14.txt
        Status: Draft 14 went through IESG review; 2 DISCUSS
        Draft 15 to be released after IETF addressing IESG comments.
    # AI: Eduardo to release draft 15 after IETF 61
    # AI: once draft15 is out, chairs to follow-up with AD
    
      o DOCSIS Cable Device v2 MIB Update
        Status: draft expired, need new ID Editor
        Draft 07 should address all open comments on ID
        Call for volunteer re-sent on November 3, 2004
    # AI: WG chairs to name new editor by December 10 (was Nov 19 but new
    # volunteers were provided and chairs need more time to assign it)
        Target date for revised ID: tbd with new editor
    
      o draft-ietf-ipcdn-pktc-mtamib-05.txt
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-05.txt
        Status: revised ID needed
        Draft 05 attempted to address all the MUST fix; one pending issue
        was actively discussed during the meeting: pktcMtaDevErrorOid
        table and the syntax of pktcMtaDevErrorOid, pktcMtaDevErrorValue.
        see MIB doctor comments at:
        http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01325.html
        The size limit issue in that table should also be closed on the
        mailing list.
    # AI: Jean-Francois to close this one.
        In the WG meeting, we had consensus that since the OID and its
        value is provided in the MTA config file by an operator in the
        form of a character string, it is better to leave the syntax
        as SnmpAdminString rather than OBJECT IDENTIFIER. It was also
        requested that the above explanation be mentioned in the doc.
        Eugene Nechamkin also pointed out (via email, in response to draft
        meeting notes) that some recent discussions on the reflector in
        November have raised issues that should be addressed
        (pktcMtaDevProvConfigHash in particular)
    # AI: authors to release draft06 addressing open comments.
    
      o draft-ietf-ipcdn-pktc-signaling-07.txt
        http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-07.txt
        Status: all oustanding issues addressed, except for
                pktcSigDevToneTable enhancements and PktcRingCadence for a
                fourth octet;
        New comments on the list need to be closed. Randy Presuhn
        commented that he could review the updated draft to make sure his
        comments were addressed.
    #AI: authors to list close open comments and release draft08 after
    #    IETF 61
    
    - IPCDN WG next steps
    We briefly discussed the IPCDN WG Next Steps, including:
     - Finish all DOCSIS MIBs by December 2004
       Finish all work on active IDs
       Risk: Cable Device MIBv2
     - Request publication for
       PacketCable/IPCablecom MTA MIB
       PacketCable/IPCablecom Signaling MIB
     - Revise Charter Milestones for
    
       a) PacketCable/IPCablecom Management Event MIB (expired draft 03)
       (we would like to push the work on this ID until 2005 to get
        implementations and testing under way)
    
       b) CableHome MIBs
       CableHome MIBs - there is no activity on the list.  Is there any WG
       interest to support this work?  It was suggested by Greg N that we
       should update the drafts to the latest CableHome MIBs.
    
    
    

    Slides

    IPCDN WG Update