Summary

This document describes the peering policies for HOSTOWEB (AS37738 & AS205897).

Background

An Internet exchange point (IX or IXP) is the physical infrastructure through which Internet service providers (ISPs) and content delivery networks (CDNs) exchange Internet traffic between their networks.

Policy Statement

HOSTOWEB will peer with network operators at IXs for anyone. Our inclination is to setup multiple peering sessions for redundancy wherever and at whatever point conceivable. HOSTOWEB will also peer with route servers on all IXs where we are available.

Peering Requirements

• To be eligible for peering, each candidate must:
• Use a registered public autonomous system (AS) number;
• Publish valid contact information via PeeringDB
• Maintain valid AS and prefix records with a public Internet Routing Registry (IRR).
• A peer may only send toward us traffic intended for a destination network we advertise. The use of static or default routes toward us is not permitted.
• The following features not required but we can configure if you need:
• RFC 2385 — BGP MD5 authentication
• RFC 7999 — BLACKHOLE community
• RFC 8326 — Graceful BGP session shutdown

Peering with HOSTOWEB on Internet Exchanges

• No traffic volume required. But our peering policy is selective.
• BGP sessions should be established in IPv4 and IPv6 if available.

Peering with HOSTOWEB on Private Peering

• Our BGP peering policy is selective, but for PNI, we start with 10GB-LR or 100GB-LR4 interfaces.
• Traffic with the peer ASN should be at least around 1Gbps peak to start discussing about PNI.
• BGP sessions should be established in IPv4 and IPv6 if available
• HOSTOWEB provides IPv4 /31 and IPv6 /126 networks for the PNI

Maximum Prefixes

We suggest to set the following maximum-prefixes:

• IPv4 : 500 prefixes
• IPv6 : 500 prefixes