Re: [admin-discuss] Next steps towards a net zero IETF

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 21 March 2023 21:02 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCAC1C14CE46; Tue, 21 Mar 2023 14:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b="Kz+8r9k3"; dkim=pass (1024-bit key) header.d=yitter.info header.b="fSIht7lf"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1nou2r_NMkdp; Tue, 21 Mar 2023 14:02:07 -0700 (PDT)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2752FC14CF1E; Tue, 21 Mar 2023 14:02:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id D7EA0BD534; Tue, 21 Mar 2023 21:02:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1679432520; bh=Azid+fFIWo7l29bvMDxYwUxuf5e2ZSb3zXdwioMHfx0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Kz+8r9k3kyoGG68LvuBTmf8eB2v7qwiBeVc+QOE4QNpSHYwlBPZ3LYcSjK6++qGd2 XRws9J4Df1036LNbT91BFVPgnDQp59gr9+iWd36bueta8P+k5s07J2ekNlUto2BnM9 DY9KfuEI1QYPjG+3abchLZ7lZY0DZHr2PKJLNUGk=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lmpE3XfsGQVO; Tue, 21 Mar 2023 21:01:59 +0000 (UTC)
Date: Tue, 21 Mar 2023 17:01:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1679432519; bh=Azid+fFIWo7l29bvMDxYwUxuf5e2ZSb3zXdwioMHfx0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fSIht7lf3dzdIJ9mTaaacZSPPejvBjWosppxRshUPgWqpzDz+MgX8tvWboNc0GoVH 5CX05h3x8VSmJy/H9aoKv8S4PKLi76OhGIusbyIpW6MmPD1sJjicfoioC1GtV72i82 2ukW5oCORfnJ5sphvB7CcUaLyyHwzIVUC05D3DlA=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: admin-discuss@ietf.org
Cc: ietf@ietf.org
Subject: Re: [admin-discuss] Next steps towards a net zero IETF
Message-ID: <20230321210158.6uelg47rosiswjxq@crankycanuck.ca>
Mail-Followup-To: admin-discuss@ietf.org, ietf@ietf.org
References: <B8DF18B2-77A2-4A6B-962A-DEFBB1EDFF5A@staff.ietf.org> <20230321172025.18971B41BD75@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20230321172025.18971B41BD75@ary.qy>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/32IC65rwOQqc7AODGO0lymJGllE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2023 21:02:11 -0000

Dear colleagues,

I work for the Internet Society but this is only my opinion.

On Tue, Mar 21, 2023 at 01:20:24PM -0400, John Levine wrote:

>also reiterate the point that carbon offsets are for suckers.
[…]
>forestry school about how you design forest carbon offsets and it
>became clear that you have to make some extremely optimistic
>assumptions. You have to believe that whoever has sold you the offset
>will be able and willing to prevent logging in some remote forest for
>fifty years, and also that they won't turn around resell the same
>offset to someone else next year and the year after that. They talked
>about how one might audit these things, but it wasn't very persuasive.

There is little question that many—perhaps all—offset programs are at least deficient in the actual carbon they will capture over the course of the program.
That does not, however, mean that they are necessarily an empty or worthless effort.  There are several ways in which they can be beneficial _even if_ they do not generate all the promised benefits.

To begin with, of course, actually building in some cost from carbon emissions requires two things: (1) an analysis of how much carbon an activity creates and (2) a commitment to spending that additional money.  It is not hard to see that at least some activities could increase carbon emissions in an expensive way just in case a carbon offset is in place, while yet providing only marginal benefit.  In that case, the activity will decline, which will inevitably reduce carbon outputs.  At its heart, this is the _real_ point of trying to put a price on carbon, and buying carbon offsets is necessarily a part of that story.

Second, while the auditing infrastructure for carbon offsets is currently weak (perhaps to the point of absurdity), there is little reason to suppose that the auditing industry will not get better at auditing this area of corporate expenditure as interest grows.  And, as failures to respond to audits indicating inadequate controls grow, liability for the consequences of increased carbon will conceivably rise too.  That creates a new pressure for action on carbon outputs.

Finally, if an organization is serious about these matters, every carbon offset purchase is a sign of continued carbon outputs.  Thus, the community (by way of budget and audit documents) automatically gets a way of knowing whether the organization is in fact reducing its carbon outputs (by, say, reducing travel or buying less-carbon-intensive energy) or whether it is not so reducing.  The carbon budget of the IETF is, right now, pretty obscure.  If you're going to have disputes with people about how much you owe for a given resource, that will allow others to see the extent to which you have accurately measured your resource consumption.

None of this, of course, suggests that carbon offsets will make the carbon go away.  But they might provide information about the way the organization prioritizes carbon intensity, and thereby allow the organization to change direction.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com