Contracts (Usually) Commercial Relationship Bilateral or Multilateral Bilateral via Private Network Interconnect (PNI) IP Transit via Internet Exchange Point Paid Peering (Customer Routes)
Trident 2: 144,000 routes in 1 RU ◦ “Appropriate” is relative to your peers and their routes ▪ Global table: ~600,000 IPv4 prefixes ▪ Telx NYC route server: ~7500 IPv4 prefixes ▪ Netflix: 6 IPv4 prefixes (in NYC)
leak private ASNs in your AS path • • ◦ Many IXPs (mostly based on IXP Manager) require this • ◦ Most peers will accept only /24 and shorter for IPv4 and /48 for IPv6
◦ Set syslog warnings and read them • ◦ Not really different than transit, but no one upstream to filter for you ◦ Drop bogon prefixes ▪ RFC 1918 space ▪ Your own space ◦ Unrealistic AS-paths ▪ Consider filtering “tier 1” ISP ASNs from peers
Some common standards but in no way universal ◦ Real-time blackhole ◦ Selective drop of announcements ▪ Opt-out: “0:$ASN” ▪ Opt-in: “24115:24115” (sometimes needed when using opt-out)