Policy Statement on Address Space Allocations

At 08:20 1996-01-25 -0500, Sean Doran wrote:
>
>> The same ISP has said publicly that they will route /19 prefixes in our
>> address space: 193/8 and 194/8.  The discussion is still going over
>> future /8s.  But read the last paragraph of the policy statement! 
>
>Sure, there is no filtering in 193/8 and 194/8,
>and as a result we have VERY poor aggregation.
>
>Consider this random cut-and-paste from 194/8.
>
>*  194.19.36.0      144.228.101.1          1     90      0 1239 701 3300
3301 5381 i
>*  194.19.37.0      144.228.101.1          1     90      0 1239 701 3300
3301 5381 i
>*  194.19.40.0      144.228.101.1          1     90      0 1239 701 3300
3301 5381 i
[etc. etc.]

Since, you have presented examples routed through 3300 I felt it was ok to
comment this. We have experinced that customers of ours sometimes later
purchased a connection from another ISP keeping the connection to us.
Therefor will all allocation of address space to that customer no longer be
aggregated by us. Even if we know that this customer in most cases has
customers of his own, we usually don't reserve blocks for him. Well, you see
the result in the routing table. I thought in the beginning of CIDR that I
would never had to announce anything but 194.16/13. For connectivity reasons
this is not possible.

The only solution might be that every network that later becomes an AS has
to renumber the complete network (and it's customers also). In addition to
that he has to become a Local Internet Registry with his own address space.
One AS, one registry....

/Hakan


-- Unisource Business Networks Sweden
-- Uniplus Internet Services * TIPnet NMC * Goteborg
-- phone +46-31-7708072 * fax +46-31-7114664
-- PGP: http://dojan.tip.net/hh/PublicKey.htm