Re: Blue Sheet Change Proposal

Marshall Eubanks <tme@multicasttech.com> Fri, 04 April 2008 21:51 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF2E83A6BA3; Fri, 4 Apr 2008 14:51:58 -0700 (PDT)
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 CAE273A6BA3; Fri, 4 Apr 2008 14:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.51
X-Spam-Level:
X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[AWL=1.089, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 8TYgAwg951we; Fri, 4 Apr 2008 14:51:56 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 3B0A73A6A00; Fri, 4 Apr 2008 14:51:56 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [???6??p????O7IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 10923379; Fri, 04 Apr 2008 16:52:02 -0500
In-Reply-To: <8282D6B77F4B287BF995B8F7@p3.JCK.COM>
References: <8282D6B77F4B287BF995B8F7@p3.JCK.COM>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <FF5ACE65-1876-4729-9463-3D912DC1A4F1@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: Blue Sheet Change Proposal
Date: Fri, 4 Apr 2008 17:51:58 -0400
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.753)
Cc: Harald Alvestrand <harald@alvestrand.no>, Derek Atkins <derek@ihtfp.com>, IETF Discussion <ietf@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

I thought that people might like to see where the Blue Sheets are  
currently stored by the IETF Trust once the
Secretariat is done with them :

http://www.americafree.tv/IETF_Trust/index.html

I feel fairly certain that addresses are not being scanned there.

Regards
Marshall

On Apr 4, 2008, at 5:19 PM, John C Klensin wrote:
>
>
> --On Friday, 04 April, 2008 11:56 -0400 Derek Atkins
> <derek@ihtfp.com> wrote:
>
>> Harald Alvestrand <harald@alvestrand.no> writes:
>>
>>> Diving straight into armchairing myself, I'll just note that
>>> under EU data privacy laws, it's illegal to collect personal
>>> info for which you have no legitimate purpose - so if we
>>> never use those emails for anything, we shouldn't collect
>>> them.
>>
>> I've used them.  One time when I chaired a BOF I collected the
>> email addresses to personally ask if they wanted to be involved
>> in the mailing list.  (It was done this way because the list
>> was not set up prior to the meeting).  So, having email
>> addresses was very important to inform everyone in the room of
>> the list address.
>
> Yes.  And, as a sometime BOF or WG chair, I've often asked the
> secretariat for copies of the blue sheets (and gotten them) to
> check names of spellings against the minutes, to write people
> asking for clarification about what they said, and to get my own
> sense of the profile and pattern of those participating in the
> meetings compared to those who were participating on the list.
> Some of those uses require email addresses, some don't.  But the
> activity is, IMO, legitimate and useful enough that I'm
> reluctant to give up the email addresses unless someone
> demonstrates that there is a real problem that needs solving.
>
> I won't repeat what others have said about the presence or
> absence of the problem, but I'm not convinced either.
>
>     john
>
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf