Hi Dave, thanks for your comments. On 15/12/2012 19:21, David Farmer wrote:
If we use the London 2012 Olympics as an extreme example, the events were scheduled from July 27th to August 12th or 17 days, and would seem to be allowed 47 days under the policy.
The official 2012 olympics budget was around £9.3 billion (€11.5b, $14.5b). I'm sure with that sort of budget, it would be possible to procure any quantity of addresses :-)
month for set up and testing. Maybe attendance in the range of 50 or 100 thousand could be used as a threshold between these larger scale event and more typical events or conferences that this policy change is intended to cover.
similarly, any massive-scale event like this will have a massive budget. This policy proposal isn't really aimed at that. It's aimed at solving a class of problems including smaller scale events, research and general temporary projects. It cannot and should not attempt to satisfy all requirements for temporary resource assignments for all time. "One size never fits all".
Could I also make a suggestion, that you allow for reservations on temporary resources to be made up to one year in advance.
In fact we discussed this at the last RIPE meeting in Amsterdam: https://ripe65.ripe.net/archives/steno/18/ Check out the transcript from about 1/2 way down the page. I think there are problems associated with a booking system model. My preference at this stage is to keep the policy and the implementation very simple; if it turns out that this doesn't work for people, we can revisit the issue in future. The purpose of this particular policy tweak is to fix a timing issue which makes the current temporary assignment policy difficult to implement in real life. Nick