[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 ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Mon Jul 22 15:16:04 CEST 2019
On Sun, Jul 21, 2019 at 05:19:15PM -0400, Hans Petter Holen wrote: > On Sun, 14 Jul 2019 at 17:56, JORDI PALET MARTINEZ via address-policy-wg < > address-policy-wg at ripe.net> wrote: > > > What I???m saying is that we force the change of status from non-legacy to > > legacy if addresses are transferred to a new member or an existing member, > > as both of them will have all the legal bindings already with RIPE NCC. > > > > If the goal is to have a correct and updated registry adding criteria by > force to transfers is counter productive. > > For larger address space transactions this will simply lead to transfer of > legal entities, or other legal constructs to circumvent the policies. > > I belive the community should focus strongly on an accurate registry as the > main principle. One should remember that "the main" is distinct from "the only". Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland
- 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 ]