* [Bloat-ietf] discontinuing the bloat-ietf mailing list
@ 2015-12-20 19:41 Dave Täht
2015-12-23 16:22 ` Perry E. Metzger
0 siblings, 1 reply; 3+ messages in thread
From: Dave Täht @ 2015-12-20 19:41 UTC (permalink / raw)
To: bloat-ietf
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bloat-ietf] discontinuing the bloat-ietf mailing list
2015-12-20 19:41 [Bloat-ietf] discontinuing the bloat-ietf mailing list Dave Täht
@ 2015-12-23 16:22 ` Perry E. Metzger
2016-01-04 22:55 ` Dave Täht
0 siblings, 1 reply; 3+ messages in thread
From: Perry E. Metzger @ 2015-12-23 16:22 UTC (permalink / raw)
To: Dave Täht; +Cc: bloat-ietf
Is the work still needed, though?
Perry
On Sun, 20 Dec 2015 19:41:02 +0000 Dave Täht <dave@taht.net> 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
--
Perry E. Metzger perry@piermont.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bloat-ietf] discontinuing the bloat-ietf mailing list
2015-12-23 16:22 ` Perry E. Metzger
@ 2016-01-04 22:55 ` Dave Täht
0 siblings, 0 replies; 3+ messages in thread
From: Dave Täht @ 2016-01-04 22:55 UTC (permalink / raw)
To: Perry E. Metzger; +Cc: bloat-ietf
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 <dave@taht.net> 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
>
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-01-04 22:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-20 19:41 [Bloat-ietf] discontinuing the bloat-ietf mailing list Dave Täht
2015-12-23 16:22 ` Perry E. Metzger
2016-01-04 22:55 ` Dave Täht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox