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/address-policy-wg@ripe.net/
[address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Mon Feb 4 15:52:06 CET 2019
Hi Martin, > I don't think that we have to change current policy at all. > > Current policy allows to get /22 divided to smaller blocks, so it doesn't have to be changed just because of this. > > My personal opinion on IPv4 exhaustion is that it would be better to come sooner than later. Any means of slowing exhaustion down would just prolong the IPv4 agony. Reaching zero free pool is the only way. Please look at the presentation I linked to and Daniel's comment. > Please stop trying to conserve any more IPv4 addresses, IPv4 has reached a dead-end, let it die peacefully. This is not about conserving IPv4 addresses. Sander
- Previous message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
- Next message (by thread): [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]