One would think that operators not updating filters to permit properly allocated space IS an operational issue. True, there are some non-operational facets to the issue, but that is not sufficient to call this off-topic... I can think of no better place than NANOG to say "Hey, some of you still have not updated your filters, I still do not have the reachability I should have.". His problem is indicative of future problems to come as we expand the use of previously unallocated IPv4 space. If the community cannot solve his problem, what reachability assurance do we have on any future allocations out of spaces with a similar history? James H. Smith II NNCSE NNCDS Senior Systems Engineer First Call Response Center The Presidio Corporation -----Original Message----- From: Michael.Dillon@radianz.com [mailto:Michael.Dillon@radianz.com] Sent: Friday, December 06, 2002 11:57 AM To: nanog@merit.edu Subject: Re: Operational Issues with 69.0.0.0/8...
My question is as follows - We are losing customers because of this problem. It is costing us reputation and money. It is out of our control. If you were us, what would you do? We have already asked ARIN to reassign us to a "friendlier" CIDR, and they refuse.
This is no longer a technical operational issue so it is out of scope for this mailing list. But if you think that ARIN could do something to solve your problem then you should raise the issue on the ARIN public policy mailing list. You can find subscription information for that list here http://www.arin.net/mailing_lists/index.html -- Michael Dillon
On Fri, Dec 06, 2002 at 12:14:51PM -0500, James Smith wrote:
One would think that operators not updating filters to permit properly allocated space IS an operational issue.
To quote a friend "public shaming will only go so far". At some point, you have to communicate to your customers and to the customers of the broken networks that the vendor shouldn't be used. This is one case where no attempt at finger-pointing could even remotely be made; when a customer/whoever protests, offer to conference in with $broken_network's technical people and have them admit they're broken. It's the same approach needed for fixing wildly random deaggregation. Actually *talking* to people works. I think I already pointed to the one hole that might be ARIN's problem to fix, but to be blunt about it... I wouldn't expect NO entry for properly activated/allocated space. Regardless if you choose the RIPE approach, the APNIC approach, or come up with a new one, the values returned for queries should at least differentiate from "space over which I have authority" and "space over which I do not have authority": prompt> whois -h rr.arin.net 69.0.0.0/8 % ARIN Internet Routing Registry Whois Interface % No entries found in ANS, ARCSTAR, ARIN, BCONNEX, % BELL, CANET, CW, FGC, KOREN, LEVEL3, POC, RADB, RIPE and VERIO database. prompt> whois -h rr.arin.net 70.0.0.0/8 % ARIN Internet Routing Registry Whois Interface % No entries found in ANS, ARCSTAR, ARIN, BCONNEX, % BELL, CANET, CW, FGC, KOREN, LEVEL3, POC, RADB, RIPE and VERIO database. prompt> -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE
participants (2)
-
James Smith -
Joe Provo