[E-impact] routing around high-power links (was Re: [OPSAWG] side meeting #119: Power Metrics: concrete usage example)

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 28 March 2024 00:35 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: e-impact@ietfa.amsl.com
Delivered-To: e-impact@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6ABC15152D for <e-impact@ietfa.amsl.com>; Wed, 27 Mar 2024 17:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (2048-bit key) header.d=sandelman.ca
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 yJsIs13AEeFd for <e-impact@ietfa.amsl.com>; Wed, 27 Mar 2024 17:35:07 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62B42C15171B for <e-impact@ietf.org>; Wed, 27 Mar 2024 17:35:07 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [111.65.57.89]) by relay.sandelman.ca (Postfix) with ESMTPS id 5C09B1F448 for <e-impact@ietf.org>; Thu, 28 Mar 2024 00:35:04 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="PI4lHuaH"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id A0138A191D; Thu, 28 Mar 2024 11:34:58 +1100 (AEDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711586098; bh=nlH0Ap8oazcyxNLroCcNYpoRK0x/q0umFmAuBDXkeaE=; h=From:To:Subject:In-reply-to:References:Date:From; b=PI4lHuaHaWsniycaN3fdzp6HvglrJTTink4Y+fiKjIrvkmANYEKYTCCqVcY8eFhIk 8aemVXTY4uQ34ZXOJm7x9Ty5LDoq5s7vD47GZ2UXNquwT0LItvzMyqwoDTlV0oOHYJ R0bsq42oNp3Q7fuoXDt2fYQNbkW8webey4BLU43MJPpajC8kMXFbCl5ua4GOwuHppR ARr8QARMOxHuZyltKMz8YLQaCvzbmFBaT/y8eBF7YlqYm1/ZypxsZEhhoLtNM8K7vu Im4azm+/noQ0dlmzMy8q+XKYL1RwUyMwQhXMLsVSofgf0w3+yT7hCx0ZRQSDeaFIXZ h+j3BotgTEYUg==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 9D621A190E for <e-impact@ietf.org>; Thu, 28 Mar 2024 11:34:58 +1100 (AEDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: E-Impact IETF <e-impact@ietf.org>
In-reply-to: <142C9E5A-16AB-46AF-92B4-61EA5B3A4942@ifi.uio.no>
References: <CAKr6gn3Ze0FrskGYouRjP+yRTG7Ts60EPy-LveHOXVRFBXNPew@mail.gmail.com> <6E972713-CA73-4D61-AF02-B83E59CCF8AD@id3as.co.uk> <9d3f52c06a274680a0762d65baa1308b@huawei.com> <3BB20F26-CC7B-4467-8C89-3622A08347B6@id3as.co.uk> <f279b87f5a394657a5285e8f914baf0b@huawei.com> <A26397BE-A568-4A40-8897-611BC18B91E7@id3as.co.uk> <CC2DF697-19ED-4FE5-9A22-EB16630E373C@ifi.uio.no> <LV8PR11MB8536590F9C9EB518A9F62A89B5352@LV8PR11MB8536.namprd11.prod.outlook.com> <142C9E5A-16AB-46AF-92B4-61EA5B3A4942@ifi.uio.no>
Comments: In-reply-to Michael Welzl <michawe@ifi.uio.no> message dated "Wed, 27 Mar 2024 12:24:08 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 28 Mar 2024 11:34:58 +1100
Message-ID: <538769.1711586098@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/e-impact/6Id-pv6SEzK1GnJcg4x6VdEVFx4>
Subject: [E-impact] routing around high-power links (was Re: [OPSAWG] side meeting #119: Power Metrics: concrete usage example)
X-BeenThere: e-impact@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Environmental impacts of the Internet <e-impact.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/e-impact>, <mailto:e-impact-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/e-impact/>
List-Post: <mailto:e-impact@ietf.org>
List-Help: <mailto:e-impact-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/e-impact>, <mailto:e-impact-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2024 00:35:11 -0000

One of the things that people have tried to do since ATM was new and fancy
was to provide for more bandwidth by taking the not-shortest path.  That is,
go around the circle rather than across it.   That has mutated into MPLS and
SRv6 efforts.  And SDN. I never was clear if anyone actually was able to do
this.

For latency-tolerant bulk traffic (think backups, but also recorded video [youtube]
might apply), going around is not that big a deal.  Particularly if one can
get a lower price.  Ha, price: we don't charge for traffic today, so any
efficies are not reflected in revenue (operator) or expense (user).

Why is this an energy issue?  Well, the shortest path links are likely to get
congested, and as a result may get upgraded to higher speeds, which often
means more energy used.  Meanwhile the circular, higher latency links might
go underused, yet still consuming energy.

So for me, this is where some new routing algorithm (or application of the
many circuit-link systems) would make significant sense.  But to make any of
this work, we need an interface from the network to the host.  Some people
thought APN was going to do this, but so far we have only
herbert-host2netsig.  Tom was planning a BOF.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*