Peering Policy
Founded
in October 1994. Bouygues Telecom is a French ISP and Operator that operates a
network in France and Europe with more than 25 core POPs and several hundred
access POPs.
Bouygues
Telecom has a selective peering policy. The Peers are selected based on, the
amount of traffic exchanged with Bouygues Telecom ASN 5410, capability and
mutual benefit for both networks.
For
peering requests, please contact peering@as5410.net
General
technical requirements for peering with Bouygues Telecom
- The peer must be registered in a public
Internet Routing Registry (IRR) database.
- Record
completed in PeeringDB.
- A peer
of AS5410 must have publicly routable ASN.
- The BGP session must be established in IPv4
and IPv6.
- A peer
should have a 24x7 NOC with BGP expertise.
Traffic
Requirements for public peering
- Bouygues
Telecom are not present on public exchange server router. Any exchange with
public IXP via Bouygues Telecom ASN should establish a direct BGP session.
- For
partner with traffic < 40 Gbps, Bouygues Telecom invites you to contact us to
establish a direct BGP session on the French public exchange.
- For
partner with traffic < 40 Gbps, not present on a French public exchange, Bouygues
Telecom invites you to contact us to establish a direct BGP session on a
foreign public exchange.
- Bouygues Telecom doesn’t support backup
session over public exchange.
- Bouygues Telecom doesn’t support session
over public exchange if a direct private peering in service.
Traffic
Requirements for private peering
- For
partner with traffic > 40 Gbps, Bouygues Telecom
invites you to contact us to set up private peering connection agreement.
- Interconnection
must be 100 Gigabits Ethernet (100GbE LR4/FR1) or 400 Gigabits Ethernet (400GbE
FR4/LR4).
- Partner must enable IPv6 and IPv6 traffic percentage
should be > 40%.
- Partner should communicate following KPI according to downstream traffic's peak of the month, on a monthly basis:
-
ABR (Average Bit Rate) per session, per service, per
network (fixed/cellular).
-
Split of end-user’s terminals used (smartphone, tablet, PC, TV) in
proportion of the number of sessions.
-
Class of internet traffic (e.g., streaming video is one class of
traffic, file download and email are others) in proportion of traffic.
-
Forecast of year N and N+1.
-
Routing strategy between PNI, CDN, Transit in
proportion of traffic.
Traffic
Requirements for Locally hosted Cache
- Under
certain conditions and after impact assessment, Bouygues Telecom gives you the
possibilities to deploy caching servers on its network.
Routing Policy
- Peering
sessions with Bouygues Telecom ASN 5410 will advertise all Bouygues Telecom’s
routes.
- The
candidate shall not send unsolicited traffic to Bouygues Telecom’s ASN.
Technical constraint
-
For security reason there is rate limitation on ICMP protocol over all
our peering routers which has no impact on services. It is a global
configuration and there is no exception. Please avoid running continuous pings.
-
Bouygues Telecom announce prefix no longer than /24 in IPv4 and /48 in
IPv6.
-
Session via GIX will be removed if it stays unestablished for more than
3 months.