Re: idnits and smilint on Cable Device MIB Draft 09

Hi -

> From: "Woundy, Richard" <[email protected]>
> To: "Ipcdn (E-mail)" <[email protected]>
> Cc: "Randy Presuhn" <[email protected]>; "Woundy, Richard" <[email protected]>
> Sent: Sunday, July 24, 2005 7:12 PM
> Subject: RE: [ipcdn] idnits and smilint on Cable Device MIB Draft 09
...
> The significant MIB compilation problem with version -09 was the
> inclusion of deprecated groups in the current compliance statements
> 'docsDevCmCompliance' and 'docsDevCmtsCompliance'.
>
> After further discussion among the authors, we decided that we should
> remove the deprecated groups from the current compliance statement. The
> key realization is that if a particular version of DOCSIS requires
> implementation of a deprecated group, then that requirement can be
> captured in a CableLabs specification, not in this internet-draft/RFC.
> This internet-draft/RFC should be agnostic with regards to DOCSIS
> versions and their (evolving) requirements.

I think this is a very sensible solution.

> The unfortunate consequence is that the group 'docsDevNmAccessExtGroup'
> is no longer referenced by any compliance statement. This group consists
> of a single MIB object that was invented by CableLabs after publication
> of RFC 2669. We still include this MIB object (and group) for future
> reference -- although it is immediately deprecated.
...

Since the DESCRIPTION spells out why it is there, I think this is a
satisfactory solution. even if it does trigger a warning message.

Randy