Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-auth-opt-03
Eric Rescorla <ekr@networkresonance.com> Fri, 27 February 2009 06:47 UTC
Return-Path: <ekr@networkresonance.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D21213A67F9 for <tcpm@core3.amsl.com>; Thu, 26 Feb 2009 22:47:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level:
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 K+5hyEHBbK5e for <tcpm@core3.amsl.com>; Thu, 26 Feb 2009 22:47:50 -0800 (PST)
Received: from romeo.rtfm.com (romeo.rtfm.com [74.95.2.173]) by core3.amsl.com (Postfix) with ESMTP id 0405B3A63D3 for <tcpm@ietf.org>; Thu, 26 Feb 2009 22:47:50 -0800 (PST)
Received: from romeo.rtfm.com (localhost.rtfm.com [127.0.0.1]) by romeo.rtfm.com (Postfix) with ESMTP id B207850822; Thu, 26 Feb 2009 23:11:01 -0800 (PST)
Date: Thu, 26 Feb 2009 23:11:01 -0800
From: Eric Rescorla <ekr@networkresonance.com>
To: Ron Bonica <rbonica@juniper.net>
In-Reply-To: <49A7534B.3080509@juniper.net>
References: <20090223161758.33753C140BB@lawyers.icir.org> <49A5A072.5040303@juniper.net> <49A6E581.6020905@isi.edu> <49A70733.6070200@juniper.net> <49A70909.1020607@isi.edu> <49A70C8C.2080705@juniper.net> <20090226232913.05B6C50822@romeo.rtfm.com> <49A7534B.3080509@juniper.net>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20090227071101.B207850822@romeo.rtfm.com>
Cc: tcpm@ietf.org, mallman@icir.org, Joe Touch <touch@ISI.EDU>
Subject: Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-auth-opt-03
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2009 06:47:50 -0000
Merging two messages: [# 1] > Is there anything in the disclosure language that suggests that the > license is revocable or otherwise not perpetual, so long as the one > licensing condition is met? If so, the licensing language says something > that we didn't mean to say. We can fix that. Well, that's a pretty big condition, IMO. > The one condition of the license (i.e., we won't sue you if you don't > sue us) is copied verbatim from many other IETF IPR disclosures. We ask > only for the same protection that is granted routinely to other vendors. > > Is there some reason why this protection should not be granted? If so, > there are lots of problematic IPR disclosures on the IETF web page. [# 2] > This kind of equilibrium is exactly what Juniper is hoping to achieve. > Juniper' like the vast majority of its competitors, makes money from > sales, not litigation. We want to spend our dollars on engineers, not > lawyers. > > To some degree, I believe that that equilibrium has already been > reached. I hold this belief because this licensing condition is so common. > > Searching the IPR disclosure web page, I see one company (aside from > Cisco and Juniper) using exactly the same language. One other company > uses nearly identical language to say the same thing. Most other > disclosures have some condition of "reciprocity". I'm not sure what to say to this other than "huh?" IETF isn't granting any protection to anyone. Rather, IETF determines whether to incorporate specific technologies into their standards. One consideration when making those decisions is whether those technologies are encumbered and if so, the conditions under which the license is granted. The license Juniper proposes is substantially less free than it could be, and I, for one, would prefer that if the TCPM WG has the option it select a technology which isn't subject to licensing terms of this type. Again, I can certainly understand why Juniper would like to have a mutually assured destruction patent situation with other companies, but why exactly is it in the IETF's interest to assist them in that endeavor? -Ekr
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Eric Rescorla
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Mark Allman
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Joe Touch
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Joe Touch
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Joe Touch
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… David Borman
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Eric Rescorla
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Eric Rescorla
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Caitlin Bestler
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Eric Rescorla
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Caitlin Bestler
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Mark Allman
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Mark Allman
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Ron Bonica
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Eric Rescorla
- Re: [tcpm] Juniper's IPR on draft-ietf-tcpm-tcp-a… Eric Rescorla