Hi Pete, Hi all, To me it seems that you lost the core of my idea.
Richard was indeed talking about duplicate JSON tags (key-value pairs). The point is, that if we do not use key-value objects and instead transit to a flattened, sequential JSON array, there just can't exist any duplicate JSON tags in the data. A flattened array is also able to be parsed in predicable time. And mathematically it is nearly impossible to generate identical SHA-512 hashes from different data anyway. Regards, Timo It looks like Pete Resnick aimed to say: > On 14 Sep 2026, at 2:40, Timo Gerke wrote: > >> Hi Richard, >> hi all, >> >> Interesting, Richard. >> >> In message <[email protected]> you said >> >> "JSON schemas cannot forbid duplicate keys..." >> >> Since my idea does not save keys in the JSON data the duplicate >> key problem looks solved and the object nesting depth is solved >> in one go. > > Richard was referring to duplicate keys in the sense of key-value pairs, > not cryptographic keys. > >> As I suggested in my last mail, we should consider beleving keys in >> DNS. > > Again, the current spec does not keep any of the signature information > in JSON. It sounds like your concern simply does not apply. > > pr Timo Gerke Hamburg, Germany "If you think technology can solve your security problems then you don't understand the problems and you don't understand the technology." -- Bruce Schneier
OpenPGP_0x9F03DF9F597BF31E.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
