RE: AD review: draft-ietf-ipcdn-docsisevent-mib-04.txt
Nakanishi Greg-MGI8179 <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <D5A7E45D575DD61180130002A5DB377C0D8BDD41@ca25exm01> |
Burt, OK with me. I'll get the update into the next revision. Thanks, greg -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Wijnen, Bert (Bert) Sent: Thursday, November 04, 2004 6:58 AM To: Ipcdn (E-mail) Subject: [ipcdn] AD review: draft-ietf-ipcdn-docsisevent-mib-04.txt Not a final review, just a question first that came up when I did a quick initial browse: I do not understand: MODULE -- docsDevNotif --mandatory groups GROUP docsDevCmNotifControlGroup DESCRIPTION "Mandatory in CM." GROUP docsDevCmNotificationGroup DESCRIPTION "Mandatory in CM." ::= { docsDevNotifCompliances 1 } Why would you not specify instead: docsDevCmNotifCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for CM Notifications and Control" MODULE --docsDevNotif MANDATORY-GROUPS { docsDevCmNotifControlGroup, docsDevCmNotificationGroup } After all, it is the compliance for CM, and for a CM, both groups are mandatory. So using my alternate method makes that a spec that is machine readable. Same for the Cmts compliance of course. Bert _______________________________________________ IPCDN mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ipcdn