From: "Dave Täht" <dave@taht.net>
To: bloat-ietf@lists.bufferbloat.net
Subject: [Bloat-ietf] discontinuing the bloat-ietf mailing list
Date: Sun, 20 Dec 2015 19:41:02 +0000 [thread overview]
Message-ID: <20151220194102.GA1743@mail.taht.net> (raw)
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.
next reply other threads:[~2015-12-20 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 19:41 Dave Täht [this message]
2015-12-23 16:22 ` Perry E. Metzger
2016-01-04 22:55 ` Dave Täht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151220194102.GA1743@mail.taht.net \
--to=dave@taht.net \
--cc=bloat-ietf@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox