On Wed, 16 Aug 2000, Herbert Baerten wrote:
- have to start up its own LIR (which includes getting a /20 allocation),
And some additional money, of course ...
- have to request a /20 or larger assignment from an existing LIR, in order to get an 'announcable' prefix, right (i.e. one that will not be filtered out anywhere)?
Well, not the "assignment", becuase the assignment can't have subassignments. A rather better approach is to try to plan address space assignment within the current allocation smarter. Say, if xx.foo was allocated 172.16/16 in the past and it wants to start its business in the country YY, then they may "reserve" a small /20 within that allocation (say 172.16.240/20) and start assigning addresses to YY customers from that /20, while using the rest of the /16 for XX customers. From AS Y they will announce 172.16.240/20 and everything will be fine. Of course, everything would be much more elegant if RIPE NCC finally implemented the additional SUB-ALLOCATED PA/PI status attribute, that was proposed by James Aldridge long ago, adopted by the LIR working group and passed to the DB WG for implementation. With such a scheme the LIR xx.foo would simply make a sub-allocation of 172.16.240/20, register it normally in the RIPE Database, give it SUB-ALLOCATED PA status, so the whole picture would look more proper and clean. Regards, Beri -- ----- ___ Berislav Todorovic, Network Engineer ---- / / /____ ____ _/_ -- KPNQwest N.V. - IP NOC (formerly EUnet) --- /--- / // //___/ / --- Singel 540, 1017 AZ Amsterdam, NL -- /___ /___// //___ /_ ---- Phone: (+3120) 530-5457; Fax: (+3120) 622-4657 - --- Email: beri@EU.net; Mobile: (+31651) 333-641