Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

Frank Ellermann <nobody@xyzzy.claranet.de> Sat, 27 August 2005 00:02 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8o97-0005sJ-Mo; Fri, 26 Aug 2005 20:02:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8o95-0005sE-3u for ietf@megatron.ietf.org; Fri, 26 Aug 2005 20:02:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02138 for <ietf@ietf.org>; Fri, 26 Aug 2005 20:02:01 -0400 (EDT)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8o9t-0004Zs-Tx for ietf@ietf.org; Fri, 26 Aug 2005 20:02:54 -0400
Received: from root by ciao.gmane.org with local (Exim 4.43) id 1E8o7s-0000sG-TA for ietf@ietf.org; Sat, 27 Aug 2005 02:00:48 +0200
Received: from 62.80.58.221 ([62.80.58.221]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 27 Aug 2005 02:00:48 +0200
Received: from nobody by 62.80.58.221 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 27 Aug 2005 02:00:48 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sat, 27 Aug 2005 01:26:24 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 38
Message-ID: <430FA520.2EAB@xyzzy.claranet.de>
References: <198A730C2044DE4A96749D13E167AD375A2AB8@MOU1WNEXMB04.vcorp.ad.vrsn.com> <7ae58c22050826112058b14708@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 62.80.58.221
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: ietf-mxcomp@imc.org, spf-discuss@v2.listbox.com
Subject: Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Dotzero wrote:

> Writing a standard which subverts the intent of individuals
> publishing to a different and existing standard is simply
> unethical and wrong.

+1
 
> What happened was essentially a political move because people
> chose not to publish SPF2 records for PRA. So, the response
> was to force people to opt-out (publish an essentially
> meaningless SPF2 record) because the SID camp was losing in
> the real world marketplace.

+1

> One argument that was put forth after the announcement that
> SID would apply PRA to SPF1 records was that it was a
> conspiracy to get publishers to yank their SPF1 records.

Yes, when I said "excessive technical incompotence or outright
corruption" it wasn't the polite way to put it, but it was and
still is how I feel about it.

> People and organizations chose to publish a record according
> to a standard because they have a reasonable expectation on
> how that record will be used. While there may be edge cases
> of abuse, the expectation is that most people will respect
> the standard. That's why it's called a standard.

+1

> "Your honor, I have this alternative means of interpreting
> what a red stoplight indicates.....go go go as fast as you
> can".

LOL, precisely.  Full ACK on all your points, bye, Frank



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf