OK, this might sound like a trivial request but it really isn't. As you know, I am finishing the first release of what is now the third version of the Mesh architecture and I think I have it right this time because I have reduced the number of moving parts drastically. The Mesh now has three main parts: 1) An infrastructure that allows users to manage their devices by connecting them to a personal Mesh 2) An infrastructure that allows users to exchange credentials with other users using the trust validation criteria appropriate for the intended use. 3) An infrastructure that allows users to manage application configurations including but not limited to managing cryptographic credentials. This is all built on three new cryptographic primitives. 1) Uniform Data Fingerprints provide naming and addressing infrastructure. UDFs are not URIs but can be used to construct URIs. UDFs are used to represent cryptographic digests, nonces, keys and key shares. 2) DARE (Data At Rest Encryption) Messages: Are a JSON-ish equivalent to a PKCS#7 wrapper with support for the meta-cryptography used in the Mesh. UDFs are used for addressing type purposes. 3) DARE Containers: Are a sequence of DARE Messages and provide Blockchain type functionality for authenticity with incremental encryption capability. Containers are used as the basis for DARE Catalogs which contain sets of items, DARE Archives which are an encrypted file archive expressed as a DARE Catalog and DARE Spools which contain queues of tasks, messages. The problem I have come to is that I am now using the term message as a term of art to mean two different things in different parts of the same system. This did not matter when the terms were defined as DARE was an application built on top of the Mesh at that point. Now it is the platform on which the Mesh is built. And so there is a lot of scope for confusion. So what can I use as the name for a DARE Message? _______________________________________________ The cryptography mailing list cryptography@metzdowd.com https://www.metzdowd.com/mailman/listinfo/cryptography

On 6/13/19 9:58 AM, Phillip Hallam-Baker wrote: > [...] > > So what can I use as the name for a DARE Message? I like "DARE stub" and "DARE parcel." The DARE container may be a container of parcels or a box/crib of stubs. I would try to visualize something people are familiar with then extract that structure and its terms to the virtual structure of your protocol. Vide telegram, telegraph, radio, cable, wire, file cabinets, book shelves, smoke signals, pigeons, etc. Here are some possibilities: parcel - parcel packet - stub - entry - chit - post - page - leaf - card - message packet - word packet - communiqué - dispatch - dispatch packet - missive - record - imprint - transcript - correspondence - article - document - composition - broadcast Gonq ( https://cipher.icu ) _______________________________________________ The cryptography mailing list cryptography@metzdowd.com https://www.metzdowd.com/mailman/listinfo/cryptography

On 6/13/19 10:58 AM, Phillip Hallam-Baker wrote: So what can I use as the name for a DARE Message? > As I recently suggested for a project that was overloading "frame", "message", /et alia/: try an unrelated paradigm. As a musician, I suggested prelude, intro, verse, stanza, refrain, coda, outro, etc. Since this is a mesh, you might try electrical engineering topology terms, such as bridge (also a good music term), transform, etc. (I used transform in the original IPsec.) Memorable names are always helpful! _______________________________________________ The cryptography mailing list cryptography@metzdowd.com https://www.metzdowd.com/mailman/listinfo/cryptography