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

Hi -

> From: "Eugene Nechamkin" <[email protected]>
> To: "Randy Presuhn" <[email protected]>; <[email protected]>
> Sent: Friday, January 14, 2005 2:41 PM
> Subject: RE: [ipcdn] [pkt-prov] MTA MIB Error OID table - a number ofques tions
...
> pktcMtaDevErrorOid  OBJECT-TYPE
>           object instance will contain the human readable string of
>           '.1.3.6.1.2.1.XXX.1.1.6.0'.

Get rid of the leading "."

...
>           For example, if the value of an OID in the configuration
>           file was interpreted by the MTA as being .1.2.3.4.5, and

Get rid of the leading "."

 ...
>           representation of the pktcMtaDevErrorsTooManyErrs object,
>           i.e. the string '.1.3.6.1.2.1.XXX.1.1.4.1.0'.

Get rid of the leading "."

...
> pktcMtaDevErrorValue  OBJECT-TYPE
...
>           interpreted by the MTA as being .1.2.3.4.5, and the MTA
>           cannot recognize this OID as a valid one, then this
>           pktcMtaDevErrorValue object instance will contain human
>           readable (string) representation of value '.1.2.3.4.5'.

Get rid of both leading "." characters.

...
>           representation of the pktcMtaDevErrorsTooManyErrs object,
>           i.e. the string '.1.3.6.1.2.1.XXX.1.1.4.1.0'.
...

Get rid of the leading "."

The grammar for the dotted decimal notation does not permit a leading
dot.  The following message explains it all:

|Message-Id: <[email protected]>
|X-Sender: [email protected]
|X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
|Date: Fri, 23 Jun 2000 12:15:52 -0700
|To: [email protected]
|From: "Kurt D. Zeilenga" <[email protected]>
|Subject: Re: Where is the OID "dot convention" spelled out?
|Cc: [email protected]
|In-Reply-To: <[email protected]>
|Mime-Version: 1.0
|Content-Type: text/plain; charset="us-ascii"
|X-Loop: [email protected]
|Status: RO
|
|See RFC 1778, 2.15:
|   Values of type objectIdentifierSyntax are encoded according to the
|   following BNF:
|
|     <oid> ::= <descr> | <descr> '.' <numericoid> | <numericoid>
|
|     <descr> ::= <keystring>
|
|     <numericoid> ::= <numericstring> | <numericstring> '.' <numericoid>
|
|   In the above BNF, <descr> is the syntactic representation of an
|   object descriptor. When encoding values of type
|   objectIdentifierSyntax, the first encoding option should be used in
|   preference to the second, which should be used in preference to the
|   third wherever possible. That is, in encoding object identifiers,
|   object descriptors (where assigned and known by the implementation)
|   should be used in preference to numeric oids to the greatest extent
|   possible. For example, in encoding the object identifier representing
|   an organizationName, the descriptor "organizationName" is preferable
|   to "ds.4.10", which is in turn preferable to the string "2.5.4.10".
|
|This was refined in RFC 2252, 4.1.  In particular, it eliminates
| the "ds.4.10" form.

Randy