Current Meeting Report
Slides
2.2.6 IP over Cable Data Network (ipcdn)
NOTE: This charter is a snapshot of the 53rd IETF Meeting in Minneapolis, MN USA. It
may now be out-of-date. Last Modified:
19-Feb-02
Chair(s):
Richard Woundy <rwoundy@cisco.com>
Andrew Valentine <a.valentine@eu.hns.com>
Internet Area Director(s):
Thomas Narten <narten@us.ibm.com>
Erik Nordmark <nordmark@eng.sun.com>
Internet Area Advisor:
Thomas Narten <narten@us.ibm.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 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. |
Internet-Drafts:
Request For Comments:
| RFC | Status | Title |
|
| 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 | | Baseline Privacy Interface Management Information Base
for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems |
Current Meeting Report
IETF IPCDN Meeting
Minneapolis, Minnesota USA
March 19, 2002
Reported by Jason Schnitzer (jason@stargus.com)
Administrative Items
- Andrew Valentine stepped down as co-chair due to a career change.
- Rich Woundy moved from Cisco to AT&T Broadband.
- A new co-chair position is under discussion.
- Meeting attendees engaged in a discussion over the relationship between IPCDN internet drafts and CableLabs DOCSIS specification references. CableLabs often mandates the implementation of obsolete IDs out of necessity to "freeze" DOCSIS OSS MIB specifications for testing and certification purposes. As a result, CableLabs often certifies CMTS and CM devices against obsolete IPCDN MIB IDs. Is there a practical way to synchronize? It was proposed by Thomas Narten (IESG area advisor) that stable MIB IDs be released as informative or experimental RFCs for CableLabs certification reference. Early help from IETF MIB doctors on new IPCDN MIBs might ease the transition as well.
- Question: should the "Account Management" section of the DOCSIS OSS specification be moved to the IETF IPCDN space for future work? Much of this section is based on work driven by the IPDR standards effort.
- Kaz Ozawa (Toshiba/CableLabs) was unable to be present to represent the BPI+/CRL discussion.
Status of Drafts
- "DOCSIS Application of RFC 2933 MIB" (aka DOCSIS IGMP MIB) and "DOCSIS Subscriber Management MIB" completed last call, and will be submitted to the IESG after the meeting.
- "DOCSIS 1.1 QoS MIB" completed last call with minor issues. The chair will work with the authors to produce a version ready for submission to the IESG soon.
- "DOCSIS BPI+ MIB" requires some changes raised during its last-call, and may include additions from CableLabs for CRL (Certificate Revocation List) information.
- "DOCSIS 2.0 RF MIB" (RFC 2670 update) requires some changes raised during its last call. A new proposal was distributed to the mailing list.
- DVB/Euromodem technology has weak industry support at this time. The remaining ID's need to be captured in an informational RFC. Rich asked for volunteers to provide editorial support for this effort.
- A subset of the "DOCSIS 1.1 Event Notification MIB" was moved to the "DOCSIS 2.0 RF MIB". This move impacts the definition of the notification objects as well.
- Updates are pending for the "Cable Device MIB" (RFC 2669 update). Rich will continue as editor.
Charter Status
- The working group entertained a proposal to add PacketCable MIBs to the IPCDN charter.
PacketCable MIB Overview
(presented by Jean-Francois Mule of CableLabs)
- The presentation proposed the extension of the IPCDN charter to include PacketCable MIBs:
a. PacketCable MIB framework (probably won't be transferred to IPCDN)
b. MTA Device MIB
c. MTA signaling MIB
d. Event Management MIB
- A meeting attendee asked whether there would be functional conflicts between the DOCSIS and PacketCable MIBs. Jean-Francois knew of no obvious functional collision between DOCSIS MIB functionality and PacketCable MIB functionality (chair's note: IPCDN WG members should validate this claim, of course).
- There were no objections from group to extend the IPCDN charter to include PacketCable MIBs. Thomas Narten raised the pre-requisite for volunteers with vested interest in PacketCable to carry work forward within IPCDN. Editors for these MIBs must be identified.
Slides
Agenda
PacketCable mibs