Re: pktcSigPowerRingFrequency description change

Hi -

> From: "Sumanth Channabasappa" <[email protected]>
> To: "Eugene Nechamkin" <[email protected]>; "Beacham Gordon-CGB005" <[email protected]>; <[email protected]>
> Sent: Wednesday, October 20, 2004 11:03 AM
> Subject: RE: [ipcdn] pktcSigPowerRingFrequency description change
...
> How about:
>
> "The default value for this object is dependent on the primary usage
> area of the device. For devices compliant with PacketCable (North
> America)  it MUST be set to f20Hz and for devices compliant with
> IPCablecom (Europe)  it MUST be set to f25Hz."
...

In addition to Harrie's point about whether this is an exhaustive list
of possibilities, note that these MUSTs impose a *stronger*
conformance requirement than the original DEFVAL.  RFC 2578
clause 7.9 says:

   The DEFVAL clause, which need not be present, defines an acceptable
   default value which may be used at the discretion of an agent when an
   object instance is created.  That is, the value is a "hint" to
   implementors.

That's a *lot* weaker than a MUST in the DESCRIPTION clause.
Now if that's what the group wants to do, fine.  I just want to be sure
it's a conscious decision.

Randy