Jeremy Barton

I was thinking about this recently, too. I wondered if it might be (differently/also) useful to give it an initial buffer... not to say "start with these contents", but that...

> A completely separate idea would be to support one shot encoding for non-constructed items. Yeah. I think a more "natural" representation, given the static AsnDecoder type, would be to...

Explicit encodes as a SEQUENCE with one item, right? So it might need to know CER-ness, because I think CER might have to write an `EXPLICIT [0]` as ``` C0...

I don't think this'll land in 7; but marking it ready-for-review in 8. Let's take the AsnEncoder piece over to a new issue.

@richlander is usually involved in the flow for adding new distros to the graph. Rich?

Configuration options certainly empower users/administrators to make some blanket policy statements; but I think it's worth noting that signing and verifying have different policies applied to them. [NIST SP 800-57p1r5](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-57pt1r5.pdf)...

Some instances of this seem detectable, like having the rule say "if the exact clause I'm adding already exists, just ignore it". HashSet and sort the output to just rewrite...

@lindexi I'm not sure I follow. > 3. We use `_camelCase` for internal and private fields and use `readonly` where possible. Prefix internal and private instance fields with `_`, static...

`const` values are replaced by the compiler with their constant value, so if you look at generated output IL you'd see the literal `80`. `static readonly` means there's still a...

[Video](https://www.youtube.com/watch?v=kmTMJT4BMtw&t=0h0m0s) * We should add the overloads as presented, with a defaulted CancellationToken; but we need to remove the defaults from JsonSerializerOptions overloads to avoid the defaults making an ambiguous...