Re: Applying "Note Well" to side meetings

Richard Barnes <rlb@ipv.sx> Sun, 21 July 2019 14:02 UTC

Return-Path: <rlb@ipv.sx>
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 1A1C1120129 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 07:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 g6AD621oKa5V for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 07:02:29 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 C4C5512004E for <ietf@ietf.org>; Sun, 21 Jul 2019 07:02:29 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id q20so37471442otl.0 for <ietf@ietf.org>; Sun, 21 Jul 2019 07:02:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=izEnEzb4EvASCKyuWLCSeWvlFpaZ7zz1FNXVYaUJ9+s=; b=KpwWAPa6Dps8Y7svKDRAwLGRJfuHO8yqStf+tXb/nTwoAPkx/6Wv8Ft5t+ViUmtU8L Ns12aCtazdWGPqd+0oGLg8TjsWkt1UrrvutOVNXqOV2j2cC9Q3EFF0mkqFuc1+O9zeUw fKBRqqVPsgXW4Ym/6khVZ9XLbx1d+y8/AD2VaVJi5bkYv2iJN3GztXGatEY+G+DlSeOO rmj18tnt+x+P0kiRYrvhXcGTBBvSASQjcEBC6jX9u3iGvupJp8+8Bhcj/q50XpCFsPKf TaHBuNXb46IGABFBvUmMsOa3D0OYNMdXroWFuTvJ/XqMxFRGY7Mczp7t7yKx7/ASerfl MARg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=izEnEzb4EvASCKyuWLCSeWvlFpaZ7zz1FNXVYaUJ9+s=; b=OSBZvvaNCsdQbfUK/i7ECZtPK2HLZMIXAgNqdGrrwKucOwz9Vx9BKuDMghDIjH24VQ vqtZURXqQpsm8te/OjHUiuoI4NZc5F7zA2LZXBr8NtpRv9XRi/VsAIHPTkpryFSnZNjo KIs48GYZv6XMq+7nP7sO13Vn4Jx750ZptjeeN8MoPYPDLxpQaEDABdRYXTwExjYzbExT FfOc5qUlEtXJueei2b7zafyqqoeyma5IycW0/+yNjafeY1cpbjD0BfxZnvIT25egNr1C cAExJ8+Pl+dafKOgqYSmIzevgFa3LJF+k61HX73ir8NA3w2qYcTHL8JDk5XitjVrGAuS Cdqw==
X-Gm-Message-State: APjAAAXUEy8EPSmGxJkZkBme5V9pStfL0J5trKzQqUEafznLJIJ0QD2a 6POMi6tgAWUPggtQd8gA5h8NrMO1FnZKqWhiu8g=
X-Google-Smtp-Source: APXvYqycPq5G7SbE84g2TLSQ+EvZ0oWbFhhIi0vlsjI+y7VTLreJrSxQD+WRgFcZrpId3ea+8aVGB8UDhaXtdD0HVkk=
X-Received: by 2002:a9d:5911:: with SMTP id t17mr45920982oth.159.1563717748877; Sun, 21 Jul 2019 07:02:28 -0700 (PDT)
MIME-Version: 1.0
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> <6B571E29-4534-4FDD-AB38-7E04E7A589CB@sobco.com>
In-Reply-To: <6B571E29-4534-4FDD-AB38-7E04E7A589CB@sobco.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Sun, 21 Jul 2019 10:02:08 -0400
Message-ID: <CAL02cgQR5n_f=X27UoxTVesJskeBy6FmYq8SSj=C=UM3nfydzw@mail.gmail.com>
Subject: Re: Applying "Note Well" to side meetings
To: "Scott O. Bradner" <sob@sobco.com>
Cc: Colin Perkins <csp@csperkins.org>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f37b40058e316891"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sOZXW6vCx90qH1noBpSxnH8tJXc>
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 14:02:33 -0000

Great, so unless anyone wants to tell Colin that ANRW needs to adopt the
Note Well, we've validated that side meetings held alongside IETF can have
their own IPR rules.

To Warren's "don't be a jerk" point -- this absolutely doesn't mean that
people *shouldn't* disclose their IPR, it just means they're not
*obligated* to, in the sense of RFC 8179.

--Richard


On Sun, Jul 21, 2019 at 9:54 AM Scott O. Bradner <sob@sobco.com> wrote:

> 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/
> >
> >
> >
> >
>
>