From: Vint Cerf <vint@google.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net, ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] hpcc++
Date: Mon, 9 May 2022 12:25:39 -0400 [thread overview]
Message-ID: <CAHxHggc+AcdOPNBfWgMMBmtEzCFTqqd3-kx90uTEJy=0sc94Xg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7tRiKUFfXq0NTsBAaLTtAWq_BAWVb20jCxwvMS8PKUgA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]
would these methods also allow for a fixed latency (ie avoiding giving
precedence to parties closer - kind of like trying to prevent high
frequency stock trading by front running)?
v
On Mon, May 9, 2022 at 11:40 AM Dave Taht <dave.taht@gmail.com> wrote:
> I like the degree to which "sojourn time" has been socialized.
>
> https://datatracker.ietf.org/doc/draft-miao-rtgwg-hpccplus/
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Ecn-sane mailing list
> Ecn-sane@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/ecn-sane
>
--
Please send any postal/overnight deliveries to:
Vint Cerf
1435 Woodhurst Blvd
McLean, VA 22102
703-448-0965
until further notice
[-- Attachment #1.2: Type: text/html, Size: 1726 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3995 bytes --]
prev parent reply other threads:[~2022-05-09 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 15:40 Dave Taht
2022-05-09 16:25 ` Vint Cerf [this message]
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='CAHxHggc+AcdOPNBfWgMMBmtEzCFTqqd3-kx90uTEJy=0sc94Xg@mail.gmail.com' \
--to=vint@google.com \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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