]> Huawei

China chengen@huawei.com

Huawei

China bill.wu@huawei.com

Orange

France mohamed.boucadair@orange.com

Telefonica I+D

Spain oscar.gonzalezdedios@telefonica.com

North Carolina State University

United States of America cpignata@gmail.com, cmpignat@ncsu.edu

Operations and Management Network Inventory YANG energy efficiency energy saving energy management This document defines YANG modules for energy saving management at both device and network levels. Also, the document specifies a common module that is used independent of the model layer. Discussion Venues Discussion of this document takes place on the Network Inventory YANG Working Group mailing list (inventory-yang@ietf.org), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction With the growth of networks and the increase of awareness about the environmental impact, it is important to ensure energy efficiency in the operation of network infrastructures. Operators are thus seeking for more information to reflect the power consumption of a network and the contribution of involved nodes. As described in , monitoring energy, power can be required for purposes such as:

• designing control loops for energy saving,
• investigating energy-saving potential,
• evaluating the effectiveness of energy-saving policies and measures,
• accounting for the total power received and provided by an entity, a network, or a service,
• predicting an entity's reliability based on power usage, and
• planning for the next maintenance cycle for an entity

However, there are no standard mechanisms to report and control power usage or energy consumption of different networking equipment under different network configuration and conditions. For example, in 'tidal network' in which traffic volume undergoes significant fluctuations at different times, various energy management methods might be envisaged to optimize the energy efficiency at the network scale, e.g., by selectively disabling ports or cards on specific network nodes based on (forecast) traffic patterns. This document defines YANG modules for use in energy management within a newtork. The modules covers both network and device levels (). The modules can be used, e.g., for monitoring the energy consumption of network devices, such as (but are not limited to) routers, switches, security gateways, hosts, or servers. Where applicable, device monitoring extends to the individual components of the device. The network model augments the "ietf-network" module , while the inventory model augments the "ietf-network-inventory" module with the following rationale:

• Parameters that reflect the saving modes and methods are considered as capabilities, and are thus maintained in the inventory.
• Required parameters to control and adjust nodes and components behaviors are added to the network topology as this allows operator to better assess the implications on node-specific action on the overall network.

The document leverages types defined in and .

Notes to the RFC Editor

• Note to the RFC Editor: This section is to be removed prior to publication.

This document contains placeholder values that need to be replaced with finalized values at the time of publication. This note summarizes all of the substitutions that are needed. Please apply the following replacements:

• XXXX --> the RFC number assigned to this I-D
• IIII --> the RFC number assigned to
• 2024-01-23 --> the actual date of the publication of this document

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 when, and only when, they appear in all capitals, as shown here. The meanings of the symbols in the YANG tree diagrams are defined in . The following terms are used in the document:

Network Inventory:

A collection of data for network devices and their components managed by a specific management system .

Chassis:

A physical container that allows installation of power modules, fan modules, and various types of boards and cards .

Network Element:

A manageable network entity that contains hardware and software units, e.g., a network device installed on one or several chassis .

Board and Card:

A pluggable equipment can be inserted into one or several slots/ sub-slots and can afford a specific transmission function independently . The core modular units for processing data. Depending on functions, they can be classified into Main Processing Unit (MPU), Switch Fabric Unit (SFU), Line Processing Unit (LPU), and other types. MPU is responsible for system control, management, and monitoring. SFU is responsible for line-rate data switching on the data plane. LPU is responsible for data packet processing and traffic management.

Port and Interface:

A port is a physical entity that is used for connections. While an interface is a logical entity for connections.

YANG Prefixes Names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, as shown in . Prefixes and Corresponding YANG modules

Prefix	YANG Module	Reference
ianahw	iana-hardware	[IANA_YANG]
ni	ietf-network-inventory
yang	ietf-yang-types

Energy Saving Management Data Model Overview

