Re: Proposed IESG Statement on IPR Declarations

Barry Leiba <barryleiba@computer.org> Fri, 08 July 2016 17:05 UTC

Return-Path: <barryleiba@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 414E012D51F; Fri, 8 Jul 2016 10:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 rvxGNJc_y7by; Fri, 8 Jul 2016 10:05:30 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (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 3CEF412D816; Fri, 8 Jul 2016 10:05:14 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id l125so41122373ywb.2; Fri, 08 Jul 2016 10:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=GCXRsTkAlgjhDuZxeOxi83Qta4iAsQiXbdQeEIz2fAE=; b=Y6XOs6sdTExJzx+0cTf1yDOQ8fwrKL+BwqSR/w6EWRMts+7NtegQPbpZ3/xOaK9Lx5 cZvSqGd14v52uHJDXVcSmIoMKB7KvKd/PYHS3umI/HcNyqGLxh0dxX8MMzEYkAvexJKZ toYukQ4GlghQgC/iXkkt/fkA/d9HdXSU0+AD1TEXuiNvDAl1677oUp92FnGgTyYYsGCE XeU0fGPmRmFwLrvnCJehoXmqYqmpmmFEr/kVmE9DFBSpPkg1QFtPQLWuLW3r7sRVRhJA ucMnfGv/aCcnzxzmjpg9Kymh425pdofPIN2T8alMP/udyTXhmwpEiUu2nMdPPapzxXcB xmnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=GCXRsTkAlgjhDuZxeOxi83Qta4iAsQiXbdQeEIz2fAE=; b=HURZscbjW19V4mzqR6PvvkEeFopTIhvK6JOrKxfZELYI+3c31WLox8PTWUpBGBOnGD yD/Sw1IPGyH1JTQWwndxVGTsQ18IORr3WXaOEY1Sz8bkQqXFSETyJ8FguYCYBXlGBvvx Lg2xPraAsIeJnxcipn2wRCdm7pwri3D9gNzvxVnyHwCb7aU1yGy/JmHr1c2fgNX2Q2gw SoOoC7F1ACSgffBy3hNW2UEdpDrZiwHRKogf0yqs4S2lEb9TiwFaqfRcyvGWY/RrF6Sk CPUnr3tVsA8opTKB6ru5um6ycpsFTiWd2tVtEvdRGeeSWlwhdVpTucKD8gSVSd1H0Zf/ M7kA==
X-Gm-Message-State: ALyK8tKsvsTLSVs4SbNx7lzFOr91e+W94OwsSFkmfGstvZxaqxg4H76g4wKD+O4zHb2Qxw1NyHHFnXt1jbrQ2Q==
X-Received: by 10.37.3.202 with SMTP id 193mr5166958ybd.130.1467997513304; Fri, 08 Jul 2016 10:05:13 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.83.33.137 with HTTP; Fri, 8 Jul 2016 10:05:12 -0700 (PDT)
In-Reply-To: <69CA0FF8E7852A4C7C7947B5@JcK-HP8200>
References: <20160707202122.23634.18168.idtracker@ietfa.amsl.com> <CAC4RtVAEQfWN-xgtrDS0kKg6EV22hdskJKL++vsp80vi0XOjUA@mail.gmail.com> <69CA0FF8E7852A4C7C7947B5@JcK-HP8200>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 08 Jul 2016 13:05:12 -0400
X-Google-Sender-Auth: u9chaYbLcKOdvTzpA5vVcrb2_Lo
Message-ID: <CALaySJJBmpz+LRWzB5EdGpvCgr3O7eX_2bDjFeMnJF68MrgNMg@mail.gmail.com>
Subject: Re: Proposed IESG Statement on IPR Declarations
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NUV_5NufbzCUjQlVJvUqxMys-bU>
Cc: IETF discussion list <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 08 Jul 2016 17:05:32 -0000

On the third point...

> (3) When I heard that the IESG was planning an additional
> statement in this area, I assumed it would address the one
> recent claimed development that seemed to be a loose end --
> whether someone who is listed as both an inventor and a
> co-author on a document can possibly claim to not have
> reasonably have personal knowledge of a possible or perceived
> interaction between the two.   I think current version of BCP 79
> might actually be a tad weak there: such inventors not
> disclosing because of (unpublished) hair-splitting that might
> make the invention inapplicable is not in the community's
> interest.  I think the intent of BCP 79 is (or should be) that
> they disclose and, if appropriate, disclose why they don't think
> there is an interaction.    Anything else just feels a little
> sleazy and does not benefit either the IETF processes or the
> inventor -- especially given the risk that the inventor's
> company will later come along and try to enforce the patent
> against users of the IETF's spec, disclosing only after others
> build products or when the enforcement action is started.  I
> think BCP 79 allows enough latitude for a formal interpretation
> along those lines.  But this statement is completely silent on
> the matter.

I agree that clarification of that is important, but I think it's
entirely out of scope for an IESG statement, and, rather, something
that has to be addressed by the BCP 79 update work.

Barry