Re: [DNSOP] draft-dickinson-dnsop-nameserver-control-00

bert hubert <bert.hubert@netherlabs.nl> Mon, 27 October 2008 19:11 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@optimus.ietf.org
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7483B28C205; Mon, 27 Oct 2008 12:11:26 -0700 (PDT)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 795293A6BB7 for <dnsop@core3.amsl.com>; Mon, 27 Oct 2008 12:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 iGvY9OmMROsf for <dnsop@core3.amsl.com>; Mon, 27 Oct 2008 12:11:23 -0700 (PDT)
Received: from outpost.ds9a.nl (outpost.ds9a.nl [85.17.220.215]) by core3.amsl.com (Postfix) with ESMTP id 96C073A6BB6 for <dnsop@ietf.org>; Mon, 27 Oct 2008 12:11:09 -0700 (PDT)
Received: by outpost.ds9a.nl (Postfix, from userid 1000) id 066CB82E2F; Mon, 27 Oct 2008 20:11:10 +0100 (CET)
Date: Mon, 27 Oct 2008 20:11:10 +0100
From: bert hubert <bert.hubert@netherlabs.nl>
To: TS Glassey <tglassey@earthlink.net>
Message-ID: <20081027191110.GA10670@outpost.ds9a.nl>
Mail-Followup-To: bert hubert <bert.hubert@netherlabs.nl>, TS Glassey <tglassey@earthlink.net>, dnsop@ietf.org
References: <20081027160900.95AD33A6A0E@core3.amsl.com> <FEB5969C-F0A4-454C-A0BF-7DAF9358E539@jadickinson.co.uk> <002f01c950c6$477eaa80$2000a8c0@tsg1>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <002f01c950c6$477eaa80$2000a8c0@tsg1>
User-Agent: Mutt/1.5.9i
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] draft-dickinson-dnsop-nameserver-control-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

On Thu, Nov 27, 2008 at 11:01:13AM -0800, TS Glassey wrote:
> Yeah and like the other DNSSEC I-D's I dfound numerous things in it that 
> would violate the controls put in place by US Patent 6,370,629 of which I 
> am one of the two owners and controlling parties to that IP.

Please start litigating. I've looked at this patent and the other one you
mentioned in the context of DNSSEC, and based on earlier discussions with a
patent attorney, your claims don't look like they would stand up at least in
Dutch courts.

draft-dickinson-dnsop-nameserver-control does not even mention a
geographical location, nor does it mention anything that is time controlled.

If I recall correctly, making bogus IPR claims is a punishable offense at
least in Germany - SCO suffered that fate.

So either litigate or refrain from intimidating us.

	Bert

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop