Re: The Next Generation

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 12 September 2019 14:35 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 9C8BC12008B for <ietf@ietfa.amsl.com>; Thu, 12 Sep 2019 07:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 mOYnCZuPJrMF for <ietf@ietfa.amsl.com>; Thu, 12 Sep 2019 07:35:21 -0700 (PDT)
Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) (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 768BC1200FD for <ietf@ietf.org>; Thu, 12 Sep 2019 07:35:21 -0700 (PDT)
Received: by mail-ot1-f52.google.com with SMTP id s28so26280644otd.4 for <ietf@ietf.org>; Thu, 12 Sep 2019 07:35:21 -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=wpZ4lDWz8LWxuMzEzgc8NhxYUZRUdXBlVpgc3p8w9no=; b=DqyPdEqJlZ0Q7WKhDe+6z/VnHl6ThBG+Z3YunGz/LN2W/gnkmsCs7DYY4ySaxnsme7 DtrI0hUIlDRiLJBsATa3+1YulC6pIotDb6u6ltGxpd0fAOlCKga+74N+zgsQFH5VecWz v8yA1HG9l13KvCoM/6GsHLfbazRvn5yOT2QJX8Qdnn16cBMTb0+KUdD+QAUYv8/Pp5lp 6rkwNhHZrm7iTchYTM9/agHoUVjU0aXFUaZ2xKj1wbOybYdZYgC5uoCNSbZ0hJdHwxaP hyFUGYBANnHq5rYNCMRp7WFXcC3PNMGx/Cg0EvsoILZBt8IcoiWWOae6TjDzjh/uQGjh BvMA==
X-Gm-Message-State: APjAAAXcOvdk4pearLDD/iY7+vsM7GzpnPJiqn7FBTYgJNEt7+T3TRWk RtQfHCiL324B69YMrrCmTSWwN3IbLfgpzkg8Uyt15S0X
X-Google-Smtp-Source: APXvYqxPOZ/5KTchOcWoLNM1gdx8pglq2h296wowJeFy/BlWTi3/SIwkwFLwd15IXEZBFOCVUVUPsI5RotTPHSKfiUU=
X-Received: by 2002:a9d:6a12:: with SMTP id g18mr6621165otn.37.1568298920237; Thu, 12 Sep 2019 07:35:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sz3j0iLGsB2bGvfitPzCkiTCJYHfmUF5S-8zPYMt1r+3A@mail.gmail.com> <6.2.5.6.2.20190911094010.0c933fa8@elandnews.com> <20190911194723.GC18811@localhost> <6.2.5.6.2.20190911131143.11401cb8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20190911131143.11401cb8@elandnews.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 12 Sep 2019 10:35:08 -0400
Message-ID: <CAMm+Lwi2CDBCDUhMG7Z487G-BYVp4rRJ=YG73Z=M=TkZ=jaAbQ@mail.gmail.com>
Subject: Re: The Next Generation
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: Nico Williams <nico@cryptonector.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000ade7d05925c0c41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/brL4vDewuCni93K1qCpIgCi9zDc>
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: Thu, 12 Sep 2019 14:35:24 -0000

I have been concerned about this for a while. I was one of the youngest
people engaged in IETF when I started 25 years ago and if you set aside the
grad students who participate while they are doing their thesis, I am still
one of the younger participants.

If you look at average age, it is misleading because the younger folk don't
tend to stick around. And that is probably due in large part to the
dynamics of our industry which has an even bigger demographic issue that
will probably not be acknowledged until the growth suddenly halts as
Moore's law is repealed and all the youngsters go into biotechnology.

I do have a recruitment plan. I see a vast untapped desire for an open
end-to-end secure federated messaging service with Data at Rest security.
There are proprietary schemes in that space (Signal, Telegram, AIP) but
they are all limited in scope because they don't support open services and
so it is impossible for two enterprises to connect unless they choose a
single supplier.

There is a community that is very interested in deploying this technology
to secure the communications infrastructures of political campaigns and I
have begun making contacts in that regard. Some of you will remember I used
the same strategy to promote the Web over rival network hypertext schemes
in the early 90s.

So here is the curious thing, each one of the groups contacted so far has
had the same response: This is something we should do but we should make
our rivals aware of it as well because the end goal here is protecting the
democratic process, not just winning an election.