william(at)elan.net wrote:
Author/Change controller: IESG based on recommendation
of SPF Council
Related Information: SPF Council Website -
http://spf.mehnle.net/
What should it be changed to?
That is what I recommended it be changed to.
Co-opting the IESG under the "overview" of the SPF Council
smells like net suicide ;-) For a real world example see 3865:
o Author/Change controller: IETF
Since you want to submit this for standard track and not
experimental, having personal name/address there may not be
appropriate.
RfC 3864 says:
| Author/Change controller:
| For Internet standards-track, state "IETF". For other
| open standards, give the name of the publishing body
| (e.g., ANSI, ISO, ITU, W3C, etc.).
We're not yet at plan-B with full IETF liaison agreements etc.,
Jabber avoided this bureaucracy too so far. "IETF" should do.
Good catch - I've arranged write access on the corresponding
mailing list <ietf-message-headers.lists.ietf.org>, as soon as
Wayne fixed "Author/Change controller: IETF", other nits like
s/prefix/qualifier/g and the IESG publishes the "last call" we
can forward the registration template to this list.
It's not exactly crowded, see also...
<http://dir.gmane.org/gmane.ietf.message-headers>
...with two articles in the last six months ;-) Bye, Frank
P.S.: 21:47 * grumpy waves - 21:47 + 38 * Frank waves back