[address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies

Hi Randy, 

I think that the time for the temp assignment to be made, stretched to 1 year or more, will become an issue for the NCC to work with. 
It is my personal view / feeling, that not many requests are done to the NCC for longer periods than specified in the policy.. And this looks like fixing policy for a corner case.

Not only of the point that Gert made, but also because it will make the life of the IPRA's must harder with the time that we add..
As we can also expect more requests to be made, if the policy would be changed ... 

As this is for research .. have you considered working with other research networks that hold large amount of numbers because they were NIR's before RIPE was setup ? 
Like Surf in The Netherlands for instance .. or Janet in the UK.. or alike ..

If they are presented with a proper documented research request .. they will consider those requests and they are not bound by policy restrictions that we are discussing here. 

It could fix your specific case .. and that is why these orgs are actually doing what they are doing ..  

Regards,
Erik Bais 


On 25/01/2022, 18:34, "address-policy-wg on behalf of Randy Bush" <address-policy-wg-bounces at ripe.net on behalf of randy at psg.com> wrote:

    ok, i did it again, tried to fit a square peg in a round hole.  while
    the immediate problem is past, thanks to the ncc reg folk, i fear that
    we could benefit from thinking a bit more about $subject.
    
    for a research experiment, we wanted eight or a dozen routable, i.e.
    /24, prefixes which we would announce from various places in the
    topology.  each /24 would have one pingable address, let's assume .42.
    
    because this is ops based research, we have to
      o go through the ncc bureaucrazy
      o actually deploy and test
      o run the measurements for a few months
      o do the analysis
      o possibly tune or vary the experiment
      o write the paper and submit it
      o wait three months for the accept/reject
      o if rejected, retune and submit to a different venue
      o the reviewers may ask for us to re-run to get fresh data for
        publication
      o whine whine
    this takes six to twelve months.
    
    if you are familiar with $subject, you will sense there are two problems
    here.  587 is designed for a much shorter time window, and it kind of
    assumes more that 1:256 utilisation.
    
    you can imagine that my request to registration services generated a bit
    of discussion :).  as our social environment has become less tolerant,
    reg services understandably wants simple rules they can follow and which
    clearly justify their actions.  and geeks such as i just want our mtv
    :).
    
    i suspect we may be able to wordsmith conditions to deal with the time
    length issue.  but i suspect that codification of guidelines covering
    the needs & justifications for research experiments, folk qualifying
    strange devices, and those doing other weird things will not be so easy.
    
    i am considering a policy proposal in this space; but want to learn what
    others see and think, and to see if it is worth the time and effort.
    
    and can we please keep discussion focused on temporary address space
    assignments?
    
    thanks.
    
    randy
    
    
    -- 
    
    To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/