The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Sep> msg00362



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

AW: ISPs offering VPN service

  • From: Curtis Villamizar <curtis@workhorse.fictitious.org>
  • Date: Tue, 26 Sep 2000 11:49:43 -0400
  • cc: "'curtis@avici.com'" <curtis@avici.com>, "'mpls@uu.net'" <mpls@UU.NET>, "'nbvpn@bbo.com'" <nbvpn@bbo.com>


In message <DB74A4E69C7CD311B740006008136E078D349B@MCHH213E>, Hummel Heinrich w
rites:
> 
> 2) Establishing a VPN by a network administrator completely from his desk. 
>    Juha's "soft-LSP" scenario   should even be extended to a "3rd-party LSP s
> etup" scenario. 

Use IPSEC and don't bother your provider at all.

> 3) Routing between different (and not allied) VPNs while utilizing the instal
> led source- and destination-VPNs:

Use IPSEC and don't worry about who in the VPN uses which provider.

> What do you think?
>    
> Heinrich

You want to use IPSEC for the above.

Some providers don't want to hear that because it means no added
revenue for maintaining the VPN but a while back they didn't want to
hear about IP because they couldn't charge per connection or per byte.

If you want a single provider VPN where the customer has to have no
involvement in the management just pays someone (and relies on their
security), then use RFC2547.

Curtis