Sanjaya,
O.k. Slightly disappointed no one with real experience
of routing space has voiced yet..
--- Sanjaya sanjaya@apnic.net wrote:
Dear colleagues,
In the forum, I was reminded that 'ensuring
routability' is not in accordance
with RFC 2050.
YAY!!
I believe that what we want is a standard process of
testing a newly allocated
block to help identify networks that are filtering
the new block, allowing the
concerned parties to contact these networks.
all due respect to those people who MAY get a bogon
assignment or allocation. BUT really, is this APNIC's
problem? and secondly - doesn't this just add to the
work a "concerned party" has to do?
To avoid the conflict with RFC 2050, perhaps it is
better if the objective is to
"test and promote" rather than "test and ensure"
routability.
Why not just "educate"! Routing issues like this
appear to be based on two painful facets.
1) IRR is not effective and therefor not widely used.
(why should I have to publicly announce my
business ' routing policies)
2) operators need to get off their high-horses and
accept that monolithic filters are dated!
Seriously, this is more about education and awareness
than spending buckets of members' money on testing and
emailing reports that no-one reads.
I dream of the day I might get to a NANOG, but it
strikes me that this where most of this bogon space
has issues.. Get APNIC to do presentation after
presentation at the routing aware conferences on how
to fix and re-learn route filtering. You will have an
inertia problem.. but you have to start somewhere.
I don't think that having the RIRs announce bogon
space to address a point issue is worthwhile.
-Jas.
--
Jas Webb
Send instant messages to your online friends http://au.messenger.yahoo.com
