AS 690 aut-num progress (LONG!!!)

Curtis,

> There is one problem for which there is no way to express the
> requirement in ripe-181.  There is no way to specify an as-in line
> (which is required and has no means restrict to specific peers) and no
> way to specify that certain destinations are not accepted at all at
> some peers using interas-in or as-in lines.  This is need where we
> peer with someone at two interconnects, accept one as primary and
> don't accept the same set of routes from the other peering at all.

There is a hack Cengiz came up with:

Create a fake interas-in line for a non-existant interface, and give
that line the same policy as the as-in line.  (The current AS690 object
in the RADB does this using local IP 0.0.0.0/32).  That way any code
following the spec will say "Ok;  everything is accepted through the
non-existant interface;  I guess the other interfaces accept only
what they explicitly list".

--Dale
 



-------- Logged at  Fri Mar 17 20:10:04 MET 1995  ---------