Beyond Peering LANs: Representing IXP Services in a World That No Longer Fits the Schema

For most of its history, the IXP directory model has been based on the assumption that an IXP is a peering LAN. A member connects to it using an ASN and a port and the directory describes this relationship. IXPDB, PeeringDB and the tools built on top of them all reflect this model. Recent work in the Connect Working Group has rightly advocated for better authoritative IRR data in the directory layer and the IXPDB IRR implementation is one outcome of this.

However, the operational reality at many IXPs is evolving faster than the schema. The recent SFMIX case study at Euro-IX Vienna demonstrated an IXP running a parallel opt-in service: a separate ASN, partial routes, hosted caches, VRF-leaking by BGP community and a distinct commercial model running alongside the traditional L2 fabric. SFMIX is far from alone; cloud on-ramps, multi-site fabrics and remote-peering arrangements are all stretching the directory model in similar ways. A consumer asking „who can I peer with at IXP X?“ increasingly receives an incomplete picture.

This talk will examine the current state of the directory layer in this environment. Drawing on the IXPDB IRR work and ongoing discussions with PeeringDB, I will outline where the current schema breaks down (multi-ASN service offerings, opt-in services, service tiers, non-LAN peering at an IXP location), what concrete extensions have been prototyped or proposed and where the design choices have real consequences for downstream consumers (route server operators, member networks, automation pipelines and the BCOP work itself). The intent is to leave the Working Group with a working list of ideas that could be implemented by the directories, IXPs and with the help of the Working Group itself.