Re: Proposed IETF Websites Privacy Policy; Community Input Requested
S Moonesamy <sm+ietf@elandsys.com> Sun, 22 March 2015 20:17 UTC
Return-Path: <sm@elandsys.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 776C51A1A7E for <ietf@ietfa.amsl.com>; Sun, 22 Mar 2015 13:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level:
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0ILtu63IxYAn for <ietf@ietfa.amsl.com>; Sun, 22 Mar 2015 13:17:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 118BD1A1A60 for <ietf@ietf.org>; Sun, 22 Mar 2015 13:17:17 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.204.52]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id t2MKH5b7001912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sun, 22 Mar 2015 13:17:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1427055436; x=1427141836; bh=jhWy2Li0otwXP5rmbrFjfFNuVsZ4YGNwJ8HgHdLmAw8=; h=Date:To:From:Subject:In-Reply-To:References; b=NWkFzcjnALQ3O8bg7b8WOOOaqULkpcjfJKLJuNPrYpEW5AERtedqWuetU0ivSBhpR gZq6G7TNBusY8EOqMYTbv2M+DHaLAHlUzJ32iV9HJPskDVEBm2vA/O2qcRVATXDN/4 0ZTHVVzleeuGnlk5SUGWrNjKes6p33Y4mLVQ5Rkw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1427055436; x=1427141836; i=@elandsys.com; bh=jhWy2Li0otwXP5rmbrFjfFNuVsZ4YGNwJ8HgHdLmAw8=; h=Date:To:From:Subject:In-Reply-To:References; b=FhfS6+uuRqZhlKd18zHj610jjilWKCgAyLT95w3YmTiQqbxC4dAWVaKmPjymPFuFU nTZxg8ZdgKJ/yR5662WJgxlwtHi4oL3nwv7uUMOY9ih8Kb7xJx9YOnhBPc+Zh/LiBz 8N23s/caytfAVWL7suRJrbIS2+2ZNchMbNvhUFsY=
Message-Id: <6.2.5.6.2.20150322122713.0e93c238@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 22 Mar 2015 12:41:25 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Proposed IETF Websites Privacy Policy; Community Input Requested
In-Reply-To: <20150203155217.2391.76679.idtracker@ietfa.amsl.com>
References: <20150203155217.2391.76679.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IlYYGbuw0g-JHPdhmn2pPtQv80M>
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: Sun, 22 Mar 2015 20:17:18 -0000
Hello, At 08:52 03-02-2015, IETF Administrative Director wrote: >The IAOC would like community input on a proposed IETF websites >Privacy Policy. > >We are required by California law (and good net citizenship) to have >an accurate >privacy policy on our websites. Counsel have reviewed this >statement for compliance >with US and EU privacy regulations. [snip] >The IAOC will consider all comments received by 17 February 2015. Apologies for the late response. The proposed privacy policy for the IETF web site is four pages. Most people probably won't read beyond "the Internet Engineering Task Force (IETF) is committed to protecting the privacy and security of the personal information of our participants and of visitors to our site". What is the meaning of the following: "You also consent to our using the information to communicate with you further about your interaction with the site, programs, and services, hat IETF may offer to you, and your relationship with IETF." "If you provide personal data through this site, you acknowledge and agree that such personal data may be transferred from your current location to the offices and servers of the IETF and its affiliates, agents, and service providers located in the United States and in other countries." In simple terms the person is agreeing to his/her personal data to be transferred anywhere in the world and to (unknown) affiliates of the IETF. "When you interact with the site, we strive to make your experience easy and meaningful. We may use cookies and other means to track user activity and collect site data." The above text about cookies sounds like marketing. I suggest explaining that the IETF uses cookies for purposes X, Y, etc and list some information about the cookies for the technically-inclined. "We offer specific opt-in and opt-out options so if you do not wish to receive such mailings, please inform the IETF by email, phone, or postal mail directed to the contact information provided at" Doesn't the IETF use "opt-in" by default? Regards, S. Moonesamy
- Re: Proposed IETF Websites Privacy Policy; Commun… S Moonesamy
- RE: Proposed IETF Websites Privacy Policy; Commun… James Gannon
- Proposed IETF Websites’ Privacy Policy; Community… IETF Administrative Director
- Re: Proposed IETF Websites’ Privacy Policy; Commu… Bjoern Hoehrmann
- Re: Proposed IETF Websites’ Privacy Policy; Commu… John Levine
- Re: Proposed IETF Websites’ Privacy Policy; Commu… Joseph Lorenzo Hall
- Re: Proposed IETF Websites’ Privacy Policy; Commu… Tom Taylor
- Re: Proposed IETF Websites’ Privacy Policy; Commu… Mark Nottingham
- RE: Proposed IETF Websites’ Privacy Policy; Commu… Adrian Farrel
- Re: RE: Proposed IETF Websites’ Privacy Policy; C… John Levine
- Re: Proposed IETF Websites’ Privacy Policy; Commu… Alexey Melnikov
- Re: Proposed IETF Websites’ Privacy Policy; Commu… t.p.