Re: LCAS and GMPLS

[Wataru Imajuku <imajuku.wataru@lab.ntt.co.jp>]

Hi, Stephen

> Stephen,
>
>
> > Another requirement to consider is whether the associating the LSPs 
> needs to be recursive.  For example, consider an STS-3c-2v where one of 
> the STS-3c is a real contiguously >
> >  concatenated LSP, and the other is actually an STS-1-3v (three STS-1 
> LSPs).  From a bearer plane point of view, this is possible.  Does the 
> service maintain the two STS-3c LSP > association and the three STS-1 LSP 
> association?
> > I suggest that there be a requirement for recursive association.
>
> IB>> This is an interesting requirement. Fortunately, it is possible to 
> realize this requirement via GMPLS signaling by including several 
> ASSOCIATION objects of the same type into the same Path message. For 
> instance, one of them will indicate that the signalled LSP belongs to the 
> nested VCAT group, while another -to the nesting VCAT group.

 Current ASSOCIATION objects relates only two connections.
 I think that introducing the concept of virtual connection indicating 
the group of VCAT is good idea.
 Use of Call ID object （assigning VCAT Group) and Assosiation object
(indicating VCAT group in Call ID) may be one of solution.

Best Regards,
Wataru

---------------------------------
Wataru Imajuku
@NTT Network Innovation Labs.
TEL +81-46-859-4315
FAX +81-46-859-5541