A Study of 28 Peering Policies
The following are snippets of Peering Policy Clauses found in the Peering Rules of the Road - A Study of 28 Peering Policies study. Clauses were categorized and put into rough categories for comparison.
The following are snippets of Peering Policy Clauses found in the Peering Rules of the Road - A Study of 28 Peering Policies study. Clauses were categorized and put into rough categories for comparison.
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
Mr Norton is Founder of DrPeering, an Internet Peering portal and consultancy, with over twenty years of Internet experience.
From 1998-2008, Mr. Norton’s title was Co-Founder and Chief Technical Liaison for Equinix. From the beginning, Mr. Norton focused on building a critical mass of carriers, ISPs and Content Providers. To this end, he created the white paper process, identifying interesting and important Internet peering operations topics, and documenting what he learned from the peering folks. He published and presented his research white papers in a variety of international operations and research forums. These activities helped establish the relationships necessary to atract the set of Tier 1 ISPs, Tier 2 ISPs, Cable Companies, and Content Providers necessary for a healthy Internet Exchange Point ecosystem.