The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-May> msg00020



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

RE: Reasons to deploy MPLS-TE

  • From: Ping Pan <pingpan@cs.columbia.edu>
  • Date: Tue, 4 May 2004 14:01:22 -0400 (EDT)
  • cc: Stephen Mullaney <stephen.mullaney@parc-technologies.com>, mpls-ops@mplsrc.com
  • Resent-Date: Tue, 4 May 2004 14:35:07 -0400
  • To: Jean Philippe Vasseur <jvasseur@cisco.com>
  • X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by host.secure4-hosting.net id i44I3KSt014399
  • X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report='X_AUTH_WARNING 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __HAS_MSGID 0, __SANE_MSGID 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, DEAR_SOMETHING 0.000, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0'
  • X-PMX-Version: 4.6.0.97784, Antispam-Core: 4.6.0.97340, Antispam-Data: 2004.4.25.98889

In addition, the ability to define, pindown and monitor the data path.
ERO's and RRO's do wonders.

On Tue, 4 May 2004, Jean Philippe Vasseur wrote:

> I think that the short answer is indeed: that depends ... This could be
>          1) FRR
>          2) Bandwidth optimization
>          3) Bandwidth guaranties
>   or *any* combination of the above and we have several examples of such
> combinations
>
> JP.
>
> At 10:00 AM 5/4/2004 +0100, Stephen Mullaney wrote:
> >I have talked to quite alot of providers about TE and as Eric said, FRR is
> >top of the list.  However, in countries where BW costs an arm and a leg
> >(Sth Africa for instance), TE is seen as a way of putting off network
> >upgrades which saves both money and pain.  I have also seen this
> >requirement in Eastern Europe and know it is in use in Australia.
> >
> >-----Original Message-----
> >From: McCallum, Robert [mailto:robert.mccallum@thus.net]
> >Sent: 03 May 2004 15:40
> >To: 'Eric Osborne'; Lavoisier J.L.Farias; mpls-ops@mplsrc.com
> >Subject: RE: [MPLS-OPS]: Reasons to deploy MPLS-TE
> >
> >
> >Of course Eric isnt in the slightest bit biased about TE :-)
> >
> >Robert McCallum
> >CCIE #8757 R&S
> >01415663448
> >07818002241
> >
> > > -----Original Message-----
> > > From: Eric Osborne [mailto:eosborne@cisco.com]
> > > Sent: 03 May 2004 15:39
> > > To: Lavoisier J.L.Farias; mpls-ops@mplsrc.com
> > > Subject: Re: [MPLS-OPS]: Reasons to deploy MPLS-TE
> > >
> > >
> > > On Sat, 1 May 2004 17:47:16 -0300, Lavoisier J.L.Farias
> > > <lavoisier_farias@uol.com.br> wrote:
> > >
> > > > Dear Sir,
> > > >
> > > > My name is Lavoisier Farias and I work in a Brazilian software
> > > > company. I am also currently working in my thesis at the State
> > > > University of Campinas (UNICAMP). I have some basic questions
> > > > regarding MPLS. In Brazil, I do not know any service
> > > provider that is
> > > > implementing MPLS-TE in their networks(*). Hopefully there
> > > exist some
> > > > one that I don't know yet. So, my questions are:
> > > >
> > > >  - What are the reasons to the service providers around the world
> > > > deploying MPLS-TE ? Is the lack of bandwidth the main requirement ?
> > >
> > > In my experience, fast reroute has been the biggest driver
> > > for installing
> > > mpls-te in a network; there are certainly large networks out
> > > there using
> > > it for bandwidth optimization and stats collection, but FRR
> > > has been the
> > > most widely talked about.
> > >
> > > >  - Is there exist some network using MPLS-VPN (2547) and MPLS-TE at
> > > > the same network ?
> > >
> > > Yes
> > >
> > > > And final question more related to my thesis subject:
> > > > - Is the reoptmization feature available in Cisco Routers
> > > really used
> > > > into deployed MPLS-TE networks ?
> > >
> > > Yes
> > >
> > >
> > >
> > > eric
> > >
> > > >
> > > > Regards and Thanks,
> > > >
> > > > Lavoisier José Leite Farias.
> > > > Network System Engineer.
> > > > (*) There are Traffic Engineer in some networks but since
> > > they have an
> > > > existing ATM network.
> > > >
> > > >
> > > > -------
> > > > The MPLS-OPS Mailing List
> > > > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> > >
> > >
> > > -------
> > > The MPLS-OPS Mailing List
> > > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> > >
> >
> >-------
> >The MPLS-OPS Mailing List
> >Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> >Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> >
> >
> >-------
> >The MPLS-OPS Mailing List
> >Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> >Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>

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