Russ Cox
This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...
Does the NSS prefix need to be on every function, or is that implied by the x509roots package name?
We need x/crypto/x509roots/fallback, which has no API. Do we need to export a parser for NSS files? Or maybe the NSS parser should be x509roots/nss? Do we want to enable...
Spoke to @rolandshoemaker about this. We don't need to expose the parser in order to deliver the fallback package, but people had been asking for the NSS parser anyway, so...
Any thoughts on the suggestions in my previous comment, especially about x509roots not being the module boundary?
I agree that x/crypto/x509roots/fallback should be its own module; everything else is part of x/crypto.
Summarizing from above, the proposed API for golang.org/x/crypto/x509roots/nss is: ``` package nss // Constraint is a constraint to be applied to a certificate or // certificate chain. type Constraint interface...
Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group
No change in consensus, so **[accepted](https://go.dev/s/proposal-status#accepted)**. 🎉 This issue now tracks the work of implementing the proposal. — rsc for the proposal review group
These were coming in multiple times per day and have now stopped for almost two weeks. Closing.