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

"Eugene Nechamkin" <[email protected]>
Newsgroups gmane.ietf.ipcdn
Message-ID <24CDBA67F085904999751B3C4F9E8C0B01E76CD7@NT-RMNA-0740.brcm.ad.broadcom.com>
To address this concern, the last veraion of the description clause with the softer language allowing the locatlization has been introduced (see the latest e-mail exchange on the topic).

Eugene.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dave Thaler
Sent: Wednesday, January 12, 2005 12:03 PM
To: Jean-Francois Mule; [email protected]
Cc: Eugene Nechamkin; PacketCable Provisioning and OSS Majordomo List; Leandro Rzezak
Subject: RE: [ipcdn] [pkt-prov] MTA MIB Error OID table - a number of questions

The problem I have with 
	> must all be equal to
	> 'TOO MANY ERRORS IN THE CONFIGURATION FILE'
is that nothing else in the DESCRIPTION clauses indicates that the text must be in English, and this introduces a MUST which is not localizable to other languages.

-Dave

> -----Original Message-----
> From: Jean-Francois Mule [mailto:[email protected]]
> Sent: Tuesday, January 11, 2005 3:35 PM
> To: [email protected]
> Cc: [email protected]; Dave Thaler; Sumanth Channabasappa; 
> PacketCable Provisioning and OSS Majordomo List; Leandro Rzezak
> Subject: RE: [ipcdn] [pkt-prov] MTA MIB Error OID table - a number of 
> questions
> 
> All,
> 
>   Eugene and I are updating the IETF IPCDN MTA MIB draft 06.
> 
>   We'd like to close one of the open items that did not get address in 
> the
> draft05 released in October: pktcMtaDevErrorOidsTable and what MTA 
> behavior should be when the number of errors exceeds the table size 
> limit of 1024.
> 
>   Based on the input received, we'd like to propose the following:
>  1. keep 1024 as a reasonable number of errors in a single config file  
> 2. if more than 1024 I had ping the list, >/dev/null": the MTA should 
> forget about any subsequent errors i.e. any error after 1024 does not 
> get stored in the table, and the last entry (1024th)'s is populated 
> with a reason indicating that there are more errors per the 
> suggestions received by Leandro and Sumanth on the list.
> 
> Proposed text changes:
> pktcMtaDevErrorOidIndex  OBJECT-TYPE
>     SYNTAX      Unsigned32 (1..1024)
>     MAX-ACCESS  not-accessible
>     STATUS      current
>     DESCRIPTION
>         " This object is the index of the MTA configuration error
>           table. It is an integer value which starts at value '1'
>           and is incremented for each encountered configuration
>           file error or warning.
>           If the number of configuration errors exceeds 1024, all
>           errors beyond the 1024th one must be ignored - these
>           subsequent errors are not reflected in the
>           pktcMtaDevErrorOidsTable. In this case, the value of the
>           pktcMtaDevErrorOid, pktcMtaDevErrorValue, and
>           pktcMtaDevErrorReason objects for the 1024-th table entry
>           must all be equal to
>           'TOO MANY ERRORS IN THE CONFIGURATION FILE'."
>     ::= {pktcMtaDevErrorOidsEntry 1}
> 
> 
> Let us know if this change is acceptable or else, feel free to propose 
> text improvements or suggestions.
> Thanks,
> Jean-François
>
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.