Re: Blue Sheet Change Proposal

Dave Crocker <dhc2@dcrocker.net> Fri, 04 April 2008 08:13 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 5588328C169; Fri, 4 Apr 2008 01:13:52 -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 7552A28C1E0 for <ietf@core3.amsl.com>; Fri, 4 Apr 2008 01:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[AWL=0.721, 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 NbdxYYoq8Uyw for <ietf@core3.amsl.com>; Fri, 4 Apr 2008 01:13:49 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 42D123A6807 for <ietf@ietf.org>; Fri, 4 Apr 2008 01:13:49 -0700 (PDT)
Received: from [192.168.0.4] (adsl-67-127-190-96.dsl.pltn13.pacbell.net [67.127.190.96]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id m348DiAW016361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Apr 2008 01:13:50 -0700
Message-ID: <47F5E338.3000809@dcrocker.net>
Date: Fri, 04 Apr 2008 01:13:44 -0700
From: Dave Crocker <dhc2@dcrocker.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: Blue Sheet Change Proposal
References: <C41ABF2B.198EB%eburger@bea.com> <47F5ADE0.6060300@dcrocker.net> <E6C2E8958BA59A4FB960963D475F7AC30BCBDE8243@mail.acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC30BCBDE8243@mail.acmepacket.com>
X-Virus-Scanned: ClamAV 0.92/6575/Thu Apr 3 18:31:52 2008 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 04 Apr 2008 01:13:50 -0700 (PDT)
Cc: IETF Discussion <ietf@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


Hadriel Kaplan wrote:
> IANAL, but I believe if we don't record the emails, it doesn't stop us from
> honoring a subpoena and giving over the blue sheets with the data we do have.
> I'm not saying if that's good or bad. But anyway I assume the IETF has legal
> counsel which has been asked what, if anything, should be recorded to protect
> the IETF and its members, and that they said we don't need to keep emails
> which is why this topic is being discussed by us rather than being moot?


Sorry.  Meant to be more clear.  It wasn't the mere formality, but the practical 
benefit of the email address, in being able to actually contact attendees.

As for the reported use of the lists for spam, they need not be included in the
proceedings.  Hadn't thought about it before, but I'm not seeing why attendee
lists are particularly useful for the Proceedings.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf