<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<?rfc docmapping="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-green-power-and-energy-yang-06" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="GREEN-PEM-YANG">Power and Energy YANG Module</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-green-power-and-energy-yang-06"/>
    <author initials="B." surname="Claise" fullname="Benoit Claise">
      <organization>Everything OPS &amp; Arrcus</organization>
      <address>
        <email>benoit@everything-ops.net</email>
      </address>
    </author>
    <author initials="G." surname="Chen" fullname="Gen Chen">
      <organization>Huawei</organization>
      <address>
        <email>chengen@huawei.com</email>
      </address>
    </author>
    <author initials="M." surname="Palmero" fullname="Marisol Palmero">
      <organization>Individual</organization>
      <address>
        <email>marisol.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="J." surname="Lindblad" fullname="Jan Lindblad">
      <organization>All For Eco</organization>
      <address>
        <email>jan.lindblad@for.eco</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>OPS</area>
    <workgroup>GREEN</workgroup>
    <keyword>Internet-Draft</keyword>
    <keyword>GREEN</keyword>
    <keyword>YANG</keyword>
    <keyword>Power</keyword>
    <keyword>Energy</keyword>
    <abstract>
      <?line 111?>

<t>This document defines a YANG data model for Power and Energy
monitoring and control of devices within or connected to communication
networks.</t>
    </abstract>
  </front>
  <middle>
    <?line 117?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

<t>This document defines a YANG data model for Power and Energy
Monitoring and control of devices within or connected to communication
networks, for the use cases document in
<xref target="I-D.ietf-green-use-cases"/>.</t>
      <t>The data model includes both the monitoring and control of Energy
Objects for networked devices.</t>
      <t>This YANG data model is based on the "GREEN framework"
<xref target="I-D.ietf-green-framework"/>, following the "GREEN terminology"
<xref target="I-D.ietf-green-terminology"/>.</t>
      <t>Power and Energy Monitoring and Control can be applied to devices in
communication networks. All identifiable devices with measurable or
representable Power and Energy characteristics fall within the scope
of this specification. Target devices include, but are not limited to,
routers, switches, Power over Ethernet (PoE) endpoints, smart Power
Distribution Units (PDUs), and storage and compute servers.</t>
      <t>Where applicable, device monitoring extends to the Components of the
device as well as software and services running on the device. As a
result, the metrics to be monitored include Device Level Energy
Efficiency (DLEE), Component Level Energy Efficiency (CLEE), and
potential Service Level Energy Efficiency (SLEE) at the orchestrator
level. For example, a router can contain Components such as a Line
Processing Unit (LPU), a Switch Fabric Unit (SFU), and a Main
Processing Unit (MPU).</t>
      <section anchor="terminology">
        <name>Terminology</name>
        <t>This document makes use of the terms defined in
<xref target="I-D.ietf-green-terminology"/>:</t>
        <ul spacing="normal">
          <li>
            <t>Power</t>
          </li>
          <li>
            <t>Nameplate Power</t>
          </li>
          <li>
            <t>Power State</t>
          </li>
          <li>
            <t>Power Interface</t>
          </li>
          <li>
            <t>Power Inlet</t>
          </li>
          <li>
            <t>Power Outlet</t>
          </li>
          <li>
            <t>Power Factor</t>
          </li>
          <li>
            <t>Energy</t>
          </li>
          <li>
            <t>Energy Object</t>
          </li>
          <li>
            <t>Component</t>
          </li>
          <li>
            <t>Energy Monitoring</t>
          </li>
          <li>
            <t>Energy Efficiency</t>
          </li>
          <li>
            <t>Device Level Energy Efficiency (DLEE)</t>
          </li>
          <li>
            <t>Component Level Energy Efficiency (CLEE)</t>
          </li>
          <li>
            <t>Service Level Energy Efficiency (SLEE)</t>
          </li>
        </ul>
        <t>The terms reused from <xref target="I-D.ietf-green-terminology"/> and
<xref target="I-D.ietf-green-framework"/> are capitalized in this
specification.</t>
        <t>This document defines the following term, which is also capitalized:</t>
        <dl>
          <dt>Power Cap:</dt>
          <dd>
            <t>An upper limit on the Power that an Energy Object receives, set by
an administrator or a controller and enforced by the device, for
example by reducing the clock frequency of a Component. Unlike the
Nameplate Power, which is a fixed design value, a Power Cap can
change during operation.</t>
          </dd>
        </dl>
        <t>This document uses the terms Power and Energy in accordance with
<xref target="I-D.ietf-green-terminology"/>. Power refers to the instantaneous
rate at which a device consumes or produces electrical energy
(typically expressed in watts). Energy, by contrast, represents the
cumulative amount of work performed over time (typically expressed in
joules or watt-hours). Both concepts are required within this YANG
module. Power enables real-time monitoring, control, and optimization
of device operation, while Energy provides a time-integrated view
necessary for accounting, reporting, and even for sustainability
analysis. This specification includes both Power and Energy
attributes.</t>
        <t>The terminology for describing YANG modules is defined in <xref target="RFC7950"/>.
The meanings of the symbols in the YANG tree diagrams are defined in
<xref target="RFC8340"/>.</t>
      </section>
    </section>
    <section anchor="the-green-framework">
      <name>The GREEN Framework</name>
      <t>The "GREEN framework" described in <xref target="I-D.ietf-green-framework"/>
covers monitoring and controlling devices and Components where
monitoring includes measuring Power, Energy, demand and attributes of
Power.</t>
      <t>For the whole picture of the monitoring interfaces and the relevant
requirements, please refer to the "GREEN reference model" in
<xref target="I-D.ietf-green-framework"/>.</t>
    </section>
    <section anchor="power-and-energy-data-model">
      <name>Power and Energy Data Model</name>
      <t>The Power and Energy Data Model reports the Power and Energy of each
Energy Object, in fixed units per leaf (milliwatts for instantaneous
Power and the Power Cap, watts for the Nameplate Power, and
milliwatt-hours for Energy), together with the measurement accuracy,
etc.</t>
      <t>Power and Energy are reported per direction, as unsigned values.
Received is the Power or Energy flowing into the Energy Object through
its Power Inlets, and provided is the Power or Energy flowing out of
it to other Energy Objects through its Power Outlets. Both can be
non-zero at the same time: a power supply receives Power from its
source and provides Power to the device, and the difference is its
loss. The same Power Interface can act as a Power Inlet and a Power
Outlet: a battery receives Power while charging and provides Power
while discharging. The state of a battery, such as its charge and
capacity, is out of scope of this document; it is covered by the
Battery MIB <xref target="RFC7577"/>. For Power over Ethernet, the Power provided
by a switch is measured at its PoE ports, and the Power received by a
powered device at its own Power Inlet; the difference is dissipated
mainly in the cable and connectors.</t>
      <t>The net Power of an Energy Object is its received Power
minus its provided Power, so that Power passed from one Energy Object
to another is not counted twice when the net Power of several Energy
Objects is summed. An example is given in <xref target="psu-example"/>.</t>
      <t>A containment tree view of the Power and Energy Monitoring is presented.
The model uses the admin and oper leaves within the power-state
container to represent the intended (administrative) and operational
(actual) Power States respectively. The two leaves together form the
complete Power State management interface. The operational tree
('container energy-objects') will typically contain a significantly
larger number of instances than the configuration tree
('container energy-control'). The configuration tree, which is limited
to explicitly provisioned entries, provides a compact self-contained
view of the intent. For this reason, although an NMDA
(Network Management Datastore Architecture) design with a single
"state" leaf (per <xref target="RFC8342"/>) was considered, it is not adopted in
this document.</t>
      <t>The model also allows an administrator or controller to request a
Power Cap on an Energy Object, for example to cap the Power of a GPU
in a cluster. The requested limit is
configured in the power-cap container in /energy-control. The device
enforces the requested limit, or the closest value that the Energy
Object supports, and reports the limit in effect in the power-cap
container of the Power attributes in /energy-objects. Discovering the
range of limits that an Energy Object supports is out of scope of this
document.</t>
      <t>The existence of a Power Cap and its effect are reported separately. The
power-cap container in /energy-objects is present only while a cap is
enforced, and the Energy Object then does not draw more Power than the
enforced limit. The limiting leaf indicates whether the cap is
constraining the Energy Object at this time, that is, whether the
Energy Object would draw more Power without the cap, so that its
operation is reduced to stay within the limit. For example, with a cap
of 300 W, a GPU that would draw 80 W when idle, or 200 W with a light
workload, is not constrained (limiting is false), whereas a GPU that
would draw 450 W during a training job is held at 300 W and runs more
slowly (limiting is true).</t>
      <t>A management system cannot reliably derive the limiting indication by
comparing the received Power with the enforced limit: the Power
that the Energy Object would draw without the cap is not observable,
caps are typically enforced as an average over a time window, and the
measurement accuracy blurs the comparison. The device, which applies
the cap, knows whether it is constraining the Energy Object.</t>
      <t>The id of an entry in /energy-control/energy-objects/energy-object
<bcp14>SHOULD</bcp14> be the id of an existing or anticipated entry in
/energy-objects/energy-object. This allows an administrator or
controller to correlate a configured Power State intent with the Energy
Object being monitored. The id is a leafref with require-instance
false, so that the configuration can be created before the Energy
Object is introduced and remains after it has disappeared from the
system. If the referred Energy Object does not currently exist, the
configuration item for it has no effect.</t>
      <t>The relationship list models the relationship between an Energy
Object and its peer Energy Objects, using the
<tt>energy-relationship-type</tt> identities: <tt>powered-by</tt> and <tt>powering</tt>
(Power Source Relationship), <tt>metered-by</tt> and <tt>metering</tt> (Metering
Relationship), <tt>aggregated-by</tt> and <tt>aggregating</tt> (Aggregation
Relationship), and <tt>enabled-by</tt> and <tt>enabling</tt> (Functional Enablement
Relationship).</t>
      <t>Each pair of identities expresses the same relationship from the
perspective of each participant (e.g., if Energy Object A is powered-by
Energy Object B, then Energy Object B is powering Energy Object A).
These relationship categories, including their use for power/metering
topology discovery and for preventing double-counting of Energy values,
are defined in <xref target="I-D.ietf-green-framework"/>. For each relationship
type, one or more peer Energy Objects can be identified via the <tt>id</tt>
leaf within the <tt>peer</tt> list, a string value that is preferably the
peer's UUID; if the UUID is not known, another identifier can be used,
together with human-readable details captured in the <tt>details</tt> leaf.</t>
      <t>Regarding relationships among Energy Objects, this document does not
provide a mechanism to configure relationships on the device (i.e.,
there is no relationship list under /energy-control); the
relationship list under /energy-objects/energy-object is read-only
operational data (config false).</t>
      <t>For relationships between Components within the same device (e.g.,
between a Line Processing Unit (LPU) and a Switch Fabric Unit (SFU)),
the device can typically determine and populate this data directly,
without requiring external configuration.</t>
      <t>Relationships between Energy Objects located on different devices are
