-
-
If [TLSRPT](https://tools.ietf.org/html/rfc8460) serves the same purpose as the `report` field in the list, do we still need this field? Do they serve the same purpose? `TLSRPT` relies on DNS, but the…
-
I register multiple plugins which provide content parsers.
But only the content parser of the last registered plugin is recognized.
## 🐛 Bug Report
```
const parser = (fastify: FastifyInst…
-
Hi,
there could be an extra check for
_smtp._tls.example.org
Details:
the latest draft is available here:
https://tools.ietf.org/html/draft-ietf-uta-smtp-tlsrpt-23
and the IESG has already app…
-
Like we mention in the spec, policies can specify a reporting endpoint during their `testing` phase. Here's an issue to track progress on how we'll actually aggregate and send failure reports to those…
-
1. In "File Format", the example JSON no longer matches the description. For instance, there is no explanation of the `tls-policies` field.
2. There is no explanation of what `*.example.com` refers to…
-
I would like to suggest the following replacement for the Section 6.2 (Report Type):
OLD:
This document registers a new parameter "report-type="tlsrpt"" under
"multipart/report" top-level…
-
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
Substantive:
§1.1: There are at least a f…
-
Requiring that the selector have a particular name or name prefix associates semantics with selector names, of which there is none. It also requires the management (e.g., rotation) of more keys per do…
-
There is one minor issue with tlsrpt-18:
If you look at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-uta-smtp-tlsrpt-18
it is easy to see. The formatting immediately before section 5 got sq…