From: "David Fernández" <davidfdzp@gmail.com>
To: Hesham ElBakoury <helbakoury@gmail.com>
Cc: starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Reducing Eenergy Consumption and Carbon Foot Print of Satellites Network
Date: Thu, 28 Nov 2024 16:11:05 +0100 [thread overview]
Message-ID: <CAC=tZ0qHFnfGa835GRPn7ED73jKpy_X-qjbcmxO4HJbF4OmkXQ@mail.gmail.com> (raw)
In-Reply-To: <bf140aab-eb5c-4eb8-836e-4da0969e792d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2186 bytes --]
Hi Hesham,
Not really, but this one in English is referencing it and somehow
reusing/summarizing it.
https://dvb.org/wp-content/uploads/2023/11/S100_Study-Mission-on-Energy-Aware-Delivery-and-Consumption_Nov-2023.pdf
Regards,
David
On Thu, 28 Nov 2024 at 15:36, Hesham ElBakoury <helbakoury@gmail.com> wrote:
> Hi David,
>
> Is there an english version of the document:
> Arcom-arcep-ademe-etude-impact-environnemental-des-usages-audiovisuels.pdf
> <https://www.arcom.fr/sites/default/files/2024-10/Arcom-arcep-ademe-etude-impact-environnemental-des-usages-audiovisuels.pdf>
>
> Thanks
>
> Hesham
> On 11/28/2024 2:39 AM, David Fernández wrote:
>
> Hi Hesham,
>
> You may check this report, in case you missed it, for ideas on how to
> reduce energy consumption and carbon footprint, in general for the
> audiovisual sector, but satellite distribution of video may be considered
> there:
> https://en.arcep.fr/news/press-releases/view/n/environment-071024.html
>
> You may be interested in following this IETF group, too:
> https://datatracker.ietf.org/group/green/about
>
> This workshop already happened, but you may get something from there too,
> about the development of energy neutral devices:
> https://6g-conference.dnac.org/2024/en-iot-2024
>
> Considering that most of the CO2 is emitted during a device fabrication
> (e.g. 79% for laptops, according to Atos), making them last long and being
> modular and repairable may be the best way to reduce the carbon footprint
> (and the increasing amount of e-waste).
>
> Regards,
>
> David
>
> Date: Sat, 23 Nov 2024 11:16:11 -0800
> From: Hesham ElBakoury <helbakoury@gmail.com>
> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: [Starlink] Reducing Eenergy Consumption and Carbon Foot Print
> of Satellites Network
> Message-ID:
> <CAFvDQ9p6R9wdGFri3YPdU5=
> 25FjyD6iN5yT+oW7XkgCZk77bow@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I appreciate your input and pointers to publications regarding how to
> reduce energy consumption and carbon footprint of satellites network.
>
> Thanks
> Hesham
>
>
[-- Attachment #2: Type: text/html, Size: 4139 bytes --]
next prev parent reply other threads:[~2024-11-28 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 10:39 David Fernández
2024-11-28 12:58 ` David Lang
2024-11-28 14:53 ` Ulrich Speidel
2024-11-28 13:25 ` Hesham ElBakoury
2024-11-28 14:36 ` Hesham ElBakoury
2024-11-28 15:11 ` David Fernández [this message]
2024-11-28 16:29 ` Hesham ElBakoury
2024-11-28 15:21 ` Ulrich Speidel
-- strict thread matches above, loose matches on Subject: below --
2024-11-23 19:16 Hesham ElBakoury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=tZ0qHFnfGa835GRPn7ED73jKpy_X-qjbcmxO4HJbF4OmkXQ@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--cc=helbakoury@gmail.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox