Re: Future Handling of Blue Sheets

"James M. Polk" <jmpolk@cisco.com> Mon, 23 April 2012 19:23 UTC

Return-Path: <jmpolk@cisco.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 78E8D21F85D3 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 12:23:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.463
X-Spam-Level:
X-Spam-Status: No, score=-110.463 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 x55+YDoKwcEQ for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 12:23:43 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id A937D21F85A2 for <ietf@ietf.org>; Mon, 23 Apr 2012 12:23:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=3904; q=dns/txt; s=iport; t=1335209023; x=1336418623; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=gS3tNtEK38b1+OzY3qm/IuFhDp/De5DDxep7z9/mmvo=; b=OdDrxLLe6eNxe8d5/6i/FmZ+PCiPBVuQsdN3cP8e4sYNdWol31p37x+n strHO8Ti9trCtbHqVk+bjhorJ62fv7ZrBpF5ZUrjgFbdzmS/8KmrQrgPP wXrH91yzkk/E038XYUDID3VzwEeUcLxeZWY1mgFLhhxm4gn9lDNi/D65G s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAO6rlU+rRDoJ/2dsb2JhbABEsV6BB4IJAQEBBBIBHgcCPxAHBBgeEBk+BgEbGYdsDJo0jyWRB5BsYwSIY5tsgWmDB4E+
X-IronPort-AV: E=Sophos;i="4.75,468,1330905600"; d="scan'208";a="41820941"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 23 Apr 2012 19:23:43 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q3NJNgKF031010; Mon, 23 Apr 2012 19:23:42 GMT
Message-Id: <201204231923.q3NJNgKF031010@mtv-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 23 Apr 2012 14:23:41 -0500
To: Michael StJohns <mstjohns@comcast.net>, Andy Bierman <andy@netconfcentral.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <20120423183118.C09EE21F8587@ietfa.amsl.com>
References: <2AC114D8-E97B-47A0-B7E0-9EF016DCB09F@ietf.org> <DCC302FAA9FE5F4BBA4DCAD465693779173ED21640@PRVPEXVS03.corp.twcable.com> <ACDB7FE7-5C75-49C4-904D-8542AC05C66E@sobco.com> <4F9581D3.2020605@gmail.com> <20120423171307.2FA7E21F8705@ietfa.amsl.com> <4F9590B1.7070408@netconfcentral.org> <20120423183118.C09EE21F8587@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ietf@ietf.org
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: Mon, 23 Apr 2012 19:23:44 -0000

At 01:31 PM 4/23/2012, Michael StJohns wrote:
>At 01:26 PM 4/23/2012, Andy Bierman wrote:
> >On 04/23/2012 10:13 AM, Michael StJohns wrote:
> >>
> >>
> >>At 12:22 PM 4/23/2012, Melinda Shore wrote:
> >>>On 4/23/12 6:58 AM, Scott O Bradner wrote:
> >>>>see rfc 2418 - they are to keep a record as who is taking part 
> in a WG's activities
> >>>>keeping track of attendees is a basic part of any standards 
> development organization's process
> >>>
> >>>The tension here appears to be between transparency of process and an
> >>>individual right to privacy.  I think that the IETF has a considerable
> >>>stake in the former, not just because of the frequency with which some
> >>>little pisher or other threatens to sue over what they perceive to be
> >>>trust/collusion issues, but because openness is an IETF institutional
> >>>value.  I think it should continue to be.  I understand the privacy
> >>>issues (although I won't necessary lump them as an instance of revealing
> >>>PII) but tend to think that the information being revealed is pretty
> >>>sparse and the privacy concerns here probably aren't substantial enough
> >>>to counterbalance the organizational interest in keeping processes as
> >>>open as possible.
> >>>
> >>>Melinda
> >>
> >>
> >>And to put a further point on it - the last sentence of the "NOTE 
> WELL" notice (http://www.ietf.org/about/note-well.html) that 
> applies to each and every IETF meeting and working group session 
> and IETF activity is very clear that written, audio and video 
> records can and will be kept.  A person attending an IETF meeting 
> has no reasonable expectation of privacy for those things we define 
> as "IETF activities".
> >>
> >>So if someone demands "privacy", the price is non-participation 
> in the IETF.
> >
> >Not exactly -- the NOTE WELL applies to contributions.
> >Is just showing up and observing the meeting considered a contribution?
>
>The NOTE WELL implicates any "statements", oral, written or 
>electronic as well as "submissions".
>
>The last sentence of the NOTE WELL says "A participant in any IETF 
>activity acknowledges that written, audio and video records of 
>meetings may be made and may be available to the public." - and that 
>puts paid to the concept that an attendee has a "privacy" 
>expectation during the meeting.

How can anyone have the expectations for privacy to a meeting they 
have already publicly signed up and paid for - likely with a credit 
card that can also be tracked. To then be concerned about individual 
meeting attendance tied to a certain room during a certain time 
*after the fact* (sometimes by weeks or more) is just silly, and a 
waste of time.

Scan the bluesheets, keep the email addresses for a better record of 
who is who at a certain meeting, destroy the blue sheets after the scan.

James


> >Personally, I don't think the blue sheets should even be filled out,
> >let alone published.  The WG chairs can convey the meeting room 
> size requirements
> >without passing around clipboards and (hopefully) everybody 
> writing down their name.
> >
> >There is no correlation between the blue sheets and IETF contributions.
> >I don't see what purpose they serve anymore.
>
>
>AFAIK, you're not a patent troll.  I have met them during IETF 
>meetings.  One of my RFC's was patented - without my knowledge or 
>consent.  (cf  RFC2786 vs US Patent No. 7290142)  Fortunately, the 
>record was clear that the RFC and the drafts preceded the applicants 
>"spark".  However, it might have been more interesting had there 
>been need to a) prove when the first public disclosure was made and 
>b) implicate a specific person, company or entity in being present 
>when that disclosure was made.  Hence the blue sheets.
>
>So they do serve a purpose.
>
>Mike
>
>
>
> >>Mike
> >>
> >
> >Andy