AS8473 Peering Policy
Last updated: 2023-02-17.
AS8473 is the primary ASN of the Swedish ISP Bahnhof AB (english).
Bahnhof has a PeeringDB record which contains all relevant information, including NOC and abuse department contact information.
- These points are to be considered more as guidelines, rather than hard rules.
- Each peering request is handled case-by-case.
- Exceptions to this policy will be granted at the sole discretion of Bahnhof.
- This policy may at any time be modified at Bahnhofs discretion without any prior notice.
- All peering - whether public or private - shall be settlement-free. Any costs related to private interconnections shall be shared equally between Bahnhof and the peering partner.
- Contracts between parties is not a requirement but can be arranged if deemed necessary.
- Bahnhof may without any notice terminate the peering.
- A peering relationship shall not be established with current downstreams of either Bahnhof or existing peering partners.
- Bahnhof requires that the peering partner has an up-to-date PeeringDB record.
- If this is not possible the peering partner shall take responsibility for updating Bahnhof whenever relevant information changes.
- Peering partner shall have a 24/7 NOC.
- Both Bahnhof and the peering partner shall actively cooperate in resolving incidents, including but not exclusive to security and abuse.
- Bahnhof will not accept prefixes shorter than /8 (IPv4) and /16 (IPv6), or longer than /24 (IPv4) and /48 (IPv6).
- Bahnhof does not honour MED.
- Invalid RPKI prefixes will be dropped.
- MD5 is supported, but not required.
- Bahnhof will announce prefixes as received by downstreams.
- The peering partner shall register announced routes in the proper IRR database.
- The peering partner shall only announce its own and downstream routes towards Bahnhof. No routes learned from other peering or transit relationships shall be announced.
- No static routes shall be directed towards Bahnhof.
- Unless agreed otherwise Bahnhof will announce consistent routes at locations and expects peering partner to do the same.
Public peering on Internet Exchange Points
- Peering sessions shall be established on all common IXPs.
- If we already receive prefixes via a Route Server a direct peering session will only be considered if there is a substantial amount of traffic between the two networks.
- Private interconnection shall be not established with a capacity lower than 10Gbit/s.
- While not a requirement it is preferred to establish private interconnections at two or more common points of presence.