![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Rick, I suspect you didn't read the important bit. > > it's not the memory. it's the processing power required which is quite > > non-linear. This is not to do with operational accidents. It's to do with generic growth. However, we should also engineer our systems to be robust during operational accidents. Brian Rick H Wesson wrote: > > randy, > > just because routers meltdown from leaks and mis-configurations is not a > reasonable justification for ARIN's tight policies on IPv4 allocations, > which kim stated earlier was to keep space aggrigated for router memory > requirements, adding speed and processing power to that definition still > does not justify the strict policy decisions. > > -rick > > On Tue, 7 Dec 1999, Randy Bush wrote: > > > it's not the memory. it's the processing power required which is quite > > non-linear. > > > > it's not the memory for the /24s in old b space, it's the horrifying *large* > > and *long* meltdowns caused by inadvertant leakage of bogus announcements of > > /24s in old b space > > > > randy > >
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.