Re: IETF NCS Sig MIB Tone Table

Hi -

> From: "Beacham Gordon-CGB005" <[email protected]>
> To: <[email protected]>; <[email protected]>
> Sent: Wednesday, January 05, 2005 8:22 AM
> Subject: [ipcdn] IETF NCS Sig MIB Tone Table
...
> PktcSigDevToneEntry ::= SEQUENCE {
...

This really should be TWO tables.
One would control properties that apply to the whole sequence,
and a second with an additional index to permit individual
entries for each of the tones in a sequence.  This would
reduce the number of object definitions in the MIB module,
make the scope of applicability of the attributes clearer, and
generally make it easier to understand what's going on.

When I see
>     pktcSigDevToneFirstFrequency            Unsigned32,
....
>     pktcSigDevToneSecondFrequency           Unsigned32,
...
>     pktcSigDevToneThirdFrequency            Unsigned32,
...
>     pktcSigDevToneFourthFrequency           Unsigned32,
...
>     pktcSigDevToneFifthFrequency            Unsigned32,

I get the feeling that the model needs to be re-factored, both in light
of the need to support these more complex sequences and from
a simple data modeling perspective.

Randy