IETF Logo Mail Archive

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

Scott Kitterman <scott@kitterman.com> Thu, 11 August 2011 17:58 UTC

Return-Path: <scott@kitterman.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 9C25021F8C00 for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 10:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 KAtwgBTXCpY2 for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 10:58:18 -0700 (PDT)
Received: from mailout00.controlledmail.com (mailout00.controlledmail.com [72.81.252.19]) by ietfa.amsl.com (Postfix) with ESMTP id 3107921F8C07 for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 10:58:18 -0700 (PDT)
Received: from mailout00.controlledmail.com (localhost [127.0.0.1]) by mailout00.controlledmail.com (Postfix) with ESMTP id CDCBE38C131; Thu, 11 Aug 2011 13:58:52 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1313085532; bh=AE9GyG++fpKwOkahDSrFuBFCQZRqiN5gz1SSp4J7tXU=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=eWTZYDhW8A9eNNAgtVU5r4GRXm69gioxm3AKzdWAPzYwOaYZMSBd3Dxp/0/uCl8KV QY1t/rIGYmHZckKenFI+9BY5eXMP+Qx5LpYpbhMUE4UWPjmPNXDJXiA82Nsi52qQqG rvakieGarDWojuqsFaMgAcTqE/O1b6KLvKlgw+1o=
From: Scott Kitterman <scott@kitterman.com>
To: apps-discuss@ietf.org
Date: Thu, 11 Aug 2011 13:58:51 -0400
User-Agent: KMail/1.13.6 (Linux/2.6.38-10-generic-pae; KDE/4.6.2; i686; ; )
References: <20110809225415.89118.qmail@joyce.lan> <201108111351.34118.scott@kitterman.com> <F5833273385BB34F99288B3648C4F06F13512DF6CC@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF6CC@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201108111358.51671.scott@kitterman.com>
X-AV-Checked: ClamAV using ClamSMTP
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 17:58:18 -0000

On Thursday, August 11, 2011 01:53:22 PM Murray S. Kucherawy wrote:
> > -----Original Message-----
> > From: apps-discuss-bounces@ietf.org
> > [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Scott Kitterman
> > Sent: Thursday, August 11, 2011 10:52 AM
> > To: apps-discuss@ietf.org
> > Subject: Re: [apps-discuss] Updating the status of SPF
> > 
> > I'm not sure in IETF terms what the best way to address this in a charter
> > would be.  Suggestions?
> 
> 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."

That sounds good to me.

Scott K

v2.29.0 | Report a Bug | By Email | System Status