Re: IETF Chair

Benjamin Kaduk <kaduk@mit.edu> Wed, 14 October 2020 23:40 UTC

Return-Path: <kaduk@mit.edu>
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 075303A1158 for <ietf@ietfa.amsl.com>; Wed, 14 Oct 2020 16:40:47 -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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Gb-2Clfw2ATg for <ietf@ietfa.amsl.com>; Wed, 14 Oct 2020 16:40:45 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 4B7683A1165 for <ietf@ietf.org>; Wed, 14 Oct 2020 16:40:44 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 09ENeaUL001826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 14 Oct 2020 19:40:42 -0400
Date: Wed, 14 Oct 2020 16:40:35 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF Chair
Message-ID: <20201014234035.GV50845@kduck.mit.edu>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAMm+Lwg9AmOLve+BZr23n-pdSMsNpebmXM_G6dhO4rBnv4243Q@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VcPvlJH7dYJfVjvlojYuDV3beF8>
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, 14 Oct 2020 23:40:47 -0000

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