All:
This is a little bit CPS and a little bit routing policy, so sending it to the peering WG list for discussion. I think we've discussed in a few forums last year the effort to migrate the Microsoft non-research peering out of the main R&E routing instance and into the CPS VRF. As some of you may recall, Internet2 began accepting Microsoft-at-large routes back in 2002 to assist with the push of some critical Windows SP2 updates. This came in the form of a larger set of routes across what had traditionally been the Microsoft Research peering in Seattle via the Pacific Northwest Gigapop.
Now that we have a commodity service, it makes sense to get these routes out of the main R&E routing table and into the CPS VRF with the rest of our commodity peers. That'll get the traffic into the CPS overlay network and managed in line with commodity expectations. We've already brought up peering with Microsoft in the CPS VRF, so current CPS participants are getting these routes via both their main R&E peering and their CPS peerings.
What we'd like to propose is turning down the Microsoft routes in the main R&E instance. There's no reason to rush into this, so happy to iterate through some discussion on list or on the next NTAC call. Those folks that aren't taking commodity CPS feeds may feel the effect of the change.
As a data point, I've attached a graph of traffic to/from the Microsoft origin AS. It's not an insignificant amount of traffic, so getting this migrated to the VRFs would free up a bit of bandwidth on the R&E focused backbone links and leverage the geographically distributed peerings so the backhaul to Seattle is less necessary.
-Chris
<graph7effdaaae9c8fad7231f752cf3f73f22.png>Chris Robb, Internet2 Manager of Operations
O: 812.855.8604 C: 812.345.3188
****************
Winter 2010 ESCC/Internet2 Joint Techs
Hosted by the University of Utah - Salt Lake City, UT
January 31 - February 4, 2010
http://events.internet2.edu/2010/jt-slc/
