One clarification, A computer program should do this for the RFC Editor. I don't want to see even more manual processing steps introduced into this procedure. It should be pretty easy to derive a diff from the canonical XML source minus comments. I don't think that the RFC XML should contain comments by the way, looks like a covert channel to me. All manner of bad things could occur.
________________________________ From: John C Klensin [mailto:[EMAIL PROTECTED] Sent: Mon 26/11/2007 10:03 AM To: Eliot Lear; Paul Hoffman Cc: Working Group Chairs; Jari Arkko; IETF Discussion Subject: Re: Lets be careful with those XML submissions to the RFC Editor --On Monday, 26 November, 2007 11:21 +0100 Eliot Lear <[EMAIL PROTECTED]> wrote: > This argues that XML files be submitted as the authoritative > source at the time of WGLC, Paul, if they are going to be > submitted at all, and the I-D manager generates the text. I'm > fine with that, by the way. Eliot, I'd urge a little caution on this. I can't speak for others, but I tend to extensively annotate my working source extensively with comments about the source of a change, obsolete or alternate proposed text, proposals under discussion and what I think about them, etc. I generally consider that material confidential, especially when it responds to comments received off-list. I typically remove material of that type before handing the XML over to the RFC Editor but taking it out of the working drafts prior to WGLC or even prior to IETF LC (when some of it might be needed to review discussions of an issues and how and why it was resolved) risks the loss of important information. It seems to me that, regardless of whatever else we do, the RFC Editor should generate a document from the XML and compare it to whatever the IESG approved before going forward. Even if we insert other steps, that is probably a necessary precaution. I believe it is also sufficient, which makes it especially attractive. john
_______________________________________________ Ietf mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ietf
