-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frank Ellermann wrote:
Julian Mehnle wrote:
For the record, this was _entirely_ about the following: Wayne sent the
password for his #spf-council IRC bot through spf-private, and I
requested everyone to respond with their valid hostmasks so I could
configure my IRC bot with them.
Thanks for info. Does SPF-private now have a similar function like
iesg(_at_)ietf, i.e. read access restricted to Council members and write
access for everybody minus spam ?
No, not really. Generally all council business is supposed to be public.
The few things that are considered council business by the council, but
must be kept secret in the interest of the project, are handled on
spf-private. The IRC bot password and the individual council members'
hostmasks were considered to be in that category.
The council will always keep the openness principle[1] in mind. There
shall be no secret cabal.
But it could also make sense to use this private list as some kind of
"write only" device for any "private" stuff (like say quoting private
mails without prior permission of the author.)
I think that would be too lax a use of spf-private. Unauthorized quoting
can easily be substituted by paraphrasing. Only if the content is
competitive or its release otherwise strategically counterproductive,
would it be appropriate to use spf-private.
References:
1. http://new.openspf.org/Council_Resolution/8
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD5235wL7PKlBZWjsRAkJxAKDSgd2x5Ev7Pnivk/fqgAhhI6snogCePP0E
PU9xjCLJCtl4DgZAuo0xucU=
=kviC
-----END PGP SIGNATURE-----
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com