From: Vint Cerf <vint@google.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Dave Taht <dave.taht@gmail.com>,
starlink@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] Fwd: IPv6 "bloat" history
Date: Mon, 28 Mar 2022 13:28:22 -0400 [thread overview]
Message-ID: <CAHxHggf3L4vq4qo00b8Kacw3U_27_hDftaXYzXOFcccyn82xCQ@mail.gmail.com> (raw)
In-Reply-To: <877d8e2e6i.wl-jch@irif.fr>
[-- Attachment #1.1: Type: text/plain, Size: 369 bytes --]
https://datatracker.ietf.org/wg/poised/about/
https://www.rfc-editor.org/rfc/rfc1396.html
v
On Mon, Mar 28, 2022 at 1:13 PM Juliusz Chroboczek <jch@irif.fr> wrote:
> > POISED was the result.
>
> Could somebody please explain?
>
--
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: 1058 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3995 bytes --]
prev parent reply other threads:[~2022-03-28 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cfd8ee83-fe8b-003b-cb91-a0ddcb59affd@mtcc.com>
[not found] ` <b63ec299-9ed6-7f16-e0c8-18a0ec4e5327@necom830.hpcl.titech.ac.jp>
[not found] ` <1A3B85A2-7978-4590-92A6-5B3077A3938C@delong.com>
[not found] ` <72d82d3f-f05e-de88-5f09-d6b3afe8478c@necom830.hpcl.titech.ac.jp>
[not found] ` <367728dd-02e8-cff1-ea9d-8f59e987fbe0@gmail.com>
2022-03-22 18:13 ` Dave Taht
2022-03-22 18:33 ` Vint Cerf
2022-03-28 17:13 ` Juliusz Chroboczek
2022-03-28 17:28 ` 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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHxHggf3L4vq4qo00b8Kacw3U_27_hDftaXYzXOFcccyn82xCQ@mail.gmail.com \
--to=vint@google.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=jch@irif.fr \
--cc=starlink@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