[address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)

Nick sums up my opinion admirably. Whilst I have some sympathy with the aim, I do not believe it will achieve it, and there will be some unwarranted side-effects.

-1 Do not support as is

Ian

-----Original Message-----
From: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] On Behalf Of Nick Hilliard
Sent: 19 October 2016 10:53
To: Marco Schmidt <mschmidt at ripe.net>
Cc: address-policy-wg at ripe.net
Subject: Re: [address-policy-wg] 2016-03 New Version and Impact Analysis Published (Locking Down the Final /8 Policy)

Marco Schmidt wrote:
> We encourage you to read the draft document and send any comments to
> <address-policy-wg at ripe.net> before 17 November 2016.

The purpose of the policy is to restrict the flow of /22 allocations
from the RIPE remaining ipv4 pool.  While I'm sympathetic to this idea,
the policy is not going to fix the problem that it sets out to fix and
will create a new set of problems which will be extremely difficult for
the RIPE NCC to recover from.  Consequently I do not support it, because:

1. the core problem won't be fixed: the outgoing flow of /22s will not
be affected in any way because speculators will get allocations using
shelf Companies which can be sold as-is, thereby bypassing any policy
that the RIPE community might want to consider in this area.  The only
way to even begin to fix this would be to move back to a needs-based
allocation policy.

2. unregistered transfers will become a problem and this may become
intractable in the future.  This directly goes against the core
principals of the RIPE database which is to ensure accurate registration
of address holder details.

Also, asset divesting is not catered for in the policy. If a company /
LIR splits up, there is no way to handle splitting of IPv4 address
allocations in the policy.  There is no clear way to fix this problem
within the principals of the policy.

As an aside note, the problem of ipv4 allocation speedup from the RIPE
NCC has been exacerbated by the recent RIPE NCC GM resolution: "The
General Meeting approves the ability of RIPE NCC members to create
additional LIR accounts".  The net effect of this is that there is now a
divergence between intended RIPE policy and RIPE NCC implementation.
This is probably not helpful in the long run.

Nick

Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of Sky plc and Sky International AG and are used under licence.

Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of Sky plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.