Re: [spfbis] WGLC: draft-ietf-spfbis-4408bis-14

"John Levine" <johnl@taugh.com> Wed, 24 April 2013 00:26 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06CA521F9418 for <spfbis@ietfa.amsl.com>; Tue, 23 Apr 2013 17:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level:
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qKm26m83LrM for <spfbis@ietfa.amsl.com>; Tue, 23 Apr 2013 17:26:53 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 28BCF21F93DA for <spfbis@ietf.org>; Tue, 23 Apr 2013 17:26:52 -0700 (PDT)
Received: (qmail 89526 invoked from network); 24 Apr 2013 00:26:52 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 Apr 2013 00:26:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=517726cc.xn--hew.k1304; i=johnl@user.iecc.com; bh=EQEThnH91xKW+vwfzXY+EFo0VfVDXAjoWQop5U9UIOw=; b=ThlmpWd9pvADbKH+6MZeqKFsbDkb73Wg4GHX85O6URVtC5mPFeomqIdm8ZoxCkmGEP+7hcl5x53WLZKW/Ka8HwhQSXx1nuhKLa89OYUqAxEOqe/U3XhvjcODoKmZBN4EN3Dah4MzyMUevRQ8QyevkvBfZF4yIE57+FL1JZ+Il5g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=517726cc.xn--hew.k1304; olt=johnl@user.iecc.com; bh=EQEThnH91xKW+vwfzXY+EFo0VfVDXAjoWQop5U9UIOw=; b=CfCnJS+9Qk6LjzMEv9OXUXxe8WAPDGMwjo5CzFbQon1Ujc7dNv1fu4OWUygrfvv7QZIr61Ap+zyZfZg+L6+C4jPiFEMn/z72no9vBpr56BVU80B65US1H58t3AFMCznT2c3yF8OU5m6Re/RJTGTCG8ZaqCD+k9xsyzIJ3e7Y8ew=
Date: Wed, 24 Apr 2013 00:26:29 -0000
Message-ID: <20130424002629.13505.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: spfbis@ietf.org
In-Reply-To: <CAL0qLwYkudUHYrGmsHyOLsB76j=Zrn5NCCacVnd1ncG=sQNmyg@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Cc: superuser@gmail.com
Subject: Re: [spfbis] WGLC: draft-ietf-spfbis-4408bis-14
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 00:26:54 -0000

>Section 4.6.4:
>
>I imagine you're going to say that 10 is the limit imposed by most
>implementations, but shouldn't we say that there should be a finite,
>perhaps configurable limit, and operational experience has shown that 10 is
>a reasonable default?

If everyone doesn't have the same limit, an SPF check might fail at a
site with a lower limit and the identical check would succeed at one
with a higher limit.  The limit has been 10 for a long time and I
don't see any reason to change it now.

>The "Some implementations ..." sentence seems to be malformed.  I can't
>parse it.

That whole paragraph could be replaced by "the result of evaluating
check_host() with a syntactically invalid domain is undefined."

>Section 5.6:
>
>For IPv4, shouldn't the CIDR be 1*2DIGIT?  For IPv6, shouldn't the CIDR be
>1*3DIGIT?

What's wrong with 10.1.0.0/016 ?

>Section 11.3:

>Is that second bullet true?  It appears to claim that IP address spoofing
>is effectively impossible.

Ever since TCP stacks started randomizing sequence numbers in the
mid-1990s, spoofing a TCP session has been implausibly hard.  Spoofing
UDP is all too easy, but that's not what we're talking about here.

R's,
John