RFC 2295 on Transparent Content Negotiation (fwd)

[Marc Slemko <ma...@znep.com>]

---------- Forwarded message ----------
Date: Tue, 17 Mar 1998 15:31:49 -0800
From: RFC Editor <rf...@ISI.EDU>
To: IETF-Announce:  ;
Cc: rfc-ed@ISI.EDU
Subject: RFC 2295 on Transparent Content Negotiation


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


        RFC 2295:
 
        Title:      Transparent Content Negotiation in HTTP
        Author(s):  K. Holtman, A. Mutz
        Status:     Experimental
        Date:       March 1998
        Mailbox:    koen@win.tue.nl, mutz@hpl.hp.com
        Pages:      58
        Characters: 125130
        Updates/Obsoletes: None

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


HTTP allows web site authors to put multiple versions of the
same information under a single URL.  Transparent content
negotiation is an extensible negotiation mechanism, layered on
top of HTTP, for automatically selecting the best version when
the URL is accessed.  This enables the smooth deployment of
new web data formats and markup tags.

This document is a product of the HyperText Transfer Protocol Working
Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
It 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@IETF.ORG.  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 RFC-Manager@ISI.EDU.  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 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
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.