From: d@taht.net (Dave Täht)
To: bloat <bloat@lists.bufferbloat.net>
Cc: Steven Bellovin <smb@cs.columbia.edu>
Subject: [Bloat] Re-ECN
Date: Sat, 12 Feb 2011 22:31:03 -0700 [thread overview]
Message-ID: <878vxksdpk.fsf@cruithne.co.teklibre.org> (raw)
JG's blog comments contain a wealth of information as yet unexplored and
quantified. I ran across mention of re-ECN[1], which seems to have some
potential.
In particular, I liked the full backward compatibility with RFC3514[2].
Is the "is it safe to use ECN" research going on exploring what happens
when the last unused bit in the TCP header is also set?
--
Dave Taht
http://nex-6.taht.net
1: http://tools.ietf.org/html/draft-briscoe-tsvwg-re-ecn-tcp-09
2: http://tools.ietf.org/html/rfc3514
next reply other threads:[~2011-02-13 5:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 5:31 Dave Täht [this message]
2011-02-13 10:29 ` Richard Scheffenegger
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=878vxksdpk.fsf@cruithne.co.teklibre.org \
--to=d@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=smb@cs.columbia.edu \
/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