This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/members-discuss@ripe.net/
[members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
- Previous message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
- Next message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philippe Bonvin
webmaster at galphanet.com
Sat Feb 20 18:33:28 CET 2016
Dear all, Thanks to the RIPE for asking this question. Yes I think that multiple LIR accounts are a problem. I don’t see any valid reason to this. The role of the RIPE is to ensure an equal distribution of resources and having multiple LIR accounts doesn’t serve this cause. Selling IP addresses should not exist, in fact the name and address of the RIPE is in every whois queries in their address space ! The address space should be treated as a finite resource that nobody own, we merely have the authorization to use a part of it. If one company merge or split to another, they can ask the RIPE to change the ownership of the resources. Also, if one company want to separate their business activities, they can do it with multiple ASN. There is no technical reason to allow multiple LIR per legal entity. I understand that it is easy to create new companies but in my opinion there should be more restrictions than that : 1. To open a new LIR account, the applicant must follow a welcome course given by the RIPE explaining the good practice. (This would be covered by the opening fees). 2. The new LIR should justify their needs : a. Why they need an ASN and the routing policies (like enforced today) b. How they plan to use their address space (IPv4 and IPv6) 3. Then, the RIPE would assign an ASN and a IPv6 space corresponding the needs plus a margin 4. If the LIR wants to have a /22, then they should prove that the IPv6 space is effectively in use (for example a web server or an smtp server) and that their ASN are multi homed. 5. The /22 should not be transferable at all and should be announced by an ASN of the LIR. 6. The contact person and email address cannot be the same for 2 LIR. With these rules, it should be more difficult but not impossible to open a LIR for having more IPv4 addresses. It seems to me that the RIPE has in the past had a similar workload. Then, the RIPE should bill the LIR for the IP space they have, like it was before. The big LIR contribute financially more than the smaller ones, in the same idea that a big company pays more taxes than a smaller one. The RIPE can concede a reduced IP space fee if the LIR can demonstrate an IPv6 address space effectively in use. This check should be done once a year before the billing. That should help older LIR with only IPv4 to have an IPv6 space announced and to encourage the return of unused IPv4. Best regards Philippe >> Dear colleagues, >> >> The RIPE NCC Executive Board would like to ask the membership to >> discuss >> the issue of RIPE NCC members opening additional LIR accounts. >> >> There were comments at the RIPE NCC General Meeting (GM) in November >> 2015 that members having the ability to open additional LIR >> accounts, >> each of which can request a /22 of IPv4 address space, may run >> against >> the spirit of the last /8 policy. In light of this, the Board >> decided to >> temporarily suspend the ability of RIPE NCC members to open >> additional >> LIR accounts. >> >> The RIPE NCC began to allocate IPv4 address space from the last /8 >> policy on 14 September 2012. Since that time the RIPE NCC has >> allocated >> more than 8,600 /22s, yet there remains 0.94 of a /8 still in the >> pool. >> >> ACTION REQUIRED: >> The Board asks the membership to provide their opinion on and >> discuss >> the following points: >> >> 1. Is the activity of members opening additional LIR accounts a >> problem >> that must be prevented? > Yes, should be prevented. > >> 2. If this activity is a problem that must be prevented, what action >> should the RIPE NCC take to attempt its prevention? > Stop allowing opening multiple LIR account for one legal entity. > >> Statistics pertinent to this discussion are available in this >> article on >> RIPE Labs: >> > https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-lir-accounts?pk_campaign=members&pk_kwd=list-ncc <https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-lir-accounts?pk_campaign=members&pk_kwd=list-ncc> >> >> The Board asks that members discuss this issue on the Members >> Discuss >> mailing list <members-discuss at ripe.net <mailto:members-discuss at ripe.net>>. >> >> The Board will monitor the discussion and will review it at the next >> Executive Board Meeting on 31 March 2016. Depending on the outcome >> of >> that meeting, the Board may propose a resolution for members to vote >> on >> at the RIPE NCC General Meeting in May 2016. >> >> Best regards, >> >> Nigel Titley >> RIPE NCC Executive Board > > If you don't want to receive emails from the RIPE NCC members-discuss > mailing list, please log in to your LIR Portal account and go to the > general page: > https://lirportal.ripe.net/general/ <https://lirportal.ripe.net/general/> > > Click on "Edit my LIR details", under "Subscribed Mailing Lists". From > here, you can add or remove addresses. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20160220/62333d9e/attachment.html>
- Previous message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
- Next message (by thread): [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]