IETF Logo Mail Archive

Request for well-known URI: ecips

Wei Tang <hi@that.world> Thu, 07 March 2019 19:34 UTC

Return-Path: <hi@that.world>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30787126DFA for <wellknown-uri-review@ietfa.amsl.com>; Thu, 7 Mar 2019 11:34:50 -0800 (PST)
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 (1024-bit key) header.d=that.world
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 DOskQi39ogUH for <wellknown-uri-review@ietfa.amsl.com>; Thu, 7 Mar 2019 11:34:47 -0800 (PST)
Received: from hat.that.world (hat.that.world [IPv6:2a01:4f8:171:270b::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7960B1279A3 for <wellknown-uri-review@ietf.org>; Thu, 7 Mar 2019 11:34:44 -0800 (PST)
Received: from nicethoughts (unknown [94.134.88.16]) (Authenticated sender: sorpaas) by hat.that.world (Postfix) with ESMTPSA id 4526FC5F82B for <wellknown-uri-review@ietf.org>; Thu, 7 Mar 2019 19:34:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=that.world; s=mail; t=1551987282; bh=pOWTtvzlsOf6qU+w3JHoBasuVvhNqoiV7/H0bYxnzWA=; h=From:To:Subject:Date; b=jsT2PdfCYY0/eZ+LzjkTxxGM3fQXmm8UtEtSDQwJj831QhonkJMH39B6kMwU1vHmp ifbnGQNrMIfgUmgegVV0Fj7tI/Apa2qVYh293sDgmwOtrVpmeWJQqQBjmDp9MMAaCK VnuEcQ4uFGnzZq79cWE2pYecYlCcwtmc8EOtyeMU=
User-agent: mu4e 1.0; emacs 26.1
From: Wei Tang <hi@that.world>
To: wellknown-uri-review@ietf.org
Subject: Request for well-known URI: ecips
Date: Thu, 07 Mar 2019 20:34:36 +0100
Message-ID: <87y35qxyur.fsf@that.world>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wellknown-uri-review/2mvLCy-_omoPsyqjIV2ri6mw5yg>
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wellknown-uri-review/>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 19:36:50 -0000

Hi all,

We're working on a solution to make a specification repository (called
Ethereum Classic Improvement Proposals) more decentralized, as this is
one of the thing that is often requested by our community. Our current
draft is based on federation -- basically by allowing an aggregator to
build up a list of repositories, and then fetch specification
information from a well known URI. We didn't use solutions like
ActivityPub because upgrading to it from the current structure is
complicated, and we don't need the majority of its features.

We need the well known URI both because we need to attest the
"authoritiveness" of the specification (it needs to have a single source
of truth in one particular repository), and also because for an
aggregator, fetching a repository with thousands of specifications by
individual URI would be too inefficient.

* URI suffix: ecips
* Change controller: Wei Tang <hi@that.world>
* Specification document(s): https://ecips.that.world/24-ECIPURI

-- Wei

v2.23.0 | Report a Bug | By Email