Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

wayne <wayne@schlitt.net> Tue, 13 December 2005 19:12 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmFZn-0003br-5Q; Tue, 13 Dec 2005 14:12:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmFZl-0003XO-75 for ietf@megatron.ietf.org; Tue, 13 Dec 2005 14:12:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08425 for <ietf@ietf.org>; Tue, 13 Dec 2005 14:11:31 -0500 (EST)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmFae-0004XO-86 for ietf@ietf.org; Tue, 13 Dec 2005 14:13:33 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EmFWS-0008Vp-3k for ietf@ietf.org; Tue, 13 Dec 2005 20:09:12 +0100
Received: from footbone.schlitt.net ([67.52.51.37]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 13 Dec 2005 20:09:12 +0100
Received: from wayne by footbone.schlitt.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 13 Dec 2005 20:09:12 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: wayne <wayne@schlitt.net>
Date: Tue, 13 Dec 2005 13:07:59 -0600
Lines: 24
Message-ID: <x4slswke7k.fsf@footbone.schlitt.net>
References: <200512092141.NAA00720@gra.isi.edu> <x4fyp1n5xs.fsf@footbone.schlitt.net> <tslbqznbcem.fsf@cz.mit.edu> <x48xuqksa1.fsf@footbone.schlitt.net> <1134489989.5110.47.camel@bash.adsl-64-142-13-68> <439F0E4C.1493@xyzzy.claranet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: footbone.schlitt.net
User-Agent: Gnus/5.110004 (No Gnus v0.4) XEmacs/21.4.17 (linux)
Cancel-Lock: sha1:k/FdrR0m6dkgd4T3ABEke1LIGRQ=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

In <439F0E4C.1493@xyzzy.claranet.de> Frank Ellermann <nobody@xyzzy.claranet.de> writes:

> Whatever you think, but your complaints about the theoretical
> upper limit of DNS queries in an attack scenario resulted in
> some of the most interesting post-MARID changes (Wayne's I-Ds).

This is bunk.

The DoS limits that are in draft-schlitt-spf-classic are almost
exactly the same as those found in the libspf2 implementation I
created.  The analysis of the packet sizes and the expansion factors,
and the writing of libspf2 happened well before MARID was even
started.  I know of one other SPF implemenation, and I think there was
another, that implemented roughly the same limits as I created in
libspf2.  The justification for adding those limits into the SPF spec
was, in large part, because they reflected existing practices.

Doug Otis did complain a lot about the DoS potential, and his
complaints did go unheeded by the draft authors and the working group
chairs.  However, his complaints could not have possibly had any
impact on the current limits in the SPF spec.


-wayne


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf