legacy modularity usage for eco-conception
draft-stephan-legacy-path-eco-design-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Author | Emile Stephan | ||
| Last updated | 2024-05-20 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-stephan-legacy-path-eco-design-00
WG Working Group E. Stephan
Internet-Draft Orange
Intended status: Informational 20 May 2024
Expires: 21 November 2024
legacy modularity usage for eco-conception
draft-stephan-legacy-path-eco-design-00
Abstract
This draft discusses the usage of inventory information for assessing
the adaptation of existing devices to eco-design. It is driven by
the weight of the manufacturing in the sustainability cost with
regard to the power consumption.
About This Document
This note is to be removed before publishing as an RFC.
The latest revision of this draft can be found at
https://emile22.github.io/sustainability/draft-stephan-legacy-path-
eco-design-latest.html. Status information for this document may be
found at https://datatracker.ietf.org/doc/draft-stephan-legacy-path-
eco-design/.
Discussion of this document takes place on the Green BoF individual
mailing list (mailto:green-bof@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/green-bof/. Subscribe at
https://www.ietf.org/mailman/listinfo/green-bof/.
Source for this draft and an issue tracker can be found at
https://github.com/emile22/sustainability.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Stephan Expires 21 November 2024 [Page 1]
Internet-Draft legacy modularity and eco-design May 2024
This Internet-Draft will expire on 21 November 2024.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
3. Network and devices modularity . . . . . . . . . . . . . . . 3
4. Simple Update . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Simple Software Update . . . . . . . . . . . . . . . . . 4
5. Complex Update . . . . . . . . . . . . . . . . . . . . . . . 4
6. Gain measurements . . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . 5
9.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
Many companies in Europe have integrated sustainability improvements
into their core business strategies. It is driven by a growing
awareness of environmental issues and regulatory requirements like
CSRD (Corporate Sustainability Reporting Directive), a regulatory
framework proposed by the European Commission to enhance corporate
transparency and ensure that companies provide comparable information
to assess their sustainability performance.
Sustainability impacts numerous aspects of the life cycle management
(LCM) of devices. In this draft we discuss the advantages of
leveraging existing devices modularity to introduce eco-designed
components in the networks while being able to assess the gains in
sustainability.
Stephan Expires 21 November 2024 [Page 2]
Internet-Draft legacy modularity and eco-design May 2024
The rational is the urgent need to start decreasing resource
consumption by simply replacing devices components. It can be view
as a very basic use case of GREEN-bof [GREEN-BOF] approach.
2. Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Network and devices modularity
Networks and theirs devices are modular per design to cope with
manufacturing and operationnal obvious constraints. Existing devices
are going to be progressively replaced with eco-design products.
Both will co-exist in the networks as there is a balance to find
between the increase of the live duration of existing devices and
their replacement with eco-design devices [SUST-INS].
The same approach applies at the same time to individual devices:
legacy devices will include progressively more and more eco-designed
hardware components.
Eco Design means that the products include environmental
considerations throughout their entire lifecycle to reduce their
environmental impact. In France they are based on General Reference
Base for Eco-Design in digital services ("RGESN") at
https://ecoresponsable.numerique.gouv.fr/publications/referentiel-
general-ecoconception/.
Eco-design can be summarized as the concepts and current practices
related to the integration of environmental aspects into every stage
of a product lifecycle. This starts at product design and
development [ISO/TR 14062:2002 ]
The upgrade of legacy devices with eco-designed cards can be separate
in 2 categories:
* "Simple" update : The adaptation is simple, a card is 'just'
replaced with another one which consumes significally less power
by itself when running and which required less ressources during
its manufacturing and its deployment.
* "Complex" update: The replacement of the card requires the adding
or the update of software components to enable dynamic power
consumption.
Stephan Expires 21 November 2024 [Page 3]
Internet-Draft legacy modularity and eco-design May 2024
4. Simple Update
Network operators update their devices components since decades. By
consequence, update with eco-designed components can started
immediatly as there is no dependency on management solutions. The
assessement of environmental and power gains can be done manually or
with adhoc scripts from the datasheets of the manufacturer or using
an adhoc processing.
It is clear that information for doing static assessement is spread
over many media or OPS interfaces (datasheet, Web URL, CLI , YANG,
MIB, IPFIX ...). A proposal consists in documenting how to do static
assessement for a set of devices and components based on volontaring
[GREEN-BOF].
In the mid term, in a way to scale the assessement, inventory
[IVY-WG] requires to distinguish legacy devices which include eco-
designed components and eco-designed components inside legacy
devices. This must not delay the initial deployment of eco-designed
components in legacy devices described above.
4.1. Simple Software Update
Software modularity increases with the generalisation of continuous
developpement and deployement approaches. Power consumption of
current software components of network devices are rarely evaluated.
They can be updated immediatly 'just' by replacing with another one
which consumes significally less power by itself.
It might seem inappropriate to try to decrease the power consumption
of a software component as intituively it is only doing what is
expected, so this can't be reduced.
This exists for assessing power efficiency of Web application
components with good results. As an example, GreenIT is available as
a browser plugin https://github.com/cnumr/GreenIT-Analysis.
5. Complex Update
Currently network devices are mostly always-on. The design of their
software components do not include dynamic power management.
The update of legacy networks and devices to support dynamic power
management is something complex because it impacts the different type
of components:
* hardware component must support variation of power, of bit rate or
only being shutdown and restarted
Stephan Expires 21 November 2024 [Page 4]
Internet-Draft legacy modularity and eco-design May 2024
* firmware component must expose the monitoring and the actionable
functions to the software components
* software component must be updated or added to operate these new
capabilities
Legacy hardware components are designed for being rarely stopped and
re-started. The rythm of start/stop supported by such components
must be documented to prevent wrong usage of their real capacity.
This must be present in the datasheet or exposed by the components
themselve.
6. Gain measurements
On the short term, as promoted by the GREEN-BoF, the assessement at
the device level requires firstly datamodels augmentation [IVY-WG] to
expose these capabilities and configuration updates and then metrics
to measure the power consumption [POWEFF].
There is room for hackathon sessions to compare asessment methods.
7. Security Considerations
The tracking of LCM information may reveal information of the device
usages.
8. IANA Considerations
At this step this document has no IANA actions.
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
9.2. Informative References
[GREEN-BOF]
"BOF proposal for GREEN WG Creation", 10 May 2024,
<https://github.com/marisolpalmero/GREEN-bof>.
Stephan Expires 21 November 2024 [Page 5]
Internet-Draft legacy modularity and eco-design May 2024
[IVY-WG] "Network Inventory YANG", 23 June 2023,
<https://datatracker.ietf.org/wg/ivy>.
[POWEFF] Jan Lindblad, Snezana Mitrovic, Marisol Palmero, and
Gonzalo Salgueiro, "Power and Energy Efficiency", 7 May
2024, <https://datatracker.ietf.org/doc/html/draft-opsawg-
poweff>.
[SUST-INS] Per Andersson, Jan Lindblad, Snezana Mitrovic, Marisol
Palmero, Esther Roure, Gonzalo Salgueiro, and Stephan
Emile, "Sustainability Insights", 20 October 2023,
<https://datatracker.ietf.org/doc/draft-almprs-
sustainability-insights/>.
Acknowledgments
TODO acknowledge.
Author's Address
Emile Stephan
Orange
2, avenue Pierre Marzin
22300 Lannion
France
Email: emile.stephan@gmail.com
Stephan Expires 21 November 2024 [Page 6]