The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2001-Sep> msg00066



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

RE: A Question on LMP for unbundled links

  • From: "Mohammad Siddiqui" <siddiqui_2000@hotmail.com>
  • Date: Wed, 26 Sep 2001 00:32:34 +0000
  • Cc: mpls@UU.NET
  • Resent-Date: Tue, 25 Sep 2001 22:37:49 -0400
  • To: jplang@calient.net, mpls-ops@mplsrc.com
  • X-OriginalArrivalTime: 26 Sep 2001 00:32:34.0948 (UTC) FILETIME=[BC902440:01C14622]
  • X-Originating-IP: [64.102.254.33]

Hi Jonathan:

Thanks a lot for your profound reply. It's much appreciated.

The follow-up question that I've is that, can we still assign a local link 
ID independently of the TE Link ID to an unbundled TE Link (A TE Link with 
only one component link)? In which case, TE Link ID will be an addressable 
entity and component link ID will be a locally assigned identifier. Do you 
think if such an assignment is made, the neighboring nodes have to implement 
link bundling support (as mentioned in draft-ietf-mpls-bundle-00.txt? Or 
there are no pit-falls associated with assigning TE link ID and component 
link ID independently, for unbundled interfaces.

Thanks in advance.

/Siddiqui

>From: Jonathan Lang <jplang@calient.net>
>To: 'Mohammad Siddiqui' <siddiqui_2000@hotmail.com>, mpls-ops@mplsrc.com
>CC: mpls@UU.NET
>Subject: RE: A Question on LMP for unbundled links
>Date: Tue, 25 Sep 2001 09:20:48 -0700
>
>Siddiqui,
>
> > -----Original Message-----
> > From: Mohammad Siddiqui [mailto:siddiqui_2000@hotmail.com]
> > Sent: Monday, September 24, 2001 10:29 AM
> > To: mpls-ops@mplsrc.com
> > Cc: mpls@UU.NET
> > Subject: A Question on LMP for unbundled links
> >
> >
> > Hi:
> >
> > I've a question on how the TE Link ID and Component Link Port IDs that
> > should be assigned for unbundled links. By unbundled link, I am 
>referring
>to
> > the bundle (aka TE Link) that contains only ONE component Link.
> > Specifically, how the two neighboring node will communicate Link Summary
> > messages for the unbundled links. What should be the TE Link ID within 
>the
>
> > LMP Link Summary message in the unbundled case. Would TE Link Id = 0
> > suffices for unbundled links?
>The TE Link Id would equal the Data link Id.
>
> > Or TE Link Id has to be a routable address or
> > should be a number derived from the unnumbered space. Also, since UNI
>125.6
> > requires TE Link ID to be set to the TNA address, how we deal with this
> > requirement for unbundled links. Can we set (local TE Link ID, component
> > link ID) = (0, TNA address) for unbundled UNI interfaces?
>For UNI 125.6, the TNA address is equal to the TE Link Id.
>
> >
> > Your reply to this question will be much appreciated.
> >
> > Thanks in advance.
> >
> > Regards
> >
> > /Siddiqui.
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at
>http://explorer.msn.com/intl.asp


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml