Re: Applying "Note Well" to side meetings

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 21 July 2019 12:12 UTC

Return-Path: <brian.e.carpenter@gmail.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 9C78112011E for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 05:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 SjciBlng27EF for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 05:12:07 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2404B12004E for <ietf@ietf.org>; Sun, 21 Jul 2019 05:12:07 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id y26so35697660qto.4 for <ietf@ietf.org>; Sun, 21 Jul 2019 05:12:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=B/9UDTEG1p7oifSOHyxyWqdgTcHOBNqM3YQPn3IQPvk=; b=qMn3jnoGSPvM0vCu2pT1Jmetrw4DimOG3HcriJs7VSZ1BCkWipBqItPyZ2c9aaql+r jhT/TkyN+tB9g3mXE24aX8b3cBn+UXnjvYkPHLubAkvQnLe6HM+E9DTjvjlgZyVqgYE6 BeFBwWSL5CLtciCFcenkmtv80y/6bg6ebpuRQs8TzqJ6hzrFaHd/6IS23I8L/scoYjxt J7CFnRZWXuSYedlQxR5KwJISEqSw2vAp26tJtyQK5DYIt9MnZEUESEOFkMR8M8GDHJSF Up4p2AhBWs+S/Yt4SjWpZHi/9xcLOAS2a1zqCpPYh8qUuRCkk3OYwPnPqAjLr+C7wAmN 0Ezw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=B/9UDTEG1p7oifSOHyxyWqdgTcHOBNqM3YQPn3IQPvk=; b=Rd+6J+NQ9PsHFdQFsGJXPE9qQ4Q/hAXag3N0wqg4nqKbhJC7G8Le6ArO7uVf3/XYSB Aq2UNzqOTLy2Kd/k/HxzOO4o0dTCS9Y9Da9qGD3tVxe21WCgZbfrRbg8NBWTrHLQ1UUL E3Rk3iuHS+PS1h6xdI4PhjabGARL1uldYvtwT8FJySngPFzNcfN/u0JVTSthHNm0gPT+ 9UkmRcWHQrtI+QhROSAY3i4mgbSA/C3OtSVIw6Z50KW2x/2SXFwZd9ahW/93bBUMqPTF Y5Z9UEQB1v83j93MmpLRqc7AAiGzZ4xkc3NV87YiPr8JrQkowSWjcMPdhB+pmub8DhRz L2fA==
X-Gm-Message-State: APjAAAUqe7MpEWnRRMIuBgeKu6NW5lMQ7on1SO0zmtqgyldC0qoWM2TP Do6D5FERx+Zqr9smD988iZwipuJ/qlE=
X-Google-Smtp-Source: APXvYqwgcfVq8F7L0VHK5qZZPLjrFb7HUSnRGzr6XsZ3zapkn4UMKleWsErtqC1BZfxokhNVegPxrQ==
X-Received: by 2002:ac8:45d0:: with SMTP id e16mr44650876qto.337.1563711125783; Sun, 21 Jul 2019 05:12:05 -0700 (PDT)
Received: from [31.133.145.144] (dhcp-9190.meeting.ietf.org. [31.133.145.144]) by smtp.gmail.com with ESMTPSA id u7sm20524295qta.82.2019.07.21.05.12.05 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Jul 2019 05:12:05 -0700 (PDT)
Subject: Re: Applying "Note Well" to side meetings
To: ietf@ietf.org
References: <007b01d53f2f$ef335830$cd9a0890$@olddog.co.uk> <31FFC7AF-AA65-4FC1-9F5E-9ABA6226BA10@sobco.com> <003b01d53fb7$181bae50$48530af0$@olddog.co.uk> <CAL02cgS78danBA7U32-Q=nfHMUuxfp8k4b1Zp0CvO_bJp9oUcg@mail.gmail.com> <393FED16-8C70-4ADD-BEBE-E75549CD7FF3@sobco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <89200eeb-4929-2e2e-80c1-fa79d14eb2aa@gmail.com>
Date: Mon, 22 Jul 2019 00:12:05 +1200
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: <393FED16-8C70-4ADD-BEBE-E75549CD7FF3@sobco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z6so6R1BXP8cGyrL1hm_g5D0jLQ>
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: Sun, 21 Jul 2019 12:12:10 -0000

