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] Bad Ideas in Address Policy
- 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 ]
Jim Reid
jim at rfc1035.com
Tue Feb 5 14:07:58 CET 2019
On 5 Feb 2019, at 12:25, Alexey Galaev <alex at vpsville.ru> wrote: > > Let check how many IPv4 not announce by BGP IP addresses can be used without them being routed on the public Internet. It’s also possible to make BGP announcements that tell lies. It’s not feasible for an RIR to recover address space from an LIR (unless the LIR voluntarily hands it over), assuming there was a suitable policy in place. Which there isn’t. > return 250.0.0.0/8 to the free pool That’s not going to help either. [Assuming we knew for sure there’s absolutely nothing deployed today that won’t fail or misbehave if that ~40 year old reserved address range was brought into use.] Activating 250/8 would just postpone the exhaustion point by a few months. And then we’d be back to where we are today. No matter what we do to conserve or reclaim IPv4 addresses, there simply isn’t enough of them. Our planet has 7-8 billion people and there are only 4 billion IPv4 addresses.
- 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 ]