Re: Comments on <draft-cooper-privacy-policy-01.txt>

todd glassey <tglassey@earthlink.net> Fri, 09 July 2010 14:37 UTC

Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D6563A6A74 for <ietf@core3.amsl.com>; Fri, 9 Jul 2010 07:37:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FGv2-3fEIEBU for <ietf@core3.amsl.com>; Fri, 9 Jul 2010 07:37:00 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 9CF873A6A6F for <ietf@ietf.org>; Fri, 9 Jul 2010 07:36:59 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=YAJW3zmE0JHcAtP3z7p8eaYDsqXIHbQfMRoyzQh1OYXyyu20o8sYlTCiOI5stDIb; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.66] (helo=[192.168.1.100]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1OXEhF-00008n-U6 for ietf@ietf.org; Fri, 09 Jul 2010 10:36:58 -0400
Message-ID: <4C373409.8020308@earthlink.net>
Date: Fri, 09 Jul 2010 07:36:57 -0700
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Comments on <draft-cooper-privacy-policy-01.txt>
References: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org> <47076F01-CC4C-45E6-803E-8E2516BE15AC@gmail.com> <20100709113224.123900@gmx.net>
In-Reply-To: <20100709113224.123900@gmx.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7990ded9ed63158b3b37560123ff341e85350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.66
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 09 Jul 2010 14:37:01 -0000

 On 7/9/2010 4:32 AM, Hannes Tschofenig wrote:
> Hi Bob, 
>
> just a very quick reaction to your mail: 
>
> ~snip~ 
>> I have issues with the Introduction.  The first sentence says: 
>>
>>    In keeping with the goals and objectives of this standards body, the
>>    IETF is committed to the highest degree of respect for the privacy of
>>    IETF participants and site visitors.
>>
>> This makes it sound like the highest priority of the IETF is Privacy.  I
>> don't think this is true as I described above.  The vast majority of what
>> the IETF does in Public.  There is very little that is Private.  The IETF is
>> careful about what needs to be kept private and does not disclose it


Everything you have said is true but in this case the specific use of
the privacy policy is in this case to provide people who are slammed
with SPAM from people illegally harvesting contact information from IETF
postings and mailing list activity to create their own personal
commercial email lists and NOT to protect their identity or who they
represent...

You cannot take that away from them no matter what - and since the IETF
in its raging toothless manner fails to protect that data itself, it is
up to the IETF to enable everyone else to protect themselves from damage
which occurs to them by being in the IETF.

Also on the other side of the privacy coin, you will find that EVERYONE
here has a formal legal right to know who everyone else is representing
in the IETF meaning that there is no direct privacy control possible.




Todd Glassey