Re: RIM patents using a mime body in a message (and ignores IETF IPR rules)

Scott Brim <scott.brim@gmail.com> Mon, 30 November 2009 21:33 UTC

Return-Path: <scott.brim@gmail.com>
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 764B128C0D7 for <ietf@core3.amsl.com>; Mon, 30 Nov 2009 13:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level:
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599]
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 1FFZvRlGgMwC for <ietf@core3.amsl.com>; Mon, 30 Nov 2009 13:33:51 -0800 (PST)
Received: from mail-vw0-f184.google.com (mail-vw0-f184.google.com [209.85.212.184]) by core3.amsl.com (Postfix) with ESMTP id A538728C0D6 for <ietf@ietf.org>; Mon, 30 Nov 2009 13:33:51 -0800 (PST)
Received: by vws14 with SMTP id 14so1403339vws.32 for <ietf@ietf.org>; Mon, 30 Nov 2009 13:33:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=UDeMEhlRr/BBoUrVS1+HaJ85YMEgFDpVd87TlJpwTcY=; b=Q7uIZRiNxaPlwqV1szBylo7NmPsdNoQRkMeilKGuYJdnATSKaHqlVso7ByOYlwH7lr VnyZ42/77B5bSqhhS9dp+YPbZi6qrmNnKSCTrYhoQG+3mX6J39QAwF3lb7dRjL2zLBv8 iUa5E3u2Yjj0ahjhiaugeyS5K00QNh0UW1jWM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=UkBR9EVKJBEWfeMU9wt9AbGcUEbJDhWSf68LjkygRLA5K4IPMzm8askgB0j7xIRnRK GVAnvjO2MMFpytV60X4s9iQ+8RUH2v/WyXzxJBbAz1rOm+DMD4vRoPZSrXm1X44Fl7pm irYmWakblun2Y5H0cVtaCuxBfsyj/KNesTuoY=
Received: by 10.220.122.213 with SMTP id m21mr452129vcr.86.1259616821806; Mon, 30 Nov 2009 13:33:41 -0800 (PST)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 21sm7903481vws.7.2009.11.30.13.33.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 30 Nov 2009 13:33:40 -0800 (PST)
Message-ID: <4B143A31.2070707@gmail.com>
Date: Mon, 30 Nov 2009 16:33:37 -0500
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
Subject: Re: RIM patents using a mime body in a message (and ignores IETF IPR rules)
References: <487AB12E-FD4A-4AD5-8641-17B4B64C6F8F@cisco.com> <4B04A9C5.6060904@gmail.com> <5F5E5CDB0670267DF04D9561@PST.JCK.COM> <01NG9VCEWETC0002QL@mauve.mrochek.com> <A6741735F236784CBB00AAD60DCED23F034FE5CB@XCH02DFW.rim.net> <20091120151251.B04DCF2403F@odin.smetech.net> <87iqd1v9qq.fsf@mocca.josefsson.org> <4B0A8B41.30005@gmail.com> <20091123124442.46510698@gg1.cs.columbia.edu> <4B11A797.5080905@gmail.com> <871vjgujwz.fsf@mocca.josefsson.org>
In-Reply-To: <871vjgujwz.fsf@mocca.josefsson.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
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-Archive: <http://www.ietf.org/mail-archive/web/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, 30 Nov 2009 21:33:52 -0000

Simon Josefsson allegedly wrote on 11/30/2009 10:11 AM:
> There is no requirement in the IETF process for organizations to
> disclose patents as far as I can see.  The current approach of only
> having people participate, and disclose patents, in the IETF is easy to
> work around by having two persons in an organization doing different
> things: one works on specifying and standardizing technology, and the
> other is working on patenting the technology.

Simon, from rfc3979:

   l. "Reasonably and personally known": means something an individual
      knows personally or, because of the job the individual holds,
      would reasonably be expected to know.  This wording is used to
      indicate that an organization cannot purposely keep an individual
      in the dark about patents or patent applications just to avoid the
      disclosure requirement.  But this requirement should not be
      interpreted as requiring the IETF Contributor or participant (or
      his or her represented organization, if any) to perform a patent
      search to find applicable IPR.