Re: HL7 Standards Process (was RE: EDIINT and HIPAA)
Terry Harding <[email protected]>
| Newsgroups | gmane.ietf.ediint |
|---|---|
| Message-ID | <00f701c05579$f43917c0$1dc40118@THARDINGLAPTOP> |
> Terry, > > > The packaging remains the same for either transport and returned MDNs > > also follow the same format, transport independant. > > I don't mean to nit-pick but I don't believe this is accurate. Didn't the > AS2 testers discover a problem with the To and From headers that are used in > AS1, that resulted in a "packaging change" to use AS2-To and AS2-From within > AS2. IMO, this means that AS1 and AS2 use DIFFERENT packaging, not hugely > different, but different. Would you agree? Dick, you are not nit-picking.... Yes, you are correct with the header issue. But lets look at the creation of a multipart/signed message. Step 1: Place payload inside a MIME body part Step 2: Place bodypart inside a S/MIME multipart/signed construct Step 3: Add transport dependant headers So during the creation of a message, I perform steps 1 and 2 the same way for either AS1 or AS2. Next i add the top level transport headers for SMTP or HTTP and send the message. The headers you referred to are actually top level transport specific headers. When i made the statement about the packaging being the same regardless of transport, i am referring to the actual MIME construct of the message. Transport specfic headers will vary from transport to transport. AS2 added AS2-To and AS2-From to the top level headers, but i still packaged the payload the same way. Terry Harding Cyclone Commerce