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 use of IRR Peering Policy Clauses

Excerpts from Peering Polices

Use of the Internet Routing Registry (IRR) is strongly encouraged for prompt prefix filter updates. Networks that do not provide a Routing Registry object to use for filter generation may have all routes filtered based upon some arbitrary criteria, such as mask length, or number of prefixes announced. – Speakeasy

Speakeasy maintains the right to add an entry describing any peering interconnect into the Internet Routing Registry system for the purpose of easing BGP filter generation. – Speakeasy

Routes must be registered with a recognised route registry: ARIN, RIPE or APNIC. – ATDN

Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering. Both parties shall make good faith efforts to keep this information up to date. – nLayer

All peers are expected to utilize IRR resources.  All peers will be configured with loose prefix limits based upon  registered/announced routes to guard against leaks. Peers  are encouraged to register routes or send notice in advance   of dramatic deltas in announcements to allow for adjustments to those limits. -- RCN

# Peers should register and maintain proper route objects in the RADB or mirrored IRR. – Mzima

Routes must be registered with a recognized route registry: ARIN, RIPE or APNIC. – LambdaNet

Use of the Internet Routing Registry is encouraged. OpenAccess reserves the right to make entries into the IRR on behalf of the peer if needed. – OpenAccess

Each Peer will maintain accurate prefix and routing information in a publicly accessible Internet Routing Registry (IRR). – Highwinds

Must utilize RADB or mirrored IRR resources and shall be configured with max prefix limits, allowing 25% headroom, based upon registered/announced routes – Charter

Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering.  Both parties should make good faith efforts to keep this information up to date. – WVFiber