Re: Ah, I see the cause of the situation now... (tls-authz situation)

jnc@mercury.lcs.mit.edu (Noel Chiappa) Tue, 10 February 2009 21:39 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 093763A6D5D for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 13:39:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 8AfxfRfCLZm3 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 13:39:13 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 413F73A6D56 for <ietf@ietf.org>; Tue, 10 Feb 2009 13:39:13 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id BACF76BE55F; Tue, 10 Feb 2009 16:39:13 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Ah, I see the cause of the situation now... (tls-authz situation)
Message-Id: <20090210213913.BACF76BE55F@mercury.lcs.mit.edu>
Date: Tue, 10 Feb 2009 16:39:13 -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: Tue, 10 Feb 2009 21:39:14 -0000

    > From: Alex Loret de Mola <edgarverona@gmail.com>

    > The last call ... instructs the public to contact this mailing list in
    > order to express their comments.

No, it instructs _the people it was sent to_, the IETF community (which is of
course open to anyone who wants to join, with no pre-conditions or cost), not
"the public". Viz.:

    >> This Last Call is intended to determine whether the IETF community had
						       ^^^^^^^^^^^^^^^^^^
    >> consensus to publish draft-housley-tls-authz-extns as a proposed
    >> standard 
    >> ...
    >> The IESG solicits final comments on whether the IETF community has
						   ^^^^^^^^^^^^^^^^^^
    >> consensus to publish draft-housley-tls-authz-extns as a proposed
    >> standard.

This doesn't mean hundreds of Toms, Sallies and Harries who have no
familiarity with the IETF, or any detailed knowledge of the specifics of the
case, are being encouraged to basically cut-and-paste comments from a press
release (which is effectively what the FSF document is) and spam the community
list with them.

(The IETF community of course is fully aware that to do so would be unwelcome
in the extreme, so we don't need to add instructions to _them_ not to drill
holes in their skulls.)


    > If the intent wasn't to solicit these kinds of responses, the wording
    > of last calls may need to be amended in the future

Well, that might be useful. Maybe a link to a web page with fuller
comment on the subject?

	Noel