Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")

joel jaeggli <joelja@bogus.com> Mon, 04 April 2016 21:08 UTC

Return-Path: <joelja@bogus.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 F10E712D87F for <ietf@ietfa.amsl.com>; Mon, 4 Apr 2016 14:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 2PxUwD_OGsLw for <ietf@ietfa.amsl.com>; Mon, 4 Apr 2016 14:08:10 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5231312D7E6 for <ietf@ietf.org>; Mon, 4 Apr 2016 14:08:10 -0700 (PDT)
Received: from dhcp-b257.meeting.ietf.org ([IPv6:2001:67c:370:176:cdf5:5ee7:c354:d084]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u34L85wR087693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 4 Apr 2016 21:08:07 GMT (envelope-from joelja@bogus.com)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Stephan Wenger <stewe@stewe.org>, Barry Leiba <barryleiba@computer.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com> <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <dec483cf-5ee1-49dd-83a4-da2005211130@bogus.com>
Date: Mon, 4 Apr 2016 18:08:04 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qLJ8940XbkvAFCPxbq1FUuc5V0pBLN58o"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2LULCQJw2Zt7DmGbpda1LlB2mCY>
Cc: IETF <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: Mon, 04 Apr 2016 21:08:12 -0000

On 4/4/16 5:06 PM, Stephan Wenger wrote:
> Hi all,
> 
> Barry and I had a chat about this.  I also had offline conversations
> with Mike Cameron and a chat with Joel.  Barry and I at least agree on
> the problems.  The solutions are mine for now, and they absolutely are
> in need of wordsmithing...
> 
> Based on the discussion so far, there seem to be a need for the following:
> 
> 1. A clarification that an AD, by the nature of his/her office,
> regularly becomes aware of Contributions late in the process (for
> example at IETF Last Call) and, therefore, cannot be expected to
> disclose any IPR Covering those Contributions until such late time in
> the process.
> To fix this point, a simple explanatory sentence somewhere in section
> 5.2.2 would suffice.  For example “By the nature of their office, IETF
> area directors regularly become aware of Contributions late in the
> process (for example at IETF Last Call) and, therefore and in such
> cases, cannot be expected to disclose any IPR Covering those
> Contributions until such late time in the process.”
> 
> The purpose of this sentence is to protect an AD and its sponsoring
> company from allegations, both within the IETF and in courts, that they
> disclosed late against policy.
> 
> 2. A clarification or, more likely, a substantial change that, like any
> other individual in the IETF, also an AD has the option to recuse
> himself from involving himself/herself in the decision making process of
> a document, even a document in his own area. For example, an AD that did
> never comment on a document and abstained during the IETF Last Call
> would not incur a disclosure obligation, even if the Contribution were
> in his/her own area.  


I kind of have a problem with this point. it signals that you would have
to make a disclosure if you did participate. which is tantamount to
disclosing but with an extraordinarily incomplete statement.

> This second point is more tricky.  Is the formulation currently in the
> draft, which defines ADs as Participants, inline with what’s written in
> point 2?  I’m coming around to think that it does not.  Instead, I think
> we have a contradiction in the current draft—on one hand, an AD who
> intentionally stays away from influencing the decision process regarding
> a Contribution should not incur an obligation based on the underlying
> principle of the policy—no more than anyone else; but the text about ADs
> being Participants rules out that interpretation.  Having contradictions
> in patent policies is a Very Bad Idea since at least Rambus (ca. 2003).
>  Is that correct so far?
> 
> Based on the current formulation, and without violating the policy, an
> AD who is under the gun of his IPR department not to disclose a specific
> IPR has only the option to step down.  Is this what we want in each and
> every case?  Or would we rather be pragmatic and allow an AD to recuse
> himself/herself occasionally?  If yes, I think we need language
> indicating that such a mechanism is available, but also is meant to be
> used sparsely, and at least implying that ADs who are forced to use it
> more than under exceptional circumstances are indeed to step down.  
> 
> The paragraph below tries to express this.  The markup will probably
> only be visible if you choose to view the HTML version of this email.
> 
> “
> k. "Participating in an IETF discussion or activity": means making a
> Contribution, as described above, or in any other way acting in
> order to influence the outcome of a discussion relating to the
> IETF Standards Process. Without limiting the generality of the
> foregoing, acting as a working group chair or Area Director
> constitutes "Participating" in all activities of the relevant
> working groupor area. "Participant" and "IETF Participant" mean
> any individual Participating in an IETF discussion or activity.  _Under _
> _extraordinary circumstances only, an AD may choose not to Participate _
> _in the discussion or activity of his/her area, recuse himself/herself _
> _from IESG deliberations of related documents, and abstain during _
> _the IESG ballot process, thereby not incurring the obligations based_
> _on Participating._
> "  
> 
> Stephan
> 
> 
> On 4/4/16, 11:39, "barryleiba@gmail.com <mailto:barryleiba@gmail.com> on
> behalf of Barry Leiba" <barryleiba@gmail.com
> <mailto:barryleiba@gmail.com> on behalf of barryleiba@computer.org
> <mailto:barryleiba@computer.org>> wrote:
> 
>     A follow-up here:
> 
>     I'd be more comfortably with something more waffly, something more
>     like this:
> 
>     Without limiting the generality of the foregoing, acting as a working
>     group chair or Area Director can often be considered "Participating"
>     in all activities of the relevant working group or area; as such,
>     working group chairs and Area Directors are expected to make a best,
>     good-faith effort to carry out the responsibilities of Participants.
> 
>     Or perhaps we want to separate WGCs from ADs here, and the text needs
>     more work in any case, but I hope people see the general point.
> 
>     Barry
> 
>     On Mon, Apr 4, 2016 at 10:27 AM, Barry Leiba
>     <barryleiba@computer.org <mailto:barryleiba@computer.org>> wrote:
> 
>                 The "reasonably and personally aware" applies to the
>                 IPR, not to the
>                 participation.
> 
> 
>             I think this is incorrect.
> 
>             According to section 5.1.2 (disclosure requirement based on
>             Participation, not own IPR), a disclosure obligation exists
>             if “the
>             Participant believes Covers or may ultimately Cover that
>             Contribution”.  I don’t think anyone could argue that an AD
>             has a
>             “believe” in a patent or application he/she is aware of Covers a
>             Contribution when he has never seen the Contribution.
> 
> 
>         Would you accept "I didn't read the draft" as an acceptable reason
>         that someone engaged in active discussion on a draft didn't
>         disclose?
> 
>         We don't have different levels of Contributor here.  Someone
>         making a
>         Contribution has an obligation to disclose, even if s/he was one of
>         those who said, "I didn't read the draft, but...."  If we
>         declare the
>         ADs to be Contributors, why does the same not apply to them?
> 
>             A late disclosure is better than no disclosure
> 
> 
>         I hope we all agree on that!
> 
>             clearly, an AD
>             has a much better justification of making such a late
>             disclosure.  I
>             would hope that no one would complain if an AD makes a late
>             disclosure
>             and, when asked for the reason of lateness, he says “I was not
>             responsible AD; I came across this during final review in
>             IETF last
>             call, and just identified this. “  In fact, people should
>             appreciate
>             this.
> 
> 
>         Maybe so, but as it stands now in the document, it's still a late
>         disclosure, and there might still be backlash, legal concerns by
>         employers, and reluctance to put people in that position.
> 
>         If that's the consensus, then there we have it... but I think we
>         should be very careful about unintended consequences of this one.
> 
>         Barry
> 
>