IETF Logo Mail Archive

Re: very secret, was Approaching the IETF - A View from Civil Society

John Levine <johnl@taugh.com> Fri, 28 July 2023 17:36 UTC

Return-Path: <johnl@iecc.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 3DD88C14CE5D for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2023 10:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.858
X-Spam-Level:
X-Spam-Status: No, score=-1.858 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="SP7oKAZj"; dkim=pass (2048-bit key) header.d=taugh.com header.b="ERTvxPtY"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ab6d5m-WF176 for <ietf@ietfa.amsl.com>; Fri, 28 Jul 2023 10:36:53 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB1BC151061 for <ietf@ietf.org>; Fri, 28 Jul 2023 10:35:47 -0700 (PDT)
Received: (qmail 35730 invoked from network); 28 Jul 2023 17:35:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=8b90.64c3fc70.k2307; bh=JaCbSpXBBuB3WIFkMtLLi7EwIPxu2vPImSVTJxSus9k=; b=SP7oKAZjBvaIvZAeoQ+OdmETyGi7ThkZxoolIbbBwvZ/aPIY6qK9fRUZVSmqv0smv3iaSCd1OzbUxyBvJDFXo3XnSv4PZO/KOJ542hKyeHpRBdiMmxpuIqChGsfhF2OV9t2damri1H14Oy+vIyfFDjFaE03e9p9TYE7JAuPIWN20e2U0J7czpAVDQu7iO5/Xg26Z1QAZMGSDVkSmdu+6qaL9i9cl/hKRjEgS/fMos/j+jvE43zdClqx4l3vHkFUkevLKX48/C+mKYa5fO9QrL5S5DHhYM83VWWuxMB2QQKOmrehHmS+NPH0hm0U3X+8WYvuO+VIdcyPzJn9w7uD6dg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=8b90.64c3fc70.k2307; bh=JaCbSpXBBuB3WIFkMtLLi7EwIPxu2vPImSVTJxSus9k=; b=ERTvxPtYxSLNhcbdC/S3KzOWJnRK2khPQpX15xc+N/4lxvSTs1ZDKfwOh4JHfLI+7XQlBkIMT5lbKjdqKTQOtiHhzuq6CUvVlVHVnT6DTCrC2cgN5tN3ydgzNbTiuTDawj7kOreK2nbk/CrphN377JaQb3cwRomH+1O+eO1y6pkpVUSN9L54XlpmdLj1lnrtk7oR0I55ISVR1GGpgr8Yc/GNiz02/c+eSnxjMkSlqNUtCnsu79WAIYswwOE+IL7GK84XUvDxlZ+lyty6AHAchTZdkS7zAvupj0sXjw9EaIjgGV/SDi4ye+lGL1OEzO8Xporv+AriBFq0tPLPxHLRCw==
Received: from dhcp-832f.meeting.ietf.org ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 28 Jul 2023 17:35:44 -0000
Received: by dhcp-832f.meeting.ietf.org (Postfix, from userid 501) id 99212FF288B4; Fri, 28 Jul 2023 10:35:42 -0700 (PDT)
Date: Fri, 28 Jul 2023 10:35:42 -0700
Message-Id: <20230728173543.99212FF288B4@dhcp-832f.meeting.ietf.org>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: very secret, was Approaching the IETF - A View from Civil Society
In-Reply-To: <CBCDA803-6DAC-47F7-88C3-A52A77537A7C@yahoo.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y4I6N47QW4omQSuj5V1ntyFIaFc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Fri, 28 Jul 2023 17:36:59 -0000

It appears that Lloyd W  <lloyd.wood@yahoo.com> said:
>hi Dan,
>
>You do realise you're posting to a public IETF mailing list,
>archived publicly on the web for anyone to read? And that, as a submission to the IETF, that access to your mail is
>authorised by the IETF?

Here in the US, disclaimers like the one below just mean "we don't
have the foggiest understanding of privacy or copyright law" since
they are completely meaningless. I gather that in the UK they are not
quite as vacuous so prudence dicates that we delete his mail unread.

R's,
John

>
>> On 28 Jul 2023, at 07:09, Dan Sexton <Dan@iwf.org.uk> wrote:
>> 
>> The information contained in this email is confidential. It may also be legally privileged. It is intended only
>for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you
>must not disclose, copy, circulate or in any other way use or rely on the information contained in this email. Such
>unauthorised use may be unlawful. If you have received this email in error, please inform us immediately and delete
>it and all copies from your system. Internet Watch Foundation does not accept responsibility for changes made to
>this message after it was sent
>

v2.46.0 | Report a Bug | By Email | System Status