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

Ray Pelletier <rpelletier@isoc.org> Sat, 08 June 2013 13:03 UTC

Return-Path: <rpelletier@isoc.org>
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 A8EAF21F9A1F for <ietf@ietfa.amsl.com>; Sat, 8 Jun 2013 06:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level:
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4TGi47TQ1IFF for <ietf@ietfa.amsl.com>; Sat, 8 Jun 2013 06:03:13 -0700 (PDT)
Received: from smtp86.ord1c.emailsrvr.com (smtp86.ord1c.emailsrvr.com [108.166.43.86]) by ietfa.amsl.com (Postfix) with ESMTP id 62D0521F99B4 for <ietf@ietf.org>; Sat, 8 Jun 2013 06:03:13 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 11B92500A8; Sat, 8 Jun 2013 09:03:13 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id C252050096; Sat, 8 Jun 2013 09:03:12 -0400 (EDT)
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.org]
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EA4@EXMB01CMS.surrey.ac.uk>
Date: Sat, 08 Jun 2013 09:03:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9024F1F-65A2-4FDC-8750-772642041A88@isoc.org>
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> <290E20B455C66743BE178C5C84F12408223F494EA4@EXMB01CMS.surrey.ac.uk>
To: l.wood@surrey.ac.uk
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
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 13:03:17 -0000

On Jun 8, 2013, at 6:09 AM, <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk> wrote:

> 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.

The ietf list has 2,155 subscribers, Announce, 3,203 with 915 duplicates, for total unique addresses of 4,442.

Ray


> 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
>>>