Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA14938; Fri, 5 Jan 1996 11:24:55 -0500 Received: by CS.UTK.EDU (bulk_mailer v1.3); Fri, 5 Jan 1996 11:24:23 -0500 Received: from vp.netgate.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id LAA14916; Fri, 5 Jan 1996 11:24:21 -0500 Received: from [205.214.160.43] (d14.netgate.net [205.214.160.46]) by vp.netgate.net (8.6.12/8.6.9) with ESMTP id IAA12217; Fri, 5 Jan 1996 08:41:00 -0800 X-Sender: dcrocker@ng.netgate.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 5 Jan 1996 08:24:15 -0800 To: Jacob Palme From: Dave Crocker Subject: Re: Name of RFC822 Cc: ietf-drums At 3:33 AM 1/5/96, Jacob Palme wrote: >not a great success, more and more IETF standards have textual >names. Example: SMTP, ESTMTP, HTML, HTTP etc. well, I like to claim that my primary contribution to the MIME effort was to convince Nathaniel and Ned of the importance of having a name. One likes to learn from one's errors... >RFC822 ought to have such a name now when its RFC number will >not be 822 any more. Some suggestions: The modern view is that 822 is about headers and mime is about content. I suggest that we enforce that distinction. Some possibilities: HIM (Headers for Internet Mail) HAS (Headers for Addresses and Structure) IMH (Internet Mail Headers) SHIM (Simple Headers for Internet Mail) I guess I vote for the last one. d/ -------------------- Dave Crocker +1 408 246 8253 Brandenburg Consulting fax: +1 408 249 6205 675 Spruce Dr. dcrocker@brandenburg.com Sunnyvale, CA 94086 USA http://www.brandenburg.com