Overview As described in , the Network Inventory YANG data model is used to maintain the base network inventory information. This document defines the YANG module "ietf-ni-energy-saving", which augments network element of the network Inventory base model with energy saving modes, associated energy saving methods and augments the component of the network inventory base model with capability related power attributes. "ietf-ntw-energy-saving" augments the node of asbstract network model defined in with energy consumption and power usage related attributes. At the network element level, the data model covers configuration of the energy saving mode and a set of related parameters to manage (e.g., retrieve or adjust) the status of power units, fans, boards, cards, ports, processors, and links. For example, the adjustment methods include frequency tuning, shutdown, or sleep mode. In addition, the methods also support the energy saving configuration for the 'tidal' traffic flow, where related components can be turned off, e.g., during "idle" hours to optimize the energy consumption and then woken up based on some triggered (e.g., busy hours or other scheduled events). The data model defines energy saving modes representing some energy consumption levels, which are basic, standard, or deep. For each consumption level, there is a combination of methods to reach the energy saving target level. At the component level, the data model includes a set of monitoring statistics for energy consumption and energy saving operational state of each component within the network device. It also includes threshold related power parameters such as rated power, expected volts. In order to ease reuse of various paramters independent of the module layer, this document alos defines a common model: "ietf-energy-saving-common". The structure of each module is provided in the following subsections.

Common Energy Saving Management Module Structure shows the tree diagram of the YANG data model defined in .

Common Energy Saving Management Tree Structure

Energy Saving Management Network Model The structure of the ESM Network Model is depicted in .

ESM Network Model Tree Structure

ESM Inventory Model The structure of the ESM Network Inventory Model is depicted in .

ESM Inventory Model Tree Structure

YANG Modules

