This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
- Previous message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
- Next message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Mon Jul 15 10:05:33 CEST 2019
* 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
- Previous message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
- Next message (by thread): [address-policy-wg] question about IPv4 legacy and transfers - should we convert legacy to non-legacy with transfers?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]