Re: [lir-wg] IPv6 assignments to RIPE itself
- Date: Tue, 14 Jan 2003 14:06:35 +0100
Hi,
On Tue, Jan 14, 2003 at 01:04:42PM +0100, Jeroen Massar wrote:
> Example: SixXS (www.sixxs.net) has the IPng tunnelbroker which delegates
> /60's from 3ffe:8114:2000::/48. We used to register every /60 in the
> 6bone database.
<rant>
Which brings up an interesting problem. According to the official
guidelines, you're not supposed to assing anything that is not
an /64 or /48.
Of course this isn't helpful, as a home/DSL/tunnel user might want to
use *two* networks, or *three*, but will never use more than 16 - and
such a /60 is just perfect for them (I have considered doing the same
for our dialup DSL customers).
But the IETF in their infinite wisdom decided that this is not what
people will want, so you're supposed to give them a /48. Which, for
DSL and Tunnel usage, means "a sizeable chunk of the /32 that a LIR
holds".
</rant>
> But updating this every time an allocation is made and with
> the number of allocations isn't quite handy especially as the parameters
> enclosed in the inet6num could change a lot (eg endpoint changes).
Now that part could be automated. Especially with the sync updates, this
is fairly easy :-).
On the other hand, adding referral mechanism for the inet6num: hierarchy
would certainly be less strain to the RIPE DB. It's there for the domain:
tree, so it shouldn't be too hard.
Item for the working group (LIR or DB)?
Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 55593 (55180)
SpaceNet AG Mail: netmaster@localhost
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
80807 Muenchen Fax : +49-89-32356-299
