RE: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC

"Brian Rosen" <br@brianrosen.net> Thu, 24 February 2005 19:13 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01637; Thu, 24 Feb 2005 14:13:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Onu-0007ae-Nf; Thu, 24 Feb 2005 14:37:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4ONQ-0001Nj-JC; Thu, 24 Feb 2005 14:10:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4ONO-0001Lo-0p for ietf@megatron.ietf.org; Thu, 24 Feb 2005 14:10:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01246 for <ietf@ietf.org>; Thu, 24 Feb 2005 14:10:16 -0500 (EST)
Message-Id: <200502241910.OAA01246@ietf.org>
Received: from dx28.winwebhosting.com ([70.85.77.84]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4OkL-0007Te-A3 for ietf@ietf.org; Thu, 24 Feb 2005 14:34:01 -0500
Received: from acs-24-154-127-163.zoominternet.net ([24.154.127.163] helo=BROSENLT) by dx28.winwebhosting.com with esmtpa (Exim 4.44) id 1D4ONH-0000Fx-VB for ietf@ietf.org; Thu, 24 Feb 2005 13:10:12 -0600
From: Brian Rosen <br@brianrosen.net>
To: ietf@ietf.org
Date: Thu, 24 Feb 2005 14:10:05 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <E1D3b8C-0007jf-Qd@newodin.ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcUaKi0/ErVzaGhARRGzWtUCYP6zngAdyHWw
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - dx28.winwebhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Subject: RE: Last Call: 'Labels in Subject Headers Considered Ineffective At Best' to Informational RFC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit

I read the first draft of this document, and wondered:
Does this propose to change IETF behavior on list management, so that the
name of the list (usually same as working group) is not put in the Subject:
using the feature of mailman that does this?

When it was just a draft, it was just speculation.

Now that the IESG is considering this draft, I want to ask:
Is that what you have in mind?

I think having the IETF list traffic have the solicitation class keyword
marked appropriately is a good idea.

I think having every email program on the planet become capable of filtering
on this keyword is a good idea.

I think having every email program on the planet become capable of
displaying this field when it is not empty has some value, but I'm not sure
what the tradeoffs are when the display is small, as on a PDA or mobile
phone.

However, until we get the latter two accomplished, I want the list manager
to mark the Subject: with the name of the list.

I don't know about you, but what I have today (very popular email program
from a gigantic company and very cool cellphone/PDA combo thingy that works
pretty darn nice for email) WILL NOT WORK WELL FOR ME if Subject is not
marked.  One does not have filters, and does not have a way to display an
arbitrary header field.  One has filters, but I don't see a filter mechanism
for "Solicitation Class", and I don't see that key word in the fields I can
display, although there appears to be a way to define your own field so
maybe that would work.  Dunno, but unless it works at least as well as
marking Subject, I don't want to get rid of that feature.

So, I ask that the author of the draft state his intentions with respect to
IETF list management, and that such an intention form part of the
consideration of the IETF on what to do with the draft.

Brian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Tuesday, February 22, 2005 9:35 AM
> To: IETF-Announce
> Subject: Last Call: 'Labels in Subject Headers Considered Ineffective At
> Best' to Informational RFC
> 
> The IESG has received a request from an individual submitter to consider
> the
> following document:
> 
> - 'Labels in Subject Headers Considered Ineffective At Best '
>    <draft-malamud-subject-line-02.txt> as an Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2005-03-22.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-malamud-subject-line-02.txt
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
> 




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf