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 10:56 PM
> Subject: RE: [ipcdn] pktcSigPowerRingFrequency description change
...
> I was looking at some of the comments regarding 'pktcRingCadence' and
> would like to propose the following text:
...
> "This object provides an encoding scheme for ring cadences, including
> repeatability characteristics.
>
>
>
> The first three octets are reserved. The octets that follow are used to
> encode a 'bit-string', with each bit corresponding to 50 milliseconds. A
> bit value of '1' indicates the presence of a ring-tone and a bit value
> of '0' indicates the absence of a ring-tone, for that duration (50 ms).
> This entire bit-string MUST be placed using network-byte order and
> encoded as octets that preserve that ordering.

"placed"?

Also what value do the one to seven bits after the first bit-count bits
have?  must they be set to any particular value?  on a get, do they
need to have the same value that they were set to?

> The first two of the reserved octets indicate the length of the encoded
> 'bit-string' and MUST range between 1 and 264. (Note: The length MUST
> also be consistent with the number of octets that encode the cadence).

Which octet is high order, which is low order?
Suggest adding "in bits" before "and MUST".

> The third of the reserved octets indicates 'repeatability' and MUST
> support only the values 0x80 or 0x00 - the former value indicating
> 'repeatability' and the latter indicating 'non-repeatability'.
...

Instead of "support only the values", suggest "be either"

Randy