From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00::f03c:91ff:feae:7028]) by lists.bufferbloat.net (Postfix) with ESMTPS id B072A3ECF5 for ; Sun, 20 Dec 2015 14:41:03 -0500 (EST) Received: by mail.taht.net (Postfix, from userid 1003) id 5D0F9228A0; Sun, 20 Dec 2015 19:41:02 +0000 (UTC) Date: Sun, 20 Dec 2015 19:41:02 +0000 From: Dave =?iso-8859-1?Q?T=E4ht?= To: bloat-ietf@lists.bufferbloat.net Message-ID: <20151220194102.GA1743@mail.taht.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Subject: [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: Sun, 20 Dec 2015 19:41:03 -0000 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.