Peering Policy

 

Work to Fix Things Clauses

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 to work to fix things

Categories:

  1. a.Unsolicted Bulk Email

  2. b.Security violations

b. Denial of service attacks/Hacking

c. Network abuse (including but not limited to spam issues)

d. Downed peering sessions, interfaces, or circuits

e. Disrupted, damaged, or flapping peering sessions

f. Similar/related infrastructure and security issues



Excerpts from Peering Polices

Work to fix Problems, Spam, DDOS, etc.

Each Internet Network must be responsive to unsolicited email and network abuse complaints, as well as routing and security issues, providing a knowledgeable technician within a two-hour period after notice. – Verizon

Both parties shall be responsive to unsolicited bulk email, hacking, Denial of Service, and other network security and abuse issues. A good faith effort should be made to provide a qualified network engineer to trace ongoing network attacks within a reasonable amount of time.

Both parties shall be responsive to unsolicited bulk email and Denial of Service attacks, as well as other network abuse complaints. – NAC

tw telecom peers must agree to assist in resolving security violations, denial of service attacks, and other abuse incidents originating within the peer network. Refusal to assist may result in de-peering. – TW Telecom

Both parties shall be responsive to unsolicited bulk email, hacking, Denial of Service, and other network security and abuse issues. A good faith effort should be made to provide a qualified network engineer to trace ongoing network attacks within a reasonable amount of time. – nLayer

Both parties shall make every reasonable effort to restrict the transmission of Denial of Service attacks and packets with forged source addresses from their network. – nLayer

All peers must agree to actively cooperate in resolving at   least the items in the following non-exhaustive list:  - security violations  - denial of service attacks  - network abuse (including but not limited to spam issues)  - downed peering sessions, interfaces, or circuits  - disrupted, damaged, or flapping peering sessions  - similar/related infrastructure and security issues – RCN

# Both parties shall make every reasonable effort to limit and control Denial of Service (DoS) attacks and forged packets from within their network. – wbsconnect

All peers must agree to assist in resolving security violations, denial of service attacks, and other abuse incidents originating within the peer's, or a customer of the peer's, network. -- DALnet

# Peers must be responsive to dealing with unsolicited email, denial of service attacks and other security concerns. – Mzima

Applicant must also agree to actively cooperate to resolve security incidents, denial of service attacks, and other operational problems. – Comcast

Applicant must maintain responsive abuse contacts for reporting and dealing with UCE (Unsolicited Commercial Email), technical contact information for capacity planning and provisioning and administrative contacts for all legal notices. – Comcast

#  Applicant must respond to all operational issues within 24 hours – tinet

Peer must cooperate in case of network abuse. On occurrence of Denial of Service attacks Peer shall implement filters on request. – LambdaNet

Peer must agree to actively cooperate to resolve security incidents, denial of service attacks, and other operational problems. – OpenAccess

Each Internet Network must be responsive to unsolicited e-mail and network abuse complaints, as well as routing and security issues, providing a knowledgeable technician within a two-hour period after notice. – Highwinds

Must agree to actively cooperate in resolving items in the following:

a. Security violations

b. Denial of service attacks

c. Network abuse (including but not limited to spam issues)

d. Downed peering sessions, interfaces, or circuits

e. Disrupted, damaged, or flapping peering sessions

f. Similar/related infrastructure and security issues – Charter

Both parties shall be responsive to unsolicited bulk email, hacking, Denial of Service, and other network security and abuse issues. A good faith effort should be made to provide a qualified engineer to trace ongoing network attacks within a reasonable amount of time. – WVFiber

Both parties shall make every reasonable effort to restrict the transmission of Denial of Service attacks and packets with forged source addresses from their network. – WVFiber

Peer must have a professionally managed 24x7 NOC. Peer must agree to repair or otherwise remedy any problems within a reasonable timeframe. Peer must also agree to actively cooperate to resolve security incidents, denial of service attacks, and other operational problems. – AT&T