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

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 05 February 2015 17:32 UTC

Return-Path: <alexey.melnikov@isode.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 141F71A1A2E for <ietf@ietfa.amsl.com>; Thu, 5 Feb 2015 09:32:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level:
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] 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 AQ51GZklfLan for <ietf@ietfa.amsl.com>; Thu, 5 Feb 2015 09:32:00 -0800 (PST)
Received: from statler.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id CB5511A8850 for <ietf@ietf.org>; Thu, 5 Feb 2015 09:31:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1423157513; d=isode.com; s=selector; i=@isode.com; bh=3qu41QwuQRz1gATlqk8qSt4iog0ea8RPRSEJ4VQMTXA=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=rBG4xgx1Nxe2DDCy9N0GPdtMg5qSse3VSq7Y+wWWsVxrtSqHUhf83mebCjC+Y413NwfC/T 3Ufg0pVWLMauYMUBG+Ksg/nZb1FNOvTYfI/4kVYj23mQ7pQVIiBRxZco2CyCM62xCPETsp EWfJa3INIje2OO8WHBFOAkq+lCEa+NM=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <VNOpCAAXb06n@statler.isode.com>; Thu, 5 Feb 2015 17:31:52 +0000
Message-ID: <54D3A8E8.5050508@isode.com>
Date: Thu, 05 Feb 2015 17:31:20 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
To: John Levine <johnl@taugh.com>
Subject: Re: Proposed IETF Websites’ Privacy Policy; Community Input Requested
References: <20150205172612.23769.qmail@ary.lan>
In-Reply-To: <20150205172612.23769.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Q_rOEg6OxZpOT-X0u6XrRrJR8v0>
Cc: "ietf@ietf.org" <ietf@ietf.org>
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:32:01 -0000

On 05/02/2015 17:26, John Levine wrote:
> 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?
I thought all BoF/WG mailing list (but one) that were not hosted on IETF 
servers were migrated to @ietf.org.
>>> Does the IETF have a privacy policy overall?