Internet connectivity in any Cisco Security Cloud Operations (SCO) location carry traffic for services hosted out of that particular location only. This is true for peering as well as for transit. In other words there is no peering between Cisco SCO locations (data centers). As Cisco SCO rolls out peering in its other locations globally, separate sessions to the same peering partners will need to be set up for the different locations (using the same ASN on Cisco side). 

At this time, Cisco SCO has public peering established with LINX Juniper and Extreme networks for its London hosting facility. There are plans to have more locations connected to regional public peering networks going forward.  

Cisco SCO follows a selective peering policy at this point. Since we are at the initial stages of setting up our peering infrastructure, we will review each request before deciding to either move forward with the peering request or defer it for a later stage. The decision is purely based on capacity constraints and a slow but steady ramp up plan. Cisco SCO will also reach out to different organizations with request for peering from time to time. The following peering types are of interest to us at this point:

1. ISPs (regional and global)
2. Major content providers of Internet
3. CDNs.
4. Providers of miscellaneous services in the Internet (voice, video, telephony etc.) 
5. Business partners

Upon agreement for a new peering session with a new peering partner, CIsco SCO will set up the BGP sessions in its routers and will not exchange any prefixes initially. Once is session is known to be stable for 2 - 3 days, prefixes will be exchanged for routing actual traffic.  

MD5 password for sessions can be accommodated but not encouraged.
