Re: why to contact the IETF
"Steven M. Bellovin" <smb@cs.columbia.edu> Tue, 10 February 2009 19:19 UTC
Return-Path: <smb@cs.columbia.edu>
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 0470F3A69DF for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 11:19:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.599
X-Spam-Level:
X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
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 Dp3gFxuMMe0U for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 11:19:40 -0800 (PST)
Received: from machshav.com (machshav.com [198.180.150.44]) by core3.amsl.com (Postfix) with ESMTP id F07FE3A6936 for <ietf@ietf.org>; Tue, 10 Feb 2009 11:19:39 -0800 (PST)
Received: by machshav.com (Postfix, from userid 512) id 9CF6632930B; Tue, 10 Feb 2009 14:19:41 -0500 (EST)
Received: from yellowstone.machshav.com (localhost [127.0.0.1]) by machshav.com (Postfix) with ESMTP id 67D11329225; Tue, 10 Feb 2009 14:19:39 -0500 (EST)
Received: from cs.columbia.edu (localhost [127.0.0.1]) by yellowstone.machshav.com (Postfix) with ESMTP id CE679296915; Tue, 10 Feb 2009 14:19:35 -0500 (EST)
Date: Tue, 10 Feb 2009 14:19:35 -0500
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: lrosen@rosenlaw.com
Subject: Re: why to contact the IETF
Message-ID: <20090210141935.0fa03ef6@cs.columbia.edu>
In-Reply-To: <DD50ADA4B37241B5B7E2FDF5EE9646A6@LROSENTOSHIBA>
References: <20090210142744.GJ13560@shinkuro.com> <C5B7054D.2F9A%mshore@cisco.com> <20090210160246.GM13560@shinkuro.com> <1006C42E-B6EC-4C7C-8D03-CFA08F2E06D5@cisco.com> <DD50ADA4B37241B5B7E2FDF5EE9646A6@LROSENTOSHIBA>
Organization: Columbia University
X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64--netbsd)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: 'IETF discussion list' <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: Tue, 10 Feb 2009 19:19:41 -0000
On Tue, 10 Feb 2009 10:59:52 -0800 "Lawrence Rosen" <lrosen@rosenlaw.com> wrote: > The result of the FSF campaign has been to raise a legal concern No, they didn't raise the concern. The concern had been raised previously by people who are obviously IETF participants, including Simon Josefsson. (I don't recall if you've posted on this particular I-D, but I obviously put you in the category of IETF participant, too.) > obviously important to many of us: Will users of the proposed IETF > TLS specification require patent licenses from RedPhone to use such > implementations in the US or elsewhere? > > I don't yet know the answer to this question. Does anyone here? As you well know, the IETF per se doesn't care about the answer to that question. Individual participants may care, of course, and can and should use that information when making their own judgments. More precisely -- the statement "the IETF should not standardize draft-chthulhu-shogoth-666.txt because the technology is patented" is a NOP according to IETF policies on patented works. The proper formulation is "I feel that standardizing draft-chthulhu-shogoth-666.txt is a bad idea because in this particular case, the licensing terms are too onerous for the benefit gained", perhaps with a suggestion that some other technology be adopted instead. > > Several emails here have valiantly attempted to get us to focus on the > technical aspects of the RedPhone patent claims, the progress of the > patent in the PTO and PCT, and other technical issues. Speaking only > for myself, I haven't yet seen any justification for us fearing the > RedPhone patent claims. They may be as bogus as the hundreds of other > patent infringement claims that companies receive letters about every > day. OTOH, they may be deadly submarines ready to attack us all. > > Why don't we organize to answer the patent claim infringement issues > like professionals do? Ask technical experts. Consult a patent > attorney. Render expert opinions. Absolutely -- that's everyone's right, privilege, and (arguably) duty. I haven't looked at it myself because I have no particular interest in it at the moment, but this is definitely the proper course. It's also perfectly proper to post analyses to influence others -- that was done years ago in IPsec to reassure people that a particular patent was unlikely to be enforceable. --Steve Bellovin, http://www.cs.columbia.edu/~smb
- Re: Ietf Digest, Vol 9, Issue 25 Alex Loret de Mola
- Re: how to contact the IETF Alex Loret de Mola
- Re: how to contact the IETF Ofer Inbar
- Re: how to contact the IETF Andrew Sullivan
- Re: how to contact the IETF Melinda Shore
- Re: how to contact the IETF Andrew Sullivan
- Re: how to contact the IETF Andrew Sullivan
- Re: how to contact the IETF Melinda Shore
- Re: how to contact the IETF Andrew Sullivan
- RE: how to contact the IETF Ed Juskevicius
- Re: how to contact the IETF Cullen Jennings
- RE: why to contact the IETF Lawrence Rosen
- Re: why to contact the IETF Steven M. Bellovin
- Re: why to contact the IETF Brian E Carpenter
- Re: how to contact the IETF Wes Hardaker