[address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?

Hi Tore,

I think my previus email just explained it.

The motivation is my personal view that we have a problem (as a community) by not bringing into the system the legacy resources.

I'm alone with that view? I don't know, and that's why I'm asking.

What is clear to me is that, according to existing policies, I share this view with 4/5 of the RIR communities.

What is the effect of that? Simple, an unbalance of transfers among regions, because if someone for whatever reason want to get resources and keep them non-legacy, can just come to RIPE for that. This is good for RIPE? I don't think so, we could keep growing the non-legacy resources, while other regions get "cleaned".

Regards,
Jordi
@jordipalet
 

El 15/7/19 10:05, "address-policy-wg en nombre de Tore Anderson" <address-policy-wg-bounces at ripe.net en nombre de tore at fud.no> escribió:

    * Gert Doering
    
    > On Sat, Jul 13, 2019 at 01:37:19PM +0200, JORDI PALET MARTINEZ via address-policy-wg wrote:
    >> I keep thinking that ripe-682 (RIPE resource transfer policies), should have a provision (as it is the case in all the other RIRs), in order to "convert" the legacy resources to non-legacy, when they got transferred.
    > 
    > What is it that you want to achieve with this?
    
    +1
    
    I've read this entire thread and I still have no idea what the motivation for this (pre-)proposal actually is. Is it a solution in search of a problem?
    
    Maybe if you could explain by example, Jordi?
    
    Were you involved in a transfer of legacy resources and stumbled across some kind of obstacle caused by current policies (that this proposal addresses)?
    
    Tore
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.