Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!jbreeden
From: jbreeden@netcom.COM (John Breeden)
Newsgroups: comp.sys.novell
Subject: Re: IPX corruption possible across routers
Message-ID: <1991Jun8.025601.13098@netcom.COM>
Date: 8 Jun 91 02:56:01 GMT
References: <1991Jun3.212342.4603@npd.Novell.COM> <1056@rsp.UUCP> <1991Jun7.185359.659@npd.Novell.COM>
Organization: Netcom - Somewhere in the S.F. Bay Area
Lines: 20

In article <1991Jun7.185359.659@npd.Novell.COM> timm@Sed.Novell.COM (Tim Myers) writes:
>In article <1056@rsp.UUCP> tom@rsp.UUCP (Thomas Ruf) writes:
>The implementors of IPX thought differently about how CPU cycles should
>be spent--checksums are ignored. The designers of AppleTalk also thought 
>differently--checksums are optional. 

Big difference between CAN'T do and optional. At least Apple was smart
enough to make it optional. I guess this is a case of Novell being right 
and every other NOS implementation being wrong. It's easy to under-
stand when you realize this is the same company that brings us a 802.2
header with the SAPs set to ff's and a 802.3 frame on broadband with the
lenght field set to 00 (-:

-- 
 John Robert Breeden, 
    jbreeden@netcom.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
 -------------------------------------------------------------------
 "The nice thing about standards is that you have so many to choose 
  from. If you don't like any of them, you just wait for next year's 
  model."