RE: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]

<l.wood@surrey.ac.uk> Sat, 08 June 2013 10:09 UTC

Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1797921F9A3A for <ietf@ietfa.amsl.com>; Sat, 8 Jun 2013 03:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level:
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXVLMwL5rEq0 for <ietf@ietfa.amsl.com>; Sat, 8 Jun 2013 03:09:23 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.144]) by ietfa.amsl.com (Postfix) with ESMTP id D171921F9A35 for <ietf@ietf.org>; Sat, 8 Jun 2013 03:09:22 -0700 (PDT)
Received: from [195.245.231.67:32799] by server-8.bemta-5.messagelabs.com id B0/16-29170-1D203B15; Sat, 08 Jun 2013 10:09:21 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-82.messagelabs.com!1370686160!29669401!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received:
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26070 invoked from network); 8 Jun 2013 10:09:20 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-6.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 8 Jun 2013 10:09:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Sat, 8 Jun 2013 11:09:20 +0100
From: l.wood@surrey.ac.uk
To: glenzorn@gmail.com, ietf@ietf.org
Date: Sat, 08 Jun 2013 11:09:19 +0100
Subject: RE: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
Thread-Topic: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
Thread-Index: Ac5kEeT8b9+RdDP+So242SvCBA6nFQAHNOXg
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EA4@EXMB01CMS.surrey.ac.uk>
References: <201306070453.r574r3Wt010088@rotala.raleigh.ibm.com> <CADnDZ89FjyPtvJQSqY+kmX+1KYkc0jo1mRpOgkfcEnTH6Vbg6A@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA462@mbx-01.win.nominum.com> <201306071449.r57EnN5N008971@cichlid.raleigh.ibm.com> <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com> <CABCOCHR+5M06ToW4jLzALv+FuNHiVbytCGEgkQ3JvG4aUBty=w@mail.gmail.com> <CAK=bVC8ZQ6bZP7V2KWp2Lj3nt-Hd=0camBFqT=ThCKJwqGf0Zw@mail.gmail.com> <51B223C7.2010401@braga.eti.br> <51B23A06.7060402@gmail.com>, <51B2CFB2.3010803@gmail.com>
In-Reply-To: <51B2CFB2.3010803@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sat, 08 Jun 2013 10:09:28 -0000

I believe that last calls must stay on this ietf list.

Any last-call-only list must be *in addition* to the ietf list, with all announcements crossposted, and anyone sensitive to general discussion can subscribe to that instead.

Last calls need wide exposure.

(I'm acked in at least one RFC as a result of discussion on this list as a result of last call.)

I'd go further and say that if you're contributing to an ietf workgroup, subscribing to ietf and ietf-announce should be mandatory for posting rights in that group. Sure, you can filter the mails to /dev/null, but getting a broad idea of what's going on is a good thing, no? I'm willing to bet that at least half of our design problems have resulted from people doing narrowly-focused work in only one group or area...

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Glen Zorn [glenzorn@gmail.com]
Sent: 08 June 2013 07:31
To: ietf@ietf.org
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for     ietf@ietf.org]

On 06/08/2013 02:52 AM, Brian E Carpenter wrote:

> Rule 1 for complex and divergent mail threads is to change the
> Subject header when the subject changes. If you don't do that,
> your mail is rather likely to get junked.
>
> I think that IETF last call threads should stay on the main IETF
> discussion list. That is exactly the right place for them.

Since I've requested (read "begged" ;-) for such threads to be moved to
their own list on several occasions, I disagree again.

> It's rather trivial to filter them into a dedicated folder;
> I have one called 'lastcallsin', that also picks up most
> WG Last Call threads, although those have less standardised
> subject headers.

This would appear to work consistently only as long as 'Rule 1' above is
not followed.

>
>     Brian
>
> On 08/06/2013 06:17, Juliao Braga wrote:
>> +1
>>
>> Em 07/06/2013 15:09, Ulrich Herberg escreveu:
>>> I like the idea of a separate list for last calls. It would not solve
>>> the issue of noise for all of us (and not reduce the overall amount of
>>> emails), but it would separate general discussions from IETF LCs. I
>>> have IETF emails filtered by mailing list into different IMAP folders,
>>> and thus a separation could be useful for me.
>>>
>>> Ulrich
>>