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] About the /22 allocation limitation
- Previous message (by thread): [address-policy-wg] About the /22 allocation limitation
- Next message (by thread): [address-policy-wg] About the /22 allocation limitation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dpto. Datos Television Costa Blanca
datos at tvt-datos.es
Fri Apr 11 10:19:25 CEST 2014
Good morning all, >>> But instead of running into exhaustion in "2 months" we can handle it to >>> be "2 years". Please, take in account the time between quotes as an >>> example. >> An example, perhaps, but a wildly unlikely one if I understand¹ your >> proposal correctly. The LIRs in the RIPE region have over the last 18 >> month gathered up a large unmet demand. Therefore I expect that if we do >> create a new small pool for "normal" allocations, it will be gone pretty >> much overnight. It'll be like a lottery, just like when a radio host >> announces «we've got N free X for the first Y people to call us». I do >> not believe this would be useful to the community. >> >> [1] To 1) leave the "last /8 policy" as it currently is (1 /22 per LIR) >> for 185.0.0.0/8 only, and 2) allocate according to demonstrated need for >> all other addresses that somehow finds their way into the RIPE NCC's >> allocation pool (such as returned/reclaimed from LIRs, delegated from >> the IANA Recovered IPv4 Pool, and so forth). This new pool would have a >> minimum allocation size of /24 and no maximum size. Have I understood >> correctly? > I would be against a policy proposal in this form. It would unequal to > the members and would create more hassle for everyone (introducing the > need based justification again, after we have just removed it...that > would be the worst idea) Isnt unequal right now? Are you saying is equal LIRs with thousands and thousands of IP address when there are LIRs with only a /22? Is equal that the LIRs with thousands can make lot of money from LIRs with only a /22? Its so hard to prove you need more IPs? > > Considering the size of the available and reserved pool, and noticing > that it's mostly going up and not down, I would, support a policy > proposal that would change the /22 in a /21 (for example). All members > that already received a /22 could receive a second one, all members > that have not requested a /22 from the last /8, could request a /21. > Thats could be a possibility, but again giving IP space to all the ones ask for it, in my honest opinion, will produce the same problem we have now. New LIRs will run out while old and big LIRs will make money selling IPs to little new LIRs. El 10/04/2014 13:30, Gert Doering escribió: > True. But will it change anything? We knew that we'd run out of IPv4 > at least 10 years ago, and we've made lots of noise to push people towards > IPv6 - and it only started for real when IPv4 had run out. Yes it will. At least I think so. Im not saying to give more space to everyone. Please consider isnt the same LIRs with thousands and thousands of IP space and LIRs with only a /22 Without the possibility, even in the future, of giving more IP space to little new LIRs you are dooming them. > > So if we had made it "last longer", then the "IPv6 for real" deployment > in the large ISPs would have started later - and the installed basis of > IPv4-using gear would have been much larger, so the migration would have > been*more* work... Sorry, didnt understood you. My english isnt so good. Kind Regards, -- Daniel Baeza Centro de Observación de Red Dpto. Internet y Telefonía Television Costa Blanca S.L. Telf. 966190565 WEB: http://www.tvt.es Correo: datos at tvt-datos.es --AVISO LEGAL-- En cumplimiento de la Ley Orgánica 15/1999, de 13 de diciembre de protección de datos de carácter personal, se pone en conocimiento del destinatario del presente correo electrónico, que los datos incluidos en este mensaje, están dirigidos exclusivamente al citado destinatario cuyo nombre aparece en el encabezamiento, por lo que si usted no es la persona interesada rogamos nos comunique el error de envío y se abstenga de realizar copias del mensaje o de los datos contenidos en el mismo o remitirlo o entregarlo a otra persona, procediendo a borrarlo de inmediato. Asimismo le informamos que sus datos de correo han quedado incluidos en nuestra base de datos a fin de dirigirle, por este medio, comunicaciones comerciales, profesionales e informativas y que usted dispone de los derechos de acceso, rectificación, cancelación y especificación de los mismos, derechos que podrá hacer efectivos dirigiéndose a Televisión Costa Blanca, S.L., C/ San Policarpo 41 Bajo. C.P: 03181 Torrevieja (Alicante). -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20140411/462a09de/attachment.html>
- Previous message (by thread): [address-policy-wg] About the /22 allocation limitation
- Next message (by thread): [address-policy-wg] About the /22 allocation limitation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]