[address-policy-wg] 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Previous message (by thread): [address-policy-wg] 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Next message (by thread): [address-policy-wg] 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Ingvoldstad
frettled at gmail.com
Fri Sep 22 15:40:04 CEST 2017
On Fri, Sep 22, 2017 at 3:28 PM, Tom Hill <tom.hill at bytemark.co.uk> wrote: > The concern was that once the minimum size is a /24, as proposed, there > will be a need to permit /25 or /26 announcements to permit certain > traffic engineering strategies. Not that /22s will continued to be > disaggregated. Disaggregation to /24 is bad enough as it is, IMO. "Well, actually" This just means that "certain traffic engineering strategies" will no longer be viable for new entrants. -- Jan
- Previous message (by thread): [address-policy-wg] 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
- Next message (by thread): [address-policy-wg] 2017-03 New Policy Proposal (Reducing Initial IPv4 Allocation, aiming to preserve a minimum of IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]