From: Pete Heist <pete@heistp.net>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] SCE deployment for experiments and internal use
Date: Fri, 19 Mar 2021 13:33:38 +0100 [thread overview]
Message-ID: <a549986121362f858c27d16c38d6efa81deba62f.camel@heistp.net> (raw)
It's been discussed a couple times that it's possible to deploy SCE
transports and middleboxes without IETF approval, providing that they
adhere to the guidelines in the draft. Namely, DSCP must be used, and
no SCE marking is allowed for traffic that may end up on the open
Internet. That is pretty limiting, and restricts usage to local
experiments or traffic within participating ASs, but perhaps it would
still be useful to gather some experimental data.
This can already be done today by just building the SCE kernel with the
right options enabled (https://github.com/chromi/sce), but does anyone
think there's a benefit to making it easier by making packages for some
platform? I'm not sure yet who would have the time to prepare these
packages, I'm just floating the idea first. It may be more attractive
to spend the time on if there were an experiment planned, or a platform
or location where it's likely to get used...
Pete
reply other threads:[~2021-03-19 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a549986121362f858c27d16c38d6efa81deba62f.camel@heistp.net \
--to=pete@heistp.net \
--cc=ecn-sane@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