On 14 August 2015 at 10:54, Marco Schmidt <mschmidt@ripe.net> wrote:
https://www.ripe.net/participate/policies/proposals/2015-04
We encourage you to review this proposal and send your comments to <address-policy-wg@ripe.net> before 14 September.
Couple of questions/comments...
From 1.0
Shouldn't the scope be explicit as to what is/isn't included
From 2.1
"Transfers can be on a permanent or non-permanent basis." How is this going to be recorded and managed within the context of reflecting it being a non-permanent transfer?
From 2.2
"assigned by the RIPE NCC on a restricted basis (such as IPv4 or 16-bit ASNs)" Rather than "such as" this needs to be a definitive list of what is classed as a restricted resource
From 3.1
Again a list of conditions or references to policies that impose restrictions needed
From 4.0
M&A process is mentioned, should there be other references to this? Especially as M&A (as I understand it) allows 2.2 to be overridden General - As this is about transfers should this also cover returning resources to ripe NCC so all types of transfers be included - broadly support the unification of transfer policy into a single document, just things bits are missing or muddy J -- James Blessing 07989 039 476