[saag] Hello from the Ethereum Foundation

Virgil Griffith <i@virgil.gr> Mon, 27 March 2017 16:06 UTC

Return-Path: <i@virgil.gr>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A847129465 for <saag@ietfa.amsl.com>; Mon, 27 Mar 2017 09:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=virgil.gr
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 1MwS2mcusMKu for <saag@ietfa.amsl.com>; Mon, 27 Mar 2017 09:06:40 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 74E7B129454 for <saag@ietf.org>; Mon, 27 Mar 2017 09:06:40 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id p77so34823957ywg.1 for <saag@ietf.org>; Mon, 27 Mar 2017 09:06:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virgil.gr; s=dkim; h=mime-version:from:date:message-id:subject:to; bh=fG37KPLbTFelh4npkV34wekwzeCkKH0rMNLcZoPbo28=; b=YXsZDTK0FBvybs0D5UuHVZqJqA6OuPMUCldkK2LENXgLpe/zLcudow2r1T0+1rPP4P 0m3VorPbiGN9Pv7IVdA9oC5pPjr9h4l0cTkXR5AKJFnhJ9kJW7R53f8vxtiHFOzMgRgw WuLOoRPECzhlwYWHZME3rsTaiyj1ZEfg6Ab5A=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fG37KPLbTFelh4npkV34wekwzeCkKH0rMNLcZoPbo28=; b=cPEsNIiFqQynYAxShhW74Nz2fiuiZh47NJaXbZMACd9k2kEdtAg4BC0+jJ2B+a3ULW aL2PzCczldtntRxIYzn5GAVSKLIbYhY214UzbbcV8lMQrd4G9XeTYs7UZf/yx3sMTwGb M2d6HCalymNLvllcezW9TkSpHFW/Joq3soiCneO/UczWNbxMNHyRZr6ozXrQ3Sbc3x+o mE/v/3zG5EmGjpuMl4OKNsa2+qm1/fwwWJULFU31OCc5OZxAxLMiJeAXJMsy1+9ecIu6 dv3XbQOiR2jV/Ts1tBCEx8JWDe6DCEGj18hrqJ1HMnNQm7D23zzXNyMAP9LYc5XlE5Th 5FEw==
X-Gm-Message-State: AFeK/H0Q8uhgIUv8AVeZqsE/5BfzOq6+Ti7Rc6+Q6ss7aPgrGaUcGqAJk2QF4mf9koiS1gD46ahLhtucESrAfg==
X-Received: by 10.13.225.80 with SMTP id k77mr18639082ywe.83.1490630799334; Mon, 27 Mar 2017 09:06:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.252.26 with HTTP; Mon, 27 Mar 2017 09:06:18 -0700 (PDT)
From: Virgil Griffith <i@virgil.gr>
Date: Tue, 28 Mar 2017 00:06:18 +0800
Message-ID: <CADop2NHa1QaFA_zmYLBpbKKts5o__wKa9E0DbNq_-sFuw-_h+w@mail.gmail.com>
To: saag@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c071944493f7c054bb8875a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/yV65gWEp9bOiEr8AOr5BzNrWCTQ>
Subject: [saag] Hello from the Ethereum Foundation
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 16:06:42 -0000

Hello everyone.

I was invited to this list by Walid Al-Saqaf.  I represent the Ethereum
Foundation and am joining this list because the Foundation is starting to
build-out our public platform. For an example of this build-out, we
recently launched the new Ethereum Name Service:

https://hackernoon.com/hosting-a-dns-domain-on-the-blockchain-58a41dc50028#.b5tetdpiw
https://github.com/ethereum/ens


As-is, the Ethereum Name Service allows any "smart-contract" or "dapp" on
Ethereum to be accessed via a human-readable name.  Normally this requires
access to the Ethereum system, but we've opened this up to the
world-wide-web by with the DNS proxy "ens.domains".  But we wish to do
better.  Particularly, we are interested in getting the TLD .eth as a
reserved name for the Ethereum platform and get .eth added to the list of
reserved names akin to these:

* https://tools.ietf.org/html/rfc6761
* https://tools.ietf.org/html/rfc7686

Our (very long term) aspiration is to demonstrate by example how a
blockchain can be used as a fully transparent, decentralized
domain-registry.  We hope that if other TLDs see that this can be done
securely, that they might be inspired to emulate us resulting in more
secure, transparent DNS for all internet users.

The Ethereum Foundation has two benefits to the IETF:

(1) There's been plenty of talk on the interface between the web and
blockchain systems, e.g.,
https://www.w3.org/2016/04/blockchain-workshop/report

As Ethereum is the most flexible blockchain platform in the world, we're a
good candidate for experiments in this direction.

(2) There's been talk of wanting to doing IoT with URIs, again particularly
referencing blockchain,

https://www.technologyreview.com/s/603298/a-secure-model-of-iot-with-blockchain/
,

and Ethereum is a good fit for this as well.


I am writing here to get feedback just for how things work around here and
any suggestions for achieving our goals.  Outside of our interest in the
.eth TLD, if you have ideas for other ways Ethereum might help the IETF,
we're obviously interested in doing that, and we can discuss the
possibility of devoting some man-hours to doing that.

Thanks much,
-Virgil