Re: IETF Chair
Larry Masinter <LMM@acm.org> Fri, 16 October 2020 05:04 UTC
Return-Path: <masinter@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 0610E3A0BDF for <ietf@ietfa.amsl.com>; Thu, 15 Oct 2020 22:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.548
X-Spam-Level:
X-Spam-Status: No, score=-1.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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 SnWsvIdfqz9O for <ietf@ietfa.amsl.com>; Thu, 15 Oct 2020 22:04:30 -0700 (PDT)
Received: from mail-lf1-f46.google.com (mail-lf1-f46.google.com [209.85.167.46]) (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 338A83A0A9F for <ietf@ietf.org>; Thu, 15 Oct 2020 22:04:29 -0700 (PDT)
Received: by mail-lf1-f46.google.com with SMTP id 184so1298395lfd.6 for <ietf@ietf.org>; Thu, 15 Oct 2020 22:04:29 -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=E6vuMYR2Hl7PZ84sHdURBd/zSKxIDAi6vccieqiWFtI=; b=ZC0LGdxtgI/nklqHx1FyG2CvhPY4DoVfOnHm9pE9hPLMNAim3PTO7NXc5JgSsYv6DV v8jpmFWb/vzVsGTDOTMMqhBNo3c/CZAx28QJy2rXd6SIpWOHuibbFgL7rhuBJFQz5726 NhBEIycCRkr9Zuo0hMm6MI5rEx9XntQwUlb67HEnMGSRfV23ku5ut+FqsrZZKS9LkFva ugzC1cApGeL/p4mQ4YIEgNn7wsTlRVC2kCAD6HAWZ/SfuUaQExkyNwH6laHwCBqnnU8r ScurwiAzxJfd/3OL9N3HTT5x9hox2Te5/vgCDlVr38UVMF4KVM+5/SZdLgMwUCRo/QPZ 6oDg==
X-Gm-Message-State: AOAM532UTXAvTOl4LyEMLvxfli8qSmE9E+SBKhcJpDTuUcUdazFl7Kvn T6kp1DSAshKMtvS6D/vtyC/gjgsWHTAjZWyVoIs=
X-Google-Smtp-Source: ABdhPJwTv1j+i1jP2Zqqo+046YiTmfJcEDOsxFNDLifnQMq6bQ6VcOTKT+jgxK+SWVvOQqs4iXK/0cuE2BNWZzUpeUw=
X-Received: by 2002:ac2:551d:: with SMTP id j29mr608618lfk.134.1602824667359; Thu, 15 Oct 2020 22:04:27 -0700 (PDT)
MIME-Version: 1.0
References: <2B51679C-2BED-4F7B-B146-FF1524B00AA5@akamai.com> <C775E80B-9A31-492E-BA6A-96F9FE831316@akamai.com> <128277543.164613.1602611739735@email.ionos.com> <CAMm+LwjCGVUuFXK+fAzpV176hseXB9iLzC-7OZQZf=ca9+3x0A@mail.gmail.com> <CAC4RtVBsuiQCr3AKUjuHERpVEAviiFMXnEqZ0qa5jUnWK+zjfA@mail.gmail.com> <a1c2cf63-cae6-c37e-82ea-57ce44bcdff3@mtcc.com> <CAMm+Lwg9AmOLve+BZr23n-pdSMsNpebmXM_G6dhO4rBnv4243Q@mail.gmail.com> <20201014234035.GV50845@kduck.mit.edu>
In-Reply-To: <20201014234035.GV50845@kduck.mit.edu>
From: Larry Masinter <LMM@acm.org>
Date: Thu, 15 Oct 2020 22:04:17 -0700
Message-ID: <CAKq15vcJOROHhqDe1MWThz6uc5=rsLbwQi=ziZCwQiZe-feLuA@mail.gmail.com>
Subject: Re: IETF Chair
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ef6f2305b1c2b216"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7uhwouMJcHDuagmxBq3dDbj9_gs>
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 05:04:37 -0000
This conversation seems to be about 'good ideas the IETF has ignored for various (mainly stupid) reasons." But I can't tell what you expect the IETF Chair to do? On Wed, Oct 14, 2020 at 4:41 PM Benjamin Kaduk <kaduk@mit.edu> wrote: > On Wed, Oct 14, 2020 at 07:00:49PM -0400, Phillip Hallam-Baker wrote: > > On Wed, Oct 14, 2020 at 5:01 PM Michael Thomas <mike@mtcc.com> wrote: > > > > > > > > On 10/14/20 12:16 PM, Barry Leiba wrote: > > > >> But 90% of the efforts of the academy and 99% of those of commerce > are > > > focused on > > > >> the Blockchain, an integrity technology. > > > > It's worse than that, because not only is most of the effort placed > on > > > > blockchain technology, blockchain technology is also being pushed as > > > > the answer to *everything*. Blockchain technology has a place, but > it > > > > doesn't make sense everywhere, and when one says, "Wait, let's take a > > > > step back and look at what we really *need* blockchains for, and > where > > > > we don't," then one seems a heretic... or at best, quaintly naïve. > > > > > > What place might that be? I really can't think of any. Maybe you can > use > > > it for buying and selling tulips. > > > > > > Mike > > > > > > Every day thousands of courts are presented with digital evidence, pretty > > much all of which should be excluded because it is far too easy to tamper > > with. I have spent days engaged in pointless arguments over > > admissibility that could be avoided entirely. > > > > Every piece of digital evidence that is collected should be time stamped > at > > the time it is collected and enrolled in a notary service using a one way > > sequence. At regular intervals, the notary offering this service should > > cross notarize with other notary services, thus making it impossible for > > any one notary to defect without detection unless every other notary > > colludes. And NIST and every other national lab should run a national > cross > > notary service whose probity would be automatically considered valid by > the > > courts of that country. > > > > That is not the sort of construct I see being built in blockchain land. > > Noooo, much more fun selling virtual cowrie shells. But it is exactly the > > sort of infrastructure we need. > > Yup, that would be swell. Too bad I don't have a budget to help make it > happen. > > -Ben > > -- -- https://LarryMasinter.net <http://larry.masinter.net>
- IETF Chair Salz, Rich
- Re: IETF Chair Brian E Carpenter
- Re: IETF Chair Sarah Banks
- Re: IETF Chair Carsten Bormann
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Salz, Rich
- Re: IETF Chair Timothy Mcsweeney
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Kyle Rose
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Kyle Rose
- Re: IETF Chair Timothy Mcsweeney
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Carsten Bormann
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Salz, Rich
- Re: IETF Chair Timothy Mcsweeney
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Salz, Rich
- RE: IETF Chair Khaled Omar
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Mezgani Ali
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Theodore Y. Ts'o
- Re: IETF Chair Leif Johansson
- Data at rest (was Re: IETF Chair) Robert Sparks
- Connections, and timing (was: IETF chair) Keith Moore
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Barry Leiba
- Re: IETF Chair Phillip Hallam-Baker
- Re: blockchain, not IETF Chair John Levine
- Re: IETF Chair Michael Thomas
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Benjamin Kaduk
- Re: IETF Chair Stephen Farrell
- Blockchain is alchemy Phillip Hallam-Baker
- Re: Connections, and timing (was: IETF chair) Amelia Andersdotter
- Re: IETF Chair Ben Laurie
- Re: IETF Chair Larry Masinter
- Re: IETF Chair Timothy Mcsweeney
- Re: IETF Chair Timothy Mcsweeney
- Re: IETF Chair Timothy Mcsweeney