There's a thread on nanog-l at the moment about temporary internet assignments:
http://mailman.nanog.org/pipermail/nanog/2012-September/051655.html
I had already booked a slot in the AP-WG under AOB to talk about this because the policy is broken and needs fixing. Specifically, the timescales specified in the policy allow the assignment to be made one week before use: the consistent feedback is that this isn't enough time for large conference organisers to get things organised in time. The problems we're trying to address are: - enough time for debogonisation - enough time for pre-configuring equipment prior to shipment (which can be weeks in advance) - not knowing well in advance what address ranges you're going to get causes massive headaches, which is exactly what you don't need coming up to a frenzied configuration - conference attendees often arrive several days earlier than the conference formally starts, and they expect teh interwebs to work There are a couple of options for dealing with this: 1. specify new time limits (e.g. receive one month in advance, hand back one week after) 2. don't specify time limits but allow the IPRAs to have discretion on what seems sensible to them 3. keep the current time limits but ask the RIPE NCC whether it would be possible to implement a booking system. I.e. your assignment would only be active during the requested time period, but you would know well in advance what the options were. If anyone has opinions on which of these they prefer (or any other suggestions on how to deal with the issue), can you either post here or let me know off-list and I'll summarise at RIPE65 in advance of posting a policy amendment for ripe-526 shortly after the meeting? Nick