[members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss

First off; I'm glad someone is trying to keep the conversation on track
rather than allowing it to degrade further into the politics of IPv4
allocation restrictions /(and it is pure politics at this stage)/.

As Paul points out the goal of this discussion is to reduce abuse of an
extant policy, not a new one, and since the goal of said extant policy
is to encourage IPv6 adoption I would agree with applying all of the
below. But if we have to choose only one option then I'd vote for option
5 as it looks the most effective.

-Tim


On 12/02/16 23:13, Paul Civati wrote:
>
> So going back to the original question really, which was multiple LIR accounts..
>
> This has diverged into how/why people are taking them and that is that people
> want to abuse the rules around limited remaining IPv4 resources set aside
> for new entrants.
>
> So we can disincentivise through cost, admin and technical approaches.
>
> 1. Time delay before a new LIR can be merged with another, 12 months?
> This seems a reasonable option, why would anyone create a brand new
> LIR and then want to merge it <12 months.
>
> 2. Make additional fees for multiple LIRs under one organisation, if you
> want it fine, but pay for the additional admin burden.
>
> 3. Additional fees for six months once an LIR is merged.  May seem
> drastic but if people are abusing current rules then you have to combat
> them.
>
> 4. If an LIR is opened it has AS and IP4/6, there should be some kind of 
> rule about this IP space having been visible through that AS number before 
> a merger is permitted.  I am thinking about creating technical admin burden 
> for people creating many LIRs, so that they will have to go through the 
> technical hassle of setting up configurations before doing a merger,
> ie. even if you are willing to pay extra fees to open 10x LIR to get
> space then also be prepared to set up 10x BGP configs for it.
>
> Not completely related to the original point, but if you want to reduce 
> motivation for people to still rely on IPv4 straight off then:
>
> 5. New LIR opens and is issued with IPv6 space immediately, then and only
> once that IPv6 space is up and visible in routing tables can you apply for
> your IPv4 space for that LIR.  If you are not ready to run IPv6 at LIR opening,
> will you ever be?
>
> Just throwing out some ideas, may not be perfect of course..
>
> Regards,
> Paul.
>

-- 
<http://liquidns.com>
	


  Tim Armstrong


    Technical Director
    Treestle B.V.
    Goudsesingel 78, 3011 KD,
    Rotterdam, The Netherlands
    Chamber of Commerce: 59116803
    Office:   +31 (0) 10 3400 720
    Mobile:   +31 (0) 61 7544 472




    Treestle runs one of the world's fastest global managed DNS
    platforms at www.liquidns.com <http://www.liquidns.com/> and
    offers LiquiD AutoScaler, a website-user centric autoscaling
    solution at www.liquidautoscaler.com <http://www.liquidautoscaler.com/>.


    Independent software vendor for:

	 
<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=ORG-TB77-RIPE&type=organisation>
	


    Member of:

    <https://apps.db.ripe.net/search/lookup.html?source=ripe&key=ORG-TB77-RIPE&type=organisation>

<https://aws.amazon.com/marketplace/pp/B013UXHSOO/?ref=_ptnr_pe_>
<https://cloudstore.interoute.com/LiquiDAutoScalerBasic><https://liquidautoscaler.com/documentation/other/quickstart>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20160213/f59b5bb9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bbhggbae.png
Type: image/png
Size: 9152 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20160213/f59b5bb9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eiafjgbe.png
Type: image/png
Size: 124 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20160213/f59b5bb9/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ccafbfdj.png
Type: image/png
Size: 3713 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20160213/f59b5bb9/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: idhdgjag.png
Type: image/png
Size: 2584 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20160213/f59b5bb9/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hcdhicih.png
Type: image/png
Size: 3491 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20160213/f59b5bb9/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: afihiheh.png
Type: image/png
Size: 2051 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/members-discuss/attachments/20160213/f59b5bb9/attachment-0005.png>