Two points: 1. It might be worth an effort to see if there are existing knobs to tweak for sustainability. For example, every recommended repetition rate for discovery or refresh messages, especially multicast, could be reviewed to see if it can usefully be slowed down. Every link-local protocol could be reviewed for compatibility with wake-on-LAN. 2. Network Energy Management could be a good topic for an IAB workshop or program. Not a joke: before investing much effort in this topic, we should consider whether that effort (e.g. convening a workshop) will consume more energy than it saves. Regards Brian On 06-Aug-22 11:22, Joel Halpern wrote:
I can't speak for Fred, but I don't think we as a community even know what "energy efficient protocol" means. Much less how that trades off against all the other aspects of protocol design. We do consider message size and frequency when we design protocols. We consider those aspects along with lots of others. if that is "designing energy efficient protocols" then we already do so. On the other hand, design for issues such as to to partially wake up a sleeping device is generally outside our remit and skill set. And is meaningless for many of our devices. Yours, Joel On 8/5/2022 7:18 PM, Hesham ElBakoury wrote:Hi Fred, Do you think IETF engineers have the skill sets to design energy efficient protocols or enhance existing ones to be more energy efficient ? Thanks, Hesham On Fri, Aug 5, 2022, 1:22 PM Fred Baker <fredbaker.ietf@xxxxxxxxx> wrote: Echoing a previous post, I’m not sure sustainability is part of our skill set. If we were to try to forcibly add it, I suspect we’d get the same level of response security originally got: “sustainability is not specified in this document”. Sent using a machine that autocorrects in interesting ways... > On Aug 5, 2022, at 2:26 AM, Stewart Bryant <stewart.bryant@xxxxxxxxx> wrote: > > Perhaps it is time for a new mandatory section in RFCs: sustainability?
