Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: SLIP documents
Message-ID: <1991Feb13.063759.24753@Think.COM>
Date: 13 Feb 91 06:37:59 GMT
References: <1991Feb8.203703.25654@zoo.toronto.edu> <1991Feb11.233102.24222@Think.COM> <85079@sgi.sgi.com>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 21

In article <85079@sgi.sgi.com> vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:
>> 4.2BSD-based UDP implementations violate both these requirements.
>(I'm assuming you mean 4.3BSD base UDP implementations, which follow the
>rules you criticize, not 4.2 BSD.)

No, I meant 4.2BSD, since that is the release whose default value of
udpcksum is wrong.  Since the latest release of SunOS has this default
wrong, I assumed it is 4.2-based (but perhaps they changed the default in
the process of porting 4.3 TCP/IP, due to another of their misguided ideas
about backward-compatibility (the same misguidedness that causes them to
continue to default the broadcast address wrong)).  I'm not sure what the
latest Ultrix does, but I think 3.5 had the wrong default.  These are the
only BSD-based systems I have access to (we've got an SGI box, but it won't
let me login because it doesn't mount my home directory (I've never before
used a Unix system that didn't say something like "can't access home
directory, using /").
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar