Subject: Re: [Adslmib] Non-Standard Band Plans [Comments on Ver 05 draft VDSL-LINE-MIB]

From: [email-masked]
Date: Thu, 31 Oct 2002 11:19:02 +0200

Umberto,

I don't see anything special in a non-standard band plan that requires a
special behavior (except for specifying the "propietary" band plan itself,
which should be out of the scope of the formal MIB).

Moreover, MCM is NOT a precondition for using a non-standard band plan .
Can you explain why "the agent will reject the SET request" when an
operator prefers to use SCM with a non-standard band plan?

best regards,
Moti Morgenstern

Senior System Engineer
Inovia Telecoms Ltd.
Member of the ECI Telecom group
30 Hasivim St.
Petach Tikva, Israel 49133
Tel.: +972-3-9266258 Fax: +972-3-9268182
e-mail: [email-masked]

                      "Umberto                                                                                                         
                      Bonollo"                 To:      <[email-masked]>, <[email-masked]>                                            
                      <umberto@                cc:                                                                                     
                      nstc.nec.com.au>         Subject: [Adslmib] Non-Standard Band Plans [Comments on Ver 05 draft VDSL-LINE-MIB]     
                      Sent by:                                                                                                         
                      adslmib-admin@                                                                                                   
                      ietf.org                                                                                                         

                      31/10/02 09:07                                                                                                   

To Bob Ray and Rajesh Abbi:

Hi,

Your comments on the following would be appreciated:

1. To enter a non-standard band plan the manager:

1.1  first has to set vdslLineConfBandPlan = other(4).

1.2 Thereafter, the tables called vdslLineMCMConfProfileTxBandTable
and vdslLineMCMConfProfileRxBandTable *** must *** contain at least
one row entry each.

2. This entails a few things:

2.1 The PDU that sets vdslLineConfBandPlan = other(4) must at the
same time (within the same PDU) create at least one row entry in each of
vdslLineMCMConfProfileTxBandTable and vdslLineMCMConfProfileRxBandTable,
else the agent will reject the SET request.

2.2 Given 2.1 has occurred, at no stage will the agent
allow vdslLineMCMConfProfileTxBandTable or
vdslLineMCMConfProfileRxBandTable
to become empty as this means nothing
with respect to the configuration.

2.3 Hence, now when the manager sets  vdslLineConfBandPlan to something
else
apart from other(4) then at the same time (in the same PDU) the row entries
in vdslLineMCMConfProfileTxBandTable and vdslLineMCMConfProfileRxBandTable
will all be deleted.

3. So the above discussion assumes:

3.1 vdslLineMCMConfProfileTxBandTable and vdslLineMCMConfProfileRxBandTable
can each never be empty when vdslLineConfBandPlan = other(4) .

4. Comments on alternate meanings for non-standard band plans are welcomed
(e.g.):

4.1 Does vdslLineConfBandPlan = other(4) with
vdslLineMCMConfProfileTxBandTable is empty and
vdslLineMCMConfProfileRxBandTable is empty have any meaning for the
equipment?
Ans: No[?]

4.2 Does vdslLineConfBandPlan = other(4) with
vdslLineMCMConfProfileTxBandTable is empty and
vdslLineMCMConfProfileRxBandTable is nonempty have any meaning for the
equipment?
Ans: No[?]

4.3 Does vdslLineConfBandPlan = other(4) with
vdslLineMCMConfProfileTxBandTable is nonempty and
vdslLineMCMConfProfileRxBandTable is empty have any meaning for the
equipment?
Ans: No[?]

Regards,
Umberto Bonollo ([email-masked])
NEC Australia

_______________________________________________
Adslmib mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/adslmib

_______________________________________________
Adslmib mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/adslmib