[cryptography] Introducing TDMX - Trusted Domain Messaging eXchange (Specification)

Peter Klauser pjklauser at gmail.com
Fri Sep 20 04:34:14 EDT 2013

TDMX is an application layer messaging protocol over HTTPS. The sending and
receiving agents (applications) are addressable with email addresses.
  billing at companyA.com sends an electronic invoice file to
accounting at companyB.com#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 billing at companyA.com can send to accounting at companyB.com#BillingAPI
   and companyB.com's administrator authorizes accounting at companyB to
receive from billing at companyA.com 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

On Fri, Sep 20, 2013 at 12:02 AM, shawn wilson <ag4ve.us at gmail.com> wrote:

> Per the purpose - this is to encrypt messages that generally traverse
> TCP/53 (zone transfer and the like), correct?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.randombit.net/pipermail/cryptography/attachments/20130920/5c886e93/attachment.html>

More information about the cryptography mailing list