Re: Draft "Convince your boss" note for IETF participants

Bob Hinden <> Wed, 28 September 2022 15:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 593DDC1522D0 for <>; Wed, 28 Sep 2022 08:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2s0aOxCMrYej for <>; Wed, 28 Sep 2022 08:29:13 -0700 (PDT)
Received: from ( [IPv6:2001:4860:4864:20::29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id AEBC7C1522CC for <>; Wed, 28 Sep 2022 08:29:13 -0700 (PDT)
Received: by with SMTP id 586e51a60fabf-13175b79807so7654012fac.9 for <>; Wed, 28 Sep 2022 08:29:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date; bh=SJIOkycVcxKIErFAgzzfnbKYtmoD7z2atcI+1V6fbbY=; b=HGvY3JO4yqC+OO9HFrnKB/d9FuWn3cYnot/1GBanQrUvXpM9PGXQGQyaA9nB1StEiG y+NdvkiURTvYyePpuqu/Yy+ZYplJkWEQeKoFaOtco1heqoDCMJ1l+7iGOhKHOVCo1xXU qN2n5OEBUxVh0ZDnaOzcTS3nJVz+8iimCdFh9e8aHNjvGTBfvKqhSFx0urQUcQNiKXq5 NhC8XcCVBQqlJfv0w/cj8nnPkCYYjuuzd5XvJTxeGy7RQmlkNdCch3pW3e/akAH8SPxQ 8dxKyZyS+0NMX6oKKnglkZ3Xa393Ik3sFzdKmOhNfwxfgOol5Su0I6TgUPMNBzewUQgQ 0fYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=SJIOkycVcxKIErFAgzzfnbKYtmoD7z2atcI+1V6fbbY=; b=mrngkAtMv5MjRWtoz/L++BASjuWzpQEcTszdyHI9Db+YhrbM86IpSqmKuKqWpdVe3U aSJI/pnqVRrFnmaeRBOH7Thj9MNcQY1JYHxbp2CsIN8kGO1zI5gZEw9qNAOhGeCCzCmP iCNGvcd4KTYyXObQhsw7TtHvtPqPI9xts4/6IPjA/sV4c6bh53U2s0qAXWzv5Z7VCzex tDSJHY1UekQrLxsmH2NAKgfl/+Czrmkp62adIoh/UdWaziQEef75nPLUWWCyC36hkiI4 mvlMb/y/gt9s6+bWV2mLe/9sjTi6mbGjzpKkhXtu4iMxsO6MsZGsMPCaW6KxdKy4AlyD VR+g==
X-Gm-Message-State: ACrzQf1F/+H83rn1LSw03fdnAyR81kYSC/rcW9E3BaigVe292DrW8djx gZka3hJcQPiTwmy1clihKVs=
X-Google-Smtp-Source: AMsMyM5LT6Uelh166zDnSinhpvBuNxFK/1oqd/7QrLuK5+rs49snUCNBIq0HFFdBZKGSNnj5RZzpTA==
X-Received: by 2002:a05:6870:d146:b0:127:76fd:382 with SMTP id f6-20020a056870d14600b0012776fd0382mr5662562oac.257.1664378952028; Wed, 28 Sep 2022 08:29:12 -0700 (PDT)
Received: from ([2600:1700:4383:c05f:5426:c083:bcee:4e0]) by with ESMTPSA id k187-20020aca3dc4000000b003504805a618sm1922866oia.45.2022. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Sep 2022 08:29:10 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_8E1CFB5D-F3FC-41D0-8BCB-7588769A1C47"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.\))
Subject: Re: Draft "Convince your boss" note for IETF participants
From: Bob Hinden <>
In-Reply-To: <>
Date: Wed, 28 Sep 2022 08:29:05 -0700
Cc: Bob Hinden <>, WG Chairs <>
Message-Id: <>
References: <>
To: Greg Wood <>
X-Mailer: Apple Mail (2.3696.
Archived-At: <>
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Sep 2022 15:29:14 -0000


Please don’t call the IETF a conference ("write a post-conference report”).    I know you know that the IETF is a place where one goes to work on new protocol standards and specifications.   We have w.g. meetings, not sessions.

Further, IMHO there isn’t a lot of value to attend an IETF meeting without following the work of a working group by participating on the email list, commenting on a proposal, and submitting new proposals.

I think a better approach would be something like

   I have submitted a new proposal (w/ link to ID) and would like to attend the meeting in
   London to discuss it with others who have provided feedback.  This draft is important to our business
   because it solves the <foo> problem that we see in our business.  Etc., etc.


   There is work going on in <w.g. name> that solves an important problem we see in our business.   I have
   been following this work online and would like to attend the meeting to discuss issues with the w.g. and
   I have some idea on how it could be improved.  It would be more effective if I attend in person.

Hope this is helpful.


> On Sep 28, 2022, at 7:22 AM, Greg Wood <> wrote:
> Hello!
> As an experiment, based on material some other technology conferences provide to (potential) participants, and at the suggestion received from an IETFer, we’ve created a draft “Convince Your Boss” note that might be used by someone seeking approval to attend an IETF meeting in-person:
> Any and all comments about whether this might be useful to you or participants in your groups, or suggestions about how it might be tuned to be more useful, would be most welcome — either on this list or directly to me.
> More broadly, it would be useful to know whether there is any specific information or material that would make it easier for IETF participants to participate in the IETF—not just meetings, but also (for example) devoting time to work in the IETF. Again, I’m happy to receive suggestions directly or on the list.
> Please let me know if I can provide more information or answer any questions.
> Thank you,
> -Greg
> --
> Greg Wood
> +1-703-625-3917