Re: Applying "Note Well" to side meetings

"Scott O. Bradner" <sob@sobco.com> Sun, 21 July 2019 13:53 UTC

Return-Path: <sob@sobco.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 ED862120024 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 06:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level:
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 i63Hx48w9Ylj for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 06:53:51 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 09CF4120019 for <ietf@ietf.org>; Sun, 21 Jul 2019 06:53:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 80F031804903; Sun, 21 Jul 2019 09:53:48 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EgszKxhJuoXf; Sun, 21 Jul 2019 09:53:38 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 5D9F618048EF; Sun, 21 Jul 2019 09:53:38 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Applying "Note Well" to side meetings
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <E67E41AB-098E-4149-BA26-E73D70F571FB@csperkins.org>
Date: Sun, 21 Jul 2019 09:53:37 -0400
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B571E29-4534-4FDD-AB38-7E04E7A589CB@sobco.com>
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> <BDEB9199-DD31-4098-B649-E9FF6AD7F7A7@sobco.com> <13771141-8AB9-4249-A2A3-A4684A74A33A@csperkins.org> <899ABA3E-890E-4EF3-A621-0A53CF1A7ED3@sobco.com> <E67E41AB-098E-4149-BA26-E73D70F571FB@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xnihskgoZYJd4hOMBSNQK2emjLk>
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 13:53:53 -0000

sorry, I was confused by the meeting at the IETF - I expect I’m not the only one based on the discussion - maybe the first slide needs to say 

	“THIS IS NOT AN IRTF RG”

Scott



> On Jul 21, 2019, at 9:46 AM, Colin Perkins <csp@csperkins.org> wrote:
> 
> Since the ANRW is an academic conference, we made the decision to follow the usual norms for such events and not require IPR disclosure. 
> 
> If the work is brought into an IRTF RG, or an IETF WG, then the usual IRTF and IETF IPR disclosure rules apply.
> 
> Colin
> 
> 
>> On 21 Jul 2019, at 09:41, Scott O. Bradner <sob@sobco.com> wrote:
>> 
>> you made an explicit decision that people can hide their IPR?
>> 
>> have fun with that
>> 
>> Scott
>> 
>>> On Jul 21, 2019, at 9:36 AM, Colin Perkins <csp@csperkins.org> wrote:
>>> 
>>> The ANRW is an academic workshop that happens to be co-located with IETF. We made an explicit decision when starting the workshop, several years ago now, that the Note Well does not apply to it. 
>>> 
>>> If work is brought from ANRW into either an IRTF RG or an IETF WG, then the Note Well would apply, of course.
>>> 
>>> Colin
>>> 
>>> 
>>> 
>>>> On 21 Jul 2019, at 08:08, Scott O. Bradner <sob@sobco.com> wrote:
>>>> 
>>>> ps - I see that ANRW is an IRTF research group - thus https://irtf.org/ipr applies 
>>>> (and that says that the IETF rules apply)
>>>> 
>>>> Scott
>>>> 
>>>> 
>>>>> On Jul 21, 2019, at 8:02 AM, Scott O. Bradner <sob@sobco.com> 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 ***
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Colin Perkins
>>> https://csperkins.org/
>>> 
>>> 
>>> 
>>> 
>> 
> 
> 
> 
> -- 
> Colin Perkins
> https://csperkins.org/
> 
> 
> 
>