Re: Proposed IESG Statement on IPR Declarations

Jari Arkko <jari.arkko@piuha.net> Tue, 12 July 2016 22:38 UTC

Return-Path: <jari.arkko@piuha.net>
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 6538812D9B8 for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2016 15:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level:
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] autolearn=ham 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 NQnMJOyWFgeI for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2016 15:38:48 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E05F512DA74 for <ietf@ietf.org>; Tue, 12 Jul 2016 15:38:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 42B862CEFA; Wed, 13 Jul 2016 01:38:46 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qeT8NXS8cMWL; Wed, 13 Jul 2016 01:38:45 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2C7872CEF9; Wed, 13 Jul 2016 01:38:35 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: Proposed IESG Statement on IPR Declarations
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_77C509DD-32CB-4FA6-90D6-E035A29EBC26"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAC4RtVAEQfWN-xgtrDS0kKg6EV22hdskJKL++vsp80vi0XOjUA@mail.gmail.com>
Date: Wed, 13 Jul 2016 00:38:32 +0200
Message-Id: <9B54CC46-5A15-4996-B771-EB0E8AC22AFE@piuha.net>
References: <20160707202122.23634.18168.idtracker@ietfa.amsl.com> <CAC4RtVAEQfWN-xgtrDS0kKg6EV22hdskJKL++vsp80vi0XOjUA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Cv3486y-X4KkKnBH7smi0thmTzQ>
Cc: IETF discussion list <ietf@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: Tue, 12 Jul 2016 22:38:50 -0000

Barry, Brian, et al,

This is indeed not designed to be a change of procedure. And we’re open to doing this in various ways, either as an update of some text on the appropriate web page, or as initially proposed, an IESG statement.

However, I wanted to say that we received advise from IETF lawyers that highlighting that we do not check or endorse statements in the IPR declarations more visibly would be useful, even if the material is already presented in the RFCs.

A few more follow-ups:

John:

> RFC 6701 explicitly puts WG Chairs and the IESG into the
> enforcement business


RFC 6701 is about the responsibility of contributors to make
declarations. And actions if that doesn’t happen. It is *not*
about the content of those declarations, however.

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

There a number of different things we might have to do with IPRs.

Does bcp79bis (draft-bradner-rfc3979bis) cover your issue? If not,
please submit an issue to Scott and Jorge.

That document is on our plate to complete (and mostly on my plate,
Scott and Jorge are awaiting me for the next steps).

Jari