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] The final /8 policy proposals, part 3.2
- Previous message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
- Next message (by thread): [address-policy-wg] RIPE NCC NRO Number Council Candidates Confirmed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Remco van Mook
Remco.vanMook at eu.equinix.com
Thu Sep 17 19:49:00 CEST 2009
Not everybody is going to run out at the same time because there are likely already LIRs whose assignment rate is so low they'll still have space from their current allocation in 2015 or so - intentional or not. Remco ----- Original Message ----- From: address-policy-wg-admin at ripe.net <address-policy-wg-admin at ripe.net> To: address-policy-wg at ripe.net <address-policy-wg at ripe.net> Sent: Thu Sep 17 16:11:53 2009 Subject: RE: [address-policy-wg] The final /8 policy proposals, part 3.2 > Agree for as long as there are addresses enough to meet the applicants > needs. Yet it is IMHO pointless to hand out micro-blocks as a sorry > response to a PA-request for a substantially larger block. In particular, what if the applicant's competitor just received a much larger allocation two weeks earlier? That's why I think that any policy change related to the last IPv4 allocations should focus on some way to make sure that all LIRs run out of IPv4 at roughly the same time. Maybe the policy change needs to take effect before we reach the last /8 from IANA. Maybe we need some kind of cap on maximum allocation that shrinks month by month. Maybe we should link the allocation size to the number of weeks it would take to use it up given the applicant's historical run-rate, and then shrink that number of weeks every month. > This isn't > about forcing anyone in any particular direction, but about whether it > is of greater benefit to the community at large to allocate > such blocks > to organizations with a potential to enable connectivity between large > numbers of new users and the existing v4 network. Has anyone clearly explained how any organization would enable such connectivity in a way that existing LIRs could not? It sounds like people are assuming that there may be some magic bullet while in reality there are just network providers providing services. The technical details of those services change over time for all LIRs. Innovation is not restricted to new entrants. --Michael Dillon This email is from Equinix Europe Limited or one of its associated/subsidiary companies. This email, and any files transmitted with it, contains information which is confidential, may be legally privileged and is solely for the use of the intended recipient. If you have received this email in error, please notify the sender and delete this email immediately. Equinix Europe Limited. Registered Office: Quadrant House, Floor 6, 17 Thomas More Street, Thomas More Square, London E1W 1YW. Registered in England and Wales No. 6293383. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20090917/442d0b11/attachment.html>
- Previous message (by thread): [address-policy-wg] The final /8 policy proposals, part 3.2
- Next message (by thread): [address-policy-wg] RIPE NCC NRO Number Council Candidates Confirmed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]