North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: Problems with specific routing policies for each exchange point
- From: Abha Ahuja
- Date: Fri Oct 31 13:26:58 1997
It seems that this situation has brought up a lot of questions about the
use of the rs-in and rs-out lines with AS-MACROS. The goal of allowing
the AS-MACROS in these lines was the same as there use withing the as-in
and as-out lines. It makes things simple and convenient to administer...
improved functionality. Our code originally didn't do the error checking
for the AS-MACRO looping in the rs-in and rs-out lines (although with
RtConfig we caught it in the as-in and as-out lines). We will be making
the correct changes in the next few days.
If anyone has any more questions regarding these issues, please feel free
to contact me (or Jake).
On Fri, 31 Oct 1997, Danny McPherson wrote:
> > 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
> > 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: email@example.com Phone: +1 510 486-8634
abha ahuja firstname.lastname@example.org
Merit Network, Inc. 313.764.0294