RE: Previous consensus on not changing patent policy (Re:Referencesto Redphone's "patent")

"Powers Chuck-RXCP20" <Chuck.Powers@motorola.com> Wed, 18 February 2009 22:32 UTC

Return-Path: <Chuck.Powers@motorola.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 6082E3A67F0 for <ietf@core3.amsl.com>; Wed, 18 Feb 2009 14:32:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.598
X-Spam-Level:
X-Spam-Status: No, score=-7.598 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, 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 7AdWLbN3mXWT for <ietf@core3.amsl.com>; Wed, 18 Feb 2009 14:32:34 -0800 (PST)
Received: from mail153.messagelabs.com (mail153.messagelabs.com [216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id D36FB3A676A for <ietf@ietf.org>; Wed, 18 Feb 2009 14:32:33 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: Chuck.Powers@motorola.com
X-Msg-Ref: server-7.tower-153.messagelabs.com!1234996361!9299767!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [136.182.1.14]
Received: (qmail 18949 invoked from network); 18 Feb 2009 22:32:41 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (136.182.1.14) by server-7.tower-153.messagelabs.com with SMTP; 18 Feb 2009 22:32:41 -0000
Received: from il27exr01.cig.mot.com (il27exr01.mot.com [10.17.196.70]) by motgate4.mot.com (8.12.11/Motorola) with ESMTP id n1IMWfEH017940 for <ietf@ietf.org>; Wed, 18 Feb 2009 15:32:41 -0700 (MST)
Received: from il27vts03 (il27vts03.cig.mot.com [10.17.196.87]) by il27exr01.cig.mot.com (8.13.1/Vontu) with SMTP id n1IMWeRL006591 for <ietf@ietf.org>; Wed, 18 Feb 2009 16:32:40 -0600 (CST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25]) by il27exr01.cig.mot.com (8.13.1/8.13.0) with ESMTP id n1IMWdTd006578 for <ietf@ietf.org>; Wed, 18 Feb 2009 16:32:39 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C99218.CE5EED3A"
Subject: RE: Previous consensus on not changing patent policy (Re:Referencesto Redphone's "patent")
Date: Wed, 18 Feb 2009 17:32:38 -0500
Message-ID: <2963ECA56B01F94B9964469DCB8A2B5A056511D3@de01exm69.ds.mot.com>
In-Reply-To: <2788466ED3E31C418E9ACC5C3166155768B2A4@mou1wnexmb09.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Previous consensus on not changing patent policy (Re:Referencesto Redphone's "patent")
thread-index: AcmRURCmpmfKAu+rRVyhfdnYTKRSGgAwb+E3AAFaLdA=
References: <20090216230741.53056.qmail@simone.iecc.com><499B3D4D.2040601@earthlink.net> <2788466ED3E31C418E9ACC5C3166155768B2A4@mou1wnexmb09.vcorp.ad.vrsn.com>
From: Powers Chuck-RXCP20 <Chuck.Powers@motorola.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>, TSG <tglassey@earthlink.net>, John Levine <johnl@iecc.com>
X-CFilter-Loop: Reflected
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: Wed, 18 Feb 2009 22:32:35 -0000

One problem I see with that approach would be the inevitable replay of
TLS-auth -> a working group agrees up front that there is
patent-encumbered technology that is too useful to not include in the
spec (which has happened in the IETF in the past), that group would
therefore agree to follow that model, and then when they were done, a
firestorm of FSF folks who had not even read the material, much less
were aware of how the original decision had been reached, would assail
the IETF with "the sky is falling" emails about how the world will come
to an end if the IETF publishes the specification.
 
Apart from that, it would likely be a total rats nest to try and track
what work was done under what IPR agreement; allowing IPR policy
decisions to be made on a WG by WG basis would, IMO, be a nightmare,
except for the lawyers.
 


Regards, 
Chuck 
------------- 
Chuck Powers,
Motorola, Inc
phone: 512-427-7261
mobile: 512-576-0008 

 


________________________________

	From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
Behalf Of Hallam-Baker, Phillip
	Sent: Wednesday, February 18, 2009 4:18 PM
	To: TSG; John Levine
	Cc: ietf@ietf.org
	Subject: RE: Previous consensus on not changing patent policy
(Re:Referencesto Redphone's "patent")
	
	

	Do you think that the IETF has changed direction though?
	
	Methinks not.
	
	This is one of those issues where there is a faction that will
defend the status quo regardless of the flaws that are revealed. They
will wait till the end of the discussion and announce that there is no
consensus to do anything differently so they must win.
	
	I really do not understand the justification for not allowing a
WG to state the IPR policy that will apply during the charter process.
If we are going to have people volunteer time an effort to create a
standard they have the right to know at the start whether the result
will be encumbered or if one particular party gets to set up a toll
booth.
	
	
	In fact there are two very different status quos. There is the
defacto status quo and there is the de jure status quo. And it is rather
interesting that on every one of my pet IETF peeves, my position is the
defacto status quo and it is only the official status quo that is out of
line.
	
	
	Officially a working group does not need to set an IPR standard
up front.
	In practice every working group in any part of the IETF I
participate in has to deliver a standard that is compliant with the W3C
policy that every essential part of the spec be implementable without
using encumbered technology. Attempts to do otherwise are totally
futile.
	
	I guess it is possible that things are different outside the
security, applications and operations side, but I find it very hard to
believe that a necessary to implement technology at the Internet level
could be encumbered without creating a blogstorm of slashdot
proportions.
	
	
	Officially the specs are in the obsolete text format
	In practice they are written in XML and the engineers
implementing them use either the HTML version or buy the O'Rielly
nutshell book.
	
	
	Officially there are three stages in the standards process
	In practice there are two stages.
	
	
	I really wish it was possible to have a discussion on this topic
without getting condescending lectures as to why it is absolutely
unthinkable to change the official status quo when folk are already
doing exactly what I have been suggesting for five years or more.
	
	
	
	-----Original Message-----
	From: ietf-bounces@ietf.org on behalf of TSG
	Sent: Tue 2/17/2009 5:42 PM
	To: John Levine
	Cc: ietf@ietf.org
	Subject: Re: Previous consensus on not changing patent policy
(Re: Referencesto Redphone's "patent")
	
	John Levine wrote:
	>> But are the 1,000 or so emails in recent days from the FSF
campaign
	>> not a loud enough hum to recognize that our IPR policy is out
of
	>> tune?
	>>    
	>
	> Are you really saying that all it takes is a mob motivated by
an
	> misleading screed to make the IETF change direction?
	>  
	Yes  - exactly that.
	> >From the sample of the FSF letters I read, many of the people
writing
	> didn't know the difference between Redphone and Red Hat, and
if as
	> many as two of them had even looked at the draft or IPR
disclosure in
	> question, it'd be a lot.
	>
	> The FSF's absolutist position on patents was set in stone 20
years
	> ago.  I don't see why we should be impressed if they
occasionally
	> throw a handful of pebbles at us.
	>
	> R's,
	> John
	> _______________________________________________
	> Ietf mailing list
	> Ietf@ietf.org
	> https://www.ietf.org/mailman/listinfo/ietf
	>
	>  
	
	_______________________________________________
	Ietf mailing list
	Ietf@ietf.org
	https://www.ietf.org/mailman/listinfo/ietf