Re: [RRG] Thoughts on the RRG/Routing Space Problem

[Russ White <riw@cisco.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>> I'm not sure it would affect the current growth in the routing table
>> much. Lets review some of the basic characteristics of the situation:
>>
>> - Getting PI space is possible.
>>
>> - The cost of acquiring such space is negligible for organizations that
>> would be in a position to employ it; far, far lower than the cost of
>> equipment, for instance.
> 
> True, but it's decidedly non-zero.  

Certainly the cost of getting PI space is non-zero, but that's not the
critical cost. The cost to get PI IPv4 space is no-zero, as well--and
yet, that hasn't solved the "table size" problem.

The cost of getting space isn't, I don't think, the problem. IMHO, the
cost of deaggregating that space is zero. And I don't see anyplace where
the cost of deaggregating increases, hence, I don't see anything to stop
the current trend for larger table sizes.

Splitting the table into smaller pieces might make the problem go away
for a short period of time, but it will only prove to be a drop in the
bucket against the tide driving more granularity (state) into the network.

:-)

Russ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHVeIJER27sUhU9OQRAmWSAJ9MKb9A5zu0RxC32WcUy6g2fYB6jACdGRaj
r2ohjtkTCSgeQSxD/xR1YwM=
=1rL0
-----END PGP SIGNATURE-----

--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg