Re: Proposed IESG Statement on IPR Declarations

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 13 July 2016 06:37 UTC

Return-Path: <brian.e.carpenter@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 206C112DADD for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2016 23:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 iXK79p-2uNIW for <ietf@ietfa.amsl.com>; Tue, 12 Jul 2016 23:37:43 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 7D8BD12DB07 for <ietf@ietf.org>; Tue, 12 Jul 2016 23:37:41 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id o80so53054616wme.1 for <ietf@ietf.org>; Tue, 12 Jul 2016 23:37:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=qaXWkIbrBvr6Q7XRHxml/vEDD0z/bs7A3Arlq18YPl4=; b=KQfIadcVRyoS7AMMyRqEQa1tzZbGZudrC4nA00tLtVBszGxolNy/Ag9EeQn51S+vGR 0WiDqJTE0R9XOX2AEUmkhYivQIG2qldGn1jnn8Y0fIAMcUEpjSmgDbrgq/NFuqkvuRa5 Jm657qv5mNbiUPVJWqb74Wmd2yh3IkO8DoDbpHBTz4EfBTseiLZAOvA6djAhuWckD17q 3WE5omjTSUcyrJ5uaSUh0W+T9s3ADrJvbzrgiiBltYcthyakPnHFu7wFNoxgHoqmyZ7v k+Fzid8zqqm399f6oqq8HQKkxZODTDSRk8fg4DMj/0KRlguGpdar/1+3nhUPx1JA+TOV eY5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=qaXWkIbrBvr6Q7XRHxml/vEDD0z/bs7A3Arlq18YPl4=; b=HMIXziWVgMi5SO5w2uHsb6UtZHuTcXc4mM/i5BKqtkJl3y9rI/zf6JTHjfwVep5hvG PxH0S4V079rHh3y3FCh/aqGhs84cyTlI2VXyXhpSSVa0Xnk9RJWd/omrrZoTTLkek3kU WBJ4/189kC5kYe36fQoyjwvU+N9f9e4HCafCntxumxzM2asvY0+ZFkK56xzRpqQdpJnT wWJkwzd/81wEjh+b/HUfc5vWu3vUEXleGiCBGcKwGhR3+Uc82WTk9uTYMpRRiYDo2gv7 OLNt+k/CeSZRvaB2rfOlffJlrfTXiZpp9pOWfaKIXa/3Y9B9y85+8vjCRDephkJGi26q f8vA==
X-Gm-Message-State: ALyK8tI46xRCfF9Rk09OgOkGlj+wmSbnRHalS115LQmSRv/rwkaQjKy2SOwLRW24mxjUPQ==
X-Received: by 10.28.10.66 with SMTP id 63mr26316788wmk.54.1468391860021; Tue, 12 Jul 2016 23:37:40 -0700 (PDT)
Received: from [10.0.1.29] (cpc66883-mort6-2-0-cust696.19-2.cable.virginm.net. [92.233.126.185]) by smtp.gmail.com with ESMTPSA id i195sm9636886wmg.1.2016.07.12.23.37.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Jul 2016 23:37:39 -0700 (PDT)
Subject: Re: Proposed IESG Statement on IPR Declarations
To: Jari Arkko <jari.arkko@piuha.net>, Barry Leiba <barryleiba@computer.org>, John C Klensin <john-ietf@jck.com>
References: <20160707202122.23634.18168.idtracker@ietfa.amsl.com> <CAC4RtVAEQfWN-xgtrDS0kKg6EV22hdskJKL++vsp80vi0XOjUA@mail.gmail.com> <9B54CC46-5A15-4996-B771-EB0E8AC22AFE@piuha.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b408d38f-504d-9cf4-98d0-f5c93c534551@gmail.com>
Date: Wed, 13 Jul 2016 18:37:43 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <9B54CC46-5A15-4996-B771-EB0E8AC22AFE@piuha.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UQFx-OHanpzk4X4jTL-8kYSEoGc>
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: Wed, 13 Jul 2016 06:37:47 -0000

On 13/07/2016 10:38, Jari Arkko wrote:
> 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.

Understood. But surely https://datatracker.ietf.org/ipr/... is the most visible place
to do that.

    Brian

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