Re: Weekly posting summary for ietf@ietf.org

Ted Lemon <Ted.Lemon@nominum.com> Fri, 07 June 2013 15:52 UTC

Return-Path: <Ted.Lemon@nominum.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 7953321F86D3 for <ietf@ietfa.amsl.com>; Fri, 7 Jun 2013 08:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.752
X-Spam-Level:
X-Spam-Status: No, score=-106.752 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 Vh15iV5YTPd3 for <ietf@ietfa.amsl.com>; Fri, 7 Jun 2013 08:52:23 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 6F0E321F85C9 for <ietf@ietf.org>; Fri, 7 Jun 2013 08:52:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUbIBsImL6eyQacapOli2EHuM4YMhv0nC@postini.com; Fri, 07 Jun 2013 08:52:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AFA3B1B81D6 for <ietf@ietf.org>; Fri, 7 Jun 2013 08:52:15 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A703019005D; Fri, 7 Jun 2013 08:52:15 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 7 Jun 2013 08:52:15 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
Thread-Topic: Weekly posting summary for ietf@ietf.org
Thread-Index: AQHOYzsLp8/g0Ry7ykWpXmTin4ybS5kqYjiAgABmagCAAAKmgIAAEGaAgAABKQA=
Date: Fri, 07 Jun 2013 15:52:14 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751CA801@mbx-01.win.nominum.com>
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>
In-Reply-To: <CABCOCHSkLj0409hyeqKNdomOdrScYypi_7a1xWqMEUV9eTPuCw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751CA801mbx01winnominum_"
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>, "<ietf@ietf.org>" <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: Fri, 07 Jun 2013 15:52:31 -0000

On Jun 7, 2013, at 11:48 AM, Andy Bierman <andy@yumaworks.com<mailto:andy@yumaworks.com>> wrote:
So why not move the signal?
Put IETF Last Call mail on last-call@ietf.org<mailto:last-call@ietf.org> and leave this list for everything else.

The discussion still has to happen somewhere.   I certainly am not restricting my meaningful participation in last calls, but even in that case it is important to be restrained and not get into long fruitless discussions, which, I am afraid, I am wont to do.