Re: [Secdispatch] Ciphertext format draft

Yaron:

How do you see AAD being used? 

Also, CMS carries a field that tells how to parse the plaintext (the content type) after it obtained by decryption.  I cannot tell whether that is useful or in you use case, but I can imagine places where it would be very helpful.

Russ

> On Jan 15, 2021, at 9:53 AM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
> 
> 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 <https://tools.ietf.org/id/draft-sheffer-ietf-ciphertext-format-01.xml>
>  
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org <mailto:Secdispatch@ietf.org>
> https://www.ietf.org/mailman/listinfo/secdispatch <https://www.ietf.org/mailman/listinfo/secdispatch>