The MPLS-OPS Archive

[Alok <alokdube@hotpop.com>]

Hello Folks,

can people please share some information on the best way to setup 
signalled LSPs?

Typically, are they as follows:
a. setup an LSP to an end point.
b. implement some CAR/rate-limited way to cap traffic to get to the end 
point.

at this point, as the signalling travels to the end point of the LSP, it 
has to satisfy some constraints.

However, say we have;

A-----B------<big network>--C--<big network>----D---E
                                                   

and i wish to setup an LSP which satisfies some constraints like 
bandwidth/Latency etc.

C being the common point for all possible paths from A to E.

Is there a way that:

a. The signalling carries the source of the LSP and say a "sequence" number.
b. The signalling tries all possible paths to E via the big network domain
c. the (sequence number, source identifier) are sufficient to identify 
the "signal" to avoid looping.
d. C may not be a looping point but since it has seen /tried to signal 
the (sequence number, source identifier) it does not try the same again.
e. again from C multiple paths are signalled (all of those which can 
satisfy the constraints)
f. one of them reaches E 1st, if there is enough (constraint) from D to 
E, D forwards it to E , else D can simply "drop/send a nack".
g. once E has accepted one path to A and sets up a reverse path, it can 
drop all other incoming based on source identifer/send a nack to all 
other requests that hit it based on (source,sequence).

-thanks
Alok





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