Re: Proposed IETF Privacy Policy for Review

JORDI PALET MARTINEZ <> Wed, 16 March 2016 17:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4A0F512D657 for <>; Wed, 16 Mar 2016 10:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hi7uRL3DQW-K for <>; Wed, 16 Mar 2016 10:15:51 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CAD7012D9DE for <>; Wed, 16 Mar 2016 10:15:50 -0700 (PDT)
X-MDAV-Processed:, Wed, 16 Mar 2016 18:15:47 +0100
Received: from [] by (MDaemon PRO v11.0.3) with ESMTP id md50000370407.msg for <>; Wed, 16 Mar 2016 18:15:46 +0100
X-Spam-Processed:, Wed, 16 Mar 2016 18:15:46 +0100 (not processed: spam filter heuristic analysis disabled)
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
User-Agent: Microsoft-MacOutlook/
Date: Wed, 16 Mar 2016 18:15:45 +0100
Subject: Re: Proposed IETF Privacy Policy for Review
Message-ID: <>
Thread-Topic: Proposed IETF Privacy Policy for Review
References: <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 16 Mar 2016 17:15:53 -0000

I’m very surprised about this:

If you would like to request information regarding our disclosure of your Personal Data to third parties for direct marketing purposes, please email your request to and we will provide this information free of charge. This information includes a list of the categories of Personal Data that was shared with third parties for direct marketing purposes and the names and addresses of all third parties with which we shared such information in the immediately preceding calendar year.

Unless I’m missing something, I don’t think the IETF must provide any personal data to third parties, so my suggestions is that this sections needs to be rewritten to reflect that.


-----Mensaje original-----
De: IETF-Announce <> en nombre de IETF Administrative Director <>
Responder a: <>, <>
Fecha: miércoles, 16 de marzo de 2016, 18:02
Para: IETF Announcement List <>
Asunto: Proposed IETF Privacy Policy for Review

>The IAOC would like community input on a proposed IETF 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.  
>The policy discusses the following:
>  1.  General – Most Personal Data Submitted to IETF Will Become Public
>  2.  You Consent to International Transmission of Your Data
>  3.  Exceptions – Information That We Do Not Release to the Public
>  4.  Security
>  5.  Children
>  6.  Inquiries
>  7.  Compliance
>  8.  Other Organizations
>  9.  Consent
>The proposed Privacy Policy is located here:
>The IAOC will consider all comments received by 31 March 2016.
>Ray Pelletier
>IETF Administrative Director