Re: Future Handling of Blue Sheets

Eric Burger <eburger-l@standardstrack.com> Wed, 25 April 2012 22:06 UTC

Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD76F21F8852 for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2012 15:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6b23OrHtQck for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2012 15:06:37 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 0FCA421F884D for <ietf@ietf.org>; Wed, 25 Apr 2012 15:06:36 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:50258 helo=[192.168.15.135]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1SNAM6-0007Hl-N8 for ietf@ietf.org; Wed, 25 Apr 2012 15:06:34 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Future Handling of Blue Sheets
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173ED21640@PRVPEXVS03.corp.twcable.com>
Date: Wed, 25 Apr 2012 18:06:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A62A799-6E70-40A5-B5A9-EB522FC72C85@standardstrack.com>
References: <2AC114D8-E97B-47A0-B7E0-9EF016DCB09F@ietf.org> <DCC302FAA9FE5F4BBA4DCAD465693779173ED21640@PRVPEXVS03.corp.twcable.com>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 25 Apr 2012 22:06:37 -0000

I would strongly support what Wes is talking about here.  I see two (other) reasons for keeping blue sheets.  The first is it is a recognized method of showing we have an open standards process.  The second is to support those who are trying to defend themselves in patent suits.  Frankly, I hope the IETF makes it hard for those who want to abuse the IETF process to get patents or ignore prior art and then come after the industry for undeserved royalties.

For the former purpose, just having a list is sufficient. However, for the latter purpose, one needs records that would be admissible in court. Without eating our dog food and having some sort of audited digital signature technology, a simple scan will not do.

On Apr 23, 2012, at 10:04 AM, George, Wes wrote:

>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of IETF
>> Chair
>> Sent: Sunday, April 22, 2012 10:31 AM
>> To: IETF
>> Subject: Future Handling of Blue Sheets
>> 
>> 2.  Scan the blue sheet and include the image in the proceedings for the WG
>> session; and
>> 3.  Discard paper blue sheets after scanning.
> 
> [WEG] Based on some other messages in this thread, there seems to be a lack of clarity as to the full, official purpose of the blue sheets. Are they simply to track generic participation levels for room sizing, or are they also meant as a historical record of attendees to a given WG? It seems that if they are being subpoenaed, and they are archived today, I tend to think that they're meant to officially track attendees. I'd appreciate someone correcting me if I'm wrong.
> 
> If blue sheets are meant to be an official record, then technically we should document handling/scanning/storage procedures for WG chairs and the secretariat such that this scan will be admissible in lieu of a paper copy for any subpoena or other court proceeding. But if we're honest, I'm not sure that they're of much use as an official record either way. Do we have procedures today that would prevent tampering before the paper copy ends up in an archive box? And even then, blue sheets and jabber logs (for remote participants) are still ultimately a best-effort honor system, and therefore there is no guarantee of their validity. I can remotely participate without registering for the meeting, and can sign into Jabber as "Mickey Mouse" just as easily as I can sign the blue sheet that way. I can also sign as "Randy Bush" or sign my own name completely illegibly.
> 
> Could we simply do a headcount for room sizing, and treat the matter of official attendee record for WG meetings as a separate problem? IMO, it's not currently solved by the blue sheets, and I don't see that changing just because we dispense with the paper copies in a box in a warehouse.
> 
> Thanks
> Wes George
> 
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.