Michal Krsek writes:
Some IXPs are not only infrastructure for interconnection and they sometimes offer some public services. I cannot determine all of them, but in example: NTP, traffic statistics, root DNS servers and some other (hope people from LINX or NETNOD should find some others).
I think this was addressed in the discussion, with the solution to get normal IPv6 space from the usual sources for thoses services. For example the K root nameserver does not sit on the LINX exchange network itself, but in a very different netblock, and this model could be applied to IPv6, too. If an IXP insists on putting those services on the same net, they can of course do so if they get routable IPv6 space for it, through standard procedures. Use of those addresses for IXPs is in no way forced.
3. definition of an IXP -----------------------
Three or more ASes and thee or more separate entities attached to a LAN (a common layer 2 infrastructure) for the purpose of peering and more are welcome to join.
What is the goal of this definition? It is to restrict other subjects to use these addresses?
I'd pragmatically say the need came up for addresses for this usage, so it had to be defined somehow, in order not to create a source for arbitrary non-routable globally-unique IPv6 addresses.
If yes, there are also some transit ISPs POPs which fit your definition. We discussed definition of IXP on some forums, but we didn't get right definition. Definition is different on basis of your goal :-)
Well, it can be discussed endlessly what the "right" definition is. I wouldn't mind if some "transit ISPs POPs" fit this definition if people peer there (as opposed to just getting transit). So they next question will be what "peering" is, but please, no ...
Hm ... So IXP have to establish it's own LIR or borrow this service from it's members ? :-)
Yes, why not? It's not externally visible through which LIR the request was made. Robert