Derek Atkins wrote:
The problem is that it's the TXT that's approved, not the XML..
This whole thread is about making sure that the XML received by
the RFC Editor matches the Text that was approved by the IESG.
Starting with what was approved necessarily means ignoring the
XML and starting with the TXT, unless they validate that the
XML generates the approved TXT.
Right.
My own question is: Is it the job of the RFC Editor to verify that what is
published matches what the IETF approved?
I think it shouldn't be, in that quality control on IETF-approved documents
belongs in the IETF, not the publication operator.
The RFC Editor needs a control point within the IETF that asserts that the
submitted document is the right version.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf