coments on draft G.SHDSL.BIS MIB

Thank you Clay for taking on the editorship of G.SHDSL.BIS.
My comments are below.

Reference this paragraph:

> 2.3.2.   Changes to Line Rate Objects
>
>  Four objects in the HDSL2/SHDSL Line MIB have rate limitations.
>   In each case, these objects have the syntax
>
>        SYNTAX      Unsigned32(0..4112000)
>
>   Changes introduced in G.SHDSL.bis support an increased upper rate
>   of 5696 kbits/s, leading to the updated syntax
>
>        SYNTAX      Unsigned32(0..5696000).


Comments:

I think the original RFC3276 was incorrect with respect to the maximum line
rate for 2 pairs.
A single G.SHDSL pair may have a line rate up to 2312000 bps.  With two
pairs, doubling that amount
would be 4624000.  I think RFC3276 incorrectly doubled the value of
(2048000 + 8000) to get 4112000.

Now, with 4 wire pairs, it seems correct to have 2312000 * 4,  or 9248000
as the maximum line rate.
Am I missing something ?  Is there something I don't understand about the
5696000 number ?

I also think the defaults should follow G.SHDSL instead of HDSL2.
The default for hdsl2ShdslSpanConfMinLineRate would be 200000 (192000 +
8000).
And the default for hdsl2ShdslSpanConfMaxLineRate would be 2312000.

Also, I think a status parameter with the data rate or effective bandwidth
of the span would
be useful.  The maximum data rate would be (2312000 - 8000) * 4, or
9216000.

hdsl2ShdslStatusActualDataRate OBJECT-TYPE
           SYNTAX      Unsigned32(0..9216000)
           UNITS       "bps"
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
           "Contains the actual data rate for this HDSL2/SHDSL span. "

       ::= { hdsl2ShdslSpanStatusEntry xxx }


Comments ?

Lee Nipper
Verilink Corporation