There are differences in the architecture we use and the one they use. We
offload quite a bit from the central CPU.
>With a very small routing table and no filters I assume :-) I have seen
>the performance of a pm2 declining when increasing bandwidth and so at
>384kbps I switch but instead of going IRX I buy cisco since I also *NEED*
Ah - The PM-2R/eR and the IRX aren't really directly comparable. The memory
layout is very different as the 2R/eR has reserved room for existing or
potential analog/BRI ports. And there is code in the ComOS for the PM that
isn't in the IRX, etc. The IRX build is optimized for one thing - high
speed routing.
>classless routing, keepalives, custom and weighted fair queueing, isdn
>backup, clockrate, header and payload compression, ...
Fair enough. We don't pretend to do everything the Cisco's do.
>Now this gets interesting ... when will *WE* see it running ?
It is in alpha now, hopefully in beta for early '97. We have a fantastic
routing engineer who joined us this year from Cisco, he is the one who
finished work on OSPF and is doing the new protocols. That is what he is
primarily dedicate to. We're getting big enough to have more specialization.
>THEN those who have a working implementation of something capable of doing the
>job will set the standard and eat the cake.
We believe that we can turn features fast enough now that if the cataclysm
happens we will be able to respond. But really, there will probably be a
telegraph long before the final hour.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588