[6bone] Exchange Point Addresses
Pekka Savola
pekkas@netcore.fi
Mon, 17 Jun 2002 23:18:35 +0300 (EEST)
Pim, ww,
Please note that IX allocation is not meant to be "globally routable". If
you accept that, you can get IXP allocation, at least in RIPE region.
Many IX's don't really need that (they only want addresses for e.g. switch
fabrics or p-t-p addresses, not for services).
IX, depending on how you build it, could have any kind of addressing you
want. You could do private peerings and use addresses from either party.
But that is very bothersome if the technique is based on broadcast medium,
like Gigabit Ethernet.
On Mon, 17 Jun 2002, Pim van Pelt wrote:
> On Mon, Jun 17, 2002 at 12:45:59PM -0400, ww@GROOVY.NET wrote:
> | Hi,
> |
> | At the Toronto Internet Exchange (TORIX) we've been talking about
> | making it possible to peer natively over IPv6. The problem is
> | getting addresses for the exchange -- RIPE seems to have a clear
> | policy (they'll hand out a /64), but ARIN doesn't appear to. It
> | would not be appropriate to use addresses from one of the providers
> | at the exchange since TORIX has been, since its inception,
> | provider neutral and we'd like to keep it that way.
> They give out a (non-aggregatable) /48, which is IMO almost 100%
> pointless (not a /64 like you mentioned).
>
> | Any suggestions or pointers to how to go about acquiring some
> | numbers for the exchange would be appreciated.
>
> As with your collegues at AMS-IX (NL), you will simply be left out in
> the cold. When you approach a registry with a remark like you just
> made, you will be told that you are no more special than any other
> company that wishes to have their own globally routable space (call it
> PI, call it TLA).
>
> At current, at least in the region I am active in (RIPE), IXPs cannot
> obtain address space without becoming dependant on a member. By the
> way, neither can the RIR itself.
>
> groet,
> Pim
>
>
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords