[Ilc] New Non-WG Mailing List: Ilc -- Discussion of mechanisms and applications for Internet-level consensus.

IETF Secretariat <ietf-secretariat@ietf.org> Fri, 10 February 2017 19:39 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: ilc@ietf.org
Delivered-To: ilc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE9F7129B29; Fri, 10 Feb 2017 11:39:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148675558593.29252.3504599276468340795.idtracker@ietfa.amsl.com>
Date: Fri, 10 Feb 2017 11:39:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ilc/92Al2PFF19CWDE6mx1K4LM2GFAw>
X-Mailman-Approved-At: Fri, 10 Feb 2017 14:47:54 -0800
Cc: mshore@fastly.com, ilc@ietf.org, dm-list-ietf-ilc@scs.stanford.edu
Subject: [Ilc] New Non-WG Mailing List: Ilc -- Discussion of mechanisms and applications for Internet-level consensus.
X-BeenThere: ilc@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: "Discussion of mechanisms and applications for Internet-level consensus." <ilc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ilc>, <mailto:ilc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ilc/>
List-Post: <mailto:ilc@ietf.org>
List-Help: <mailto:ilc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ilc>, <mailto:ilc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 19:39:46 -0000

A new IETF non-working group email list has been created.

List address: ilc@ietf.org
Archive: https://mailarchive.ietf.org/arch/search/?email_list=ilc
To subscribe: https://www.ietf.org/mailman/listinfo/ilc


Several applications depend on Internet-wide consensus to secure an append-only log, provide tamper-resistant timestamps, and atomically commit transactions across mutually distrustful parties with no preexisting relationship. Examples include: 

* The IETF trans working group is specifying data structures and operational mechanisms for providing secure logging and auditing of TLS server certificates, but lacks a mechanism for determining consensus among logs (or consensus about whether or not a resource should be logged). These functions are currently served by an experimental gossip protocol that can potentially be strengthened through global consensus. 

* The Stellar payment network, is used by remittance companies to trade currencies and send payments across the Internet. 

* UCSD's SPAM (Secure PAckage Manager) project relies on a secure global log both to enable revocation of previously published vulnerable software packages and to guarantee that a particular software release has been publicly available for audit (somewhat like certificate transparency). 

* Stellar has an ongoing secure naming project that aims to allow domain name owners to assign human-readable names to end-user public keys without retaining the ability to lie about those public keys undetected. 

This list is to discuss such applications, the mechanisms that can meet their consensus needs, and a potential role of the IETF in devising a stable specification for an Internet-level consensus mechanism. 

For additional information, please contact the list administrators.