Changes needed to Last Call boilerplate

jnc@mercury.lcs.mit.edu (Noel Chiappa) Thu, 12 February 2009 23:31 UTC

Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 909B128C232 for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 15:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 85TZDB0w0IyY for <ietf@core3.amsl.com>; Thu, 12 Feb 2009 15:31:47 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id D7D2128C278 for <ietf@ietf.org>; Thu, 12 Feb 2009 15:31:47 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id D779D6BE551; Thu, 12 Feb 2009 18:31:48 -0500 (EST)
To: ietf@ietf.org
Subject: Changes needed to Last Call boilerplate
Message-Id: <20090212233148.D779D6BE551@mercury.lcs.mit.edu>
Date: Thu, 12 Feb 2009 18:31:48 -0500
From: jnc@mercury.lcs.mit.edu
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2009 23:31:48 -0000

I've heard from a number of the FSF thundering herd people to the effect of
'but the announcement says send email to ietf@ietf.org". (They're
conveniently ignoring the fact that it says "the IETF community" all over the
place in the Last Call, but never mind.)

So clearly we need to change it to say something like:

 Members of the IETF can send email to ietf@ietf.org. Members of the public
 to whom this Last Call is forwarded, you can send email to
 ietf-comment@ietf.org, but we cannot guarantee to do anything with comments
 at such a late stage in the process. Please join the IETF if you wish to
 influence standards while the are being worked on; see
 http://www.ietf.org/<mumble> for instructions on how to do that.

(For "Members of the IETF" we can substitute "People who are subscribed to
the IETF Discussion list", if people think that is needed in place of the
technically somewhat nebulous "Members of the IETF".)

And hopefully we can get a few brave souls to volunteer to read ietf-comment,
and send on any comments which are novel and or important.

    Noel