[lir-wg] IPv6 assignments to RIPE itself
Ronald van der Pol Ronald.vanderPol at rvdp.org
Wed Jan 15 13:59:35 CET 2003
On Wed, Jan 15, 2003 at 12:37:24 +0100, leo vegoda wrote: > Hi Ronald, > > Ronald van der Pol <Ronald.vanderPol at rvdp.org> writes > >On Tue, Jan 14, 2003 at 10:12:27 +0100, Gert Doering wrote: > > > >> I tend to agree with you. The /42 has been sub-allocated from Surfnet > >> to the RIPE NCC (the NCC being "Just any Surfnet customer" here, not > >> acting in their function as RIR). > > > >But RIPE NCC as RIR did approve it according to 5.4.2 of ripe-246. > >How many hats does RIPE NCC have in this case :-) > > This is not the case. Each assignment has been made to a separate > organisation. There is a single assignment for the RIPE NCC. There is a > separate assignment for the RIPE meeting. RIPE is not the same as the > RIPE NCC. > > Similarly, assignments made to employees' home networks are to separate > End Users and not the RIPE NCC. > > Each assignment within the allocation is to a separate End Site. This all happened when I already left surfnet. So I don't know the details. But this sounds strange. Are you saying surfnet assigned /48s directly to RIPE NCC employees? I suppose surfnet dealt with one customer, RIPE NCC, and assigned several /48s to it. BTW, I agree RIPE* is special. I can understand the need for separate /48s for the RIPE NCC office and the RIPE meetings. However, I would expect RIPE NCC employees to get /64s from the RIPE NCC /48 or get a /48 from their home ISP. rvdp
[ lir-wg Archives ]