OPENTRANSIT
2008 PEERING POLICY
(Reviewed in Dec 2007)
This
Peering Policy describes the criteria that France Telecom –
OPENTRANSIT-INTERNET, has decided for acting in direct and public peering
relationships. This Peering Policy consists in establishing peering connections
between OPENTRANSIT-INTERNET and peer networks where such exchanges are
mutually equitable and are cost-effective. In addition to the criteria set
forth below, OPENTRANSIT-INTERNET’s ability to enter into peering agreement with
a particular carrier is subject to
availability of peering ports and to OPENTRANSIT-INTERNET backbone capacity in
particular locations.
I. Definitions.
Autonomous System. The
Autonomous System (AS) is the representative entity dealing with IP network
consistency we consider to exchange traffic over two peering partners.
Geographically dispersed. Any two connections between
OPENTRANSIT-INTERNET and a particular peering partner are geographically
dispersed if they are either (1) 250 miles apart or greater or (2) located in
different regions among the geographic.
Geographic regions.
Subdivision of the continent where OPENTRANSIT-INTERNET has nodes are
set forth in Attachment 1.
Local peering. A local peering refers to interconnections
contracted on a specific country with internet route from this country
only.
Mandatory points. In each region, some locations will be
mandatory cities. It means that some cities are seen as major required points
for peering relation. These mandatory points are 3 among these 6 cities in the
US : New-York, Ashburn, Palo Alto, LA, Dallas and Chicago, 3 among the 5
following cities in Europe: Paris, London, Frankfurt, Amsterdam, Madrid.
Private peering. Direct peering refers to an implementation of
dedicated bandwidth between the larger Network Service Providers (“NSPs”) to
reduce inefficiencies related to scaling interconnections between the large
Internet backbones. Traffic is exchanged on a bilateral basis via local BGP-4
peering sessions.
Public peering. Public peering refers to an implementation of
a BGP-4 peering session between NSPs through an exchange point (IX or NAP). The
interconnection supports for public peerings are not dedicated.
Peering. Where two interconnected networks exchange
traffic strictly between their own networks.
See Private Peering and Public Peering.
Regional peering. A regional peering refers to interconnections
taken with a peering partner over one of the major continent in the world.
Route announcement. The means by which two peering partners
notify each other of address information in order for the peering partners to
exchange Internet traffic.
Transit relation. Where one network uses another network to
provide all or most of its connectivity.
II. General Principles
A. All private peering connections shall be at
speeds of 155 megabits per second (“Mbps”) or higher.
B. A consistent worldwide peering shall
interconnect (in private or public) on geographically dispersed point in the
world over Europe and America (US). A global peering consists in several
peering locations both in Europe, and in the US. A global peering is contracted
on a worldwide basis over two Autonomous System only.
Whenever the peering partner has network
presence in multiple continents where OPENTRANSIT-INTERNET also has Points Of
Presence, it is mandatory to open peering legs in ALL possible continents. This
is to ensure that the peering interconnections benefit both partners equally by
making sure that traffic is exchanged optimally in the respective continents.
In case Hot Potato routing is in place and that a single AS is used on both
sides, this also allows to ensure that both parties carry the traffic on
symmetrical basis.
This
applies for any entity, regardless if a single AS number is used in the
multiple continents. In case different AS numbers are used on the partner side,
peering with OPENTRANSIT-INTERNET would be done in each continent with the
respective applicable AS number on the partner side.
For example, if a carrier
having presence both in Europe and in USA solicits peering with Opentransit,
peering has to be operated both in Europe and in USA (US alone or Europe alone
is not possible). If a carrier
has presence in US with AS#X, in Europe with AS#Y, then he must be ready to
peer with France Telecom AS5511 with 2 ASes in each respective continent.
C. Peering connections shall be
geographically dispersed. North America is seen as a region.
D. No OPENTRANSIT-INTERNET transit customer
shall be entitled to enter into a peering relationship with
OPENTRANSIT-INTERNET at the same time that such transit customer is maintaining
transit connections with OPENTRANSIT-INTERNET. OPENTRANSIT-INTERNET transit
customers that qualify for a peering relationship may continue their transit
connections on a graduated basis only until the transit customer’s peering
connections with OPENTRANSIT-INTERNET are operating and exchanging traffic.
E.
OPENTRANSIT-INTERNET
will reset all BGP communities on received routes.
F.
OPENTRANSIT-INTERNET may
reset all MED on received routes.
G.
Partner may implement
filtering (AS filtering, route filtering, max-prefix limit) but have to inform
OPENTRANSIT-INTERNET noc about such filtering and any modification on the
filters.
H.
Partner must have route
consistency on all peering points.
III. Infrastructure Requirements for Any
Peering Arrangement
Each peering
partner shall meet the following infrastructure requirements:
A. Each of the peering partner’s backbone hubs
shall be connected to at least two other hubs on its own backbone at mandatory
capacity (cf section E).
B. The peering partner shall operate a fully
staffed, twenty-four hour, seven-day-a-week (“24x7 “) Network Operations Center
(“NOC”).
C. The peering partner shall establish “trouble
ticket” and escalation procedures to resolve customer service issues.
D. OPENTRANSIT-INTERNET would not come
into peering relation with customer of existing peering partner.
E. For regional and worldwide peering, the
partner shall have a nationally-deployed, Internet backbone in the countries in
which he desires enable a peering relation. The peering partner’s shall operate
on dedicated IP circuits of at least OC-192 in the US and in Europe. Aggregated
traffic must not be lower than 4.0 Gb/s.
F. For local peering, the partner shall
interconnect on 2 cities not necessary dispersed and have at least 4.0 Gb/s
of aggregated traffic with OPENTRANSIT-INTERNET.
IV.
Routing Requirements
Each peering partner shall meet the
following requirements with respect to routing:
A. The
peering partner shall carry full Classless Internet Domain Routing (“CIDR”) at
edge routers using BGP-4 and aggregated routes;
B. The
peering partner shall register routes (routing policy) with the Internet
Routing Registry (IRR) or another OPENTRANSIT-INTERNET-recognized Internet routing registry (RIPE,…);
C. The
peering partner shall implement routes filtering at the partner’s network edge;
D. The
peering partner shall provide consistent routing announcements, i.e., the same
set of routes announced with the same autonomous system (“AS”) path length at
all peering locations;
E. The
peering partner shall not establish a route of last resort, i.e., default
route, directed at OPENTRANSIT-INTERNET;
F. The
peering partner shall announce only its own
customer routes to OPENTRANSIT-INTERNET, not any routes from any of its
other peers;
G.
All traffic exchanged
between OPENTRANSIT-INTERNET and its peering partners shall be carried over the
peering connections established between OPENTRANSIT-INTERNET and the peering
partner. The peering partner shall not forward route announcements of the
peering partner’s network via another provider.
H.
OPENTRANSIT-INTERNET
will announce only customer routes originating from the peering area (either
local, Regional or Worldwide).
V. Traffic and Capacity Requirements
A. General Requirements for All Peers
1. In order for OPENTRANSIT-INTERNET to consider
an application to peer with OPENTRANSIT-INTERNET, a potential peering partner
shall provide OPENTRANSIT-INTERNET with a readable hard copy of its network
within the region he whish to peer or a global copy if the request consists
into a global peering, including a list of existing peering connections;
2. Each operating peering connection with
OPENTRANSIT-INTERNET shall have a minimum 10Mb of bilateral traffic;
3. Traffic volumes are measured in either
direction, inbound or outbound, whichever is higher, on a weekly aggregated
average basis over all the points where the parties exchange traffic. Any
imbalance of traffic shall not exceed a ratio of up to 2,5:1 in either
direction;
4. When OPENTRANSIT-INTERNET cannot
measure a prospective peer’s traffic because there is no existing connection or
relationship between OPENTRANSIT-INTERNET and that prospective peer,
OPENTRANSIT-INTERNET reserves the right to enter into a public peering
relationship with that prospective peer prior to any direct peering
relationship. OPENTRANSIT-INTERNET may
then measure the prospective peer’s traffic to determine if the prospective
peer meets this Peering Policy’s volume criteria;
5.
All traffic must
ingress and egress through peering points.
6.
OPENTRANSIT-INTERNET
may shutdown any private or public peering without any notice if the link is
loaded more than 95 % during more than 2 hours.
B. Requirements Specific to Direct
Peers
1.
In case of peering
upgrade consideration, For each additional prospective peering connection to
existing locations, beyond those for which the direct peering partner
originally qualifies, the direct peering partner shall meet an average daily
traffic utilization of 65% for an individual existing connection (based on its
payload). (For example, a 155Mb connection would require about 96Mb average
daily .
2.
OPENTRANSIT-INTERNET
reserves the right to consider additional engineering factors to determine
whether a peer satisfies daily utilization requirements.
3.
France Telecom may
shutdown or alleviate peering if existing legs cannot stand 1 leg failure.
VI. Interconnection Method for Public
Peering and Direct Peering
A. General
After determining whether a potential peering
partner qualifies for peering with OPENTRANSIT-INTERNET, Interconnections and the type of peering – i.e. whether public or
direct – shall be determined according to practical economic considerations
that are sensible for both parties.
B. NDA
All applicants must sign a Non Disclosure
Agreement before discussing and establishing peering connections.
C. Public Peering Arrangements
1. Prospective public peering partners shall have
active connections to at least three geographically dispersed interconnection
points where and OPENTRANSIT-INTERNET is also connected.
See http://vision.opentransit.net/docs/peering_policy/ix-points.txt for list of Public peering
available.
2. OPENTRANSIT-INTERNET may change the number of
NAPs at which it peers, and, in the course of its peering relationships with
partners, may alter the NAPs at which it peers with partners. Neither OPENTRANSIT-INTERNET nor its peering
partners shall implement any changes to the number or location of the NAPs
without first providing the other party thirty (30) days’ prior notice.
D. Direct Peering Arrangements
1. Concurrent
with the establishment of direct peering connections with any peering partner,
OPENTRANSIT-INTERNET shall terminate any public peering exchanges with
that peering partner. No peering
partner may be simultaneously connected with OPENTRANSIT-INTERNET as both a
direct peer and a public peer.
2.
Neither party will
apply port, service or other charges.
3.
In the case of private peering
that necessitate the provisioning of a local loop (like an intra-building or a
metropolitan link), all costs associated to this link are to be supported by
the party having ordered it. The responsibility of supervision, maintenance and
troubleshooting is also incumbent on this party paying for this transmission
capacity.
VII. IPV-6 PEERING
IPV6 peering is now available on our network.
IPV6 and IPV4 are considered as a whole, thus any ipV4 peers
can apply for IPV6 peering too.
In order to encourage IPV6 emergence, Opentransit can setup
some specific ipv6 peers disregarding some critera of this peering policy.
VIII. Violations and Corrective Measures
A. Whether the criteria in this policy
are met may be reviewed weekly. In the event that any peering partner fails to
meet any of the criteria of this peering policy, OPENTRANSIT-INTERNET reserves
the right to seek remedies, which may include but shall not be limited to
charging the peering partner for all traffic that the peering partner sends over
the OPENTRANSIT-INTERNET network. OPENTRANSIT-INTERNET also reserves the right
to demand and receive full compensation from the peering partner
B. Each peer has to respect the Open
Transit Internet Acceptable Use Policy (AUP). This policy is designed to help
protect Open Transit Internet’s customers and the Internet community in
general. This policy is available following this link: http://www.opentransit.net/policy/AUP.html
C. Peering
agreement can be terminated with cause by either party with thirty days written
notice.
IX. Term
Peering agreements shall
have a one (1) year term and shall automatically renew un
less cancelled by either
party. Agreements may be terminated at
will by either party on thirty (30) days written notice.