[Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission

[Carsten Bormann <[e-mail]>]

Public service announcement:

The, er, characteristic of the submission process explained below has been fixed during the pre-111 moratorium.
So, starting from yesterday, you can now directly submit the kramdown-rfc generated hybrid v3 XML as Internet-Drafts; no additional step via -3c is needed any more.
(The improvement of course also lets non-markdown drafts benefit that are edited directly in RFCXMLv2 or hybrid v3 XML.)

Thanks to the tools team!

Grüße, Carsten


>> With the --v3 (-3) flag, kramdown-rfc2629 produces XML that xml2rfc can process, and that --v2v3 can turn into the current version of v3.
> 
> … and if you want to submit this as an I-D, use
> 
> 	kdrfc -3c foo.md
> 
> and submit the foo.v2v3.xml *ONLY*.
> 
> (I’ll probably add API submission soon.)
> 
> Grüße, Carsten

[1]: <https://mailarchive.ietf.org/arch/msg/wgchairs/EikOARXSYfKz9-D-YLSjNaVN7MU>

 * Merged in [19242] from [e-mail]:
   Run v2v3 converter internally when v2 XML is submitted. Fixes #3305.  

(My more detailed description of the problem in
<https://mailarchive.ietf.org/arch/msg/ietf-and-github/-neyBKvA24nCKh1r2ELz4taGz7s>
contains a recommendation to do the v2v3 conversion locally before submission — this is of course still possible, but unless the I-D relies on a very recent xml2rfc fix that you have installed locally but may not have found its way into datatracker, no longer necessary.)