On Mon, Mar 4, 2013 at 2:46 PM, Emilio Madaio <emadaio@ripe.net> wrote:
We encourage you to read the draft document text and send any comments to address-policy-wg@ripe.net before 18 March 2013.
Needs a _lot_ more discussion. 1) The impact analysis implies that this applies to RIPE LIRs getting PA/legacy IP space from non-RIPE RIRs. As I understand the text, this is not the case. The proposal merely deals with transfer of RIPE PA/legacy IP space to non-RIPE LIRs. IMO, this means that the wording in the PDP is unclear or that the impact analysis is flawed. Either way, this is not desirable. 2) What are the requirements so that another RIR's policy is seen as "compatible inter-RIR transfer policy"? Who defines this and where? 3) "Increases the supply of IPv4 addresses available to RIPE NCC LIRs" Again, I can not see this in the wording of the PDP. If anything, this decreases the available pool. I am not saying this is good or bad, merely stating a fact. 4) "Maintains the integrity of RIPE's whois database and ensures they are part of the approval and transfer process" If transfers outside of RIPE are not allowed, surely the whois database will remain correct. If it's not correct and policies have been circumvented in the process there are procedures to deal with this. I am not saying I agree or disagree with the apparent(?) intention behind all this; I think we need to have a clear understanding of what's actually proposed before we can argue about specifics. -- Richard PS: "of an RIR" is incorrect; it's "of a RIR"