Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard

"John R Levine" <johnl@taugh.com> Mon, 19 August 2013 19:59 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B55311E82D2 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 kW6Tu0HTpj6N for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:59: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 976E611E82BA for <ietf@ietf.org>; Mon, 19 Aug 2013 12:59:53 -0700 (PDT)
Received: (qmail 91845 invoked from network); 19 Aug 2013 19:59:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=166c4.52127937.k1308; bh=7kRE0s1LIirmlYQrbhSspCraGZ/R9SC0rtMqgsdFfTw=; b=E1DvQ6AjPyV3KA4JUV4vPtZGKfMkFAb0VnjnCEZxRJbT+RHNRLzftcJsJWCOwi1vayvaW3NuXu41VdWbRZP6tIGlDdeI4cdtXTfDOsoiMFSILSc7M2di+8teuBuvbCqyH4/JhumgC/qv75mzB1+h7LTUhSL8DUwMx9jyHsZBl5V6TRNPlNd3AtjksBxpcHxm1yJqfGLR/HjvMkaF6l17X3ZrjivE6b9zF1epJ2PqF/VmRxL+qnyZpLxHL1HPyLnR
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=166c4.52127937.k1308; bh=7kRE0s1LIirmlYQrbhSspCraGZ/R9SC0rtMqgsdFfTw=; b=cOgKbk6+GnfA1Yc4qKvwXCvusZiIS3ip0FjAzN1UIIA+MqqkC6JIUFoFvLLMqWG3Jv3/Mt2bjGDQyNnye04ki6JnyEjQzCu89b+QhUdTUSDHdrVsQjSz28CvWJf9ogdV0+hX95R7D/x+zCPtOwd02QnUueJwd4XnMItjyrqOf5kv0Pb1A2uhwY0C85egvz2/iSq+VvfCezBRCu9EsFvJFC/CpOHXMrd/FpglZ9d02fv9BJlacPJoJ7RV+3ex6cRc
Received: (ofmipd 127.0.0.1); 19 Aug 2013 19:59:29 -0000
Date: Mon, 19 Aug 2013 15:59:50 -0400
Message-ID: <alpine.BSF.2.00.1308191543490.62330@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Måns Nilsson <mansaxel@besserwisser.org>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130819190533.GA30516@besserwisser.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 19:59:54 -0000

>>> * The charter disallows major protocol changes -- removing the SPF RR type
>>> is a direct charter violation; since SPF is being used on the Internet. ...

The SPF working group discussed this issue at painful, extensive length.

As you saw when you read the WG archives, there is a significant interop 
bug in rfc 4408 in the handling of SPF and TXT records, which (again after 
painful and extension discussion) we decided the least bad fix was to get 
rid of SPF records.  I don't see anything in your note about how else you 
think we should address the interop bug.

In your case it doesn't matter, since your TXT and SPF records make no 
usable assertions, but a lot of people use SPF right now as part of their 
mail stream management.

R's,
John