Re: Applying "Note Well" to side meetings

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 22 July 2019 17:40 UTC

Return-Path: <jmh@joelhalpern.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 3FBCF1202B1 for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 10:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AAQgpW_dVw1 for <ietf@ietfa.amsl.com>; Mon, 22 Jul 2019 10:40:06 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38F15120292 for <ietf@ietf.org>; Mon, 22 Jul 2019 10:40:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 45splp0y2NzYw1J; Mon, 22 Jul 2019 10:40:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1563817206; bh=BUiWNnBNipQJxBFbHV0DWC5YfzSU2Ds6fG4ic1AUmM4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=RP8PXPvFU7w0MQwbZf41BAsC4ara7uV6sHhz3mJxRaGy4+5Zv/CO8S0ci73umgeDc 0TOstFVS78KVTXlyTxpt1rKHR/WXTzl9K9R30933B6k6sHOaPkrbT4Iwz8aJ3AmVOb RTo3hUn9UqlO/vl5u+Sy7Wb28RSaCPZbWRTGHXHs=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [IPv6:2001:67c:370:128:1d5e:d608:1451:a431] (unknown [IPv6:2001:67c:370:128:1d5e:d608:1451:a431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 45spln4G66zKm5K; Mon, 22 Jul 2019 10:40:05 -0700 (PDT)
Subject: Re: Applying "Note Well" to side meetings
To: Nico Williams <nico@cryptonector.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
References: <007b01d53f2f$ef335830$cd9a0890$@olddog.co.uk> <DM6PR14MB282741D8727A72156457555AF8C50@DM6PR14MB2827.namprd14.prod.outlook.com> <63AC1040-37C8-4DAA-B222-1F166D333CF7@akamai.com> <CAL02cgRxxic78LeDKonAFMJKAuuXtYeZnScVJ6MXyPZFaZt7wA@mail.gmail.com> <20190722155714.GK24576@localhost>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <440fb203-19fe-2dd6-679a-500b89b739e3@joelhalpern.com>
Date: Mon, 22 Jul 2019 13:40:02 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <20190722155714.GK24576@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xNKioDbtp27t59lMbu0PE9xUMvo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Jul 2019 17:40:13 -0000

Well...
If you have a side meeting, and discuss papers (which do not happen to 
have been Internet Drafts) and you do not invoke Note Well, then you do 
not have the right to use those papers for future IETF work.

Note Well is not just about patent disclosure.  It covers multiple things.

Yours,
Joel

On 7/22/2019 11:57 AM, Nico Williams wrote:
> On Sun, Jul 21, 2019 at 06:25:12AM -0400, Richard Barnes wrote:
>> Maybe folks could provide a citation for this?  Because I have exactly the
>> opposite impression — that the Note Well only applies in contexts where it
>> is explicitly stated that it does, e.g., official sessions.
> 
> I've long understood that Note Well applies when and only when
> ('WWHEN'?) it is invoked, and should be invoked whenever IETF work is
> discussed among participants with different employers even if the
> meeting is not an official IETF meeting.
> 
> Depending on the cast of attendees I might not invoke Note Well in a
> side meeting with an unstated understanding that we're not out to screw
> each other on IP.  However, this is a bad habit, and I should always
> invoke Note Well when discussing IETF work or potential IETF work with
> colleagues from other organizations.  It's a bad habit not just because
> my friends might purposefully or otherwise screw me, but also because I
> might forget to invoke Note Well when others are around.
> 
> Official IETF meetings are (I guess) required to invoke the Note Well,
> whether they be interim or not, whether they be remote or not, but it
> still needs to be invoked in order to really apply.
> 
> Bar BoFs are unofficial meetings, and thus not required to invoke Note
> Well, thus too arguably there is no implied intent to have Note Well
> apply to them, which is why Note Well should be invoked explicitly.  My
> advice would be that Note Well always be invoked at the start of the bar
> BoF and in any email threads for organizing a bar BoF and any
> invitations sent (so that late arrivals understand the expectation that
> Note Well applies).
> 
> It must not be a common occurrence that bar BoF participants intend Note
> Well to _not_ apply.  It would be nice if Note Well could be made to
> impliedly apply by default, but I guess that's not feasible.
> 
>> As Adrian says, there is a line.  I understood that line to be something
>> like, “The organizers of the meeting decide to apply Note Well”, just as
>> one might apply the Chatham House Rule.  So side meetings could be covered
>> if they chose, but not by default.
> 
> +1
> 
>> In any case, the premise for this thread seems a bit confused, since side
>> meetings are by definition not subject to IETF control.
> 
> A lot of work happens in bar BoFs though, so it's a fair question.  So
> either we shouldn't have them at all or we should acknowledge that they
> are a thing.  The IETF can't control a bar BoF, but a) it can provide
> advice about them, and b) it could provide rooms for ad-hoc BoFs with
> Note Well plastered on the walls :)
> 
> Nico
>