FYI. This has been posted to Secdispatch, and I thought CBOR and COSE might want to take a look. (Feel free to reply to the original thread in Secdispatch, to keep the conversation in one place).
Francesca From: Secdispatch <[email protected]> on behalf of Yaron Sheffer <[email protected]> Date: Friday, 15 January 2021 at 15:54 To: "[email protected]" <[email protected]> Cc: "Keselman, Gleb" <[email protected]>, Yoav Nir <[email protected]> Subject: [Secdispatch] Ciphertext format draft Hi, we just submitted draft-sheffer-ietf-ciphertext-format-01 [1]. This is a CBOR-based set of headers for encrypted data, with the goal of enabling automation of large datasets that contain encrypted data, typically interspersed with plain data. Specifically we want to facilitate discovery of encrypted data (e.g., this database column contains ciphertext) and attributing this data back to the service that created the data and the key that was used to encrypt it. We received good feedback on the SAAG list to change from generic TLV to CBOR, which we implemented in -01. The authors would appreciate this list’s feedback regarding next steps. Thanks, Yaron [1] https://tools.ietf.org/id/draft-sheffer-ietf-ciphertext-format-01.xml
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
