here's as far we have got.

Marten ,

you write :

> * route:  193.0.0.0/20
> * origin: AS2
> * hole:   193.0.0.0/24
> * hole:   193.0.2.0/23
> * hole:   193.0.4.0/22
> * hole:   193.0.10.0/23
> * hole:   193.0.12.0/22
> * 

> * and 

> * 

> * 

> * route:     193.0.9.0/24
> * descr:     Enterprise 2
> * origin:    AS2
> * comm-list: SPECIAL
>
>But Gilles, how do I know what routes are actually being used and what
>not? According to the two route objects above, I would expect to see
>193.0.9.0/24 in my routing table, where the whole idea is that only
>193.0.0.0/20 is routed ...

I just wen to remind you the postulate :

  - A route is something that is present in the routing table of
    a router, belonging to an AS define in the routing registery, 

    somewhere in the Internet.
    ---------

Somewhere does not mean in your router that mean for example in
AS1 router. That has been clealy said by Tony in a previous mail :

Tony Message :

*Well yes and this paragraph is the important bit. Not the host route part
*as in practivce there would not be so many. But the important part of the 

*component infomration is what is used to make up a route (the only thing
*used in actual routing). Remember a route is a route seen somewhere
*in the Internet. A component is not.                      ---------

I know that the goal is to generate as big aggregat as we can but
for example as 193.0.0.0 has been granted to Europe does that mean
that the day when Europe will announce 193.0.0.0/8 to US all
subset of 193.0.0.0/8 will vanished from the routing registery ?
I cannot believe that.


Then you write :

>Again the problem is here that if AS1 has other (non-aggretable)
>routes there is no way to specify that the two more specifics are only
>relevant to the AS1 and AS2 and are not seen anywhere else. With
>components you can tell that these two are not seen specifically, but
>are used to make up the aggregate. I agree that components could be
>used in the config between AS1 and AS2 to derive the aggregate.

Again you are forgetting the postulate. And to tell the truth I will not
be in favor to generate config depending on an attribut so difficult
to manage.

Gilles



-------- Logged at  Wed May 25 17:21:34 MET DST 1994  ---------