[45025] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Adoption of MPLS in the Enterprise

daemon@ATHENA.MIT.EDU (Jesper Skriver)
Thu Jan 10 16:41:19 2002

Date: Thu, 10 Jan 2002 22:40:18 +0100
From: Jesper Skriver <jesper@skriver.dk>
To: Lee Watterworth <lwatterworth@rim.net>
Cc: "NANOG (E-mail)" <nanog@nanog.org>
Message-ID: <20020110224018.I6320@skriver.dk>
Mail-Followup-To: Jesper Skriver <jesper@skriver.dk>,
	Lee Watterworth <lwatterworth@rim.net>,
	"NANOG (E-mail)" <nanog@nanog.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BE61C6476F812B429389D76D730A11D1035A13@xch04ykf.rim.net>; from lwatterworth@rim.net on Wed, Jan 09, 2002 at 09:40:02PM -0500
Errors-To: owner-nanog-outgoing@merit.edu


On Wed, Jan 09, 2002 at 09:40:02PM -0500, Lee Watterworth wrote:
> 
> Hi,
> 
> MPLS has been in use at providers for a number of years.  
> 
> Does anyone have experience with MPLS adoption at the enterprise level?  For
> what reasons was it deployed?

The same reasons service providers do it - offer multiple L3 networks on
the same physical infrastruture, also known as MPLS L3 VPN's

At least that's the deployments I've seen.

/Jesper

-- 
Jesper Skriver, jesper(at)skriver(dot)dk  -  CCIE #5456
Work:    Network manager   @ AS3292 (Tele Danmark DataNetworks)
Private: FreeBSD committer @ AS2109 (A much smaller network ;-)

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.

home help back first fref pref prev next nref lref last post