Re: [spfbis] Review of draft-ietf-spfbis-experiment-05

Barry Leiba <barryleiba@computer.org> Mon, 23 April 2012 16:13 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 CECAC21F872B for <spfbis@ietfa.amsl.com>; Mon, 23 Apr 2012 09:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Qgnv-UkfEdig for <spfbis@ietfa.amsl.com>; Mon, 23 Apr 2012 09:13:57 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 18FD221F8725 for <spfbis@ietf.org>; Mon, 23 Apr 2012 09:13:57 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so7224004ghb.31 for <spfbis@ietf.org>; Mon, 23 Apr 2012 09:13:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Zol7pD5IlW2IdRwMMQ40AJcKrldxCtE1tTtOwJlxm/4=; b=RlyMNxtn5eHV54DOptecqpK8Q/rNTDEy+sUmOZFQTVQfFQrdO8UGTECq0rUMUJuUvs XZaG/WLJZyS7IKmFE0b7MTI8cBldbFYooFZCd0jTKYsYiqegBhPYudgdHKpGZD8IuD6x B+l+ShKiSEXEsQPvXdNR1UrnlntKwtQdtjoSXfOSZWuOAyxQlASYptb/rlJAdXVOhgjF z2/r5Vo49y51dwSoM5+wXmTlM/8snkkx5JLBTBXRh9TJNg1BFd2lDJwob1HCEaaU+HCG ycsxBE+nHs6CWKecDYqt3HpZrPmqQyi3LhbIIklJbTWFu8pTX9+GsIZnsmtL2ZBTcQK6 m1FQ==
MIME-Version: 1.0
Received: by 10.101.58.1 with SMTP id l1mr4677024ank.67.1335197636706; Mon, 23 Apr 2012 09:13:56 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.152.14 with HTTP; Mon, 23 Apr 2012 09:13:56 -0700 (PDT)
In-Reply-To: <63583111.FeGGmhBaS4@scott-latitude-e6320>
References: <CAC4RtVAV5PH+VMzppVxAQgGq0f28ARN846e17G_8sbLCThm-KA@mail.gmail.com> <3365685.ptXhF5PY8S@scott-latitude-e6320> <20120423145947.GH55520@mail.yitter.info> <63583111.FeGGmhBaS4@scott-latitude-e6320>
Date: Mon, 23 Apr 2012 12:13:56 -0400
X-Google-Sender-Auth: aAoG0gyBvowHyuvoPqRq2U_I1yA
Message-ID: <CAC4RtVCnFXT=goe0tgJjq1CsOV_TRK+XSR5GDu8DjGtVN7b8KA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Scott Kitterman <spf2@kitterman.com>
Content-Type: multipart/alternative; boundary="001636eee35ad7438504be5aeccc"
Cc: "spfbis@ietf.org" <spfbis@ietf.org>
Subject: Re: [spfbis] Review of draft-ietf-spfbis-experiment-05
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: Mon, 23 Apr 2012 16:13:57 -0000

> I'm arguing that the current text remain.

Scott is right that because what's there has rough consensus, he does not
need to establish consensus to leave it there.

That said, I think the current text ill-serves the document, so let me try
again.  How about this, which I think does not attempt to attribute
anything but the Experimental requirement to the old IESG:

OLD
   Due to the absence of consensus behind one or the other, and because
   Sender-ID supported use of the same policy statement defined by SPF,
   the IESG at the time was concerned that an implementation of
   Sender-ID might erroneously apply that statement to a message and,
   depending on selected recipient actions, could improperly interfere
   with message delivery.  As a result, the IESG required the
   publication of all of these documents as Experimental, and requested
   that the community observe deployment and operation of the protocols
   over a period of two years from the date of publication in order to
   determine a reasonable path forward.

NEW
   Consensus did not clearly support one protocol over the other, and
   there was significant concern that the two would conflict in some
   significant operational situations, interfering with message delivery.
   The IESG required the publication of all of these documents as
   Experimental, and requested that the community observe deployment
   and operation of the protocols over a period of two years from the date
   of publication in order to determine a reasonable path forward.

Does that work?  I think it says what it needs to say without trying to
either blame anyone or get into historical details that are not necessary
in this document.

Barry