Common Module The module imports types defined in . file "ietf-energy-saving-common@2024-01-23.yang" module ietf-energy-saving-common { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-energy-saving-common"; prefix esm-common; import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Types"; } organization "IETF xxx Working Group."; contact "WG Web: ; WG List: Author: Gen Chen Editor: Qin Wu Editor: Mohamed Boucadair Author: Carlos Pignataro "; description "This module contains a collection of YANG definitions for power and energy management of devices. It also augments both the network topology and inventory models. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; revision 2024-01-23 { description "Initial revision."; reference "RFC XXXX: YANG Data Models for Energy Saving Management"; } feature energy-saving { description "Specifies support of energy saving management."; } identity energy-saving-mode { description "Base identity for energy saving mode."; } identity basic { base energy-saving-mode; description "Basic energy saving mode. In this mode, the system will shut down idle modules and put them in a sleep mode."; } identity standard { base energy-saving-mode; description "Standard energy saving mode. In this mode, the system extends basic energy saving mode with more advanced Lossless energy saving features, e.g., power module schedule."; } identity deep { base energy-saving-mode; description "Deep energy saving mode. In this mode, the system extends standard energy saving mode with more advanced system level energy saving features, e.g., board scheduling."; } identity energy-saving-method { description "Base identity for energy saving method."; } identity zone-based-fan-speed-adjustment { base energy-saving-method; description "The system collects information about the temperatures of the service boards in the chassis and the zones where the service boards reside. According to the current temperature and target temperature of each board, the system implements stepless speed adjustment in different zones."; } identity unused-high-speed-interface-shutdown { base energy-saving-method; description "When detecting an unused high-speed interface, the system shuts down the interface to reduce power consumption of the interface circuits. When the interface needs to run service, the system will automatically wake up the interface and restore the interface to the normal working state."; } identity unused-port-shutdown { base energy-saving-method; description "When detecting an unused user port, the system automatically or manually shuts down the interface circuits and optical module of the port to reduce port power consumption. When detecting that the port needs to run service, the system automatically enables the port and restores the port to the normal running state, without affecting application of the board."; } identity unused-board-shutdown { base energy-saving-method; description "When detecting an unused board, the system automatically shuts down the power supply of the board, ensuring zero power consumption of an unused board. When detecting that the board needs to run service, the system automatically powers on the board and restores the board to the normalrunning state, without affecting application of the whole device."; } identity dynamic-frequency-adjustment { base energy-saving-method; description "When detecting that a service board is carrying a small service load, the system automatically reduces the working frequency of the service processing module of the board while maintaining the service quality. In doing so, power consumption of the service processing module is reduced. When the service load of the board increases, the system automatically increases the working frequency of the service processing module to meet service needs."; } identity unused-channel-shutdown { base energy-saving-method; description "When an unused channel is detected, the unused channel is closed. Dynamically open the channel when detecting that there are services on the channel."; } identity load-based-power-module-scheduling { base energy-saving-method; description "Power modules intelligently schedule internal power supply based on the power load. When the power load decreases, some power supplies are automatically disabled. When the power load increases, the disabled power supplies are enabled again. "; } identity load-based-board-scheduling { base energy-saving-method; description "Boards intelligently schedule internal forwarding resources based on the service load. When the service load decreases, some forwarding resources are automatically disabled or the working frequency of the forwarding resources is reduced. When the service load increases, the disabled forwarding resources are enabled again or the working frequency of forwarding resources is improved. In the case of burst traffic, packet forwarding may be delayed, but packets will not be lost."; } identity energy-saving-power-state { description "Base identity for power state."; reference "RFC 7326: Energy Management Framework"; } identity off-state { base energy-saving-power-state; description "Indicates that the component typically requires a complete boot when awakened."; reference "RFC 7326: Energy Management Framework"; } identity sleep-state { base energy-saving-power-state; description "Indicates that a component with energy management support is not functional but immediately available such as wake up mechanism."; reference "RFC 7326: Energy Management Framework"; } identity low-power-state { base energy-saving-power-state; description "Indicates that some components with energy management support are not available and these components can take measures to use less energy."; reference "RFC 7326: Energy Management Framework"; } identity full-power-state { base energy-saving-power-state; description "Indicates that all components with energy management support are available and may use maximum power."; reference "RFC 7326: Energy Management Framework"; } typedef energy-saving-operator { type enumeration { enum on { value 1; description "Power-on for energy saving."; } enum off { value 2; description "Power-off for energy saving."; } } description "Energy saving operator."; } grouping energy-consumption-data { description "Grouping for energy monitoring."; leaf average-power { type yang:gauge64; units "mW"; description "The average consumed power."; } leaf saved-power { type yang:gauge64; units "mW"; description "The saved power."; } leaf real-power { type yang:gauge64; units "mW"; description "The actual observed consumed power."; reference "RFC 6988: Requirements for Energy Management"; } leaf actual-volts { type int32; units "mV"; description "The actual observed voltage."; reference "RFC 6988: Requirements for Energy Management"; } leaf actual-amperes { type int32; units "mA"; description "The actual observed current."; reference "RFC 6988: Requirements for Energy Management"; } leaf actual-celsius { type int32; units "0.01 C"; description "The actual observed temperature."; } } grouping energy-saving-modes { description "Grouping for energy saving mode and methods."; list energy-saving-mode { key "mode"; description "The energy saving mode."; leaf mode { type identityref { base energy-saving-mode; } description "The energy saving mode."; } leaf-list energy-saving-method { type identityref { base energy-saving-method; } description "The energy saving method."; } } } grouping power-parameters { description "Grouping for energy paramters."; leaf temperature-upper-bound { type int32; units "0.01 C"; description "The upper bound overheat temperature of the component. Upon the upper bound is exceeded, an alarm will be triggered to indicate fatal failure."; reference "RFC 8632: A YANG Data Model for Alarm Management"; } leaf temperature-middle-bound { type int32; units "0.01 C"; description "The middle bound overheat temperature of the component. Upon the middle bound is exceeded, an alarm will be triggered."; reference "RFC 8632: A YANG Data Model for Alarm Management"; } leaf temperature-lower-bound { type int32; units "0.01 C"; description "The lower bound overheat temperature of the component. Upon the lower bound is exceeded, the alarm will be triggered."; reference "RFC 8632: A YANG Data Model for Alarm Management"; } leaf rated-power { type yang:gauge64; units "mW"; description "The rated power."; } leaf expected-volts { type int32; units "mV"; description "The expected volts."; } leaf low-volts-bound { type int32; units "mV"; description "The lower volts bound which might cause equipment misbehavior or even damage."; } leaf low-volts-fatal { type int32; units "mV"; description "The lowest volts bound which might cause equipment fatal damage."; } leaf high-volts-bound { type int32; units "mV"; description "The higher volts bound which should trigger an alarm."; reference "RFC 8632: A YANG Data Model for Alarm Management"; } leaf high-volts-fatal { type int32; units "mV"; description "The highest volts bound of monitoring class which will cause fatal failure."; } } grouping energy-power-consumption-stats { description "Statistics data about energy and power monitoring."; leaf total-energy-consumption { type yang:gauge64; units "Wh"; description "Accumulated energy consumption of equipment."; } leaf saved-energy { type yang:gauge64; units "Wh"; description "Saved energy consumption of equipment."; } leaf eer { type decimal64 { fraction-digits 18; } units "Gbps/Watt"; description "The energy efficiency rating (EER) is a metric generally defined as a functional unit divided by the energy used."; } } } ]]>

