Re: [Secdispatch] Ciphertext format draft

[Yaron Sheffer <[e-mail]>]

We would love feedback from the CBOR community, but to clarify: we are merely using CBOR in the simplest way possible, we are not proposing any changes to it.

 

                Yaron

 

From: Francesca Palombini <[e-mail]>
Date: Friday, January 15, 2021 at 17:06
To: "[e-mail]" <[e-mail]>, Cose Wg <[e-mail]>
Cc: "Keselman, Gleb" <[e-mail]>, Yoav Nir <[e-mail]>, Yaron Sheffer <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: Re: [Secdispatch] Ciphertext format draft

 

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 <[e-mail]> on behalf of Yaron Sheffer <[e-mail]>
Date: Friday, 15 January 2021 at 15:54
To: "[e-mail]" <[e-mail]>
Cc: "Keselman, Gleb" <[e-mail]>, Yoav Nir <[e-mail]>
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