Anna Weine

> The only things I know about PQC at the moment is that 1) it's implemented in TLS for Chrome, and 2) the keys are awfully big and 3) it...

Hi, If I understood the question correctly: We do use the id (like for the mentioned X25519MLKEM768 we use only the id - see here: https://searchfox.org/mozilla-central/source/security/nss/lib/ssl/sslt.h#263) for TLS/DTLS

> I'm not sure that this is the right way to build this. In NSS, we don't include the compressor. That's so that the integration is left to the using...

> Right. I imagine you would define a trait that defines the compression interface. Then the code would hold a `Box`. Is this what you meant? https://github.com/mozilla/neqo/pull/2592 I also wrote...

> @Frosne please run `cargo fmt` before pushing to fix formatting nits. Will do!

> Here's an idea for this that might make it a little nicer for decompression-only users: > > ```rust > pub trait CertificateDecompression { > const ID: u16; > const...

> Are we waiting on anything for this PR? Code changes by @Frosne or an updated review by @martinthomson? Me! I will get back to the patch as soon as...

> The reason I suggested the different spelling is that it allows using code to implement something without having to type `unimplemented!()`. It creates a guarantee that the code they...

> I think that the ~ideal interface is: > > ```rust > pub trait CertificateDecoder { > const ID: u16; > const NAME: &CStr; > fn decode(input: &[u8], output: &mut...

> > I still believe that we need to return a result after the decoding operation in order to transfer the information whether the decoding was successful or not. Same...