<sigh>Not again. Hasn't this one managed to die
yet?
The myth was founded by lazy network admins back in the days when 10Base-T was the standard, 10Base-2 was just starting to take root and most people ran AppleTalk over daisy-chained 230k serial cables.
On large networks (> 100 systems or so) AARP (the element of AppleTalk that is responsible for most of the 'chattiness')
could consume a pair percentage of the
available 230kbps on the original serial cabling.
Even that traffic could be mitigated by implementing an AppleTalk router, and was further reduced in AppleTalk Phase 2, introduced in System 7 around 1996. That's 12 years ago.
In addition, due to the serial nature of AppleTalk, traffic from a system at one end of the network had to pass through every other node to get to a machine at the other end. This reduced overall throughput.
Modern networks have increased their bandwidth significantly. Even a 100Base-T network has 400 times the available bandwidth of the original serial implementation. Gigabit ethernet has 4,000 times the bandwidth. In addition, these networks are switched, which means that any conversation between two nodes is only sent down the wires leading to those specific nodes (and any intermediate switches).
So, the
minimal number of AppleTalk packets on the wire (remember, much of the chattiness went away in 1996), coupled with the switched nature of modern networks that are
vastly faster than the old serial cables means that a typical AppleTalk network consumes a
trivial amount of bandwidth. Really.
In terms of how to educate people nowadays, there are three things to point out:
1) AARP (and AppleTalk in general) is LESS 'chatty' than TCP/IP
2) AARP (and AppleTalk in general) is LESS 'chatty' than TCP/IP
3) AARP (and AppleTalk in general) is LESS 'chatty' than TCP/IP
(yes, you have to make the point three times)
If he wants further proof, run a
tcpdump from any node on the network and count the number of AppleTalk packets seen.
Then compare that with the number of ARP (Ethernet Address Resolution Protocol) packets.
Then compare
that with the number of NETBIOS packets.
If your network is so strained that the few AppleTalk packets are breaking it I suggest turning off all those Windows machines since NETBIOS generates
far more traffic than AppleTalk does.