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

Sam Hartman <hartmans-ietf@mit.edu> Mon, 28 March 2016 16:16 UTC

Return-Path: <hartmans-ietf@mit.edu>
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 B0FA112DBA2 for <ietf@ietfa.amsl.com>; Mon, 28 Mar 2016 09:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no 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 5S_YAl3jaNqy for <ietf@ietfa.amsl.com>; Mon, 28 Mar 2016 09:16:00 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81CE012DB91 for <ietf@ietf.org>; Mon, 28 Mar 2016 09:16:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 3BBCD20B74; Mon, 28 Mar 2016 12:12:56 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uQiVZH85N2Os; Mon, 28 Mar 2016 12:12:55 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 28 Mar 2016 12:12:55 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 618F687221; Mon, 28 Mar 2016 12:15:58 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <DC9B799D-A1EF-457C-B791-9F103FDA7CD6@vigilsec.com> <56F59441.8030901@gmail.com> <FDF935D9B80D3F03F2A93CD8@JcK-HP8200.jck.com> <tsl4mbuxpbd.fsf@mit.edu> <AD6EE22C0DAB6A509C75EDBB@JcK-HP8200.jck.com>
Date: Mon, 28 Mar 2016 12:15:58 -0400
In-Reply-To: <AD6EE22C0DAB6A509C75EDBB@JcK-HP8200.jck.com> (John C. Klensin's message of "Fri, 25 Mar 2016 17:55:07 -0400")
Message-ID: <tsllh52varl.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4UWpQV5NPKneGPu7NTw8oal0TAU>
Cc: Sam Hartman <hartmans-ietf@mit.edu>, 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, 28 Mar 2016 16:16:01 -0000

>>>>> "John" == John C Klensin <john-ietf@jck.com> writes:

    John> Ok, Sam,

    John> How do you feel about documents created in a group with some
    John> other name, even if all the participants are active in the
    John> IETF, creating an implementation or two, and then bringing the
    John> spec to the IETF and saying "standardize this, but the spec is
    John> fully-baked and deployed so you can't change it much without a
    John> lot of justification"?  We've seen that happen multiple times.
    John> IMO, most of them were for other reasons but, if someone has
    John> bad intentions toward the IETF disclosure rules, that is the
    John> obvious mechanism for them to use and it results in much later
    John> disclosure than you would like, with no IETF ability to claim
    John> that people were obligated to disclose earlier.

I'm much more comfortable with this actually.  See, I know that if I
participate in such an effort I'm not working under IETF IPR rules.
Again for me, especially when I'm contributing as an individual rather
than being funded by someone, it's a question of whether we're creating
a commons together.  You want my time, you disclose before you advocate
your proposal.
It's important to me I be able to make that stick.