[recipe] FYI: draft-eckert-ietf-and-energy-overview

Toerless Eckert <tte@cs.fau.de> Mon, 11 July 2022 18:22 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: recipe@ietfa.amsl.com
Delivered-To: recipe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4589FC06B988; Mon, 11 Jul 2022 11:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, 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=no autolearn_force=no
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 gOe_AZE6nbY2; Mon, 11 Jul 2022 11:22:05 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (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 83993C06B98E; Mon, 11 Jul 2022 11:22:03 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 84EB7549FAD; Mon, 11 Jul 2022 20:21:56 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7BE7D4EB428; Mon, 11 Jul 2022 20:21:56 +0200 (CEST)
Date: Mon, 11 Jul 2022 20:21:56 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: architecture-discuss@ietf.org, recipe@ietf.org
Cc: draft-eckert-ietf-and-energy@ietf.org
Message-ID: <YsxqRMY8bg2E7cbt@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/recipe/eLIsZagj5GZvIV9qcFn7WdpWJzc>
Subject: [recipe] FYI: draft-eckert-ietf-and-energy-overview
X-BeenThere: recipe@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RECIPE \(Reducing Energy Consumption with Internet Protocols Exploration\)" <recipe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/recipe>, <mailto:recipe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/recipe/>
List-Post: <mailto:recipe@ietf.org>
List-Help: <mailto:recipe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recipe>, <mailto:recipe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2022 18:22:07 -0000

I've seen over the last year some random interest in various IETF groups
in looking at the impact of what the IETF does on Energy consumption, and
i wasn't myself clear about that.  So we tried to figure out a bit what
we  _think_ the impact is, and ended putting together some initial document attempting to
summarize the various categories we could think of.

Most of the impact is probably something we might call incidental, aka: digitization through
IP, converged networks, Internet and the like, but of course there is also our IoT (low energy networking)
work and EMAN etc. pp. So even trying to find useful categorization/taxonomy is difficult.

  https://datatracker.ietf.org/doc/draft-eckert-ietf-and-energy-overview/

I would d love to get feedback / thoughts on this work, also looking for
collaborators, if you're interested.

The work is hosted here on github: https://github.com/toerless/energy

2 summary slides here:

   https://github.com/toerless/energy/raw/main/what-has-the-ietf-ever-done-for-energy.pdf

Will be happy to take feedback also simply via github issues, even if just
feedback like "i hated this doc / i liked this doc" if you should read it.

Not quite sure where to best discuss work like this on IETF mailing lists,
but i found an old mailing list 10 year in hiatus: recipe@ietf.org,

 recipe -- RECIPE (Reducing Energy Consumption with Internet Protocols Exploration)

So maybe that's a more dedicated good place to start instead of architecture-discuss
(which often has not been too welcoming of non-IAB promoted/lead work discussions, ...)

Cheers
    Toerless