Informational RFC-to-be: draft-laroche-ted-net-protocol-00.txt

[Harald Tveit Alvestrand <Harald.Alvestrand@xxxxxxxxxx>]

This draft is concerned with your subject area.
I think it should not be published as an RFC, and have told
the RFC Editor my opinion.
I will change this recommendation if the EDIINT group comes
out strongly supporting its publication.
What do you think?

                 Harald A
 
>Date: Tue, 3 Mar 1998 15:08:56 -0800 (PST)
>From: RFC Editor <rfc-ed@xxxxxxx>
>To: iesg@xxxxxxxxxxx
>Subject: Informational RFC-to-be: draft-laroche-ted-net-protocol-00.txt
>Cc: rfc-ed@xxxxxxx
>
>
>
>IESG,
>
>This RFC-to-be was submitted to the RFC Editor to be published as
>Informational: draft-laroche-ted-net-protocol-00.txt
>
>
>Two week timeout is initiated (17 March 1998).
>
> The Ted.Net protocol for messaging based business interchanges
>
>
>
>The Ted.Net protocol improves messaging systems while 
>being fully compatible with all of them.
>
>Ted.Net improvements bring to messaging systems' end users : 
>- large file transfers capabilities,
>- pretty good level of privacy,
>- integrity control of the transfered data,
>- time stamped proofs of the acceptance of data by the recipient.
>
>With the secure and stable services of Ted.Net, users can rely on 
>private or public messaging systems, SMTP, X400, or editors' 
>ones, to put on Electronic Data Interchanges (EDI).
>
>
>
>
>Sincerely,
>
>
>Alegre Ramos - USC/ISI
>Request for Comments Documents
>
>Voice: (310) 822-1511 x153
>Fax: (310) 823-6714
>EMAIL: RFC-ED@xxxxxxx
>
-- 
Harald Tveit Alvestrand, Maxware, Norway
Harald.Alvestrand@xxxxxxxxxx