Subject: RE: Use of RSVP in MPLS (2)

From: Javier Antich <[email-masked]>
Date: Thu, 14 Jun 2001 18:18:28 +0200

Hi

Traffic Engineered tunels are expected to be innitiated/terminated in
routers as a result of a traffic engineered path calculation (either by the
administrator, by a network simulation tool, or by constraint-based
routing). As a result, currently is the administrator, by configuration, who
triggers the establishment of TE-LSPs, not the end applications. TE tunnels
are something that end application are not aware today, probably also
because a TE tunnel does not give the application any resources reservation,
unless you implement some other features like CAR, WRR, WFQ, .... TE
currently is useful for network administrators to have a better utilization
of the network resources, rather than for applications asking for QoS like
in "traditional" RSVP.

                                          ^   ^
==============ooo====(.)v(.)====ooo=====
Javier Antich Romaguera
Network Consultant
---------------------------------------------------------------------------
TELINDUS 
Pza. Ciudad de Viena, 6-2º
28040 Madrid 
---------------------------------------------------------------------------
[email-masked]
tel: +34 91 456 00 08
fax: +34 91 536 10 74
---------------------------------------------------------------------------
For more information about our products and services,
please visit our website http://www.telindus.com
---------------------------------------------------------------------------
Full connectivity & mobility
==================ooo0===0ooo========

> -----Mensaje original-----
> De:	Roberto Canonico [SMTP:[email-masked]]
> Enviado el:	jueves 14 de junio de 2001 18:09
> Para:	[email-masked]
> CC:	[email-masked]
> Asunto:	Use of RSVP in MPLS (2)
> 
> Francis, thanks for your reply.
> A few more questions for all ...
> 
> > The protocol allows the setup to be initiated from an end system.
> > However, the question is whether or not the service provider policy
> accepts LSP establishment requests from a host end system.
> 
> Q1 - Has such a scenario any chance to be implemented in "real" MPLS
> networks ?
> 
> Q2 - I remember in RSVP for IntServ, the resource
>         reservation process was originated by a request
>         issued by an application through a special API.
>         In the case of RSVP-TE, what is the event that triggers
>         this signalling phase ?
>         In different words, what entities are in charge of
>         deciding if a new LSP is to be created in an MPLS network ?
> 
> Thanks again for your attention.
> Regards,
>     Roberto Canonico
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> "Roberto Canonico" <[email-masked]> on 14/06/2001 13:34:30
> 
> 
> 
>  To:      [email-masked]
> 
>  cc:      (bcc: Francis ARTS/BE/ALCATEL)
> 
> 
> 
>  Subject: Use of RSVP in MPLS
> 
> 
> 
> 
> 
> 
> Hi all.
> After reading several documents and
> IDs related to RSVP-TE and its use in MPLS
> to setup new LSPs, it is clear that the setup
> process is initiated by the ingress LSR
> which sends an RSVP PATH message downstream
> to the egress LSR.
> Now my question are:
> - who instructed the ingress LSR to send the
>   RESV message ?
> - would be it possible for the setup process to
> be initiated by a end system wishing to establish
> a new LSP through the MPLS network (a la IntServ) ?
> Thanks in advance for your clarifications.
> Regards,
>     Roberto Canonico