Re: Possible RFC 3683 PR-action

jnc@mercury.lcs.mit.edu (Noel Chiappa) Wed, 26 March 2008 00:31 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1058028C266; Tue, 25 Mar 2008 17:31:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.973
X-Spam-Level:
X-Spam-Status: No, score=-100.973 tagged_above=-999 required=5 tests=[AWL=-0.536, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jf90-q8tVzGq; Tue, 25 Mar 2008 17:31:43 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23CD53A6A5E; Tue, 25 Mar 2008 17:31:43 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61A0C3A6A5E for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 17:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gJBc5bFNRDCJ for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 17:31:41 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id A046D3A6838 for <ietf@ietf.org>; Tue, 25 Mar 2008 17:31:41 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 672A1872F5; Tue, 25 Mar 2008 20:29:11 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Possible RFC 3683 PR-action
Message-Id: <20080326002911.672A1872F5@mercury.lcs.mit.edu>
Date: Tue, 25 Mar 2008 20:29:11 -0400
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

    > From: "Hallam-Baker, Phillip" <pbaker@verisign.com>

    > If someone participates under a pseudonym with the objective of
    > inserting patented technology and anyone finds out they are in big
    > trouble. Much worse than any prior case.

We should write in our rules that anyone who contributes technology to any
IETF activity which they know to be either a) patented, b) the subject of a
filing, or c) the subject of a planned future filing, *without disclosing said
patent status* to the WG/I*, either:

- i) thereby grants an irrevocable, in perpetuity, no-fee license to use said
patent(s) to everyone in connection with any implementation of any IETF
specification resulting from said activity (if they are in any kind of
position to do so, e.g. are an employee of the patent holder),

or:

- ii) agrees to indemnify anyone in the universe for any costs they may incur
through use of said patent(s) in connection with any implementation of any
IETF specification resulting from said activity (if they aren't).

That oughta go a long way to fixing *that* problem.

(And if our IP rules, which I haven't looked at recently, already said that,
my apologies, and don't kick me too hard! :-)

	Noel
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf