- About
- Documents
- Meetings
- History
- Photos
- Email expansions
- List archive ”
Note: The data for concluded WGs is occasionally incorrect.
WG Name IP over Cable Data Network Acronym ipcdn Area Operations and Management Area (ops) State Concluded Charter charter-ietf-ipcdn-01 Approved Document dependencies Show Additional resources Additional IPCDN Web Page Personnel Chairs Jean-Francois Mule, Richard Woundy Area Director Dan Romascanu Mailing list Address [email protected] To subscribe http://www.ietf.org/mailman/listinfo/ipcdn Archive https://mailarchive.ietf.org/arch/search/?email_list=ipcdn
Final Charter for Working Group
The IETF IPCDN Working Group develops and standardizes MIBsfor IP-capable data-over-cable systems, for example cablemodems, multimedia terminal adapters and associatedcable-data equipment in a cable headend.These MIBs cover not only cable data interfaces, but alsomanagement of cable-data equipment and systems.
The WG mailing list may be used to discuss Internet-relatedissues in data-over-cable equipment and systems. In the eventof a particular new Internet technology issue arising in thecable-data context, the WG will identify whether that is besthandled within the IETF or is best handled by another standardsbody. In the event that new IETF MIB work is requested, the WGchairs can discuss additional WG work items with the AD. Suchadditions will have to go through normal re-charter process.If non-MIB work gets identified, such items are not normalwork items for this IPCDN-MIB WG and must go through normalIETF new WG chartering process.
Standardization of MIBs for DOCSIS and PacketCable systems areexplicitly within the scope of the IPCDN Working Group.
The IPCDN WG will also keep informed on what other groups inthe industry are doing as it relates to the efforts of thisworking group.
The WG will align its specifications with IPv6 and SNMP Standards.
Related groups:
CableLabs (http://www.cablelabs.com/) is structured into projects.In its Cable Modem DOCSIS project, CableLabs has produced threegenerations of data over cable specifications: DOCSIS 1.0,DOCSIS 1.1, and DOCSIS 2.0.In its PacketCable project, CableLabs has produced one generationof interface specifications for delivering real-time multimediaservices over DOCSIS (http://www.packetcable.com/specifications/).Internationally, IPCablecom is the global name associatedwith the extensions & global standardization of PacketCablein ETSI & ITU-T SG9.
DOCSIS 1.0 includes specifications for a bidirectionaldata-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, thedevice at the subscriber premise) and the Cable Modem TerminationSystem (CMTS, the device at the cable headend). For DOCSIS 1.0systems, the IPCDN WG has published the Cable Device MIB(RFC 2669), the RF Interface MIB (RFC 2670), and the BaselinePrivacy MIB (RFC 3083).
DOCSIS 1.1 extends the DOCSIS 1.0 specifications to supportbetter quality of service parameters (RFIv1.1), to enableoperation in European cable networks (EuroDOCSIS), and toauthenticate modems and firmware images (BPI+). The IPCDN WGwill update the Cable Device and Radio Frequency MIBs forDOCSIS 1.1, and repair flaws discovered in operational use.Other IPCDN WG documents will address the operational andmanagement issues for new DOCSIS 1.1 functional components(e.g. BPI+), for subscriber device management, and foruniform event notification. The IPCDN WG has also published the DOCSISSubscriber Management MIB (RFC4036) for DOCSIS 1.1 and 2.0systems.
DOCSIS 2.0 enhances the DOCSIS 1.1 specifications at thephysical layer, in particular to support two new physicallayer encodings: S-CDMA and A-TDMA. The IPCDN WG will updatethe Radio Frequency MIB for DOCSIS 2.0.
PacketCable 1.0 is built on top of the DOCSIS 1.1 cable modeminfrastructure and it includes a suite of interfacespecifications covering multimedia terminal adapter (MTA)device provisioning, voice over IP session signaling, QoSsignaling based on IETF standards. The key systems in aPacketCable network are the multimedia terminal adapter (MTA),a Call Management Server (CMS), a PacketCable-compliantDOCSIS 1.1 CMTS, Media Gateway Controllers, Media Gatewaysalong with back-office systems. In ITU-T SG-9 and ETSI AT,IPCableCom has standardized PacketCable to create a set ofinternational standards.
Work items:
The IPCDN WG will address issues related to network management,especially as they concern HFC access networks. It is expectedthat other services (i.e. RSVP, IPSEC, etc.) will operatemostly 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 aDOCSIS 1.1 device,- managing the Baseline Privacy Plus system for aDOCSIS 1.1 device,- uniform event notification on a DOCSIS 1.1 device,- revise MIB documents for:- DOCSIS 1.0 RF Interface MIB to support EuroDOCSISparameters and DOCSIS 2.0 physical layer management,- the DOCSIS 1.0 Cable Device MIBs to address SNMPv3and IPv6 compliance and interoperability issues,
– IPCablecom & PacketCable- publish MIB documents for:- managing the device parameters ofPacketCable/IPCableCom MTA devices,- managing the signaling parameters ofPacketCable/IPCableCom MTA devices,- managing events for PacketCable/IPCablecom systems,
Milestones
Date Milestone Associated documents Jan 2006 Re-evaluate charter and milestones or conclude wg
Done milestones
Date Milestone Associated documents Done Submit updated DOCSIS RF MIB to IESG for consideration as a Standards Track RFC (Proposed Standard) Done Submit updated DOCSIS Cable Device MIB to IESG for consideration as a Standards Track RFC Done Submit PacketCable/IPCableCom MTA signaling MIB to IESG for consideration as a Standards Track RFC Done Submit PacketCable/IPCableCom MTA device MIB to IESG for consideration as a Standards Track RFC Done Submit PacketCable/IPCableCom MTA event MIB to IESG for consideration as a Standards Track RFC Done Submit DOCSIS Event Notification MIB to IESG for consideration as a Standards Track RFC Done Submit DOCSIS BPI+ 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 Subscriber Management MIB to IESG for consideration as a Standards Track RFC Done Submit Baseline Privacy MIB to IESG for publication as a Standards Track RFC Done Post I-Ds revising RF and CM MIBs to support DOCSIS1.1 and for compliance with SNMPv3 and IPv6 Done Post final I-D on Baseline Privacy MIB; Last call
