Re: Identify AI bots in emails at IETF?

Eliot Lear <lear@cisco.com> Mon, 14 October 2019 10:02 UTC

Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44EBB12018D for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2019 03:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ZRRLYQQzfdjK for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2019 03:02:41 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44403120143 for <ietf@ietf.org>; Mon, 14 Oct 2019 03:02:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5192; q=dns/txt; s=iport; t=1571047361; x=1572256961; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=cavvhkVn6q9FRRJhoRJaBdOHo8GxMtU37jMWPe2Y7+k=; b=hkni2v9FSovhSTzWHPXLH0VCKjWR8WC4xKb9ukI3GItbEGpvUkv2t5y7 jKpYTFJF1DWXyhledeyDhhA16gmx+7wr99DvNMMgQq4GSoUau/MS1VeI4 zp+z2Ezu+V5vdeZ0B0WxOkTuVyn7Qa4tJ6kqQ/IaWsE2P37moxPQCp51J 8=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AQAADxRqRd/xbLJq1cChoBAQEBAQEBAQEDAQEBAREBAQECAgEBAQGBaAQBAQEBCwGCH4E/ASASKoQkiQKHbYlqiTOGDxSBZwIHAQEBCQMBAS8BAYRAAoMCNQgOAgMJAQEEAQEBAgEFBG2FOYVLAQEBAQIBI1YFCwsEFCoCAiE2BhODIgGCRgMOIK8bdYEyhU2COw2CGxCBNAGBUopTgX+BOB+CHi4+ghqBdwEHCwGDLTKCLASWJ5ZbQYIsgi+BE41PhAgbmUCYXotzgxMCBAYFAhWBVAM0Z3EzGggbFWUBgkE+EhAUkBc/AzCOQIJFAQE
X-IronPort-AV: E=Sophos;i="5.67,295,1566864000"; d="asc'?scan'208,217";a="17970272"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 14 Oct 2019 10:02:39 +0000
Received: from dhcp-10-61-105-163.cisco.com (dhcp-10-61-105-163.cisco.com [10.61.105.163]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x9EA2cFG010757 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 14 Oct 2019 10:02:38 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <424B598D-34C4-44ED-AA8C-BBECD4D5C4F2@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D7D27C9A-122E-4986-91F8-03FD590EEEF4"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Identify AI bots in emails at IETF?
Date: Mon, 14 Oct 2019 12:02:37 +0200
In-Reply-To: <91c56549-23f7-ab70-fb6a-02368fbb3e9f@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <91c56549-23f7-ab70-fb6a-02368fbb3e9f@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.105.163, dhcp-10-61-105-163.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O6x3rTfy4s8yaR3DxkR2-HABxZA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2019 10:02:44 -0000

It’s a fun question, and there is (at least to me) an obvious answer.  In the good old days we used to have key signing parties at the IETF, and it would be possible for people to attest that I am indeed me and you are indeed you.  That way, at least you could see by people’s signatures whether or not there was someone who signed their key who you knew.

The problem is that the UX would have to keep up with that.  I’m not sure it’s quite up to the task.

Eliot

> On 14 Oct 2019, at 10:39, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> Hi IETFers,
> 
> How to identify whether or not the emails from somebody are from an 'AI bot'?
> 
> Recently I have had public and private email exchanges, related to the DHC WG.            One party involved in the discussion, that I know personally, suggested that the 3rd party might be an AI bot, because his/her emails seem so generated by an automaton - be it language translation or other AI generator.
> 
> I must excuse if the person is real, but also I feel sorry I spent too much time explaining things in private to what might be an AI bot and am nervous against whoever programmed it.
> 
> Alex
>