![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
IETF mailing lists are intended for OPEN discussion; the benefits
(cross-pollination between lists, lack of inhibition about stating
your opinions) are widely recognised as outweighing widely-accepted
drawbacks (e.g. Peter Lewis advertising every forum everywhere he can
think of, allisat going on yet another hallucinogen-induced trip down
memory lane).
midcom is not open. midcom should not be part of the IETF, much less a
working group.
No, I don't care that having a moderator-in-the-middle filtering
everything is in the spirit of the midcom charter and must be for my
own good. I _really_ don't like the concept of an IETF-approved
poster to a mailing list on an IETF-run server.
We can do our own filtering, if we choose to, and we don't need the
IETF to do it for us. Moderator approval of individual posters is
outside the spirit of RFC2418, and would require AD and IESG approval.
What are we coming to?
L.
<L.Wood at surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>
---------- Forwarded message ----------
Date: Thu, 1 Feb 2001 11:00:40 -0500 (EST)
From: midcom-admin at ietf.org
To: l.wood at eim.surrey.ac.uk
Subject: Mail sent to midcom
Your mail to 'midcom' with the subject:
Re: [midcom] WG scope/deliverables
Is being held until the list moderator can review it for approval.
The reason it is being held:
Only approved posters may post without moderator approval.
Either the message will get posted to the list, or you will receive
notification of the moderator's decision.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.