I was not questioning the function, only the requirement. It seems that if the problem exist between NAPNET and GENUITY, it might exist elsewhere and changing to the specific ASes would be a simple fix.
Are there cases where an AS macro would be really beneficial in the inet-rtr.rs-(in|out) statements?
Well, assuming you use as-macros as they were intended (to simply objects) .. it shouldn't be a problem. The code is obviously broken and Jake is fixing it. I assume that we could create another 2 macros listing every AS individually, but then that'd be more changes that'd we'd have to make every time we pick-up or drop an AS. I've removed AS-NAPNET from the AS-GENUITY macro until the problem is corrected.. -danny
Frankly, it's paranoia that causes me to only put specific ASes in the statements. While I'm willing to let an ISP tell me what ASes they are carrying, I want to know exactly with whom I'm exchanging routes.
I always thought of Randy as the conservative type, but maybe not as much as I. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634