140 likes | 268 Views
IPCDN WG Update. Richard Woundy Jean-François Mulé IPCDN Co-Chairs Richard_Woundy@cable.comcast.com jfm@cablelabs.com. Meeting Agenda. Agenda Bashing Administration and Re-Chartering DOCSIS Submissions 5 WG drafts under revision PacketCable/IPCablecom Submissions 3 new WG drafts
E N D
IPCDN WG Update Richard Woundy Jean-François Mulé IPCDN Co-Chairs Richard_Woundy@cable.comcast.com jfm@cablelabs.com IPCDN Working Group
Meeting Agenda • Agenda Bashing • Administration and Re-Chartering • DOCSIS Submissions • 5 WG drafts under revision • PacketCable/IPCablecom Submissions • 3 new WG drafts • CableHome Submissions • 5 new drafts – all individual submissions • Status of Expired WG drafts • 6 expired drafts • WG next steps • Lots of drafts requires lots of WG participation and review IPCDN Working Group
Administration / Recharter 1 • Draft review status • Two drafts in Area Director review and require complete author feedback to the MIB doctor: DOCSIS IGMP MIB, Subscriber Management MIB • Internet-draft management issues • Use ipcdn mailing list for technical discussions of drafts • Authors should make more frequent draft updates, i.e. not just before IETF draft submission deadlines • Proposal: IPCDN expired drafts for 2 consecutive IETF meetings will be discontinued, and reassigned to new authors or removed from the WG charter • Authors need to provide more timely responses to MIB doctors and other IESG reviewers • Beware of imminent changes to SNMP boilerplates • IPCDN website update • Rich promises to be ready by December 1st! IPCDN Working Group
Administration / Recharter 2 • Re-charter progress • Drop DVB/Euromodem MIB efforts, after consultation with the ECCA Technical Committee (contact: Dirk Jaeger) • Add CableHome MIB efforts? (contact: Doug Jones) • Determine new WG action items, milestones • Alignment of IPCDN milestones with CableLabs certification waves (CW#25, CW#26, CW#27 in 2003) • Current WG priorities • Finish DOCSIS 1.1 & 2.0 drafts ASAP • IPCablecom/PacketCable MIBs • CableHome MIBs IPCDN Working Group
DOCSIS Submissions 1 • New Internet Drafts • draft-ietf-ipcdn-subscriber-mib-07.txt • draft-ietf-ipcdn-device-mibv2-03.txt • draft-ietf-ipcdn-bpiplus-mib-07.txt • DOCSIS Application of RFC 2933 MIB • Author still working on response to MIB doctor comments for –04, with WG chair assistance • Seek coordination with authors of IGMP, IGMPv2 MIBs • Define formal MIB compliance statements for DOCSIS, based on CM/CMTS interface, active/passive modes, etc. • DOCSIS Subscriber Management MIB • Author responding to MIB doctor comments for –06 • Version –07 resolves many MIB doctor comments • Unresolved: “overlap” of IP filters, CPE controls with similar RFC 2669 tables IPCDN Working Group
DOCSIS Submissions 2 • DOCSIS 2.0 RFI MIB • Resolve DOCSIS channel utilization issue: provide new counter objects instead of percentage objects, defining “utilized minislots” for new counters, … • Extend docsIfCmtsCmStatusValue to add "operational" status? TBD… • Author to submit version –05 with WG consensus • Ready (almost) to start WG last call? • Cable Device MIB • Version –03 incorporates individual comments and DOCSIS OSSI recommendations • Deprecate IP filters, CPE controls in favor of Subscriber Management MIB on CM? Or extend CD MIB tables for IPv6? • Ready (almost) to start WG last call? IPCDN Working Group
DOCSIS Submissions 3 • BPI+ MIB • New draft editor (Alexander Katsnelson, CableLabs) has submitted version –07 • Remove extraneous CRL references in text and MIB • Did we resolve the tie-breaking for IP Multicast rows? • Use docsBpi2CmtsIpMulticastAddress or docsBpi2CmtsIpMulticastIndex as tie-breaker for docsBpi2CmtsIpMulticastMapTable rows? • Do we need to clarify meaning of date and time (i.e. include the timezone) for these objects? • docsBpi2CodeMfgCodeAccessStart • docsBpi2CodeMfgCvcAccessStart • docsBpi2CodeCoSignerCodeAccessStart • docsBpi2CodeCoSignerCvcAccessStart • Ready (almost) to start WG last call? IPCDN Working Group
PacketCable/IPCablecom 1 • New Internet-Drafts • draft-ietf-ipcdn-pktc-eventmess-00.txt • draft-ietf-ipcdn-pktc-mtamib-00.txt • draft-ietf-ipcdn-pktc-signaling-00.txt • Management Event MIB • Issue: Reword the text in the DESCRIPTION of pktcDevEvReportEndpointName • Issue: Should the SYSLOG UDP port number be configurable ala pktcDevEvSyslogUdpPort? • Issue: Change pktcDevEvThrottleInhibited DESCRIPTION to match similar RFC2669bis object? • MTA MIB • Issue: Remove MD5 hashing from pktcMtaDevProvConfigHash • Issue: Remove overlap with the Entity MIB? • Network Control Signaling MIB • Issue: Bulk up the glossary • Issue: Add risk assessment for read-write/read-create objects to the Security Considerations IPCDN Working Group
PacketCable/IPCablecom 2 • Drafts have integrated IPCDN chairs’ feedback and recommendations • All three MIBs pass MIB compilation (SMICng and others) • MIBs are rooted under mib-2 in temporary location • SMI corrections • DisplayString replaced by SnmpAdminString • INTEGER replaced by Integer32 • Object definitions made friendly wrt RFC2578 and RFC2580 • Removed all obsolete objects, corrected date values • Fixed root OIDs for notification objects • MIB Framework document dropped • Was individual submission – not chartered by WG • Start the formal WG review! • Let’s identify specific technical reviewers in this meeting, and on the mailing list IPCDN Working Group
CableHome Submissions 1 • Individual submissions from Doug Jones, YAS/CableLabs for the CableHome project • Security MIB • draft-jones-cable-gateway-security-mib-00.txt • Configuration MIB • draft-jones-cable-gateway-config-mib-00.txt • Device Management MIB • draft-jones-cable-gateway-device-mib-00.txt • Address Mapping MIB • draft-jones-cable-gateway-addressing-00.txt • Remote Diagnostic Tools MIB • draft-jones-cable-gateway-tools-mib-00.txt IPCDN Working Group
CableHome Submissions 2 • Some object overlap with other IETF draft MIBs • draft-ietf-dhc-server-mib-07.txt • draft-ietf-nat-natmib-05.txt • Others? • Assumption is that author(s) will remove overlapping objects • Shall we add these CableHome drafts to the WG charter? • Can we identify specific technical reviewers in this meeting, and on the mailing list? IPCDN Working Group
Expired Drafts • DOCSIS 1.1 QoS MIB • Issue 1: RowStatus objects need to specify if column object values can be modified when ‘active’ • docsQosServiceClassStatus • docsQosServiceClassPolicyStatus • Issue 2: Update to docsQosServiceFlowPkts description • Authors have allowed version –06 to expire • DOCSIS 1.1 Event Notifications • Resolving overlap of objects with latest RFC 2670 update via DOCSIS ECR: oss-r-02017 • Authors have allowed version –02 to expire • DVB/Euromodem MIBs (4 drafts) • Euromodem/DVB NIU and INA MIBs will be dropped, per recommendation of the ECCA Technical Committee IPCDN Working Group
IPCDN WG Next Steps 1 • Publish new DOCSIS IGMP MIB, Subscriber Management MIB drafts to resolve MIB doctor comments, and prepare for IETF last-call • Prepare DOCSIS 2.0 RFI MIB, Cable Device MIB, and BPI+ MIB drafts for working group last-call • Resolve authorship of expired WG internet-drafts or cancel them • Obtain author feedback on reasonable draft milestones • Align milestones with relevant CableLabs certification waves • Review PacketCable/IPCablecom and CableHome MIBs • Obtain IESG agreement on new charter IPCDN Working Group
IPCDN WG Next Steps 2 • Next steps for WG authors • Help the chairs define reasonable milestones for charter • Make more frequent draft updates – and don’t let drafts expire • Be flexible with respect to internet-draft requirements changes (e.g. SNMP boilerplates, normative vs. information references) • Prepare drafts for working group last-call, etc. • Respond in a timely manner to MIB doctor comments, and help us resolve them • Let the chairs know when you need help • Next steps for WG participants • Review DOCSIS MIBs (RFI 2.0, Cable Device, BPI+) in anticipation of WG last-call • Review PacketCable/IPCableCom MIBs for technical correctness • Read and review CableHome MIBs • Provide technical comments on the ipcdn mailing list, not just privately to draft authors • Provide comments on the IPCDN recharter IPCDN Working Group