The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Dec> msg00141



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: GMPLS - Hierarchies

  • From: neil.2.harrison@bt.com
  • Date: Wed, 6 Dec 2000 22:06:57 -0000
  • Cc: mpls@UU.NET, ip-optical@lists.bell-labs.com

We really must start to get layering in into our heads......the user-plane
*must* apply a well-known piece of characteristic information between the
source and sink of a trail.  These are the 'true' labels....the fact that
some control-plane sets them up is almost incidental.  The real arguments
starts as to the *nature* of that control-plane, but as I said that is
orthogonal to the fact that LSPs do create real hierarchies (in the
user-plane).

neil

> -----Original Message-----
> From:	Udo Neustadter [SMTP:neustadter@tropicnetworks.com]
> Sent:	Wednesday, December 06, 2000 5:03 PM
> To:	Peter Ashwood-Smith
> Cc:	mpls; ip-optical
> Subject:	RE: Re: GMPLS - Hierarchies
> 
> May understanding is that the hierarchy build is a logical one, and no
> real
> labels are added to the flow. The flow is identified by the specific TDM
> channels. I just can not see where the waste of bandwidth is coming from.
> 
> Udo
> 
> >...
> >
> >  This is most likely to occur with TDM and OXC equipement at the OC-192
> and OC-48 rates where there is a
> >close mapping between the OXC lambda and the TDM signal bandwidth. It
> won't
> work sell so well at lower rates
> >because you waste too much bandwidth and are forced into a heirarchy
> whether you want one or not.
> >
> >  Cheers,
> >
> >  Peter Ashwood-Smith
> >...