[Diem] Re: architectural considerations document

[Felix Linker <[e-mail]>]

Hi Alex,

Thanks for that doc. I think what you describe quite closely matches how
our current prototypes work already (for reference
https://github.com/adem-wg/adem-proto)

We don't require DNSSEC, as it doesn't provide any additional security and
because authorization (and thus extra validation steps) are necessary
anyway.

I have some questions on your draft:

   - In your Sec. 5, you mention a hierarchical structure, and you say that
   this "hierarchy is effectively a Merkle tree of chains of trust." Is it or
   is it just "effectively" - and what does the word "effectively" do here?
   - You also mention that "[s]igned fields are included in a cryptographic
   hash of the record." So will that hash be signed? I don't think you mention
   that. And what's the benefit of signing the hash vs just signing the record?

Cheers,
Felix

Am Mo., 16. März 2026 um 10:04 Uhr schrieb Alex Rosenberg <
[e-mail]>:

> I pushed this document up to datatracker the other day in hopes to
> facilitate conversation. I foolishly assumed that the email list would be
> notified of new documents being published. My apologies for not sending
> this notification prior to today’s meeting.
>
> It primarily describes the mental model I’ve been forming of what DIEM
> might look like for the use cases we’ve already discussed.
>
> Digital Emblems - Architectural Considerations
> <https://datatracker.ietf.org/doc/draft-rosenberg-diem-architecture/>
> datatracker.ietf.org
> <https://datatracker.ietf.org/doc/draft-rosenberg-diem-architecture/>
> [image: ietf-logo-nor-180.png]
> <https://datatracker.ietf.org/doc/draft-rosenberg-diem-architecture/>
> <https://datatracker.ietf.org/doc/draft-rosenberg-diem-architecture/>
>
> Alex
> _______________________________________________
> Diem mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>