The MPLS-OPS Archive

[Mooney Sherman <Mooney.Sherman@gov.ab.ca>]

Here's my two cents!

I agree that an organization would want full control of their IPSec - one of
the solution I had tested over MPLS was Nortel's Connetivity. One thing I
liked was the choice of triple DES and AES encryption choices along with
ability to use compression. The hit on overhead was minimal by using
compression.

Cheers

Mooney 

-----Original Message-----
From: Roger Clark Williams
To: McCallum, Robert
Cc: MPLS-ops Mailing List
Sent: 5/4/2004 7:49 AM
Subject: RE: RE: [MPLS-OPS]:  Mpls and the Banking environmnet

Robert, it is my understanding that the USDA is using either VPNSC or
ISC 
for IPSec deployment. I am not 100% sure of that, but I have heard it 
stated more than once and had USDA people in classes. I will say that,
for 
the most part, a potential IPSec client wants to do it himself and not 
allow a provider or 3rd party do it. I think that is the reason that
most 
classes are on the MPLS iteration of ISC/VPNSC

Roger

At 08:24 AM 5/4/2004, McCallum, Robert wrote:
>Hmmmm,  does it work Roger.  For some reason I seem to be thinking that
>there were issues with this and that
>It is only just now that the solutions are indeed operable.  I maybe
wrong
>its just something in the back of my head
>Which is nagging me and I don't know why.
>
>Robert McCallum
>CCIE #8757 R&S
>01415663448
>07818002241
>
> > -----Original Message-----
> > From: Roger Clark Williams [mailto:rogwilli@cisco.com]
> > Sent: 03 May 2004 22:47
> > To: MPLS-ops Mailing List
> > Subject: Fwd: RE: [MPLS-OPS]: Mpls and the Banking environmnet
> >
> >
> > Cisco has had deployment tools for IPSec VPNs over MPLS for
> > 2-3 years in
> > the form of the VPN Solution Center and the IP Solution
> > Center products
> >
> > Roger Williams
> >
> >
> > >Resent-Date: Mon, 3 May 2004 15:48:20 -0400
> > >X-Authentication-Warning: host.secure4-hosting.net: mplsrc12
> > set sender
> > >to
> > >mpls-ops-request@mplsrc.com using -f
> > >From: "McCallum, Robert" <robert.mccallum@thus.net>
> > >To: "'Andy Brauer - BCX - Networks'" <Andy.Brauer@bcx.co.za>,
> > >         mpls-ops@mplsrc.com
> > >Subject: RE: [MPLS-OPS]:  Mpls and the Banking environmnet
> > >Date: Mon, 3 May 2004 20:25:26 +0100
> > >X-Mailer: Internet Mail Service (5.5.2657.72)
> > >Resent-From: mpls-ops@mplsrc.com
> > >X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/7078
> > >X-Loop: mpls-ops@mplsrc.com
> > >Resent-Sender: mpls-ops-request@mplsrc.com
> > >X-from-outside-Cisco-experimental-header: 128.107.250.143
> > >X-PMX-Version: 4.5.0.92886
> > >
> > >What problems are there with IPSec?  If you envrypt the data
> > before it
> > >gets to the mpls network then that should surely do.
> > >
> > >I do know that Cisco are developing IPSEC MPLS VPNS but I am
> > not sure
> > >if
> > >and when it is due out (it maybe out already).
> > >
> > >Robert McCallum
> > >CCIE #8757 R&S
> > >01415663448
> > >07818002241
> > >-----Original Message-----
> > >From: Andy Brauer - BCX - Networks [mailto:Andy.Brauer@bcx.co.za]
> > >Sent: 03 May 2004 19:05
> > >To: mpls-ops@mplsrc.com
> > >Subject: [MPLS-OPS]: Mpls and the Banking environmnet
> > >
> > >Good Day,
> > >I have been investigating securing MPLS for a Large Bank.
> > >I  have looked at DMVPN and IPSEC as options but both have
> > problems. Is
> > >there any good recommendations from any other Banks which
> > have secured
> > >MPLS over a public infrastructure.
> > >
> > >Kind Regards,
> > >Andy Brauer
> > >Business Connexion Networks (Pty) Ltd
> > >
> > >Office: +27 (0)11 266 1174
> > >Mobile: +27 (0)82 453 8992
> > >Fax: +27 (0)11 266 1001
> > >Email: Andy.Brauer@bcx.co.za
> > >Web Site: www.bcx.co.za
> > >
> > >NOTICES:
> > >1. This message and any attachments are confidential and intended
> > >solely
> > >for the addressee. If you have received this message in
> > error, please
> > >notify the sender at Business Connexion (Pty) Ltd immediately. Any
> > >unauthorised use, alteration or dissemination is prohibited.
> > >
> > >2. Business Connexion (Pty) Ltd accepts no liability
> > whatsoever for any
> > >loss whether it be direct, indirect or consequential, arising from
> > >information made available and actions resulting there from.
> > >
> > >3. Please note that Business Connexion only binds itself by way of
> > >signed
> > >agreements. 'Signed' refers to a hand-written signature,
> > excluding any
> > >signature appended by 'electronic communication' as defined in the
> > >Electronic Communications and Transactions Act, no. 25 of 2002.
> > >
> > >4. Directors: P.A. Watt, A.C. Farthing, M.W. Schoeman, B.
> > Mophatlane,
> > >I.
> > >Mophatlane, B. Sithole.
> >
> > Roger Clark Williams
> > Network Consulting Engineer
> > Global OSS/NMS Practice
> > Cisco Systems, Inc.
> > phone: 802.221.1104
> > cell: 802.355.9933
> > email: rogwilli@cisco.com
> > http://wwwin.tools.cisco.com/sales/go/ossservi> ces
> >
> > -------
> >
> > The MPLS-OPS Mailing List
> >
> > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> >

Roger Clark Williams
Network Consulting Engineer
Global OSS/NMS Practice
Cisco Systems, Inc.
phone: 802.221.1104
cell: 802.355.9933
email: rogwilli@cisco.com
http://wwwin.tools.cisco.com/sales/go/ossservices 

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

----------------------------------------------------------------------------
This communication is intended for the use of the recipient to which it is
addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take action
relying on it. Any communication received in error, or subsequent reply,
should be deleted or destroyed.

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