dkg

@kesara, thanks for testing it out and confirming that there is whitespace in some variants! Now that we have confirmed that the test is brittle, it sounds like we might...

To be clear, the reason that this is a problem is that the cryptographic signature on the message is broken.

I just tested another mail path to the archive, using the [email protected] mailing list from protonmail, and confirmed that from-munging is happening there too: https://mailarchive.ietf.org/arch/msg/ietf-smtp/C1r1ssVW21z3lpSJNV2swPy15z4/ This second message was unsigned,...

Yep, i am aware of the history of From munging and its relationship to mbox. If you have to from-munge because you're storing in mbox format, there are reversible ways...

thanks for digging into this, @rjsparks (and i'm sorry to see that one of your messages got bit by this too)! If this issue needs to be reassigned to some...

One thing to note is that some documents might only have a limited set of the bcp 26 keywords (e.g. a draft that asks only for SPECIFICATION REQUIRED but never...

[draft-ietf-openpgp-crypto-refresh](https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/) says: > The key words "PRIVATE USE", "SPECIFICATION REQUIRED", and "RFC REQUIRED" that appear in this document when used to describe namespace allocation are to be interpreted as described...

Hm, i hadn't realized it was such an idiosyncratic thing. If you think it's too unusual to be worth including in `kramdown-rfc`, feel free to close this issue. If you...

hm, so maybe the first thing would be to prod the xml2rfc folks to define a `` element?

ok, so it sounds like i'll need to put the labelling/tagging thing on hold (i've [indicated interest on the xml2rfc list](https://mailarchive.ietf.org/arch/msg/xml2rfc/lNfxTmujCXm9mp0c3on17uroyPQ/)), and maybe this issue can focus on the boilerplate...