Re: Proposed New Note Well
Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 04 January 2016 21:31 UTC
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7447D1AC3BF; Mon, 4 Jan 2016 13:31:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Q9LZQCPNKLAz; Mon, 4 Jan 2016 13:31:12 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 F24501AC3BA; Mon, 4 Jan 2016 13:31:11 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id q63so172068273pfb.0; Mon, 04 Jan 2016 13:31:11 -0800 (PST)
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-type :content-transfer-encoding; bh=qbqxnAf1VdPT9ZGCFhAXM5yTteXhpZKNzkk4RIJ+PnQ=; b=wRI4pszzVbQBTTM2rSm4CZCKXkwmRB1mE76+Diu3GjnXG+uA/j1/TwJkC9A3eBUbSV LRB3v/SFtzMoBulSh9u/ivKi39h3qF9v4JJzX7XSkzJ8d+ywTtlRS6MAhpZq1ic5XUZK Dps1Cl1XWofLCTnBXFZ9BIfl4D/IGOmn16Uars7AXkRWOp1O8qn1v5s2Tflx+K4IRzKX a0KWGmJHF4w88cD79mQrxhSeCBfniJopPrizFJjcqMNisC4Qk2NIec9aZZZ3kmxchvRn 7A+RZ3CesfPQB40qMLl+rD1R9caEsKBbS45kgrmRVy5ZK9J9Mciu+MxXIZe49Vuoi9zV Qtag==
X-Received: by 10.98.67.67 with SMTP id q64mr58822329pfa.133.1451943071631; Mon, 04 Jan 2016 13:31:11 -0800 (PST)
Received: from ?IPv6:2406:e007:51d5:1:28cc:dc4c:9703:6781? ([2406:e007:51d5:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 6sm65477421pfm.46.2016.01.04.13.31.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jan 2016 13:31:10 -0800 (PST)
Subject: Re: Proposed New Note Well
To: "Scott O. Bradner" <sob@sobco.com>, "John C. Klensin" <john-ietf@jck.com>
References: <20160104154102.1127.50621.idtracker@ietfa.amsl.com> <568AC7FE.101@gmail.com> <6451D0B3-9B0C-475E-B178-98E9EB6FD7D9@sobco.com> <11ED7904-3309-4B87-B8A4-7C4663C1AC30@sobco.com> <6EC907910707D24C66FF601E@JcK-HP8200.jck.com> <B8C14BAA-699A-4890-9A1C-B227D07CC5B3@sobco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <568AE4B0.7060700@gmail.com>
Date: Tue, 05 Jan 2016 10:31:28 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <B8C14BAA-699A-4890-9A1C-B227D07CC5B3@sobco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ddVwqbHlfGh57rHaOz1q9qm4aHU>
Cc: IETF <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 04 Jan 2016 21:31:14 -0000
On 05/01/2016 09:36, Scott O. Bradner wrote: > >> On Jan 4, 2016, at 3:21 PM, John C Klensin <john-ietf@jck.com> wrote: >> >> Scott, >> >> I think this actually muddies the issue. We've actually got two >> separate disclosure rules. Summarizing them in different >> language (and after reviewing what is in the RFCs), they are: >> >> (1) If you are personally involved with a patent and/or you or >> your organization claim ownership or some other beneficial >> interest in it that you know about (or might reasonably be >> expected to know about), then you are _required_ to disclose. > > unless you do not “participate” in the standards process relating to that IPR > (see RFC 3979 section 6.1.2 - only binding on a person participating in a discussion) > > this is the issue that stalled the previous attempt by the IESG to redo the Note Well > the previous version stated the requirement as you did - an absolute requirement > to disclose if you have knowledge of “your” iPR - a number of people pointed > out that this was not a accurate description of the rules > > also the “benefit” language was trying to help with the “owns” case - it is not just that you > or your organization owns the patent - it also covers the case where you or your organization > has the right to license the patent to others and the case where you or your or your organization > will receive money (or other consideration) from some party who has the right to license the patent to others To be clear, adding a legally precise definition of the "benefits from" case to BCP 79 would, IMHO, be a good idea. But since it is not currently defined there, the proposed Note Well language, IMHO, misrepresents what the BCP says. IANAL, so a view on this from an experienced IPR litigator would be useful. Brian > > >> >> (2) If (1) does not apply but you happen to know about the >> patent claims anyway, you are encouraged to disclose but are >> under no formal requirement to do so. >> >> The second is particularly important to those of us who might >> get a call from someone saying "TrollCo claims it has patent >> rights that cover such-and-such. Do you have an opinion about >> that with regard to either applicability or validity?" Because >> even the asking of questions like that may be covered by NDAs, >> the exact IETF requirements are fairly important. > > yup - I’m well in that boat myself > >> >> As usual, what this suggests to me is that the Note Well should >> avoid saying things that are misleading. > > or leave things out in a way that is misleading > > Scott > >> That, in turn, means >> either sticking to general advice and pointing to the relevant >> documents (in that sense, this attempted revision seems to be a >> step in the right direction) or being very specific and precise. >> The proposed language in this area seems to be neither. >> >> Similarly, >> >> >> >> --On Tuesday, January 05, 2016 08:37 +1300 Brian E Carpenter >> <brian.e.carpenter@gmail.com> wrote: >> >>> On 05/01/2016 05:05, John C Klensin wrote: >>> ... >>>> In particular, don't say "By participating with the >>>> IETF, you agree to follow IETF processes and policies" and >>>> then identify only a few of them as if they were the complete >>>> list. >>> >>> I thought about trying to express that in my rewrite, but >>> couldn't see an easy way to cover it. As I repeat from time to >>> time, the hard way to cover it is >>> http://www.ietf.org/about/process-docs.html . Good luck in >>> trying to summarise that for the Note Well. >> >> But that suggests that either the Note Well should be about IPR >> and should say to, possibly adding a sentence there are lots of >> important non-IPR policies of which people need to be aware or, >> difficult or not, it should be comprehensive. Picking one >> handful of policies and ignoring others seems like a recipe for >> trouble unless the boundary or stopping rule is clearly >> identified. As you suggest above, good luck with that >> delineation as well as with the comprehensive summary. >> >> john >> >> >> >> >> --On Monday, January 04, 2016 14:48 -0500 "Scott O. Bradner" >> <sob@sobco.com> wrote: >> >>> ps - stated better in RFC 3979 sec 6.6 >>> >>> 6.6. When is a Disclosure Required? >>> >>> IPR disclosures under Sections 6.1.1. and 6.1.2 are >>> required with respect to IPR that is owned directly or >>> indirectly, by the individual or his/her employer or >>> sponsor (if any) or that such persons otherwise have the >>> right to license or assert. >>> >>> >>>> On Jan 4, 2016, at 2:41 PM, Scott O. Bradner <sob@sobco.com> >>>> wrote: >>>> >>>> >>>>>> • If you are aware that any contribution to the IETF is >>>>>> covered by patents or patent applications that are owned >>>>>> by, controlled by, or would benefit you or your sponsor, >>>>>> you must disclose that fact, or not participate in the >>>>>> discussion. >>>>> >>>>> Where does "or would benefit" come from in BCP 79? While I >>>>> agree with the sentiment, I don't think it follows from our >>>>> rules, so I think it must be deleted. >>>> >>>> the concept comes from (for example) RFC 3979 section 6.1.3 >>>> 6.1.3. IPR of Others >>>> >>>> If a person has information about IPR that may Cover IETF >>>> Contributions, but the participant is not required to >>>> disclose because they do not meet the criteria in Section >>>> 6.6 (e.g., the IPR is owned by some other company), such >>>> person is encouraged to notify the IETF by sending an email >>>> message to ietf-ipr@ietf.org. Such a notice should be sent >>>> as soon as reasonably possible after the person realizes >>>> the connection. >>>> >>>> i.e. the text is trying to deal with the case where you know >>>> of IPR but it is not "yours" >>>> >>>> this seemed to be a clean way to express the condition - just >>>> eliminating the phrase would, imo, make it harder to >>>> understand when disclosure is required - other ways to get >>>> the point across would be helpful >>>> >>>> Scott >>>> >>>> >>>> >>> >> >> >> >> > > . >
- Re: Proposed New Note Well Ted Lemon
- Proposed New Note Well IESG Secretary
- RE: Proposed New Note Well Adrian Farrel
- Re: Proposed New Note Well John C Klensin
- Re: Proposed New Note Well Doug Ewell
- Re: Proposed New Note Well Brian E Carpenter
- Re: Proposed New Note Well Brian E Carpenter
- Re: Proposed New Note Well Scott O. Bradner
- Re: Proposed New Note Well Scott O. Bradner
- Re: Proposed New Note Well John C Klensin
- Re: Proposed New Note Well Scott O. Bradner
- Re: Proposed New Note Well Mark Nottingham
- Re: Proposed New Note Well Dave Cridland
- Re: Proposed New Note Well Brian E Carpenter
- Re: Proposed New Note Well Stephan Wenger
- Re: Proposed New Note Well Jorge Contreras
- Re: Proposed New Note Well Jorge Contreras
- Re: Proposed New Note Well Brian E Carpenter
- Re: Proposed New Note Well Stephan Wenger
- Re: Proposed New Note Well Harald Alvestrand
- Contributions (Re: Proposed New Note Well) Harald Alvestrand
- Re: Proposed New Note Well John C Klensin
- Re: Proposed New Note Well Brian E Carpenter
- Re: Proposed New Note Well Stephan Wenger
- Re: Proposed New Note Well lloyd.wood
- Re: Proposed New Note Well Stephan Wenger
- Re: Proposed New Note Well Scott O. Bradner
- Re: Proposed New Note Well Scott O. Bradner
- Re: Proposed New Note Well Abdussalam Baryun
- Re: Proposed New Note Well Pete Resnick
- Re: Proposed New Note Well Scott Bradner
- Re: Proposed New Note Well Tim Chown
- Re: Proposed New Note Well Pete Resnick
- Re: Proposed New Note Well John C Klensin