Re: Current State: An EDIINT Short Status/ Request

[carl@xxxxxxxxx (Carl Hage)]

steveb@premenos.com (Steve Botts) writes:
: The handoff of data looks kind of like this for outbound EDI:
: 
: 	Business Application  
: 	    \/
: 	EDI Translator 
: 	    \/ 
: 	Security & Authentication Agent (Templar)
: 	    \/  
: 	Transport Agent 
: 	    \/		
: 	Internet

And expanding the middle part, we get:
 	EDI Translator 
 	    \/ 
	compression (content encoding)
	    \/
	character encoding (base64)
 	    \/
 	MIME header insertion
 	    \/
 	MIME Receipt insertion
 	    \/
 	Message signature and encryption, with MIME headers added
 	    \/
 	Message logging
 	    \/
 	Large message splitting
 	    \/  
 	Transport Agent 

It is straightforward to implement encryption code as a plug in, though
some standards might need to be developed, e.g. stdin, stdout, arguments,
and result code, for each implementation. (These standards don't need to
be part of the protocol definition.)

The key length is irrelevant to the standard, except that the protocols
might need the ability to include the secret parts of keys above 40 bits.
If the Pro-CODE legislation passes, export won't be a problem for the US.
--------------------------------------------------------------------------
Carl Hage                                              C. Hage Associates
<email:carl@chage.com> Voice/Fax: 1-408-244-8410       1180 Reed Ave #51
<http://www.chage.com/chage/>                          Sunnyvale, CA 94086