Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!lanai.UUCP!ron
From: ron@lanai.UUCP (Ron Holt)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  An informal survey [slide-locks]
Message-ID: <9104301821.AA03299@Eyring.COM>
Date: 30 Apr 91 18:21:09 GMT
References: <9104301734.AA14557@ftp.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23

James B. Van Bokkelen writes:
> 
>>     You can e-curse him at seifert@asylum.sf.ca.us
> 
> He said he's sorry, and he can't go back in time and fix it, so I suggest
> that flames be directed to /dev/null, or the IEEE/ISO.  They're the current
> owner of the standard, and they seem quite willing to issue addendums long
> after the initial standard came out...
> 
> James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
> FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901

Yes, I realize this.  Perhaps I should have added a smiley face after
the last line of my message.  I thought it was clear from my quote that
the problem is recognized and it's not something that can be changed now.
Byte magazine mentioned his email address for reference and so did I in
my message.  I think most people would realize it would be rather pointless
to flame anybody now about this issue.  My only reason for posting my
message was to share with others some interesting insights into Ethernet
from Seifert's article.

Ron Holt	ron@Eyring.COM  uunet!lanai!ron
Eyring Inc.	+1 801-375-2434 x434