Questions about RFCs 1494, 1495.
Justin Ziegler <Justin.Ziegler@inria.fr> Fri, 03 June 1994 08:16 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00495; 3 Jun 94 4:16 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00491; 3 Jun 94 4:16 EDT
Received: from survis.surfnet.nl by CNRI.Reston.VA.US id aa01149; 3 Jun 94 4:16 EDT
Received: from concorde.inria.fr by survis.surfnet.nl with SMTP (PP) id <02321-0@survis.surfnet.nl>; Fri, 3 Jun 1994 10:03:35 +0200
Received: from chandon.inria.fr (chandon.inria.fr [128.93.2.8]) by concorde.inria.fr (8.6.9/8.6.9) with SMTP id KAA24927; Fri, 3 Jun 1994 10:03:25 +0200
Received: by chandon.inria.fr; Fri, 3 Jun 1994 10:03:10 +0200
Message-Id: <199406030803.AA05563@chandon.inria.fr>
To: Harald.T.Alvestrand@uninett.no
Cc: wg-msg@rare.nl, mime-mhs@surfnet.nl
Subject: Questions about RFCs 1494, 1495.
Date: Fri, 03 Jun 1994 10:03:09 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Justin Ziegler <Justin.Ziegler@inria.fr>
Harald, 1) RFC 1494 defines: - mime-postscript-body, - mime-jpeg-body, - mime-gif-body, why not also define: - mime-partial-body, - mime-external-body, - mime-richtext-body, - mime-audio-body, - mime-mpeg-body. ? Later one would also have to define many others... 2) Would it not be a good idea to put in the mime-postscript-body, and in the mime-jpeg-body, and in the mime-gif-body a big parameter field like in the mime-body-part (except the content-type). This enables the mapping of content-description and all the other header fields. ? Justin & Vira
- Questions about RFCs 1494, 1495. Justin Ziegler
- Re: Questions about RFCs 1494, 1495. Ned Freed
- Re: Questions about RFCs 1494, 1495. Ned Freed
- Re: Questions about RFCs 1494, 1495. Carl S. Gutekunst
- Re: Questions about RFCs 1494, 1495. Ned Freed
- Re: Questions about RFCs 1494, 1495. Paul Rarey
- Re: Questions about RFCs 1494, 1495. Carl S. Gutekunst
- Re: Questions about RFCs 1494, 1495. Ned Freed
- Re: Questions about RFCs 1494, 1495. Paul Rarey