Network Module The module imports "ietf-network" and "ietf-energy-saving-common". file "ietf-ntw-energy-saving@2024-01-23.yang" module ietf-ntw-energy-saving { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ntw-energy-saving"; prefix esm-ntw; import ietf-energy-saving-common { prefix esm-common; reference "RFC XXXX: YANG Data Models for Energy Saving Management"; } import ietf-network { prefix nw; reference "RFC 8345: A YANG Data Model for Network Topologies"; } import ietf-yang-types { prefix yang; reference "RFC 6991: Common YANG Types"; } import iana-hardware { prefix ianahw; reference "https://www.iana.org/assignments/iana-hardware/iana-hardware.xhtml"; } organization "IETF XXX Working Group."; contact "WG Web: ; WG List: Author: Gen Chen Editor: Qin Wu Editor: Mohamed Boucadair Author: Carlos Pignataro "; description "This module contains a collection of YANG definitions for power and energy management of devices. It also augments both the network topology and inventory models. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; revision 2024-01-23 { description "Initial revision."; reference "RFC XXXX: YANG Data Models for Energy Saving Management"; } augment "/nw:networks/nw:network/nw:node" { if-feature "esm-common:energy-saving"; description "Energy monitoring data for network elements."; container energy-power-consumption { config false; description "Statistics data about energy and power monitoring."; uses esm-common:energy-power-consumption-stats; leaf start-time { type yang:date-and-time; description "The time (in hundredths of a second) since the network management portion of the system was last re-initialized. It corresponds to the sysUpTime MIB object. It specifies the start time of the energy measurement results collection."; reference "RFC 3418: Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)"; } } container energy-saving-modes { description "List of the energy saving mode."; uses esm-common:energy-saving-modes; } list component { key name; config false; description "List of components."; leaf name { type string; description "The name assigned to this component. This name is not required to be the same as entPhysicalName."; } leaf class { type identityref { base ianahw:hardware-class; } mandatory true; description "An indication of the general hardware type of the component."; reference "RFC 6933: Entity MIB (Version 4) - entPhysicalClass"; } container energy-monitoring { description "Energy monitoring data for components."; container energy-consumption { description "Statistics of component about energy monitoring."; uses esm-common:energy-consumption-data; } container energy-saving { description "Controls energy saving parameters of a component."; leaf enabled { type boolean; default "true"; description "Controls whether the energy-saving of the component is enabled (when set to true) or disabled (set to false)."; } leaf power-state { type identityref { base esm-common:energy-saving-power-state; } description "The device energy saving operator state."; } } } } } } ]]>

Network Inventory Module The module imports "ietf-network-inventory" and "ietf-energy-saving-common". file "ietf-ni-energy-saving@2024-01-23.yang" module ietf-ni-energy-saving { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ni-energy-saving"; prefix esm-ni; import ietf-energy-saving-common { prefix esm-common; reference "RFC XXXX: YANG Data Models for Energy Saving Management"; } import ietf-network-inventory { prefix ni; reference "RFC IIII: A YANG Data Model for Network Inventory"; } organization "IETF xxx Working Group."; contact "WG Web: ; WG List: Author: Gen Chen Editor: Qin Wu Editor: Mohamed Boucadair Author: Carlos Pignataro "; description "This module contains a collection of YANG definitions for power and energy management of devices. It also augments both the network topology and inventory models. Copyright (c) 2024 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; revision 2024-01-23 { description "Initial revision."; reference "RFC XXXX: YANG Data Models for Energy Saving Management"; } grouping network-element-ref { description "Contains the information necessary to reference a network element."; leaf ne-ref { type leafref { path "/ni:network-inventory/ni:network-elements" + "/ni:network-element/ni:ne-id"; require-instance false; } description "Used to reference a network element."; } } grouping component-ref { description "Contains the information necessary to reference a component."; leaf node-ref { type leafref { path "/ni:network-inventory/ni:network-elements" + "/ni:network-element[ni:ne-id=" + "current()/../ne-ref]/ni:components/ni:component" + "/ni:component-id"; require-instance false; } description "Used to reference a component."; } uses network-element-ref; } augment "/ni:network-inventory/ni:network-elements" + "/ni:network-element" { if-feature "esm-common:energy-saving"; description "Energy management static data for network element."; container energy-management { config false; description "Statistics of the energy management."; leaf energy-monitoring-capability { type boolean; description "Indicates whether monitoring can be performed."; } container energy-saving-modes { description "List of supported energy saving modes."; uses esm-common:energy-saving-modes; } } } augment "/ni:network-inventory/ni:network-elements" + "/ni:network-element/ni:components/ni:component" { if-feature "esm-common:energy-saving"; description "Energy management static data for component."; container power-parameters { config false; description "Power parameter monitoring."; uses esm-common:power-parameters; } } } ]]>

