O2 Broadband Peering Policy
This policy specifies the criteria with which any potential peer must agree to before a connection request can be commenced. These criteria will be published by Telefónica within the public domain.
A decision on a new PNI will not be made by Telefónica solely on the criteria below. The information returned by a potential peer will be used to filter out non-compliant peers in order to move forward or cease the connection process in its initial stages.
In summary, this policy will be used to facilitate the gating process in the initial stages of any given PNI connection request.
A third party autonomous system will agree to a total minimum busy hour traffic exchange with O2 (ASN 35228).
A third party autonomous system will have a 24x7x365 networks operations centre or "NOC" that proactively monitors all peering connections and provides an escalation path to quickly identify and resolve network problems.
Each party shall respond within a reasonable amount of time to unsolicited bulk email, hacking, "denial of service" and other network security and abuse issues. Each party shall use reasonable endeavours to provide a qualified network engineer to trace ongoing network attacks within a reasonable amount of time.
A third party autonomous system must agree to repair or otherwise remedy any problems within a reasonable amount of time.
Each party shall use all reasonable endeavours to provide advance written notice of any planned maintenance and notice of any unplanned outages affecting any interconnection as soon as possible after the occurrence of such outages.
Routing / interconnect criteria
The parties shall, prior to connection, agree a preferred routing policy defining how traffic will be routed between each autonomous system.
A third party autonomous system must use MD5 passwords to secure BGP sessions where possible. Should MD5 passwords not be supported by a third party, details should be provided to Telefónica with any peering request.
A third party autonomous system must only send traffic that is destined for the IP prefixes announced by AS 35228. The third party autonomous system must not point default route or use static routes to send Telefónica traffic that does not match the routes announced by AS 35228.
A third party autonomous system must not sell or give AS 35228 next-hop to any other third party (i.e. peer must not re-advertise AS 35228 received prefixes to any other peer).
All private network interconnects must, where achievable, be provided as a resilient pair with each one of the pair being delivered at a diverse Telefónica internet demarcation point and different sites.
Where possible all third party autonomous systems must have a backup peering connection via a mutual exchange point, and this connection must be established via a direct BGP session and not a route server connection.
All peering requests shall be sent by email to [email protected]
A third party autonomous system which complies with all the criteria set out in this policy does not guarantee acceptance by Telefónica of any peering request. Telefónica reserves the right to, in its sole discretion, reject a peering request for any reason or no reason at all.
Telefónica reserves the right at any time and with immediate effect to cancel or suspend peering for a period of time, including where it determines in its sole discretion that any form of network abuse has occurred via the peering interconnect or for peers who no longer meet the criteria set out in this policy.
Telefónica shall be entitled to vary, replace or withdraw this policy from time to time, including as market and traffic conditions affecting network interconnections change. Any such variation shall be binding upon the peer with effect from the date on which the Telefónica communicates the relevant variation, replacement or withdrawal to the peer.