Cross-database AS-macro references

Tony,

I'm typing as fast as I can.

In message <199505111340.JAA19322 at lovefm.reston.mci.net>, Tony Bates writes:
> In theory yes  but it does raise the IRR thing again which I still
> dont see moving ahead to quickly 
> but anyway I am not sure what this buys unless ANS can really
> suport configs based on AS based plocies (even if this means mapping
> down to route in the implementation). 

As you have probably figured out from past mail on this list, the ANS
aut-num presented some fairly severe performance problems for some of
the tools.  This took a little time to fix.  There have been other
problems getting some of Merit's tools ported to our AIX config
generation box.  There shouldn't be portability problems with perl,
but some code has pathnames embedded and poor or no error message,
requires perl5 with both gdbm and ndbm and this combination hasn't
ported to AIX very smoothly.

A second problem is that the aut-num has been generated directly from
the PRDB.  We've been told by CANET (emphatically), RIPE, and MCI,
that the data in the PRDB is stale and that advisories should be taken
from the RADB.  This change in input source format hasn't been
accommodated in the code.

So much for the update.  Target date remains ... how about two weeks?

> It is nice to have a bunch of ASes to reference ANS
> customers by but if by this it means ANS will start implementing what
> they talked about doing which is using ripe-181 policy for
> configuration they have to get MEDs working. I know this is perhaps
> the wrong place to be spouting this but I still have not seen a
> concrete date as to when you will take advisories directly from us or
> anyone else for that matter and I'd rather see this happen than
> spending time on setting up AS-MACROs for ANS. I'm probably mixing
> issues here but things seem more than a little unclear as to when
> support of other RR will be put in place.

Sorry, we aren't ready to do MED yet.

For the majority of destinations fixed interchange preferences per
home AS works fine.  It works for the major COREN regionals.  It
doesn't work for MCI and Sprint direct connect destinations as well
without MED.  We know this and we know we have to fix it.

Sorry about the schedule slip.  I happen to be working long days and
weekends to try to get certain config tools transitioned from Merit
which is a prerequisite for the AS based aut-num if you want any sort
of testing before deployment.  You're just going to have to be a
patient a little longer.

Regards,

Curtis



-------- Logged at  Thu May 11 21:37:21 MET DST 1995  ---------