IETF Logo Mail Archive

[Secdispatch] Open Ethics Transparency Protocol

n.lukianets@openethics.ai Mon, 31 January 2022 16:13 UTC

Return-Path: <n.lukianets@openethics.ai>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E763A0AE2; Mon, 31 Jan 2022 08:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.433
X-Spam-Level:
X-Spam-Status: No, score=-6.433 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=openethics.ai
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 jSJ7YImw7ofq; Mon, 31 Jan 2022 08:13:18 -0800 (PST)
Received: from nlskm21.hostsila.org (nlskm21.hostsila.org [88.218.28.6]) (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 7BDFE3A0AEF; Mon, 31 Jan 2022 08:13:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=openethics.ai; s=default; h=Content-Transfer-Encoding:Content-Type: Message-ID:Subject:Cc:To:From:Date:MIME-Version:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=2TUWEQJ0uOUvVqAaFZi68o1AXN3/R+98Wx38AWlqz5g=; b=KTu4N5LLtQhE344hl+Ps5yk36P yZrA82RIlzzMVqOmtRmOdQ2+O/FHNUo3qYFHabJqtaq/C06XAfkypb0DMCMxJSU3U8eWbiCTjnsV6 GRKhQfVwprZwh6aeto10TFUzHs15Z/cgqgKbog9j3vFKhaFZu8oMjlxKII8XuhWdDCR2MtksPnVGk PY4VSDklp1Wtn0rs8bUL8LnkbCh4za5sd4rwOrTcEGsbiffckK8FA17PXhISGPb9gL7q6uP0K6EaU fwSAB+v3yl9xk7dFz/j1XLghTQ5+lwtTWXGmgLuSrTZB0ee6MsbJ4KFo3avP0+sXjbuzOf/uZM3sB 7w9pBRpg==;
Received: from [127.0.0.1] (port=1956 helo=nlskm21.hostsila.org) by nlskm21.hostsila.org with esmtpa (Exim 4.94.2) (envelope-from <n.lukianets@openethics.ai>) id 1nEZIq-0006uh-4Z; Mon, 31 Jan 2022 18:13:15 +0200
MIME-Version: 1.0
Date: Mon, 31 Jan 2022 18:13:15 +0200
From: n.lukianets@openethics.ai
To: art@ietf.org, secdispatch@ietf.org, dispatch@ietf.org, hrpc@irtf.org
User-Agent: Roundcube Webmail/1.4.12
Message-ID: <6dac86b0eb3b96490dadffdc0f1d307a@openethics.ai>
X-Sender: n.lukianets@openethics.ai
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - nlskm21.hostsila.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - openethics.ai
X-Get-Message-Sender-Via: nlskm21.hostsila.org: authenticated_id: n.lukianets@openethics.ai
X-Authenticated-Sender: nlskm21.hostsila.org: n.lukianets@openethics.ai
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/yVFebzSs74RuQo13EwuTeknnECE>
Subject: [Secdispatch] Open Ethics Transparency Protocol
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2022 16:13:24 -0000

Hi everyone,
Nikita Lukianets from the Open Ethics initiative here.

I've been working on the mechanisms to enable transparency for data 
collection and data processing practices for autonomous systems and 
specifically, those powered by machine learning models. Since 2020 I 
have started to draft a guiding document to reflect ways disclosures 
could be submitted, verified, and exchanged. Eventually, I would like to 
see how this work could result in an open standard.

I've chosen IETF as a home for this work as AI-powered applications are 
becoming ubiquitous. Therefore, we should start looking at them from the 
internet standard and supply chain perspectives.
There's an emergent need to bring a legally-agnostic and standardized 
way to describe these systems from privacy, security, fairness, 
datasets, and explainability stances.

The idea is simple
* Following the example of the food (construction, pharma, electrical 
appliance) industry, we need every application to (voluntary) disclose 
the "ingredients", e.g. how data is collected and outputs are produced.
* We need to have a standard way (protocol) to represent each disclosure 
in human- and machine-readable formats, validate, verify and process 
them.
* Complex apps will involve chaining the disclosures for the components 
involved.


My motivation is to continue the discussion here and get feedback 
allowing us to iterate on the protocol. I'd like to bring this 
discussion to a relevant group or/and welcome the creation of the new 
one, also potentially bringing the conversation to the IETF meeting in 
Vienna.

Below are the links with more info
Article to bring the context, in plain English
https://lukianets.medium.com/why-algorithmic-transparency-needs-a-protocol-2b6d5098572f

The IETF I-D
https://datatracker.ietf.org/doc/draft-lukianets-open-ethics-transparency-protocol/

GitHub repo
https://github.com/OpenEthicsAI/OETP

Thanks a lot for your help and thoughts


Nikita Lukianets
Founder, CTO PocketConfidant
Founder Open Ethics initiative
Twitter: @nikiluk
https://fr.linkedin.com/in/nikiluk
Schedule a 30 min call: https://lukianets.com/meet/

v2.23.0 | Report a Bug | By Email