RE: Review of draft-ietf-ipcdn-pktc-mtamib-04.txt

"Wijnen, Bert (Bert)" <[email protected]>
Newsgroups gmane.ietf.ipcdn
Message-ID <7D5D48D2CAA3D84C813F5B154F43B155062BE42F@nl0006exch001u.nl.lucent.com>
Look fine to me too
Bert

> -----Original Message-----
> From: Dave Thaler [mailto:[email protected]]
> Sent: Wednesday, January 12, 2005 03:39
> To: Jean-Francois Mule; [email protected]
> Cc: Wijnen, Bert (Bert); [email protected]; C. M. Heard;
> [email protected]
> Subject: RE: Review of draft-ietf-ipcdn-pktc-mtamib-04.txt
> 
> 
> Jean-Francois Mule writes:
> > To close on one additional comment:
> > Dave wrote:
> > > 12) pktcMtaDevErrorOid, pktcMtaDevErrorValue, etc:
> > >     why are OIDs of type SnmpAdminString rather than an
> > > OBJECT IDENTIFIER
> > >     type/subtype?  As is, the management station cannot do
> > > simple things
> > >     like expanding the OID into the defined string tokens in the
> MIB.
> [...]
> > So, the resolution is:
> >     - no object syntax change
> >     - change the description of the pktcMtaDevErrorOid to 
> indicate the
> > following:
> >          "Note that the syntax of this object is SnmpAdminString
> >           rather OBJECT IDENTIFIER because the object value is
> >           provided by an operator in the MTA configuration file
> >           in the form of a character string."
> >     - after more review of the pktcMtaDevErrorValue object, 
> we do not
> > believe the above text should be added to its description as this
> > pktcMtaDevErrorValue object may contain all kinds of object 
> values in
> the
> > case where the MTA can recognize the OID but cannot interpret the
> given
> > value.
> [...]
> 
> This resolution looks fine to me.
> 
> -Dave
>
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.