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] Transfer Requirements for IPv4 Allocations
- Previous message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
- Next message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Radu-Adrian FEURDEAN
ripe-wgs at radu-adrian.feurdean.net
Thu Apr 23 14:34:50 CEST 2015
On Thu, Apr 23, 2015, at 14:20, Gert Doering wrote: > The last /8 is not there to do "business as usual, based on IPv4" - it > is there to enable *new* market entrants to run a few critical things > with IPv4, while the main deployment has to happen on IPv6. This is sliding off-topic, but I don't see lots of new entrants interpreting things this way. For the moment it still is "business as usual based on ipv4" (with *SOME* ipv6 addition) or "no business at all". Besides, with a free pool larger than 12 months ago, larger than in october 2012 and the second largest among RIRs (after AfriNIC), there still is something that could be done for the new players.
- Previous message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
- Next message (by thread): [address-policy-wg] Transfer Requirements for IPv4 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]