Randy Bush wrote: >> Gert Doering wrote: >> Also, it might lead to deaggs (Markus' case) where a /14 that was >> originally "in one LIR" would be "3x /16, plus some smaller fragments >> in the LIR" and "lots of /24 PI managed by the NCC" now - so the /14 >> won't get a ROA, and he'll have to announce more-specifics. > > lemme see if i get this. to have the owner registration correct, some > address space will have to be broken up and owned by multiple IRs, thus > fragmenting routing? i like correct registration, but the commons has > become pretty polluted
Well, my example was for a /16 (not the /14, which comes with another story), currently announced by the LIR as /16 and partially as /17, with 6 smaller ranges announced by another entity of this LIR and 23 PIs announced out of 38 (so much for "accuracy" ...) by other ASes. Breaking up the /16 into PIs and PAs would end up with 42 new prefixes in the routing table (beside the current 3+6+38 seen ones). OTOH, at least the 23 announced prefixes would become PIs as the others (50€ for the LIR or a direct agreement with RIPE) and the remaining 15 PIs would be either returned or registered as the rest. @Ingrid: Have you made an analysis, how many new prefixes would show up in the routing table by de-aggregation the A-PI/A-U allocations (best case/ worst case), how many of the PIs in there are currently seen (or not) as separate announcement? Just to get a feeling ... (yes, everyone can do this, but everyone is busy ... ;-). Markus -- Darmstädter Landstrasse 184 | 60598 Frankfurt | Germany +49 (0)178 5352346 | <[email protected]> | www.kpn.de KPN EuroRings Germany B.V. | Niederlassung Frankfurt am Main Amtsgericht Frankfurt HRB99781 | USt.IdNr. DE 815496855 Geschäftsführer Jesus Martinez & Jacob Leendert Hage
