The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2002-Jan> msg00206



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

Re: Market info re: MPLS

  • From: Mathew Lodge <mathew@cplane.com>
  • Date: Wed, 23 Jan 2002 17:56:40 -0800
  • Cc: Daniel Kharitonov <dkharitonov@yahoo.com>, saqibj@margallacomm.com, mpls-ops@mplsrc.com
  • Resent-Date: Wed, 23 Jan 2002 22:10:28 -0500
  • To: raszuk@cisco.com
  • X-Sender: lodge@localhost

At 02:22 AM 1/24/2002 +0100, Robert Raszuk wrote:
>Pls notice that 2547 does not require ANY ACTION on the end customer
>site to connect his sites. In fact it transparently provides a
>"multihop" IGP result - something what Daniel was looking for. How it
>can get more simple ???

Operationally, it's not the same as if the different sites were just 
connected together in a single enterprise network. With 2547, the customer 
now has to maintain a routing relationship with a service provider (CE and 
PE must exchange routing info somehow). This is either via a dynamic 
routing protocol or static routes. If it's static routes, then these must 
be manually figured out and updated manually. If it's dynamic, the customer 
must be careful what he advertises and worry about the routes he's 
receiving, and otherwise change behavior because the PE belongs to an 
external, 3rd party entity.

So yes, 'twas badly worded to imply that some the protocols could be 
simpler -- operationally, it could be simpler -- the irony being that I was 
trying to argue that no routing protocol changes would be just fine :-/

Cheers,

Mathew



| Mathew Lodge                 | mathew@cplane.com     |
| Director, Product Management | Ph: +1 408 789 4068   |
| CPLANE, Inc.                 | http://www.cplane.com | 

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