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/[email protected]/
[address-policy-wg] 2015-05
- Previous message (by thread): [address-policy-wg] 2015-05
- Next message (by thread): [address-policy-wg] 2015-05
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tom Smyth
tom.smyth at wirelessconnect.eu
Wed Oct 21 13:20:31 CEST 2015
Perhaps people would support the Proposal, if the there was a stricter condition on the transfers, ie that the Lir has not had any transfered IPs added to its registry, (in addtition to the rule that the Lir has not transferred IPs out of its registry) On Wed, Oct 21, 2015 at 12:14 PM, Uros Gaber <uros at ub330.net> wrote: > Hi, > > I would support this proposal with some amendments, first there should be > a 'top-cap' on how many IPs a LIR can have and still request a new /22 > every 18 months - for example if a LIR has an /20 equivalent or more > already assigned this LIR could not request new allocation (this has > already been pointed out on the list) and I think that there should also be > a minimum RIPE free space cap, where if we would reach somewhere in the > range of /12 only new LIRs are eligible to get new /22 allocation. > > This is to get new entrants in the market some more wiggle room against > the old players. > > Sincerely, > Uros > > On Wed, Oct 21, 2015 at 12:40 PM, Ciprian Nica <office at ip-broker.uk> > wrote: > >> >> >> On 10/21/2015 1:26 PM, Shahin Gharghi wrote: >> > Hello >> > >> > I support this proposal. If you are worry about running out of IPv4, you >> > should stop those are registering new LIRs, transfer the IPs and close >> the >> > LIR. Even 2015-01 is unable to stop them. >> > If it is limited to those LIRs who didn't transfer any IP to other >> LIRs, I >> > think it could reduce amount of unnecessary transfers. >> > I heard a lot about this: "New entrants should have access to IPv4". I >> > think you should say that in this way: " The new entrants should have >> > access to the INTERNET". Don't you think the new LIRs need to run IPv6? >> or >> > imagine we are in 2020 and we ran out of IPv4, what should we do? Do it >> > now. I think we are just postpone switching to v6. >> > >> > >> >> If RIPE runs out of IPv4 sooner it will not help switching to v6 faster. >> It only means that the new entrants will have to buy the resources from >> the market at prices which will be obviously higher. >> >> Iran is a good example, as a country can be considered a relatively new >> entrant. What has happened over there ? 0.05% IPv6 adoption rate >> according to google stats and Iran is the #1 importing country of IPv4 >> resources. >> >> I don't understand why there's still this confusion that if RIPE's pool >> will be empty, many think there will be no more IPv4 available and >> everyone will go the next day to IPv6. It's totally wrong. >> >> Ciprian Nica >> >> >> > -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 --------------------------------- PLEASE CONSIDER THE ENVIRONMENT BEFORE YOU PRINT THIS E-MAIL This email contains information which may be confidential or privileged. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify me by telephone or by electronic mail immediately. Any opinions expressed are those of the author, not the company's .This email does not constitute either offer or acceptance of any contractually binding agreement. Such offer or acceptance must be communicated in writing. You are requested to carry out your own virus check before opening any attachment. Thomas Smyth accepts no liability for any loss or damage which may be caused by malicious software or attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20151021/90aba1f2/attachment.html>
- Previous message (by thread): [address-policy-wg] 2015-05
- Next message (by thread): [address-policy-wg] 2015-05
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]