Re: why to contact the IETF

Marshall Eubanks <tme@multicasttech.com> Tue, 10 February 2009 19:34 UTC

Return-Path: <tme@multicasttech.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 61B103A6CA9 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 11:34:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.469
X-Spam-Level:
X-Spam-Status: No, score=-103.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 RqbPyX5ShKph for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 11:34:03 -0800 (PST)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 4FB6F3A6CB1 for <ietf@ietf.org>; Tue, 10 Feb 2009 11:34:03 -0800 (PST)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 14591323; Tue, 10 Feb 2009 14:32:55 -0500
Message-Id: <29A5766C-61A0-4E40-B638-CB481E31DAF6@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: jnc@mercury.lcs.mit.edu
In-Reply-To: <20090210192441.7337A6BE5F1@mercury.lcs.mit.edu>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: why to contact the IETF
Date: Tue, 10 Feb 2009 14:33:39 -0500
References: <20090210192441.7337A6BE5F1@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.930.3)
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: Tue, 10 Feb 2009 19:34:04 -0000

On Feb 10, 2009, at 2:24 PM, Noel Chiappa wrote:

>> From: "Lawrence Rosen" <lrosen@rosenlaw.com>
>
>> The result of the FSF campaign has been to raise a legal concern
>> 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?
>
> That point could have been raised _much_ more efficiently with a  
> single email
> message from someone such as yourself.
>
>> I don't yet know the answer to this question. Does anyone here?
>
> I'm not sure I'd really believe any determination short of a court's  
> anyway -
> attorneys can advise, but until the proverbial butcher-baker- 
> candlestickmaker
> get their say after a trial, it's got an element of coin-toss to it,  
> no?

In my experience, attorneys will almost never give hard answers to  
questions like this. And it
typically takes a few million dollars in coins to make a toss.

Regards
Marshall

>
>
>> If the TLS specification really is patent-encumbered, in the
>> professional view of experts who have reason to understand the  
>> details,
>> my vote here and those of many FSF members and FOSS advocates too  
>> will
>> be to have nothing more to do with it.
>
> Taking no strong position on this particular specification (which is  
> not in my
> area of interest), but, as a general observation, nothing says  
> anyone has to
> use any particular IETF specification. If you don't want to mess  
> with a
> potential patent hassle, just don't use it.
>
> The IETF is just a place to create standards in an open way, and it  
> seems
> there is some open community of experts interested in this area who  
> seem to
> have determined that the advantages of using an encumbered solution  
> here
> outweigh the disadvantages.
>
> An effective critique of that judgement _does not_ mean just saying
> 'encumbered technology is bad', because most of us already agree  
> with that
> general statement. One would have to understand the details of why  
> they felt
> that that the advantages of using this particular encumbered solution
> outweighed the obvious disadvantages, and show where the problem  
> with that
> reasoning was.
>
> Alternatively, if there are a community of people who see a need,  
> and don't
> like using a patent-encumbered solution, they can create an  
> alternative not so
> hampered - and the IETF would, I would expect, be happy to afford  
> them an open
> forum to do so.
>
> 	Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf