RE: Blue Sheet Change Proposal

Dean Anderson <dean@av8.com> Mon, 14 April 2008 17:14 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 BD9DA28C335; Mon, 14 Apr 2008 10:14:29 -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 E2F2828C335 for <ietf@core3.amsl.com>; Wed, 9 Apr 2008 22:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level:
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 VZTBv-mjRalM for <ietf@core3.amsl.com>; Wed, 9 Apr 2008 22:27:56 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) by core3.amsl.com (Postfix) with ESMTP id 87DC128C26B for <ietf@ietf.org>; Wed, 9 Apr 2008 22:27:55 -0700 (PDT)
Received: from citation2.av8.net (citation2.av8.net [130.105.12.10]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id m3A5S4Bb024029 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Apr 2008 01:28:04 -0400
Date: Thu, 10 Apr 2008 01:28:03 -0400
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@citation2.av8.net
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
Subject: RE: Blue Sheet Change Proposal
In-Reply-To: <BB56240F3A190F469C52A57138047A033B9201@xmb-rtp-211.amer.cisco.com>
Message-ID: <Pine.LNX.4.44.0804100113070.22754-100000@citation2.av8.net>
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 14 Apr 2008 10:14:28 -0700
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

Speaking as president of the LPF; not a lawyer but a knowledgeable 
layman.

I think you are correct that the patent issue is a red herring. The
patentee has the _right_ (not the obligation) to keep patent application
contents secret. Failure to keep the secret merely causes them to lose
the _right_ to trade secret status.  They might want that status in the
event the patent application is rejected.  They lose the trade secret
right if the patent is granted, when the patent application is published
18 months after filing, or if they disclose the information publicly, or
if someone _independently_ rediscovers the secret. Obviously, if they
are trying to standardize the patent, they can't have trade-secret
status anyway: the "secret" is publicly disclosed in the draft text.  
So the issue of disclosure is moot.

I have no opinion on whether blue sheet changes are a good idea or a bad
idea for other reasons.  Generally, though, my experience and view is
that truth and disclosure is always a good thing for the public
interest.

		--Dean

On Wed, 9 Apr 2008, Wes Beebee (wbeebee) wrote:

> Regarding the legal issues - if the sessions are broadcast over the
> Internet, and freely downloadable (w/o specifying or tracking who was
> downloading them), how can you be certain that someone was NOT aware
> of certain IPR?  Also, if someone was in the room, how can you be
> certain they WERE aware of certain IPR?  The only thing that the IETF
> can say is that every contribution to the IETF is considered to be
> publically disclosed, and this is indeed what the Note Well says.
> 
> It seems to me that the IPR concerns are a red herring.
> 
> - Wes
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Eric Burger
> Sent: Thursday, April 03, 2008 8:07 PM
> To: IETF Discussion
> Subject: Re: Blue Sheet Change Proposal 
> 
> Two purposes for Blue Sheets:
> 
> 1. Redundant data entry: Quite often, the name is illegible, while the
> e-mail is legible.  We don't care about the e-mail address, what we
> really care about is who was there.  IMHO, this is the important use for
> capturing the e-mail address.
> 
> 2. Legal issues: When the inevitable patent dispute happens, we WILL get
> served to report who was in the room when a particular subject was
> discussed.  Other standards bodies have had this problem, if we haven't
> had it, it means our time is near :-(
> 
> 
> On 4/3/08 4:22 PM, "Mark Andrews" <Mark_Andrews@isc.org> wrote:
> 
> > 
> > 
> >> All,
> >> 
> >> We are considering changing the meeting Blue Sheet by eliminating the
> 
> >> need to enter an email address to avoid spam concerns.
> >> 
> >> Is there any good reason to retain that info bit?
> >> 
> >> Ray
> >> _______________________________________________
> >> IETF mailing list
> >> IETF@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> > 
> >         It's is the only unique token on the blue sheets.  This
> >         assumes no shared email accounts which is a pretty reasonable
> >         assumption in this case.
> > 
> >         Mark
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
> > _______________________________________________
> > IETF mailing list
> > IETF@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> > 
> 
> 
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
> _______________________________________________
> 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
> 
> 

-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 344 9000   


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