 |
 |
| This document
shall serve as a guideline for ISP seeking peering
agreement with Telefonica International Wholesale
Services. All questions regarding this document,
or request for peering, should be directed to peering@wholesale.telefonica.com |
| Telefonica
International Wholesale Peering Guidelines - Public & Private |
| Operations
Requirements |
| Both parties shall
maintain a fully staffed Network Operations Center
that operates 24 hours a day, 7 days a week. |
| 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. |
| 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. |
| Both parties shall
provide access to a route server, looking glass,
or similar service for the purposes of routing audits,
diagnostics, and troubleshooting. |
| Technical
Requirements |
| Both parties shall
maintain sufficient backbone and interconnection
capacity to support the traffic being exchanged.
Both parties shall work quickly to establish additional
capacity to accommodate traffic growth. |
| 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. |
| 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. |
| 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. |
| 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-hop to a third party.
These activities are considered theft of service,
and will be prosecuted to the fullest extent of
the law. |
| Neither party shall
announce to the other a more specific route of a
prefix heard from a third party transit customer. |
| Traffic
Requirements |
| Minimum traffic exchange of 6 Gbps. Public peerings are not established, only private sessions if requirements are fulfilled. |
| Consistent routes
announcements |
| The partner will
have to operate a fully redundant network capable
of supporting node failures without hampering significantly
the performance of the traffic exchange with the
other backbone.At least two connection in each region (Europe and USA)
are required, and each connection shall carry less than 50%
of total traffic in order to be fully redundant. |
| Telefonica
International Wholesale Services - IPv4 Peering Points |
ASN |
12956 |
AS-SET |
AS-TDATANET |
#pref. |
aprox.5000
|
| London-Telehouse East/Telehouse North |
|
| Paris-Interxion |
|
| PAIX Palo Alto |
|
| EQUINIX Dallas |
|
| EQUINIX Ashburn |
|
| New York 60 Hudson |
|
| Telefonica
International Wholesale Services - IPv6 Exchange
Point Peering Information |
ASN |
12956 |
| Exchange |
Primary IP |
| AMSIX |
2001:7F8:1::A501:2956:1 |
| LINX |
2001:7F8:4::329C:1 |
|
|
|
|
|
|
