On Sat, 30 Apr 2005, Frank Ellermann wrote:
wayne wrote:
no one remembered who did or why.
IIRC Mark or Julian. But maybe I confuse it, Mark promised
to investigate who added the obscure RfC editor note to -00.
So far I got no reply about it from the RfC editor. It was a Cc:
explicitly marked as "FYI", so I also don't expect an answer.
I've now also mentioned this issue on the general IETF list:
<http://mid.gmane.org/4272B65D(_dot_)10F0(_at_)xyzzy(_dot_)claranet(_dot_)de>
Somebody did this, and I'd like to know who, why, and when.
For those who need to be remined, this all concerns notes found in
https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=1599&filename=draft-schlitt-spf-classic
As I said before, I'm fairly certain the note was to RFC Editor and not
from and it must have come from somebody at IESG. If I have to guess, I'd
say probably Ted Hardie.
I base it on the fact that "RFC Editor Note" immediately follows custom
prepared announcement message ("DRAFT of message to be sent AFTER approval").
Following the announcement draft are additional sections of the information
for RFC Editor processing and that appears to include custom "RFC Editor
Note" and "IESG Note" and "IANA Note" (both of which are not filled). That
entire text was put together out of the template and that is why you see
it like that.
The announcements (when custom) are written for RFC Editor by either WG
(WG chair) or IESG and most often it is prepared by the AD listed as IESG
contact and in that announcement it is Ted Hardie. That is why I think
that section of text for RFC-Editor processing all together was prepared
by Ted Hardie and that "RFC-Editor Note" must have come from him.
I can't answer as to why, but my view of this is that it exceeds his
authority to have such a change (remove or change KEYWORD) done it all
by himself without previously having received an approval from the WG
(for WG document) or author of the document (but its possible such
approval did come as its only necessary to receive approval from one
of the authors).
--
William Leibzon
Elan Networks
william(_at_)elan(_dot_)net