Re: Applying "Note Well" to side meetings
John C Klensin <john-ietf@jck.com> Sun, 21 July 2019 13:41 UTC
Return-Path: <john-ietf@jck.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 5AC51120024 for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 06:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.105
X-Spam-Level:
X-Spam-Status: No, score=-1.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_NONE=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 2MrGrhPZFuqi for <ietf@ietfa.amsl.com>; Sun, 21 Jul 2019 06:41:51 -0700 (PDT)
Received: from bsa3.jck.com (unknown [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A1C9120020 for <ietf@ietf.org>; Sun, 21 Jul 2019 06:41:51 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hpC60-0003fO-ME; Sun, 21 Jul 2019 09:41:48 -0400
Date: Sun, 21 Jul 2019 09:41:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Applying "Note Well" to side meetings
Message-ID: <794B88659DA6503122A22C9D@JcK-HP5.jck.com>
In-Reply-To: <CAMm+LwjtoyTuEJhdQCoS-_8RMWujQDUmkRSp8ETNqw-vw6rkKQ@mail.gmail.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> <89200eeb-4929-2e2e-80c1-fa79d14eb2aa@gmail.com> <CAMm+LwjtoyTuEJhdQCoS-_8RMWujQDUmkRSp8ETNqw-vw6rkKQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nZhqH0xgfbMI-Bj5nbELxdeWDoc>
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:41:53 -0000
Actually, Phill, you may well be referring to something earlier, but the case that raised (or created) awareness of the problem in the US and several SDOs who had not been paying enough attention before was ASME vs. Hydrolevel case that started in 1971 and cumulated in a US Supreme Court Decision in 1982. But the problem (which is actually at least two separate potential problems, see below) was known, and discussed in ANSI and ANDI-accredited SDOs, long before that. I would be surprised if there were not similar discussions in ISO and assorted other national standards bodies, but I was not aware of them. The ASME case was special for another reason, because is was less about IPR but about conflicts of interest in interpretation of a standard and violations of antitrust laws. As Scott has heard me say too many times and for too long, I've always been concerned that the IETF's policies concentrate almost exclusively on patent issues and disclosure and largely ignore issues that could be construed as attempts it interfere with competition or violation associated laws and regulations in relevant countries. In a way, those other issues should be even more important to the IETF. As you point out, in many cases when a standards body is used to reinforce or give some advantage to a particular patent, the patent gets invalidated (probably not enough cases, but many) hurting the patent claimant and everyone trying to use the IPR. But taking actions that can be interpreted as conspiracies to restrain trade put the IETF in jeopardy. Much of the standards community was surprised that the courts allowed ASME to continue as a standards developer because the outcome could possibly even have shut them down as a professional society. In that context, while I have no concerns about the personal integrity and ethics of any of the people involved, we now apparently have two separate Areas with more than one AD from the same company. The optics are nonetheless terrible. If someone wanted to devote time to developing an explicit code of ethics for such situations, it would probably help both the IETF and the individuals by being able to show, if questions arose, that there were explicit rules, that they were reasonable, and that they had been followed. best, john --On Sunday, 21 July, 2019 08:36 -0400 Phillip Hallam-Baker <phill@hallambaker.com> wrote: > It is worth remembering that the original concern arose out of > an episode many decades ago when a patent holder sent people > to a standards meeting to insert a requirement to make use of > technology they had an undeclared interest in.
- Applying "Note Well" to side meetings Adrian Farrel
- Re: Applying "Note Well" to side meetings Phillip Hallam-Baker
- RE: Applying "Note Well" to side meetings Adrian Farrel
- Re: Applying "Note Well" to side meetings Phillip Hallam-Baker
- Re: Applying "Note Well" to side meetings Brian E Carpenter
- Re: Applying "Note Well" to side meetings Salz, Rich
- Re: Applying "Note Well" to side meetings Scott O. Bradner
- Re: Applying "Note Well" to side meetings Richard Barnes
- RE: Applying "Note Well" to side meetings Adrian Farrel
- Re: Applying "Note Well" to side meetings Richard Barnes
- Re: Applying "Note Well" to side meetings Scott O. Bradner
- Re: Applying "Note Well" to side meetings Scott O. Bradner
- Re: Applying "Note Well" to side meetings Warren Kumari
- Re: Applying "Note Well" to side meetings Phillip Hallam-Baker
- Re: Applying "Note Well" to side meetings John C Klensin
- Re: Applying "Note Well" to side meetings Colin Perkins
- Re: Applying "Note Well" to side meetings John C Klensin
- Re: Applying "Note Well" to side meetings Scott O. Bradner
- Re: Applying "Note Well" to side meetings Colin Perkins
- Re: Applying "Note Well" to side meetings Scott O. Bradner
- Re: Applying "Note Well" to side meetings Colin Perkins
- Re: Applying "Note Well" to side meetings John C Klensin
- Re: Applying "Note Well" to side meetings Richard Barnes
- Re: Applying "Note Well" to side meetings Allison Mankin
- Re: Applying "Note Well" to side meetings Richard Barnes
- Re: Applying "Note Well" to side meetings Lars Eggert
- Re: Applying "Note Well" to side meetings Keith Moore
- Re: Applying "Note Well" to side meetings S Moonesamy
- Re: Applying "Note Well" to side meetings Colin Perkins
- Re: Applying "Note Well" to side meetings Alissa Cooper
- Re: Applying "Note Well" to side meetings John C Klensin
- RE: Applying "Note Well" to side meetings Adrian Farrel
- Re: Applying "Note Well" to side meetings Phillip Hallam-Baker
- Re: Applying "Note Well" to side meetings Nico Williams
- Re: Applying "Note Well" to side meetings Brian E Carpenter
- Re: Applying "Note Well" to side meetings Nico Williams
- Re: Applying "Note Well" to side meetings Joel M. Halpern
- Re: Applying "Note Well" to side meetings Joel M. Halpern
- Re: Applying "Note Well" to side meetings Pete Resnick