Re: Update of the MIME-MHS Specs
Keith Moore <moore@cs.utk.edu> Sat, 07 May 1994 00:36 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12762; 6 May 94 20:36 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12758; 6 May 94 20:36 EDT
Received: from survis.surfnet.nl by CNRI.Reston.VA.US id aa17782; 6 May 94 20:36 EDT
Received: from WILMA.CS.UTK.EDU by survis.surfnet.nl with SMTP (PP) id <10248-0@survis.surfnet.nl>; Sat, 7 May 1994 02:25:33 +0200
Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.9c-UTK) id UAA27430; Fri, 6 May 1994 20:24:10 -0400
Message-Id: <199405070024.UAA27430@wilma.cs.utk.edu>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Keith Moore <moore@cs.utk.edu>
To: Charles Combs <0003647213@mcimail.com>
cc: mime mhs <mime-mhs@surfnet.nl>, moore@cs.utk.edu
Subject: Re: Update of the MIME-MHS Specs
In-reply-to: Your message of "Fri, 06 May 1994 18:51:00 EST." <82940506235128/0003647213DB2EM@mcimail.com>
Date: Fri, 06 May 1994 20:24:09 -0400
X-Orig-Sender: moore@cs.utk.edu
> I suggest that the splitting and recombining messages is the wrong solution > to exchanging large messages. No matter how small you dice the message there > will always be a node or recipient who can't accept pieces and put them > together. Nobody thinks that message/partial is an ideal solution. It's designed for exceptional cases where the sender knows that the recipient *can* accept the pieces and put them together, and that the mail system *can* likely transmit the pieces and get them together intact (perhaps with some delay between sending each piece.) (maybe the next MIME RFC should make this very clear.) > I suggest that a better usage of store and forward messaging for large > information objects is to deliver knowledge about the information object to > the recipients and provide another communications channel for recipients to > retrieve the information object. > > Why can't we automate this manual process? Let's get the larger than 1MB > messages out of the store and forward path and make better use of our > resources. Uhhh...unless I completely misunderstand what you are talking about, MIME already has this capability. It's called message/external-body. Yes, it does get used a lot more often than message/partial. Keith Moore
- Update of the MIME-MHS Specs Steve Kille
- Re: Update of the MIME-MHS Specs Harald T. Alvestrand
- Re: Update of the MIME-MHS Specs Carl S. Gutekunst
- Re: Update of the MIME-MHS Specs David Herron
- Re: Update of the MIME-MHS Specs Carl S. Gutekunst
- Re: Update of the MIME-MHS Specs Carl S. Gutekunst
- Re: Update of the MIME-MHS Specs Ned Freed
- Re: Update of the MIME-MHS Specs Carl S. Gutekunst
- Re: Update of the MIME-MHS Specs Ned Freed
- Re: Update of the MIME-MHS Specs Charles Combs
- Re: Update of the MIME-MHS Specs Ned Freed
- Re: Update of the MIME-MHS Specs Keith Moore
- Re: Update of the MIME-MHS Specs Carl S. Gutekunst
- Re: Update of the MIME-MHS Specs Ed Switalski