RE: MIME-based Secure EDI -- AS1

David,
	As you indicate EDIINT AS1 is not used for all EDI transported
over the Internet ... but just as important not all data being
transported via EDIINT AS1 is EDI data.  Here is my 2 cents...

	I believe the UCC asked for XML data to be used in the testing
of EDIINT AS2 to insure there was no marriage to X12 etc.  If neither
AS1 nor AS2 is married to EDI data, ideally the title of the
specification would not make such an inference.    In its broadest sense
EDI means "Electronic Data Interchange" which is fine ... but in common
usage EDI has come to be closely associated with X12 and readers assume
something called "EDIINT" cannot handle other data structures such as
XML.
	EDIINT AS1 and EDIINT AS2 are both "Secure Peer-to-Peer Business
Quality Data Transports".  Right?

-----Original Message-----
From: David Fischer [mailto:[email protected]]
Sent: Thursday, December 20, 2001 1:28 PM
To: [email protected]
Cc: Ned Freed; Rik Drummond
Subject: MIME-based Secure EDI -- AS1




After reading the comments from the Last Call on AS1, it seems there are
two
concerns:

1)  The name might suggest that all EDI on the Internet would be done
this way.

Solution:  Add the words Peer-to-Peer in the title.

2)  There is some dissent to the way in which security is applied in
this spec.

Solution:  Changing the security methods in AS1 would not align with the
original functional specification of this group.  Support for VANs was
not part
of the functional spec.  No change.

A new Draft IETF specification will be issued today with the change in
title as
in (1) above.

http://www.ietf.org/internet-drafts/draft-ietf-ediint-as1-15.txt

Best Regards,

David Fischer
Drummond Group.