The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2001-Mar> msg00172



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

Re: About RSVP-TE scalability - please help

  • From: Yakov Rekhter <yakov@juniper.net>
  • Date: Mon, 26 Mar 2001 14:04:29 -0800
  • cc: mpls-ops@mplsrc.com
  • Resent-Date: Mon, 26 Mar 2001 19:01:18 -0500
  • To: Srihari Raghavan <sraghava@vt.edu>

Srihari,

> Hi all,
>    I have some questions regarding RSVP/RSVP-TE. Can anyone please help me
> with it?
> 
>    Am I right in saying the following things about RSVP/RSVP-TE when used
> for MPLS traffic engineering at the core/backbone networks?
> 
>    1. RSVP in its original form is used to set up per-flow (data traffic)
> state at each intermediate router. Is this found not scaleable because of
> the 'soft state', potential large number of data flows and non usage of
> reliable protocols like TCP?

Largely because of the potentially large number of flows.

>    2. RSVP-TE, by contrast, is ONLY used to set up CRLSPs or ERLSPs and not
> 'flows' like that as MPLS 'traffic trunks'. Because, the number of LSPs (CR
> or ER) can be far less than the number of traffic flows through it, RSVP-TE
> is more scalable?
>       Or, is it the case that the 'labels' being distributed by the egress
> using RSVP-TE defines the traffic across the LSP and since 'labels' and LSPs
> can be subject to label merging and LSP aggregation, RSVP-TE is scalable in
> the core? Or is there anything that I am missing here about RSVP-TE
> scalability?

The former. For more on this see rfc2430.

Yakov.

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