IETF Logo Mail Archive

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 Levine" <johnl@taugh.com> Thu, 22 August 2013 17:19 UTC

Return-Path: <johnl@iecc.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 3037811E80ED for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 10:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.686
X-Spam-Level:
X-Spam-Status: No, score=-102.686 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, 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 xFp1m2PvVp+T for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 10:19:14 -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 D04DF11E810D for <ietf@ietf.org>; Thu, 22 Aug 2013 10:19:12 -0700 (PDT)
Received: (qmail 3973 invoked from network); 22 Aug 2013 17:19:11 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Aug 2013 17:19:11 -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=5216480f.xn--hew.k1308; i=johnl@user.iecc.com; bh=rVUm8uUaBOGhVQoz1q0pEAEybkF0lrNyttStnY/r8Qo=; b=rs1KQC1NQLxf+V7cc6Vce3peIdVUK9DUuqnNRUZR/Z2k5ChCqyHQV6tobCPQ1iQop1nSlazZ5ICglgUVqC4LqpouaabvAH8NGYrUiUKkRFEe1cVCVyc99sym7AGAZhdlnFAuQz8RNRqofbuyAI1vlamzRtgKJrRuja6ahb5sZE8G3J+DiFPyDA2z/QE2xTIfUCB+Jw+a9jGu6cyrbXqJq46d4t3CZMJahAsQR3Y48w4bDytJl+ofD+SuUuMxu+uS
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=5216480f.xn--hew.k1308; olt=johnl@user.iecc.com; bh=rVUm8uUaBOGhVQoz1q0pEAEybkF0lrNyttStnY/r8Qo=; b=q2Ez9Ot9EvCDkaEe7GpDHGSgYMlaZFx7McwXjvBMFSr8qEpMKlWZTgXS8/QHRdslzn99/pcPCnTpIp09SgcWBT4ZRQtQmOi+yAQ3NvK+k9KJojyed+0clA2rOOXAVyXyrgnXvBk2Ofwe1xWQrKVnr9mAWABdAo5bLK+Ax++hsPim6KmeIJEUnIzOw+QzJQ2weORZ8yOAXOK19XPe2UUNROr1wH+ZNSPQZafp4WAcKAsUtnnhBirH1HFHNKx7EHF1
Date: Thu, 22 Aug 2013 17:18:49 -0000
Message-ID: <20130822171849.5154.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.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: <5215CD8D.3080302@sidn.nl>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
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: Thu, 22 Aug 2013 17:19:18 -0000

In article <5215CD8D.3080302@sidn.nl> you write:
>So what makes you think the above 4 points will not be a problem for the
>next protocol that comes along and needs (apex) RR data? And the one
>after that?

SPF is ten years old now.  It would be helpful if you could give us a
list of other protocols that have had a similar issue with a TXT
record at the apex during the past decade.

R's,
John

v2.23.0 | Report a Bug | By Email