CIDR deployment

Thu Mar 17 18:38:53 UTC 1994

Erik-Jan,

> NET           ASN       REGIONAL              COUNTRY        RESULT
> ------------  --------  --------------------  -------------  ---------
> 133.11.0.0    AS372(?)  NSN-AMES-AS(?)        Japan          Unreach
> 128.250.0.0   AS372(?)  NSN-AMES-AS(?)        Australia      Unreach

This is not actually NSI's problem, it is caused by the fact that the
NSFnet has not been configured to accept 192.87.111/22 and hence is
not carrying it.  The confusing part is that connectivity through
there to most places still works because the NSFnet has a default
route pointing at Washington2.Dante.net, which runs without route
filters.  What this breaks, however, is that since NASA doesn't default
to anyone they won't be able to reach anything which isn't explicitly
announced to them, but we don't have the route to send to them.

At the current state of the art, then, you really need to have the
aggregate configured into the NSFnet database before this will work
well.  We should also consider pulling the default route from
the backbone, it is in principle no longer needed and causes no end
of confusion about where the problems are occurring.

Dennis Ferguson