RE: References to Redphone's "patent"
Ted Hardie <hardie@qualcomm.com> Fri, 13 February 2009 19:51 UTC
Return-Path: <hardie@qualcomm.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 CC4353A6DC5 for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 11:51:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 aE6GztJGqaOY for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 11:51:36 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id C53063A6DEC for <ietf@ietf.org>; Fri, 13 Feb 2009 11:51:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=hardie@qualcomm.com; q=dns/txt; s=qcdkim; t=1234554704; x=1266090704; h=mime-version:message-id:in-reply-to:references:date:to: from:subject:content-type:x-ironport-av; z=MIME-Version:=201.0|Message-ID:=20<p06240806c5bb7c75954c @[10.227.68.59]>|In-Reply-To:=20<AB05B60FFA04487A82D32669 F96F2681@LROSENTOSHIBA>|References:=20<87skmknar8.fsf@ash bery.wjsullivan.net>=0D=0A=20<tslfxiiuzs5.fsf@live.mit.ed u>=0D=0A=20<1F52870FDF6C4903800E145AAEB9FAF7@LROSENTOSHIB A>=0D=0A=20<4995B9B2.5040702@connotech.com>=0D=0A=20<AB05 B60FFA04487A82D32669F96F2681@LROSENTOSHIBA>|Date:=20Fri, =2013=20Feb=202009=2011:51:40=20-0800|To:=20"lrosen@rosen law.com"=20<lrosen@rosenlaw.com>,=0D=0A=20=20=20=20=20=20 =20=20"ietf@ietf.org"=0D=0A=09<ietf@ietf.org>|From:=20Ted =20Hardie=20<hardie@qualcomm.com>|Subject:=20RE:=20Refere nces=20to=20Redphone's=20"patent"|Content-Type:=20text/pl ain=3B=20charset=3D"us-ascii"|X-IronPort-AV:=20E=3DMcAfee =3Bi=3D"5300,2777,5525"=3B=20a=3D"15491307"; bh=XVoT73IA7NZUZAegUxNVAdP6I2P8uFzp4rQ9PXeCzcw=; b=Cdso9QiAcGjn0SqX0/OfHUoTGvV04SniMewWiRHIQ1qcGfARprvavbRl u86MlUR9xltaysr134LLlFlzguuTEiSu9GAvuC2vJSDTyFaPrN6pKmtvV Jfqp5/l3NvmvQMk5PpcvUMCH2XQPddxjkPYWDSiwsF2gZbbD7TB2teiNl U=;
X-IronPort-AV: E=McAfee;i="5300,2777,5525"; a="15491307"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Feb 2009 11:51:43 -0800
Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n1DJphGE016206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 Feb 2009 11:51:43 -0800
Received: from nasanexhub02.na.qualcomm.com (nasanexhub02.na.qualcomm.com [10.46.143.120]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n1DJpgSw031658 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 13 Feb 2009 11:51:43 -0800
Received: from nasanexmsp01.na.qualcomm.com (10.45.56.204) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.1.336.0; Fri, 13 Feb 2009 11:51:42 -0800
Received: from [10.227.68.59] (10.46.82.6) by qcmail1.qualcomm.com (10.45.56.204) with Microsoft SMTP Server (TLS) id 8.1.336.0; Fri, 13 Feb 2009 11:51:41 -0800
MIME-Version: 1.0
Message-ID: <p06240806c5bb7c75954c@[10.227.68.59]>
In-Reply-To: <AB05B60FFA04487A82D32669F96F2681@LROSENTOSHIBA>
References: <87skmknar8.fsf@ashbery.wjsullivan.net> <tslfxiiuzs5.fsf@live.mit.edu> <1F52870FDF6C4903800E145AAEB9FAF7@LROSENTOSHIBA> <4995B9B2.5040702@connotech.com> <AB05B60FFA04487A82D32669F96F2681@LROSENTOSHIBA>
Date: Fri, 13 Feb 2009 11:51:40 -0800
To: "lrosen@rosenlaw.com" <lrosen@rosenlaw.com>, "ietf@ietf.org" <ietf@ietf.org>
From: Ted Hardie <hardie@qualcomm.com>
Subject: RE: References to Redphone's "patent"
Content-Type: text/plain; charset="us-ascii"
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: Fri, 13 Feb 2009 19:51:37 -0000
At 10:48 AM -0800 2/13/09, Lawrence Rosen wrote: >That's why I'm so irritated that the previous IPR WG, since disbanded >(fortunately), refused even to discuss a patent policy for IETF. Armed with my calming cup of white tea, I point out that this is not true. The group considered the question of whether an update in this area was required, and it declined to take on any change. The current policy is that IETF participants are required to notify the IETF of any IPR which they reasonably and personally know to cover a contribution. This allows individual participants to make informed decisions about whether they wish to support work on those contributions and the WGs and IETF as a whole whether it wishes to publish the work, given the known situation. Taking that set of decisions out of the WGs and into a specialist body has substantial risks, chief among them the risk that the body's analysis of the risk does not come with insurance cover for the decisions taken by individuals. If the body says "This patent application is invalidated by prior art" and the patent examiners do not agree, those who have acted on that basis are in a troublesome situation. If the specialist body says "This patent does not cover this draft" and a court later disagrees, the same is true. Also, if the body says "this patent does cover this draft", it is the WG participants who spend time and effort to develop an alternative, possibly only to later discover that they would have disagreed with the specialist body on either the coverage or the risks inherent in infringement. The IPR working group also pointed out, repeatedly, the risk in demanding that all submissions to the IETF have no known encumbrance: anyone can claim they have covering IPR at any time and use that tool to block progress on a standard. Given the value of maintaining a proprietary lock on some areas, this is a substantial risk. The IETF policy amounts to this: you must disclose what you know, and the people impacted by the decision make it. I'm sorry that irritates you, Larry, but I remain convinced that it is the right thing for the IETF. Two cents and one bag of "Moonlight Spice", steeped 5 minutes, worth of opinion, Ted Hardie
- FSF's comment on draft-housley-tls-authz-extns John Sullivan
- Re: FSF's comment on draft-housley-tls-authz-extns Willie Gillespie
- Re: FSF's comment on draft-housley-tls-authz-extns Paul Hoffman
- Re: FSF's comment on draft-housley-tls-authz-extns Sam Hartman
- References to Redphone's "patent" Lawrence Rosen
- Re: FSF's comment on draft-housley-tls-authz-extns ned+ietf
- RE: FSF's comment on draft-housley-tls-authz-extns Powers Chuck-RXCP20
- Re: References to Redphone's "patent" Thierry Moreau
- RE: References to Redphone's "patent" Lawrence Rosen
- RE: References to Redphone's "patent" Ted Hardie
- Re: References to Redphone's "patent" Thierry Moreau
- How we got here, RE: References to Redphone's "pa… Hallam-Baker, Phillip
- Re: How we got here, RE: References to Redphone's… Brian E Carpenter
- RE: How we got here, RE: References to Redphone's… Hallam-Baker, Phillip
- Re: How we got here, RE: References to Redphone's… Henning Schulzrinne
- Re: How we got here, RE: References to Redphone's… Michael Richardson
- Re: FSF's comment on draft-housley-tls-authz-extns Byung-Hee HWANG
- Re: FSF's comment on draft-housley-tls-authz-extns John Sullivan