RE: pktcSigPowerRingFrequency description change

 
While not disagreeing with the proposal to delete the DEFVAL clause from
the MIB Object definition, I am not completely comfortable with the fact
that IETF MIB draft would make a reference to the document
([PKT-SP-MIB-SIG]) which will be obsolete when draft becomes an RFC (or
soon thereafter). Besides, I am not sure to which extent the mentioning
of compliency with the [PKT-SP-MIB-SIG] or with the [ITU-T-J169] is
unambigous. Not sure presisely what this "compliency" means. What's the
intention here - to say that for MTAs compliant with NorthAmerican-PC
the defval should be f20 but for MTAs compliant with Euro-PC the defval
should be f25Hz ? I think the reference to the compliency should be made
less ambiguous. 
 
Eugene.

________________________________

From: [email protected] [mailto:[email protected]] On Behalf
Of Beacham Gordon-CGB005
Sent: Tuesday, October 19, 2004 8:48 AM
To: [email protected]; '[email protected]'
Subject: [ipcdn] pktcSigPowerRingFrequency description change


The following changes are recommended to the description of the
pktcSigPowerRingFrequency object.
 
delete: DEFVAL { f20Hz }
add: This default value for this object MUST be f20Hz for MTAs compliant
to [PKT-SP-MIB-SIG]. The default value for this object MUST be f25Hz for
MTAs compliant to [ITU-T-J169].
 
Gordon

_______________________________________________
IPCDN mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ipcdn