Re: [pkt-prov] MTA MIB Error OID table - a number ofques tions

"Randy Presuhn" <[email protected]>
Newsgroups gmane.ietf.ipcdn
Message-ID <004c01c4f9fb$ffb6e3e0$7f1afea9@oemcomputer>
Hi -

I like this latest proposal more.  However, I think the DESCRIPTION of
pktcMtaDevErrorOidIndex needs a little more work.  Specifically,

> From: "Eugene Nechamkin" <[email protected]>
> To: "Wijnen, Bert (Bert)" <[email protected]>
> Cc: <[email protected]>
> Sent: Thursday, January 13, 2005 9:19 PM
> Subject: RE: [ipcdn] [pkt-prov] MTA MIB Error OID table - a number ofques tions
...
> pktcMtaDevErrorOidIndex  OBJECT-TYPE
 ...
>           pktcMtaDevErrorOidsTable. In this case, the value of the
>           pktcMtaDevErrorOid, pktcMtaDevErrorValue, and

remove pktMtaDevErrorOid from this list.

>          pktcMtaDevErrorReason objects for the 1024-th table entry
>           MUST all be contain the following error string:

replace "be contain" with "be"

>           '<Err_OID> - Too many errors in the configuration file.'.
>           In this string, the <Err_OID> is the meta-symbol representing
>           the corresponding Error OID. This meta-symbol contains

"contains" should be something like "will be replaced with"

>           the human readable representation (character
>          string) of the pktcMtaDevErrorsTooManyErrs object,
>           i.e. the string '.1.3.6.1.2.1.XXX.1.1.4.1'.

Delete the leading "."

Add:
            The object pktMtaDevErrorOid MUST in this case have the
             value '1.3.6.1.2.1.XXX.1.1.4.1'

>     ************************************************************
>     * NOTES TO RFC Editor (to be removed prior to publication) *
>     * Please replace XXX with the IANA-assigned number under   *
>     * mib-2.                                                   *
>     ************************************************************
>
>          The <Err_OID> MUST be present in the error string. The
>          rest of the error string will contain explanatory text
>          which should be semantically close to the error being
>          indicated."
...

This "should be semantically close" contradicts the "MUST" which
appears earlier.

Randy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.