[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 ]
Jetten Raymond
raymond.jetten at elisa.fi
Mon Feb 4 14:32:54 CET 2019
Hi Sander, The current policy does not become useless: "In case an allocation of a single /22 as per clause 1 can no longer be made, multiple allocations up to an equivalent of a /22 in address space will be made to fulfill a request." is in the current proposal. Rgds, Ray -----Original Message----- From: Sander Steffann <sander at steffann.nl> Sent: 4. helmikuuta 2019 15:29 To: Jetten Raymond <raymond.jetten at elisa.fi> Cc: Marco Schmidt <mschmidt at ripe.net>; address-policy-wg at ripe.net Subject: Re: [address-policy-wg] 2019-02 New Policy Proposal (Reducing IPv4 Allocations to a /24) Hi Raymond, > To make it more clear what I mean, a /24 will not be enough to connect a say /29 IPv6 to the v4 world, a /22 ( or any range of addresses up to a /22 in size ) is not enough either. Therefore I support the current policy, and am against the new proposal. Can you please explain how you see that? This proposal only deals with the situation *after* the current policy becomes useless... Cheers, 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 ]