I think that the idea behind this draft is a good one but that the choice of
technology is wrong.
The template should be on a web site available for download and that the way to
get it there is the same as is used eg to get SMI TCs on to a website, namely
publish it as an appendix to an RFC, so the body of the RFC is a proper RFC,
formatted as usual, with the usual genuine comments to the RFC Editor, IANA etc
and the appendix is then labelled 'do not touch' as far as RFC Editor, IANA etc
are concerned and provides the material which will be loaded on to the website.
The Appendix would benefit from a convention so show that the sections therein
are at a second level, eg a marking or escape character before each section
head, which is removed when the Appendix is placed on to the web site.
The current approach of interleaving what will appear in the template, comments
thereon and the normal RFC material is likely to confuse all who come after.
Tom Petch
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf