Re: [spfbis] The RRTYPE topic (was: WGLC: draft-ietf-spfbis-4408bis-14)

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 30 May 2013 01:15 UTC

Return-Path: <ajs@anvilwalrusden.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 98A2421F939E for <spfbis@ietfa.amsl.com>; Wed, 29 May 2013 18:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level:
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 qXlXoWPxVnZA for <spfbis@ietfa.amsl.com>; Wed, 29 May 2013 18:15:40 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id C92FE21F93C4 for <spfbis@ietf.org>; Wed, 29 May 2013 18:15:40 -0700 (PDT)
Received: from mx1.yitter.info (c-50-136-77-224.hsd1.nh.comcast.net [50.136.77.224]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 2CE318A038 for <spfbis@ietf.org>; Thu, 30 May 2013 01:15:40 +0000 (UTC)
Date: Wed, 29 May 2013 21:15:41 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: spfbis@ietf.org
Message-ID: <20130530011540.GE43673@mx1.yitter.info>
References: <CAL0qLwan7JO4t2UB1uWYwwf1MmwhY56szenSY7awT_pNP5UjLg@mail.gmail.com> <B6A88D56-9318-40A3-8E0C-A49EE37A3F3F@gmail.com> <20130529143635.GZ23227@verdi> <CD0B53CE-E90E-4296-B724-0749361D7626@gmail.com> <20130529202145.GA9506@mx1.yitter.info> <20130529212602.5909734DBABF@drugs.dv.isc.org> <20130529214234.GB9584@mx1.yitter.info> <20130529220822.2326134DBF6E@drugs.dv.isc.org> <CAL0qLwa2Eh_tbSHCULhUGALf_hNOmOW01HA6pPgVPfDK2YMEhA@mail.gmail.com> <20130530003906.6983934DF471@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20130530003906.6983934DF471@drugs.dv.isc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [spfbis] The RRTYPE topic (was: 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: Thu, 30 May 2013 01:15:46 -0000

No hat.

On Thu, May 30, 2013 at 10:39:05AM +1000, Mark Andrews wrote:

> You have a DNS record with a mnemonic of SPF that is not to be used
> for SPF.  What does the instruction "Put a SPF record in the DNS"
> mean?  Will it result in a type 99 record being added?  How will
> such errors be prevented?

Wouldn't it be good of name servers to detect someone attempting to
serve a deprecated RRTYPE, and warn them of this?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com