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] 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 ]
Daniel Suchy
danny at danysek.cz
Sun Sep 24 12:34:49 CEST 2017
I don't think. Even DNS operators (root and TLD) are normally using /24 for their anycast nodes - and DNS reachability is *critical* for internet operation. Also other services - like CDNs for Google, Facebook etc are using /24 - and yes, those *large* service providers are fragmenting their prefixes and increasing size of DFZ. In the past, /24 was *normally* used for PI allocations even in RIPE NCC region, and they're still active... If someone filters prefixes due to limited HW resources in his own equipmnet, he *always* has default route pointing to someone with full (unfiltered) BGP view, where final routing decision is made. It's a must, running network filtering /24 without default route pointing out to upstream is technical suicide. - Daniel On 09/24/2017 12:09 PM, Servereasy wrote: > as it could cause visibility/performance issues as lot of ISPs are filtering /24s.
- 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 ]