Security Considerations This section uses the template described in Section 3.7 of . The YANG modules specified in this document define a schema for data that is designed to be accessed via network management protocol such as NETCONF or RESTCONF .These network management protocols are required to use a secure transport layer and mutual authentication, e.g., SSH without the "none" authentication option, Transport Layer Security (TLS) with mutual X.509 authentication, and HTTPS with HTTP authentication (). The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. There are several data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. Specifically, the following subtrees and data nodes have particular sensitivities/vulnerabilities:

energy-saving-modes:

This leaf specifies the energy saving mode set globally on a device.

esm-ntw:energy-saving/esm-ntw:enabled:

This leaf enable/disables energy saving state of specific component. Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. Specifically, the following subtrees and data nodes have particular sensitivities/vulnerabilities:

'TBC':

....

IANA Considerations

The "IETF XML" Registry This document requests IANA to register the following URIs in the "ns" subregistry within the "IETF XML Registry" :

The "YANG Module Names" Registry This document requests IANA to register the following YANG modules in the "YANG Module Names" registry within the "YANG Parameters" registry group.

References Normative References This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models. Huawei Technologies Nokia Vodafone TIM Cisco This document defines a base YANG data model for network inventory that is application- and technology-agnostic. This data model can be augmented with application-specific and technology-specific details in other, more specific network inventory data models. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document obsoletes RFC 6536. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] Informative References This document defines requirements for standards specifications for Energy Management. The requirements defined in this document are concerned with monitoring functions as well as control functions. Monitoring functions include identifying energy-managed devices and their components, as well as monitoring their Power States, Power Inlets, Power Outlets, actual power, Power Attributes, received energy, provided energy, and contained batteries. Control functions include such functions as controlling power supply and Power State of energy-managed devices and their components. This document does not specify the features that must be implemented by compliant implementations but rather lists features that must be supported by standards for Energy Management. YumaWorks Orange Huawei This memo provides guidelines for authors and reviewers of specifications containing YANG modules, including IANA-maintained modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) and RESTCONF protocol implementations that utilize YANG modules. This document obsoletes RFC 8407. Also, this document updates RFC 8126 by providing additional guidelines for writing the IANA considerations for RFCs that specify IANA-maintained modules. This document defines managed objects which describe the behavior of a Simple Network Management Protocol (SNMP) entity. This document obsoletes RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2). [STANDARDS-TRACK] This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of the Entity MIB module published as RFC 4133. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230. Futurewei Futurewei Ericsson Nokia Nvidia Nokia North Carolina State University This document explains the need for network instrumentation that allows to assess a number of sustainability-related attributes such as power consumption, energy efficiency, and carbon footprint associated with a network, its equipment, and the services that are provided over it. It also suggests a set of related metrics that, when provided visibility into, can help to optimize a network's "greenness" accordingly. HP HP HP H3C With the rapid growth of networks around the globe there is an ever increasing need to improve the energy efficiency of network devices. Operators are begining to seek more information of power consumption in the network, have no standard mechanism to measure, report and compare power usage of different networking equipment under different network configuration and conditions. This document provides suggestions for measuring power usage of live networks under different traffic loads and various switch router configuration settings. It provides a benchmarking suite which can be employed for any networking device .

Acknowledgments This work has benefited from the discussions that occured during the Sustainable Networking Side Meeting in IETF#117 and the "e-impact" IAB workshop. In particular, assess several sustainability-related attributes such as power consumption, energy efficiency, and carbon footprint associated with a network, its equipment, and the services that are provided over it and suggest a set of metrics that provide network observability and can be used to optimize a network's "greenness". provides suggestions for measuring power usage of live networks under different traffic loads and various switch router configuration settings.