Re: Problems in XML source of Cable Device MIB, Draft 09
"Randy Presuhn" <[email protected]> Tue, 26 Jul 2005 11:35:13 -0700
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <009b01c59210$c35e5b00$7f1afea9@oemcomputer> |
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 6:48 PM > Subject: RE: [ipcdn] Problems in XML source of Cable Device MIB, Draft 09 ... > I was unable to avoid the following errors from the tool. All of these > normative references are either from the IMPORTS clause, or from one or > more REFERENCE clauses. ... See the top of page 10 in the MIB review guidelines http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-04.txt All you need to do is identify the sources of IMPORTed TCs and whatnot in your overview section. I'd suggest doing the same thing for the documents referenced from REFERENCE clauses. Something as simple as "The following documents are mentioned in REFERENCE clauses:..." would satisfy me. Randy