RE: docsIfCmtsModulationTable and StorageType TC ?

Andy, 
 
Let me expand the question to the DOCSIS reflectors,
 
This is a well known issue, that has its roots in RFC 2670 where no
read-create entries has a defined StorageType value
Also the IPCDN group is aware of the new guidelines for MIB revision
(current draft 02 )  in section 4.6.4 defines requirements to say what
to do at agent initialization for read-create entries and storageType is
one of the various options. 
 
 
Predefined entries I believe are well cover by the row object
docsIfCmtsModulationEntry which says "Initial default entries may be
created at system initialization time." , It leaves them some sort of
persistence, weather permanent or read-only are another subject.
 
A current ECR to OSSI spec  OSSIv2.0-R-04.0121-2 covers the cases where
Entries in the modulation profile table may not allow SNMP SETs as a
regular read-create entry.
 
Since this optional template/default topic is a vendor differentiation
area we believe that it is OK having in the MIB the minimum
requirements, for those vendors not willing to implement default
entries, specially due the broad implementation of this MIB as is right
now. 
 
 
We are close to request last Call for this MIB and would prefer not to
introduce optional features, only broken pieces.
Although, we would follow carefully the Bert's and other MIB doctors,
advisors and IPCDN members recommendations in this area to get the MIB
clear as possible and ready for IESG approval.
 
Let me know if I cover your concerns
 
Eduardo
 
-----Original Message-----
From: Donati Andrew-MGIA0477 [mailto:[email protected]] 
Sent: Thursday, January 22, 2004 9:15 AM
To: '[email protected]'
Cc: Eduardo Cardona; '[email protected]'; '[email protected]'
Subject: docsIfCmtsModulationTable and StorageType TC ?



All,
 
Do all Read-Create tables within the DOCS-IF-MIB need to have
StorageType objects?
There is a case in the docsIfCmtsModulationTable where the presence of
this object will be very helpful.
If a vendor chooses to implement several pre-configured default
modulation profiles that cannot be destroyed,
these rows can have the status of "permanent" or "readOnly" (depending
on whether or not values are allowed
to be changed within these rows).   Currently, if a vendor desires to
implement one or more pre-defined default
modulation profiles that are intended to not be deleted, it may be
difficult to comply with the Row Status
Textual Convention described in SMIv2- TC.   
 
Regards,
Andy Donati
Motorola BCS