RE: New Version Notification - draft-ietf-ipcdn-docsisevent-mib-0 5.txt

I get:
  !! Missing citation for Normative reference:
  P039 L042:    [10]  SCTE Data Standards Subcommittee, "Data-Over-Cable Service

I could fix theat with an RFC-Editor note if you tell me where to insert the citation.

On page 37:
   It is RECOMMENDED that implementers consider the security features as
   provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for the SNMPv3 cryptographic mechanisms (for
   authentication and privacy).
Causes:
  !! Missing Reference for citation: [RFC3410]
  P038 L017:    provided by the SNMPv3 framework (see [RFC3410], section 8),

I could fix that with an RFC-Editor note.

It makes me wonder if all references are in sync with the citations.
Someone, please check and send a positive acknowledgement that you HAVE checked
them all and that they are OK.

But I still see:
   docsDevCmNotifCompliance MODULE-COMPLIANCE
       STATUS current

       DESCRIPTION
       "The compliance statement for CM Notifications and Control"

       MODULE --docsDevNotif
       --mandatory groups

           GROUP docsDevCmNotifControlGroup
           DESCRIPTION
               "Mandatory in CM."

           GROUP docsDevCmNotificationGroup
           DESCRIPTION
               "Mandatory in CM."

       ::= { docsDevNotifCompliances 1 }

And I thought we had agreed that you would change it to:

   docsDevCmNotifCompliance MODULE-COMPLIANCE
       STATUS current

       DESCRIPTION
       "The compliance statement for CM Notifications and Control"

       MODULE --docsDevNotif
           MANDATORY-GROUPS {
               docsDevCmNotifControlGroup,
               docsDevCmNotificationGroup
           }
       ::= { docsDevNotifCompliances 1 }

What am I missing?

And also:
   docsDevCmtsNotifCompliance MODULE-COMPLIANCE
       STATUS current
       DESCRIPTION
           "The compliance statement for DOCSIS CM and CMTS."
       MODULE --docsDevNotif
       --mandatory groups

           GROUP docsDevCmtsNotifControlGroup
           DESCRIPTION
               "Mandatory in CMTS."

           GROUP docsDevCmtsNotificationGroup
           DESCRIPTION
               "Mandatory in CMTS."

       ::= { docsDevNotifCompliances 2 }

should be (possibly) be (but see my questions):

   docsDevCmtsNotifCompliance MODULE-COMPLIANCE
       STATUS current
       DESCRIPTION
           "The compliance statement for DOCSIS CM and CMTS."

bw asks: is it really for CM and CMTS or only for CMTS?

       MODULE --docsDevNotif
           MANDATORY-GROUPS {
               docsDevCmtsNotifControlGroup,
               docsDevCmtsNotificationGroup
           }
       ::= { docsDevNotifCompliances 2 }

if it is both for CM and CMTS, then you seem to be telling me that it is
optional for CM. So maybe this one should be just for CMTS (with just 
mandatory groups) and then the first MODULE-COMPLIANCE should have these
2 groups added as optional groups!?

If this is just for CMTS, then the DESCRIPTION clause should say so and then my 
suggested change is the proper way to specify it.

You have put this 
   Note that notifications are also under the control of the MIB modules
   defined in RFC 3413 [17].
In the security COnsiderations section. That is not a secuurity concern (I think).
Rather it is something to describe (I think) in the DESCRIPTION clauses of
docsDevCmNotifControl and docsDevCmtsNotifControl.

W.r.t. Persistency of the writable objects you have added:
        If the device is rebooted, the value of this object should revert
        to the default value.
which meets my concern. 
It is something however that you and the WG chairs may want to make sure that
the WG agrees with.

Bert
> -----Original Message-----
> From: Jean-Francois Mule [mailto:[email protected]]
> Sent: Friday, January 07, 2005 19:19
> To: [email protected]
> Cc: Richard Woundy @ Comcast; [email protected];
> [email protected]; [email protected]
> Subject: RE: New Version Notification -
> draft-ietf-ipcdn-docsisevent-mib-05.txt
> 
> 
> Bert,
> 
>    Let us know what the next step is on this ID.
> 
> Thanks,
> Jean-François 
> 
> > -----Original Message-----
> > From: ID Tracker [mailto:[email protected]] 
> > Sent: Friday, January 07, 2005 11:46 AM
> > To: Richard Woundy @ Comcast; [email protected]; 
> > Jean-Francois Mule; [email protected]; 
> > [email protected]; [email protected]
> > Subject: New Version Notification - 
> > draft-ietf-ipcdn-docsisevent-mib-05.txt
> > 
> > 
> > 
> > New version (-05) has been submitted for 
> > draft-ietf-ipcdn-docsisevent-mib-05.txt.
> > http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docsiseve
> nt-mib-05.txt
> 
> 
>