[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Label type to be used

Dimitri, Kireeti,
Thanks for the clarifications. The changes proposed look ok.

a) do you agree with the above change?

yes

b) in your implementation today, what do expect the label to represent
   i) in the case of [PSC, LSC]?

port

ii) in the case of [PSC, TDM] with a fully transparent signal?

port

c) if you implement as the draft says, would it be a hardship to change
   this?

n/a

thanks,
/anca

At 11:19 AM 3/18/2004 -0800, Kireeti Kompella wrote:
Hi Anca,

On Thu, 18 Mar 2004, Anca Zamfir wrote:

> Does "label represents a port" means port label must be used in signaling?
> Or a label (from the respective LSP domain) that takes the whole port
> resource should be used? For example, in the [PSC, TDM] I think that
> signaling should still use a TDM label. Is this interpretation correct?

"represents a port" means port label should be used.

If you look at GMPLS-SONET-SDH, last para of section 2:

   The traffic parameters and label encoding defined in [RFC3471]
   Section 3.2 MUST be used for fully transparent STS-1/STM-0/STS-
                                ^^^^^^^^^^^^^^^^^

If you use traffic params from 3471/3473, you *cannot* use an SUKLM
label.  However, section 3.2 of 3471 covers lots of label types (port,
lambda, ATM/FR), so that reference is not very helpful, except to say
that the label is not SUKLM.

Kireeti.
-------