The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2001-Dec> msg00069



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

Re: MPLS VPNs interconnection

  • From: Robert Raszuk <raszuk@cisco.com>
  • Date: Tue, 18 Dec 2001 23:06:08 +0100
  • CC: Karl Garcia <Karl.Garcia@cosinecom.com>, "'Chrysostomos Tziouvaras '" <tziou@ics.forth.gr>, "'mpls-ops@mplsrc.com '" <mpls-ops@mplsrc.com>
  • Organization: Signature: http://www.employees.org/~raszuk/sig/
  • Resent-Date: Tue, 18 Dec 2001 19:51:32 -0500
  • To: Dan Jamison <Dan.Jamison@cosinecom.com>


I am glad it works for you on site !!! But what you did is something
that should be called utilization of various media/protocols to access
VPNs not "VPNs interconnection" ;-).

R.

> Dan Jamison wrote:
> 
> I'm at a customer now.  We have implemented IPSec dial, IPSec tunnels
> from various CPE, and frame comming into the Cosine VRF.  The Cosine
> VRF is being used as a IPSec/MPLS gateway and also for access to the
> Internet for other Cisco VRFs (and IPSec connected sites) connected
> sites using our stateful firewall.
> 
> Dan Jamison
> Cosine NC
> 
> -----Original Message-----
> From: Karl Garcia
> To: 'raszuk@cisco.com'; Chrysostomos Tziouvaras
> Cc: mpls-ops@mplsrc.com
> Sent: 12/18/2001 10:34 AM
> Subject: RE: MPLS VPNs interconnection
> 
> Hi,
> 
> Well, Robert is right that this is not possible in the Cisco world.
> :-)
> 
> However, not naming any names, there is equipment available today
> (actually shipping !)
> that can interconnect BGP/MPLS VPNs (layer 3), IPSec VPNs, FR and ATM
> VPNs.  In Q1 of 2002, this equipment will also support layer 2 MPLS
> VPNs.
> 
> And it is built for the SP; that means it is carrier-class and
> scalable.
> 
> Hope this helps,
> _______
> Karl
> 
> Karl Garcia
> Sr. Mrkt. Engr.
> CoSine Communications, Inc.
> 
> -----Original Message-----
> From: Robert Raszuk [ mailto:raszuk@cisco.com
> <mailto:raszuk@cisco.com>
> ]
> Sent: Tuesday, December 18, 2001 4:10 AM
> To: Chrysostomos Tziouvaras
> Cc: mpls-ops@mplsrc.com
> Subject: Re: MPLS VPNs interconnection
> 
> I don't think this is possible on the SP side.
> 
> Of course all of the below provide a concept of hub & spoke so at the
> Hub side of your customer you could interconnect the VPNs as you like.
> 
> R.
> 
> > Chrysostomos Tziouvaras wrote:
> >
> > Dear all,
> > can anyone provide me pointers to documentation about the
> interconnection
> > of VPNs that employ different technologies, such as layer 2 MPLS
> VPNs,
> 
> > layer 3 MPLS VPNs and traditional VPNs (eg FR or ATM VPNs).
> >
> > Regards
> > Chrysostomos
> >
> > -------
> > The MPLS-OPS Mailing List
> > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> <http://www.mplsrc.com/mplsops.shtml>
> > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> <http://www.mplsrc.com/mpls-ops_archive.shtml>
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> <http://www.mplsrc.com/mplsops.shtml>
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> <http://www.mplsrc.com/mpls-ops_archive.shtml>
> ########################################################################
> 
> ############################## This email communication may contain
> CONFIDENTIAL INFORMATION and is intended only for the use of the
> intended recipients identified above.  If you are not the intended
> recipient of this communication, you must not use, disclose,
> distribute,
> copy or print this email. If you have received this communication in
> error, please immediately notify the sender by reply email, delete the
> 
> communication and destroy all copies.
> ########################################################################
> 
> ##############################
> 
> ######################################################################################################
> This email communication may contain CONFIDENTIAL INFORMATION and is
> intended only for the use of the intended recipients identified
> above.  If you are not the intended recipient of this communication,
> you must not use, disclose, distribute, copy or print this email. If
> you have received this communication in error, please immediately
> notify the sender by reply email, delete the communication and destroy
> all copies.
> ######################################################################################################

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