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

Melinda Shore <melinda.shore@gmail.com> Fri, 07 June 2013 20:00 UTC

Return-Path: <melinda.shore@gmail.com>
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 16D4E21F996D for <ietf@ietfa.amsl.com>; Fri, 7 Jun 2013 13:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qrzM6RVOtyqV for <ietf@ietfa.amsl.com>; Fri, 7 Jun 2013 13:00:33 -0700 (PDT)
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by ietfa.amsl.com (Postfix) with ESMTP id 50EEA21F9970 for <ietf@ietf.org>; Fri, 7 Jun 2013 13:00:31 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so801507pde.9 for <ietf@ietf.org>; Fri, 07 Jun 2013 13:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zWYpX892g7UIXfw8VeV1Ewlf0ALYWkTVIdX6CeYbQl4=; b=0zZEOLN/fdRr6kDokinoKiRqfgt+CSLCEGLcbv712bBi1W1fYsehjHPN0njWdOKnMx 2C3Igk6vUQr6SUVyZkhxcTN5xc4smb5kQocOb5bSmF2Gft7vZk8JsMRnQHBpjdAqyq1S JARt5hvLFQh2SVlCkJ+bRs1FDNQM0OKJpuOGBaRL8v5MafsLY/j9PgdlqBEMWAFb+Meq pF+4e8W8N5K14kUax8eOSrYk4xKfST+n0PwxrUAxle1psz3c5mpKVJdoS4jHhqcfC62o 8juxTJ89tlhG+nXCx2Z47ZxEtdAxtIg3G4rCABddwErh0xGjxMZqdfMLj3ke04qP3bl/ RHxQ==
X-Received: by 10.66.118.79 with SMTP id kk15mr4276253pab.193.1370635231166; Fri, 07 Jun 2013 13:00:31 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id kv2sm226096pbc.28.2013.06.07.13.00.29 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 13:00:30 -0700 (PDT)
Message-ID: <51B23BDB.2060202@gmail.com>
Date: Fri, 07 Jun 2013 12:00:27 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Best list for IETF last calls [was: Weekly posting summary for ietf@ietf.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>
In-Reply-To: <51B23A06.7060402@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: Fri, 07 Jun 2013 20:00:39 -0000

On 6/7/13 11: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.

I tend to think so, as well.  You never know when someone's
going to stumble over something and make a comment that matters.
The cost is that you get jackasses being loud and petty, but frankly
you'd get that on a last call mailing list, anyway, since IETF
last calls have in a few cases been known to function as jackass
magnets.

It seems to me that the real problem isn't last calls, it's
people not understanding that behaving badly has a cost associated
with it, and that cost is that they're alienating people they'd
(apparently) like to work with and demolishing their chances of
getting an editorship or moving into leadership roles.

Melinda