Re: V2 Changes for next RFI v2 MIB (draft 10)

Hi, Eduardo,

   Thanks a lot for listening to me. I am happy with the new text.

    But I still have concern about saving notInService or notReady rows for 
modulation profiles into NVRAM and have them persistent across CMTS 
reboot,  especially for the rows with inconsistent attributes which is 
allowed for rowStatus in 'notInService' and 'notReady'.

   Though this is extreme case, but since the MIB or spec does not prevent 
to do so or does not make it optional, that means CMTS MUST implement such 
capability to save rows with inconsistent attributes into NVRAM which is a 
waste of CMTS resource and complicated the implementation for no or little 
gain.

   Possible to make it an optional that saving rows with inconsistent 
attributes into NVRAM and persistent across reboot ?

    Thanks a lot for your advice !
    Minnie




At 10:27 AM 4/15/2004 -0600, Eduardo Cardona wrote:

>Hi all,
>
>Please find attached the summary of changes after all your feedback,
>special thanks to Randy Presuhn for all the detailed comments.
>
>Please note that the storageType objects are being set as CMTS only
>requirement docsIfCmtsGroupV2  since the CM compliances are read-only or
>any other tables do not apply to CMs.
>
>Change #9 for the docsIfCmRangingTimeout please review the other
>question sent to the list and OSSI reflector
>
>Please see if the coments are being captured properly.
>
>
>PDF has the color change, also attached text file for convenience.
>
>
>Thanks
>
>Eduardo
>