Re: [Din] Updated charter proposal

Melinda Shore <melinda.shore@nomountain.net> Sat, 14 July 2018 19:07 UTC

Return-Path: <melinda.shore@nomountain.net>
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 DF4A9130DF4 for <din@ietfa.amsl.com>; Sat, 14 Jul 2018 12:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.889
X-Spam-Level:
X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nomountain-net.20150623.gappssmtp.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 KhIDfaR2Ckp4 for <din@ietfa.amsl.com>; Sat, 14 Jul 2018 12:07:32 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 1134A130DC2 for <din@irtf.org>; Sat, 14 Jul 2018 12:07:31 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id a195-v6so15667968itd.3 for <din@irtf.org>; Sat, 14 Jul 2018 12:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=subject:cc:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=K9LobzKG95WwlwHgdYGL+Km7zWBPu4PbXpNwqdMIsS8=; b=V+k4S8iVPW9fpC7sF8lDXl7KV5+TlmT/l6gotIyu6+svHvekY3ybc+7u3RjRHFTYCA pJ6W+WiK1YyfTMriyyIRZxsrVAPkw9FCak3RULMD9uBznaoHUEPgeDTD3J/rGVq8WSuw r5ZDLwA2f2QSRNtFFvI5Rl4KxO8JLBLSO149KjWuWtB5hocD8zCNZd5unYJcalzeuTxS RyBtgxk92CH3HktvP3oNO/8NhOxJ45V3GgnRH93N0wGphyjGGQsbRWnYGhYcBsUIn4uT bNZtnSHMkyHXoBfBD5vVWuZUGGIPxlFrdXmw4mYXHvATvIYcoSmXnBB/+bLw6ik79vqI SKAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=K9LobzKG95WwlwHgdYGL+Km7zWBPu4PbXpNwqdMIsS8=; b=Q4QdQpSEIMK3X/qJR2Mztn3CWtQxwThDwzO1WEHB1VqOISwUm8+fJ7I4pwvCoUnot/ oKGNdaXGQNXQNhXZWlbe922cDEUC4GRD8G9p9JeP40JtLf+eh7Yeyv6p9PwjqKoE0Mnp mGcP8Z77JNLj9Izs5jHe7Zxsjcmbd+PaHghZm//ekWwi/b1x3hAigypB8GLteXFnk4ta S2EzS1FiiQY0Tqo4+ENkPVAkpJWZHHHNbTGI4YA9ykRn//PE41/aIKJRC3fE225mcYuS woOykx5Er5vo2K2Ra8tkiYKDf9js5jBzap9cvBrRknmx3cN3vZ38nM+pCt6L3pPcl8AK Ktbw==
X-Gm-Message-State: AOUpUlEMZfNxSZsrdtQABBnD8DkpocCTbwmyDBwG3n/0dGv/rCDMG5iP bwgtrQVFgXLD9PdNDvViu8Riwlc6uQ==
X-Google-Smtp-Source: AAOMgpc/RrlKQ8YbOo/y7q4e62lY9fXo/UCEJp05QAHo1WhINFs65gQWHQHhE2Im+3Cs/hsBsTHkgw==
X-Received: by 2002:a24:2116:: with SMTP id e22-v6mr8247178ita.47.1531595251187; Sat, 14 Jul 2018 12:07:31 -0700 (PDT)
Received: from dhcp-90a0.meeting.ietf.org ([2001:67c:1232:144:3149:3c62:ad70:8fea]) by smtp.gmail.com with ESMTPSA id b2-v6sm7103288iok.40.2018.07.14.12.07.30 for <din@irtf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Jul 2018 12:07:30 -0700 (PDT)
Cc: "din@irtf.org" <din@irtf.org>
References: <76cd5da5-c2ba-dc04-e1bb-6ffd49f94eb3@nomountain.net> <D56BEA89-1EDA-47C1-8072-102DB2B1361A@ulusofona.pt> <20180713153505.csx5ih4g3ynhsrkk@faui48f.informatik.uni-erlangen.de> <A397738A-7F2D-43D8-9914-E85ABC40A40A@telefonica.com>
From: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <41aad02d-2b9a-e0a3-b8ee-b4760bf6d4a3@nomountain.net>
Date: Sat, 14 Jul 2018 15:07:29 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <A397738A-7F2D-43D8-9914-E85ABC40A40A@telefonica.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/m0M7kps1XtTAqHKRfyf5WJvGTrc>
Subject: Re: [Din] Updated charter proposal
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.27
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: Sat, 14 Jul 2018 19:07:33 -0000

I'm not sure it's helpful to consider "decentralized" and "distributed"
as having a subsetted relationship (in either direction).  It may be
helpful to be more explicit about what's meant by "decentralized" in the
dinrg context, especially since we're seeing some proposals which may
or may not be considered decentralized depending on definition and
scope.

Vitalik proposes three characteristics:

. architectural decentralization (number of entities in the network),
. political decentralization (control/policy), and
. logical decentralization

with the latter being somewhat problematic, in that at some point you
probably want consistent state across all participants (i.e. you
should be able to continue if there's a partition, but then eventually
converge).

I'm not sure I agree with this framing but it may be a useful starting
point for discussion.

Melinda

-- 
Software longa, hardware brevis

PGP key fingerprint  4F68 2D93 2A17 96F8 20F2
                     34C0 DFB8 9172 9A76 DB8F