IANAL and I think the IESG needs to get the IETF's lawyer's opinion, preferably before tomorrow morning. But given the words in the BCP, better safe than sorry.

A meeting scheduled in a room paid for as part of the IETF meeting sure seems as if it's probably intended to affect the standards process.

   Brian

On 22-Jul-19 00:02, Scott O. Bradner wrote:
> you are entitled to your opinion, of course, but I am speaking as a person who ran the BOF where the specific
> text "intended to affect the IETF Standards Process” was developed and agreed to as well as a person who 
> edited the specific text - it is my opinion that the BOF (and thus the IETF) intended the rules to apply
> wherever actions are taken or text developed that are "intended to affect the IETF Standards Process” 
> in particular, IPR disclosure is required if known
> 
> I have no opinion as to the facts of the specific case of ANRW since I have not been following that
> 
> Scott
> 
>> On Jul 21, 2019, at 7:42 AM, Richard Barnes <rlb@ipv.sx> wrote:
>>
>> Scott, I think you may be over-stating things a bit.  The IETF doesn't get to make universal statements that apply to things out of its remit.  For example, there are numerous research conferences that are held on IETF-related technologies -- often with a specific focus on providing helpful input to IETF! -- which are not held under note well.
>>
>> The location of such meetings alongside IETF meetings does not change this fact.  AFAICT, ANRW is not covered by Note Well, despite having the explicit goal of "transition[ing] research back into IETF".
>>
>> The definition of Contribution in 8179 makes this clear from the start:
>>
>> """
>> "Contribution": any submission to the IETF ...
>> """
>>
>>
>>
>> On Sun, Jul 21, 2019 at 7:27 AM Adrian Farrel <adrian@olddog.co.uk> wrote:
>> Thanks Scott, that's helpful.
>> A
>>
>> -----Original Message-----
>> From: Scott O. Bradner <sob@sobco.com> 
>> Sent: 21 July 2019 11:24
>> To: Adrian Farrel <adrian@olddog.co.uk>
>> Cc: IETF Rinse Repeat <ietf@ietf.org>
>> Subject: Re: Applying "Note Well" to side meetings
>>
>> speaking as co-editor of the ruleset
>>
>> see the definition of “Contribution” in RFC 8179
>>
>> basically, the “note well” applies whenever activities that are "intended to 
>> affect the IETF Standards Process” may happen
>>
>> Scott
>>
>>> On Jul 20, 2019, at 3:18 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>>>
>>> Hi,
>>>
>>> Normally [1] when we have a "bar BoF" (also known as a "side meeting") we do
>>> not apply the terms of the "Note Well" [2]. We have usually considered bar
>>> BoFs to be outside the IETF because the IETF has no control over who meets
>>> and drinks.
>>>
>>> However, this time around, the side meetings are somewhat more formal with
>>> room bookings and projectors and advertisements and so on.
>>>
>>> So, does the Note Well apply to these side meetings?
>>>
>>> Apologies if I missed an email on this: I sometimes don't focus as much as I
>>> should.
>>>
>>> Thanks,
>>> Adrian
>>>
>>> [1] For some practical definition of "normal"
>>> [2] https://www.ietf.org/about/note-well/
>>> --
>>> Read some fairy stories for adults of all ages
>>> .. Tales from the Wood
>>> .. More Tales from the Wood
>>> .. Tales from Beyond the Wood
>>> .. Tales from the Castle
>>> Get them on line https://www.feedaread.com/profiles/8604/
>>> Or buy a signed copy from me by post
>>> *** Stop me in the corridor at IETF-105 to get a copy ***
>>>
>>>
>>>
>>
> 
>