A new Request for Comments is now available in online RFC libraries.


        RFC 1867:

        Title:      Form-based File Upload in HTML
        Author:     E. Nebel & L. Masinter
        Date:       November 1995
        Mailbox:    masinter@parc.xerox.com, nebel@xsoft.sd.xerox.com
        Pages:      13
        Characters: 26,726
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1867.txt


Currently, HTML forms allow the producer of the form to request
information from the user reading the form.  These forms have proven
useful in a wide variety of applications in which input from the user
is necessary.  However, this capability is limited because HTML forms
don't provide a way to ask the user to submit files of data.  Service
providers who need to get files from the user have had to implement
custom user applications.  (Examples of these custom browsers have
appeared on the www-talk mailing list.)  Since file-upload is a
feature that will benefit many applications, this proposes an
extension to HTML to allow information providers to express file
upload requests uniformly, and a MIME compatible representation for
file upload responses.  This also includes a description of a backward
compatibility strategy that allows new servers to interact with the
current HTML user agents.  The proposal is independent of which
version of HTML it becomes a part.  This RFC is the product of the
HyperText Markup Language Working Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
This memo does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute