- members-discuss - mailman.ripe.net

Re: [members-discuss] < new LIRs by country > [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
by Matthias Šubik 20 Feb '16

20 Feb '16

> On 19.02.2016, at 14:19, Claudiu Foleanu <claudiu.foleanu(a)tennet.ro> wrote: > > Hi Matthias, > > No, i`m not interested in blaming a country. I already did my research and combined with some other info from this topic you will quickly find that > the low cost of 100 eur for a company in the Uk has already been used. Since 2015 january there is a number of 400 new lir`s added from Uk. > I can provide a list of new equipments (cheap) that are not ipv6 ready. The latest available on the market are Netis routers and equipments witch some of then are not ipv6 ready. And we cannot force the clients to upgrade routers,computers,softwares,phones,sip`s and so on.. > > And btw i don`t think UK is now in a new internet buble or hosting buble or whatever requires ipv4 buble This is an interesting approach: looking on the legal side, separating by country is of course valid. In my first assumption I naïvely thought just look at the plain numbers. But you mention the equipment side: The customer will have to upgrade the router sooner or later, but the regulation should make it about the same time for all of us. so there is not too much negative influence on the market. If some can buy IPs, other can’t, there is a better start with an offset of currency and age of LIR. Therefor we need to tell everybody, that new devices get new, read IPv6-enabled, connections. We can deal with RFC 6598 (CGNAT) for a while, but customer should prefer v6 ready equipment, and we should not wait to actively deliver v6 connectivity. *question to all readers* There are a lot of CGNATed networks, especially with mobile broadband. Hands up who has a public IP on the smart phone, and didn’t ask for it. *thank you* Ask the other LIRs what they see … I can only speak for the market I’m in, and in Austria residential internet products get converted to to CGNAT right now. And the network I’m writing this e-mail from is inside a /13 route (!), but I share this outbound IPv4 with others, and have working v6 connectivity on my desktop. And I’m obviously not in the AS I’m responsible for, as I stated earlier, we are one of the smaller LIRs. We did start with v6, the end was visible when we started buying our equipment. Matthias

2 1

Re: [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
by Philippe Bonvin 20 Feb '16

20 Feb '16

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-li… <https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-li…> >> >> The Board asks that members discuss this issue on the Members >> Discuss >> mailing list <members-discuss(a)ripe.net <mailto:members-discuss@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.

1 0

Re: [members-discuss] [comms] [ncc-announce] [news] RIPE NCC, Members and Multiple LIRs
by Sylvain Vallerot 19 Feb '16

19 Feb '16

TL,DR: LIR account control is not related to the last /8 policy which is about allow End Users to get minimal ressources, debate should occur about a policy about the last *assignment* to the new EndUser. Dear all, I'ts been a long time yesterday to read all theses threads about wether or not to continue to allow members to open new LIR accounts. Let 'A' be "wether or not to allow members to open new LIR accounts". We've seen quite quickly that this proposition would be a very poor attemps to avaoid some members to get another /22, disregarding the last /8 policy, since this can be easily achieved another way (creating another company by example). Workarounds exist, some of them quite respectful of the letter of the policy, some but simply cheating and/or providing false information to the Ripe. Facing the poor impact such a measure would have on the real problem that we are strugling with, debates went naturally quite further to try to take other aspects into consideration and try to get a more effective solution thant just A. This has no end, we can't get to a conclusion trying to match A with the last /8 policy because the are not related. Many people here recalled that the last /8 policy spirit (if not the letter) is to allow newcomers to born and get the minimal IPv4 ressource to be able to jumpstart. This is what it is all about. But those newcomers do not have to be LIRs. Thinking that they should is wrong in two ways : forgetting that most companies needing to born outside there are actually EndUsers (yes, our clients quite often), and taking it for granted that a LIR has an ASN, a network, is an IP operateur itself or even an ISP, which is just wrong. But a LIR is *just* an IP distributor benefiting from a special relationship with the Ripe to *serve* its EndUsers. So having a policy like the last /8 read from an ASN or ISP perspective instead of from the EndUser's is quite an abuse of our LIR personality. Now, A is just void, never mind. It has been the occasion for many to contribute and have an oversight of some mechanisms for controlling the distribution of the last /8, and/or ways to cheat. We can use these to think about realistic measures to achieve the real goal. And the real problematic from last /8 policy could be stated like : « how to state distribution rules for the LIRs in order to have them to distribute one and only one /2x per EndUser, and enforce them » /2x to be defined later. Such a statement would help us to have a discussion that has a chance to come to something constructive. This also means a change of paradigms that will quite help : 1. hey LIRs, last IPv4s are not for you. 2. EndUsers back to the center of the Ripe's preocupations 3. limiting a LIR to one or several accounts is void, limiting them to a /22 is void also 4. back to serious and responsible relations between EndUsers and LIRs : EndUsers identities and relations should be seriously documented 5. LIRs back to their distribution role (not consumers), with a clear responsibility about making serious assignments and respect the policy limit per EndUser 6. allocations unlocked but LIR abuse will not be tolerated So, back to a normal working for LIRs that commit to achieve their real function and assume responbility for that. LIRs that mess up their LIR function and their IP operator have already received their last /22. They now for long that IPv4 is not available, and they must move to ipv6 or get IP on the market. LIRs that understand and commit to make a proper distribution to the new EndUsers coming should be able to fullfill their role, under control, but without irrelevant restrictions. Please comment. Best regards, Sylvain -- http://www.opdop.fr - mutualiser et interconnecter en coopérative Opdop - Société Coopérative d'Interêt Collectif sous forme de SARL sur IRC réseau geeknode #opdop - tél: 0950 31 54 74, 06 86 38 38 68

2 2

Re: [members-discuss] < new LIRs by country > [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
by Matthias Šubik 19 Feb '16

19 Feb '16

> On 19.02.2016, at 10:37, Claudiu Foleanu <claudiu.foleanu(a)thorpanel.com> wrote: > ... > I wonder if ripe does not have a report on creation of new lir`s who requested a /22 by country. I think this report will be useful. This would overestimate the role of a country, and ignore the fact that countries differ by size, and differ by LIR per inhabitant already with a heavy contrast. You could say “damn germans / spaniards / whatever”, but is is totally ignoring the size difference. If you would really want that info, just count it, the LIR code is country code based, and the LIR table is downloadable. We had another question on this list “what happens if we need more IPv4 addresses” because of growth. So to realize the size difference, we might need to calculate the growth in internet adoption in the different countries as well. I did not buy no (important) IPv6 incapable equipment for around eight years now. So I doubt there is legitimate growth in v4, except to reuse old equipment (which is just a delay of an investment). And yes, end user prices for v4 might rise as well, this can’t be prevented from now on, maybe just delayed. Matthias

2 1

Re: [members-discuss] Is mailing list become too small for RIPE?
by Lu Heng 19 Feb '16

19 Feb '16

Hi Mathias: Seems few people likes the idea, and consider the outbreak happened few days ago with massive unscripble request, it is obivious that most new member don't even know they ware automatically scribe to this list. NCC please provide an feed-back on the suggestion and maybe, board should discuss it the issue(or it is more of operational matter?) On Fri, Feb 19, 2016 at 1:38 PM, Matthias Šubik <matthias.subik(a)ucnd.at> wrote: > >> On 19.02.2016, at 13:35, Lu Heng <h.lu(a)anytimechinese.com> wrote: >> >> Hi Matthias: >> >> A forum supports Email notification and replies(in which most open >> software nowadays do that), if you dislike forum, you can still follow >> the threads interests you the maillisng list way. > > QED … but we can leave it like that, > we agree to disagree. That’s fine for me. >> >> And for member like me like more passive experience of engagement, >> probably forum the way it is, will do better. > > I agree, but for the point, this doesn’t serve the purpose the list was created for. This is a new idea. > > This e-Mail is not copied to the list, as it probably is a notion of personal preference. Nobody cared enough to reply on the question “why do we have this *list* anyway” … > > take care > Matthias > -- -- Kind regards. Lu

2 1

Re: [members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
by Aleksey Bulgakov 19 Feb '16

19 Feb '16

2 1

Re: [members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
by Thomas Mangin 18 Feb '16

18 Feb '16

As requested … —- Dear Thomas, My name is Claudiu Foleanu from TENNET TELECOM and Interlan Association (We hosted RIPE71 in Romania). I have tried now for a couple of days to post to this topic but for some reason i cannot. I have already mailed ripe-ncc to check this issue. This topic is very important to us and we wish to contribute to it. Can you post this message for me? I have no other solution for this message to reach the members. Thanks so much. Best regards, Claudiu Foleanu ----------------------------------------------- Hi, We in Romania trough Interlan Association are complaining about the issues regarding ipv4 "market" (witch seems to be supported by the community) for over 1 year now. We had a consultant from RIPE in Bucharest and we detailed each and every issue regarding this problem. Ipv4 / Ipv6 was not created for people to make money. It was created to ensure communication between people. Don`t get me wrong, we are not against the market, the unused resources should be redistributed somehow (ripe-ncc,market). But we should take care and ensure that new entities can have IPv4 ip space. RIPE-NCC should request usability reports from every LIR at least once every year. Unused resources should be redistributed. Three times over the last couple of years we have lost ip space witch was rented from other LIR`s. Or had to pay a huge amount of money to transfer them. Three times now we had to renumber and remake the topology of the network in order to support the loss. Why are we not using more IPV6? Facebook is ipv6 akamai,google ok.. Nice. But we have over 10.000 divices routers,switches,etc.. witch do not support ipv6. And we are talking just about customer related devices. Their own home routers,switches,ip phones etc... We should convince China and the manufacturers to build software ipv6 ready! We already tried and it`s not that easy. One manufacturer asked for 200.000 usd in order to redo the software ipv6 ready for some routers. Ask VODAFONE why are they buying ipv4. The answer will be the same. Customers do not have ipv6 ready devices, or they have to many of their own devices ipv6 not ready. You should ask the customers of the LIRS if it was ok to get their ipv4 allocated space taken away by a notification received by email. Big companies should not be allowed to transfer ipv4 to their lir if they do not have at least 30 - 50% implementation on ipv6. We are putting the burden of the costs on the back of start-ups and leaving the big companies to profit on this market. I`m not quite sure what prompted this discussion but i`m glad it`s out! You should look into address space witch left Romania. I can tell you that over 50% at least of that address space was in use. I now get 3 -5 emails each day from small companies in Romania asking for address space. But we have none to give. We have allocated everything in order to try to help! Our solution: You make a new lir to get a /22 ok, then you cannot sell the ip address space. If the lir is for whatever reason closed the ip address space should be requested back. Nobody will create a new lir for a /22 and pay the fees required if the address space given it`s tied to that lir, it will just be to expensive. Best regards, Claudiu Foleanu TENNET TELECOM -----------------------------------------------

18 32

Re: [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
by marco＠naefmarco.ch 18 Feb '16

18 Feb '16

Hello RIPE supports reselling of big subnets by providing their Transfer listing service. Those networks shouldn’t be sold. They should be returned to the NCC pool and be assigned to providers who need them. Von: members-discuss [mailto:members-discuss-bounces@ripe.net] Im Auftrag von Pavel Odintsov Gesendet: Donnerstag, 11. Februar 2016 15:42 An: Radu Brebu <dial(a)dialcube.ro> Cc: members-discuss(a)ripe.net Betreff: Re: [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss Hello, folks! That's good conversation. I'm representing VPS service company. We bought multiple /20 and /21 subnets at last 2 years. But actually there really big injustice exists here! I've followed all RIPE guidance and request resources only when they really required for next 3-6 months. I have 95% subnet utilization in each network! All my IP addresses really used. But I known so much LIR's who just ignore RIPE rules and requested bunch of /18, /16 networks many years ago.... just because they can. Right now almost all this networks are on IPv4 market. And I should pay my money to persons which violated RIPE rules for a long time. Than't really weird, isn't it? On Thu, Feb 11, 2016 at 5:34 PM, Radu Brebu <dial(a)dialcube.ro <mailto:dial@dialcube.ro> > wrote: Hi all, This is a socialist way of thinking, you are free (ipotetic speaking) to open another lir and satisfy your VPS needs no? some companies prefer to plan their business long term. In my opinion it's not ok to prioritize resources keeping in mind only the need. We are leaving and doing business in a capitalist environment, buying resources it is what is all about. On 02/11/16 16:19, José Manuel Giner wrote: I agree with it. We need IPs to continue providing VPS servers, and other LIRs with unused prefixes, no sense... On 11/02/2016 15:09, Aleksey Bulgakov wrote: Hi, all. I think, it is better to return unused allocations, received before 2012, to the NCC pool. -- Kind regards, Aleksey Bulgakov FastTelecom, CEO 7 926 6908729 14:02, 11 февраля 2016 г., Nigel Titley : 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? 2. If this activity is a problem that must be prevented, what action should the RIPE NCC take to attempt its prevention? 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-li… <https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-li…> &pk_kwd=list-ncc The Board asks that members discuss this issue on the Members Discuss mailing list . 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/ Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses. ---- 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/ Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses. -- Sincerely yours, Pavel Odintsov CTO, FastVPS Eesti OU

14 19

Re: [members-discuss] [ncc-announce] [news] RIPE NCC Members and Multiple LIR Accounts - Please Discuss
by lir＠di-net.ru 18 Feb '16

18 Feb '16

First of all, I think we all should agree that current debates are all about abusing LIR creation procedure to get extra IPs. Why some percent of members was trying to explain here their reasons why they can't use IPv6. Relatively to the main discussion in short: I believe we can do nothing to prevent different types of abusing for a 'long distance'. They've asked whether the activity of members opening additional LIR accounts is a problem that must be prevented? Sure it is, RIPE can block requests from existing LIRs, or add some extra payments for such procedure. The second option actually is nothing but a small delay to the times until the prices for IPv4 will be higher than LIR charges. As mentioned earlier, if we just block an ability to create LIR for an existing member, it's definitely not a problem to register new companies. It is not even necessary to create a new company, almost everyone can open paint application and create all needed documents. RIPE has no ability to validate somehow whether the documents are juridical correct or not, including merging/sell documents. The principles of honesty, responsibility and reasonableness are fading when money comes to play. IPv4 address space is already monetized and we can't fight with or deny this fact. Besides, I don't agree that any types of audit can help here. This procedure requires huge effort not only from RIPE employees but from LIR engineers too, in large LIRs it may be prolonged for indeterminable time. Estimating effectiveness of every particular LIR address space and attempts to retrieve some IPv4, could lead RIPE to become a regulator not a coordinator. It's a good idea to check ARIN policies applied to their last block, and may be adopt some paragraphs. Some basic principles that are emphasized: - Documentation, network schemes and so on are strongly required for any allocation. In contrast with ARIN, RIPE just give /22 to any new member. - Necessity to provide data demonstrating utilization of this space (immediately and after one year) Summarizing all above, I think RIPE should prevent any IPv4 address allocations (including new LIR members) without complete plans, schemes and demonstrations of necessity and effectiveness. May be RIPE can afford one dedicated engineer being responsible for analyze such plans. Still it must be clear that complete IPv4 exhaustion is just the question of time, no matter how hard RIPE put the screws on allocation procedure. Alex Klimenko Digital Network NOC

1 0

Re: [members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
by Александр Клименко 18 Feb '16

18 Feb '16

First of all, I think we all should agree that current debates are all about abusing LIR creation procedure to get extra IPs. Why some percent of members was trying to explain here their reasons why they can't use IPv6. Relatively to the main discussion in short: I believe we can do nothing to prevent different types of abusing for a 'long distance'. They've asked whether the activity of members opening additional LIR accounts is a problem that must be prevented? Sure it is, RIPE can block requests from existing LIRs, or add some extra payments for such procedure. The second option actually is nothing but a small delay to the times until the prices for IPv4 will be higher than LIR charges. As mentioned earlier, if we just block an ability to create LIR for an existing member, it's definitely not a problem to register new companies. It is not even necessary to create a new company, almost everyone can open paint application and create all needed documents. RIPE has no ability to validate somehow whether the documents are juridical correct or not, including merging/sell documents. The principles of honesty, responsibility and reasonableness are fading when money comes to play. IPv4 address space is already monetized and we can't fight with or deny this fact. Besides, I don't agree that any types of audit can help here. This procedure requires huge effort not only from RIPE employees but from LIR engineers too, in large LIRs it may be prolonged for indeterminable time. Estimating effectiveness of every particular LIR address space and attempts to retrieve some IPv4, could lead RIPE to become a regulator not a coordinator. It's a good idea to check ARIN policies applied to their last block, and may be adopt some paragraphs. Some basic principles that are emphasized: - Documentation, network schemes and so on are strongly required for any allocation. In contrast with ARIN, RIPE just give /22 to any new member. - Necessity to provide data demonstrating utilization of this space (immediately and after one year) Summarizing all above, I think RIPE should prevent any IPv4 address allocations (including new LIR members) without complete plans, schemes and demonstrations of necessity and effectiveness. May be RIPE can afford one dedicated engineer being responsible for analyze such plans. Still it must be clear that complete IPv4 exhaustion is just the question of time, no matter how hard RIPE put the screws on allocation procedure. Alex Klimenko Digital Network

1 0