[address-policy-wg] delegate LIR portal access to specific user for specific resources - was: 2023-02 New Policy Proposal (Minimum Size for IPv4 Temporary Assignments)

Hi Elvis,


On 14/03/2023 08:42, Elvis Daniel Velea wrote:
> Hi Massimo,
> 
> thank you for your message. Let me see if I have an answer to some of 
> your questions/comments. See inline.

> 
>     -------
>     I also mention below a variation of this proposal, which could be it's
>     own proposal/thread (suggestions welcome):
> 
>     There should be an easy way to do "temporary assignments" (which may or
>     may not be the correct term in this case) to researchers/developers,
>     starting from address space of a company which is "sponsoring" the
>     research.
> 
> 
>     The key part of what I would like to have is the possibility to provide
>     somebody with access to LIR portal services but limited to a specific
>     subset of my resources.
> 
>     In general, a company is not going to support a research/experiment by
>     providing indiscriminate access to the LIR portal. Creating a new
>     LIR or
>     transferring prefixes is not a plausible solution in this context.
> 

> 
> An existing LIR can do an assignment to a researcher/developer as we 
> speak. All assignments an LIR makes are ‘temporary’, some may last a day 
> and some may last 10 years…

Can you explain this better? I have been asking to several ncc contacts 
and there was no suitable solution for this at the moment.

Asking researchers/developers to create their own LIRs so that resources 
can be transferred is not a practical solution, but I'm not sure you are 
referring to this. Giving the researcher/developer access to the LIR 
portal/APIs for all the resources is also not a solution.


> 
> If you want the researcher to have access to services like RPKI, they 
> can ask their LIR. In some cases, maybe temporary transfers could also 
> be of use.

Again, I don't see a way to do this at the moment.

> 
> Note that this proposal aims to update the temporary assignment proposal 
> that is currently in place. The RIPE NCC makes these temporary 
> assignments from a pool of IPs they have reserved specifically for this 
> purpose.

I understand. This is why I said that this could be a different proposal 
(even if related by a similar purpose). I changed the email subject to 
avoid confusion.

> 
> 
>     Also, I believe this would remove the need for an approval procedure
>     from the RIPE NCC side: (1) if the address space used is of a company,
>     there is less need to validate the research project motivations; and
>     (2)
>     the company "sponsoring" is also the one responsible for the address
>     space.
> 
> 
> I am not sure I understand what you mean by this. The NCC does not need 
> to approve any assignments made by LIRs. The NCC will need to approve 
> temporary assignments if the request is sent by an LIR (for an end-user) 
> based on the current temporary assignment policy.

That's exactly what I'm saying. Assignments done by LIRs of their own 
resources do not require approval, while they would satisfy the research 
use case (in summary: using prefixes from the ncc stash is not needed in 
all cases).


Thanks for your answers.

Ciao,
Massimo