Re: [admin-discuss] Next steps towards a net zero IETF
Richard Shockey <richard@shockey.us> Tue, 21 March 2023 22:26 UTC
Return-Path: <richard@shockey.us>
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 1F59AC151700 for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2023 15:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 (768-bit key) header.d=shockey.us
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 MHcJyvQizR3n for <ietf@ietfa.amsl.com>; Tue, 21 Mar 2023 15:26:23 -0700 (PDT)
Received: from outbound-ss-820.bluehost.com (outbound-ss-820.bluehost.com [69.89.24.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8171C1516E9 for <ietf@ietf.org>; Tue, 21 Mar 2023 15:26:23 -0700 (PDT)
Received: from cmgw12.mail.unifiedlayer.com (unknown [10.0.90.127]) by progateway2.mail.pro1.eigbox.com (Postfix) with ESMTP id 7703810048533 for <ietf@ietf.org>; Tue, 21 Mar 2023 22:26:23 +0000 (UTC)
Received: from box5527.bluehost.com ([162.241.218.19]) by cmsmtp with ESMTP id ekQxpXdZfZEg8ekQxphDm0; Tue, 21 Mar 2023 22:26:23 +0000
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.4 cv=R+zGpfdX c=1 sm=1 tr=0 ts=641a2f0f a=KXpOjjFwo8kCkgxs2x2AJQ==:117 a=KXpOjjFwo8kCkgxs2x2AJQ==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=-kFOsPF1Im4zmhyN:21 a=IkcTkHD0fZMA:10:nop_charset_1 a=MKtGQD3n3ToA:10:nop_fastflux_from_domain_1 a=1oJP67jkp3AA:10:nop_fastflux_mid_domain_1 a=k__wU0fu6RkA:10:nop_rcvd_month_year a=qMgonR0qfJAA:10:endurance_base64_authed_username_1 a=jqBRFv0mrdUA:10:from_fastflux_domain1 a=XuENCJiIAAAA:8 a=DyqFNPAwAAAA:8 a=48vgC7mUAAAA:8 a=Pf6QpW2kAAAA:8 a=gaFvYFmYQcxJKJqpousA:9 a=QEXdDO2ut3YA:10:nop_charset_2 a=Je86qq7sbXYMP0AVEajm:22 a=B4mLgs--WQ84evSG-RZG:22 a=w1C3t2QeGrPiZgrLijVG:22 a=aScfhB3owP0e7kdt9tb6:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To: References:Message-ID:CC:To:From:Subject:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=CjC0RkUz++ZeHw2G2S1/o9FkNT7in2uuH+EXeB8pANE=; b=eUsfJLVqgh+HuoK6dBQ4P8U/t5 q0IRau3e2RsRLnwvSJ7NtHcKC8MqiGOf0Qi0Mu++xZ0w+at2hGlEgtCwF2k7a6E9nMwzB+5Iq2IwD XhpvxzK8RBhKP1y0Ql3WReqi1;
Received: from pool-100-36-48-45.washdc.fios.verizon.net ([100.36.48.45]:56176 helo=[192.168.1.214]) by box5527.bluehost.com with esmtpa (Exim 4.95) (envelope-from <richard@shockey.us>) id 1pekQw-003VTr-S4; Tue, 21 Mar 2023 16:26:23 -0600
User-Agent: Microsoft-MacOutlook/16.71.23031200
Date: Tue, 21 Mar 2023 18:26:13 -0400
Subject: Re: [admin-discuss] Next steps towards a net zero IETF
From: Richard Shockey <richard@shockey.us>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, admin-discuss@ietf.org
CC: ietf@ietf.org
Message-ID: <8EB0C5E4-A95B-40F7-9ED6-AC060A2892A3@shockey.us>
Thread-Topic: [admin-discuss] Next steps towards a net zero IETF
References: <B8DF18B2-77A2-4A6B-962A-DEFBB1EDFF5A@staff.ietf.org> <20230321172025.18971B41BD75@ary.qy> <20230321210158.6uelg47rosiswjxq@crankycanuck.ca>
In-Reply-To: <20230321210158.6uelg47rosiswjxq@crankycanuck.ca>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box5527.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-BWhitelist: no
X-Source-IP: 100.36.48.45
X-Source-L: No
X-Exim-ID: 1pekQw-003VTr-S4
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-36-48-45.washdc.fios.verizon.net ([192.168.1.214]) [100.36.48.45]:56176
X-Source-Auth: richard@shockey.us
X-Email-Count: 8
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NTUyNy5ibHVlaG9zdC5jb20=
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mXV0eavZXIWyRwbalLPhPMOyhyI>
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 22:26:28 -0000
Andrew you are the Chair of ISOC. We all know this. I completely oppose any use of ISOC/PIR.org funds to use for this bovine effuent. We need to support, as we do, young engineers to attend IETF meetings and learn how the process works ..or doesn’t work. We need proper out reach to national regulatory authorities on what we are doing and why. I know there are issues with ISOC's 501 c3 non profit status. https://www.irs.gov/charities-non-profits/charitable-organizations/exemption-requirements-501c3-organizations You want to throw money into the sewer ..fine. But don’t expect some of us to support it. BTW you know I live in Reston. I'm happy to do a face to face if you are interested. On 3/21/23, 5:01 PM, "ietf on behalf of Andrew Sullivan" <ietf-bounces@ietf.org <mailto:ietf-bounces@ietf.org> on behalf of ajs@anvilwalrusden.com <mailto:ajs@anvilwalrusden.com>> wrote: 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 <mailto:ajs@anvilwalrusden.com>
- Re: [admin-discuss] Next steps towards a net zero… John Levine
- Next steps towards a net zero IETF Greg Wood
- Re: Next steps towards a net zero IETF Christian Huitema
- Re: Next steps towards a net zero IETF Greg Wood
- Re: Next steps towards a net zero IETF Wes Hardaker
- Re: [admin-discuss] Next steps towards a net zero… John Levine
- Re: [admin-discuss] Next steps towards a net zero… John C Klensin
- Re: [admin-discuss] Next steps towards a net zero… Richard Shockey
- Re: [admin-discuss] Next steps towards a net zero… Hesham ElBakoury
- Re: Next steps towards a net zero IETF Eliot Lear
- Re: [admin-discuss] Next steps towards a net zero… Andrew Sullivan
- Re: Next steps towards a net zero IETF George Michaelson
- Re: Next steps towards a net zero IETF Brian E Carpenter
- Re: Next steps towards a net zero IETF Ross Finlayson
- Re: Next steps towards a net zero IETF Alexander Pelov
- Re: [admin-discuss] Next steps towards a net zero… Richard Shockey
- Re: [admin-discuss] Next steps towards a net zero… Bob Hinden
- Re: Next steps towards a net zero IETF Charlie Perkins
- Re: [admin-discuss] Next steps towards a net zero… Richard Shockey
- Re: Next steps towards a net zero IETF Christian Huitema
- Re: Next steps towards a net zero IETF Raghu Saxena
- Re: Next steps towards a net zero IETF Christian Huitema
- Re: Next steps towards a net zero IETF Brian E Carpenter
- Re: Next steps towards a net zero IETF Daniel Migault
- Re: Next steps towards a net zero IETF Masataka Ohta
- Re: Next steps towards a net zero IETF Daniel Migault
- Re: [admin-discuss] Next steps towards a net zero… Masataka Ohta
- What are our next steps? Re: Next steps towards a… Eliot Lear
- Re: [admin-discuss] Next steps towards a net zero… Julian Reschke
- Re: [admin-discuss] Next steps towards a net zero… Alexander Pelov
- Re: [admin-discuss] Next steps towards a net zero… Masataka Ohta
- Re: [admin-discuss] Next steps towards a net zero… Phillip Hallam-Baker
- RE: [admin-discuss] Next steps towards a net zero… Michael McBride
- Re: [admin-discuss] Next steps towards a net zero… Phillip Hallam-Baker
- Re: Next steps towards a net zero IETF willi uebelherr
- Re: Next steps towards a net zero IETF Andrew McConachie
- Re: Next steps towards a net zero IETF Julian Reschke
- Re: Next steps towards a net zero IETF Christian Huitema
- Re: Next steps towards a net zero IETF Fred Baker
- Re: Next steps towards a net zero IETF touch@strayalpha.com
- Re: Next steps towards a net zero IETF Julian Reschke
- Re: Next steps towards a net zero IETF Abdussalam Baryun
- Re: Next steps towards a net zero IETF Richard Shockey
- Re: Next steps towards a net zero IETF Michael Richardson
- Re: Next steps towards a net zero IETF Andrew McConachie
- Re: Next steps towards a net zero IETF Alexander Pelov
- Re: Next steps towards a net zero IETF Hesham ElBakoury
- Re: Next steps towards a net zero IETF Christian Huitema
- Re: Next steps towards a net zero IETF Hesham ElBakoury
- Re: Next steps towards a net zero IETF John Levine
- Re: Next steps towards a net zero IETF Kathleen Moriarty
- Re: [admin-discuss] Next steps towards a net zero… John C Klensin
- Re: Next steps towards a net zero IETF John C Klensin
- Re: [admin-discuss] Next steps towards a net zero… Daniel Migault
- Re: [admin-discuss] Next steps towards a net zero… Brian E Carpenter
- Re: [admin-discuss] Next steps towards a net zero… Michael Richardson
- Re: [admin-discuss] Next steps towards a net zero… Lars Eggert
- Re: Next steps towards a net zero IETF Laurence Lundblade
- Re: [admin-discuss] Next steps towards a net zero… John C Klensin
- Re: [admin-discuss] Next steps towards a net zero… Brian E Carpenter
- Re: [admin-discuss] Next steps towards a net zero… Abdussalam Baryun
- Re: [admin-discuss] Next steps towards a net zero… Mezgani Ali
- Re: [admin-discuss] Next steps towards a net zero… Bob Hinden
- Re: [admin-discuss] Next steps towards a net zero… Toerless Eckert
- Re: [admin-discuss] Next steps towards a net zero… Brian E Carpenter
- Re: [admin-discuss] Next steps towards a net zero… Lars Eggert
- Re: [admin-discuss] Next steps towards a net zero… Lars Eggert
- Re: [admin-discuss] Next steps towards a net zero… Eliot Lear
- Re: [admin-discuss] Next steps towards a net zero… John C Klensin
- Re: [admin-discuss] Next steps towards a net zero… Abdussalam Baryun