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

Alessandro Vesely <vesely@tana.it> Wed, 21 August 2013 14:14 UTC

Return-Path: <vesely@tana.it>
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 E1FC711E83C6 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level:
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 4a5Cj5obkBIj for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:14:06 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id C605711E821C for <ietf@ietf.org>; Wed, 21 Aug 2013 07:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1377094443; bh=SIaC7/iPbDA1StpwGLIFBW3OLPyX1mTg2tMGrTxtMbM=; l=737; h=Date:From:To:References:In-Reply-To; b=kSnC4GwhfFbvOJdhDRN1c499JsyLzNO0BS5u/zeNvJEOQU8jcmyAQePEmgF8OQ2Ow 6rkHZ15oFi/9uhbXoLuJ3Dfq6YGowRVVr9ffOWblsixUXr/vAKfj+JPoR22mgX6keb oNjGrQG0N/3V5OrXfgfN4a0Iyxt69Bqv39wr0W6E=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [192.168.43.171] (ge-19-118-234.service.infuturo.it [151.19.118.234]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Wed, 21 Aug 2013 16:13:57 +0200 id 00000000005DC047.000000005214CB26.0000078D
Message-ID: <5214CAFC.6050001@tana.it>
Date: Wed, 21 Aug 2013 16:13:16 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
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
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <E4FC3784-EA30-4927-A1D2-62B12E15196F@virtualized.org>
In-Reply-To: <E4FC3784-EA30-4927-A1D2-62B12E15196F@virtualized.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: Wed, 21 Aug 2013 14:14:11 -0000

On Tue 20/Aug/2013 07:27:12 +0200 David Conrad wrote:
> On Aug 19, 2013, at 10:14 PM, Randy Bush <randy@psg.com> wrote:
>>
>> one lesson i might take from this is, if i want to deploy a new
>> hack which needs an rrtype, not to use txt in the interim.

Nor the same format, IMHO.

> My personal belief is that the rationale to migrate away from TXT
> remains valid and the appropriate course of action is to fix the 
> migration strategy, not permanently encode what everyone agrees is a 
> hack into a proposed standard.

Normally, it's easier to have new births than to revive dead horses.

The proposed standard is what currently works.  By the time DKIM keys
are transmitted in binary, SPF will have a better spec too.