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/ncc-services-wg@ripe.net/
[ncc-services-wg] Re: [address-policy-wg] New Draft Document: De-boganising New Address Blocks
- Previous message (by thread): [ncc-services-wg] RE: [address-policy-wg] New Draft Document: De-boganising New AddressBlocks
- Next message (by thread): [ncc-services-wg] Re: [address-policy-wg] New Draft Document: De-boganising New Address Blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Lenz
slz at baycix.de
Tue Feb 24 17:39:53 CET 2004
Hay, Michael.Dillon at radianz.com wrote: >>The RIPE NCC has prepared a draft document titled "De-Bogonising New >>Address Blocks": > > > That is a misleading title. [...] > The real solution to this problem is to make it > possible for ISPs to closely track RIR allocations > in their filters in a semi-automated way. There may > still be a few days of delay before a new allocation > is fully routable but ISPs can compensate for that > with internal processes. > > Why can't ISPs subscribe to a feed of all new > RIPE allocations in near real-time? the problem never were the ISPs which do their job and follow the new RIR Allocation and Smallest Prefix Size Announcements. The problem always are those ISPs with dummy admins who just took some bogon template from some cool looking BGP configuration website and never update them at all, don't read RIR-mailinglists or things like NANOG-list and/or just don't care. (...and so on). I don't think a technical solution helps against this problem at all since only those ISPs who already care about their filters would use it, and there certainly will be some ISPs who don't want to pass the control about their filters to some 3rd party. ==> The only reasonable solution for now is just what's RIPE trying to do, look into the routability itself and kick all those who haven't updated their filters in time. That's a bit unfortunate since RIPE usually shouldn't have to do much with routing-issues in the first place, but actually i like that idea of THEM doing that. It's a benefit for all LIRs so it's a nice idea in my eyes. I'm currently quite amused watching some collegues of a customer of us trying to track down all unreachable sites and reach their admins for about two months now, especially since they already started putting end-user el-cheapo-DSL customers in their nice new 83.x.x.x IP-block which are the worst of all customer-types you can possibly get. I don't really want to experience that myself some day. Fortunately i could avoid playing early-adoption betatester for newly Allocated /8s up to now :) . o O(and then there was this big(?) european Telco/ISP still filtering AS-numbers >30000 up to some weeks ago :-) ) -- ======================================================================== = Sascha 'master' Lenz SLZ-RIPE slz at baycix.de = = NOC BayCIX GmbH = = http://www.noc.baycix.de/ * PGP public Key on demand * = ========================================================================
- Previous message (by thread): [ncc-services-wg] RE: [address-policy-wg] New Draft Document: De-boganising New AddressBlocks
- Next message (by thread): [ncc-services-wg] Re: [address-policy-wg] New Draft Document: De-boganising New Address Blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]