RE: [pkt-prov] MTA MIB Error OID table - a number of questions

"Eugene Nechamkin" <[email protected]>
Newsgroups gmane.ietf.ipcdn
Message-ID <24CDBA67F085904999751B3C4F9E8C0B01E76CCB@NT-RMNA-0740.brcm.ad.broadcom.com>
If your concern is the usage of the object in the different lingual
environments with presumably normative language in the object's
description, then the proposed, I believe, adequately addresses your
concern. If your concern is the interoperability, then the object
itself, without the normative requirement, carries the informative
meaning for the NMS personal, and is becoming even wider interoperable.

If this is still not satisafctory, please feel free to make a specific
editorial suggestion.

Eugene.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Randy Presuhn
Sent: Wednesday, January 12, 2005 8:25 PM
To: [email protected]
Subject: Re: [ipcdn] [pkt-prov] MTA MIB Error OID table - a number of
questions

Hi -

> From: "Eugene Nechamkin" <[email protected]>
> To: "Randy Presuhn" <[email protected]>
> Cc: <[email protected]>
> Sent: Wednesday, January 12, 2005 7:50 PM
> Subject: RE: [ipcdn] [pkt-prov] MTA MIB Error OID table - a number of 
> questions
>

> How about the following:
>
> |           pktcMtaDevErrorOidsTable. In this case, the value of the
> |           pktcMtaDevErrorOid, pktcMtaDevErrorValue, and
> |           pktcMtaDevErrorReason objects for the 1024-th table entry
must
> |           all contain the string 'TOO MANY ERRORS IN THE
CONFIGURATION FILE'
> |           or its semantic equivalent."
...

This worries me even more.  I don't see how this change to the change
could possibly help interoperability.

Randy



_______________________________________________
IPCDN mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ipcdn
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.