Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!julius.cs.uiuc.edu!apple!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: NeXT multi-media message file format
Message-ID: <896@toaster.SFSU.EDU>
Date: 17 Oct 90 00:59:09 GMT
References: <8263@milton.u.washington.edu> <9304@milton.u.washington.edu> <9314@milton.u.washington.edu>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 20

In article <9314@milton.u.washington.edu>
	mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes:
>In particular, there are magic cookies in the message header that have
>to be set up that are specific to the NeXT.  In particular, there is
>the Next-Attachment header line.  What RFC describes this?

The RFC describing Berkeley's Line Printer protocol wasn't issued
until August 1990, but no one seemed to have any trouble
implementing it and making it the de facto standard over the
years.  And vendors' "proprietary" methodologies have a funny way
of becoming standards when groups like OSF come along and pick
the "best" of what's out there.  Why NeXT isn't submitting stuff
like netinfo for consideration is beyond me.

NeXT has a pretty good track record for adherence to standards,
when such standards exist.  In the absence of standards, you
make them up as you go along.  That's an evolutionary process.
Meanwhile, you ship product.

					-=EPS=-