In message <20051207210740.GD16891@bcd.geek.com.au>, Daniel Carosone writes:
>

>
>Vendors (especially in the wintel space) use "teaming" to mean all
>sorts of things, from purely link-state based NIC failover, to the
>STP-based teaming you can do with our bridge(4), through to LACP-based
>load-balancing like agr(4), and many weird and wonderful things in
>between.  Every server NIC driver implements its own framework, and
>changes behaviour and terminology between versions of that
>driver. Trying to figure out exactly what each version of a particular
>windows driver does for a particular configuration, so that you can
>configure the switch at the other end accordingly, can be intensely
>frustrating.
>
>What's worse, I've seen at least one vendor that uses the term
>"trunking" to mean this kind of configuration, rather than what
>everyone else, including our vlan(4), means by trunking.  And then of
>course there are vendors that beleive in doing more perverse things at
>the IP level, and then not implementing those properly anyway.
>

And in the PPP world, it's multilink.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb