From: "Livingood, Jason" <jason_livingood@comcast.com>
To: Sebastian Moeller <moeller0@gmx.de>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Fwd: "Very interesting L4S presentation from Nokia Bell Labs on tap for RIPE 88 in Krakow this week! "
Date: Wed, 22 May 2024 12:48:27 +0000 [thread overview]
Message-ID: <421E9E11-618B-4D6E-A905-D7C5F9457A3D@comcast.com> (raw)
In-Reply-To: <0F222476-EB44-45E9-93C5-2E595AE08C09@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
> in the IETF the gap between the 'no politics' motto
There have always been politics at the IETF and in every other SDO, open source project, etc. – it is human nature IMO.
> And the fact that WG members see no harm in having private only strategy discussions with chairs and ADs.
In my personal experience at the IETF, when you are lead author or editor of a working group document it is routine to strategize with WG chairs and even ADs on how to keep the document moving forward, how to resolve conflict and achieve consensus, and how to be well-prepared for meetings. That IMO is a sign of WG chairs and ADs doing their job of developing standards on a timely basis.
JL
[-- Attachment #2: Type: text/html, Size: 2849 bytes --]
next prev parent reply other threads:[~2024-05-22 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 15:31 [Bloat] " Frantisek Borsik
2024-05-21 16:18 ` Jonathan Morton
2024-05-21 17:13 ` Livingood, Jason
2024-05-21 17:32 ` Sebastian Moeller
2024-05-22 5:40 ` [Bloat] Fwd: " Sebastian Moeller
2024-05-22 8:47 ` Frantisek Borsik
2024-05-22 12:48 ` Livingood, Jason [this message]
2024-05-22 13:10 ` [Bloat] " Sebastian Moeller
2024-05-22 9:37 ` Jonathan Morton
2024-05-22 12:30 ` [Bloat] [EXTERNAL] " Livingood, Jason
2024-05-22 12:27 ` Livingood, Jason
2024-05-22 12:54 ` [Bloat] [EXTERNAL] " Sebastian Moeller
2024-05-22 17:37 ` Sebastian Moeller
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=421E9E11-618B-4D6E-A905-D7C5F9457A3D@comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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