This is a multi-part message in MIME format.
--------------15DA1EC34FF1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
If you want to use multipart/form-data, it's apparently
destined for standards track.
Larry
--------------15DA1EC34FF1
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Received: from alpha.xerox.com ([13.1.64.93]) by casablanca.parc.xerox.com with SMTP id <71841>; Wed, 7 May 1997 02:53:16 PDT
Received: from tyholt.uninett.no ([129.241.131.12]) by alpha.xerox.com with SMTP id <18061(6)>; Wed, 7 May 1997 02:53:11 PDT
Received: (from daemon at localhost) by tyholt.uninett.no (8.7.6/8.7.3) id LAA00912 for directorate-real; Wed, 7 May 1997 11:52:39 +0200 (METDST)
Received: from munken.uninett.no (munken.uninett.no [129.241.131.10]) by tyholt.uninett.no (8.7.6/8.7.3) with SMTP id LAA00905; Wed, 7 May 1997 11:52:31 +0200 (METDST)
X-Authentication-Warning: tyholt.uninett.no: Host munken.uninett.no [129.241.131.10] didn't use HELO protocol
X-Mailer: exmh version 1.6.7 5/3/96
From: Harald.T.Alvestrand at uninett.no
To: Steve Coya <scoya at ietf.org>
cc: iesg-secretary at ietf.org, moore at cs.utk.edu, directorate at apps.ietf.org
Subject: Re: Template for Masinter-form
In-reply-to: Your message of "Tue, 29 Apr 1997 08:08:22 EDT."
<Pine.WNT.3.96.970429080722.-103061D-100000 at dell06.cnri.reston.va.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 7 May 1997 02:53:27 PDT
Message-ID: <7059.862998807 at munken.uninett.no>
Sender: unknown at uninett.no
The IESG has approved the Internet-Draft "Returning Values from Forms:
multipart/form-data" <draft-masinter-form-data-00.txt> as a Proposed
Standard. The IESG contact person is Harald Alvestrand and Keith Moore.
Technical Summary
This specification defines an Internet Media Type,
multipart/form-data.
Its intended use is as a way of returning a set of values as the result
of a user filling out a form. Typical applications include form values
generated by HTML forms and submitted by HTTP post or by electronic mail,
but the format is independent of those contexts. The definition
of multipart/form-data is derived from its original definition
in RFC 1867, which was Experimental.
Working Group Summary
No basic objections have been raised.
Alternative methods have been suggested, but have not been
written up, so alternative technology does not exist at the moment.
Protocol Quality
The spec has been reviewed for the IESG by Harald T. Alvestrand
There are implementations; see the URL
ftp://ftp.parc.xerox.com/pub/masinter/file-upload-impl.txt for details.
--------------15DA1EC34FF1--