RFC 2936 on HTTP MIME Type Handler Detection

RFC Editor <rfc-ed@ISI.EDU> Wed, 27 September 2000 19:33 UTC

Message-Id: <200009271909.MAA11251@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2936 on HTTP MIME Type Handler Detection
Cc: rfc-ed@ISI.EDU, ietf-trade@lists.eListX.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 27 Sep 2000 12:09:16 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2936

        Title:	    HTTP MIME Type Handler Detection
        Author(s):  D. Eastlake, C. Smith, D. Soroka
        Status:     Informational
	Date:       September 2000
        Mailbox:    Donald.Eastlake@motorola.com,
                    chris.smith@royalbank.com, dsoroka@us.ibm.com  
        Pages:      13
        Characters: 25238
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-trade-mime-detector-03.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2936.txt


Entities composing web pages to provide services over the Hypertext
Transfer Protocol (HTTP) frequently have the problem of not knowing
what Multipurpose Internet Mail Extensions (MIME) types have handlers
installed at a user's browser.  For example, whether an Internet Open
Trading Protocol (IOTP) or VRML or SET or some streaming media handler
is available.  In some cases they would want to display different web
pages or content depending on a MIME handler's availability.  This
document summarizes reasonable techniques to solve this problem for
most of the browsers actually deployed on the Internet as of early
2000.  It is intended to be of practical use to implementors during
the period before the wide deployment of superior standards based
techniques which may be developed.

This document is a product of the Internet Open Trading Protocol
Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2936.txt"><ftp://ftp.isi.edu/in-notes/rfc2936.txt>

RFC 2936 on HTTP MIME Type Handler Detection RFC Editor