generally established and maintained at the controller or Energy
Management System (EnMS) level, which has visibility into the
broader network topology, as discussed in
<xref target="I-D.ietf-green-framework"/>. A device may still report a known
inter-device relationship (e.g., using the peer's network-level UUID)
when it has been made aware of it, but this module does not provide a
mechanism to configure such relationships on the device itself.</t>
      <sourcecode type="yangtree"><![CDATA[
module: ietf-power-and-energy
  +--ro energy-objects
  |  +--ro energy-object* [id]
  |     +--ro id                     string
  |     +--ro source-component-id?   -> /hw:hardware/component/name
  |     +--ro power
  |     |  +--ro instantaneous-power-received?   uint64
  |     |  +--ro instantaneous-power-provided?   uint64
  |     |  +--ro nameplate-power?                uint32
  |     |  +--ro data-source-accuracy?           identityref
  |     |  +--ro power-factor?                   power-factor
  |     |  +--ro measurement-local?              boolean
  |     |  +--ro power-cap!
  |     |     +--ro limit       uint64
  |     |     +--ro limiting?   boolean
  |     +--ro energy
  |     |  +--ro total-energy-received?   yang:counter64
  |     |  +--ro total-energy-provided?   yang:counter64
  |     |  +--ro discontinuity-time?      yang:date-and-time
  |     |  +--ro data-source-accuracy?    identityref
  |     |  +--ro measurement-local?       boolean
  |     +--ro certifications*        identityref
  |     +--ro power-state
  |     |  +--ro oper?   identityref
  |     +--ro relationship* [type]
  |        +--ro type    identityref
  |        +--ro peer* [id]
  |           +--ro id         string
  |           +--ro details?   string
  +--rw energy-control
     +--rw energy-objects
        +--rw energy-object* [id]
           +--rw id             -> /energy-objects/energy-object/id
           +--rw power-state
           |  +--rw admin?   identityref
           |  +--rw oper?
           |          -> /energy-objects/energy-object
           |             /power-state/oper
           +--rw power-cap
              +--rw limit?   uint64
]]></sourcecode>
    </section>
    <section anchor="relationship-to-the-hardware-yang-data-model">
      <name>Relationship to the Hardware YANG Data Model</name>
      <t>The ietf-hardware YANG Data Model for Hardware Management <xref target="RFC8348"/>
is required in connection with the 'source-component-id' leaf.</t>
      <t>In the Power and Energy YANG Module defined in this specification,
the leaf 'source-component-id' refers to a hardware component
defined in the ietf-hardware module <xref target="RFC8348"/>.</t>
      <t>The ietf-hardware module provides three identifiers for hardware
components: 'name', 'physical-index', and 'uuid'.  The 'name'
leaf is the list key and uniquely identifies a component within
a single device, but carries no uniqueness guarantee across
different devices or management systems.  The 'physical-index'
leaf optionally matches entPhysicalIndex in the Entity MIB
<xref target="RFC6933"/> when the entity-mib feature is supported.  The 'uuid'
leaf is a Universally Unique Identifier <xref target="RFC9562"/>, intended to
be unique across space and time, and therefore suitable for
stable identification of a component across management systems.</t>
      <t>The GREEN YANG module imports the ietf-hardware module <xref target="RFC8348"/>
and uses the 'name' leaf as the value of 'source-component-id'. The
'name' leaf is the list key of the hardware components and uniquely
identifies a component within a single device. For component
identification across devices and management systems, the device
<bcp14>SHOULD</bcp14> also report the 'uuid' leaf of the referenced component.</t>
      <t>The mapping between energy-object entries in this YANG Module and the
hardware-components in ietf-hardware YANG module <xref target="RFC8348"/> is
designed to be 1:1, architecturally aligning each energy-object entry
with exactly one physical hardware component via source-component-id.
As no hardware class exists for hardware accelerators such as GPUs,
this document requests a new "accelerator" hardware class (see
<xref target="accelerator-class"/>).</t>
      <t>There are also cases where controllers generate their own set of UUIDs
for the hardware components. In such a case, it might be necessary to
document the mappings between the UUIDs generated on the hardware side
and the UUIDs on the controller side. In general, the devices (such as
routers) generate the UUID, and the controller can query it.</t>
      <t>The ietf-hardware YANG module <xref target="RFC8348"/> allows discovering all the
device components, including the containment tree, and the parent/child
relationship, which is important for Energy/Power aggregation (see the
contains-child relationship in RFC 8348).</t>
    </section>
    <section anchor="relationship-to-the-eman-work">
      <name>Relationship to the EMAN Work</name>
      <t>The EMAN IETF Working Group
(https://datatracker.ietf.org/wg/eman/about/) is a concluded Working
Group that produced several RFCs in the domain of Power and
Energy. The Working Group produced MIB modules for monitoring and
control for Power and Energy, for the context information, for battery
monitoring <xref target="RFC7577"/>, and an extension to the ENTITY-MIB to add the
UUID definition <xref target="RFC6933"/>.</t>
      <t>For various reasons, those MIB modules were not implemented by
vendors.</t>
      <t>The Power and Energy data model defined in this specification uses the
Monitoring and Control MIB for Power and Energy <xref target="RFC7460"/> as a
starting point to discuss the solution to the different use cases in
<xref target="I-D.ietf-green-use-cases"/>.</t>
      <t>However, it has not been the goal to simply map the MIB module to a
YANG module. The changes compared to the EMAN MIB modules are mainly
due to the alignment with the up-to-date requirements of the network
carriers on Energy Efficiency. Compared to the MIB modules, some
definitions and types are optimized, some new data nodes are added,
and some legacy MIB objects are removed accordingly.
For example, the signed eoPower object of <xref target="RFC7460"/> is replaced by
the Power received and the Power provided, as unsigned values, in the
same way as the Energy counters.</t>
    </section>
    <section anchor="power-and-energy-yang-module">
      <name>Power and Energy YANG Module</name>
      <t>Note to the RFC Editor: Please replace all occurrences of "XXXX" in
this document with the RFC number assigned to this document, and the
revision date of both YANG modules with the date of publication of
this document. Please remove this note before publication.</t>
      <t>This YANG Module is used to monitor and control Power and Energy usage
of network devices and the Components on these devices.</t>
      <sourcecode type="yang" markers="true" name="ietf-power-and-energy@2026-11-01.yang"><![CDATA[
module ietf-power-and-energy {
  yang-version 1.1;
  
  namespace "urn:ietf:params:xml:ns:yang:ietf-power-and-energy";
  prefix eo;
  
  import ietf-hardware {
    prefix hw;
    reference
      "RFC 8348: A YANG Data Model for Hardware Management";
  }

  import ietf-yang-types {
    prefix yang;
    reference
      "RFC 9911: Common YANG Data Types";
  }

  import iana-power-and-energy {
    prefix ianaeo;
    reference
      "RFC XXXX: Power and Energy YANG Module";
  }

  organization
    "IETF GREEN Working Group";
  
  contact
    "WG Web:  <https://datatracker.ietf.org/wg/green/>
     WG List: <mailto:green@ietf.org>

     Author:  Benoit Claise
              <mailto:benoit@everything-ops.net>
     Author:  Gen Chen
              <mailto:chengen@huawei.com>
     Author:  Marisol Palmero
              <mailto:marisol.ietf@gmail.com>
     Author:  Jan Lindblad
              <mailto:jan.lindblad@for.eco>";
     
     
  
  description
    "This YANG module defines a data model for Power and Energy
     monitoring and control of devices within or connected to
     communication networks.

     The capitalized terms used in this module (for example,
     Power, Energy, Energy Object, Component, Power State,
     Nameplate Power, and Power Inlet) are defined in
     I-D.ietf-green-terminology, except Power Cap, which is
     defined in RFC XXXX.
     
     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 (RFC 2119) (RFC 8174) when, and only when,
     they appear in all capitals, as shown here.
     
     Copyright (c) 2026 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
     (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
     for full legal notices.";

  revision 2026-11-01 {
    description
      "Initial revision";
    reference
      "RFC XXXX: Power and Energy YANG Module";
  }
  
  identity data-source-accuracy {
    description
      "Base identity for all possible data accuracy types.
       This identity serves as the root for a hierarchy of accuracy
       types, allowing for extensibility while maintaining alignment
       with current and future industry standards.

       The hierarchy, as defined in this YANG module, is as follows.
       Other modules may extend this hierarchy with additional
       accuracy base- and sub-types as needed.

       data-source-accuracy
        +-- accuracy-like-parent
        +-- accuracy-unknown
        |    +-- accuracy-unavailable
        +-- accuracy-estimated
        |    +-- accuracy-static
        |    +-- accuracy-historic
        |    +-- accuracy-learned
        +-- accuracy-measured
             +-- accuracy-measured-bronze
             |    +-- accuracy-measured-bronze-1
             |    +-- accuracy-measured-bronze-10
             |    +-- accuracy-measured-bronze-100
             |    +-- accuracy-measured-bronze-1000
             +-- accuracy-measured-silver
             |    +-- accuracy-measured-silver-...
             +-- accuracy-measured-gold
             |    +-- accuracy-measured-gold-...
             +-- accuracy-measured-red
             |    +-- accuracy-measured-red-...
             +-- accuracy-measured-ones

       The accuracy levels under accuracy-measured are based on
       percent-wise accuracy classes:
          bronze:  +/- 30%
          silver:  +/- 10%
          gold:    +/- 5%
          red:     +/- 2%

       In addition, the accuracy-measured-ones identity indicates
       a Power or Energy measurement with all digits valid, except 
       trailing zeros.

       Since percent-wise accuracy works poorly for very small
       values, standards such as IEC 62053, IEC 61850-7-4 and
       IEEE 1451 define accuracy classes based on a combination of
       percent-wise accuracy and absolute accuracy thresholds.
       E.g. +/-1 % of reading  +  +/-0.05 absolute units.

       Similarly, for each percent-wise accuracy class, this module
       defines a few absolute tolerance classes, indicated by
       suffixes to the accuracy identity names. The suffixes indicate
       absolute accuracy thresholds:
          no suffix:   +/-0.5  absolute units
          -1:          +/-1    absolute unit
          -10:         +/-10   absolute units
          -100:        +/-100  absolute units
          -1000:       +/-1000 absolute units
       Thus, for example, accuracy-measured-gold-10 indicates
       a Power data measurement with an accuracy of either
       +/-5% or +/-10 absolute units, whichever is larger.

       For example, a power sensor reading might report a value
       of 16250 milliwatts, under accuracy-measured-gold-10. This 
       indicates that the actual Power value is between 15437.5 and 
       17062.5 milliwatts, since 5% of 16250 milliwatts is 812.5 
       milliwatts, which is greater than the absolute threshold of 
       10 milliwatts.

       At another time, the same sensor might report a value
       of 150 milliwatts, under accuracy-measured-gold-10. This 
       indicates that the actual Power value is between 140 and 160 
       milliwatts, since 5% of 150 milliwatts is only 7.5 milliwatts,
       which is less than the absolute threshold of 10 milliwatts.";
  }
  identity accuracy-unknown {
    base data-source-accuracy;
    description
      "The accuracy of the Power or Energy data is unknown.";
  }
  identity accuracy-unavailable {
    base accuracy-unknown;
    description
      "The Power or Energy data is not available for some reason,
       such as a sensor failure or a Component being powered off.";
  }
  identity accuracy-like-parent {
    base data-source-accuracy;
    description
      "The accuracy of the Power or Energy data is the same as the
       accuracy of the same data for the parent Energy Object. The
       parent Energy Object is found by following the 'parent' leaf
       of ietf-hardware up the containment tree towards the root,
       starting from the Component that this Energy Object
       describes (see source-component-id): it is the Energy Object
       of the first Component found that has one. This identity is
       useful for hierarchical Energy Objects where child objects
       inherit the accuracy characteristics. If there is no parent
       Energy Object, the accuracy is unknown, as for
       accuracy-unknown.";
    reference
      "RFC 8348: A YANG Data Model for Hardware Management
       RFC 6933: Entity MIB (Version 4)";
  }
  identity accuracy-estimated {
    base data-source-accuracy;
    description
      "The Power or Energy data is estimated, perhaps based on a
       model, history or calculation rather than a direct
       measurement.";
  }
  identity accuracy-static {
    base accuracy-estimated;
    description
      "The Power or Energy data is based on static data, such as
       manufacturer specifications, datasheet of typical Power values
       or nameplate ratings, rather than real-time measurements.";
  }
  identity accuracy-historic {
    base accuracy-estimated;
    description
      "The Power or Energy data is based on historical measurement
       data for this specific system and usage pattern.";
  }
  identity accuracy-learned {
    base accuracy-estimated;
    description
      "The Power or Energy data is based on a machine learning model
       prediction.";
  }
  identity accuracy-measured {
    base data-source-accuracy;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor.";
  }
  identity accuracy-measured-bronze {
    base accuracy-measured;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 30% OR |actual-sensor| <= 0.5";
  }
  identity accuracy-measured-bronze-1 {
    base accuracy-measured-bronze;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 30% OR |actual-sensor| <= 1";
  }  
  identity accuracy-measured-bronze-10 {
    base accuracy-measured-bronze;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 30% OR |actual-sensor| <= 10";
  }  
  identity accuracy-measured-bronze-100 {
    base accuracy-measured-bronze;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 30% OR |actual-sensor| <= 100";
  }  
  identity accuracy-measured-bronze-1000 {
    base accuracy-measured-bronze;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 30% OR |actual-sensor| <= 1000";
  }  
  identity accuracy-measured-silver {
    base accuracy-measured;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 10% OR |actual-sensor| <= 0.5";
  }  
  identity accuracy-measured-silver-1 {
    base accuracy-measured-silver;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 10% OR |actual-sensor| <= 1";
  }  
  identity accuracy-measured-silver-10 {
    base accuracy-measured-silver;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 10% OR |actual-sensor| <= 10";
  }  
  identity accuracy-measured-silver-100 {
    base accuracy-measured-silver;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 10% OR |actual-sensor| <= 100  ";
  }  
  identity accuracy-measured-silver-1000 {
    base accuracy-measured-silver;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 10% OR |actual-sensor| <= 1000";
  }  
  identity accuracy-measured-gold {
    base accuracy-measured;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 5% OR |actual-sensor| <= 0.5";
  }
  identity accuracy-measured-gold-1 {
    base accuracy-measured-gold;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 5% OR |actual-sensor| <= 1";
  }  
  identity accuracy-measured-gold-10 {
    base accuracy-measured-gold;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 5% OR |actual-sensor| <= 10";
  }  
  identity accuracy-measured-gold-100 {
    base accuracy-measured-gold;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 5% OR |actual-sensor| <= 100";
  }  
  identity accuracy-measured-gold-1000 {
    base accuracy-measured-gold;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 5% OR |actual-sensor| <= 1000";
  }  
  identity accuracy-measured-red {
    base accuracy-measured;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 2% OR |actual-sensor| <= 0.5";
  }
  identity accuracy-measured-red-1 {
    base accuracy-measured-red;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 2% OR |actual-sensor| <= 1";
  }  
  identity accuracy-measured-red-10 {
    base accuracy-measured-red;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 2% OR |actual-sensor| <= 10";
  }  
  identity accuracy-measured-red-100 {
    base accuracy-measured-red;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 2% OR |actual-sensor| <= 100";
  }  
  identity accuracy-measured-red-1000 {
    base accuracy-measured-red;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with precision and accuracy such that
       |actual-sensor| <= sensor * 2% OR |actual-sensor| <= 1000";
  }  
  identity accuracy-measured-ones {
    base accuracy-measured;
    description
      "The Power or Energy data is a direct, real-time measurement
       from a sensor with all digits valid, except trailing zeros.
       For example, a sensor reading of 12300 represents a sensor
       value between 12250 and 12350.";
  }
  
  typedef power-factor {
    type uint8 {
      range "0 .. 100";
    }
    default 100;
    description
      "The percent value of the Power Factor measurement.
       Leaf often omitted, implying 100%.";
  }

  identity power-state {
    description
      "Base identity for all possible Power States. This identity
       serves as the root for a hierarchy of Power States, allowing
       for extensibility while maintaining alignment with the IANA
       Power State Set Registry.";
    reference
      "IANA: Power State Set Registry:
       https://www.iana.org/assignments/power-state-sets/";
  }
  identity power-state-on {
    base power-state;
    description "full power on.";
    reference
      "IANA: Power State Set Registry (ieee1621-power-state-set):
       https://www.iana.org/assignments/power-state-sets/";
  }
  identity power-state-off {
    base power-state;
    description "power off.";
    reference
      "IANA: Power State Set Registry (ieee1621-power-state-set):
       https://www.iana.org/assignments/power-state-sets/";
  }
  identity power-state-sleep {
    base power-state;
    description "low-power state.";
    reference
      "IANA: Power State Set Registry (ieee1621-power-state-set):
       https://www.iana.org/assignments/power-state-sets/";
  }
  identity energy-relationship-type {
    description "Base identity for Energy Object relationships";
  }
  identity powered-by {
    base energy-relationship-type;
    description "Energy Object A is powered by Energy Object B";
  }
  identity powering {
    base energy-relationship-type;
    description "Energy Object A is powering Energy Object B";
  }
  identity metered-by {
    base energy-relationship-type;
    description "Energy Object A is metered by Energy Object B";
  }
  identity metering {
    base energy-relationship-type;
    description "Energy Object A is metering Energy Object B";
  }
  identity aggregated-by {
    base energy-relationship-type;
    description "Energy Object A is aggregated by Energy Object B";
  }
  identity aggregating {
    base energy-relationship-type;
    description "Energy Object A is aggregating Energy Object B";
  }
  identity enabled-by {
    base energy-relationship-type;
    description
      "Energy Object A is enabled by Energy Object B. B must be 
       operational for A to function correctly";
  }
  identity enabling {
    base energy-relationship-type;
    description
      "Energy Object A is enabling Energy Object B. A must be 
       operational for B to function correctly.
       The inverse relationship is 'enabled-by'.";
  }

  grouping power-values {
    description
      "A set of Power measurement values that are associated with an 
       Energy Object. 
       This grouping is defined so that other modules, for example
       a controller-side module collecting and aggregating Power
       data from devices, can reuse the same leaf definitions
       instead of redefining them.";
    container power {
      description
        "Container for Power measurement attributes.";
      
      leaf instantaneous-power-received {
        type uint64;
        units "milliwatts";
        mandatory false;
        description
          "The Power that the Energy Object receives right now,
           summed over all its Power Inlets. It includes the Power
           that the Energy Object uses itself and the Power that it
           converts, passes on, or stores, for example in a power
           supply or a charging battery. If the device can measure
           this value, it MUST report it.";
      }

      leaf instantaneous-power-provided {
        type uint64;
        units "milliwatts";
        mandatory false;
        description
          "The Power that the Energy Object provides right now to
           other Energy Objects, summed over all its Power Outlets,
           for example the output of a power supply, Power over
           Ethernet, or a discharging battery. The difference
           between the received and the provided Power is the
           Power that the Energy Object dissipates or stores. An
           Energy Object without Power Outlets does not report this
           leaf; otherwise, if the device can measure this value,
           it MUST report it.";
      }
      
      leaf nameplate-power {
        type uint32;
        units "watts";
        description
          "The Nameplate Power of the Energy Object: the maximum
           continuous Power the Energy Object is designed to consume
           or deliver, as specified by the manufacturer. For an
           Energy Object that provides Power, such as a power
           supply, it is the rated provided Power. It is a
           rated design value, not an expected operating value or an
           observed maximum, and does not change during operation.
           Used for power budget calculations and capacity
           planning.";
        reference
          "I-D.ietf-green-terminology: Terminology for Energy
           Efficiency Network Management";
      }
      
      leaf data-source-accuracy {
        type identityref {
          base data-source-accuracy;
        }
        default accuracy-like-parent;
        description
          "The accuracy of the Power data source. Indicates
           whether the data source is a direct measurement, an
           estimate, or unavailable and also the accuracy level of
           the data source. By default, the accuracy is inherited
           from the parent Energy Object (see accuracy-like-parent),
           facilitating hierarchical accuracy definitions without
           the need to specify accuracy at every level. An Energy
           Object without a parent Energy Object, such as the one
           at the top of the containment tree, SHOULD report this
           leaf explicitly. A module that reuses this grouping
           outside a device can refine the default, for example to
           accuracy-unknown. It applies to both the received and the
           provided Power; when their accuracy differs, it reports
           the accuracy of the less accurate of the two. This
           metadata is crucial for network management applications
           to assess the reliability and accuracy of the Power
           data.";
      }
      
      leaf power-factor {
        type power-factor;
        description
          "The percent value of the Power Factor measured at the
           Power Inlets of the Energy Object. This information is
           important for understanding the electrical
           characteristics of the Energy Object and for correctly
           interpreting the received Power data.";
      }
      leaf measurement-local {
        type boolean;
        description
          "Indicates whether the Power measurement is local (true) 
           or remote (false). A local measurement is taken 
           directly at the Energy Object, while a remote 
           measurement is collected from an external source. 
           This information can be useful for troubleshooting and 
           understanding the data source.";
      }
      container power-cap {
        presence
          "A Power Cap is enforced for this Energy Object. When this
           container is absent, no cap is enforced and the Nameplate
           Power is the upper limit.";
        description
          "Container for the Power Cap in effect for this Energy
           Object.";
        leaf limit {
          type uint64;
          units "milliwatts";
          mandatory true;
          description
            "The upper limit on the Power that this Energy Object
             receives, currently enforced: the Energy Object does
             not draw more Power than this limit, whether or not the
             cap is constraining it at this time (see 'limiting').
             It differs from the requested limit when the requested
             limit is outside the range that the Energy Object
             supports.";
        }
        leaf limiting {
          type boolean;
          description
            "True if the cap is currently constraining the Energy
             Object: without the cap, it would draw more Power than
             the limit, so its operation (for example, its clock
             frequency) is reduced to stay within the limit. False
             if the Energy Object would not draw more Power than the
             limit even without the cap, so the cap has no effect
             at this time. Absent if the device cannot determine
             whether the cap is constraining the Energy Object.";
        }
      }
    }
  }
  
  grouping energy-values {
    description
      "A set of Energy measurement values that are associated with an 
       Energy Object. 
       This grouping is defined so that other modules, for example
       a controller-side module collecting and aggregating Energy
       data from devices, can reuse the same leaf definitions
       instead of redefining them.";
    container energy {
      description
        "Container for Energy measurement attributes.";
      
      leaf total-energy-received {
        type yang:counter64;
        units "milliwatt-hours";
        description
          "The total cumulative Energy received by the Energy
           Object, in the same direction as
           instantaneous-power-received. This value is useful for
           tracking overall Energy usage over time for billing,
           reporting, or optimization purposes. If the device can
           measure this value, it MUST report it.
           Discontinuities in the value of this counter can occur
           at re-initialization of the management system and at
           other times as indicated by the value of
           discontinuity-time.";
      }

      leaf total-energy-provided {
        type yang:counter64;
        units "milliwatt-hours";
        description
          "The total cumulative Energy provided by the Energy
           Object to other Energy Objects, in the same direction
           as instantaneous-power-provided.
           This value is relevant for Energy Objects that provide
           Energy, such as power supplies, PoE switches,
           batteries, or renewable energy sources. An Energy Object
           without Power Outlets does not report this leaf;
           otherwise, if the device can measure this value, it MUST
           report it. Discontinuities in the value of this
           counter can occur at re-initialization of the
           management system and at other times as indicated by
           the value of discontinuity-time.";
      }

      leaf discontinuity-time {
        type yang:date-and-time;
        description
          "The time on the most recent occasion at which one or more
           of the Energy counters of this Energy Object
           (total-energy-received and total-energy-provided)
           suffered a discontinuity, for example when the Energy
           Object was created or its Energy measurement was reset.
           If no such discontinuity has occurred since the last
           re-initialization of the local management subsystem,
           then this leaf contains the time the local management
           subsystem re-initialized itself. If the device reports
           an Energy counter, it SHOULD report this leaf.";
      }
      leaf data-source-accuracy {
        type identityref {
          base data-source-accuracy;
        }
        default accuracy-like-parent;
        description
          "The accuracy of the Energy data source. Indicates
           whether the data source is a direct measurement, an
           estimate, or unavailable and also the accuracy level of
           the data source. By default, the accuracy is inherited
           from the parent Energy Object (see accuracy-like-parent),
           facilitating hierarchical accuracy definitions without
           the need to specify accuracy at every level. An Energy
           Object without a parent Energy Object, such as the one
           at the top of the containment tree, SHOULD report this
           leaf explicitly. A module that reuses this grouping
           outside a device can refine the default, for example to
           accuracy-unknown. It applies to both the received and the
           provided Energy; when their accuracy differs, it reports
           the accuracy of the less accurate of the two. This
           metadata is crucial for network management applications
           to assess the reliability and accuracy of the Energy
           data.";
      }
      leaf measurement-local {
        type boolean;
        description
          "Indicates whether the Energy measurement is local 
           (true) or remote (false). A local measurement is taken 
           directly at the Energy Object, while a remote 
           measurement is collected from an external source. 
           This information can be useful for troubleshooting and 
           understanding the data source.";
      }
    }
  }

  grouping certifications {
    description
      "The certifications that apply to an Energy Object. Defined
       as a separate grouping so that it can be reused independently
       of the Power and Energy values.";
    leaf-list certifications {
      type identityref {
        base ianaeo:certification-type;
      }
      description
        "List of certifications applicable to this Energy Object.
         If this list is empty, the Energy Object has no
         certifications.";
    }
  }

  grouping relationships {
    description
      "A set of relationships between an Energy Object and its peer 
       Energy Objects.
       A device uses this grouping to report relationships such as
       powering, powered-by, metering, metered-by, aggregating, 
       aggregated-by, enabling and enabled-by.  A controller uses 
       this grouping to represent the relationships collected from 
       devices. 
       This grouping is defined so that other modules, for example
       a controller-side module collecting relationships from
       devices, can reuse the same relationship structure instead
       of redefining it.";
    list relationship {
      key "type";
      description 
        "Relationships for this Energy Object.";
              
      leaf type {
        type identityref {
          base energy-relationship-type; 
          // powered-by, powering, metered-by, metering, etc.
        }
        description
          "The type of relationship this Energy Object has with 
           peer objects.";
      }
      
      list peer {
        key "id";
        description 
          "Multiple peers for this relationship type.";
        
        leaf id {
          type string;
          description 
            "The identifier of the peer Energy Object that this
             Energy Object is powering/powered-by/metering/
             metered-by, etc., preferably its Universally Unique
             Identifier (UUID). If the UUID is not known, another
             identifier MAY be used, together with human-readable
             details in the 'details' leaf.";
          reference
            "RFC 9562: Universally Unique IDentifiers (UUIDs)";
        }
        leaf details {
          type string;
          description 
            "Additional details about the relationship.";
        }
      }
    }
  }

  container energy-objects {
    config false;
    description
      "Energy Objects container for Power and Energy attributes.";
    
    list energy-object {
      key "id";
      description
        "Power and Energy entry for an Energy Object, indexed by 
         Energy Object id. Each entry contains the complete set of 
         Power and Energy attributes for a specific physical 
         component.";
        
      leaf id {
        type string;
        description
          "An identifier that uniquely identifies the Energy Object";
      }
      
      leaf source-component-id {
        type leafref {
          path "/hw:hardware/hw:component/hw:name";
        }
        description
          "Reference to the component name in the ietf-hardware 
           model. This leaf creates a direct semantic link between 
           the Power/Energy attributes and the physical component 
           they describe. The name is unique only within a device;
           for identification across devices, use the 'uuid' leaf
           of the referenced component.";
        reference
          "RFC 8348: A YANG Data Model for Hardware Management";
      }

      uses power-values;
      uses energy-values;
      uses certifications;

      container power-state {
        description
          "Container for Power State monitoring.";
        leaf oper {
          type identityref {
            base power-state;
          }
          description
            "The current operational Power State of this Component, 
             as reported by the device. The leaf reflects the actual 
             observed Power State.";
        }
      }
      
      uses relationships;
    }
  }
  
  container energy-control {
    description
      "Energy control configuration, mirroring monitored objects. 
       The operational tree ('list energy-object' in 
       /energy-objects) will typically contain a significantly 
       larger number of instances than the configuration tree here. 
       The configuration tree represents the administrator's intent 
       and is limited to explicitly provisioned entries.";
    container energy-objects {
      description
        "Configuration container for the list of administratively 
         provisioned Energy Objects.";
      list energy-object {
        key "id";
        description
          "Control entry for a specific Energy Object.";
        
        leaf id {
          type leafref {
          path "/energy-objects/energy-object/id";
          require-instance false;
        }
          description 
            "An identifier that uniquely identifies the Energy 
             Object.";
        }
        container power-state {
          description
            "Container for Power State management.";
          
          leaf admin {
            type identityref {
              base power-state;
            }
            description
              "The administratively requested Power State for this 
               Component. This leaf represents the management system 
               intended Power State. When the 'admin' and the 
               respective 'oper' YANG leaf values differ, a 
               transition toward the 'admin' Power State is in 
               progress. Absence of a configured value indicates that 
               the Component operates at its default Power State.";
          }

          leaf oper {
            type leafref {
              path "/energy-objects/energy-object/power-state/oper";
              require-instance false;
            }
            description
              "The current operational Power State of this Component, 
               as reported by the device. 
               References the corresponding operational Energy Object 
               instance in the monitoring tree.";
          }
        }

        container power-cap {
          description
            "Container for the Power Cap of this Energy Object.";
          leaf limit {
            type uint64;
            units "milliwatts";
            description
              "The administratively requested upper limit on the
               Power that this Energy Object may receive. The device
               enforces it by adjusting the operation of the Energy
               Object, for example by lowering its clock frequency.
               Absence of a configured value means that no cap is
               requested. If the requested limit is outside the
               range that the Energy Object supports, the device
               enforces the closest supported value, which is
               reported in the power-cap container in
               /energy-objects.";
          }
        }
      }
    }
  }
}


]]></sourcecode>
      <t>The IANA-maintained identities for certification types are defined in
the following module.</t>
      <sourcecode type="yang" markers="true" name="iana-power-and-energy@2026-11-01.yang"><![CDATA[
module iana-power-and-energy {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:iana-power-and-energy";
  prefix ianaeo;

  organization "IANA";
  contact
    "        Internet Assigned Numbers Authority

     Postal: ICANN
             12025 Waterfront Drive, Suite 300
             Los Angeles, CA  90094-2536
             United States of America

     Tel:    +1 310 301 5800
     E-Mail: iana@iana.org";

  description
    "IANA-defined identities for certification types of Energy
     Objects.

     The capitalized terms used in this module are defined in
     I-D.ietf-green-terminology.

     The latest revision of this YANG module can be obtained from
     the IANA website.

     Requests for new values should be made to IANA via
     email (iana@iana.org).

     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 (RFC 2119) (RFC 8174) when, and only when,
     they appear in all capitals, as shown here.
     
     Copyright (c) 2026 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).";

  reference
    "https://www.iana.org/assignments/yang-parameters";

  revision 2026-11-01 {
    description
      "Initial revision.";
    reference
      "RFC XXXX: Power and Energy YANG Module";
  }

  identity certification-type {
    description
      "Base identity for certification types applicable to Energy
       Objects. This identity serves as the root for a hierarchy of
       certification types, allowing for extensibility.";

    reference
      "Industry sustainability and energy efficiency certifications";
  }

  identity energy-star {
    base certification-type;
    description
      "ENERGY STAR certification for energy efficiency.";
    reference
      "https://www.energystar.gov/";
  }

  identity c80-plus{
    base certification-type;
    description
      "80 PLUS Power Supply Certification";
    reference
      "https://www.clearesult.com/80plus/";
  }

  identity epeat {
    base certification-type;
    description
      "Electronic Product Environmental Assessment Tool ratings 
       (Bronze/Silver/Gold).";
    reference
      "https://www.epeat.net/";
  }

  identity eu-energy-label {
    base certification-type;
    description
      "EU Energy Label: European efficiency ratings";
    reference
      "https://eprel.ec.europa.eu/screen/home";
  }

  identity cn-energy-label {
    base certification-type;
    description
      "CN Energy Label: China efficiency ratings";
    reference
      "https://www.energylabel.com.cn";
  }

  identity cqc{
    base certification-type;
    description
      "China Quality Certification for energy efficiency";
    reference
      "https://www.cqc.com.cn/";
  }

}
]]></sourcecode>
    </section>
    <section anchor="operational-considerations">
      <name>Operational Considerations</name>
      <t>Heterogeneous sensor capabilities across Components complicate Power
and Energy aggregation. Operators must use the data-source-accuracy
identities (e.g., accuracy-measured-bronze vs. accuracy-estimated) to
weight data reliability carefully before aggregating Power
(instantaneous-power-received and instantaneous-power-provided) and
Energy (total-energy-received and total-energy-provided) values to
avoid skewing Device Level Energy Efficiency (DLEE) metrics.</t>
      <t>The device reports the Power and Energy that each Energy Object
receives and provides, not a single consumption value. The consumption
of an Energy Object is its net value, received minus provided, which a
management system or a controller computes when needed. For a power
supply, this net value is its loss (see <xref target="psu-example"/>).</t>
      <t>For implementers familiar with <xref target="RFC7460"/>, the following table maps
its Power and Energy objects to this module. The values in <xref target="RFC7460"/>
are scaled by a unit multiplier, while this module uses fixed units;
the Energy objects of <xref target="RFC7460"/> cover a configured interval, while
the Energy counters of this module are cumulative; and the
discontinuity time of <xref target="RFC7460"/> is a sysUpTime value, while this
module reports a date and time.</t>
      <table>
        <name>Mapping of RFC 7460 Power and Energy Objects</name>
        <thead>
          <tr>
            <th align="left">RFC 7460 object</th>
            <th align="left">This module</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">eoPower</td>
            <td align="left">instantaneous-power-received minus instantaneous-power-provided</td>
          </tr>
          <tr>
            <td align="left">eoEnergyConsumed</td>
            <td align="left">total-energy-received</td>
          </tr>
          <tr>
            <td align="left">eoEnergyProvided</td>
            <td align="left">total-energy-provided</td>
          </tr>
          <tr>
            <td align="left">eoEnergyDiscontinuityTime</td>
            <td align="left">discontinuity-time</td>
          </tr>
        </tbody>
      </table>
      <t>The Energy counters are of type counter64 <xref target="RFC9911"/>. With a unit
of one milliwatt-hour, a counter64 wraps around only after about 18
billion MWh, which does not happen in practice. The risk is rather a
reset that goes unnoticed: an Energy counter can restart at times
other than the re-initialization of the management system, for
example when a power supply is hot-swapped, when a line card is
reinserted, or when the Energy measurement is reset. A client that
computes the Energy over a period from two readings of a counter
therefore needs to check the discontinuity-time leaf: if it has
changed between the two readings, the difference between them is not
valid. If the device does not report discontinuity-time, a decrease
between two consecutive readings reveals most resets and locates them
between the times at which the two readings were measured; with
YANG-Push <xref target="RFC8641"/>, these times are given by the observation
timestamp defined in <xref target="I-D.ietf-netconf-notif-envelope"/>. A reset
after which the counter exceeds its previous value before the next
reading still goes unnoticed.</t>
      <t>Operators might not always be interested in the accuracy of individual
Components; what matters is the accuracy at the device or domain
level. The accuracy-like-parent identity is introduced for this
purpose. The parent Energy Object is determined by the containment
tree <xref target="RFC6933"/>, which ietf-hardware <xref target="RFC8348"/> represents with the
parent leaf: starting from the Component of an Energy Object and
following the parent leaf up the containment tree towards the root,
the first Component that has an Energy Object provides the parent
Energy Object. The Energy Object at the top of the containment tree
has no parent, so its accuracy should be reported explicitly. A module
that reuses the power-values or energy-values groupings outside a
device, such as a controller-side module, can refine the default of
data-source-accuracy, for example to accuracy-unknown. From an
implementation point of view, to facilitate data collection and
aggregation at runtime and to avoid post-aggregation data confidence
interval issues, operators and implementers should use the
accuracy-like-parent identity as much as possible.</t>
      <t>YANG Push support eliminates device-side bucket storage by streaming
Energy telemetry directly to controller-side via subscriptions.
Operators must verify the 'yang-push' bundle is enabled and validate
push-max-operational limits accommodate all Component subscriptions,
preventing notification flooding while avoiding memory overhead on the
device.</t>
      <section anchor="hardware-component-identification">
        <name>Hardware Component Identification</name>
        <t>The GREEN YANG module relies on the ietf-hardware module <xref target="RFC8348"/>
for hardware component identification.  Among the three identifiers
that ietf-hardware provides for each component: 'name',
'physical-index', and 'uuid', only 'uuid' is intended to be
unique beyond a single device.
The 'name' leaf, while serving as the list key within a device,
is meaningful only in the context of that specific device.  The
'physical-index' leaf, where present, provides a mapping to the
legacy Entity MIB <xref target="RFC6933"/>, but its availability depends on
whether the entity-mib feature is supported.</t>
        <t>The 'source-component-id' leaf in this module is bound to the 'name'
leaf of the corresponding ietf-hardware component, since 'name' is
the list key and always present, whereas 'uuid' is optional in
<xref target="RFC8348"/>. To correlate Energy Objects across devices, management
systems, and administrative domains without relying on device-local
naming conventions, a client uses the 'uuid' leaf <xref target="RFC9562"/> of the
referenced component.</t>
      </section>
      <section anchor="measurement-accuracy-and-data-source-classification">
        <name>Measurement Accuracy and Data Source Classification</name>
        <t>Power and Energy metrics may originate from a wide range of sources and
estimation methods, each with different levels of reliability. These
include direct sensor measurements, manufacturer-provided
specifications, historical observations, and predictive models. Without
explicit characterization of data quality, comparisons and aggregations
may be misleading. The GREEN YANG data model therefore requires all
Power and Energy values to be associated with an accuracy
classification.</t>
        <t>The model defines the following primary accuracy categories using YANG
identities:</t>
        <ul spacing="normal">
          <li>
            <t>Unknown Accuracy: Data accuracy cannot be determined, or measurements
are unavailable due to sensor failures, powered-off Components, or
other operational constraints.</t>
          </li>
          <li>
            <t>Estimated Data: Values derived through indirect methods:
            </t>
            <ul spacing="normal">
              <li>
                <t>Static estimates: From manufacturer datasheets, nameplate ratings
(critical for legacy devices, as described in the "Incremental
Application of the GREEN Framework" use case in
<xref target="I-D.ietf-green-use-cases"/>)
                </t>
                <ul spacing="normal">
                  <li>
                    <t>Identity: <tt>accuracy-static</tt></t>
                  </li>
                </ul>
              </li>
              <li>
                <t>Historic estimates: Based on prior measurements of this specific
system under similar conditions
                </t>
                <ul spacing="normal">
                  <li>
                    <t>Identity: <tt>accuracy-historic</tt></t>
                  </li>
                </ul>
              </li>
              <li>
                <t>Learned estimates: Generated by machine learning models predicting
consumption from workload patterns (see the "Energy-Efficient
Management of Distributed AI Training Workloads" use case in
<xref target="I-D.ietf-green-use-cases"/>)
                </t>
                <ul spacing="normal">
                  <li>
                    <t>Identity: <tt>accuracy-learned</tt></t>
                  </li>
                </ul>
              </li>
            </ul>
          </li>
          <li>
            <t>Measured Data: Direct, real-time sensor measurements with quantified
precision:
            </t>
            <ul spacing="normal">
              <li>
                <t>Bronze: +/-30% accuracy for typical values.</t>
              </li>
              <li>
                <t>Silver: +/-10% accuracy for typical values.</t>
              </li>
              <li>
                <t>Gold: +/-5% accuracy for typical values.</t>
              </li>
              <li>
                <t>Red: +/-2% accuracy for typical values.</t>
              </li>
              <li>
                <t>Ones: All digits are valid, except trailing zeros.</t>
              </li>
            </ul>
          </li>
        </ul>
        <t>Percentage-based accuracy fails for small values. For example, +/-5% of
100 mW is only 5 mW, which may be smaller than sensor noise. Industry
standards (IEC 62053, IEC 61850-7-4) address this by specifying:
Accuracy = MAX(percentage_error, absolute_threshold)</t>
        <t>The absolute threshold suffixes (<tt>-1</tt>, <tt>-10</tt>, <tt>-100</tt>, <tt>-1000</tt>) are
expressed in the unit of the qualified value: milliwatts for Power,
and milliwatt-hours for Energy. For example, <tt>-10</tt> means +/-10
milliwatts for a Power value.</t>
        <t>Example - A sensor with <tt>accuracy-measured-gold-10</tt> reports:</t>
        <ul spacing="normal">
          <li>
            <t>16.25 W -&gt; actual value between 15.4375 W and 17.0625 W
(5% = 0.8125 W &gt; 0.010 W threshold)</t>
          </li>
          <li>
            <t>0.15 W -&gt; actual value between 0.140 W and 0.160 W
(5% = 0.0075 W &lt; 0.010 W threshold, so +/-10 mW applies)</t>
          </li>
        </ul>
        <t>Explicit accuracy reporting enables:</t>
        <ul spacing="normal">
          <li>
            <t>Weighted aggregation: High-precision measurements carry appropriate
weight when calculating network-wide Energy consumption</t>
          </li>
          <li>
            <t>Upgrade prioritization: Identify devices with low-accuracy reporting
for sensor upgrades or replacement</t>
          </li>
          <li>
            <t>Compliance validation: Automated verification against regulatory
thresholds requiring specific measurement precision</t>
          </li>
          <li>
            <t>Double-accounting prevention: Understand when PDU-level measurements
(+/-2%) should override device estimates (+/-30%) to avoid counting
the same Energy twice (see the "Double Accounting" use case in
<xref target="I-D.ietf-green-use-cases"/>)</t>
          </li>
          <li>
            <t>Cross-domain correlation: Map accuracy expectations when integrating
with external systems like 3GPP energy KPIs (see the "Consideration
of other domains for obtention of end-to-end metrics" use case in
<xref target="I-D.ietf-green-use-cases"/>)</t>
          </li>
        </ul>
        <t>The accuracy hierarchy uses YANG identities for extensibility, allowing
vendors to define manufacturer-specific accuracy classes while
maintaining interoperability through standardized base types.</t>
      </section>
      <section anchor="industry-standard-certifications">
        <name>Industry-Standard Certifications</name>
        <t>Energy Efficiency certifications issued by recognized testing
organizations provide standardized benchmarks for the expected
performance of equipment and Components. These certifications are
typically based on controlled laboratory measurements and formal
evaluation procedures. The GREEN YANG data model supports reporting of
such certifications in order to complement operational measurement data.</t>
        <t>Common Certifications:</t>
        <ul spacing="normal">
          <li>
            <t>80 PLUS (Power Supply Units): Bronze/Silver/Gold/Platinum/Titanium
tiers based on efficiency at 20%/50%/100% load</t>
          </li>
          <li>
            <t>ENERGY STAR: Government-backed program certifying energy-efficient
products</t>
          </li>
          <li>
            <t>EPEAT: Electronic Product Environmental Assessment Tool ratings
(Bronze/Silver/Gold)</t>
          </li>
          <li>
            <t>EU Energy Label: European efficiency ratings</t>
          </li>
          <li>
            <t>CN Energy Label: China efficiency ratings</t>
          </li>
          <li>
            <t>CQC: China Quality Certification for energy efficiency</t>
          </li>
        </ul>
        <t>Additional certification schemes may be supported through extensible
identities.</t>
        <t>Certification data and measurement accuracy serve complementary
functions within the model.</t>
        <t>Certification information describes the verified design-time efficiency
characteristics of a device or Component, as established through
independent testing. Measurement accuracy describes the precision and
reliability of reported operational data obtained from sensors or
estimation mechanisms.</t>
        <t>Key differences include:</t>
        <ul spacing="normal">
          <li>
            <t>Certification is typically applied at manufacturing time and remains
stable throughout the product lifecycle.</t>
          </li>
          <li>
            <t>Measurement accuracy may vary over time due to calibration,
environmental conditions, or sensor degradation.</t>
          </li>
          <li>
            <t>Certification is generally associated with discrete Components,
such as power supply units.</t>
          </li>
          <li>
            <t>Measurement accuracy applies to individual metrics at Component,
subsystem, or system level.</t>
          </li>
        </ul>
        <t>Both types of information may be reported simultaneously for the same
Energy Object.</t>
        <t>Example: A power supply might have:</t>
        <ul spacing="normal">
          <li>
            <t>Certification: <tt>c80-plus</tt>
(80 PLUS certified; at the Platinum level, &gt;=92% efficient at 50%
load, independently verified. The identity does not convey the
level.)</t>
          </li>
          <li>
            <t>Measurement Accuracy: <tt>accuracy-measured-silver</tt>
(+/-10% sensor precision on real-time Power readings)</t>
          </li>
        </ul>
        <t>The certification tells operators that the Energy Object (for example,
a power supply unit) is designed to be efficient; the measurement
accuracy tells them how precisely they can monitor its actual
performance.</t>
      </section>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <t>Note to the RFC Editor: please remove this section and the reference
to <xref target="RFC7942"/> before publication.</t>
      <t>Arrcus implemented the Power-related YANG leaves of
draft-ietf-green-power-and-energy-yang-05 in its ArcOS software,
exported with YANG-Push over UDP-based Transport for Configured
Subscriptions <xref target="I-D.ietf-netconf-udp-notif"/>.</t>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This section is modeled after the template described in Section 3.7.1
of <xref target="RFC9907"/>.</t>
      <t>The Power and Energy YANG module defines a data model that is designed
to be accessed via YANG-based management protocols, such as NETCONF
<xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. These YANG-based management
protocols (1) have to use a secure transport layer (e.g., SSH
<xref target="RFC4252"/>, TLS <xref target="RFC9846"/>, and QUIC <xref target="RFC9000"/>) and (2) have to use
mutual authentication.</t>
      <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/>
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.</t>
      <t>There are two writable data nodes defined in this YANG module that
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:</t>
      <ul spacing="normal">
        <li>
          <t>/energy-control/energy-objects/energy-object/power-state/admin:
Unauthorized write access to this leaf allows an attacker to change
the administratively requested Power State of an Energy Object.
Depending on the target device or Component, this could be used to
power down critical network infrastructure (resulting in denial of
service), force a Component into a state that damages hardware, or
mask an ongoing attack by cycling Power States to disrupt
monitoring. Access to this data node <bcp14>SHOULD</bcp14> be limited to
authorized administrators via NACM.</t>
        </li>
        <li>
          <t>/energy-control/energy-objects/energy-object/power-cap/limit:
Unauthorized write access to this leaf allows an attacker to set a
very low Power Cap on an Energy Object, degrading or disrupting its
operation (resulting in denial of service), or to remove a cap that
protects the power budget of a site. Access to this data node <bcp14>SHOULD</bcp14>
be limited to authorized administrators via NACM.</t>
        </li>
      </ul>
      <t>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:</t>
      <ul spacing="normal">
        <li>
          <t>/energy-objects/energy-object/power and
/energy-objects/energy-object/energy: These subtrees expose
real-time and cumulative Power and Energy consumption for
individual hardware components. Fine-grained, time-correlated
Power/Energy telemetry can reveal operational patterns, such as
workload levels, traffic volume, or usage schedules, of a device
or of the network behind it. In some environments, this
information could be leveraged as a side channel to infer
sensitive operational or business information (e.g., data center
utilization, capacity, or customer activity patterns).</t>
        </li>
        <li>
          <t>/energy-objects/energy-object/relationship: This list exposes
relationships (e.g., powered-by, powering, metered-by) and UUIDs
between Energy Objects, which can reveal the physical and logical
power topology of a site. Disclosure of this information could
assist an attacker in identifying high-value targets (e.g., shared
power infrastructure whose disruption has a broad impact) or in
correlating Energy Objects across administrative domains.</t>
        </li>
      </ul>
      <t>This document does not define any RPC operations or YANG
notifications.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document requests IANA to perform the following actions.</t>
      <section anchor="yang-module-name-and-uri-registry">
        <name>YANG Module Name and URI Registry</name>
        <t>IANA is requested to register the following URIs in the "IETF XML
Registry" <xref target="RFC3688"/>.</t>
        <table>
          <name>IETF URI Registry: ietf-power-and-energy</name>
          <thead>
            <tr>
              <th align="left">Field</th>
              <th align="left">Value</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">URI</td>
              <td align="left">urn:ietf:params:xml:ns:yang:ietf-power-and-energy</td>
            </tr>
            <tr>
              <td align="left">Registrant Contact</td>
              <td align="left">The IESG</td>
            </tr>
            <tr>
              <td align="left">XML</td>
              <td align="left">N/A; the requested URI is an XML namespace.</td>
            </tr>
          </tbody>
        </table>
        <table>
          <name>IETF URI Registry: iana-power-and-energy</name>
          <thead>
            <tr>
              <th align="left">Field</th>
              <th align="left">Value</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">URI</td>
              <td align="left">urn:ietf:params:xml:ns:yang:iana-power-and-energy</td>
            </tr>
            <tr>
              <td align="left">Registrant Contact</td>
              <td align="left">The IESG</td>
            </tr>
            <tr>
              <td align="left">XML</td>
              <td align="left">N/A; the requested URI is an XML namespace.</td>
            </tr>
          </tbody>
        </table>
        <t>IANA is also requested to register the following YANG modules in the
"YANG Module Names" registry <xref target="RFC6020"/> <xref target="RFC9890"/> within the "YANG
Parameters" registry group.</t>
        <table>
          <name>IETF YANG Module Name Registry: ietf-power-and-energy</name>
          <thead>
            <tr>
              <th align="left">Field</th>
              <th align="left">Value</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Name</td>
              <td align="left">ietf-power-and-energy</td>
            </tr>
            <tr>
              <td align="left">Maintained by IANA?</td>
              <td align="left">N</td>
            </tr>
            <tr>
              <td align="left">Namespace</td>
              <td align="left">urn:ietf:params:xml:ns:yang:ietf-power-and-energy</td>
            </tr>
            <tr>
              <td align="left">Prefix</td>
              <td align="left">eo</td>
            </tr>
            <tr>
              <td align="left">Reference</td>
              <td align="left">RFC XXXX</td>
            </tr>
          </tbody>
        </table>
        <table>
          <name>IETF YANG Module Name Registry: iana-power-and-energy</name>
          <thead>
            <tr>
              <th align="left">Field</th>
              <th align="left">Value</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Name</td>
              <td align="left">iana-power-and-energy</td>
            </tr>
            <tr>
              <td align="left">Maintained by IANA?</td>
              <td align="left">Y</td>
            </tr>
            <tr>
              <td align="left">Namespace</td>
              <td align="left">urn:ietf:params:xml:ns:yang:iana-power-and-energy</td>
            </tr>
            <tr>
              <td align="left">Prefix</td>
              <td align="left">ianaeo</td>
            </tr>
            <tr>
              <td align="left">Reference</td>
              <td align="left">RFC XXXX</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="accelerator-class">
        <name>Accelerator Hardware Class</name>
        <t>IANA is requested to add the following enumeration to the
IANAPhysicalClass textual convention in the IANA-maintained
IANA-ENTITY-MIB module <xref target="RFC6933"/>:</t>
        <artwork><![CDATA[
   accelerator(TBD1)   -- e.g., GPU, TPU, NPU, or FPGA card
]]></artwork>
        <t>As the iana-hardware YANG module reflects IANA-ENTITY-MIB <xref target="RFC8348"/>,
IANA is also requested to add the following identity to the
iana-hardware YANG module, with a new revision statement:</t>
        <artwork><![CDATA[
   identity accelerator {
     base hardware-class;
     description
       "This identity is applicable if the hardware class is some
        sort of hardware accelerator, such as a Graphics Processing
        Unit (GPU), a Tensor Processing Unit (TPU), a Neural
        Processing Unit (NPU), or an FPGA-based accelerator card.";
     reference
       "RFC XXXX: Power and Energy YANG Module";
   }
]]></artwork>
        <t>Note to IANA: the value 16, the next unassigned IANAPhysicalClass
value, is suggested for TBD1.</t>
      </section>
      <section anchor="power-and-energy-certification-types-registry">
        <name>Power and Energy Certification Types Registry</name>
        <t>IANA is requested to create a new registry named
"Power and Energy Certification Types" within the "Power and Energy"
registry group.</t>
        <t>This document defines the initial version of the IANA-maintained
<tt>certification-type</tt> identity in the <tt>iana-power-and-energy</tt> YANG
module. The registry assigns string identity names for power and energy
efficiency certification types, for use as identityref values in
"ietf-power-and-energy" YANG module. The registered value is the
unqualified identity name (e.g., energy-star or c80-plus). No
numeric code points are assigned by this registry. Registry Template is
as follows.</t>
        <table>
          <name>IETF Power and Energy Certification Types Registry</name>
          <thead>
            <tr>
              <th align="left">Field</th>
              <th align="left">Value</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Registry Name</td>
              <td align="left">Power and Energy Certification Types</td>
            </tr>
            <tr>
              <td align="left">Reference</td>
              <td align="left">RFC XXXX</td>
            </tr>
            <tr>
              <td align="left">Registration Procedure</td>
              <td align="left">Expert Review <xref target="RFC8126"/></td>
            </tr>
            <tr>
              <td align="left">Available Values</td>
              <td align="left">Unqualified identity names as strings</td>
            </tr>
          </tbody>
        </table>
        <table>
          <name>Initial Registries</name>
          <thead>
            <tr>
              <th align="left">Identity Name</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">c80-plus</td>
              <td align="left">80 PLUS Power Supply Certification</td>
              <td align="left">RFC XXXX</td>
            </tr>
            <tr>
              <td align="left">energy-star</td>
              <td align="left">ENERGY STAR certification</td>
              <td align="left">RFC XXXX</td>
            </tr>
            <tr>
              <td align="left">epeat</td>
              <td align="left">Electronic Product Environmental Assessment Tool ratings</td>
              <td align="left">RFC XXXX</td>
            </tr>
            <tr>
              <td align="left">eu-energy-label</td>
              <td align="left">EU Energy Label: European efficiency ratings</td>
              <td align="left">RFC XXXX</td>
            </tr>
            <tr>
              <td align="left">cn-energy-label</td>
              <td align="left">CN Energy Label: China efficiency ratings</td>
              <td align="left">RFC XXXX</td>
            </tr>
            <tr>
              <td align="left">cqc</td>
              <td align="left">China Quality Certification for energy efficiency</td>
              <td align="left">RFC XXXX</td>
            </tr>
          </tbody>
        </table>
        <t>New entries to "Power and Energy Certification Types" registry require
Expert Review <xref target="RFC8126"/>. The Designated Expert(s) should verify that:</t>
        <ul spacing="normal">
          <li>
            <t>The certification is issued by a recognized and independent
standards body, testing laboratory, regulatory authority, or
equivalent organization.</t>
          </li>
          <li>
            <t>The certification has a stable, publicly accessible reference.</t>
          </li>
          <li>
            <t>The proposed identity name <bcp14>SHOULD</bcp14> be a short mnemonic derived
from the official certification name.</t>
          </li>
        </ul>
        <t>When a new certification type is added to the registry, a new
<tt>identity</tt> statement <bcp14>MUST</bcp14> be added to the <tt>iana-power-and-energy</tt> YANG
module. The following substatements to the <tt>identity</tt> statement <bcp14>MUST</bcp14> be
defined:</t>
        <ul spacing="normal">
          <li>
            <t><tt>base</tt>: <bcp14>MUST</bcp14> contain the value <tt>certification-type</tt>.</t>
          </li>
          <li>
            <t><tt>status</tt>: Include only if a registration has been deprecated (use the
value <tt>deprecated</tt>) or obsoleted (use the value <tt>obsolete</tt>).</t>
          </li>
          <li>
            <t><tt>description</tt>: <bcp14>MUST</bcp14> include the full name of the certification
program and a brief description of its energy efficiency scope.
Lines <bcp14>MUST NOT</bcp14> exceed 72 characters.</t>
          </li>
          <li>
            <t><tt>reference</tt>: <bcp14>MUST</bcp14> include a stable URI to the certification program's
official documentation or registry.</t>
          </li>
        </ul>
        <t>Unassigned or reserved values <bcp14>MUST NOT</bcp14> be present in the module.</t>
        <t>When the "Power and Energy Certification Types" registry is updated
with a new entry, a corresponding new <tt>identity</tt> statement <bcp14>MUST</bcp14> be
added to the <tt>iana-power-and-energy</tt> YANG module, and a new revision
statement <bcp14>MUST</bcp14> be added in front of the existing revision statements.</t>
        <t>IANA is requested to add the following note to the "Power and Energy
Certification Types" registry:</t>
        <t>Certification types <bcp14>MUST NOT</bcp14> be directly added to the
iana-power-and-energy YANG module. They <bcp14>MUST</bcp14> instead be added to the
"Power and Energy Certification Types" registry. When this registry is
updated, the iana-power-and-energy YANG module <bcp14>MUST</bcp14> be updated as
defined in RFC XXXX.</t>
      </section>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>This work has benefited from the regular discussions on the GREEN
Design Meetings. The authors wish to thank the WG chairs, Rob Wilton
and Diego Lopez, for organizing the recurring calls and progressing
the work. The authors also wish to thank Rob Wilton, Diego Lopez,
Tony Li, Per Andersson, Qin Wu, Chih-Tsung Huang, Alex Huang Feng,
and Amanda Baber for their helpful comments and reviews of this
document.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC7950" target="https://datatracker.ietf.org/doc/html/rfc7950">
          <front>
            <title>The YANG 1.1 Data Modeling Language</title>
            <author>
              <organization/>
            </author>
            <date year="2016" month="August"/>
          </front>
        </reference>
        <reference anchor="RFC8340" target="https://datatracker.ietf.org/doc/html/rfc8340">
          <front>
            <title>YANG Tree Diagrams</title>
            <author>
              <organization/>
            </author>
            <date year="2018" month="March"/>
          </front>
        </reference>
        <reference anchor="RFC6241" target="https://datatracker.ietf.org/doc/html/rfc6241">
          <front>
            <title>Network Configuration Protocol (NETCONF)</title>
            <author>
              <organization/>
            </author>
            <date year="2011" month="June"/>
          </front>
        </reference>
        <reference anchor="RFC8040" target="https://datatracker.ietf.org/doc/html/rfc8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author>
              <organization/>
            </author>
            <date year="2017" month="June"/>
          </front>
        </reference>
        <reference anchor="RFC4252" target="https://datatracker.ietf.org/doc/html/rfc4252">
          <front>
            <title>The Secure Shell (SSH) Authentication Protocol</title>
            <author>
              <organization/>
            </author>
            <date year="2006" month="January"/>
          </front>
        </reference>
        <reference anchor="RFC9846" target="https://datatracker.ietf.org/doc/html/rfc9846">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author>
              <organization/>
            </author>
            <date year="2026" month="July"/>
          </front>
        </reference>
        <reference anchor="RFC9000" target="https://datatracker.ietf.org/doc/html/rfc9000">
          <front>
            <title>QUIC - A UDP-Based Multiplexed and Secure Transport</title>
            <author>
              <organization/>
            </author>
            <date year="2021" month="May"/>
          </front>
        </reference>
        <reference anchor="RFC8341" target="https://datatracker.ietf.org/doc/html/rfc8341">
          <front>
            <title>Network Configuration Access Control Model</title>
            <author>
              <organization/>
            </author>
            <date year="2018" month="March"/>
          </front>
        </reference>
        <reference anchor="RFC3688" target="https://datatracker.ietf.org/doc/html/rfc3688">
          <front>
            <title>The IETF XML Registry</title>
            <author>
              <organization/>
            </author>
            <date year="2004" month="January"/>
          </front>
        </reference>
        <reference anchor="RFC6020" target="https://datatracker.ietf.org/doc/html/rfc6020">
          <front>
            <title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
            <author>
              <organization/>
            </author>
            <date year="2010" month="October"/>
          </front>
        </reference>
        <reference anchor="RFC9890" target="https://datatracker.ietf.org/doc/html/rfc9890">
          <front>
            <title>An Update to YANG Module Names Registration</title>
            <author>
              <organization/>
            </author>
            <date year="2025" month="October"/>
          </front>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>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.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>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.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="I-D.ietf-green-terminology">
          <front>
            <title>Terminology for Energy Efficiency Network Management</title>
            <author fullname="Gen Chen" initials="G." surname="Chen">
              <organization>Huawei</organization>
            </author>
            <author fullname="Mohamed Boucadair" initials="M." surname="Boucadair">
              <organization>Orange</organization>
            </author>
            <author fullname="Qin Wu" initials="Q." surname="Wu">
              <organization>Huawei</organization>
            </author>
            <author fullname="Luis M. Contreras" initials="L. M." surname="Contreras">
              <organization>Telefonica</organization>
            </author>
            <author fullname="Marisol Palmero" initials="M. P." surname="Palmero">
              <organization>Individual</organization>
            </author>
            <date day="30" month="October" year="2026"/>
            <abstract>
              <t>   Energy-efficient network management is primarily meant to enhance
   conventional network management with energy-related management
   capabilities that optimize overall network energy consumption.  To
   that aim, specific features and capabilities are required to control
   (and thus optimize) the energy use of involved network elements and
   their components.

   This document defines a set of key terms used within the IETF when
   discussing energy efficiency in network management.  Such reference
   document helps framing discussion and agreeing upon a set of main
   concepts in this area.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-green-terminology-03"/>
        </reference>
        <reference anchor="RFC8348">
          <front>
            <title>A YANG Data Model for Hardware Management</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="J. Dong" initials="J." surname="Dong"/>
            <author fullname="D. Romascanu" initials="D." surname="Romascanu"/>
            <date month="March" year="2018"/>
            <abstract>
              <t>This document defines a YANG data model for the management of hardware on a single server.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8348"/>
          <seriesInfo name="DOI" value="10.17487/RFC8348"/>
        </reference>
        <reference anchor="RFC6933">
          <front>
            <title>Entity MIB (Version 4)</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="D. Romascanu" initials="D." surname="Romascanu"/>
            <author fullname="J. Quittek" initials="J." surname="Quittek"/>
            <author fullname="M. Chandramouli" initials="M." surname="Chandramouli"/>
            <date month="May" year="2013"/>
            <abstract>
              <t>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.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6933"/>
          <seriesInfo name="DOI" value="10.17487/RFC6933"/>
        </reference>
        <reference anchor="RFC9911">
          <front>
            <title>Common YANG Data Types</title>
            <author fullname="J. Schönwälder" initials="J." role="editor" surname="Schönwälder"/>
            <date month="December" year="2025"/>
            <abstract>
              <t>This document defines a collection of common data types to be used with the YANG data modeling language. It includes several new type definitions and obsoletes RFC 6991.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9911"/>
          <seriesInfo name="DOI" value="10.17487/RFC9911"/>
        </reference>
        <reference anchor="RFC9562">
          <front>
            <title>Universally Unique IDentifiers (UUIDs)</title>
            <author fullname="K. Davis" initials="K." surname="Davis"/>
            <author fullname="B. Peabody" initials="B." surname="Peabody"/>
            <author fullname="P. Leach" initials="P." surname="Leach"/>
            <date month="May" year="2024"/>
            <abstract>
              <t>This specification defines UUIDs (Universally Unique IDentifiers) --
also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform
Resource Name namespace for UUIDs. A UUID is 128 bits long and is
intended to guarantee uniqueness across space and time. UUIDs were
originally used in the Apollo Network Computing System (NCS), later
in the Open Software Foundation's (OSF's) Distributed Computing
Environment (DCE), and then in Microsoft Windows platforms.</t>
              <t>This specification is derived from the OSF DCE specification with the
kind permission of the OSF (now known as "The Open Group"). Information from earlier versions of the OSF DCE specification have
been incorporated into this document. This document obsoletes RFC
4122.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9562"/>
          <seriesInfo name="DOI" value="10.17487/RFC9562"/>
        </reference>
        <reference anchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t>Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t>To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t>This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC9907" target="https://datatracker.ietf.org/doc/html/rfc9907">
          <front>
            <title>Guidelines for Authors and Reviewers of Documents Containing YANG Data Models</title>
            <author>
              <organization/>
            </author>
            <date year="2026" month="March"/>
          </front>
        </reference>
        <reference anchor="I-D.ietf-green-use-cases">
          <front>
            <title>Use Cases for Energy Efficiency Management</title>
            <author fullname="Emile Stephan" initials="E." surname="Stephan">
              <organization>Orange</organization>
            </author>
            <author fullname="Marisol Palmero" initials="M. P." surname="Palmero">
              <organization>Individual</organization>
            </author>
            <author fullname="Benoît Claise" initials="B." surname="Claise">
              <organization>Huawei</organization>
            </author>
            <author fullname="Qin Wu" initials="Q." surname="Wu">
              <organization>Huawei</organization>
            </author>
            <author fullname="Luis M. Contreras" initials="L. M." surname="Contreras">
              <organization>Telefonica</organization>
            </author>
            <author fullname="Carlos J. Bernardos" initials="C. J." surname="Bernardos">
              <organization>Universidad Carlos III de Madrid</organization>
            </author>
            <author fullname="Xinyu Chen" initials="X." surname="Chen">
              <organization>China Mobile</organization>
            </author>
            <date day="7" month="August" year="2026"/>
            <abstract>
              <t>   This document groups use cases for Energy efficiency Management of
   network devices.

   Discussion Venues

   Source of this draft and an issue tracker can be found at
   https://github.com/emile22/draft-ietf-green-use-cases

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-green-use-cases-02"/>
        </reference>
        <reference anchor="I-D.ietf-green-framework">
          <front>
            <title>Framework for Energy Efficiency Management</title>
            <author fullname="Benoît Claise" initials="B." surname="Claise">
         </author>
            <author fullname="Luis M. Contreras" initials="L. M." surname="Contreras">
              <organization>Telefonica</organization>
            </author>
            <author fullname="Jan Lindblad" initials="J." surname="Lindblad">
              <organization>All For Eco</organization>
            </author>
            <author fullname="Marisol Palmero" initials="M. P." surname="Palmero">
              <organization>Independent</organization>
            </author>
            <author fullname="Emile Stephan" initials="E." surname="Stephan">
              <organization>Orange</organization>
            </author>
            <author fullname="Qin Wu" initials="Q." surname="Wu">
              <organization>Huawei</organization>
            </author>
            <date day="2" month="November" year="2026"/>
            <abstract>
              <t>   Recognizing the urgent need for energy efficiency, this document
   specifies a management framework focused on networks, devices and
   device components within, or connected to, interconnected systems.
   The framework aims to enable energy usage optimization, based on the
   network condition while achieving the network's functional and
   performance requirements (e.g., improving overall network
   utilization) and also ensure interoperability across diverse systems.
   Leveraging data from existing use cases, it delivers actionable
   metrics to support effective energy management and informed decision-
   making.  Furthermore, the framework defines mechanisms for
   representing and organizing timestamped telemetry data using YANG
   data models and metadata, enabling transparent and reliable
   monitoring.  This structured approach facilitates improved energy
   efficiency through consistent energy management practices.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-green-framework-03"/>
        </reference>
        <reference anchor="RFC7577">
          <front>
            <title>Definition of Managed Objects for Battery Monitoring</title>
            <author fullname="J. Quittek" initials="J." surname="Quittek"/>
            <author fullname="R. Winter" initials="R." surname="Winter"/>
            <author fullname="T. Dietz" initials="T." surname="Dietz"/>
            <date month="July" year="2015"/>
            <abstract>
              <t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines managed objects that provide information on the status of batteries in managed devices.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7577"/>
          <seriesInfo name="DOI" value="10.17487/RFC7577"/>
        </reference>
        <reference anchor="RFC8342">
          <front>
            <title>Network Management Datastore Architecture (NMDA)</title>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/>
            <author fullname="P. Shafer" initials="P." surname="Shafer"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="R. Wilton" initials="R." surname="Wilton"/>
            <date month="March" year="2018"/>
            <abstract>
              <t>Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8342"/>
          <seriesInfo name="DOI" value="10.17487/RFC8342"/>
        </reference>
        <reference anchor="RFC7460">
          <front>
            <title>Monitoring and Control MIB for Power and Energy</title>
            <author fullname="M. Chandramouli" initials="M." surname="Chandramouli"/>
            <author fullname="B. Claise" initials="B." surname="Claise"/>
            <author fullname="B. Schoening" initials="B." surname="Schoening"/>
            <author fullname="J. Quittek" initials="J." surname="Quittek"/>
            <author fullname="T. Dietz" initials="T." surname="Dietz"/>
            <date month="March" year="2015"/>
            <abstract>
              <t>This document defines a subset of the Management Information Base (MIB) for power and energy monitoring of devices.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7460"/>
          <seriesInfo name="DOI" value="10.17487/RFC7460"/>
        </reference>
        <reference anchor="RFC8641">
          <front>
            <title>Subscription to YANG Notifications for Datastore Updates</title>
            <author fullname="A. Clemm" initials="A." surname="Clemm"/>
            <author fullname="E. Voit" initials="E." surname="Voit"/>
            <date month="September" year="2019"/>
            <abstract>
              <t>This document describes a mechanism that allows subscriber applications to request a continuous and customized stream of updates from a YANG datastore. Providing such visibility into updates enables new capabilities based on the remote mirroring and monitoring of configuration and operational state.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8641"/>
          <seriesInfo name="DOI" value="10.17487/RFC8641"/>
        </reference>
        <reference anchor="I-D.ietf-netconf-notif-envelope">
          <front>
            <title>Extensible YANG Model for YANG-Push Notifications</title>
            <author fullname="Alex Huang Feng" initials="A. H." surname="Feng">
              <organization>Deutsche Telekom</organization>
            </author>
            <author fullname="Pierre Francois" initials="P." surname="Francois">
              <organization>INSA-Lyon</organization>
            </author>
            <author fullname="Thomas Graf" initials="T." surname="Graf">
              <organization>Swisscom</organization>
            </author>
            <author fullname="Benoît Claise" initials="B." surname="Claise">
              <organization>Everything OPS &amp; Arrcus</organization>
            </author>
            <date day="31" month="October" year="2026"/>
            <abstract>
              <t>   This document defines a new extensible Notification structure,
   defined in YANG, for use in YANG-Push Notification messages, both for
   NETCONF and RESTCONF, enabling any YANG-compatible encodings such as
   XML, JSON, or CBOR.  Additionally, it defines two essential
   extensions: an extension to this structure supporting a hostname and
   a sequence number, and an extension to the YANG-Push Notifications
   supporting a timestamp characterizing the moment when the data was
   observed.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-netconf-notif-envelope-07"/>
        </reference>
        <reference anchor="RFC7942">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <date month="July" year="2016"/>
            <abstract>
              <t>This document describes a simple process that allows authors of Internet-Drafts to record the status of known implementations by including an Implementation Status section. This will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature.</t>
              <t>This process is not mandatory. Authors of Internet-Drafts are encouraged to consider using the process for their documents, and working groups are invited to think about applying the process to all of their protocol specifications. This document obsoletes RFC 6982, advancing it to a Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>
        <reference anchor="I-D.ietf-netconf-udp-notif">
          <front>
            <title>UDP-based Transport for Configured Subscriptions</title>
            <author fullname="Alex Huang Feng" initials="A. H." surname="Feng">
              <organization>Deutsche Telekom</organization>
            </author>
            <author fullname="Pierre Francois" initials="P." surname="Francois">
              <organization>INSA-Lyon</organization>
            </author>
            <author fullname="Tianran Zhou" initials="T." surname="Zhou">
              <organization>Huawei</organization>
            </author>
            <author fullname="Thomas Graf" initials="T." surname="Graf">
              <organization>Swisscom</organization>
            </author>
            <author fullname="Paolo Lucente" initials="P." surname="Lucente">
              <organization>NTT</organization>
            </author>
            <date day="29" month="July" year="2026"/>
            <abstract>
              <t>   This document describes a UDP-based transport for YANG notifications
   to collect data from network nodes within a controlled environment.
   A shim header is defined to facilitate the data streaming directly
   from a publishing process on a network device to telemetry receivers.
   Such a design enables higher frequency updates and less performance
   overhead on publisher and receiver processes compared to already
   established notification mechanisms.  A YANG data model is also
   defined for management of the described UDP-based transport.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-netconf-udp-notif-26"/>
        </reference>
        <reference anchor="RFC7951">
          <front>
            <title>JSON Encoding of Data Modeled with YANG</title>
            <author fullname="L. Lhotka" initials="L." surname="Lhotka"/>
            <date month="August" year="2016"/>
            <abstract>
              <t>This document defines encoding rules for representing configuration data, state data, parameters of Remote Procedure Call (RPC) operations or actions, and notifications defined using YANG as JavaScript Object Notation (JSON) text.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7951"/>
          <seriesInfo name="DOI" value="10.17487/RFC7951"/>
        </reference>
      </references>
    </references>
    <?line 1970?>

<section anchor="psu-example">
      <name>Example: Modeling a 750 W Power Supply</name>
      <t>This appendix shows how a 750 W power supply is modeled. The power
supply, psu-1, is fed by outlet 7 of a PDU and powers the chassis of
the device. Both are Components in the ietf-hardware module
<xref target="RFC8348"/>, and psu-1 is contained in the chassis. The values are
illustrative: the power supply receives 400 W from the PDU and
provides 376 W to the chassis, an efficiency of 94% at about half its
Nameplate Power, and the Energy counters cover the 30 days at that load
since their last discontinuity, reported in discontinuity-time.</t>
      <t>The following instance data is encoded in JSON <xref target="RFC7951"/>. Power is
in milliwatts and Energy in milliwatt-hours, and the uint64 values are
encoded as JSON strings.</t>
      <sourcecode type="json"><![CDATA[
{
  "ietf-power-and-energy:energy-objects": {
    "energy-object": [
      {
        "id": "psu-1",
        "source-component-id": "psu-1",
        "power": {
          "instantaneous-power-received": "400000",
          "instantaneous-power-provided": "376000",
          "nameplate-power": 750,
          "data-source-accuracy": "accuracy-measured-gold",
          "power-factor": 98
        },
        "energy": {
          "total-energy-received": "288000000",
          "total-energy-provided": "270720000",
          "discontinuity-time": "2026-10-01T00:00:00Z"
        },
        "certifications": [ "iana-power-and-energy:c80-plus" ],
        "relationship": [
          { "type": "powered-by",
            "peer": [ { "id": "pdu-a-outlet-7",
                        "details": "PDU A, outlet 7" } ] },
          { "type": "powering",
            "peer": [ { "id": "chassis" } ] }
        ]
      },
      {
        "id": "chassis",
        "source-component-id": "chassis",
        "power": {
          "instantaneous-power-received": "376000"
        },
        "energy": {
          "total-energy-received": "270720000",
          "discontinuity-time": "2026-10-01T00:00:00Z"
        },
        "relationship": [
          { "type": "powered-by",
            "peer": [ { "id": "psu-1" } ] }
        ]
      }
    ]
  }
}
]]></sourcecode>
      <t>From these values, a management system derives:</t>
      <ul spacing="normal">
        <li>
          <t>the loss of the power supply: 400 W - 376 W = 24 W;</t>
        </li>
        <li>
          <t>its efficiency: 376 W / 400 W = 94%, which the Energy counters
confirm over the period (270,720 Wh / 288,000 Wh);</t>
        </li>
        <li>
          <t>the Power drawn from the PDU, by summing the net Power of the Energy
Objects: 24 W for the power supply plus 376 W for the chassis, that
is 400 W, without counting twice the Power passed from the power
supply to the chassis.</t>
        </li>
      </ul>
      <t>The Power Factor and the efficiency are distinct metrics. The Power
Factor is the ratio of real power to apparent power at an Alternating
Current (AC) Power Inlet, and is considered to be 100% for Direct
Current (DC). The efficiency of an Energy Object that provides Power,
such as a power supply, is the ratio of the Power it provides to the
Power it receives. A high Power Factor does not imply a high
efficiency: in this example, the Power Factor is 98% and the
efficiency is 94%.</t>
      <t>A battery is modeled in the same way: it reports received Power and
Energy while charging, and provided Power and Energy while
discharging.</t>
    </section>
    <section anchor="changes">
      <name>Changes</name>
      <t>Note to the RFC Editor: please remove this appendix before
publication.</t>
      <section anchor="changes-from-03-to-04">
        <name>Changes from 03 to 04</name>
        <ul spacing="normal">
          <li>
            <t>Removed the unit-multiplier leaves: each leaf now has a fixed unit;
instantaneous-power is in milliwatts, int64, and optional.</t>
          </li>
          <li>
            <t>Renamed energy-entry to energy-object, object-id to id, and
power-state-admin and power-state-oper to admin and oper.</t>
          </li>
          <li>
            <t>Based the admin and oper leaves on the power-state identity, so
that both can take the Power State values.</t>
          </li>
          <li>
            <t>/energy-control mirrors /energy-objects, and its id references the
Energy Object with require-instance false.</t>
          </li>
          <li>
            <t>Relationship to the Hardware YANG Data Model: explained the three
ietf-hardware identifiers; added the Hardware Component
Identification section.</t>
          </li>
          <li>
            <t>The absolute thresholds of the accuracy identities (suffixes -1, -10,
-100, -1000) are expressed in milliwatts instead of the
unit-multiplier scale.</t>
          </li>
          <li>
            <t>IANA Considerations: addressed the IANA early review: registration
in the IETF XML Registry and the YANG Module Names registry, and the
template and initial entries of the Power and Energy Certification
Types registry.</t>
          </li>
          <li>
            <t>Took the Energy Object term from draft-ietf-green-terminology, and
referenced the latest versions of draft-ietf-green-terminology and
draft-ietf-green-framework.</t>
          </li>
          <li>
            <t>Editorial changes.</t>
          </li>
        </ul>
      </section>
      <section anchor="changes-from-04-to-05">
        <name>Changes from 04 to 05</name>
        <ul spacing="normal">
          <li>
            <t>Reported Power and Energy per direction, as unsigned values:
instantaneous-power is replaced by instantaneous-power-received and
instantaneous-power-provided; total-energy-consumed and
total-energy-delivered are renamed total-energy-received and
total-energy-provided.</t>
          </li>
          <li>
            <t>Added the Power Cap: definition, requested limit in /energy-control,
and enforced limit in /energy-objects.</t>
          </li>
          <li>
            <t>Moved certifications to the energy-object level.</t>
          </li>
          <li>
            <t>Fixed the Energy units (milliwatt-hours).</t>
          </li>
          <li>
            <t>Added the power-values, energy-values, relationships, and
certifications groupings.</t>
          </li>
          <li>
            <t>Defined the parent of accuracy-like-parent.</t>
          </li>
          <li>
            <t>The absolute thresholds of the accuracy identities are expressed in
the unit of the qualified value: milliwatts for Power, and
milliwatt-hours for Energy.</t>
          </li>
          <li>
            <t>Operational Considerations: consumption as the net Power, and the
mapping of the RFC 7460 objects.</t>
          </li>
          <li>
            <t>Added the reporting rule for measurable values, and text on Power
over Ethernet and batteries.</t>
          </li>
          <li>
            <t>Added Appendix A, an example of a 750 W power supply.</t>
          </li>
          <li>
            <t>IANA Considerations: registered the ietf-power-and-energy module,
requested an "accelerator" hardware class, renamed eu-energy-level
and cn-energy-level to eu-energy-label and cn-energy-label, and fixed
the registry table (c80-plus, cqc).</t>
          </li>
          <li>
            <t>Capitalized the terms defined in draft-ietf-green-terminology.</t>
          </li>
          <li>
            <t>Updated references, and editorial changes.</t>
          </li>
        </ul>
      </section>
      <section anchor="changes-from-05-to-06">
        <name>Changes from 05 to 06</name>
        <ul spacing="normal">
          <li>
            <t>Added Power Factor to the Terminology.</t>
          </li>
          <li>
            <t>Appendix A: distinguished the Power Factor from the efficiency.</t>
          </li>
          <li>
            <t>Relationship to the Hardware YANG Data Model and Operational
Considerations: source-component-id is bound to the 'name' leaf of
the hardware component; the device <bcp14>SHOULD</bcp14> also report the 'uuid'
leaf.</t>
          </li>
          <li>
            <t>Energy counters: yang:counter64 instead of uint64, and a
discontinuity-time leaf, which the device <bcp14>SHOULD</bcp14> report, mapped from
eoEnergyDiscontinuityTime of RFC 7460 and shown in Appendix A.</t>
          </li>
          <li>
            <t>Operational Considerations: counter wrap and reset, and how a reset
is located with the YANG-Push observation timestamp when
discontinuity-time is not reported.</t>
          </li>
          <li>
            <t>Added the Implementation Status section.</t>
          </li>
        </ul>
      </section>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA+196Xrb2JXgfzzFbdVXI6mbpChZ3uhUVWRJdqnbkhVLHqcm
n782SEIiYhBgcAHLisvzLPMs82RztrsBIEU7lUynqvUlZYkE7nLuuWdf+v1+
VKVVlozUeXGTlCrOp+o4T8rrW/XTwdlzdVpM6yyJ4vG4TD6M1PNXx8dn/fPj
0z5+G02LSR7P4eVpGV9V/TSprvrXZZLk/QWO1ofR+gmN1r+N8+v+8EE0iavk
uihvR0pX00jX43mqdVrkl7cLGOfk+PJZFH2jLqq4qnUUpYtypKqy1tXecPh4
uBfFZRKP1Mvzi+imKN9fl0W9kFVF75Nb+Gw6Un/aOMmrpMyTqn+E69roqQ16
BH/BdeO/tF38hXe78RanPa/HWQorhPWoKSxUq624ror+NW4C/p6q9ErlRaX0
IpmkV2ky3Y4ifHCEbx8Vk3qe5JWaFHlVFhmsX1cAgv+MsyKHzd0mOlqksL6q
mPSULsqqTK40/HY7518AnPN4sUjza1rNQV3NihJGiekXmKOv0lyP1NOBOszi
VCeRUld1lvEZPE3yIq3cN0V5PVLHH5LytprBkAg09T/UQVlOALJKJfM4zUZq
TG/9PrHP9YuFHgDszGTPYbJZkgdTPU9y8yHN8mMd3ySpG3QC3wHMfj+jzweT
Ym5GOx2o8zibJ2URDHgal6kuMu87Gvckn6Yf0mkdZ27sOT86QGT7/TV+5o//
7wP1Is2n4yyeBhP8e5z7X9DoB1mmnhWlOp4Ubvg/x/kgkwd/f1WUgwS+jfKi
nANafMCDVkq9enb48PH94Qh/V3J/LmcJX5ndwa46iqsY706SIeRfAO7X8XVC
jxO6qL3h7oP+8BEPEJfXSTVSs6pa6NHODjwRV2U8eZ+UtMsBrHYHcGNnVs2z
nfJqgnObdTy6tx+ug9ZwCZdQHaXxdRnPdTjto/7w3tdNi1OZaR/s7e8G054l
Fd5IdVjkV+l1XfIlOi8LQHY42K2z48vDl2fPtsPF7CJJ+KrF4AIsDIYNGLw6
vqDZ7PzhrA+/elacycy6v3d/r4UBF8mkLuGfWQLItXVx8eM2XWOgCoaudC5p
CMiw+3VLwmWYJT1+tP+gtaTLMs71AqgN4OEtkHhaYlrdqq3LFxfb7oj+Z1Ii
IQb8vResbQ/W9vDr1obrsWsbDsND+sPrk0PVVwfq9dF5/2msgbqe1lmVLrLk
I/yOnEigaXcQrguQ5/5XrgvW4l2gdTD5YDJJtMYPkbTz3f4FL5bF5XsPHj1q
HSGyRfXH0xfqVXKd6qq8DZFn/6uRB2ezV3q410FJ8IC6qZkC6qgAtb/y6g/7
u8OvvPqwUIfxj8NFH+Tq9QInUVXhizDqDPiANgCkJYbYdP+r14NrAFElv2ox
icePhw+D1T2vU4IirAShJxyecP1V8iFNQCbRqriyogQjXJzmCHjajTsL3bql
X4l+uMoIfvr9vorHCJ1JFUWXs1SjRMIizTS5olXHvAocU81xFbSPpuwYzYs8
rYoSV42fikCEO5vCNuEmqZsUpQ1gxPhlnkxQuIITA1Y+r3OhlVHOmKUHvLh5
Op2CMAqi0QmON60n9FSEVwSkP4Xin1Ybp68vLlGyw3/V2Uv6/dUxkJtXx0f4
+8WPBy9e2F8ieeLix5evXxy539ybhy9PT4/Pjvhl+FQFH0Ubpwc/wTe4z42X
55cnL88OXmyANAJ3w4cgSK64wXECX4F0uigT3HKso2miJ2U6RuEyV08Pz//v
/9ndV58+/Qvgz97u7uPPn+WPR7sP9+GPG2AmPFuRZ7fyJ1zD2whExyQucZQY
mM8kXqRVnIFYGWulZ8VNrmZJmQAo//VPCJm3I/W78WSxu/+9fIAbDj40MAs+
JJi1P2m9zEDs+KhjGgvN4PMGpMP1HvwU/G3g7n34ux/wnqn+7qMfvo/+RnQ+
/WXRuWdJZ60TOCideEtL8+jTpx9O+kcDT52C5/r03OfPA8Z3b8lpPslqwCI1
LqoZDbv8+smGXo7/DGtkIiSrggXLZgYCrSZo4KMxsekip1lYqVJXIGMmOMJG
x8Ltl58/466zrLjBVXmvw12Yp3mRFaCEwQD/0hjA+5r23lJTG2djGPQEBH64
a3AnspTPwhwVADg4FmWpDGkEQKBBWLtK4zEwDf941TyJNXA3/LwoozKBK6zh
WfqgtazJLEY6moCyAqIfQBrvpGAJ7l5PikUSwYkQlRB9khc0UJdEwr0V0wH3
1LhmOoIqaJbOU8ayXgRqMMyEqiTMAMoX/MYLKkCtU8cwH2rDauu8ON5WST5d
FECD8HFQpip+NDpCvpjCDAiS1wBTUH7Pj17rbSY2GmCMTJ/xab6ACZVOShgf
8eUNkhYG9gTh0ZO1+5iYfKxgao1HgQA4hEFALUYeR1BIInkFyNUNSs9Itoqr
6gY3TCuA2QgcZZ0TPxQ05Nfg8OA6w6lokCF7fAsS2NBEC9WVlRCZJXCqI57v
Bei+mbkYx1dwCmmST0A8PnpxfAy7twsNnlT+k4f8JKwyWhQV4k+cgfBatsYP
3rrAt1Rc0WKLEs8NJRPArQxfGZBymnyM5wsEaKz4lAmzJywV+EDU9WSGMItR
z00iEL9QYEU44WGqrRfnr3GJ6oJQRD2LxwAc+e7i2Ws5ZpAtYNz226fwNpzz
N9+oS3chm1R1Hr+H40GaxidKd1sLsZ0yZVt5v8nEwejYJ4FtkaEkZz5hnEbb
UGL/IlPPVTzxP8nIesF/vawr/89ncCcLHEvO2/yimCLC3xak7jtHYtxn7iDh
sw5MUi1M8se+A5Xg0fWwh3kBg7lMaiTOV2UxV3fAmTB1JbEmMiMiRPpXlk2Q
UkUhpVrGV/HwPWoPc/dAUkkB7+BpEEoKf+yRoeqH8WIUkQhfgyhTMokz15wf
qWZwX+ACBKcGW58kIHcjRQMyN0b1CJ6Jp7DjVO4UsubYcMJMaHWCMvsEdje+
9UgJsWe0CPHVwy+BbNQTw7gmWTF5D3BO/lLTUQCyx+5oB3BjsvR9QiRNNbHY
B4O6Sj8S19Xpda4+xFlN19zCAm86jACcJAfCO62JigLXKLthX2sBPKNDiyOh
XDiZgIgc54BXyIruZLcySJlcoV4ihDvN0aoJ/0uKWkdoFkUaxtuKDd0HQOsa
FS4A+4JEdfg9yeCwgOoAcWSrcLRV3S7wbxBkk4/ITzWj2k1cVXp7IEvv4RHQ
0cUaaLvlvLTdCLZfZ6R3qXhe1AAJOBBSSAFUqJOhxIJ8sErniVoyY/TnApRE
Wi7O3Z8VdYkLeIoiFUw9SRYwHV4KPPYU2Yhl5iIqgdKDiqYBWpIjI8RrGWd9
mtrxwp5BRBHkF/B9+lcWEq1Q6Y6akAYQUQ4S4PkhnZL0iuP2UZ+4ZvM0qpAg
ZiLtjstbEu/wzAEoNCtArij5V0L/D0lOz+haIzuJx2mWVqBI5HF2q1MQiC5b
wklD2myJygA8kiJEjEx8+Y7mEnXHKrQMNY03wjEK9Scxsb4d0CAgeiHLN6IC
mszHRaaVCFM0UIU2z6nYPOmoPMbzJzGVvkUmRjYVlj6fGZLHi22JtCrQzlaS
TJAqURpaInyT6cQIdCyoWtZ9g9KTrzNbGLPIiR8J9TAXYprMiV3j/y3EATpM
SWGTz0TDuJkVgDmA8hVa0gR8wVTCP3lV+G0J9/QD3PBIUJ0MET0FpBCkfyYG
hhYIvOizJCd5DzSFjW4lxoMVnUKLQjnbBp/GigcElbXHGrznYJtJPJlFAZfo
4Qkyya1JvCUWk8RXamuewvkQzSEUDSmcG93NBdS5p9wLZAVrEnrksXZgJij0
MC8K5K2qACEfjp61C5ZY8bgTthdMJqBsTG57UVJNuhQfJkYIBdgR7mUKZzVh
egFyYJ0jW0GagIwFbuMrZpJTvGluJ3ZB6kq4NWAEH27IY6sZyJ/Xswgh5wla
mkmJ0KQ7BwcRFrEU2DpMUtDug2m0mUe5eViE04YYk2IX5UXe/2tSFkZ+1gB+
IocjIIvkfQSqBvrIrRUOZDSSj2DwSMOJTBJ/9eYR2b+RBszRT9Mrg+awSxwi
KzQRSZm+IZHSUkHeZKncg5lI2izW8u5w1WPAk6RsLZhpP+qT14amhOuN+Ilp
qs1DsiYUlFk6kaF7VktA6NLTBIAIpLF4AqS/hzvjM2INVRkN1YgZT+BVfIiI
nZWcoqey9tOTp0glkXrff/gQRYhn1qASKKM9D00M8kQwWCw6LM4h1wFJnKDD
saJb32tcx9KgNg4Q0elbc4Z5GQ1g3hk86TjSKbqiF8hIozmww+zW8BfSaQ01
R+tOURr2hnq1bO+qLZgynrj18XkBP6z5C3tthGbogiVcgUusrUQPrKKhqgCW
xjlfIZgGTQLE6NEkcIP7RssgrT5YokZPb5w1DUHI5us5iEoDFL+N5AufXqco
JBDvW+i6L98QBT8waijRK2K/KH8YJrPKUpPi1kmGgxmZwxNVtzIsye4iHDGZ
/uCsbPgABxgQikeyDL65VjoUYRWNDgCTLU8bgC1t27FJqomzaAtuah1n276W
iSeH0g++kd3yrapuCrMcS8BRymRZtEDoGB7Ag4BanMfXiRj3hDbwWN78BL9o
a9PtRQInCj6hzW3YfQaPWfHV2ADgxgChJwEtr7LbKMNbXaq8no/5yJmdTQiy
sSB04KpZNrWILpvbvNr2S542I+YoxEqQqzNQU2EtjN/oVUxQ2QI5BXU0T35F
eCGF1El21TfzTyMfjegEK6YjRIlAoNbE47JqRpwC9nR2enQQbRlH1KkDOEoM
aLpK1EE5mcEKSQ7aNkoXcV4EYH6dJdEGodOGCAWId0zKQHDc+/wZDiDWpNjA
4oG+9IQS4s2LpyDDs6QZUEshEozcpPfGqBTrTvXUU04Jj0G91DC0U45RFW6S
GLYlmwtbkWLtc2Ck/s/PX0eEKCBVakBAPk6ZAFbNejYo9+aEjb5vrhmO6bAD
vtoJMYQHZHobiVKtRZYMJukpkZZAh9a4OxJOmOY5kUOoEjFwR+59iU9WDJQK
6Pekaq3WIwkhNXKysrcLuWIDdQQsFLmUaPqg3KLmDSPQfHqJ9cEscxnvjBrY
kHyEUyeeQ6fjjhd3idPIpgIBTyeLGHU8IUPRHQdTOLpuyKG4i1BUiAlLYGXG
AOIYalPoA+I/LRLG8mkZ3wAul54xhuBuh2E4MTbQrwhIuk1pPkUFMiFlh2gm
89WFoB1eA/ZythdBuIFyJUh3PT6DVPf8gUJBH5T/Opu2Vot3HY9HJnbMFiU5
S4kVURi0V5DTACjCrc92ZIOBZVaICKIdHOi94VC96fGt4/G95TyC75gxp1N8
FYbZG9JnPEaWXs8qCm3Linjac4xdAISMzAI2Ja+CTrZ7rEGSmGlmjbxZ9+/j
FGJAipUF9Z+LMQ4ySzISsWjlfNVAeSDQRRqoFaBNMGlV1sk28X+Ps+lbwOk5
iry4YFAh0YFyCzShRMNM5SOE4AICe3xLLDM2N64hKTnNKMSwkbvSUYN2dOBA
4+ANUIsxehTIW4HyL5sMPOuQmTFmao1iExIDFGLZ8AID59Pixt6dqEt9U+MM
FT9murRTTR4eT78Q0xl5qnRk0fN9jozCYLmRulfdFKEv6VRkUeS4tx3kukEk
wj8jcdOO+dTcYEi1SIVDoa4CBk+Ssp0kWjmqmJKWc78o5H6TogQcItui8riS
L1axYOBQJOQd4wTXap0+DPF0yoZXJEllcsXvipWjb8SkiC6VIw9teUl8ixO4
cgiBcXKFVKa9BpT+JVBBAppKjDKEuxVfVXyms5jUDnbdG1kfcYnv00CdXMm9
AD0FHwix3JJmQDZQYyqyaqaatasoXHWK95PMGzxtXgijEbQheMODepYu4JoB
cyaxxfBx78sxyFlJ4skiZsOGgS2Sll7fA9nesNV3ghr+oH24eck78b5WcBFG
6p0ocv3x7Tsamj+AUd5FW4IJrMO/8gYCavhuDiJ48CJ9gC+qrVP5NWq+FF9f
l8k1nqh7z3zGrx6Yv4q8+TY9zSZf73X6gN99VucTkfSP6TGkEuEocA7HMVCC
RZyy3G5hYU3V2tk6ghOxaANszCgsxgoG45V8XeG2bCWD60EPw5hDRDogScHC
u8FQn/ZYEmh8at/Bg22Mt01qnW6sU6K/SQ1gI6fgBOwY/YaInjTijjkxUCgW
bDyeinB2S7ClJ0u0YBNRmhY1wLRvTN0u1EHMX70oNAivNuUKg0fg+cuPEEd7
pIrD1yRadGC6IQ8mkIDM8jEd3Lt0+i4iecgTKd7hGO/oxqHYgF542IAnGLMM
B/efOCqfclJuavX69cnREzxLHAb/MKwNWQcFCYl5wKykNGtDT2EvCg2QsxrY
OdzJeCqhDyBVZribReVrBO/ki3dERQFnX8GVKOkcfVhpdMY00UL3GkFRhn5F
ohPC/ucJOrxSPWc2IKS/MXbg+ldb6SAZ9JBzlgmDoIOY1TnIIk1OuP2E5fw7
nu5kaSwpxtM+CtaRr8pTzMwWr11ENLHIh7swdNR3BXgRInjLzQ7p2kaW8JKP
X3X6+MW4uMzNv01wsm46FOCtyDNN2FkjRtFiURMH5iPDPbGFObvtRUamYuZp
wjtK3H3AdQg/uvbcuDNZMSFeiokXYpNz8S9wdSNOwSDBTGPITapnwlORo7Ld
QDlubUQJa4GOPKPABcuqW8f56cW2omALI4UhY0SLBXvCrC08Gpcgjyc2WEoZ
qkSmdqRMtXEk3kFYDmxkDCgWIFBlxpUBZ0bXNiIbUV+eCjBTiLdlpErogCyq
TzshQrAdsZLBnH6MAJ/HeL0omgZ5S8XRRHS27IJzwoS9jNGSy0hW5FU3EoSA
JEPi8L/hR2HuD9mYeKKRIuA0U4Qipf6t3y+LhuELPv6585t/VX9Kp2/5a2We
AAmv64eJauNZdgD0J+b29dPpD/Bl/3u1M7sZzYCoIbR27Pc7mErSGIM2YT+z
Cw08SLJTo9rgHDUc8oP99d4zNuJV7+XG+cTv/NDcP753b6/9Ht7qvsDBaCz+
yyKC3AL7ab/My7uiiJrWjPDjf99+21OW+nj7s8YQ46IABpMvmxbY0r/439kT
YdOQ23YIrvAxwIkfOqbyka09f1VUcda3Iqw7VETzEdvgy65DCl70T/WuF0ny
QbmmhqOgWAKBFb2IEeB0jfCLLzjilWe79HS6YTVJysqGCOh/XYU+/iGy+b41
OfLSH1a+7tMeoAMolzlKYJ/Cj5ctw60EaGiDlPhfewSlQUT8p0Qm+sF/Cr+5
aZjSI/vOTZvMqWVf2uWp8KEGsUPCtUpg2Umn7THCg7A/P5vvSU9vH0b7QTq0
xjfrrmzJa/Cz461vB6dYtgO0vgVvyrd0zz3SiQwp+kRphO9BV/puA61ZG0RA
v9vo5EuD6mO18RkDFnxJxjiJfxQ20czOEFMMDjhb8gjpMPZ9Tz6RYJVHbyMS
MSXeKM2N9xG1eWv22OxgY5tGNj/xY+e6c3t9pagdi8zSIqks3RO52LBY2Y3a
R6Jg8CY8RO6w2x10AU0esk6jaoaORqfScFCFeTyyU+uR2sRT3eypzcXsVqOM
209BrP+4yer6Zl3DBgaKLEP8KOtmqfExgB6AaSX4cJ2nf6kT9AibiY37iuM5
WW6PjCvJ2vZQxprEJWq8qJbwMDlmkl3XcQmsHvYST8pC66gt96KS2bSwarPg
xp546RhJhioILHQeUyQ42ufO5dETfNIcxTHdZnTYU3DUg8f37r11PmO+6/15
OlZXSUyxQ+QiXrA7wiyCQGihFqOegTFQtIDXtFd14pRPnOfx/Qd7b3vOL1sV
Eeqj/CxDAjAwlsAMNvmLfbVkO5sGLkgaKkZpav7VnIqYlcmv4g5Hhu2AJSMc
BzF50WgqnTtf02qcjQg7jGWG0YjvS8wfsSJfLLk/7MzxX2tin/iv2ndLB4gZ
rURM1UBMNnC4a9qAnwDMD1drA6/nCfzGaEwuTtFnKosgvLHCs2Si92vq5jdu
Uk5+tzpiqG6L/1j5MZeGhhkLvIFS34MSPN9BhuUcJbUKTvLzZ3RFsV+YfT+A
l7ujXUA/5zkmxI4z9LejyosGovYib0k7Rv8Q6spkLjKXteMYyTjUgRqD6IBI
hnsji7Vm825I89DXkGQJWdJdHsDz89e6F3qjjTcWMSRPbtSG9+JGc6ItDQrb
p0/eI3364vPnbT4unBj/z9HcOpE4Rk/7BiInhRPExIcxOBihDaiAWqqOTPBc
B3YPFDAv3gwNT+72OfrH8GBcjCsQELu/yiGRszQY45hbjc1gstOiSz8yLlB+
uMibtgR8iFYltgj/AiC8GPAmGWc72DwN6rys3qhogoFTQR9K1ckAl6KrOFOm
ntMak4wql0rjoNkwt7Yid9zSFjHyoB1A+WwaGMa8YA8mj2hPdgGNOyJkOBs5
oZBxROBsuk+jhkYNuJ6wJYV7ogyTTinr+PTgTL2xYbr0JyVF42e4p+dYCSTa
WpnzenO9g1GzO/EYTmhnmzkWxnZjrO3UDBXRUGx5XRjfjYmagpXaoONpgZYn
xGUrXonZnJ1NwdLcUBghZ2Ker8iM7IcLGzdYZx6iyxvEp5KPGPcgSccYEINf
SqCfH0zsh+NJkk/OyViU7m8gfHZ5cvlTH1eHstyU6SkZlUmGS+lEGf9QVqAI
MGQiH+IyLWoTlkNcodBJsE30KpBhKUWH+ZyivtD1+wFEABdJ1xJSvdTDlTKq
Zb/NPE2brA9r6YKnAc3+gyFeJ8wfA3mCAuQVpchR2iAb99gkW2ScH2ciRK3I
5hI518jf/BHW8QHD/awnrmIbHY55XWAwWAHUZr4gMY7DeRw86XwijypIdBal
iWjxMjMHs1fHPw2SYii8MZrWiXmMmNo8cKjWi35V9CmX3o8EN4xcrI4Ri7cl
UcxWntKAjNv+eryloI91nkQOvyQGHdR2XqYkRmB8Cj5JTIuwIi+m8ghgKroy
KEEQH8mA+Ew4DtXEwHAczbzAsALOgEFR6HYQBVEcdL7M+5NCgqeYp8N+A0Qh
pWyRxZw4FDkFywYvhNGpxtTTFZbdE2oSkbX/Jr41YqNJI2WrkO4OmPdLNEVn
RWVPEynq8RTvwkidm7h9WjKxiGLC/mJSMq7Uxh/hZ6MVvOYwAYeTeEKQAKyA
FDztwiDKhGP+qDYBjk+ZIkGyhx3ZPLLwKi8VV40gOrcFPESeNsfdiufdeznI
XRbhMKWcRFqxkMUgK7oF1VpjrR5YlDH2+3IwLtpPXaXT01YM8E3ekVEmuqwK
6lPE9rv+B1t3ZfcJfAb/Q22AdaCNusxH+P4Io7/mevRxno1yPSLDX+e4GzgG
ugvTj4DHMiDz64Zc8YnsJfLo7OYJ/WmlczGmbBjePFIH69ovaAmfo8a8tFe+
2sHM+PmKuR8/3t0dIcTh6LwFYLkw3Z4I1tANaTsdPsJwWTIh3oXV1dDctCBV
xLlJ3KIRSChhfTLg/xtyEiQJicFr481z9SYZj5T63V1yC3GRne95nfDaC1AC
Rup3WLKqKkb07e/N899H/BgXF4HRm4XB/B8zxNIyYN83BvNKf3WN06781Ryg
Xeqra5zuKl/NsRpVvboG6qrn9f0Gn7+y/4X/caLXwh2loyNz31CGQuNd9SJo
2K+tgcJvLylRIGd7OQuzcznls9aeiCSL3vLCg3v8ciOVrBFObIlbz4+2kle7
kpz8rIrtZt4dvbU8x7QHS8PUyiCtSrQMfteT/MztHPiHh5BwtV82sZAJWvxM
QRP83dQxwd+pWIn9RTbFj7EJw/3mXrc1SPDPRlmSTYHM5unBT8awaKqRbH5B
FRjZbFgKRu3uqy3cNhaC2eZfsQzMdmcVGB4D2NGtWrMUjAfHw2JxW5J2vTXZ
pnpCrGBdYvFFpxwCr0IxzYttMWuPpZaRSIeTApVlqqhBw1IqBdaLmBocfpVM
/ZITYkfDNXuZWeM0l0RWNDiR2FCID8CEIACiO3M1BcsgflWUFVeXuo5Jjpcq
FrXENRcWWApEB1CFTNq0TUKAhbBQiIWZ8GI9vTgCYsPP6kR8FrAwWBKs+ULs
8vuDiQGBg9+mVi9ALs0wYoNlI21gkFFwGeIEPW4LP/H3VqGlGphJ4piCrLqP
GuC2IwuwfSNPmMytwK6pKRoMvzO3qTHRzc3NoLya9BOSHmkqnALrROHT20+U
KPU0APv5LSio4CKJ4BkKaCQQAa2NkNWKTEiVqrDu367w5SbdRSaK2kCc2Zc2
fgl2zYKQOLE6vaLLF4TV6dy7lFUN+1wUIAtTqBSyAzsKyTgDw47oSOyrdAO0
kfHLomALSqxmoEGhnZGrCchQZgwascf2HkQWJumkwEucCof1m0gYtgSJPmcG
obsjYaIcQVezWT+f1lhSTlGtUpDmLJNh4mpXxqEuDUXcQy66e7GWug8OAi8p
xMxI/hj2wpVgeAC3cQ6Bn05TSciS110gNRxC39xikSRReU6SqSMqqvNkfeeq
HbCPVRr6bO7qfqDOOSLHfPlzxxPxB5Az0AfRPUSiQYOljMLlg6BzM52seADg
hILEqkdAQSpzb5bgS5NHGYpInY/0x2WR/7UhJbanazze3/3iF4Zf/sbXvDJc
Z886zT6EnuWVo/Pj/cFgsM7g10U2XXtofHjdgVsHumJc/P+aw4LspwMCYC8g
hZdpCY1svUiijakPZt4HVjxBd8YNcFA3EPkREj3ylsMnBiL9v+301b3ht95X
DG75ajf4CsE1oq3AV/f9b2BBI2W+2fvWbugktySGuXs3ABzFtolLlh61ctv9
tA8mYsAcpuk1RsJ/ADo8tVKuJeglEA2k0pjB7tHbixSzwrqBRvI/8JyizJgF
USi0nsNk5nVjUrKU3DqDTo4P1YO94f17Pf5199H9Yf9hf59MzgY0x8fHIHDe
3xUi3zovV/2NHIwomhl7zcrjJpPzmGyn3qfoxwdZNJs6TnE8uB7gge2qb5EN
YnAtAkn9Gx3jcDC878ahEg4+5OZAhgE0kg9Jce/Lka/n60iWc1j97iq5cTNV
Bfq/8GAEDj2LFFOuNcRoWl9hcQlbJsdOaFGJzDqSmm8eNiNZ7FoBJ/++5IWM
MVICnPuqARzv6f7uyP1BAFaNp4OHh6Pg4WHz4XDooXucnh7e8bR9nJ8eLnn6
clbrILm1t4xewgKX3lLW1FsXNHfwxSyJFEWUyC3r/rd4vXnv4epEPUU7CWU9
U661Q8NGxTapQwGCGsV+MzqzD9MG/dKlNe/DYnYf7N0fKleRpLeM4JrNS2qV
GcJlWtrsJc5sF4hwPELq/KO79/fvPQT0wWtqBtl9OHywB5/5y9BEnO5/27VI
HO/RLr5hRvDftH7Da8qYcomj3iUzWI6j21X4UzggH1Q2s8GkhEq0vED6Lgj/
g+G7PyTY7j4YdkIngGsLqqTePwyPwor0Nvk+0fouoIbAtEqRpU5NqVe0IaT5
nTL1k2XKUiAzBNnXjmXStUS7PM+1ejlWxPaX1FzuyuUsm55S9+3oVAmroNQq
qjDgKLuprCj4dQVvUDWl0i/8JimHpvpIcXW1alue8vEPgbS9I6x7trQrU1iL
kk7wHeNqljWGiaYUtSRDdD1AuclFnVNFlrDs6yY/z0FB3q0MnRP1ojNMAZjr
DQk2Rn12h2QctyYVzjsYuaiwprCCirxqrG4c89IVi7M9kvxbzzMXjiHgu0pL
XXkzMwxofnT0woeDhkUgtSyr1slVzQZloxRTyFAjU0aCbCiQohE7nObwXVqF
4kejEK3JKLWZUqEC3DAGh4KMva891vPLJhb1g/v8y3iTzBz4KgYejLzIRbVl
mhbsb6+4a1YJ/5tu2rKbZUfvocQ5w0xyJyhbgo9b7CnW5G/J5B9nk5ojXVQZ
MzdDCm6yrOybTnhZRU/YiNBJIe0Cv2p7di8yA35u60jZRcZ5jYkesNAyDM7A
tjZYg2WWcNyXZJv5zNKOgsWorYOhJMMovO4Dxyum6MCykpsZ28nfEzJmDtiW
tyzfICXU1ItcMQUT2OyNlQUWFLqzkheKlefvuReQlkF3QvWPJuMketPrQpEb
FeQfcrWvWKg1Cvw9Lpy5Ib1udDArJUZgePY6ixWzUSd0zTP/sAWzogLQnrDd
nJRoQ4np9lGVD3n1ZxZB+/zuz+p335lh/hWtKerlq65HQGlcHyz93ZWAkad+
VfDZZeiEnoMV1sbfHoCGXwih3yKIvhhGv0kgrQklNgb/2kj07t0kej3A3EWk
+alfFYTWJNIGPndcrl8jgL7oat1NpH+VIBrCyr8QSr9JMK2JS2g6/bUR6ft/
oxjN5uTVSIPP/JpAsyZxNm6c3xZsvuAu3U2Vf33Q+ULw/PbgsyaAyiUGo39i
Urz3N5Ji/P8dlPhXBpg1CTEB5o6b9GuDzPrX6G4q/KuDzZcB5zcHnTXBQyFl
/4Vo8NIAtWZgmgzRCGtpBLRgcMEeFo/2GnOZh8wIHBVhQyL2MHyEgiL27t0f
OuN8xMHO0+QqqB4msKN6TljH55F8oBRXaN8YqsHAYisPRfFccZ1V+PlK+Eqc
mKvU4fzo3C4w8MGZHb3gmhYVbKfgdIMe5TffIkhgym/NrnzU8KoZfXW0ud+f
ouFNNmtbL8zcH8hFl1u0+ZIgc5fQeXJwdmCG8Ks1XySV7V6+1D2ML4+Wvmbj
3/xcBcznoywFTkwlf6BfNAouLHzQFgr8R4og2MX7poU2aoMyHDiuq1ju5169
EbWVJkmy+2Bvt99Y6fbfb49XV+tvUvZnIlj+KTaosyRZrL9FQPa+hOfhE//F
N7qsYHabiHSRjzA0J6jbuQSmVATaB+ayBXRAdnlhaQwGapSQXjI/1a34RWdv
l6jumNvVDf/lZpcx19q7KXr9C8++1t6D8ue/3ALcsGtBwCu4/suvYS04uCLu
X7UAQzc6liEjd8BhoJ6qOeZZjhMbIuoXlMZLfICB5VdSRZ77I2B5qSUb+Fr4
3bX8DhBiTeO7Fv+0e/FelhwmomHmYqPkMcy76U5k05OprjGt3gZc9jmSaLlQ
dWAKTzEp90PC5VVu7oMlRbQuJimhrIkWN+tsREG65VNwsyzI62RqekgUfg5c
ENVuhvB7E/ex0pRJ2ZzgR5PKpJH7uHwuxYfph8OMUNaX9PIelZairtAutJMq
sXkFV8zbWHgYxHlOu+DvOV5zbjijazPEbNNI4G1YA7QP7cMuPz7ojuK6xJpc
fANMaRe0vH6yndlTCB7sP7EfcnPPDRfsvOG+w6apMUXgUVl290XXLgL1a0mb
GdurkXOn8+Km570vPfWkaQwIjs3mmQN1Urlur1bv8IdYMjHVPOL020a5Gelp
5I8BZwcroCaunMmD2U8Y7Yy9UUJ8pJxxW9ba2wj10iQlwrailGJTtkmJV1Re
DjvcSKpNl+u0UpShLzH6aeXQ4HN0FyLYpon/lRDB1ie1iGCTzPmnq9lpbwWC
SNfTAJ2CVm+whKKuFtxwLOx5ako3FI20Rtd8kw7S6xjqzvJy5rfF9N/2C+q1
Sh2FnSwlVtp/eyX0bOdN7dASO1EGiw/eMNn/AbBcCXtbgzL1048Ip57wUWBW
WM80z2hjro+u/ggrMZf/9fG3UZi9C2Xv7bVQtomtK5CyUZHDmC8CYHG7rHn8
MZ3X8wZdwKriWL7NHE/zZIiZuZJP0tc9QGzs6Z2lVNAstgGutjVsEBvMdUfj
Fedq6u55/W17XgbGEsLU8+LzucJjiI9MZ7WLx8YfflA6QQphoowQLI+34HIs
IsjYhiyt1XMXsWRqwMt1JlxfJqrKZnqvWbEoyMR9TU1eC8NYx/X0Oqn8+HCu
PGV69PqvwsnnyKkHHrI0VVhCleUlWEbqstGh3S9iI0dk67mpdo/Nlfi/os4C
/tAl8CqLe1/dGTXsT+mMfV0JNmtdpO5EGpKqeHos/dnIMsQfv5+h97RvoPVF
n14Df0zYNpFkP9eJhL1MN5JJucVHEZRgb8wMysStAUc7g0NyRMLccZsz05nL
Q1kxXXDdDpkTYGeWVnxbggwWO79f6U8IeHMjWM6Byh8SGXHGdOztQtWpGATU
priNqA3mEHduyNET4qF5QM2EPVXFwlWyaZZKlfpAK3iM1wOX1CMp3Ii0jQRy
zezFqAwBQakrzZ2QPKZUckY2syo52bDva7CHZjoOUj/pL0jVhwox1ja5eEBa
AgL6xJYGT0vvPElO0ER9pT1r8zyb14pSFfnDyhrbgaSwJdt/e55UsXF1TMp6
koouaaryeRWpaW+SbxIsoFAk79oedmkstuzAHeTfeP91nH01e+9wUtC8SNb8
79aiQGv7IUyjo7Z4xVpFpxBgXAWuYqwK4R0W9aWkWCokYBL3ElRDKcslECHC
9LLOqW3DNqv4B/OaQlhLeoB2nwKBv9WlpHkG0q3kTvCfdLanbeutKXeqytQW
NUFVwcUtqUBlhTXXuOcX3Hx+ujFEFb9P8uBd01hLdUnHPdu1V8YPb0kwtFgL
TCdJqfRLfbkMd/DfbqGE6w9nchGrklrr6VlRWCOEP0QbUXxe1Dq3hhmBOhi7
Q2P/YSi6HHgdkskMJX1ZbUpVA83fMKEKkdtrkqwxQZo4cV6YfrCu2auoM1as
bt8xETNB7oQ/uB/w3aJ6aBBxyEWbsm2sG1tqczZ/JroB3O3Il5o6VeHVyrCv
DiNe+99070colgcDUy89UPOWZdzyj7Gd9PzupXIQoy4lsQglL7WqKXWqTcdx
c6ORdRQtuqkMCgStddOw6zSLQJumZ9TmdqOSzkllWKETpZrt1W1rDftFOIZp
wm4FANZlUHvoVprD100Tch9DPnfgijMMe+jSIpOrzr3E8gYiGgno7PEt6U8c
LtUopa2G3Omy1t14puEYJErw+YKIjKjtOngHJS/puwmQ4ffhAFd0DKDRbK/Z
8RtJejhE2sXqeAMru6V3HDv2MV3SoJyhHDTsDUfwERVYDtG2tl2DVmT6O4YD
tDuy39VnugPH+F/8r8RxWHO4+B7WNtB3VFX6p7XQh+j/jzPRB5WP17LRd0D9
LiN9ZyO8pgQW9rZbbpztA+qXa9q8aGKgOnOyj3yw2GnXIJanZVzUFF2Xahck
e1GMWCgPr/BBiDBta704eSlQP0AyphLQBXWPsKUcON+bbL7EXahxAwIivw40
alap8FNkXlIMn2ncoi4XhU50h+29Qzq8w/buv3Hk9Rq03XYSXych8kDnSdhL
teQbGjR1U6canma9oha0ugjxjQkomqvsQxFMfq2tYCmh/NzskLjModDZhPH/
J9LaNdyBtMibun0IncgcnIhe6UcJzj/Ea1CZkw9hnxdbiMS31Lbtuc7I4jkm
qO/3eXGsNHUnTkLvBrsg6BnSpfLkhixhQsxYo9Ce5adDEFrfLcC+gBbifYFb
wNyk9pXFS7XWTQpVlMalWnWTgku+5FKtuklNM41d1fo3qf1k5zUK2pOud1Nw
KFEn5oVmJytsDoAScyxvJaWvvE7swUEGgplpoWGp11Lk2ermaKQTdpGNbf9l
LMdHgT5xCJnQUGe1gOW2yxjNXQm3qSpJfO2qMxlzQe2QeAMvoMKAAJpgDVx8
aEJy+lQKjpFsG+sqxN4ldFvMGB6i1WPGtV4Dk3J3uYw8wvoynWrXWCEQZdhg
KVhvmBtKN7hdh80xzhvnTte0bbHlDpndZqV/XqeFHyH+316L//Za/Ha9Fgy7
34Lboo1P//8s5h2cyprMQ05L5vP/NpnfbTJnk4pvUAmbrS+3qCCDaDzLFhQK
5UIky5vmkiO2iliTByfyYO8pgKFdgLGZpJXZPJEH7AowTRbY1zf3fDyBI8tr
0cBGHbNdxM4+Nb3t3N5Krks8lxs7jYK3vRhXdw86jSHYUAlX2phcbug4S2y/
sxBi7lhProzVWRNaJfMFCn9tCyGb8tyL4ZQGHu1jD+L217Cjhc+b4K3mmdOJ
oJC5SOB4Oq1oLg/swFD3NjNA+AhrCSduVAo0wfg9L9GgZ8PUe14Ifs+3pPXs
0oI49Z6LSsZ9uEhhbD3jd1mlBZshuhbOiWuG4Hrrb5AHa8uTfm//aAtjuDhc
UmNFnTbFIKZaA/GdSO8PMil6N9WzLDq/FqF0MIS5e9h5aQMvmSVafiy+u16v
wlV3e+4CjxT+BHYbl+1CR3inDL405N0nxTs7ARo65PTR0CFnUk3cjffF+OW6
LK6zcRk79k5EgUzZgTCDV1JqvC6PQ8DDoScdCOhY0mm3YcqfYuMUhLIUZTEc
wTuZcL2wCf907C8cojsNgE87xr5Opq3fygUImGw/KRvASDvqCA1syq3N+EEv
32fHHe2OOcOd8F3/mPFwe9QmEJSAcXZLVLHd0D4cwOtuv4XNcretikqtc6XG
tCmay1XLwxG8rZ8e/CSSxBQYR3HNchWhxawGubGPGbdBrxkBLUj6mTUwbcrf
mw0VF3+6YgNNo8X7D/ZGHftVJ0dmgZr3qLeX+xjNWv4mjDiwTYDseNSzuUWd
73JERW2fSN90heUVwtdX6bUfBH5XMoz2huxsKtx2mzgiGqwhpKLede2UUFrz
JNhqnvN686b0i4LYR7YpO9A2Lsp0oI65gT2OE9hqsPZ1BlfDiBJujBW7lRRj
W+DW9rz3RB1TGLuDmrRpSSfeLKG1oFd7F4koRU3om926Lzrqd6+M7uqoBN5c
Hj7XZD+LGC7sxs7sZmTKmePvdhT8A8PCOy/Rku29MvfWdBexo1GEubn6YQ31
QOfBGr7itWLbHJkYPWuPxt7oWOAZpKn3Vlxs6sV0/jvts7dpAObQ3QIbQ9za
euuca8Dr13Jc0s6Q3e/GmBDIBYhl5kSlO2Y8KQutnQBkRJ/Nuk6nYaF5/BEO
Y2nhtBsvO+Oov7YdLp+y/ELCqJ+29sT/IvCXB9+EmsITM1wzpMovL7ACp7py
tDjD2XUubcUbYZRFm7gvE8SWZWIbeLjfV4YZSXxJkFXor9cY9r3WpSGHJGM5
6ibOzcbIwihIO4O1Z+LXsh09wlFsqL8393IOZEkJHV0gtvsanusK7DMp0yx2
qZZnbdz8HLOxupQmmPO0LLnzrBxlYnsF+ApLEkCU+itsbbb5FLUxNW/thGx0
G+5qlpmq7pnlI8gI0uucsJUig8z73DHHdBMvTIbXJPEamAS74XVRv9Jg6R0P
efVH6BCnc9BkMI4FILCpKdDUo0ek+EqUGFtvnfmT7YjobMJ28ADj1HHzOySK
5dEW3nInrXDATAwQ3qJBEst8/u2vqaGgWyxcIWXcoRY0SQOilSdiOL6+VGm7
Wy1YwS1DWIZ/7gRrVhRBl5KDiFGnmcO3hLA0pcwvFhlCcrA8FupukryC4K0g
y5alhEK99ytBnlCoQYfvINOrCXUI0eVrN06pJgq7UEh/O1bXbIzhyLgvrzTu
dtvn3RyFbvu0Qa1NcDDIBrTKTSu4NF+HyTAFDAM1NpFKbjK7p7VIOBq7EbAg
UvNl2HquUyZM1LAmmNIHAtmSW+/DTb+GBWgJ55sknOJpSB5sSiI0wl5UrWXM
/C44TOtRVqtItTXOxyXczJNX8Keb+6+417SPNe62h3M7OH7LCnTXbeel+n/d
gZ9/szixUqBoPmpFd6NalYhaBdv+/SWE6lkbnWX3qQmMsN3lkfc1T67jDFdH
3q9NkcLY9c6YinAxS+LUl0aq3xWr/rfQn3bAehPOK+PXqXuxuB8lU5pOvTmI
RLFjgj6iRzz9c61teosLVF7qwMMfo8r7DlMYKzPFbGxcswtlHjTHWE095kls
XEI2E6JNBgV01q7VjGsPI9Zb768IYLcx6z3vAi0FJV2eDGMe7YtmJ67DYHv5
8pzcGof5XkJIE4maMu7yu+X/y+I83Lfof8NP9Gkk5oMJ6Ib9eVy+T0r93Qb6
PTf8b1D9/W6DFHdeHIZK8fy/d73SBxhKtQGDI85hSaq+KcOGe2O2nooJJtAS
lfTJLhPlWndHCArXlY2dDANeOAVtRaZdPHDZ1rLoFuNTfdNpfnewixCi/qaL
GPBtoy7zEe5phK7DuR59nGejXI8oIKxzUAIx2l7Tj+LJI/W2KK/j3MQiUS0u
epAOT2K3NsxxnGC0T55U6kBLvvoZKRlaHdTVDEhldSvE8LwAWpqN1MnhwdlZ
ePi7APP76g12qbwqYRZ1VMJd76mLGpQEda/ZT/pFAaMDhpNH5/BAqcfD4eP9
/t79ew/CB1/npGRwsT28jwfzBHPpZEWXScZ9jHfVvd0hzLOr7j8ykx33T+MU
vke4/N5UENsg+DQpIYGob0/6bsSw8fY8lXX4ybI4IyCtJAoL0wco2Nk1gBdM
aSAYH8jSnHN/fEyyIvcS6zaWo3id5Y2XuRgLxju3VyX3Qd0kY5C4EjPyK6ZS
WkIvbozMpmeUnzFGCXJK1jR6+0MqlQESuFeZ2gpAve0vF3WomwJbEG5i7Odm
j/9VZy/p91fHf3h98ur4CH+/+PHgxQv7Cw8hj3EsjvvNvX748vT0+OyIR4BP
VfARD7J5evDTJhca2Hx5fnny8uzgxaY9kWkxqTm8pKQNjhOXYolBM0IkjRWO
jvLp4bna3VdbaN7a2919vM2/Ptp9uL9NITQ8Gxvn8E8L/Vv0kSdxSXVjssyg
i+ZaEDNsJEq6O7/A/z0sFrdcJmVrsq2QyqmT48tn6rLEMlLWlAhXF33wVhdz
a4/pQmsX6zRN0OEL09OwHBqJphqHDlMUCNBYmUoxWDQSwpol7g0/wYbWrO7O
sWktul1MPL8JzQJ8tDeoR74mROqKCk7Upa4xVLoqGFi6NnHbDlUz4HA5Wifp
IhkehEfAPPAV3gL4++nFkXohz+pEws1gYbAkWPOF5CvsDyYGBA5+m1q9SK5R
pDXmAm1gkHGUGyI9Pn4kiCLfb5lChRUOAyIl3l0qViir7mPUy/aAKU9oHd24
s8ghMQziBuhy02YQufSO0y03eZ1wOKh9aWWTyT/Cz6jtrSCickpExVUSs5XT
2rEjy1fTrrLYyXeD+JFQ0DO0ttEQdK3arWaMjjldJdd2CVc5u64yl/m0poKW
Gv4BnPQDzoTtJ64ISGiI7oCkCFDYlNUvQ7csOKfLwHl2/Or5T+ri8uBVY5e0
q+aSliKDj5j8Fi5qcF182OnCgEfD/iKr9det+dFQnb94fWGUSS6Zdei/v84q
J9h4MdGgmg8mxXzn0RAX1LXYBOhu9bXgpWR+0CEnSCem9QSjTT+k8AleV7hl
BxSASHzksigy047T6qVbT6kN2c4FtbnZeV5k0+31DgFXPQA5rXNLtYmxz+Jx
kn3t5l6b+/4CRxmp47oErSvOfRyWDd21ZDQ7ZYNkMkhwjBj+2YH5QJ7ZmRXz
TiKS/xJbODxrbOFwBpfyK9bv8J6Wgyg1mORd6/7L5CuXSiv7Qx0TwTi8+66u
dQn+MpGlWjT5/FWKVZey0aVYfaNeeraYQyBrAJlSYnOjH5FpFdcJpU+Z+udY
kInIJArY4oO0NiPNTnQyz0llEd9rbiLbgI3JxCjPUBlN473sSiKIPJF+Kxlc
D3rL25h+ANbS7g67jfLITULSF0Wd+uHFEyA8WOD6FoTGK8xcbleb3FpZmpF8
KitSzbbxiUiA8MXpNjYPuIjiD0UKItb7hBjdEUclvqA0Axndq1m1dfTi+Hgb
g31K7IDNWnSYQtIdokp2iwSDJMKcIVv1EZ81xcqkeBim11xTzB5WSmPHA617
YNxW5uMIzTLNcMyUqjpitLixbVjAgPYEyGegYYwecdS2hXOZRhf9iKhYS6x2
TskKaNChUmxSUc2UUSMNwk5uVpMhalNCxadPCw00mu1Rnz+jaoTDYOF7WgEF
kcVzQKdYIpc+ffoBBLKH+w+Gnz+zkOv1gyfJaB4vdOQKH3rwN541E3srlgoC
pOACejq8GSJUevQkljq7MdkS4V5RlFuK1noODPd1V3LQXqUYL0OWxyeRZ6oy
S4Cz8ucBkFLJRt+qRloWLEvm8Edp5aB5arNLCX1iMxrC7C1OiGssgDJ14Lxf
Ly7xa2cIk90ZG45B8BivOys6lNUXRT9TT3UcTnap1M8sjMqrP0c/91s/4Ufw
iEoKPjj78/Pq+q2Mxysre/KwDLxDLjkIHy7JOPcfPrcjLMn09R/2MzRvCYo/
d2U1/ow8B4huBvzkFCR66XlhgddCW5Hsjb2uiQN46IVEtNokYzjcf4ERHz/e
3f38eaDeUFkDwkckE5joGGYd9wj3zMs3Jbadj0v4QLT0+ApzSTlsbvdRROnl
QIlO38wM4bBJsTPU4HO8SQss5WTDIspUv6ckYG7AHkeUcMhE8RpfrrGqRErV
WlppdxKFjMI211LBLNRIMlKNo3/9PHGyg0dBFmVY8hQXOiuqvr7B3RB1pGcy
zECaoAsOrkSZANYlJfXqwF4oYTJmMzGE8ysxjhwoR84bjywp9WkEkwJg42kh
YeLVTWH6o2hjfie4IFUombkiHSbaNpklk/fM89vYh+6TESYkpxQlHHFFyWlQ
jdWfTYzptoKr/+BcAlIj6vrSzKZsZkm3F9OjkCwMHdNJZMe94bKgyaQmd6nd
NijqSZxpk8OLrQ3olmCCj0BwHgXb4Exlk93b3JnCaF5bA+0JsZcINfr+ea0N
o3n0YH9XGI22I8Jr1ymWWBFfHUfyEMZF9EgFeOXZL3Esa70EbohEvo+4fgX0
BGQMUCbwkh7wriK+a27R5gpgUx08YkqvQLMFCo+mEw6hAOcOfkSJgnvpgJiW
ZY3bBaTaExGlvDBcquwmvtXWvMc+GfFz+Dli6CQG2gfyeeSkU0yMi9GfVRFJ
SnX4mrhrBDGwwmuBDodIshj91FM/tdJpE+TXrkiz9Ep1RVK2gkfoTNukxAkp
U2N9q14yY0SRPp8+wVE/eHzvHh61OH+C2Ed6AAP1gFN6oQOmTU0kc/PlIiJF
BhOTUep5zTtkNJRhPSHGbYVcnfWiuWaOTuJIAGfW6bEbJi3hdrj5iLpiNkBr
VlsU100YBU8wVBtLvTMxNJLSQjyiLafkemVZi7l1pnWliUZhmmgSluW3aqD5
wCTKOOdhHDG2+dV+u9NhekuSS9Eu1qU0NZNOOzJNn3HmX2TlWKmyUqSMAh/S
5KZHPQxMurDk7JnMHDYqR55eR9UbgA4gDWeVRrHSAheg6vsPykAgR05JHTZy
JNwFXVM1DHv7Sb/yZW05HdEZo9WXMkYN0xTl4G5SQFvIJkoUVNyqKkHPbk40
ms+EoT+uJ++B/2N1bqxfA3dTAwKBsJ9fG0SsElwa2hFteiYXjQ6O8UMaU6a/
sSSAStbQgYGhYho1Rc2w5RjWtwkryKdZ4vfSQIAQM8NSffhQfx5/7PthFeSl
Jnwu5oA/JANnmXfjgpX0IiTUCC+42UTxrSkjKwoi0ZJZimdJ3tNkjnXzUAaY
UXkmDiuQcJAo+uYbFxTsJj0JIphZTnz+6vj4LPB7oW5O1fo7orvlERYbmdJF
iOf2AReBHYZLo6dkXgjhqmZImlwcnOZ7HE5lKQ/dI1SH7dgjtYmGls1etGlC
v/uUfGD8UxSC3WOZVOKxU+2Cs8g/FUns9zi5LTDB2ajQBoYIHJ6GKKzRcpCH
U+afdhGU5J4Lo8d7EfXBiTGpDTN0aSmpjTStgP0ybYR92yBHE82DJLW1NbuK
hICTcDVJC6UYNVqTWoi4kMFNn2DTF7qFpydP5dQMAxvXHJElZRTYFsOZtHj4
kZ9hzVe5P0/H6iqJOYtPu4AIMW5sdqQubJqOCoEGCr+NSWuQxAKGc8ThXoZj
+CFLIWpMXIwUlxWRc0p1FJwJ14UggcUCjOAHh+fQoljIpQVRw0ds4GwFL4Mq
3TfycZrh/15pEVYeNONiGBckIo0t6YCXjXr3IUVmqkeZ6FFOFI57aORMJJA1
sU5g2Z2Xa2BUufsP9kD6kHo9ndkGRB1OPa3jwApgsF5KLbhg/+Rhhs40Ry9a
OqcYtyhCqSjTa6LfpvfjDVJdDsUpTFoLMZNI7IJI4GCEWTGFzdENJ0nJaBEV
l6/Qkslo7IUkcGhkWNTAxGWSkHnU06b4UGwXAKuNR+a+xQJXQEwMasMEEk9G
l/MDxJmmHJJJ6Sya1WQsx2EkEq8csVMoib/+he3TPYJ+DKqtKavvcWIdIfQw
NiDVGQvkLFN5lJkGo+mV0+QkRFEjZ2kfjbVa4tAdpQutcXcSHLJcZZ6LdRPd
sJ8tSji80is3gorVdYHR6oCZ+ASu2TMaj6Kor16z1GORbcSY5g1C1SLHiSeJ
k77sn2ikSK3ya79Ma5Ku5Piv4OOausuYNExsQeg0kB4719ki4DNsW3uS4lD6
6tiYrmmZI/U/Jfo2Kcn6AxysqK9npOZI2RrCY+y/16eAGyDnxvytRyzq+dhI
R6pnCTZbcf06jH+FnBNbIB9UhJXIAYWcW3oT6zCYAs9o4ySfMKSkXPaBq/Vh
6Cpj1TN0iWNlkA2S4ibkV2bniq+FcgwNPNHHJ/Tnz1x8qi+SRAWn+M5Kf5p2
/Y4g8KNcKR8G6LwmSQUQqHGu1kJpriZNI3ZlKlwBhH4OJ45W5XzqlajsXoq5
0byYF0lcUkqFW8tzVAxMfb85kB6U6tEFmktsGtIdc/Wl6IxvWycSh/DLCpC+
FqTQ5mKtppPgW9g3/gAOpnDpWbjhIxMcAqs4OFGXpvLpGxlW/4JnkzEI3iFq
n5p67ozZR612vh2klMnGXzDUhIJiOG6OuxwzzrNndqT+bad/b/itu9ekhXOi
jim+wXeEXLj0/O46z6Ovl56+v8bDrxJ+dm+NZ1/miBAHrjkxUpjVDYqjcy6a
D4fZHxNWu1kocRjn0nOU+GWmsJkx7wIUR2ztPX9DQgjKh/fhD2NZEKZAoxjr
pRxMXqSaS2xR9ERERV1Iy986OT5UD/aG9+/1FP26++j+sP+wv78Ncsi05OI+
KHzdmqJRsKtRZAWA79TpwR+3FnZ3/5lgSlcPa5cXGSDqf6LkDtpfNt1mPmG+
UPYLKkmXfkRX4bv+7ruegv8O5R/77/DdNoIZOSguylEwcpwIpSLmSRFYBMSR
s0Vrl6XSIwdnozamVziyAXlajMQgE+ZFjUFjMayz8yyKjkWB76uDoJn1u7YH
9Bp2T8OL84PY3u6DAYZ2qv73Jr2v0ZT6/mD/3kN8ghpTPxwMH+DzgJlbgCLf
qeHg0S4N8D38Otwdwm/eGfThw91Vw8PX+0MZHH5/MAyGHg5p5t+1hyaLDAEI
8VPqYW0jOETksQhvy8WKdszbfkO+3iQQdEbAFa5nfdcdPSAwk7gsKayvLIA/
cA188RiTxdx2JkIVmata9UnCdEmJ1sUJ0sbiusRQS2I1wC7+KisQDdjyUT5M
bMvb3lDEab9y6jWPqLl8FHDrCQv7fZIuQDpFPUSMAjTVQV0VLEGQXcGmDV+j
/I+C/zVuB7T4SDm4a5HqyCpr1ELfQ2ChBxMfUcEnXDmaflk0S0RdwKIKpt4T
A/D86HWfS+I1JKotIpTbxqqDNoUSASt2WMs16UGg7dvOqmQmjjjQkKq+GKPM
Db7sGCIvFsU/eafJ3e7gbQBnVLj6rEBZvYy2ehovHEJyFy0ppUQ7R73/miWr
iKMqvWJbrKspNF2pe8/Pz03kyH+cn/j8PIjNiCidm4VIo9AhqhTjiqGPXydY
fbToJ0ieWE36wh1HvsHbC8Qj7Y/UgkaodRB15/VWB5SYopELjo0l+lAvsnjm
ZPGMGzayR9nvvU5WQpKbxWBgBGHDgyhim4J5KC6QlU3DqfoX8lQYsKMjY8k7
Xhbtx1ZJktbgAhTXuUSGU4JL5Afs21iFxpJg0BnG7WibT2TarUWwHSqsJkkr
eAEXHMsMZ+d0B1E8W9W6gI+5TOSxEXKt+XGqQFEpSm50EZA8aVADHD5KkGyL
+bcsQF+vqRfhcjXQZLF49BfkCTJiNyEH2FiiBE02UWPGDZQfn8BQGb8InTZz
WEx4TkTaTbzhVhBwiKkGenuk2gF6O+dEtev5zmUKJ5JSM8CKCrtYYHkRZnGl
9obf7tyH/4Og8K1CSRj1MReZCdI70ihyJoD4NXnPjffghs9l77deB4DEk8AX
HHSocbzz44PLkfraiMSoOxYRB/6CMEAkauuG3OGzfzg0339B4FsUeZVtwqBW
PZkl6Ko0sqZNcDK32lAUoAKO1iB2BMMQWpIY5tfxt64cDC32MC8GjmeaMmu/
5wVXC2kO7hc9NAovWySYrdpmiqy7ePvuaBIVe85FL9ESdGn0xo6zFDRyu/vI
KyxoSM0gMJx5xVr9hTkJB41dfqgbWbIExv4FJAgGiSYidqC4EZrL0BOf6jme
wn8kt57LXZuWvnRLG0DUXrEEluaoVrfjA2Q4Nl6jMiGeBkiuOVhKIGKqIck9
AqZ5lUxuJ+jQ6XcDBjHrQyyeCp5ADDawlnQspSMizLjzb51T8rljMItgU+Ti
UzFTdWzxmpR62mLD3oVBBZiI4luCcHftYvG3HI21dENeaVjn4rZ20NhzqvIE
pmA1bYPtGezOjqKnVFrWJET5eC730aKKTjGWjIOWslvLwFDcajhjrcKCpWKC
bbELfxZ/6MCPkXpnYtDRYrJlSLxQCwx7EJeuoeW8iZ76/rvHoGNbGouPAeWG
MZBs98LSnPbCMl+zDkLXthSN3beS0MlQ2m6cg7MedihgmijxOxFp0aogiOMu
ZJF7dg5mYCbQQwSuRnJDkmXac4UuySkNmv9EcRuhtpstbceOVFVPmPy5bVqP
qsxPQTSz4kY2gtnFlARFLQI4JVvc56gC+vIMIEQE8lfoYEbzZK3Vp29CxzMZ
8Gr9OYrOsHituGYw4Ox4ilOMFDyNkh1Wt/0g0Yza+aEluMrEV8P7Ejr4eB9d
EhJ8sgA1wNmaD8pygmF51rvs9RTnKorwiamB8IFuSjQt46uq70nNzUjrPjlv
h/dR9EGwHJSTlxeg0F5V6D3qodWB7xXRBhfLQzTq9dG52HQusZ4CuaaviF2Y
kMvowvfddkbt1NMFR+58/owSMOZO1SXx60aI96UPQ/aPJeRhpuAe8pUmczYN
B9Zek4x1b/BwsBtRlCbF8Q0f0oyXXXHFvo/XWPbj0LUQB62XI3EeTCZso0EP
OkGL4eOFywFDqIpJkWkXR3F2fHn48uxZ9Cd0Oe7t776lpbw6vqCPFX78aLg/
fGuk6s6BIzuw2trdJuqFeIlqFJYInlBvDHtMWXyLFRE5Qv3i4keae3/v/t7b
nrp8cUFzPn60/+Ate3b+8PrkkD8bDodvKUhcbe0Fs0TzmowqmPqH1CrwkZim
xGGRnQOCljLFbLhI19bZweHpNm/6HsAiCsJqJCW+oMhF4COVgJzbM2OUEFo+
SgNSFAksHGGRrNnFRBxcXDCyHq6jh2ZI5y/pGsRA2ckk0vy5oOJFvN+SA4cx
Nu4GcJmdL4g8eTFNtB/H1sqkpRhGYWoTuQG4xITqlXwgcexDneVUAlMSJOeJ
LV7uyQbAmN9gSX5/pXLgCRCpPgNgW4iXDlZoXK4LUmAJteQWIR2lU4dHyVj1
ITHNEYvcLsNNSRzU5OuLord+vRHyCKPR/HXOKaWkoN7QtuTgTeg5V9ZBPZ5C
s+KqQnWHVTmKyBTDy5rFbzrCytAGfkQ8WrzQRHOwXFbVLSubVkwcnUVZ2ZRr
yixvii4+67cykAPZpoxdAeAtTjRjewLMkmOCJaUXUnDFJNmm4ClMkPWCV9Kc
sJyLGhGpmsZzoBPaBp+Ic28e6/e4zyK/LihSg6CGpgOUVW1SiUmLR6tIqst6
gRqiV4TO3GRzFhaTTE+DceKV8YpMfjAdZlAETBPhRAow+Eq8mcSLHZrqb8Ya
JAmYdM7dIUCi8IqqtMt090TkJtQoDZikDggawVz3w+4j9Q60KJnCkegQU+EP
IguklVe2Bl7QjZ40Nkqwv+swYJjgONY7jItibtsqmCq3PsXoomUtMhZ9FRnD
NhMU/1rryPVAdmFrtB5zsELhcOUAlh7+RygdobwfMdZJ+gbqwoQ8ZNltIx8m
Ak6BIZlM8r3dE0X02I/Zp/Ppr4G7pAK3ips0nuS/RiIJ2PWgnEbtL53ITlzJ
dTNryTiBj5aogaelteOH0DEHXAvkyJjjDXCSvo35wZUHtUddpCEHg2KoeaDI
G09wz6tAb93EHM7SQ4kFRX/1ocjquXSzoeZ8aI+RQu2esSKiLs+CpgaZxsks
pRr66AdkPPPxi+k0bd/rGWGoNi4Eoymn0msBraXIT3IUAlGxvaJ60R5ie1vE
toEY5oGI6Y8uSMpxpRQoCkPUVWqyLHqUujgh0zTmMda6glVjgxTCqVsLu+3B
3bjlV7YcScE2KkJIKKMJZ/zi77K4u8qusxBI5aaJorATLYz8Mg5aDwOIcJka
tJxscC0ty/kSVMWCSpD4FA3zgLKC2ruZ6IfWYSFX0Tql+hSOjqe2huAt9w+6
nnGEszBuu10NGM++eu4hHbLhm1mhE0vUi5wDwNW4RFwFmgQHQ81SyFdh/S22
v2gzEq470G0gOo6tD2K1fXFFxPmtenV+6At0MCdFEPl0jTwJXDalU4ey45em
Bgs9C9gs2nAjiCme2FG/8Qs0UA9uxoJXJ+pVcp2Siz2i0VLtCVbEzfBrUdTc
2PCmdiE5WPTij6cvIjPWBqkB9x48evSW0uGepUmGmWMUYaS+9Mdly3Vkza31
g7lpuFfMoFtZQamrWpRZg4EUMrFDrpNEaX1YI+Ti+Tq7QBjRGs52Dp4IRzag
xuWlJMvgQ7bi0yAYwaXLEcj94xupzsVjqtw/Efw7y2L9s8C/s/zWZ3evqH3b
OpfLk8XMJYs2mhdYb8jrwKk5a2e4h+mrbCV59Bh/9zwP9H507urEuLcpZcS7
pw24rY01nVmtX4Q1eEZEnFprWH4z26d86iq4gUKE0P8Bz3yNHZgRzmzBta+h
FzjCOVdco7UnxZpTB2twlek5nRgL73zJCA1cbdH/LyAcjaH/ayDEUlLRBmU3
Qvy0Nii/ACE6V9VECK7Dt+b0dg3/QIRYRslAjkAlNWNXgZd+g8EU6tM3sfuy
TwEWn5dIFfF02qB5SQ6yjak5ztkd+Oa5iJw8A6aU1Ow7kxggI4M0SjfSu/3j
s8uTy5/6mBcSJPVweshICkoq6pBo1r11+fRodxs+6/cVS5jPz1/31CX+5wz/
A/t+dv78gFKfeYDogPV6AptVwMJ0IymB31yWn4vRW8Eo2vCyriUB1tLJpeBa
TMX6bF0wMjGhMOlBwaWzeWcslWUp3MUMz2crtTs7asZuhIW30qBcl3SAdooq
nSy6CEBVMiPAHyXZRuxj3pr8RMbnZbyYoVvyHENKtPa7Z2K8htqC49vGvJJL
9pO55+T7S/n+LKlLCSnHn9ZzZ/QcN4VBBHBRsRZWiBK2pmmry8WXlE9TUpPH
uqkQNUYcEkDEd/dBz+Y4Y66AqczZujORaamNuUzX14xRaHRHPGfVoLWa0Ot8
Se7bO9QE7npisUwkCxSjplG7w07HBBuBsNJ8YyNqSSsNlctL45DKB8pUUTWV
/Bok4l27FNM7D2l5Je86aeE7Vt78qil2fXwUWvrruAFJpGR3h90cjxYtKwBn
6s5dkfUkoVbjXqV5W6gl6i5zu+GTAX+ViVfonEAW1bmLRA5WbD0PXt05xHRx
pW8P1FkREelOJ1QuklN7OcLcYiVlmxPKMJAGFp3gWorvL9VRrIXA6aXSqFpf
/lgmfXyBAOJpHbcNOeTn9a5Ng3M3NrIeG/d1Hxr63ITPwRDHH0H5r6i+Jdw8
8r7t7j142zHEgfWPSaKPWcXrZYdPxRIZj3VbgPgissHipEnbYFj+LCs48jpJ
rAKDLwG1znatI/UfQpAYNDYT3F1nMDg0KnnjXQweZHmBxc6Tp0Go4ODPXx2q
5w9I4zWq/TGkvyRsL1wkwSpvjrl2XF9r0zTeXyaN4/3isL9wSA89hQEI8qUJ
VQw6g/uRcMcZ5FhrciVL1yUVMQovnAhwcOUomRZI7BFFFlBQBz+6pW3cuc2+
jytyLrSDcVI/DDj2A4G5ApyNNeLANcmJGRdTdHlw/J4Xi9vzQvCNu4ht0xiO
BvsBJkCBsl5w8aBzXWw35VC5ngS4ZLfivMHgSSfvmAHQB13oFkNxnsUYwQKg
nOfJnHBeMg8jrwN9QYfdiurEkYBHvOFSRChztBknyZ1TyYWvPBbd41eid2Zh
75w4rKjmNC7Of3NtKcDJ5xibYAbVbpzlM0YSXUCI8Q6Fy3cj/s50fnLSX5fo
gmB/x+FN8OKJZA5zTv4VoZLHQfA4x2j3n2IJlwlh65apdaHMLO7Ld2QlLzAT
KvGfNU+ab95t0zI8ncBswqQykxZTZxkjg0mE97cTKRvqTGnEagxX9iroN4Sx
hJXuIAh6AgQN/f0vSBo0BcSlYJB6uOfymCn+8Z3F2uY6DbKTkc/0BgxwTBa5
SV5ig6ZGIJV81NKJPFH02onp9IU0PRMxzq51bEsfuJYk0kfANtn5UuKFbQAX
U3L3edogUsNbrnfmFyLAr1Zi6tp3w6qgfJC+Bhotu3IpZZ7mNkUu+ZhqadDc
1F1RTFzTvJB74X4t4EUrgTdqhmtzPKt/XrYmiw+ZqNsY1JTJbw3eUcfoJulZ
V3lykrXgiCdto2gtp99zhopVC7NHIq+hk9cLfjJMl/xVBxNMes+S6TUnW7Fi
Rg5cpjI5vGi7fAsdJmc7RizXWrM/LHeZ2xGzUHWaJCQ+SFksKU1/k+oZAyfO
ubbbm+d4q9MSNKVXxVi9SbMK8IsKPaTJdaFeAE34K2tRwuhMdakSw+tITcOo
AVt1lFpEoSUBn8GdhCsg80y4DDdvL5g0uixyEI/SnjqHQzygdDWND/0BwPim
7qHMM+tf6hqW8GMdo6f2IEs+8u/qWQIf0EYO5sjq1dN47JoFpaWaJdkCK69g
BR6bblOSZGLzzSNDktDl3O8rzCbBc7NB1BS+R/5C9fA+ZkgG0u+nb/y6pHK6
VNdwmn6kPgSawnbNy83SgRLtKYXJgpKoOPAuWSauWN4pahDfKvWQXcjnR6/5
QPAlaVMzI1cxBlJVM9cZiqLMgzJA1jfZVdonqIAiFTBwKSoNOwf4UwalUTEd
Ks2y2jiCR15Yj+zcFrLdHyJULO7Lplxw5L2HDzAptfAnwzX5XA3A8Xj/Www8
57KTszgjBhid2aIKnChsQ5SblTG5qCp+c2+oplgsJpaKaJR7xBVmGKeyWDcq
FPaCbj/t4oUSK+rZJk1LLQqUoKJSaBqg1//94uWZDZq+TyU5Gd8AU+FrL1XZ
I3n+F5z+7LbKfa78ozGzAfWh2USDNX14/gwXMEKzZrfVZBQGZWyMxAS6EXwO
H/9JDHuu9xa2gBypDUKmjZ77uKNmUOdztBQ7oRlzRcVXHAUQDH68YZa8Y0rD
4DuAdK13bIGOvlkGXOjgia4ScDhad5p4ODqvAfNwChz68SP75WcPAGK3akCg
szgtTrz36NGwY/ed9Wnp+YfDh3vt59sYTQ9TKfNhf7h7ORyO6H//a6Nz1Y2m
DYAZqrs8+sjYGzbUW+99P4zHwyvCLdgNMHjCFhvXE6weYZvQcf0JnxbMmtb9
uM/ktP+w8XzwrrSBx5eQNB30LBHeUJ/VW3+f7dVghvOdaxGaJsPZp99GDUC2
rpF58e6L1PHkV10luRa/CGr+fVDt74AqRISWHU5k/vpsugREz4SVacMOe1SX
rVkpnXV5jqFEMk2VzkWk9znlSDhkXzjhd2pvX715Am+RhmeZ4Ei+35Hnv0OW
2PNqwzZYHsVz5VdpOVeW90kd4S04nB6cDojKMBwQkd4Qh5xtP5G1MkOalvFN
HnDuHhUVqedzIz9iPXd+uNlxUALHRrQbm80WiAhkeORNme8t/5ew4VTkh54N
7LdlELj2gFvtIqb8FbtcFrWUmSwUMIL0mWdElC0/9fOUS4qdg/m4+hMV+Vf2
zUjelBq3ZFrg9E+MEpWgQJQVuVqmuD0ozu8go9oElNl+KF1Dtw4Ot2VJJ3mG
McDSSNpLp+BsHUqaRphxXR83wtHhNq8vFJ5aFV9J8rEimBRZcU5F/5h6re05
mKd+7VhW1+wXRgDEQq4YvRgC20YIYlbYLfUgup5FPrabuGxb1qVqHhh8+fjR
t7ayvbdl/Gb/W0w9A2kfA059SdwItlTI4ibGqUxhau1aIlit0yRfcmVItJ5c
U0Cp16Bh2nYFcFUFpHbyAqmKh5TPgYECnNnxhXl4VuvgNLsoTLP7xo1Pl2B4
D4cd7iMBekWjiLyYp1Xf9S2QpLsRF+ejtAJQZ8Xe6XoXPIlMp9iAfUibYSe1
Yj4oiKPS1U2qLg5oCeQMtSn71AAcW6P7UmVP+gUAX6Mg5WlPYsu93Jo+d6G2
mpF8Sh2EyfRhvsVPcGauSWZTaOx3Nt3Q7+DJqSfG+IMlcij9Bq7LGJUsDAiu
4vc+4eG0G1NtqpX7AbDB+kq6Gewstxs1tamzHWsxQIbXlUxW3d2KGbSOKRpU
+jGIhKAyfKTnjqjGMmt4lAaEZVrxbAM90Svb+sSYY/xBrZ4Jb4YFZ02iozGC
t4tHWS5oE2D91jO2shRqxiATIP/GalL0x3BIJaVUUFLK05iMDUkqY6oWrlP/
DlxaR5DxyJTPks3SI0lckjKLFoVRYEKm+8APSvSv85QaVtIKWfRN8EK2lMv+
ZA8Hu26Moyagt8uMYDAIexudsbWP/rH3vmBgSH8CEgERiFaOrddH09w7r7go
CTHcUlMCC2h1q0aRQVqPXJnKhLhOJnjk4mDy1UXL9omW3WdaJrp4CyZ4p9kS
SakIMVa6F3szX8/RciIm5Z7IDHNXI6LuUaym9SRsEDIxXUb4zeA7NDx9IMYe
U7FPJpFLuxc1XzczIhgP7C216V4jjgpJGRyt9sp5k1ThXeOoDMrM63jQ9C3G
jH1iKI06NEJ8gqdNLYS+ekbcxENJbse91TBtbIfb8cu998Ji770wA8QgbWNR
tiI8jnskVlwameUyFJA6qpt/JQVr0ifJ3vzyoneymRVl72CBy1uLjYI8Kalk
beV1n/7MXecZI4R4rXt0eBquFFGJVO3K1pAkX5FViHBwKn+di6isWAs5hjGo
lTI+wbJZmnhTHBgR54BtgFKZj+yhbfvqUkruhflYI2jL3i++mcjrRY5zbngR
bRuNML2evaNehAGit9wcL0aAqrChfNMIRWg8hp8xvEjWEmyxngt2wW0Zu0kP
owbofhz6zZNnpu+r56NYRZcHVD2PPRtO9OBlJOuQ4/tEjh9E9twCwVyowGU4
oTvakShV17WpxdOQ7K0S57Xh/EI5h/bi3Y5ItZCkw5iypGi5kqLlcjrtHENO
ppBcanHwSxArVS2goaiON1U9ia+I8YUK+4han49c6yVPmqk9oRpTe5d08/HN
AeFieB09uuuJbXO9vF2V34UKJ+V+y4BW7hTvJj/cqwY7SIlfRhullh0m3OOG
tHzu3DO1bVT8ih2uXLdyLXWw6F83IFK/1VCTN3ZXSbEy6/8DvfyJ8bZQAQA=

-->

</rfc>
