Re: [dnsext] [spfbis] Obsoleting SPF RRTYPE

Dotzero <dotzero@gmail.com> Thu, 25 April 2013 16:27 UTC

Return-Path: <dotzero@gmail.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 472B121F8613; Thu, 25 Apr 2013 09:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[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 oywa45NQFH0J; Thu, 25 Apr 2013 09:27:30 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6192021F9633; Thu, 25 Apr 2013 09:26:59 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id es20so2803456lab.27 for <multiple recipients>; Thu, 25 Apr 2013 09:26:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=g+VuFvXnjcjIFs6AMfbNW3UVe3fJaK2YkdVS4rx7nrs=; b=dMA/hlwcHFjo8llVOQJxidhmySvMl907juEEu9NwFXbrhXhMznCacKy07bNg7PmSFG bAj2B4KVDSDpwrWd3okkbmyvZtI/JVtBmjJ4CBT4O0MSmwAPsl272lvsbI0ffR6daLUo OiffQpXTrOOCt0+SIpHBQWEjq+NszX7dFKeh44w9SJIIz7VLPIfcTri5p8IbiXP6ZcBr 0+20xmyePFVU9s8IgBbMNObk1EvBB2pTMHVpdumGw0SjT202dFHxPLTGmYp+b3Wd//QS 2bjKkHF2VIhUuMQbWSvroQGl6soweIsJnUMhmxFabE2LB9zP7H7GWKYu1c12sTwqKo4R RyIA==
MIME-Version: 1.0
X-Received: by 10.112.135.133 with SMTP id ps5mr6641222lbb.42.1366907211779; Thu, 25 Apr 2013 09:26:51 -0700 (PDT)
Received: by 10.112.72.166 with HTTP; Thu, 25 Apr 2013 09:26:51 -0700 (PDT)
In-Reply-To: <20130425154235.GP23770@besserwisser.org>
References: <20130425013317.36729.qmail@joyce.lan> <80ADB3EE-17FD-4628-B818-801CB71BCBFE@virtualized.org> <BB8C643A-FC46-4B2F-B677-F1B7CAB0E79F@frobbit.se> <alpine.BSF.2.00.1304251030380.65043@joyce.lan> <14A728AE-83DC-4C1F-A88A-6F988D37F2C7@frobbit.se> <20130425154235.GP23770@besserwisser.org>
Date: Thu, 25 Apr 2013 12:26:51 -0400
Message-ID: <CAJ4XoYdF9S984wmk1vP5-o9vFxrqF3uyp0P9Kq_7BbfuNqV2-A@mail.gmail.com>
From: Dotzero <dotzero@gmail.com>
To: Måns Nilsson <mansaxel@besserwisser.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 25 Apr 2013 09:42:31 -0700
Cc: spfbis@ietf.org, "dnsext@ietf.org Group" <dnsext@ietf.org>
Subject: Re: [dnsext] [spfbis] Obsoleting SPF RRTYPE
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 16:27:48 -0000

On Thu, Apr 25, 2013 at 11:42 AM, Måns Nilsson
<mansaxel@besserwisser.org> wrote:
> Subject: Re: [dnsext] Obsoleting SPF RRTYPE Date: Thu, Apr 25, 2013 at 05:03:55PM +0200 Quoting Patrik Fältström (paf@frobbit.se):
>>
>> On 25 apr 2013, at 16:44, John R Levine <johnl@taugh.com> wrote:
>>
>> > In any event, the SPF draft is in WGLC.  Feel free to read the extensive discussion in the list archives and let them know how you feel.
>>
>> They know how i feel. We in IETF do believe in rough consensus. I am this time on the rough side.
>>
>> That does not imply I am quiet in other places, and I am as many others nervous over the implications.
>
> This is a slippery slope. One record overload is not bad, but it sort
> of opens the floodgates for systematic overloading. DNSEXT and DNSOP
> certainly need to get involved; because this is way bigger than just SPF.
>
> And IMNSHO spfbis is out of scope prescribing TXT records, just because
> of this contagiousness.
>

It is not so much that SPFbis is prescribing practice as it is
updating to describe practice and avoid potential problems that have
been identified with having both TXT and type 99 records (without a
lot of verbage to address hypothetical future use).

> For the record: I think that the spfbis draft is unfit for publication
> as RFC unless TXT records are deprectaed as only carrier of data.
>

Would you be any happier if the WG left type 99 records and in a coy
manner made it clear that usage is overwhelmingly TXT based with
little likelyhood of type 99 gathering any meaningful traction? I'm
sure that if the issues surrounding adoption of new RR types were
resolved we would not be having this discussion - but they haven't
been resolved.

Mike