From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Bloat] Fwd: Comcast Network Peer Survey on DSCP/ECN for L4S
Date: Fri, 10 Jun 2022 11:13:27 -0700 [thread overview]
Message-ID: <CAA93jw5GhopRYmw0vB5d+9JbczqDAkhpSWzrBg9uv4CMAq0E2g@mail.gmail.com> (raw)
In-Reply-To: <EEFB0C12-8FFA-4991-B9B9-480B5AD179CC@cable.comcast.com>
---------- Forwarded message ---------
From: Livingood, Jason via NANOG <nanog@nanog.org>
Date: Fri, Jun 10, 2022 at 9:02 AM
Subject: Comcast Network Peer Survey on DSCP/ECN for L4S
To: nanog@nanog.org <nanog@nanog.org>
Hi – Comcast is working on the implementation of ultra-low latency
networking, leveraging the IETF’s upcoming L4S standard. This standard
will require passing ECN and DSCP markings across network boundaries.
As a result, we are interested in your perspective on this and in how
you handle markings today. We have a short survey that should only
take a few minutes to complete. Take the survey at
https://forms.office.com/r/vGb0LUXfS1
While any network operator is welcome to take this, we are
particularly interested in any networks that are directly
interconnected with us today.
Thank you!
Jason Livingood
Comcast – Technology Policy & Standards
jason_livingood@comcast.com
PS – Apologies if any of you get a duplicate of this request via other channels.
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-06-10 18:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <EEFB0C12-8FFA-4991-B9B9-480B5AD179CC@cable.comcast.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=CAA93jw5GhopRYmw0vB5d+9JbczqDAkhpSWzrBg9uv4CMAq0E2g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.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