to some extent, that would be a -very- nosy ixp. exchange operators often try to limit their liability by staying out of the relationships between peering partners that use the exchange fabric. simply managing the "common areas" has been considered enough of a task for the ixp. (common areas; e.g. the switch-fabric, possibly cross-connects, fabric support infrastructure etc.)
hello to all
i was wondering if there were some published docs online regarding the registration of route objects and membership at an ix - specifically, do ixp's around the world require that their members register all of their route objects prior to being allowed to exchange traffic at the ix? if so, how do you/they monitor this? is it left up to the other providers at the ix to verify that they are peering with someone who registers their objects? is this something that an ix could/should worry about? i know that many providers around the world are increasingly requiring registration, and that many build their filters from these registrations, but i have been unable to find anything wrt internet exchanges.
replies on or off, i will summarize
thanks
/joshua
"Walk with me through the Universe, And along the way see how all of us are Connected. Feast the eyes of your Soul, On the Love that abounds. In all places at once, seemingly endless, Like your own existence." - Stephen Hawking -