Re: EDI Support in MIME

ANDERSON PAMELA DANIEL <anderson@tramp.colorado.edu> Tue, 12 May 1992 16:01 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa23991; 12 May 92 12:01 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa16133; 12 May 92 12:07 EDT
Received: from dimacs.rutgers.edu by NRI.Reston.VA.US id aa16114; 12 May 92 12:07 EDT
Received: by dimacs.rutgers.edu (5.59/SMI4.0/RU1.4/3.08) id AA04394; Tue, 12 May 92 11:54:12 EDT
Received: from tramp.Colorado.EDU by dimacs.rutgers.edu (5.59/SMI4.0/RU1.4/3.08) id AA04390; Tue, 12 May 92 11:54:09 EDT
Received: by tramp.Colorado.EDU id AA01829 (5.65c/IDA-1.4.4/CNS-2.1 for ietf-822@dimacs.rutgers.edu); Tue, 12 May 1992 09:53:45 -0600
Date: Tue, 12 May 1992 09:53:45 -0600
From: ANDERSON PAMELA DANIEL <anderson@tramp.colorado.edu>
Message-Id: <199205121553.AA01829@tramp.Colorado.EDU>
To: KLENSIN@infoods.mit.edu, anderson@tramp.colorado.edu
Subject: Re: EDI Support in MIME
Cc: ietf-822@dimacs.rutgers.edu

John,

I don't know a whole lot about EDI, but don't you think it has possibilities
even in the TCP/IP realm?  Could it be that users of TCP/IP networks might
have a need for EDI that could change the "issue in practice"?  

I take it, then, that there is not much interest in the Internet community
for EDI.

thanks,
pam