The following are snippets of Peering Policy Clauses found in the Peering Rules of the Road - A Brief Study of Peering Policies study.  Clauses were categorized and put into rough categories for comparison.

Here are the clauses we categorized as requirements for Notifications and Interactions between peers.

Excerpts from Peering Polices

Notification/Interaction Requirements

2.8. Each Network shall be responsible for communicating with its customers with respect to its Internet Network and the services, including Internet connectivity, each provides to its respective customers. – AboveNet

2.9 Interconnection Candidate must provide 48 hours notice to AboveNet NOC for scheduled maintenance. Said maintenance windows to be between 02:00hrs and 05:00hrs of local time. -- AboveNet

2.10 Joint quarterly capacity planning reviews for interconnection augmentation to accommodate traffic growth and minimize the possibility of latency or packet loss between both networks. – AboveNet

2.11 Peers who are unable to maintain the minimums listed in sections 1 & 2 will be given 30 days written notice to remedy the situation. – AboveNet

The applicant must provide AOL with a readable hard or soft copy network map. This map must show network topology details and active IP capacity between backbone nodes. – ATDN

Both parties shall make every reasonable effort to provide advance notice of any planned maintenance, and immediate notice of any unplanned outages, affecting any interconnection. – InterNAP

A good faith effort should be made to facilitate communication regarding network maintenance that will affect traffic exchange. – NAC

All peers are expected

  to communicate contact updates in a timely manner.  All peers  are expected to proactively send updates regarding maintenance  activities, outages, and other significant activities. All  peers will be notified likewise by RCN. – RCN

# Both parties shall provide advance notice of any planned maintenance, and immediate notice of any unplanned outages, affecting any interconnection. – wbsconnect

Upon request Peer shall provide LambdaNet with a readable hard or soft copy network map. This map shall show network topology details and active IP capacity between backbone nodes. – LambdaNet

Any outage or impairment to peering session which is identified by the remote network operator is to be reported to the HWNG NOC as soon as it is identified. – Highwinds

A good faith effort should be made to communicate information regarding network maintenance that will affect traffic exchange. – OpenAccess

Must register routes or send advance notice of dramatic changes in announcements – Charter

Potential peer must notify Cablevision in advance of any peering or technical contact changes. – CableVision

Potential peer must be willing to supply network information upon request. – Cablevision

Interconnection Candidate must provide 48 hours notice to Qwest NOC for scheduled maintenance. – Qwest

Interconnection Candidate must provide trouble reporting and escalation procedures to Qwest. Qwest must have the ability to open tickets with Interconnection Candidate. – Qwest

Both parties should make a good faith effort to facilitate communication regarding network maintenance that will affect traffic exchange. – WVFiber