This document serves as a guideline for Networks seeking Settlement-Free Interconnection, also known as Peering, with Pocketinet Communications Corporation ("Pocketinet"). All questions regarding this document, or requests for Peering, should be directed to peering _at_ pocketinet.comn.

1. Operations Requirements

1.1 Both parties shall maintain a fully staffed Network Operations Center that operates and is reachable via phone and e-mail 24 hours a day, 7 days a week.

1.2 Both parties shall provide an escalation path for resolving network issues in a timely fashion. Issues of a non-emergency technical nature should be responded to within 48 hours.

1.3 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.

1.4 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.

2. Technical Requirements

2.1 Both parties shall maintain a redundant backbone network with sufficient capacity to minimize queueing and ensure delivery of traffic both during normal and single-failure scenarios. Both parties shall act quickly and diligently to establish additional capacity to proactively accommodate traffic growth.

2.2 Both parties shall announce consistent routes across all interconnection points unless otherwise agreed to in writing.

2.3 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.

2.4 Peer shall utilize explicit prefix filters limiting the routes which they accept and in turn re-announce to Pocketinet.

2.5 Both parties shall announce only their own routes and the routes of their transit customers to the other party. No other routes are permitted, and may be filtered if detected.

2.6 Neither party shall abuse the peering relationship in any way. Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP. Neither party shall alter, sell, or give next-hops to a third party. Neither party shall use the other party's network for transit, or engage in any other routing manipulation that causes the other party's network to provide transit to peers. This would include, but is not limited to, establishing a tunnel between two different peering interconnection points, or announcing to the other the more specific routes of prefixes learned via a third party mutual transit customer.

3. Interconnection Requirements

3.1 Public Interconnection Requirements
3.1.a Both parties shall have sufficient capacity into the exchange switch to pass all traffic sent and received without queuing or loss. Both parties shall work proactively and diligently to establish additional capacity to accommodate traffic growth.

4. General Polcy

4.1 This policy may be updated from time to time, and Pocketinet reserves the right to modify, replace, or nullify this policy at any time.

4.2 Interconnection partner agrees to be bound at all times by Pocketinet's current Acceptable Use Policy, as of the Effective Date and all subsequent versions that may be modified from time to time, which is incorporated herein by this reference and is maintained at the following

4.3 Any interconnection may be temporarily suspended or disconnected at the sole discretion of either party.

4.4 Any interconnection may be terminated for any reason, with 30 days notice to the other party.