Re: [apps-discuss] Updating the status of SPF

Barry Leiba <barryleiba@computer.org> Thu, 11 August 2011 19:37 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C33CC21F8B4A for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 12:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.043
X-Spam-Level:
X-Spam-Status: No, score=-103.043 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 eETEuLVK7em9 for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 12:37:51 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD6B21F8B48 for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 12:37:51 -0700 (PDT)
Received: by yie12 with SMTP id 12so1825238yie.31 for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 12:38:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=B+O3QBBRozpHO0DWeIM/FWnC6SmyytFV499yftguGeE=; b=vkCc7bfGgJZAcm2pHcDe1r1gEkFRH3bHHiiMOcDxg0RL7LNxtFwJj6mGnThHfKIrvc NAJF7LXLeUmE7mhZf2m5tnYBdSDAi0dZF5INfLBd1ZW51Ker+yG1uBw0zCdEFKXFyOTF 2vqGEzyjexDQp/odcxtaHOIX0SUtyi0cLpM2w=
MIME-Version: 1.0
Received: by 10.146.140.9 with SMTP id n9mr7222yad.39.1313091505469; Thu, 11 Aug 2011 12:38:25 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.181.13 with HTTP; Thu, 11 Aug 2011 12:38:25 -0700 (PDT)
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF6CC@EXCH-C2.corp.cloudmark.com>
References: <20110809225415.89118.qmail@joyce.lan> <CAC4RtVBr2D+7UkFMyaL6inwvA0cPOg-Td39xSfLoG5wtVVyGFA@mail.gmail.com> <CAHhFybohD77f5t8cOZk7RcgYsgaW8z919EpRCd2ek9bAsrrXYg@mail.gmail.com> <201108111351.34118.scott@kitterman.com> <F5833273385BB34F99288B3648C4F06F13512DF6CC@EXCH-C2.corp.cloudmark.com>
Date: Thu, 11 Aug 2011 15:38:25 -0400
X-Google-Sender-Auth: VDDJGZNCDL0FPt2HaYII10cqIBg
Message-ID: <CAC4RtVATWMOxx6h+jW8oc9hOXTRr3xuw0=Owr=TUCdVWw=XdiQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Updating the status of SPF
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 19:37:51 -0000

> I would merely add a charter point saying something like "The working group
> shall ensure that no changes are made that prevent full backward compatibility
> with RFC4408 unless such changes are urgently needed."

I think the real point here is not just to *say* that, but to explain
what's going on.  Put it in the context of what the WG *is* and
*isn't* doing at this stage.

That means that what you want to say is that the working group is, at
this charter stage, documenting the *existing*, widely implemented
protocol, which has sufficiently broad, interoperable deployment to be
on Standards Track.  Say that there are suggestions for changes that
are not part of the current widespread implementation, some of which
are not backward compatible, and that *all* these changes (whether
backward compatible or not) could be in scope for a future recharter
or new working group, but are not in scope here.

Barry, as participant