General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Justin McCann <jneilm@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: IPv4 Address Exhaustion Effects on the Earth
Date: Sat, 2 Apr 2011 11:24:54 -0400	[thread overview]
Message-ID: <BANLkTikVeRptuigkKXn1mi7ecX-YVsYQsA@mail.gmail.com> (raw)
In-Reply-To: <5A6D953473350C4B9995546AFE9939EE0C9E2BAE@RWC-EX1.corp.seven.com>

I suppose we missed our chance yesterday (from NANOG)....

---------- Forwarded message ----------
From: George Bonser <gbonser@seven.com>
Date: Fri, Apr 1, 2011 at 11:44 AM
Subject: RE: IPv4 Address Exhaustion Effects on the Earth
To: "Joao C. Mendes Ogawa" <jonny.ogawa@gmail.com>, nanog@nanog.org,
lacnog@lacnic.net

...
Dang,  I was hoping to see an RFC on Bufferbloat in Avian Carriers and
how tail-drop is a messy solution that is to be avoided.

Oh well.

           reply	other threads:[~2011-04-02 15:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5A6D953473350C4B9995546AFE9939EE0C9E2BAE@RWC-EX1.corp.seven.com>]

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=BANLkTikVeRptuigkKXn1mi7ecX-YVsYQsA@mail.gmail.com \
    --to=jneilm@gmail.com \
    --cc=bloat@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