On Fri 2021-02-05 16:17:56 -0500, Derek Atkins wrote:
The ToC doesn't include anything beyond x.y.z,
Does anyone have a strong preference about the level of depth of the
sub-sub-sections included in the ToC? I think limiting to x.y.z is just
an artifact of the current toolchain we're using, though i can see how
comparing the ToC directly between this and RFC 4880 might be a
nice-to-have convenience.
I've asked Carsten on github if there's a way to adjust the depth of the
ToC from markdown:
https://github.com/cabo/kramdown-rfc2629/issues/99
I don't think we should block on this, but if Carsten (or anyone else)
points to a straightforward way to change tocDepth to 4, i wouldn't
object to applying it to the crypto-refresh draft.
--dkg
signature.asc
Description: PGP signature
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp