Hi Elvis, On Tue, Apr 25, 2017 at 07:42:12PM +0300, Elvis Daniel Velea wrote:
What it will do is, for 'transfers' of Legacy space where both the old and the new holder want to have it verified by the RIPE NCC, both parties will need to sign a document where parties authorised to sign will confirm the change of the legacy holder (basically, a transfer).
Oh, this is *voluntary*? This is not obvious from the language of the proposed changes and one does not, perhaps, expect to see anything non-mandatory in a RIPE policy document ;p So let me see if I have this right: - Transfers of legacy space stay outside the NCC's purview to the extent they do now? - LRH who *want* to have a resource transfer verified can do so by submitting verification paperwork of some description? - Changes in the db wrt legacy resources where the LRHs do *not* want this are marked as "non-verified by NCC" or something like that but they are not rejected?
Even after the comments above, do you still object to the proposal?
If my above understanding is correct, and an updated proposal would insert some language to make the voluntary nature of the transaction clearer, I'll withdraw my objection on that point. As for the cost of it and possible defrayment of same, I'll wait for the Impact Statement before making a decision. Sorry for the misunderstanding, if that it was, and best regards, Sascha Luck