This eighth Peering BOF brings together the Peering Coordinator Community to discuss peering challenges in 2005. We will start out with a few agenda items to highlight and spur discussion on some of the key interconnection issues of 2005. We finish up with .Peering Personals., a chance for Peering Coordinators to introduce themselves and their network to the group and hopefully facilitate getting peering sessions set up. Our agenda will be:

9:00-9:15: State of the Peering Internet
We polled the Peering Coordinator Community for a list of some of the top peering issues in 2005:

1. Peering vs. Transit - does peering make sense in 2005 given the prices of transit?
2. Capacity Planning - what is the growth path for peering? For example, trunking multiple gigEs or a single 10GE public peering port, or migrating larger peers to private gigE(s), etc.?
3. Traffic Analysis - do we have the tools yet to efficiently utilize the capacity we have?
4. Comcast still doesn't peer - the largest broadband networks still remains averse to peering
5. De-peering - is it declining?
6. Remote Peering - peering across oceans without a local presence has become more popular, but is it a reasonable strategy for the locals?
7. VOIP Peering is it hype or something we should prepare for?

Introducing the Remote Peering Concept and explaining why it is a bad idea is Stephen Wilcox (AS6320, Telecomplete).

Defending Remote Peering is ... TBD.

Following debate rules as we did last time, the audience will vote for the debater who made the more compelling case.

9:45-10:00: PeeringDB.com
Richard Steenbergen has taken on the community support task of running a web site for contact information for the Peering Coordinator community. He will describe and demonstrate PeeringDB.com.

10:00-10:30PM: Peering Personals
We finish up this Peering BOF by facilitating the introduction of Peering Coordinators to other Peering Coordinators using "Peering Personals."

How does this work? We solicit Peering Coordinators (before the meeting), asking them to characterize their networks and peering policies in general ways ("content heavy" or "access (eyeball) -heavy," "Multiple Points Required" or "Will Peer anywhere," "Peering with Content OK," etc.). From the answers we will select a set of ISP Peering Coordinators to present a 2-3 minute description of their network, what they look for in a peer, etc., allowing the audience to put a face with the name of the ISP. At the end of the Peering BOF, Peering Coordinators will have time to speak with Peering Coordinators of ISPs they seek to interconnect with. The expectation is that these interactions will lead to the Peering Negotiations stage, the first step towards a more fully meshed and therefore resilient Internet.

If you are a Peering Coordinator and wish to participate in this BOF, please fill out the following form and e-mail it to wbn@equinix.com with Subject: Peering BOF VIII.

Name:
Title:
Company:
AS#:

Check each that applies:
___ We are an ISP (sell access to the Internet)
    --OR--
___ We are a Non-ISP (content company, etc.)
___ We are Content-Heavy
    --OR--
___ We are Access-Heavy
___ Peering with Content Players or Content Heavy ISPs is OK by us
___ We generally require peering in multiple locations
___ We will peer with anyone in any single location
___ We have huge volumes of traffic (lots of users and/or lots of content)
	(huge: > 1 Gbps total outbound traffic to peers and transit providers)
___ We have a global network
___ We require Contracts for Peering
Current Peering Locations: _______________________
Planned (3-6 mos) Peering Locations: _______________________________

About the Presenters
As Co-Founder and Chief Technical Liaison at Equinix, William B. Norton focuses his attention on building strategic relationships among companies participating at the Internet Business Exchanges. Previously, he was the Chair of NANOG and Manager of the Internet Engineering Group at Merit, leading a variety of national and international network research and operations projects.

Richard Steenbergen is the Co-Founder of nLayer Communications, where he currently serves as Chief Technical Officer and devotes a significant amount of time to managing peering relationships. Previously, he served as a Sr. Network Engineer for several large NSPs, and was the Sr. Software Engineer responsible for developing optimized routing technologies at netVmg, Inc.

Stephen Wilcox is a Director for Telecomplete and LINX and has previously occupied senior positions at several Internet providers and exchanges. He is a participant in numerous Internet groups and forums and is also involved in various research projects.