BendTel Peering Policy

BendTel Peering (Settlement-Free Interconnection) Policy

Last Revised 7/30/2004

No peering applicant who is a BendTel transit customer shall be entitled
to enter a peering relationship with AS27008 at the same time such
transit customer is maintaining transit connections with AS27008 at any

Neither party will apply port, service, or other charges to the other party.

Applicants must maintain a fully staffed Network Operations Center (NOC),
which operates 24 hours a day, 7 days a week, 365 days a year.

Applicants must adhere to an industry standard trouble ticket process
including escalation points of contact for network related outages and
service-affecting issues.

Applicants must enforce an Acceptable Usage Policy and must be responsive to
network abuse complaints to include but not limited to: unsolicited e-mail,
security alerts, and all routing related issues.

Applicant and BendTel should exchange with each other prior to any
peering agreement a free shell or PPP account for testing and auditing
purposes related to routing. This will be used for confirmation of traffic
flows, troubleshooting of interconnection-related issues, and auditing

All network requirements must be met at the time the applicant submits the
request for peering to BendTel.

If traffic on any peering node exceeds 80 percent utilization for more than
three consecutive hours, it is the responsibility of the applicant to submit
a request to upgrade the peering circuit or BendTel reserves the right to
limit routes in order to preserve the stability of the circuit.

All peering connections will be at a minimum speed of 10Mbps, with a
preference for 45Mbps (T3) and greater speeds based on traffic engineering

Applicants are expected to register their routes, routing domains and policies
with an industry recognized Internet Routing Registry (IRR). BendTel maintains
an IRR which accepts submissions from peers and customers.

Neither BendTel nor applicants will advertise third party routes. If either
party detects third party routes, they will have the right to deny said routes.

The applicant shall not establish a route of last resort, i.e., default route,
directed at BendTel. The applicant shall not establish any routes directed at
BendTel which are not advertised by BendTel.

The applicant shall support Classless Internet Domain Routing (“CIDR”)
exchanged at edge routers using BGP-4. The routes shall be sufficiently
aggregated routes unless otherwise agreed upon by both parties.

The peering applicant will announce consistent routing announcements to
BendTel unless otherwise agreed upon by both parties. Consistent
announcements require that all routes be announced at all peering sites
with the same aggregation properties.