Re: [Tools-discuss] Ballot position change email subject (was Re: Tim Polk's No Objection on draft-ietf-proto-wgdocument-states-10: (with COMMENT))

Robert Sparks <rjsparks@nostrum.com> Fri, 10 December 2010 14:38 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@core3.amsl.com
Delivered-To: tools-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F084E3A6B07; Fri, 10 Dec 2010 06:38:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level:
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 JLzE3RaeibvW; Fri, 10 Dec 2010 06:38:15 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id EF2063A6944; Fri, 10 Dec 2010 06:38:14 -0800 (PST)
Received: from [192.168.2.105] (pool-173-71-48-4.dllstx.fios.verizon.net [173.71.48.4]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id oBAEdfDP074083 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Dec 2010 08:39:41 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <07b901cb9847$4eeff600$eccfe200$@huawei.com>
Date: Fri, 10 Dec 2010 08:39:41 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDB79CF5-7D6D-4DCD-9A14-021E8011356D@nostrum.com>
References: <20101208220838.12463.53600.idtracker@localhost> <047e01cb972e$69049970$3b0dcc50$@huawei.com> <8FEE66C9-DB75-4E33-979B-65A75BE41CCE@nostrum.com> <07b901cb9847$4eeff600$eccfe200$@huawei.com>
To: Adrian.Farrel@huawei.com
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 173.71.48.4 is authenticated by a trusted mechanism)
Cc: 'Tim Polk' <tim.polk@nist.gov>, 'The IESG' <iesg@ietf.org>, tools-discuss@ietf.org
Subject: Re: [Tools-discuss] Ballot position change email subject (was Re: Tim Polk's No Objection on draft-ietf-proto-wgdocument-states-10: (with COMMENT))
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2010 14:38:17 -0000

On Dec 10, 2010, at 2:50 AM, Adrian Farrel wrote:

> Robert,
> 
> It would be a mistake to think that I "feel strongly enough" about anything to
> spend time arguing about it. (Maybe not something to say during the NomCom
> period!)
> 
> I see your motivation here and understand it.
> The only thing I can think to add to your considerations is:
> Is it the final state ("no objection") that is interesting, or is it the change
> from the previous state ("Discuss cleared")?

Well, it's the current state, not necessarily the final state.

Not all No Objection states come after DISCUSS states. The initial position is often _very_ interesting.

Adding the old state to the Subject line (if there was an old state) would complicate searches.

> 
> Cheers,
> Adrian
> 
>> -----Original Message-----
>> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
>> Robert Sparks
>> Sent: 10 December 2010 03:30
>> To: Adrian.Farrel@huawei.com
>> Cc: 'Tim Polk'; 'The IESG'; tools-discuss@ietf.org
>> Subject: Ballot position change email subject (was Re: Tim Polk's No Objection
> on
>> draft-ietf-proto-wgdocument-states-10: (with COMMENT))
>> 
>> I had my fingers in this last, and I thought about the layout of the subject
> line
>> quite a bit
>> before laying it out this way.
>> 
>> The short answer is that you can't win - sometimes the emphasis needs to be on
>> whether there's
>> a comment, sometimes the most important piece of information is that the
>> position has changed.
>> The best we can do is get all the information on the line to facilitate
> searches.
>> 
>> This layout will be the most useful to me in forming searches later. That
> said,
>> I don't care what that order the information comes in as long as its all
> there.
>> I do care that we pick a way and leave it alone for awhile so that good search
> tools
>> can actually
>> be built.
>> 
>> With that in mind, do you feel strongly enough about this to argue for
> changing
>> it?
>> 
>> RjS
>> 
>> 
>> On Dec 8, 2010, at 5:19 PM, Adrian Farrel wrote:
>> 
>>> Folks, this subject line looks like a bug to me.
>>> 
>>> The email thread will be about the COMMENT, not about the No Objection
>>> 
>>> Cheers
>>> Adrian
>>> 
>>>> -----Original Message-----
>>>> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
>> Tim
>>>> Polk
>>>> Sent: 08 December 2010 22:09
>>>> To: The IESG
>>>> Cc: edj.etc@gmail.com; draft-ietf-proto-wgdocument-states@tools.ietf.org
>>>> Subject: Tim Polk's No Objection on draft-ietf-proto-wgdocument-states-10:
>>>> (with COMMENT)
>>>> 
>>>> Tim Polk has entered the following ballot position for
>>>> draft-ietf-proto-wgdocument-states-10: No Objection
>>>> 
>>>> When responding, please keep the subject line intact and reply to all
>>>> email addresses included in the To and CC lines. (Feel free to cut this
>>>> introductory paragraph, however.)
>>>> 
>>>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>> 
>>>> 
>>>> 
>>>> ----------------------------------------------------------------------
>>>> COMMENT:
>>>> ----------------------------------------------------------------------
>>>> 
>>>> In section 3.1, the document state withdrawn is listed but is not defined
> and
>> no
>>>> reference is given.  Text was added that indicated this is
> self-explanatory, but I
>>>> must be dense since I still don't know what it means,
>>>> 
>>>> I do not want to delay things further, though, and see no harm in moving
>> forward
>>>> with this text.
>>> 
>