Re: Weekly curated news stories about IETF-related topics

John C Klensin <john-ietf@jck.com> Fri, 16 October 2020 20:02 UTC

Return-Path: <john-ietf@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 D627B3A0AAF; Fri, 16 Oct 2020 13:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Ukb4HtX4kAqD; Fri, 16 Oct 2020 13:02:44 -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 503FF3A0AAE; Fri, 16 Oct 2020 13:02:44 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1kTVw2-00071f-Uq; Fri, 16 Oct 2020 16:02:42 -0400
Date: Fri, 16 Oct 2020 16:02:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Jay Daley <jay@ietf.org>
cc: ietf@ietf.org
Subject: Re: Weekly curated news stories about IETF-related topics
Message-ID: <41D26FC23141B40255CBE5DE@PSB>
In-Reply-To: <dd8f30df-892d-66a7-bfcf-1835c1903085@gmail.com>
References: <CE84EEA7A089318F95D685D3@PSB> <B68985BE-4A04-4257-BAFA-9921141883E5@ietf.org> <58D09C988522E7AA371F44CD@PSB> <dd8f30df-892d-66a7-bfcf-1835c1903085@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vAPco5E56d-ZOKVA9a0OTg5S7rM>
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, 16 Oct 2020 20:02:46 -0000

Brian,

Mumble.  Point conceded.  Thanks.
   john


--On Saturday, October 17, 2020 08:44 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> 
> John,
> 
> On 16-Oct-20 22:49, John C Klensin wrote:
>> 
>> 
>> --On Friday, October 16, 2020 21:48 +1300 Jay Daley
>> <jay@ietf.org> wrote:
>> 
>>> Hi John
>>> 
>>> Yes we are paying for this.  No there was no RFP as David is
>>> pretty much unique in this area. The cost is extremely small
>>> even with our time factored in and is independent of the
>>> number of subscribers so extending its availability to the
>>> entire community is the same cost as if we had kept it just
>>> for use by the comms team.  The cost is so small that we are
>>> well into micromanagement if the community needs to be
>>> consulted about a cost of this magnitude.   
>> 
>> Jay,
>> 
>> It isn't the cost (although I think I was legitimately curious
>> about that), it is the principle (actually several of them),
>> including:
>> 
>> (1) This appears to me to be an expansion of the role and
>> scope of the LLC, 
> 
> Respectfully disagree. RFC 8711 explicitly mentions "support
> outreach and communications" under "Executive Director and
> Staff Responsibilities". Previously I would have expected
> something like this to be done by ISOC, but itsm that we
> intentionally changed that.
> 
> Regards
>    Brian
> 
>> carried out without community consultation, much
>> less initiated from the community determining that it is
>> needed. Noting that one can get an unevaluated summary of
>> news items mentioning the IETf for free from multiple
>> sources, the concern about expansion of roles of the LLC and
>> the comms team, would be legitimate even if the comms team
>> decided it needed a curated news summary for its own internal
>> purposes, but that would at least not raise the issues under
>> (3) below.
>> 
>> (2) If there are costs involved and/or the work is being done
>> under a contract with the LLC, I believe that the principle is
>> that the LLC issues public RFPs and competes the activity.  I
>> haven't noticed an LLC policy that says that principle does
>> not apply if contracting or hiring is involved when the
>> amount is small or what that amount threshold is.  In
>> particular, if a hypothetical RPP were exposed to the
>> community, I believe (based on recent comments from others if
>> nothing else) there would be very strong input that
>> accountability for accuracy and means of giving feedback per
>> perceived errors or omissions be spelled out.  And that
>> brings us to...
>> 
>> (3) If this is going to be made publicly available, using an
>> IETF web site and IETF resources, the issues several others
>> have raised about accuracy and agreement about what things
>> mean apply.  Even if disclaimers are present, our publishing
>> one point of view rather than opening things up to at least,
>> e.g., letters to the editor/curator, implies a kind of
>> endorsement.
>> 
>> (4) We could debate whether David is the best person on earth
>> to do this (perhaps I would agree with you and the LLC that
>> he is) but he is by no means unique (if you believe he is, I
>> suggest that is a lack of due diligence).  There are
>> competitors to his other work (whether the LLC thinks they
>> are better or worse) and other people working in the general
>> area, some of whom are quite good.  Whether any of them would
>> be willing is a question whose answer cannot be determined
>> without asking, and you and Greg, speaking for and committing
>> the LLC as you have pointed out in other notes, have
>> apparently chosen to not ask.
>> 
>> (5) I may regret mentioning this, but there is also a
>> potential overlap here with publications that lie within the
>> scope of the RFC Series Independent Submissions Editor.
>> Noting that summaries of IETF and standardization activities
>> have been published in the RFC Series in the past, if someone
>> came to the ISE and suggested periodic publication of a news
>> summary (as an opinion piece by the person making the
>> suggestion and subject to editorial review), while I'd
>> predict the ISE would decline the opportunity for a number of
>> pragmatic reasons, it would not obviously be out of scope,
>> nor would it be out of scope for the ISE to recommend to the
>> LLC that it provide a stipend to the person doing the work
>> (again, without judging what decision would be made).  To the
>> extent to which we see the independent submission process as
>> supporting the IETF's standardization efforts (even or
>> especially when documents are published the criticize the
>> IETF's work and conclusions), the LLC is pushing the
>> boundaries of that principle as well.
>> 
>> As I have said to you in another context, the question is not
>> whether or not the LLC can do things like this, ignoring or
>> rejecting some or all of the principles above because we agree
>> that it can.  Whether it is wise, appropriate, or the best way
>> to serve the IETF and its objectives is another matter.
>> 
>> YMMD and probably will.
>>     john
>> 
>> 
>> 
>>