Re: [apps-discuss] Proposed "spfbis" working group charter

"Murray S. Kucherawy" <msk@cloudmark.com> Mon, 14 November 2011 06:18 UTC

Return-Path: <msk@cloudmark.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 0C47B11E80C1 for <apps-discuss@ietfa.amsl.com>; Sun, 13 Nov 2011 22:18:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.305
X-Spam-Level:
X-Spam-Status: No, score=-103.305 tagged_above=-999 required=5 tests=[AWL=0.294, BAYES_00=-2.599, 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 jnwECXuDBzRm for <apps-discuss@ietfa.amsl.com>; Sun, 13 Nov 2011 22:18:45 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA1611E8095 for <apps-discuss@ietf.org>; Sun, 13 Nov 2011 22:18:45 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Sun, 13 Nov 2011 22:18:45 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Date: Sun, 13 Nov 2011 22:18:42 -0800
Thread-Topic: [apps-discuss] Proposed "spfbis" working group charter
Thread-Index: Acyik8ou1EOvgCioQIGY/4BNOhoYHQAAKinQ
Message-ID: <F5833273385BB34F99288B3648C4F06F19C6C15010@EXCH-C2.corp.cloudmark.com>
References: <201111140546.pAE5k1aW035215@medusa.blackops.org> <4EC0B043.2060907@it.aoyama.ac.jp>
In-Reply-To: <4EC0B043.2060907@it.aoyama.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [apps-discuss] Proposed "spfbis" working group charter
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: Mon, 14 Nov 2011 06:18:46 -0000

> -----Original Message-----
> From: "Martin J. Dürst" [mailto:duerst@it.aoyama.ac.jp]
> Sent: Sunday, November 13, 2011 10:08 PM
> To: Murray S. Kucherawy
> Cc: apps-discuss@ietf.org
> Subject: Re: [apps-discuss] Proposed "spfbis" working group charter
> 
> I'm somewhat surprised that there is a long charter text, but it ends
> essentially with "what we'll do is in draft foo". I think the "what
> we'll do" is the core of the charter, and shouldn't be just a
> reference.

Hi Martin,

Can you explain how you got that?  I thought the charter was pretty clear about what is intended, rather than pointing off to what's in some draft.  In essence it says "Here's what we plan to do", followed by "Here's the draft where we've started doing it."

> At the absolute minimum, please refer to a numbered or dated version of
> draft-mehnle-spfbis-scope, otherwise its author(s) can easily change
> the scope of the WG.
> 
> In addition, draft-mehnle-spfbis-scope isn't even existing; I'm really
> not sure that's the way to charter a WG. Same for draft-kitterman-
> rfc4408bis.

Yes, it was ready only after the temporary embargo on postings was established.  He'll get it posted very soon now that it's lifted.  I sent him a reminder.

The other one is http://datatracker.ietf.org/doc/draft-kitterman-4408bis/, so the name is slightly wrong; easily fixed.

I haven't ever had the request to name a specific version as a starting point in a charter before, which is why it wasn't done here.

> If the above problems are sorted out, I also hope that the new WG can
> deal with EAI appropriately.

That is indeed a consideration; see http://datatracker.ietf.org/doc/draft-ellermann-spf-eai/.  The group could take this on as well, though the scope won't quite be so tight at first if it does.  I'm fine either way.

-MSK