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

Alex Loret de Mola <edgarverona@gmail.com> Tue, 10 February 2009 20:52 UTC

Return-Path: <edgarverona@gmail.com>
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 174BD3A6AB3 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 12:52:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=-0.049, 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 2fbgJENLZdbX for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 12:52:27 -0800 (PST)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by core3.amsl.com (Postfix) with ESMTP id CA2013A684F for <ietf@ietf.org>; Tue, 10 Feb 2009 12:52:26 -0800 (PST)
Received: by an-out-0708.google.com with SMTP id b2so28944ana.4 for <ietf@ietf.org>; Tue, 10 Feb 2009 12:52:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=LGMZgveeJ8nbwGKfw2RLItC0DJJeJE4Ckm9ITTVvnTo=; b=EaEIixSEj6hRZS99QwNAMbmD6UkJSEyTyn335YVSydmW7dUt1qrLk/Vfv/uOscxczl jpYic566ZLb5IRtt+sBrc5Ue/3xGpEAMPZod6pCAiqNkOx4h/S97SE7S5yVHVbqqmH07 o+kNc+rK3EMwBn0gIxnlmR4xWXK+kmIWMVMCc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=DMzifMXLmNz4Kr9pxoycWLj1wpodbc4M9SRWkD5eHlrDARcIrkjnixKOeZuFH1CXE3 oynTdUU3LxOhAMPeSJbAqBI1CHJONQrIFOT8A1bucR/Yd+ij+4+QTNmAF87BeOJRZO5H i59zk5WXhfo/BPq+I7m1ED7NnbkeG7ADGYF8c=
MIME-Version: 1.0
Received: by 10.100.57.13 with SMTP id f13mr3860737ana.143.1234299149173; Tue, 10 Feb 2009 12:52:29 -0800 (PST)
Date: Tue, 10 Feb 2009 15:52:29 -0500
Message-ID: <789dbae90902101252p5d589ec4y97d5d3b88b077094@mail.gmail.com>
Subject: Ah, I see the cause of the situation now... (tls-authz situation)
From: Alex Loret de Mola <edgarverona@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 20:52:28 -0000

Dear All:

I have received a reply from the Free Software Foundation as to why
they directed comments to this list.

The last call (http://www.ietf.org/mail-archive/web/ietf-announce/current/msg05617.html)
instructs the public to contact this mailing list in order to express
their comments.

In light of that, I can see how the FSF considered it reasonable to
send public comments this way.

Most notably:

"The IESG is considering approving this draft as a standards track
RFC. The IESG solicits final comments on whether the IETF community
has consensus to publish draft-housley-tls-authz-extns as a proposed
standard. Comments can be sent to ietf at ietf.org or exceptionally to
iesg at ietf.org. Comments should be sent by 2009-02-11."

If the intent wasn't to solicit these kinds of responses, the wording
of last calls may need to be amended in the future, and clarified so
that exactly what is meant by "comments" and if they should actually
be sent to this list.  However, unless an alternative avenue was given
it may degrade the reason why last calls are publicized to begin with.

Even if this situation has happened before, the wording of last calls
does seem to imply that comments are encouraged for the purpose of
determining consensus.  Given that, it seems unfair to have chastised
these people for having done what the message last Call was asking
them to do, even if the people making said comments may not have been
fully versed on the subject.

Hopefully, now that dialog is opened up and the suggestions given to
me to pass to the FSF have been received, they can go through one of
those avenues.  But last calls, if they're not meant to encourage the
kind of response that occurred, should probably be reworded if there
is an alternative place for them to make statements.

Sincerely,

Alex Loret de Mola