Re: [spfbis] Proof of non-deployment [root@primary.se: Cron <root@primary> /usr/local/libexec/spf-txt.sh]

S Moonesamy <sm+ietf@elandsys.com> Tue, 07 October 2014 14:37 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E2F31ACDA4 for <spfbis@ietfa.amsl.com>; Tue, 7 Oct 2014 07:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level:
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.786, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1BDkuA4VmfV for <spfbis@ietfa.amsl.com>; Tue, 7 Oct 2014 07:37:21 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 77C0F1A6F3D for <spfbis@ietf.org>; Tue, 7 Oct 2014 07:37:21 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.129.236]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s97Eb3EP006659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Oct 2014 07:37:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1412692636; x=1412779036; bh=kAW5noSWW0eKzmahd4k4BXN8McGSrBm4LUkLsMuACFM=; h=Date:To:From:Subject:In-Reply-To:References; b=zFngK5rfBUNDzbf7m9wni99Rk7o+q8boKbehqfN1w+Vb/dsRETV7IZPMTWkXCWpBN 93C+DQNGabsxASuFdAm7UfiOcdPQHVIzo0Ow2fLSqB9wVNiWY+XUIHwRTzz5lQGl06 ihlbCPVAJ5qrWPvjKgRVlT1p7noc85te3GJhXaMM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1412692636; x=1412779036; i=@elandsys.com; bh=kAW5noSWW0eKzmahd4k4BXN8McGSrBm4LUkLsMuACFM=; h=Date:To:From:Subject:In-Reply-To:References; b=QV8FVCVY/bpHsoykaCrNAbQcelyqjNxLbXKCRhlYqfcPWq3wsVjbBaMW3o2EgVoeF oWD1c2pbWwZpolY+cJfdNmywKq67DO6m6Ek+As2Fs2OTK+/wYHUpPkAG5TzZ8I45Xo eiRA/TgV9LBLA4/RjJMtDUTfxaSPnGFGGjI+zWj4=
Message-Id: <6.2.5.6.2.20141007065756.0be13418@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 07 Oct 2014 07:31:09 -0700
To: Mans Nilsson <mansaxel@besserwisser.org>, spfbis@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <20141007063737.GA28581@besserwisser.org>
References: <20141007063737.GA28581@besserwisser.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/spfbis/kaLTXbGBJLPxFBlaOYVz-hzA15I
Subject: Re: [spfbis] Proof of non-deployment [root@primary.se: Cron <root@primary> /usr/local/libexec/spf-txt.sh]
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 07 Oct 2014 14:37:24 -0000

Hello,
At 23:37 06-10-2014, Mans Nilsson wrote:
>Since only 14.82 percent of the combined TXT||SPF queries received by my
>authoritative master are SPF we must surely congratulate the SPF working
>group in being correct by determining that there are impassable barriers
>to deplying new RR types on the Internet. Only 1 in 7 queries  --
>clearly a minority -- are for this new, unusable RR type.

The following is from the write-up:

    "There was an intermediate conclusion about the topic of whether the SPF
     protocol should use the SPF RRTYPE or the TXT resource record.  It was
     followed by an objection.  After discussion of the topic at the IETF 83
     SPFBIS WG session the conclusion reached was that the decision would be
     not to publish RRTYPE 99 and and not to query RRTYPE 99.  The WG
     consensus about the RRTYPE can be described as particularly rough.  The
     topic of obsoleting the SPF RRTYPE generated a lot of controversy near
     the end of the WGLC.  There were a very high number of messages about
     the topic on the SPFBIS mailing list and the DNSEXT mailing list as some
     DNSEXT WG participants were not aware of RFC 6686."

The decision about which RR type to choose was not about one of them 
being clearly a minority.  I went through the discussions about the 
RR Type several times.  I also did that after the decision was taken 
to see whether it was the wrong choice.  A choice had to be made.  I 
am okay with being criticized for that choice.

Regards,
S. Moonesamy