IETF Logo Mail Archive

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

"John R. Levine" <johnl@iecc.com> Wed, 09 June 2021 20:27 UTC

Return-Path: <johnl@iecc.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 BF58E3A24DF for <ietf@ietfa.amsl.com>; Wed, 9 Jun 2021 13:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com
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 VdNEreGpznx4 for <ietf@ietfa.amsl.com>; Wed, 9 Jun 2021 13:27:27 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BFB23A24DC for <ietf@ietf.org>; Wed, 9 Jun 2021 13:27:27 -0700 (PDT)
Received: (qmail 67303 invoked from network); 9 Jun 2021 20:27:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=106e4.60c1242d.k2106; bh=YGX7dZP5HXMg8N+k0g3Tn/XI/Jjcx0ArJwhMvGw4MHw=; b=m/rwngfaqT0CKjCN9TOZLoAd1d11D9raOyTz8mSAyGsnK9QfPgTSKp+3Fm09BuaIJ9Vt/R1YAwT+YoIgSwo6ZOiKkroXW67+cGvp/kqZQS23Dwpxstp5zs6Jh8WRL56GKCfi8xfB/4YT0FHCQbSBvNA6j0t3HW9Ci5KQL+vgMYQpGS88+P1Xv1oLKtlP1PwgNPIZTJ7ko/Zi7lODG/oyFOXLc2eO3Dn0czrQlTwQ2sEW6cphk0jUW/Y0RdA1glHfgXsJNnoPpAyKKKVCKMm7JPRnlMPcovyyrTnVr54R+wKNMvH4+aDTipAgu+BnGk3Qvep4al7pNgRogHywEPIt1Q==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 09 Jun 2021 20:27:24 -0000
Received: by ary.qy (Postfix, from userid 501) id 2ACAEE38A38; Wed, 9 Jun 2021 16:27:23 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id C5D10E38A17; Wed, 9 Jun 2021 16:27:23 -0400 (EDT)
Date: Wed, 09 Jun 2021 16:27:23 -0400
Message-ID: <a567a4a6-8aa0-1bf1-bf3b-18c71213fa@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF general list <ietf@ietf.org>
X-X-Sender: johnl@ary.qy
Subject: Re: The problem we could solve (re github etc.)
In-Reply-To: <CAMm+Lwhs0C80K2B4MoKi1ijghE2o6tmF7E8QreCK62P1bc9Q5Q@mail.gmail.com>
References: <DM4PR11MB5438CC6D84B301C907DAA6D1B5369@DM4PR11MB5438.namprd11.prod.outlook.com> <20210609163823.72897E1865D@ary.qy> <CAMm+Lwhs0C80K2B4MoKi1ijghE2o6tmF7E8QreCK62P1bc9Q5Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dgemD9w_-eTSDLiKJw5A6PLQ6Yc>
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 20:27:34 -0000

> 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.

I suppose for people who like this stuff it would make more sense to take 
a tip from wifi and arrange for pairing by pushing a button when you are 
physically next to the device.  There is probably some standards work we 
could do, something like a physical proximity profile for SASL.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email