From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] IETF 119 - Application Throttling-Related BoF Mtg
Date: Wed, 20 Mar 2024 23:16:22 +0000 [thread overview]
Message-ID: <B46A4365-94AE-464B-812A-345C7D2AEFB3@comcast.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
At IETF 119 in a few minutes – a very interesting BoF with NN implications in US. "Secure Communication of Network Properties" asking the question of how a wireless network might communicate their rate shaping (throttling) policies. https://datatracker.ietf.org/meeting/119/session/sconepro/ Check out all the slides!
I can see the interesting technical part of this, but not sure that the shaping of video traffic in wireless networks will persist after the upcoming FCC order.
Jason
[-- Attachment #2: Type: text/html, Size: 3176 bytes --]
reply other threads:[~2024-03-20 23:16 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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B46A4365-94AE-464B-812A-345C7D2AEFB3@comcast.com \
--to=jason_livingood@comcast.com \
--cc=nnagain@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