[e2e] How can the VPN service level agreement be enforced crossing ASs?

Ping Pan pingpan at juniper.net
Thu Apr 5 19:20:05 PDT 2001


We had described a new signaling going over multiple AS's using
reservation aggregation. Here is the WEB pointer (we also had an expired
draft there too.)


Setting up tunnels between two neighboring AS's is not too difficult.
The problem is to set up tunnels over several transit AS's, where you
need to control signaling overhead, states (N**2 problem, has anyone
seen the latest AS growth chart? ;-)) and security (that is, you need to
be able to block transit guys to sniff the end user information.) That's
why you need to have aggregation.

RFC2547 is also a good way to take care this....

BTW, what's "intelligent optimzed routing" at private NAP's? Route

2 cents.

- Ping

Yingfei Dong wrote:
> The service guarantee in a single domain is not too difficult to achieve.
> However, if a src and a des of a VPN pipe are in two different ASs, how
> the VPN is implemented? We can buy bandwidth guarantee from two
> ISPs, but how to connect the two separarted pipe as a whole VPN pipe at
> the edge of ASs?
> The whole VPN pipe either crosses a NAP or goes through a private peering
> link between the two ASs. If it crosses a NAP, there is no control for the
> VPN pipe at the NAP. If it crosses a private peering link, are there some
> service agreements (e.g., bandwidth provision) on the private peering link
> between two ISPs?  (Most likely, the agreement is only about reachibility
> through BGP policies.) If no service provision on the peering link, the
> SLA of the VPN pipe is broken at the link.
> So, it is not clear how the SLA of a crossing-domian VPN is achieved
> Could anyone point out some references about this?
> One possible example I know is InterNAP, but they don't give any details
> about their implementation.
> InterNAP sets up service agreements with ISPs and builds their own Private
> NAPs. They claim that using their Private NAPs (which run their
> intelligent optimzed routing algorithms) can direct the traffic to
> a proper AS to achieve certain service quality.
> How to implement the private NAPs is very interesting.
> Looking forward to your comments or references. thanks a lot,
> yingfei
> ===================================================
> Yingfei Dong
> Ph.D student, U of Minnesota,
> 4-192 EECS Building,
> 200 Union Street, SE            Tel: 612-626-7526
> Minneapolis, MN 55455           FAX: 612-625-0572
> ===================================================

-- Ping Pan

More information about the end2end-interest mailing list