Re: Applying "Note Well" to side meetings

Richard Barnes <rlb@ipv.sx> Sun, 21 July 2019 14:04 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 7B62F120089 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 07:04:38 -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 Hv96giCj0xzC for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 07:04:35 -0700 (PDT)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (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 E7FB812004E for <ietf@ietf.org>; Sun, 21 Jul 2019 07:04:34 -0700 (PDT)
Received: by mail-ot1-x332.google.com with SMTP id b7so37428201otl.11 for <ietf@ietf.org>; Sun, 21 Jul 2019 07:04:34 -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=ylFJkXwexAVnyl//rbAMuR2Dvt9qqck8jSUm4AwMCYQ=; b=zvM+vG7OH3tQVGZKSPSqC0r7lU2krjfyq7NrWhtgPTWELyNZP6VSRM6C7htOQnCjiL okUQdWuPC+WnHRpm7y2M8mv3poO3GRP2jF5oICnfpnA2fulY+hWXYrpsbzZ7Ln5gCri+ 2UXJ/nVPYMHgrgnXO03npM+IOqGIS4R9JgfVMYDq1uKyIMSY+wTSKDGNyZW8+/18Y8CA MzQbN6YzjNC6kVBH9Vialx1TZSU+BhuZlczBw1DGPreBBufxW4Sur7w9Wn5O+flm0fGs BCbX+0A78ecXCWD1taxz6QpsEo0HhzSek+Qdf7tyf9HvyD2zxSMNm11zzH3iHA1FM1wc ScUw==
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=ylFJkXwexAVnyl//rbAMuR2Dvt9qqck8jSUm4AwMCYQ=; b=N2J4u2oecmSruStUn+RwiRNCDoIyUzvpL/dXutRk6mHVdIf/OzlFGg5aDi5oBS3E1z KlR0R/1u/dvYQJqkQ4NLdm1x7buW51KQEwFGHQK7z5b+TlGQPvoNIqIK/TsDs/38HMEB Inu2eKnQICcbQ825+sjibX6WNwlMpGUHw0jrjb5CKnrJjwAx8br2WKHPN6AxbubKG2Ht 5zJ2beMDw1HAn4dx2+nzxBwhjlLG/6685Xhny8rs/MisSeCF2UTK+lN0EYnbDGgnxHeG qRWvqhdpW1v/K+dUhBXgk3htjjOKajj9VnHNS8eW4/1QWTpzF1s0Wx2oGd7WIwxg6TnD Icuw==
X-Gm-Message-State: APjAAAWKD9NpULUqC3quqLFYfEDCdAOx/gqt9ElAXTXOvpLdQlLTXDJe u24nWpEZDtwchu2tpA8GjBAqG5Wulu5dWIiuCYw=
X-Google-Smtp-Source: APXvYqyJKjzz5oK0EiAY526QbAimyKspuw8EXOB/gEmP9w9YQR0Q4kzJh6V2mDWl5qR60H2K42GqgI7oPzSohUQ+EgQ=
X-Received: by 2002:a05:6830:1542:: with SMTP id l2mr9249988otp.241.1563717874101; Sun, 21 Jul 2019 07:04:34 -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> <AD1396F5FBA60873B976B164@JcK-HP5.jck.com>
In-Reply-To: <AD1396F5FBA60873B976B164@JcK-HP5.jck.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Sun, 21 Jul 2019 10:04:14 -0400
Message-ID: <CAL02cgTXVDLyCA5XB2NFoiFFzyPAdJrqB-kH18yMoB3KLkhwjQ@mail.gmail.com>
Subject: Re: Applying "Note Well" to side meetings
To: John C Klensin <john-ietf@jck.com>
Cc: Colin Perkins <csp@csperkins.org>, "Scott O. Bradner" <sob@sobco.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a42b3058e3170c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iiCHMiBDVWRZDSHH5BuF736Jq0s>
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:04:39 -0000

On Sun, Jul 21, 2019 at 10:02 AM John C Klensin <john-ietf@jck.com> wrote:

> Colin,
>
> The problem is that, if ANSW is an IRTF group and/or it is using
> facilities that are supported in any way by the IETF (probably
> including such things as discounts on hotel or meeting rooms due
> to the IETF contract), you don't get to decide, any more than
> you get to decide that whatever rule Montreal has about public
> drunkenness don't apply.


John: Do you have a citation for this?  It seems like if there were a
document that said, "A meeting that in any way using facilities that are
supported in any way by the IETF is subject to the Note Well", that would
be dispositive.  And if not, there's no obligation.

--Richard



> If you want to be exempt, don't
> co-locate or use IETF facilities and consult with the IAB, the
> IETF LLC, and appropriate lawyers as to whether other measures
> are appropriate.
>
> Phill's comments about concealing the existence of patents
> (pending or granted) in order to strengthen their position in
> the marketplace would apply whether the IETF has its IPR rules
> or not.
>
> Long ago, almost certainly before IASA 1.0, the IETF had a
> fairly firm rule about pre-organized side meetings which were
> not part of the IETF process.  They were not allowed to use
> _any_ IETF-provided or related resource or facilities.
> Concurrent or co-located meetings were discouraged, cards
> announcing such meetings were taken off announcement bulletin
> boards, companies wanting to hold staff meeting or do recruiting
> were told use a different hotel or other location, and so on.
> Just "no".     I never asked, but assumed that was done on
> advice of counsel because it kept the lines extremely clear.  If
> it was, I can even guess at the name of the relevant lawyer.
>
> Coming back to my response to Warren, I fear that we are
> behaving in a way that encourages trying to draw fine lines and
> hair-splitting.  I don't think that is good for the IETF
> generally.   Given that some to the issues could involve acts
> that are criminal in some locations and that courts might
> disagree with how we split those hairs, I also hope that ADs,
> IETF LLC Board members, and anyone similarly situated how gotten
> advice from their lawyers about potential risks.
>
> (my last posting on this thread before I get to Montreal)
>
> best,
>   john
>
> --On Sunday, 21 July, 2019 09:36 -0400 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 ***
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
>
>
>
>
>