cabo

xml2rfc of course croaks on ``` draft-eggert-tcpm-rfc8312bis.xml(302): Error: Did not expect element contact there, at /rfc/middle/section[4]/section[1]/section[1]/t[1]/em/contact ``` so you are probably looking at old html/txt.

Before 1.3.19, kramdown-rfc hoisted elements out of emphasis and section title spans. Now it leaves them in, which of course requires these elements to be allowed in the grammar, which...

Mysterious. Something went wrong when pushing 1.3.19, so I have replaced that with 1.3.20, but I didn't change anything that would cause this.

More mysterious. The change I made to use `` for `` is visible in your output; the change to `` isn't. (Maybe something else was botched in 1.3.19, but I...

Right now, the span-level contact is only allowed in ``, i.e. at top-level paragraphs in sections (and the block-level version directiy in sections). I haven't found a workaround yet. `...

That would need be a great feature. `` in RFCXML v3 is almost addressing this, but requires a numeric section reference. (There is also a "relative" attribute, but its description...

Interesting! I'll have a look at why there is no processing of section reference in the the link definition. (What is SEMANTICS? An RFC?)

Indeed, this would be some special processing we would add to convert_a. We already do special processing on targets starting with #. We probably would need to funnel the target...

1.6.3 has some very basic support for xrefs on the right hand side of link definitions. The effect may be somewhat surprising, so please play around whith that. The closest...

I'm not entirely sure what the objective is, but the XML looks good to me. The contorted markdown needed to generate this does not make me proud, but it seems...