North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: Operational Issues with 184.108.40.206/8...
- From: James Smith
- Date: Fri Dec 06 12:20:02 2002
Title: RE: Operational Issues with 220.127.116.11/8...
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
From: Michael.Dillon@radianz.com [mailto:Michael.Dillon@radianz.com]
Sent: Friday, December 06, 2002 11:57 AM
Subject: Re: Operational Issues with 18.104.22.168/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