From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [176.58.107.8]) by lists.bufferbloat.net (Postfix) with ESMTPS id C85793B2AB for ; Mon, 4 Jan 2016 17:53:15 -0500 (EST) Received: from dair-871.lorna-side.hm.taht.net (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) by mail.taht.net (Postfix) with ESMTPSA id D256A21E57; Mon, 4 Jan 2016 22:53:12 +0000 (UTC) To: "Perry E. Metzger" References: <20151220194102.GA1743@mail.taht.net> <20151223112237.25d172e7@jabberwock.cb.piermont.com> Cc: bloat-ietf@lists.bufferbloat.net From: =?UTF-8?Q?Dave_T=c3=a4ht?= Message-ID: <568AF878.60309@taht.net> Date: Mon, 4 Jan 2016 14:55:52 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20151223112237.25d172e7@jabberwock.cb.piermont.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Bloat-ietf] discontinuing the bloat-ietf mailing list X-BeenThere: bloat-ietf@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: IETF specific bufferbloat discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2016 22:53:15 -0000 On 12/23/15 8:22 AM, Perry E. Metzger wrote: > Is the work still needed, though? Darned if I know, don't want to run a list for it anymore. Killing this list later on in the week. > Perry > > On Sun, 20 Dec 2015 19:41:02 +0000 Dave Täht wrote: >> >> This email list, despite getting 39 people to sign up for it, has >> *never* had any traffic, and I would like to discontinue it, as one >> more mailbox I don't have to sort spam out of. >> >> Any objections? Otherwise I will kill it as of the first of the >> year. >> >> Ostensibly it was started for this reason, and if there is a place >> to do that work, great: >> >> The IETF is fundamentally a producer of words as embodied in >> specifications. >> >> This is a mailing list to discuss needed changes in IETF >> specifications as a result of bufferbloat work. A first obvious >> candidate RFC /BCP needing update is RFC 3819. >> >> _______________________________________________ >> Bloat-ietf mailing list >> Bloat-ietf@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/bloat-ietf > > >