IETF Logo Mail Archive

Re: RE: Proposed IETF Websites’ Privacy Policy; Community Input Requested

"John Levine" <johnl@taugh.com> Thu, 05 February 2015 17:26 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5A931A19E4 for <ietf@ietfa.amsl.com>; Thu, 5 Feb 2015 09:26:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.163
X-Spam-Level: *
X-Spam-Status: No, score=1.163 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_40=-0.001, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 kxsQPlWYwkEA for <ietf@ietfa.amsl.com>; Thu, 5 Feb 2015 09:26:36 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 264D51A07BC for <ietf@ietf.org>; Thu, 5 Feb 2015 09:26:36 -0800 (PST)
Received: (qmail 64296 invoked from network); 5 Feb 2015 17:26:35 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 5 Feb 2015 17:26:35 -0000
Date: Thu, 05 Feb 2015 17:26:12 -0000
Message-ID: <20150205172612.23769.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RE: Proposed IETF Websites’ Privacy Policy; Community Input Requested
In-Reply-To: <026c01d04132$ae746be0$0b5d43a0$@olddog.co.uk>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/AVCkNLqheFyIFZ4chh6_txkrbz8>
Cc: adrian@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 05 Feb 2015 17:26:37 -0000

In article <026c01d04132$ae746be0$0b5d43a0$@olddog.co.uk> you write:
>Yeah, I'd agree with that.

So would I, but given how amorphous the IETF is, it'll be a challenge to
come up with anything realistic.  For example, how would a privacy policy
apply to mailing list hosted other than on the IETF's servers?


>> Does the IETF have a privacy policy overall?

v2.23.0 | Report a Bug | By Email