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

Hi Gert,

I know we aren't ARIN and I've used that only as an example of the results of that provision.

My personal view but looking for the good of the community is that it is better to get rid ASAP of the "legacy" status for as much resources we can, so they are fully part of the policy system.

I think it is difficult to have a better opinion on this without understanding if I'm missing something from the original proposal discussion on this aspect.

Regards,
Jordi
@jordipalet
 
 

El 13/7/19 13:56, "address-policy-wg en nombre de Gert Doering" <address-policy-wg-bounces at ripe.net en nombre de gert at space.net> escribió:

    Hi,
    
    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?
    
    Legacy resources can be converted to PA today, if the holder wants that,
    but this is orthogonal to whether or not a transfer happened.
    
    > I think this is a benefit for the global community, because with that, we bring into the RIR system more and more legacy IPv4 resources, which increase the transparency and community control.
    
    Legacy resources that are documented in the RIPE database *are* transparently
    documented today.  Those get updated in a transfer, even if still "legacy".
    
    For legacy resources that are transferred outside RIPE NCC control, there
    is no lever to force the holders to do anything.
    
    > In a presentation from ARIN for the 2016-2018 period it has been mention:
    > - Overall space managed by ARIN decreased by ~14 million IPv4 addresses, due to Inter-RIR transfers
    > - Overall ARIN issued space increased by ~30 million IPv4 addresses, due primarily to conversion of legacy space via in-region transfers
    > 
    > Opinions?
    
    We're not ARIN :-) - we have our own set of "how to deal with legacy 
    addresses and address holders" policies, and they seem to serve us 
    reasonably well.
    
    So: what is the problem that you want to address?
    
    Gert Doering
            -- APWG chair
    -- 
    have you enabled IPv6 on something today...?
    
    SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
    Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
    D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
    Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
    



**********************************************
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.