On Tue 2021-01-26 11:11:19 -0500, Michael Richardson wrote:
Daniel Kahn Gillmor <dkg(_at_)fifthhorseman(_dot_)net> wrote:
> - To signal that we're in a "reset", we'll make a new draft,
> draft-ietf-openpgp-crypto-refresh, with Paul and Werner as editors.
> This new draft will be marked as a replacement for
> draft-ietf-openpgp-rfc4880bis-10.
> - crypto-refresh-00 (that is, the first revision of the new draft)
> will incorporate just the text of 4880 {PERIOD}, inconsequential
editorial
> updates, the verified errata of 4880, and incorporation of the relevant
> text from RFCs 5581 (Camellia) and 6637 (ECC), so all substantive
> changes from 4880 are things that have already been through the IETF
> document publication process already.
I suggest that -00 be just rfc4880 be just redo in modern XML.
We did that for RFC8514 (DHCPv6bis).
So, where I marked {PERIOD} above. Then let -01 be all the rest.
If the editors decide they want to make a -00 from rfc4880 itself, and
make -01 include the other stuff mentioned above, that seems reasonable
to me. crypto-refresh.md at git commit
9349ef2c0afe128e35a5172e9d41ed17619ca790 in the "step-by-step" branch on
https://gitlab.com/openpgp-wg/rfc4880bis would be a reasonable
candidate for a source for that version.
If you are using markdown, I also suggest that you start every new sentence
on a newline, as that makes the git diff process much easier.
yep, we're already doing that in the "simplifying-diffs" branch over at
https://gitlab.com/openpgp-wg/rfc4880bis
I agree that it makes the git diff much clearer, particularly for
multi-sentence paragraphs where changes show up in the beginning or
middle.
the "reflow" script in the git repo makes a number of assumptions about
an idiomatic markdown source -- if those assumptions are followed, then
it does adopt this newline-per-sentence approach.
--dkg
signature.asc
Description: PGP signature
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp