From: d@taht.net (Dave Täht)
To: richard <richard@pacdat.net>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] How do we shift the market?
Date: Tue, 08 Feb 2011 09:27:00 -0700 [thread overview]
Message-ID: <87zkq6bigb.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <20110206210317.GC3004@thyrsus.com> (Eric Raymond's message of "Sun, 6 Feb 2011 16:03:17 -0500")
Eric Raymond <esr@thyrsus.com> writes:
> richard <richard@pacdat.net>:
>> I see wiki.bufferbloat.net has the "It Works" up on it - a page here on
>> terms would be a good thing.
There *is* no wiki.bufferbloat.net site.
Successful lookups for that are artifact of bufferbloat.net's current
DNS provider, name.com, which not only never serves up a NXDOMAIN
record, but supplies a *random*, *invalid* ipv6 address for it.
d@cruithne:$ host wiki.bufferbloat.net
wiki.bufferbloat.net has address 149.20.54.81
wiki.bufferbloat.net has IPv6 address 1d00:6574:63:6f6d:6c:2e63:2800:0
d@cruithne:$ host a.random.site.bufferbloat.net
a.random.site.bufferbloat.net has address 149.20.54.81
a.random.site.bufferbloat.net has IPv6 address
7262:6c6f:6174:36e:6574:2036:3034:3830
I first noticed this behavior a few weeks ago. Originally it was worse -
it would wildcard all invalid names to an ad-filled site.
The number of things that this behavior breaks is rather large: email
rbls, people that default to ipv6, the fact that I cannot use short
hostnames, and more than once a typo sent me to the wrong machine
entirely.
I've been meaning to take these issues up with name.com once I can do so
calmly, and rationally, with tact, and diplomacy.
For now, please stick with www.bufferbloat.net as your entry point to
the site!
>
> I am *so* there! :-)
>
> I'll start a glossary page.
There's one started. I don't know if redmine can do a media-wiki like
thing and let us mark articles as belonging to a given catagory? So I
setup the glossary page to just {{include(other pages)}} for now.
I would love to see all the terms we are using tightly defined, with
definitions on the wiki... Y'all
In particular I would like to extend "Dark Buffers" to include the
concept of retries - or come up with another term for it.
--
Dave Taht
http://nex-6.taht.net
next prev parent reply other threads:[~2011-02-08 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 16:42 Jim Gettys
2011-02-06 17:21 ` richard
2011-02-06 21:03 ` Eric Raymond
2011-02-08 16:09 ` John W. Linville
2011-02-08 16:41 ` Jim Gettys
2011-02-08 16:27 ` Dave Täht [this message]
2011-02-06 20:58 ` Eric Raymond
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkq6bigb.fsf@cruithne.co.teklibre.org \
--to=d@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=richard@pacdat.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