Return to ABOUTCISCOPATENT CVS log

Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / freevrrpd

freevrrpd 1.1

    1: If you think that freevrrpd is not legal then read this mail/reply:
    2: 
    3: by lsh131.siteprotect.com (8.11.6/8.11.6) with ESMTP id hAOJwhD18461
    4: 	for <m.hertrick@neovera.com>; Mon, 24 Nov 2003 13:58:43 -0600
    5:   by sj-iport-3.cisco.com with ESMTP; 24 Nov 2003 12:00:05 +0000
    6: 	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id hAOJwdrX026823;
    7: 	Mon, 24 Nov 2003 11:58:39 -0800 (PST)
    8: Reply-To: <rbarr@cisco.com>
    9: From: "Robert Barr " <rbarr@cisco.com>
   10: To: "'Michael Hertrick'" <m.hertrick@neovera.com>
   11: Subject: RE: RFC 2338 (VRRP) and US patent #5,473,599
   12: Date: Mon, 24 Nov 2003 11:58:39 -0800
   13: Message-ID: <009401c3b2c5$5ae64e10$6601a8c0@amer.cisco.com>
   14: MIME-Version: 1.0
   15: Content-Type: text/plain;
   16: 	charset="us-ascii"
   17: Importance: Normal
   18: In-Reply-To: <3FBED170.4030604@neovera.com>
   19: Content-Transfer-Encoding: 8bit
   20: 
   21: Mr Hertrick:
   22: 
   23: The following is Cisco's policy with respect to VRRP:
   24: 
   25: 
   26: Cisco will not assert any patents owned or controlled by Cisco  against any
   27: party  for making, using, selling, importing or offering for sale a product
   28: that implements IETF RFC 2338, provided, however that:
   29: 
   30: Cisco retains the right to assert its patents  (including the right to claim
   31: past royalties) against any party that asserts a patent it owns or controls
   32: (either directly or indirectly) against Cisco or any of Cisco's affiliates
   33: or successors in title; and Cisco retains the right to assert its patents
   34: against any product or portion
   35: thereof that is not necessary for compliance with RFC 2338.
   36: 
   37: If you have any questions, or if you would prefer a royalty-bearing license,
   38: please contact me.
   39: 
   40: Robert Barr
   41: VP, Intellectual Property
   42: Worldwide Patent Counsel
   43: Cisco Systems
   44: 408-525-9706
   45: 
   46: > -----Original Message-----
   47: > From: Michael Hertrick [mailto:m.hertrick@neovera.com] 
   48: > Sent: Friday, November 21, 2003 7:01 PM
   49: > To: rbarr@cisco.com
   50: > Subject: RFC 2338 (VRRP) and US patent #5,473,599
   51: > 
   52: > 
   53: > Mr. Barr,
   54: > 
   55: > What does Cisco ask in return for a license to write and use a VRRP 
   56: > implementation in accordance with RFC 2338?
   57: > 
   58: > Thank you,
   59: > 
   60: > Michael Hertrick
   61: > 571-437-5911
   62: > Neovera, Inc.
   63: > 
   64: > 
   65: 
   66: I've send a new request from me to robert barr, freevrrpd is completly legal and agree with standards. So making, using, selling, importing or offering for sale is authorized.
   67: 
   68: Return-Path: <cyrus@smtp0.selectbourse.net>
   69: Received: from smtp0.selectbourse.net ([unix socket])
   70:  by smtp0.selectbourse.net (Cyrus v2.0.17); Fri, 05 Mar 2004 20:57:05 +0100
   71: X-Sieve: cmu-sieve 2.0
   72: Return-Path: <rbarr@cisco.com>
   73: Received: from polux.bsdfr.org (polux.bsdfr.org [80.65.231.210])
   74:  by smtp0.selectbourse.net (Postfix) with ESMTP id 2873D2EAE2
   75:  for <spe@bsdshell.net>; Fri,  5 Mar 2004 20:57:05 +0100 (CET)
   76: Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com
   77: [171.71.176.72])
   78:  by polux.bsdfr.org (8.12.10/8.12.9) with ESMTP id i25KA4GC091856
   79:  for <spe@bsdfr.org>; Fri, 5 Mar 2004 21:10:05 +0100 (CET)
   80:  (envelope-from rbarr@cisco.com)
   81: Received: from sj-core-1.cisco.com (171.71.177.237)
   82:   by sj-iport-3.cisco.com with ESMTP; 05 Mar 2004 12:09:41 +0000
   83: Received: from rbarrw2k (dhcp-171-71-102-213.cisco.com [171.71.102.213])
   84:  by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i25JuoF8011735;
   85:  Fri, 5 Mar 2004 11:56:50 -0800 (PST)
   86: Reply-To: <rbarr@cisco.com>
   87: From: "Robert Barr " <rbarr@cisco.com>
   88: To: "'Sebastien Petit'" <spe@bsdfr.org>
   89: Cc: "Robert Barr" <rbarr@cisco.com>
   90: Subject: RE: Patent issue for VRRPv2 and VRRPv3
   91: Date: Fri, 5 Mar 2004 11:56:50 -0800
   92: Message-ID: <00db01c402ec$00268b80$6501a8c0@amer.cisco.com>
   93: MIME-Version: 1.0
   94: Content-Type: text/plain;
   95:  charset="us-ascii"
   96: Content-Transfer-Encoding: quoted-printable
   97: X-Priority: 3 (Normal)
   98: X-MSMail-Priority: Normal
   99: X-Mailer: Microsoft Outlook, Build 10.0.4510
  100: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
  101: Importance: Normal
  102: In-Reply-To: <002a01c402e7$613cc510$6400a8c0@a91821794s3ti7g>
  103: 
  104: This is our policy for RFC2338. If VRRP v.2 and/or v.3 become
  105: standards-track RFC's (have they?) then this policy applies to those as
  106: well:
  107: 
  108: 
  109: 
  110: Cisco will not assert any patents owned or controlled by Cisco against any
  111: party for making, using, selling, importing or offering for sale a product
  112: that implements IETF RFC 2338, provided, however that:
  113: Cisco retains the right to assert its patents (including the right to claim
  114: past royalties) against any party that asserts a patent it owns or controls
  115: (either directly or indirectly) against Cisco or any of Cisco's affiliates
  116: or successors in title; and Cisco retains the right to assert its patents
  117: against any product or portion thereof that is not necessary for compliance with RFC 2338.
  118: If you have any questions, or if you would prefer a royalty-bearing license
  119: please contact me.
  120: Robert Barr
  121: VP, Intellectual Property
  122: Worldwide Patent Counsel
  123: Cisco Systems
  124: 408-525-9706
  125: -----Original Message-----
  126: From: Sebastien Petit [mailto:spe@bsdfr.org]=20
  127: Sent: Friday, March 05, 2004 11:24 AM
  128: To: rbarr@cisco.com
  129: Subject: Patent issue for VRRPv2 and VRRPv3
  130: 
  131: 
  132: Dear Robert Barr,
  133: 
  134: In order to be conform to the Cisco standards concerning VRRPv2 and VRRPv3
  135: (Patent #5 473 599),  I would like to obtain a legal authorization from
  136: Cisco to implement and use these protocols in OpenSource system environment, so
  137: be conform and compatible between all the existant equipments. OpenSource
  138: systems are not a risk for your company and will profit to network standards. If
  139: you cannot give me an  authorization, other solutions will be done and will be
  140: incompatible with your VRRP standard (like CARP a Common Adress
  141: Redundancy Protocol coming soon under OpenBSD 3.5)
  142: In order to continue my work in the OpenSource domain, can you tell me
  143: if you can give me an authorization for implementing and using VRRPv2,
  144: VRRPv3 ietf standard in a free opensource software (no selling) ?
  145: Is there any parts to request for that same thing ?
  146: 
  147: Regards,
  148: Sebastien Petit
  149: --
  150: spe@bsdfr.org
  151: spe@selectbourse.net
  152: 
  153: In Europe, all software and algorithms patents are invalid.