Re: [Din] [IRTF-Announce] Decentralized Internet Infrastructure (dinrg) RG Virtual Meeting: 2021-06-03 CHANGED

Curtis Villamizar <curtis@orleans.occnc.com> Wed, 26 May 2021 01:48 UTC

Return-Path: <curtis@orleans.occnc.com>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207673A184D; Tue, 25 May 2021 18:48:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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=orleans.occnc.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 iJzQuJaF3Z6w; Tue, 25 May 2021 18:48:52 -0700 (PDT)
Received: from mta5-tap0.andover.occnc.com (mta5-tap0.andover.occnc.com [IPv6:2600:2c00:b000:2500::151]) (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 E33C13A1849; Tue, 25 May 2021 18:48:51 -0700 (PDT)
Received: from harbor2.v6cc2.occnc.com (harbor2-cc2.v6cc2.occnc.com [IPv6:2603:3005:5602:8af2::231]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) (Authenticated sender: curtis@occnc.com) by mta5-tap0.andover.occnc.com (Postfix) with ESMTPSA id 54D21F03B; Tue, 25 May 2021 21:48:47 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orleans.occnc.com; s=curtis-orleans-20210422-132019; t=1621993729; bh=9FKvjbLOHGPBU2efzV4AxSg6lltMm2qVhwZVamZyM18=; h=To:cc:Reply-To:From:Subject:In-reply-to:Date; b=eZVTGzYflddGJy7KOrPa+JyrHiL866If32/aU9cF19voWKq3Xeyde2xrU6KCVli/W 5678mc6XyPrATk8TKlpttAIFWnCkDV9zb/J4j1XmhZgj6nsd894tdecZCrl+pMMuKT 0M84DLZ2VuvU/Hl6I02Doc45fmXczlzDltAIAy8yl5RessRE7R9VyG9Ai2iyhxQtUH qs7j3oprPdXpc1vj4EeqFgu29FUQfQTBUUnbb8p4ytOmsalAZm/V05OorNwUgECmer dZ0mKTcHH1qpNRNCcv+e4AAEVXWbs4NgB2S7Q4XSlRKYx5s3vc7OFruJGOwjHX3zTg U6MaDJvdiZiTw==
To: IESG Secretary <iesg-secretary@ietf.org>
cc: "IETF-Announce" <ietf-announce@ietf.org>, "IRTF-Announce" <irtf-announce@irtf.org>, din@irtf.org
Reply-To: Curtis Villamizar <curtis@orleans.occnc.com>
From: Curtis Villamizar <curtis@orleans.occnc.com>
In-reply-to: Your message of "Tue, 25 May 2021 11:52:44 -0700." <162196876495.10287.15267417001061504362@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <64205.1621993590.1@harbor2-cc2.v6cc2.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 May 2021 21:46:30 -0400
Message-Id: <20210526014851.E33C13A1849@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/bexzsIB1StwVZXUuNJDI5xXizn4>
Subject: Re: [Din] [IRTF-Announce] Decentralized Internet Infrastructure (dinrg) RG Virtual Meeting: 2021-06-03 CHANGED
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 01:48:57 -0000

Here is a place to start.  Web browsers could support DANE so that we
are not dependent on a predetermined set of CA with URLs not bound to
a specific CA so a bad actor (government for example) who has had a CA
accepted to the set included with browsers can make up their own
certificates for any site for the purpose of a man-in-the-middle atack
as long as they don't get caught or can coerce others to look the
other way (ie: claim lawful intercept).

The system of a set of equally trusted CAs is the web's largest single
flaw.

No new protocols needed for that one.  Those who prefer not to use
DNSSEC and DANE can continue to use the bag of CAs included with the
browser.

Curtis


In message <162196876495.10287.15267417001061504362@ietfa.amsl.com>
IESG Secretary writes:
> 
> MEETING DETAILS HAVE CHANGED.  SEE LATEST DETAILS BELOW.
>  
> The Decentralized Internet Infrastructure (dinrg) RG will hold
> a virtual interim meeting on 2021-06-03 from 19:00 to 22:00 UTC.
>  
> Agenda:
> # DINRG Workshop (Interim Meeting) on the Centralization in the Internet
>  
> We are planning an online workshop for the start of June that is intended to enable a principled discussion on Centralization in the Internet and its root causes.
>  
> ## Motivation
> The networking community generally seems to agree that the Internet consolidation and centralization trend has progressed rapidly over the last few years, bringing impactful societal and economical consequences. To counter that trend, multiple studies and activities have been launched to decentralize the Internet and the Web (for example see https://blog.mozilla.org/wp-content/uploads/2017/03/IHPbriefs_decentralization_March_2017.pdf, https://solidproject.org/, and https://www.decentralizedweb.net/, plus various Blockchain-inspired approaches).
>  
> When the internet started as a completely decentralized system 40 years back, at that time perhaps few people, if any, could have foreseen where it is today. How did we get from there to here? What is driving aggregation and centralization in the Internet? What are the implications for industry actors and technology as well as for users/consumers?
>  
> We believe that a good understanding of this question could make a good first step towards understanding whether it is possible/feasible, and if so, how, to steer the Internet away from centralization.
>  
> ## Objectives
> The objective of this workshop is to start an open discussion on the above question to help clearly characterize centralization in the Internet and to discuss its root causes. That is, before jumping to discussing various potential solutions, we suggest taking a step back and discussing how we got from there to here, and what were the driving forces and enablers at each stage.
>  
> We believe that a sound and evidence-based understanding is of key importance for devising any effective form of remedy and action plan. In particular, we would like to foster an understanding on the relationship of architectural properties and economic developments. For example,
> * whether any architectural features, or lack of them, made an impact on the internet ecosystem developments and business models; and
> * from a retrospective view, was there anything that might have been done differently, to have an impact on the course the Internet has taken?
>  
> This is a complex problem with many relevant factors (technical and economic) and historic developments, so we would like to invite contributions on all of these aspects to this first workshop which may likely lead to further in-depth follow-up discussion. A result of this workshop could indeed be a more substantiated agenda for more focused future research in DINRG.
>  
> ## How to Contribute
> **Please send a message until May 16th EOB to dinrg-chairs@irtf.org** if you are interested to contribute to the workshop. We ask that you include a 1-page abstract (no special formatting requirements) of your intended contribution that would help us to to categorize inputs and to have a record of the different perspectives in the workshop proceedings (DINRG meeting material).
>  
> ## Format
> * DINRG online interim meeting, with open participation
> * 3 hours duration with one break
> * Lightning talks on different aspects of the problem
> * Ample time for discussion
>  
> ## Logistics
> * Date and time: Thursday, June 3rd 2021 1900 UTC, 21:00 CEST / 05:00 AEST (Fri) / 12:00 PDT / 09:00 HST (tentatively)
> * Duration: 3 hours with a break in the middle
> * MeetEcho (Online as an IRTF DINRG meeting) -- details TBA on DINRG list
>  
>  
> Information about remote participation:
> MeetEcho: https://meetings.conf.meetecho.com/interim/?short=ed3b91f7-04e0-4cdb-9477-f1014f5ca47b