Re: Future Handling of Blue Sheets

SM <sm@resistor.net> Thu, 10 May 2012 22:20 UTC

Return-Path: <sm@resistor.net>
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 2578621F8598 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 15:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level:
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, 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 rT-ZzF5EfCmy for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 15:20:53 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8077E21F844E for <ietf@ietf.org>; Thu, 10 May 2012 15:20:53 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q4AMKmNJ027736; Thu, 10 May 2012 15:20:51 -0700 (PDT)
Message-Id: <6.2.5.6.2.20120510123935.094139d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 May 2012 15:11:25 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <367E45C5495F9BDB6E24C211@PST.JCK.COM>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com> <367E45C5495F9BDB6E24C211@PST.JCK.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: Thu, 10 May 2012 22:20:54 -0000

Hi John,
At 11:31 10-05-2012, John C Klensin wrote:
>participate in any way in an affected WG.  I hate the idea of
>the community getting embroiled in accusations and
>counter-accusations but one advantage to a working IPR policy
>(as well as general openness) of publishing the blue sheets is

I am fine either way with the handling of the blue sheets.  I am also 
fine with whatever the IESG decides (on this topic only :-)).  This 
topic has been sold as a matter of openness.  The question can be 
traced back to newspaperization.  In those days, propagation of 
information was localized.  Nowadays, it can be globalized.  That can 
be good; it can also be bad.

The scrawls from the blue sheets will be accessible after around a 
month.  Should the world be able to find out that:

   (i)  you were in Paris

   (ii) you attended the EAI session

Now let's assume that the work is covered by one of your 
inventions.  Although you were in that session according to the blue 
sheets, you did not participate in the discussion according to the 
minutes (the analogy is that you are subscribed to the mailing list 
but you have not posted any messages).  Do you have to file an IPR disclosure?

Coming back to being open and transparent, the IETF tends to have a 
variable stance on that.  Exposing information allows other people to 
evaluate fairness, whether there is conflict of interest, etc.  It 
does not always work out well; some people may be unhappy, offended 
or uncomfortable.  If you look at the list of WGs being tracked, you 
will notice that some people provided the information, some 
didn't.  I didn't ask why.  As a quick thought, I guess that people 
are uneasy with the idea of the information being publicized to the 
world or they used the default, this information is not relevant to 
any random person.

Let's ignore the IPR argument.  What question(s) should one ask in 
setting the boundaries for open and transparent?

Regards,
-sm