[yam] Another thought on the template

John C Klensin <john-ietf@jck.com> Fri, 14 August 2009 14:33 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7253E28C14C for <yam@core3.amsl.com>; Fri, 14 Aug 2009 07:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.428
X-Spam-Level:
X-Spam-Status: No, score=-2.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65O1XVFLow4P for <yam@core3.amsl.com>; Fri, 14 Aug 2009 07:33:10 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 9FFE03A6AFE for <yam@ietf.org>; Fri, 14 Aug 2009 07:33:10 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1MbxqE-000ADX-20 for yam@ietf.org; Fri, 14 Aug 2009 10:33:14 -0400
Date: Fri, 14 Aug 2009 10:33:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: yam@ietf.org
Message-ID: <ECF183775FE757FAA8EC5620@PST.JCK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [yam] Another thought on the template
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Aug 2009 14:33:11 -0000

After thinking about this a little more, and reflecting back on
the long period of discussions before we moved into a charter
proposal, I think that we need to stay tightly focused on
objectives and avoid having things in the template (or
elsewhere) that might be distractions.  Put more specifically:

The YAM objective, reflected in the Charter, is only to move
documents from Draft to Full Standard, not to invent and examine
other requirements.  Let's reinforce that, and remind WG
participants, by including the relevant requirements excerpts
from 2026 in the template and by removing anything, such as the
interoperability statement pointer, that is not part of this
stage of advancement in maturity level.

Just a proposal, but one that I think may be essential to our
trying to make the sort of fast-track progress that we intend
and anticipate.

    john