The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Apr> msg00068



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

static MPLS (was Re: Last Call on RSVP Label Allocation for Backup Tunnels)

  • From: Curtis Villamizar <curtis@workhorse.fictitious.org>
  • Date: Wed, 04 Apr 2001 19:49:36 -0400
  • cc: curtis@avici.com, Dave Danenberg <dave_danenberg@litchfieldcomm.com>, neil.2.harrison@bt.com, giles@goneto.net, mpls@UU.NET


In message <3ACB3DAF.CBFEC282@alcatel.com>, Robin Park writes:
> This is a multi-part message in MIME format.
> --------------77D7BFECF73FA26A09450C19
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> Dave,
> 
> Alcatel's implementation of MPLS does support statically configured LSPs.  I 
> would
> guess other vendors support statically configured LSPs.

Ours supports this feature as well.  So does Cisco and Juniper.

> Whether service providers widely use statically configured LSPs is another
> question, but a blanket assumption that all LSPs are configured via signaling
>  may
> not be true.

My only point was that I know of no one that is building a network
using statically configured LSPs.  The assumption was made by Dave
that the opposite was true.  I was just commenting on the validity of
that assumption.

> In these cases, the control-plane would not detect data-plane failures.

Providing measurement capabilities to better deal with rare errors
that may be undetectable when using an unused feature sounds like a
weak argument.  I suppose it would be up to the TE-WG whether that
constitutes a requirement.  In the ITU maybe.  :-)

> Regards,
> 
> Robin.

The subject says "Last Call on RSVP Label Allocation for Backup
Tunnels" and we have strayed off this topic.

Curtis