From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] ipv6 timestamp header?
Date: Thu, 16 Mar 2017 18:07:25 -0700 [thread overview]
Message-ID: <CAA93jw6_iLUzcLVExyqsixh3jTU+W9wOfxchOjvuOvexOga9uQ@mail.gmail.com> (raw)
I am curious if code for linux ever appeared that could generate an
ipv6 header specific for a timestamp? I realize full well that most
stacks would just drop additional undefined ipv6 headers - and that
inserting it into the path is a pita - but at least fiddling with the
idea for certain kinds of traffic (host to host on a single link) is
appealing at the moment.
Many proposals for such have appeared in the past, here's one:
https://www.ietf.org/proceedings/87/slides/slides-87-6man-4.pdf
And another:
http://www.dcs.gla.ac.uk/~dp/pubs/Pezaros-NOMS04-CRC.pdf
With this... and a well established grammar for parsing packets...
perhaps I can also get a pony?
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2017-03-17 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 1:07 Dave Taht [this message]
2017-03-17 13:59 ` Dave Taht
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=CAA93jw6_iLUzcLVExyqsixh3jTU+W9wOfxchOjvuOvexOga9uQ@mail.gmail.com \
--to=dave.taht@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