Re: The problem we could solve (re github etc.)
Phillip Hallam-Baker <phill@hallambaker.com> Wed, 09 June 2021 21:48 UTC
Return-Path: <hallam@gmail.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 E50393A276E for <ietf@ietfa.amsl.com>; Wed, 9 Jun 2021 14:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 v6Z5xdXGz5rZ for <ietf@ietfa.amsl.com>; Wed, 9 Jun 2021 14:48:43 -0700 (PDT)
Received: from mail-yb1-f171.google.com (mail-yb1-f171.google.com [209.85.219.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A72C3A27A2 for <ietf@ietf.org>; Wed, 9 Jun 2021 14:48:43 -0700 (PDT)
Received: by mail-yb1-f171.google.com with SMTP id p184so37612632yba.11 for <ietf@ietf.org>; Wed, 09 Jun 2021 14:48:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bidznCYJePndMu+f49YXG1GL9sSioquuBFWJ+gmu2Bg=; b=aifOTCjOiFev027JTlptIbGJiBMLvcjIInFddcepbjfn+CVt62wMSDnL7NURRluy9P LJjdI+BFQt1Fgs8/SVJD0oK85/JXbemUoFuNpw0qgjWqDMxv0YbZvtbe9mtTj2+EG2I2 gTjhDoWF+AkWDxZM2rqLFPk7eamMoby7OghXbFhYVanpmJrthYSTQW9+rGb2FSVU3TJy TwoC05MT6u/tf/oMPih67h5Iv3vKIezwjvm+OJRBolx5vYsTfK1AhjYwlgyX0N3WWYm6 hkUAn60KzLtu9DZAIX3YYI+bngxsuv70vf1LyGSGxogu//nKVuXWauFa+TpSyRk5ttpG 0Ykw==
X-Gm-Message-State: AOAM530UZQKy3afhnPYPxd7t+55XOdfHLM0WvmzwjXew1aFCmJhy7ukt Vw+2FbAUtIvqZ/BOB5DYk+ILT7KTZJlTJteqEHQ=
X-Google-Smtp-Source: ABdhPJxv5VatdhZobrqtmL71zKpT4Y3n2MnRK855PqN3QdElo/NNDZHpg/2ytYKofL6aIlubm1CQOZAI+MvGDYb0fXo=
X-Received: by 2002:a25:660b:: with SMTP id a11mr3073391ybc.172.1623275322514; Wed, 09 Jun 2021 14:48:42 -0700 (PDT)
MIME-Version: 1.0
References: <DM4PR11MB5438CC6D84B301C907DAA6D1B5369@DM4PR11MB5438.namprd11.prod.outlook.com> <20210609163823.72897E1865D@ary.qy> <CAMm+Lwhs0C80K2B4MoKi1ijghE2o6tmF7E8QreCK62P1bc9Q5Q@mail.gmail.com> <a567a4a6-8aa0-1bf1-bf3b-18c71213fa@iecc.com> <494082D95C1883FD462E6307@PSB>
In-Reply-To: <494082D95C1883FD462E6307@PSB>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 09 Jun 2021 17:48:30 -0400
Message-ID: <CAMm+Lwh3wJ9pHRB7cDK2kPXUm5ucYv+RhU-ayXqXSXoXBPL9ag@mail.gmail.com>
Subject: Re: The problem we could solve (re github etc.)
To: John C Klensin <john-ietf@jck.com>
Cc: "John R. Levine" <johnl@iecc.com>, IETF general list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f8a02205c45c3c8c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OcmRKsWRLpqydy-y73F23yJFJu0>
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:48:56 -0000
On Wed, Jun 9, 2021 at 5:22 PM John C Klensin <john-ietf@jck.com> wrote: > > 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? > The reason I tried to bring it back to stuff that is in IETF scope was because I see all of these issues as being aspects of the same broken approach to Internet accounts. Traditionally, we view an Internet account as being a thing that it LENT by the service provider to the user. And the design of DNS reflects this in that DNS is a naming system for hosts and services, it is not a naming system for people. It is ludicrously expensive for a start, $10/yr for a DNS name is not actually an unreasonable charge for running DNS authoritative services but it is an absurd amount for a user name. When WhatsApp was a paid service, it was $1/yr. So $10/yr for the user name is ridiculous. I think we need to have a reconsideration of the role of naming and authentication and authorization. And this is something a lot of service providers need to think through as tales of people losing all the Amazon digital goods they purchased because their Amazon account was revoked proves. For me, usernames and authentication are something that should intrinsically belong to the user and be theirs for life. I don't think people should lose their Internet names under any circumstances. An Internet name should be just like a traditional common name, just unique to the holder. Authorization is a different matter, that is something that is entirely in the power of the person who owns the resource in question. The IETF is an open forum, the Trilateral Commission is not, The Work is not, The Oxford Union Society is not. There are times when it is fun to participate in a completely open forum and there are times when you don't want to hear yet more stupidity from the woman claiming that vaccination causes people to become magnetized. Every one of the HVAC systems in my house is close to a wired ethernet drop. The system I am planning to move to would connect the furnaces and the AC units directly to the net and these would then in turn take temperatures from multiple sense points in the house for control purposes. A smart furnace makes infinitely more sense than a smart thermostat connected to a furnace so stupid that it can't tell me when it is over pressure, when filters need replacing, etc. etc. The reason we have smart thermostats and stupid furnaces is path dependence. And we are stuck with the Internet account provider model for the same reason.
- Why we really can't use Facebook for technical di… Dean Willis
- Re: Why we really can't use Facebook for technica… Fred Baker
- Re: Why we really can't use Facebook for technica… Töma Gavrichenkov
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Jared Mauch
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- RE: Why we really can't use Facebook for technica… Larry Masinter
- Re: Why we really can't use Facebook for technica… Emil Ivov
- Re: Why we really can't use Facebook for technica… Christian Hopps
- Re: Why we really can't use Facebook for technica… Salz, Rich
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Salz, Rich
- Re: Why we really can't use Facebook for technica… Olivier MJ Crépin-Leblond
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- RE: Why we really can't use Facebook for technica… Larry Masinter
- Re: Why we really can't use Facebook for technica… Fred Baker
- RE: Why we really can't use Facebook for technica… Larry Masinter
- Re: Why we really can't use Facebook for technica… Lloyd W
- Re: Why we really can't use Facebook for technica… Spencer Dawkins at IETF
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… lloydwood@users.sourceforge.net
- Re: Why we really can't use Facebook for technica… Bron Gondwana
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Andy Ringsmuth
- Re: Why we really can't use Facebook for technica… Lloyd W
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Why we really can't use Facebook for technica… Randy Presuhn
- Re: Why we really can't use Facebook for technica… Dean Willis
- Re: Why we really can't use Facebook for technica… Andy Ringsmuth
- Re: Why we really can't use Facebook for technica… Keith Moore
- Re: Moderation at scale is hard^Wimpossible, or W… John Levine
- Re: Moderation at scale is hard^Wimpossible, or W… Emil Ivov
- Re: Why we really can't use Facebook for technica… Richard Shockey
- Re: Why we really can't use Facebook for technica… Aqua Q Glass
- Re: Why we really can't use Facebook for technica… Aqua Q Glass
- Re: Why we really can't use Facebook for technica… Lloyd W
- Re: Why we really can't use Facebook for technica… Lloyd W
- RE: Why we really can't use Facebook for technica… Rob Wilton (rwilton)
- Re: Why we really can't use Facebook for technica… Lloyd W
- RE: Why we really can't use Facebook for technica… Rob Wilton (rwilton)
- Re: Why we really can't use Facebook for technica… Phillip Hallam-Baker
- Re: github terms of service, not Why we really ca… John Levine
- The problem we could solve (re github etc.) Phillip Hallam-Baker
- Re: The problem we could solve (re github etc.) John R. Levine
- Re: The problem we could solve (re github etc.) John C Klensin
- Re: The problem we could solve (re github etc.) Michael Richardson
- Re: The problem we could solve (re github etc.) Michael Richardson
- Re: The problem we could solve (re github etc.) Phillip Hallam-Baker
- Re: The problem we could solve (re github etc.) Alessandro Vesely
- Re: The problem we could solve (re github etc.) Phillip Hallam-Baker