From: Vint Cerf <vint@google.com>
To: nnagain@lists.bufferbloat.net
Subject: [NNagain] a new latency report
Date: Sun, 3 Dec 2023 20:40:19 -0500 [thread overview]
Message-ID: <CAHxHggdpz17uu9FvHSqY4mRooDOQybWh_GtEgzhnCtBt2bQ=Ag@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 300 bytes --]
sharing with permission - open to public
vint
https://drive.google.com/file/d/1q0-bh5Q7nCHZOhIQlMG8Jgxdwv4giDPq/view?usp=sharing
--
Please send any postal/overnight deliveries to:
Vint Cerf
Google, LLC
1900 Reston Metro Plaza, 16th Floor
Reston, VA 20190
+1 (571) 213 1346
until further notice
[-- Attachment #1.2: Type: text/html, Size: 829 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3995 bytes --]
next reply other threads:[~2023-12-04 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 1:40 Vint Cerf [this message]
2023-12-04 12:02 ` Frantisek Borsik
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='CAHxHggdpz17uu9FvHSqY4mRooDOQybWh_GtEgzhnCtBt2bQ=Ag@mail.gmail.com' \
--to=vint@google.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