Some more comments on components

Hi Marten,

Here comes a new day and some more comment on the component
management.

Let's assume the following configuration :

             ---AS2-----------AS1
                               !
             ---AS3------------!

AS1 is connected to AS2 and AS3  and cannot be used for transit
trafic. At a first stage the routes entries for AS1 are :

route:     193.0.8.0/24
origin:    AS1
component: 193.0.8.1/32 AS2
component: 193.0.8.2/32 AS3

route:     193.0.9.0/24
origin:    AS1

Then AS2 and AS3 start to agregate and that gives two entries :

route:     193.0.0.0/20
origin:    AS2
component: 193.0.0.0/23 HOLE
component: 193.0.8.0/23 AS1
component: 193.0.12.0/22 HOLE

and 


route:     193.0.0.0/20
origin:    AS3
component: 193.0.2.0/23 HOLE
component: 193.0.4.0/22 HOLE
component: 193.0.8.0/23 AS1
component: 193.0.10.0/23 HOLE

but on which entry are we going to put the old component stuff
(the interace IP address) ? On the first ? On the second ? On
both ? And from step to step we are going to end with objects
completly unmanageable. 


In the case of a dmzhost object this will not occur.

Gilles

         



-------- Logged at  Thu May 26 18:02:41 MET DST 1994  ---------