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

Alissa Cooper <alissa@cooperw.in> Tue, 12 April 2016 16:50 UTC

Return-Path: <alissa@cooperw.in>
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 98D2512E663 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=q4MMsott; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=HxGp8k0I
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 0Lv5W4okUB1G for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:50:40 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3193812E0F1 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:50:40 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 9A11A217CF for <ietf@ietf.org>; Tue, 12 Apr 2016 12:50:39 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 12 Apr 2016 12:50:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=zsHqj43/DDe/pIHYndhDNbATJAE=; b=q4MMso ttACLI3xY4/F/WfsNqVy4sjC5oYXPpqN9g0cBw9YNpctigS9WJ0XZW71iJ5uZpEN 7DiBFhKvZpK4NOVfhYHu5SKUwSSN0Ox3bmbyzpirxDFb5HUScJz3Zs6zKaqR1VYs YUPdaPsosuWF0ONQYIkbNYoi/vq92dVuch1vA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=zsHqj43/DDe/pIH YndhDNbATJAE=; b=HxGp8k0I7eyqPvs7zeD2FynCWSJ5RXX2nn2F/OSzCnVSBTn d1OP9RQxaMfrr7bHgtEqbDgQv4LoCNON7EBUymXUqnHvh43ZZ9OrhB94ek12EXvC mB9HyFK4uI2x8u3j+ljCJk3J1YyAnCq/BCvlkbuUHktIKYsvVBtUMWo+V2kA=
X-Sasl-enc: mfPFxhCyDiD191XOMJty1/zKfXossdXj/7r8CIS1lp0W 1460479839
Received: from dhcp-171-68-20-116.cisco.com (dhcp-171-68-20-116.cisco.com [171.68.20.116]) by mail.messagingengine.com (Postfix) with ESMTPA id DC48BC0001E; Tue, 12 Apr 2016 12:50:38 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <65AD4D713F340D761513414F@JcK-HP8200.jck.com>
Date: Tue, 12 Apr 2016 09:50:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F79025B0-EC2E-44CB-840A-55736DBE8318@cooperw.in>
References: <65AD4D713F340D761513414F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/JFWhwIZjt467_ksyVPHp8EKipFs>
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: Tue, 12 Apr 2016 16:50:41 -0000

> On Apr 12, 2016, at 2:29 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
> 
> 
> --On Monday, April 11, 2016 15:33 -0700 Alissa Cooper
> <alissa@cooperw.in> wrote:
> 
>>> Personally, I'd love to see the draft talk about AD
>>> participation just like it talks about other people's
>>> participation. If I really haven't participated in WG X,
>>> well, I haven't, even if my co-AD owns the group :-) And if
>>> I did participate, well, I should declare the IPR that I know
>>> of :-)
>> 
>> +1
>> This is what did not make sense to me about the draft. 
> 
> Alissa,
> 
> I'm fine with the above, but I think there is a delicate line
> involved.  Let me try to explain it this way.  As a random
> member of the community, whether I'm participating in a WG, or
> even actively monitoring it, is fairly clear.  If, for example,
> I'm attending its meetings (f2f or remotely) or signed up for
> its mailing list, the community should be able to assume that
> I'm watching the work in that WG and should be required to make
> relevant IPR disclosures even if I don't actually say anything
> or otherwise generate Contributions.    If I do none of those
> things but occasionally check on mailing list archives, read
> Last Call announcements, I think the community needs to take my
> word for it if I claim to be "not participating".
> 
> I think things are a little different (but only a little) if
> there is management involvement.  If you are the AD responsible
> for a WG, then I think the community gets to assume that you
> know what its work items are, have approved document editors,
> and have at least read the abstracts of the various drafts,
> i.e., that you are participating.  If you are some other AD in
> the same area, well, areas differ a lot and over time.  In some
> cases, ADs shadow each other as a mutual backup arrangements and
> I'd expect to be able to treat all ADs in the same area as
> "participating" in all WGs.  In others, WGs get divided up among
> ADs, after which the area might as well be as many separate ones
> as there are ADs.  At IETF evaluation time, any ADs who record a
> position other that "abstain" on a spec, or to engage in any
> IESG discussion about it, has presumably studied that spec
> closely enough to incur disclosure obligations if IPR is known
> to them because making a decision to adopt (or not) is clearly
> "participation".  The same issue might exist with Co-chairs of a
> WG with many tasks.  I'd normally assume that each one is
> familiar with and participating in every work item, but it isn't
> hard to imagine situations in which work might be split up along
> clear boundaries with one co-chair getting involved in the work
> of the other only at around the time of Last Call if then.
> 
> All of that said, I think that trying to create a collection of
> very specific rules or definitions to cover each case and
> variations on it is almost certain to cause more harm than good.
> I think the intent of the rules -- that anyone who has
> contributed to a spec or put themselves in a position in which
> they influence an IETF decision to adopt (or not) or publish (or
> not) has disclosure obligations (whether direct or third-party
> as discussed in the I-D). My expectation is that WG Chairs and,
> to even a greater extent, ADs, will be sensitive to the intent
> of the rules.  To do otherwise would be a breach of the trust
> the community placed in them and that would be at least as
> serious, perhaps more, than breaching the letter of the IPR
> rules.   
> 
> If we need rule changes in that area, they probably lie in
> making recalls more feasible rather than more case analysis in
> the IPR document(s).   If the latter documents need anything
> extra, perhaps it is an explicit statement to the effect of
> "Because of the trust the community places in them and the
> consensus-determination and decision authority associated with
> their positions, IETF Leadership including WG Chairs and Nomcom
> appointees are expected to be especially diligent in observing
> the intent of these rules”.  

WFM
Alissa

> 
> best.
>     john
> 
> 
>