TDMX is an application layer messaging protocol over HTTPS. The sending and receiving agents (applications) are addressable with email addresses. Example: [email protected] sends an electronic invoice file to [email protected]#BillingAPI - there is end2end encryption on the message sent between the two agents - messages are relayed between each agent's service providers who cannot decrypt the message contents - there is mutual authorization from companyA.com's administrator that [email protected] can send to [email protected]#BillingAPI and companyB.com's administrator authorizes accounting@companyB to receive from [email protected] via BillingAPI service. - interoperability is achievable through the use of WSI-compliant SOAP-WebServices for all point2point interfaces. Granted not the most efficient protocol choice - but the goal of interoperability is much more important in this EAI space.
If you're interrested, the chapter on "Motivation" provides some insight into why this can be more convenient than using SFTP or straightup PGP for EAI. Regards,Peter. On Fri, Sep 20, 2013 at 12:02 AM, shawn wilson <[email protected]> wrote: > Per the purpose - this is to encrypt messages that generally traverse > TCP/53 (zone transfer and the like), correct? > >
_______________________________________________ cryptography mailing list [email protected] http://lists.randombit.net/mailman/listinfo/cryptography
