IETF Logo Mail Archive

RE: [Fwd: Re: Changes needed to Last Call boilerplate]

jnc@mercury.lcs.mit.edu (Noel Chiappa) Fri, 13 February 2009 17:27 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 E256028C134 for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 09:27:34 -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=[AWL=0.000, 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 YW9KQAl1vd5e for <ietf@core3.amsl.com>; Fri, 13 Feb 2009 09:27:34 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 13DC128C19C for <ietf@ietf.org>; Fri, 13 Feb 2009 09:27:33 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id AE26B6BE54C; Fri, 13 Feb 2009 12:27:37 -0500 (EST)
To: ietf@ietf.org
Subject: RE: [Fwd: Re: Changes needed to Last Call boilerplate]
Message-Id: <20090213172737.AE26B6BE54C@mercury.lcs.mit.edu>
Date: Fri, 13 Feb 2009 12:27:37 -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: Fri, 13 Feb 2009 17:27:35 -0000

    > From: "HUANG, ZHIHUI (JERRY), ATTLABS" <jhuang1@att.com>

    > asking only "the IETF community" to respond to LC and even explicitly
    > state that "one should only respond (to LC) if he's subscribed to foo
    > and bar IETF mailing list" will probably not deter people from
    > 'drive-by' subscribing and posting of knee-jerk comments.

Hence my suggestion of a separate mailing list. If the only list mentioned
in the LC is "ietf-comments", I think people are not likely to find "ietf"
on their own.

Oh, and that suggestion that we change the wording to be "The IESG solicits
final comments from the IETF community on whether the IETF community has
consensus to publish" - that would be a good idea to do if we _don't_ set up a
separate mailbox. If we _did_, we should leave it out, so that the public
_does_ have someplace to send comments. Still, IMO 'one mailbox, no public
comments' and 'one mailbox, accept public comments' are both inferior (for
different reasons) to 'two mailboxes, accept public comments'.

    > But that's what will amount to if .. (3) no regulars would take the
    > risk to subscribe to the new mailing list. So no comment on the new
    > mailing list would effectively be heard.

I was not recommended that the new mailbox be a bit-bucket - I explicitly
called for it to be monitored by someone(s) who would bring anything novel
and/or significant to all our attention.

	Noel

v2.23.0 | Report a Bug | By Email