Re: StandICT.eu funding on offer
John C Klensin <john@jck.com> Fri, 07 May 2021 16:53 UTC
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F25D3A2768 for <ietf@ietfa.amsl.com>; Fri, 7 May 2021 09:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUCd29aFOyxJ for <ietf@ietfa.amsl.com>; Fri, 7 May 2021 09:53:45 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C013A2972 for <ietf@ietf.org>; Fri, 7 May 2021 09:53:45 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1lf3jU-000Ivv-ED; Fri, 07 May 2021 12:53:44 -0400
Date: Fri, 07 May 2021 12:53:38 -0400
From: John C Klensin <john@jck.com>
To: Pete Resnick <resnick@episteme.net>
cc: IETF <ietf@ietf.org>
Subject: Re: StandICT.eu funding on offer
Message-ID: <100CE9CF386142B15AD8098A@PSB>
In-Reply-To: <B7D400A7-C9BF-44C8-A864-C18A3818C235@episteme.net>
References: <412FE537-426A-4517-946A-B6F6A532F1B1@ietf.org> <907375A7-DCCE-4972-ACA9-D2C611BFCAB6@ietf.org> <CAA=duU1oyB6Ut17ECZweC1_NFx=Yj+okobxPPjW=zT8PobuqdQ@mail.gmail.com> <B7D400A7-C9BF-44C8-A864-C18A3818C235@episteme.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lipR8zcXzxPO2aQjhKT1cALjL8M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2021 16:53:51 -0000
--On Friday, May 7, 2021 10:26 -0500 Pete Resnick <resnick@episteme.net> wrote: > On 7 May 2021, at 10:14, Andrew G. Malis wrote: > >> I disagree about the charter call. The mailman description >> for the general IETF list is "This mailing list is for >> general topics of discussion relating to items within the >> IETF community. This is a public list for the IETF community >> to use. Any items posted are subject to the rules of BCP 78 >> and BCP 79." This posting certainly fits that >> description, it's very much of interest to the community. > > But it doesn't fit the IETF list charter, RFC 3005: > > Inappropriate postings include: > > - Announcements of conferences, events, or activities > that are not > sponsored or endorsed by the Internet Society or IETF. > > I'm not saying that we can't decide to allow postings like > this; it might be a very good thing. But we need to explicitly > make that decision, and explain why this one is OK and other > similar posts might still be problematic (if so). FWIW, I concur with Pete. If the "real" criterion is going to be "well, I think that is interesting and/or helpful or "the ExecDir gets to post these things but ordinary mortals do not".. well we just should not do things that way. Remember that rules like that came into being because of concerns about assorted trolls and event promoters creating excessive noise on the list. Even though that was clearly not the case with this announcement, allowing it without an explicit decision and clear rules invites abuse and endless debates about edge cases and whether a particular posting is appropriate. Two suggestions: (1) If the LLC considers if sufficiently useful and Jay and/or Greg think it is worth the time, put up a web page somewhere on which they, at their discretion, can post announcements that they think would be of interest to the community. If people could subscribe to a notification list that announces changes when they are made, so far the better (as long as that list is not ietf@ or ietf-announce@. People wanting to announce such an event could send the announcement to them and that would make whatever decisions are appropriate. [1] (2) Or, if the IESG thinks this is important enough, allow such postings as long as two ADs approve of it. Two to reduce possible pressure on individual ADs from their employers, professional affiliations, and friends, to reduce any possible doubt about motivations, and to make everything a tad more transparent. john
- StandICT.eu funding on offer Jay Daley
- Re: StandICT.eu funding on offer Jay Daley
- Re: StandICT.eu funding on offer Vittorio Bertola
- Re: StandICT.eu funding on offer Warren Kumari
- Re: StandICT.eu funding on offer Stephen Farrell
- Re: StandICT.eu funding on offer Andrew G. Malis
- Re: StandICT.eu funding on offer Pete Resnick
- Re: StandICT.eu funding on offer John C Klensin
- Re: StandICT.eu funding on offer S Moonesamy
- Re: StandICT.eu funding on offer Amelia Andersdotter
- Re: StandICT.eu funding on offer Carsten Bormann
- Re: StandICT.eu funding on offer Pete Resnick
- Re: StandICT.eu funding on offer John C Klensin
- Re: StandICT.eu funding on offer Michael StJohns
- Re: StandICT.eu funding on offer S Moonesamy
- Re: StandICT.eu funding on offer Vittorio Bertola