This is two days off of being an April Fools' RFC, but it's hard not to consider it to be one. Estimating carbon emissions related to a single network request

This is two days off of being an April Fools' RFC, but it's hard not to consider it to be one. Estimating carbon emissions related to a single network request sounds incredibly error prone. Computers don't have nice, linear efficiency curves, they have computational overheads, and they can't reclock perfectly according to incoming demand. So you'd need your web server to check instantaneous CPU power consumption, subtract out CPU utilization from non web server processes, divide by the currently in-flight number of requests, and multiply by the request time. All of that adds error to the process. I guess the only benefit here is that you could have some middleware somewhere that adds up CO2e figures calculated by backend web services to compute another CO2e figure? But even then this seems like a really fiddly and bad way for an organization to count up carbon. Furthermore the actual methodology for counting up CO2e is part of a proprietary ISO standard, because I doubt they expected a freely-implementable RFC to actually need to count industrial CO2e emissions.