Re: suggestion.

["Joshua Coombs" <jcoombs@xxxxxxx>]

> 3) MPPP has an archaic requirement that packets
> arrive in order. This requires front end queues
> similar to fragment processing, that is a waste
> of memory, cpu cycles and results in slowed
> connections, since all modern TCP stacks can
> handle out of sequence packets.
> 3) MPPP was designed for slow, dial-up lines (and
> ISDN). Per packet load balancing gives better
> performance in the real world, with lower CPU
> usage.

Actually, as a network engineer, there are times that guaranteed 
packet delivery order, across multiple 'bonded' links is a 
requirement.  While base TCP may tolerate out of order delivery, there 
are apps that ride ontop of it that cannot, such as VoIP.  MGCP 
sessions using G7.11 compression basically treat out of order packets 
as dropped packets.

Per Packet it good, but its not always the right tool for the job.

Joshua Coombs