Peering Policy & Requirements

If you want to peer with me, you're welcome! My peering policy is generally open, but I do have a few expectations to ensure a smooth and secure connection:

• Technical contact information must be kept up-to-date.
• Strict route filtering must be enforced to prevent accidental route leaks.
• We should collaborate in troubleshooting peering issues, actively mitigating DDoS attacks, and resolving security incidents.
• Please do not abuse the peering link by pointing default routes or unnecessarily resetting next-hops.

How to Request Peering

If you're interested in peering, just send an email with the following details about your network to get started:

• A short introduction to your network (just so I know who I'm connecting with!)
• Desired peering points (e.g., IPv6-in-IPv4 tunnel, GRE, or LocIX)
• Your Autonomous System Number (ASN)
• Your AS-SET (if you have one)
• The recommended maximum prefix limit I should configure for you
• Your contact details

You can send your peering requests directly to peering@hofstede.it.

Routing Security

• RPKI: Valid or Undefined. Valid IRR entries are the bare minimum.

Prefixes

I only do IPv6, as it's the modern internet standard.

• 2a06:9801:1c::/48 IPv6 Only

Upstream

• AS34927
• AS20473
• AS212895
• AS34872
• AS209533
• AS41051

Internet Exchange Points

• LocIX Düsseldorf
• FogIXP

I currently maintain over 100 peering sessions across these exchanges.

More Information