Re: The problem we could solve (re github etc.)

John C Klensin <john-ietf@jck.com> Wed, 09 June 2021 21:22 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 725293A26AB for <ietf@ietfa.amsl.com>; Wed, 9 Jun 2021 14:22:30 -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 OOQH6e1H5Hz1 for <ietf@ietfa.amsl.com>; Wed, 9 Jun 2021 14:22:26 -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 E0CB83A26AD for <ietf@ietf.org>; Wed, 9 Jun 2021 14:22:25 -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 1lr5eX-000Nwf-FK; Wed, 09 Jun 2021 17:22:21 -0400
Date: Wed, 09 Jun 2021 17:22:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: "John R. Levine" <johnl@iecc.com>
cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF general list <ietf@ietf.org>
Subject: Re: The problem we could solve (re github etc.)
Message-ID: <494082D95C1883FD462E6307@PSB>
In-Reply-To: <a567a4a6-8aa0-1bf1-bf3b-18c71213fa@iecc.com>
References: <DM4PR11MB5438CC6D84B301C907DAA6D1B5369@DM4PR11MB5438.namprd11.prod.outlook.com> <20210609163823.72897E1865D@ary.qy> <CAMm+Lwhs0C80K2B4MoKi1ijghE2o6tmF7E8QreCK62P1bc9Q5Q@mail.gmail.com> <a567a4a6-8aa0-1bf1-bf3b-18c71213fa@iecc.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/LFVa53aZ4HeocvNrXBJvwd8Tl74>
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: Wed, 09 Jun 2021 21:22:31 -0000


--On Wednesday, June 9, 2021 16:27 -0400 "John R. Levine"
<johnl@iecc.com> wrote:

>> 1) Connecting to Ring doorbell on my phone ...
> 
>> Log into my Nest account on the Web, get bounced to Google
>> accounts to log in. Can now view the status of my thermostat
>> but not the status of my doorbell because the whole point
>> here is making people dependent on subscription services. ...
> 
> I have a dandy thermostat powered by two AA batteries that
> makes it warmer in the morning and cooler in the evening.  (We
> don't have central A/C.) It cost under $20.  My father's house
> had a Nest which I found to be worse in every way, harder to
> program, didn't do what I wanted, cost ten times as much.
> Fortunately, I do not live the kind of life in which it would
> be imoportant to change the heat schedule when I am not in the
> house.

So, probably because my circumstances are different, I've got a
few Internet-connected thermostats.  They are connected over
wired Internet, not WiFi, and with PoE, eliminating the need for
AA batteries.  The company that sells them, well, sells them --
without a business model that depends on selling subscriptions
or tracking my behavior to either target me with ads or selling
data about to others.

So, there are choices.

And I have a question: What does this rather long thread
actually have to do with the IETF other than demonstrating that
it would be dumb for our discussions to depend on a providers
who intended to support those discussions by selling
subscriptions and/or tracking user behavior and/or comments?
"Dumb" if only because separating those who would be comfortable
with such arrangements from those who would not would almost
certainly reduce our range of perspectives and participants.

And that distinction ignores whether I should be banned from a
list for some period of time because I suggested that a proposal
--one that I don't think anyone has really made-- would be dumb.

   john