draft-eckert-ietf-and-energy-overview-01.xml

<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.9 (Ruby 3.1.2) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>

<?rfc comments="yes"?>

<rfc ipr="trust200902" docName="draft-eckert-ietf-and-energy-overview" category="info" submissionType="independent" tocDepth="5" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="energy-overview">IETF and Energy - An Overview</title>

    <author initials="T." surname="Eckert" fullname="Toerless Eckert" role="editor">
      <organization>Futurewei Technologies USA</organization>
      <address>
        <postal>
          <street>2220 Central Expressway</street>
          <city>Santa Clara</city>
          <code>CA 95050</code>
          <country>USA</country>
        </postal>
        <email>tte@cs.fau.de</email>
      </address>
    </author>
    <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
      <organization>Orange</organization>
      <address>
        <postal>
          <city>Rennes</city>
          <code>35000</code>
          <country>France</country>
        </postal>
        <email>mohamed.boucadair@orange.com</email>
      </address>
    </author>

    <date year="2022" month="July" day="07"/>

    
    
    

    <abstract>


<t>This memo provides an overview of work performed by or proposed within
the IETF related to energy and/or green: awareness, management, control or
reduction of consumption of energy, and sustainability as it related to the IETF.</t>

<t>This document is written to help those unfamiliar with the work but 
interested in it, in the hope to raise more interest in energy-related
activities within the IETF, such as identifying gaps and investigating
solutions as appropriate.</t>



    </abstract>



  </front>

  <middle>


<section anchor="introduction"><name>Introduction</name>

<t>This document summarizes work that has been proposed to or performed 
within the IETF/IRTF. Particularly, it covers IETF/IRTF RFCs as well as
ISE RFCs and IETF/IRTF or individual submission drafts
that where abandoned (e.g., lack of momentum, broad scope).</t>

<t>There are various aspects how a given work can relate to energy that are
classified into categories.  Such a classification does not attempt to propose
a formal taxonomy but it is used for the sake of better readability
Technologies are listed under a category that is specifically significant
for example by being most narrow.</t>

<t>This memo usually refers to the technologies by significant early RFC or draft version,
as opposed to the newest. This is contrary to the common practice in IETF documents to
refer to the newest version. This is done because it allows readers to better understand
the historic timeline in which specific technology was introduced. Especially successful
IETF technologies will have newer RFC that updates such initial work.</t>

</section>
<section anchor="energy-saving-an-introduction"><name>Energy Saving: An Introduction</name>

<t>Technologies that simply save energy compared to earlier/other alternatives are the
broadest and most unspecific category. In this memo such energy saving simply refers
to energy savings in some unit of electricity, such as kWh and does not take other
aspects into account.  See <xref target="sustainability"/> for more details.</t>

<section anchor="digitization"><name>Digitization</name>

<t>Digitization describes the transformation of processes from non or less digital with networking 
to more digital with computer-networking. For comparable process results, the digitized option is often,
but not always, less energy consuming. Consider for example energy consumption in the evolution of
messaging starting from postal mail and overs telegrams and various other historic form to 
solutions including e-mail utilizing for example the IETF "Simple Mail Transport Protocol" (SMTP, <xref target="RFC822"/>),
group communications utilizing the IETF "Network News Transport Protocol" (NNTP, <xref target="RFC3977"/>) or the almost
infinite set of communication options built on top of the IETF "HyperText Transport Protocol" (HTTP, 
<xref target="RFC2086"/> and successors) and IETF "HyperText Markup Language" (HTML, <xref target="RFC1866"/> and successors).</t>

<t>Traditionally, digitization had only "incidental", but not "intentional" relationship to 
energy consumption: If it saved energy, this was not only not a target benefit, it was not
even recognized as one, until probably recently.  Instead, the evolution was driven from anything-but-energy benefits,
but instead utility benefits such as improved speed, functionality/flexibility, accessibility, scalability
and reduced cost.</t>

<t>In hindsight though, digitization through IETF technologies and specifically the Internet
will likely have the largest contribution to energy saving amongst all the possible categories, but it
is also the hardest to pinpoint on any specific technology/RFC. Instead, it is often a combination of 
the whole stack of deployed protocols and operational practices that contributes to energy saving through
digitization. It is likely also the biggest overall energy saving impact of all possible categories that
relate IETF work to energy:</t>

<t>The Internet as well as all other TCP/IP networks are likely the biggest energy saving development
of the past few decades if only the energy consumption of equivalent services is compared. On the other hand,
they are also the cause for the biggest new type of new energy consumption because of all the new services
introduced in the past decades with the Internet and the hyper-scaling that the Internet affords them.</t>

</section>
<section anchor="energy-saving-through-scale"><name>Energy Saving Through Scale</name>

<section anchor="an-example-telephony"><name>An example: Telephony</name>

<t>In most cases, energy saving through the use of IETF protocols compared to earlier (digitized or non digitized)
solutions is purely a result of the reduction in the energy cost per bit over the decades in networking.
For example, the energy consumption of digital voice telephony through the IETF "Session Initiation Protocol"
(SIP, <xref target="RFC2543"/> and successors) can easily be assumed to be more energy efficient on a per voice-minute basis than
 prior voice technologies such as analog or digital "Time Division Multiplex" (TDM) telephony solely because of this 
evolution in mostly device as well as physical-layer and link-layer networking technologies.</t>

</section>
<section anchor="the-packet-multiplexing-principle"><name>The packet multiplexing principle</name>

<t>Nevertheless, it is at the heart of the packet multiplexing model employed by the IETF networking protocols
IP (<xref target="RFC791"/>) and IPv6 (<xref target="RFC1883"/> and successors) to successfully support this scaling that brough down
the cost per bit through ever faster links and network nodes, especially for networks larger than building
scale networks. While the IETF protocols have not been the first or over their early decades necessarily the
most widely deployed packet networking protocols, they where the ones who at least during the 1990th started
to break away from other protocols both in scale of deployment, as well as in development of further technologies
to support this scaling.</t>

</section>
<section anchor="end-to-end-transport"><name>End-to-end transport</name>

<t>At the core of scalability, even up to now, is the lightweight per-packet-processing enabled through
end-to-end congestion loss management architecture as embodied through the IETF "Transport Control Protocol"
(TCP, <xref target="RFC793"/> and successors). This model eliminated more expensive per-hop, per-packet processing, such as
would be required for reliable hop-by-hop forwarding through per-hop ARQ, which was key to scaling routers cost
effectively.</t>

</section>
<section anchor="internet-routing-architectures"><name>Internet Routing Architectures</name>

<t>The meshed peer-to-peer and transitive routing of the Internet enabled through the IETF "Border Gateway (Routing)
Protocol (BGP, <xref target="RFC4271"/> as well as predecessors) is another key factor to successful scalability, because it
enabled competitive market forces to explore markets quickly. Prior to the Internet, the public often only
had access to highly regulated international networking connections through often per-country monopoly regulated data networks.</t>

</section>
<section anchor="freedom-to-innovate"><name>Freedom to innovate</name>

<t>(non-IP) networks often also did not allow as much "freedom-to-innovate" (as it is often called in the IETF)
for applications running over it. Instead those networks where exploring the coupling of packet transport with
higher layer services to allow the network operator some degree of revenue sharing with the services running
on top of it, resulting not only in higher cost of those services but also preferential and often
exclusionary treatment of network traffic not fitting the perceived highest revenue service options.</t>

</section>
<section anchor="end-to-end-encryption"><name>End-to-end encryption</name>

<t>When the same business practices where applied to IP network, it was one of the key factors leading to
the development of IETF end-to-end encryption though protocols such as "Transport Layer Security" (TLS, <xref target="RFC2246"/>
and its successors). This further strengthened the ability to scale service/applications at minimum additional
cost for the underlying packet transport, arguably driving innovation into ever faster networking technology
and likely lower cost per bit.</t>

</section>
<section anchor="converged-networks"><name>Converged networks</name>

<t>Another key factor to support scaling where IETF technologies that allowed to multiplex different types of traffic
(such as "Voice, Video and Data") which previously used/required separate networks with typically incompatible networking
technologies.</t>

<t>Eliminating multiple physical networks with separate routing/forwarding nodes and separate links affords significant
energy savings even at the same generation of speed and hence energy/bit simply by avoiding the N-fold
production and operations of equipment and links. Of course, originally the CAPEX and OPEX of multiple,
technology-diverse networks and host-stacks was the core reason for unified networks, and energy saving
is in hindsight just incidental (as for all other cases mentioned here).</t>

<section anchor="intserv-and-detnet"><name>IntServ and DetNet</name>

<t>The first (non-IETF) wider adopted technology promising converged networks was  "Asynchronuous Transfer Mode" (ATM), 
which was designed and deployed at the end of the 1980th to support specifically multiplexing of "Data Voice and Video",
where both Voice and Video (at that time) required loss-free deterministic bounded latency and low-jitter and had
therefore their own Time-Division-Multiplex (TDM) networks, both separate from so-called Data networks using
packet multiplexing. This technology was very expensive on a per-bit basis due to its cell-forwarding nature
though.</t>

<t>At the end of the 1980th, it was proven (TBD: need to find the reference, cedric knows..)
that variable length packet multiplexing in network can also support non-NP-hard calculations for
bounded latency. This lead to the IETF "Integrated Services WG" (INTSERV) to support such guaranteed
throughput and bounded latency traffic via <xref target="RFC2212"/> - and to the demise of ATM.</t>

<t>IntServ has so far seen little traction because it too got superceeded as explained in the following
section - for its original use-cases (voice and video). However this type of services are being revisited for a
broader set of use-cases <xref target="RFC8575"/> in the DetNet WG, which should enable even further network infrastructure
convergence for IoT and industrial markets.</t>

</section>
<section anchor="diffserv"><name>DiffServ</name>

<t>Due to the much higher per-packet processing overhead of INSERV versus standard (so-called Best-Effort)
Internet traffic, the INTSERV model was already recognized in the 1990th to not support highest-scale at lowest
cost, leading to the parallel development of the IETF "Differentiated Services WG" (DIFFSERV) model
defined in <xref target="RFC2475"/>. This has since then become the dominant technology to support multiplexing of
applications and services originally not designed for the Internet onto a common TCP/IP network infrastructure,
specifically for voice and video over UDP (<xref target="RFC768"/>) including RTP <xref target="RFC3550"/> and SIP.</t>

</section>
<section anchor="sip"><name>SIP</name>

<t>SIP has most notably in the past two decades eliminated additional network infrastructures previously required
for (voice) telephony services starting in the early 2000 with commercial/enterprise deployments and
today by removing even the option for any (non-IP/SIP) analog or digital (ISDN) telephone service connection,
instead delivering those purely as services over adaptation interfaces on home routers (TBD: Any 
RFC to cite for those tunneling/adaptation services ?).</t>

</section>
</section>
</section>
</section>
<section anchor="higher-or-new-energy-consumption"><name>Higher or new energy consumption</name>

<t>Digitized, network centric workflows may consume more energy than their non-digitized counterpart,
as may new network centric workflows without easy to compare prior workflows.</t>

<t>In one type of instances, the energy consumption on a per-instance basis is lower than in the
non-digitized/non-Internet-digitized case, but the total number of instances
that are (Internet)-digitized is orders of magnitudes larger than their alternative options,
typically because of their higher utility or lower overall cost.</t>

<t>For example, each instance of (simple text) email consumes less energy than sending a letter or postcard.
Even streaming a movie or TV series consumes less energy than renting a DVD 
<eref target="https://www.smithsonianmag.com/science-nature/streaming-movie-less-energy-dvd-180951586">DVDvsStreaming</eref>.
Nevertheless, the total amount of instances and in result energy consumption for email and
streaming easily outranks their predecessor technologies.</t>

<t>While these instances look beneficial from a simple energy consumption
metric, its overall scale and the resulting energy consumption may in itself become an
issue, especially when the energy demand it creates risks to outstrip the possible
energy production, short term or long term. This concern is nowadays often raised against
the "digital economy", where the network energy consumption is typically cited as
a small contributor relative to its applications, such as what is running in Data Centers (DC).</t>

<t>In other cases, the energy consumption of digitization requires often significantly more
than their pre-digitization alternatives. The most well-known example of this are likely
crypto-currencies based on "proof-of-work" computations (mining), which on a per currency
value unit can cost 10..30 times or more of the energy consumed by for example gold mining
(very much depending on the highly fluctuating price of the crypto-currency). Nevertheless,
its overall utility compared to such prior currencies or valuables makes it highly
successful in the market.</t>

<t>In general, the digital economy tends to be more energy intensive on a per utility/value
unit, for example by replacing a lot of manual labor with computation), and/or it allows
for faster growth of its workflows.</t>

<t>The lower the cost of network traffic, and the more easily accessible everywhere network
connectivity is, the more competitive and/or successful most of these new workflows of the digital
economy can be.</t>

<t>Given how TCP/IP based networks, especially the Internet have excelled
through their design principles (and success) in this reduction of network traffic cost
and ubiquitous access over the past few decades, as outlined above, one can say that 
IETF technologies and especially the Internet are the most important enabler of the digital economy,
and the energy consumption it produces.</t>

</section>
<section anchor="sustainability"><name>Some Notes on Sustainability</name>

<t>Sustainability is the principle to utilize resources in a way that they do not diminish or run out over the long term.
Beyond the above covered energy saving, sustainability relates with respect to the IETF specifically to the use of 
renewable sources of energy to minimize exhaustion of fossile resources, and the impact of IETF technologies
on global warming to avoid worsening living conditions on the planet.</t>

<t>While there seems to be no IETF work specifically intending to target sustainability (TBD: did we miss anything ?), 
the Internet itself can similarly to how it does for digitization play a key role in building sustainable
networked IT infrastructures. The following subsections list three examples areas where global high performance,
low-cost Internet networking is a key requirement.</t>

<section anchor="follow-the-energy-cloud-scheduling"><name>Follow the energy cloud scheduling</name>

<t>Renewable energy resources (except for water) do commonly have fluctuating energy output. For example,
solar energy output correlates to night/day and strength of sunlight. Cloud Data Centers (DC) consume a significant
amount of the IT sectors energy. Some workloads may simply be scheduled to consume energy in accordance
with the amount of available renewable energy at the time, not requiring the network. Significant
workloads are not elastic in time, such as interactive cloud DC interactive work (cloud based
applications) or entertainment (gaming etc.). These workloads may be instantiated or even
dynamically (over time) migrate to a DC location with sufficient renewable energy and the Internet
(or large TCP/IP OTT backbone networks) will serve as the fabric to access the remote DC and
to coordinate the instantiation/migration.</t>

</section>
<section anchor="minimize-generated-heat"><name>Minimize generated heat</name>

<t>The majority of energy in cloud DC is normally also wasted as exhaust heat, requiring even more energy
for cooling. The warmer the location, the more energy needs to be spent for cooling. For this
reason, DC in cooler climates such as <eref target="https://greenmountain.no/power-and-cooling/"/> can help
to reduce the overall DC energy consumption significantly (independent of the energy being
consumed in the DC to be renewable itself). The Internet again plays the role of providing access
to those type of DC whole location is not optimized for consumption but for sustainable generation
of compute and storage.</t>

</section>
<section anchor="heat-recovery"><name>Heat recovery</name>

<t>Exhaust heat, especially from compute in DC, can be recovered when it is coupled to heating systems
ranging in size all the way from individual familys home through larger buildings (hotels etc.) all the
way to district heating systems. A provider of such type of compute-generated heat as a service
can sell the compute capacity as long as there is cost efficient network connectivity.  "Cloud &amp; Heat"
is an example company offering such infrastructures and services
<eref target="https://www.cloudandheat.com/wp-content/uploads/2020/02/2020_CloudHeat-Whitepaper-Cost-saving-Potential.pdf"/>.</t>

</section>
<section anchor="telecollaboration"><name>Telecollaboration</name>

<t>Telecollaboration has a long history in the IETF resulting in multiple core technologies over the decades.</t>

<t>If one considers textual communications via email and netwnews (using e.g.: NNTP) as early forms of Telecollaboration,
then telecollaboration history through IETF technology reaches back into the 1980th and earlier.</t>

<t>Around 1990, the IETF work on IP Multicast (e.g.<xref target="RFC1112"/> and later) enabled the first efficient forms
of audio/video group collaboration through an overlay network over the Internet called the MBone
<eref target="https://en.wikipedia.org/wiki/Mbone"/> which was also used by the IETF for more than a decade to
provide remote collaboration for its own (in-person + remote participation) meetings.</t>

<t>With the advent of SIP in the early 2000, commercial telecollaboration started to be built most often on SIP based
session and application protocols with multiple IETF working groups contributing to that protocol suite
(TBD: how much more example/details should we have here). Using this technology and the Internet, the
immersive nature of telecollaboration was brought to life-size video, was/is called Telepresence
<eref target="https://en.wikipedia.org/wiki/Telepresence"/> and later to even more immersive forms such as AR/VR telecollaboration.</t>

<t>In 2011, the IETF opened the "Real-Time Communication in WEB-browsers" (RTCWEB) WG, that towards the
end of that decade became the most widely supported cross-platform standard for hundreds of commercial
and free tele-collaboration solutions, including Cisco Webex, which is also used by the IETF itself, Zoom and
the new IETF collaboration suite MeetEcho (TBD: good references here ?).</t>

<t>While the various forms of Telecollaboration are mostly instances of digitization, they
are discussed under sustainability because of its comparison to in-person travel that is
not based on simple comparison of energy, but nowadays by comparing their impact on global warming,
a key factor to sustainability.</t>

<t>Telecollaboration was primarily developed because of the utility for the participants - to avoid travel
for originally predominantly business communications/collaborations. It  saw an extreme increase in use 
(TBD: references) in the Corona Crisis of 2019, when especially international travel was often prohibited,
and often even working from an office. This forced millions of people to work from home and utilizing commercial
telecollaboration tools. It equally caused most in-person events that where not cancelled to
be moved to a telecollaboration platform over the Internet - most of them likely relying on RTCWEB
protocols.</t>

<t>Actual energy consumption related comparison between teleconferencing and in-person travel is complex
but since the last decades is commonly based on calculating some form of CO2 emission equivalent of
the energy consumed, hence comparing not simply the energy consumption, but weighing it by the
impact the energy consumption has on one of the key factors (CO2 emission) known to impact sustainable
living conditions.</t>

<t><xref target="VC2014"/> is a good example of a comparison between travel and telecollaboration taking various factors
into account and using CO2 emission equivalents as its core metric. That paper concludes that carbon/
energy cost of telecollaboration could be as little as 7% of an in-person meeting. 
in-person meeting. Those numbers have various assumptions and change when time-effort of
participants is converted to carbon/energy costs. These numbers should even be better today
in favor of telecollaboration: cost of Internet traffic/bit goes down while cost of fossile fuel
for travel goes up.</t>

<t>Recently, air travel has also come under more scrutiny because the greenhouse gas emissions of air travel
at the altitudes used by commercial aviation has been calculated to have a higher global warming
impact than simply the amount of CO2 used by the air plane if it was exhausted at surface level. One
publicly funded organization offering carbon offset services calculates a factor 3 of the CO2 consumption of an
air plane <eref target="https://www.atmosfair.de/de/fliegen_und_klima/flugverkehr_und_klima/klimawirkung_flugverkehr/"/>.</t>

<t>In summary: Telecollaboration has a higher sustainability benefit compared to travel than just
the comparison of energy consumption because of the higher challenge to use renewable energy
in transportation than in networking, and this is most extreme in the case of telecollaboration
that replaces air travel because of the even higher global warming impact of using fossile fuels
in air travel.</t>

</section>
</section>
<section anchor="energy-optimization-in-specific-networks"><name>Energy Optimization in Specific Networks</name>

<section anchor="LLN"><name>Low Power and Lossy Networks (LLN)</name>

<t>Low Power and Lossy Networks are networks in which nodes and/or radio links have constraints.
Low power consumption constraints in nodes often originate from the need to operate nodes from
as long as possible from battery and/or energy harvesting such as (today most commonly) solar panels
associated with the node or ambient energy such as energy harvesting from movement for wearable nodes
or piezo cells to generate energy for mechanically operated nodes such as switches.</t>

<t>Several IETF WGs have or are producing work is primarily intended wo support LLN through multiple
layers of the protocol stack. <xref target="RFC8352"/> gives a good overview of the energy consumption related
communication challenges and solutions produced by the IETF for this space.</t>

<t>To minimize the energy needs for such nodes, their network data-processing mechanisms have to
be optimized. This includes packet header compression, fragmentation (to avoid latency through
large packets at low bitrates, packet bundling to only consume radio energy at short time
periods, radio energy tuning to just reach the destination(s), minimization of multicasting
to eliminate need of radio receivers to consume energy and so on. <xref target="RFC8352"/> gives a more detailed
overview, especially because different L2 technologies such as IEEE 802.15.4 type (low power)
wireless networks, Bluetooth Low Energy (BLE), WiFi (IEEE 802.11) and DEC ULE.</t>

<t>In the INTernet area of the IETF, several LLN specific WGs exist(ed):</t>

<section anchor="lowpan-wg"><name>6LOWPAN WG</name>

<t>The "IPv6 over Low power WPAN (Wireless Personal Area Networks)" (6lowpan) WG ran from 2005
to 2014 and produced 6 RFC that adopt IPv6 to IEEE 802.15.4 type (low power) wireless networks
by transmission procedures <xref target="RFC4949"/>, compression of IPv6 (and transport) packet headers <xref target="RFC6282"/>,
modifications for neighbor discovery (ND) <xref target="RFC6775"/>, as well as 3 informational RFCs
about the WPAN space and applying IPv6 to it.  "Transmission of IPv6 Packets over IEEE 802.15.4 Networks" <xref target="RFC4944"/>,
"Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks" <xref target="RFC6282"/>,
"Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)" <xref target="RFC6775"/> (6LOWPAN-ND).</t>

</section>
<section anchor="lpwan-wg"><name>LPWAN WG</name>

<t>Since 2014, the "IPv6 over Low Power Wide-Area Networks" (LPWAN) WG has produced 4 RFC
for low-power wide area networks, such as LoRaWAN <eref target="https://en.wikipedia.org/wiki/LoRa"/>,
with three standards, <xref target="RFC8724"/>, <xref target="RFC8824"/>, <xref target="RFC9011"/>.</t>

</section>
<section anchor="tisch-wg"><name>6TISCH WG</name>

<t>Since 2013, the "IPv6 over the TSCH mode of IEEE 802.15.4e" (6tisch) WG has produced 7 RFC
for a version of 802.15.4 called the "Time-Slotted Channel Hopping Mode" (TSCH), which
supports deterministic latency and lower energy consumption through the use of
scheduling traffic into well defined time slots, thereby also optimizing/minimizing
energy consumption when compared to 802.15.4 without TSCH.</t>

</section>
<section anchor="lo-wg"><name>6LO WG</name>

<t>Since 2013, the "IPv6 over Networks of Resource-constrained Nodes" (6lo) WG has generalized
the work of 6lowpan for LLN in general, producing 17 RFC for IPv6-over-l2foo adaptation layer
specifications, information models, cross-adaptation layer specification (such as header
specifications) and maintenance and informational documents for other pre-existing IETF
work in this space.</t>

</section>
<section anchor="roll-wg"><name>ROLL WG</name>

<t>In the RouTinG (RTG) area of the IETF, the "Routing Over Low power and Lossy networks" (ROLL) WG
has produced since 2008 23 RFC. Initially it produced requirement RFCs of different type of
"Low-power and Lossy Networks": urban: <xref target="RFC5548"/>, industrial <xref target="RFC5673"/>, home automation
<xref target="RFC5826"/> and building automation <xref target="RFC5867"/>.</t>

<t>Since then its work is mostly focused
on the "IPv6 Routing Protocol for Low-Power and Lossy Networks" (RPL) <xref target="RFC6550"/>, which
is used in a wide variety of the above described IPv6 instances of LLN networks
and which are discussed in two ROLL applicability statement RFCs,
 "Applicability Statement: The Use of the Routing Protocol for Low-Power and
Lossy Networks (RPL) Protocol Suite in Home Automation and Building Control" <xref target="RFC7733"/> and
"Applicability Statement for the Routing Protocol for Low-Power and
Lossy Networks (RPL) in Advanced Metering Infrastructure (AMI) Networks"
<xref target="RFC8036"/>.</t>

<t>The ROLL WG also wrote a more generic RFC for LLN, "Terms Used in Routing for Low-Power and Lossy Networks" <xref target="RFC7102"/>.
RPL has a highly configurable set of functions to support (energy) constrained networks. 
Unconstrained root node(s), typically edge routers between the RPL network and a backbone network
calculate "Destination-Oriented Directed Acyclic Graphs" (DODAG) and can use strict hop-by-hop
source routing with dedicated IPv6 routing headers <xref target="RFC9008"/> to minimize constrained nodes
routing related compute and memory requirements. "The Trickle Algorithm" <xref target="RFC6206"/> allows
to minimize routing related packets through automatic lazy updates. While RPL is naturally
a mesh network routing protocol, where all nodes are usually expected to be able to
participate in it, RPL also supports even more lightweight leave nodes <xref target="RFC9010"/>.</t>

<t>The 2013 <xref target="I-D.ajunior-energy-awareness-00"/> proposes the introducing of energy related parameters
into RPL to support calculation/selection of most energy efficient paths. The 2017
 "An energy optimization routing scheme for LLSs", <xref target="I-D.wang-roll-energy-optimization-scheme"/> 
observed that DODAGs in RPL tend to require more energy in nodes closer to the root and
proposed specific optimizations to reduce this problem. Neither of these drafts proceeded in the IETF.</t>

<t>While original use-cases for RPL where energy and size limited networks, its design is to a large
extend not scale limited.  Because of this, and due to its reduced compute/memory requirements for
the same size networks compared to other routing protocols, especially the so-called link-state
"Interior Gateway routing Protocols" (IGP), such as most commonly used protocols ISIS <xref target="RFC1142"/>
and OSPF <xref target="RFC2328"/>, RPL has also proliferated into use-cases for non-constrained networks, for example to support
the largest possible networks automatically, such as in <xref target="RFC8994"/>.</t>

</section>
</section>
<section anchor="constrained-nodes-and-networks"><name>Constrained Nodes and Networks</name>

<t>(Power) constrained nodes and/or networks exist in a much broader variety than coupled
with low-power and lossy networks. For example WiFi and mobile network connections are
not considered to be lossy networks, and personal mobile nodes with either connections
are order of magnitude less constrained than nodes typically attached to LLN network.
Therefore, broader work in the IETF than focused primarily on LLN typically uses
just the term lightweight or constrained (nodes and networks).</t>

<section anchor="lwig-wg"><name>LWIG WG</name>

<t>Since 2013, the "Light-Weight Implementation Guidance" (lwig) WG is has produced 6 informational
RFC on the groups subject, much of which indirectly supports implementing power
efficient network implementations via lightweight nodes/links,  but it also
addressed the topic explicitly including via the aforementioned <xref target="RFC8352"/> and <xref target="RFC9178"/>,
"Building Power-Efficient Constrained Application Protocol (CoAP) Devices for Cellular Networks".</t>

</section>
<section anchor="core-and-coap"><name>CoRE and CoAP</name>

<t>In the APPlication (APP) area of the IETF, the "Constrained RESTful Environments" (core) WG
has produced since 2010 21 RFC, most of them for or related to "The Constrained Application Protocol"
(CoAP) <xref target="RFC6690"/>, which can best be described as a replacement for HTTP for constrained
environment, using UDP instead of TCP and DTLS instead of TLS, compact binary message formats
instead of human readable textual formats, RESTful message exchange semantic instead of a
broader set of options (in HTTP), but also more functionality such as (multicast)
discovery and directory services, therefore providing a more comprehensive set of common application
functions with more compact on-the-wire/radio encoding than its unconstrained alternatives.
"Object Security for Constrained RESTful Environments" (OSCORE), <xref target="RFC8613"/> is a further
product of the CoRE WG providing a more message layer based, more lightweight security
alternative to DTLS.</t>

<t>While originally designed for LLN, CoAP is transcending LLN and equally becoming standards
in unconstrained environments such as wired/ethernet industrial Machine 2 Machine (M2M) communications,
because of simplicity, flexibility and relying on the single set of protocols supporting the widest
range of deployment scenarios.</t>

<t>In the SECurity (SEC) area of the IETF, the "Authentication and Authorization for Constrained Environments" (ace)
working group has since 2014 produced 4 RFC for security functions in constrained environments,
for example CoAP based variations of prior HTTPS protocols such as EST-coaps <xref target="RFC9148"/> for
HTTPS based EST <xref target="RFC7030"/>. Constrained node support in cryptography especially
entails support for Elliptic Curve (EC) public keys due to their shorter key sizes and lower compute
requirements compared to RSA public keys with same cryptographic strength. While the benefits of
EC over RSA where making them preferred, this "additional market space" (constrained node)
benefit helped in their faster market proliferation even beyond constrained networks.</t>

</section>
<section anchor="satellite-constellations"><name>Satellite Constellations</name>

<t>Emerging communication infrastructures may have specific requirements on power
consumption. Such requirements should be taken into account when
designing/customizing techniques (e.g., routing) to be enabled in such networks.
For example, <xref target="I-D.lhan-problems-requirements-satellite-net"/> identifies a set
of requirements (including power) for satellite constellations.</t>

</section>
<section anchor="devices-with-batteries"><name>Devices with Batteries</name>

<t>Many IETF protocols (e.g., <xref target="RFC3948"/>) were designed to accommodate the presence
of middleboxes mainly by encouraging clients to issue frequent keepalives.
Such strategy has implication on battery-supplied devices. In order to
optimize battery consumption for such devices, <xref target="RFC6887"/> specifies a deterministic
method so that client can control state in the network, including their lifetime.
Keepalive alive messages may this be optimized as a function of the network policies.</t>

<t>A_REC#2 of <xref target="RFC7849"/> further insist on the importance of saving battery exacerbated
by keep-alive messages and recommends the support of collaborative means to control
state in the network rather than relying on heuristics.</t>

</section>
</section>
<section anchor="sample-technical-enablers"><name>Sample Technical Enablers</name>

<section anchor="ip-multicast"><name>(IP) Multicast</name>

<section anchor="power-saving-with-multicast"><name>Power saving with multicast</name>

<t>IP Multicast was introduced with <xref target="RFC1112"/> and today also called "Any Source Multicast" (ASM)
has various protocols standardized in the IETF across multiple working groups. There are also
MPLS and BIER multicast protocols from the IETF developed in the equally named WGs.</t>

<t>These three, network layer multicast technologies can be a power saving technologies when used to
distribute data because they reduce the number of packets that need to be sent across
the network (through in-network-replication where needed). Because most current link and router technologies 
do not allow to actually save significant amounts of energy on lower than maximum utilization, these benefits are often only theoretical though. Software routers are the ones most likely to expose energy consumption somewhat proportional to their throughput for just the forwarding (CPU) chip.</t>

<t>Likewise, in large backbone networks, IP multicast can free up bandwidth to be used for other traffic,
such as unicast traffic, which may allow to avoid upgrades to faster and potentially more power consuming
routers/links. Today, these benefits too are most often overcompensated for by lower per-bit energy
consumption of newer generations of routers and links though.</t>

<t>Multicasting can also save energy on the transmitting station across radio links, compared to
replicated unicast traffic, but this is rarely significant, because except for
fully battery powered mesh network, there are typically non-energy-constrained nodes, such as (commonly) the
wired access-points in WiFi networks.</t>

<t>In result, today multicasting has typically no significant power saving benefits with available
network technologies. Instead it is used (for data distribution) when the amount of traffic that a unicast solution
alternative (with so-called ingress replication) is not possible due to the total amount of
traffic generated. This includes wireless/radio networks, where equally airtime is the limiting
factor.</t>

</section>
<section anchor="coordination"><name>Power waste through multicast based service coordination</name>

<t>(IP) multicast is often not used to distribute data requested by receivers, but also
coordination type functions such as service or resource announcement, discovery or selection.
These multicast messages may not carry a lot of data, but they cause recurring, often periodic
packets to be sent across a domain and waste energy because of various ill-advised designs,
including, but not limited to the following issues:</t>

<t>(a) The receivers of such packets may not even need to receive them, but the protocol
shares a multicast group with another protocol that the client does need to receive.</t>

<t>(b) The receiver should not need to receive the packet as far as multicast is concerned, but
the underlying link-layer technology still makes the receiver consume the packet at link-layer.</t>

<t>(c) The information received is not new, but just periodically refreshed.</t>

<t>(d) The packet was originated for a service selection by a client, and the receiving device
is even responding, but the client then chooses to select another device for the service/resource.</t>

<t>These problems are specifically problematic in the presence of so-called "sleepy" nodes <xref target="sleepy"/> that
need to wake up to receive such packets (unnecessarily). It is worse, when the network itself
is an LLN network where the forwarders themselves are power constrained and for example periodic
multicasting of such coordination packets wastes energy on those forwarders as well - compared
to better alternatives.</t>

<t>In 2006, the IETF standardized "Source Specific Multicast" (SSM) <xref target="RFC4607"/>, a variation of IP Multicast
that does not allow to perform these type of coordination functions but is only meant for
(and useable for) actual data distribution. SSM was introduced for other reasons than the
above-described power related issues though, but deprecating the use of ASM is one way to
avoid/minimize its ill-advised use with these type of coordination functions, when energy
efficiency is an issue. <xref target="RFC8815"/> is an example for deprecating ASM for other reasons
in Service Provider networks.</t>

</section>
<section anchor="wifi"><name>Multicast problems with WiFi</name>

<t><xref target="RFC9119"/> covers multicast challenges and solution (proposals) for IP Multicast over 
WiFi. With respect to power consumption, it discusses the following aspects.</t>

<t>(a) Unnecessary wake-up of power constrained WiFi Stations (STA) nodes can be minimized by wireless
Access Points (APs) that buffer multicast packets so they are sent only periodically when
those nodes wake up.</t>

<t>(b) WiFi access points with "Multiple Input Multiple Output" (MIMO) antenna diversity
focus sent packets in a way that they are not "broadcast" to all receivers within
a particular maximum distance from the AP, making WiFi multicast transmission even
less desirable.</t>

<t>(c) It lists the most widely deployed protocols using aforementioned coordination via
IP multicast and describes their specific challenges and possible improvements.</t>

<t>(d) Existing proprietary conversion of WiFi multicast to WiFi unicast packets.</t>

</section>
</section>
<section anchor="sleepy"><name>Sleepy nodes</name>

<t>Sleepy nodes are one of the most common design solutions in support of power saving.
This includes LLN level constrained nodes, but also nodes with significant battery capacity,
such as mobile phones, tablets and notebooks, because battery lifetime has long since
been a key selling factor. In result, vendors do attempt to optimize power consumption
across all hardware and software components of such nodes, including the interface hardware
and protocols used across the nodes WiFi and mobile radios.</t>

<t>Restating from <xref target="I-D.bormann-core-roadmap-05"/>: CoAP has basic support for sleepy nodes
by allowing caching of resource information in (non-sleepy) proxy nodes. <xref target="RFC7641"/>
enhances this support by enabling sleepy nodes to update caching intermediaries on their own schedule.
Around 2012/2013, there was significant review of further review of further support for sleepy
nodes in CoAP, resulting in a long list of drafts, whose sleepy nodes benefits are discussed
in <xref target="I-D.bormann-core-roadmap-05"/>: <xref target="I-D.vial-core-mirror-server"/>, <xref target="I-D.vial-core-mirror-proxy"/>,
<xref target="I-D.fossati-core-publish-option"/>, <xref target="I-D.giacomin-core-sleepy-option"/>, <xref target="I-D.castellani-core-alive"/>,
<xref target="I-D.rahman-core-sleepy-problem-statement"/>, <xref target="I-D.rahman-core-sleepy"/>, <xref target="I-D.rahman-core-sleepy-nodes-do-we-need"/>,
<xref target="I-D.fossati-core-monitor-option"/>. None of these drafts proceeded though.</t>

<t>One partial solution to some sleepy node issues related to their energy consumption,
especially the ones caused by the use of multicast <xref target="coordination"/>, <xref target="wifi"/> is the
use of the "Constrained RESTful Environments (CoRE) Resource Directory" (CoRE-RD) <xref target="RFC9176"/>.
It allows for sleepy nodes to register discover and register resources via unicast and
avoids waking up sleepy nodes when they are not selected by a resouce consumer.</t>

<t>An partial alternative to CoRE-RD is the "DNS-Based Service Discovery" {DNS-SD} <xref target="RFC6763"/>
combined with for example "Service Registration Protocol for DNS-Based Service Discovery" <xref target="I-D.ietf-dnssd-srp"/>.
Services can be seen as a subset of resources, and in networks where DNS has to be supported
anyhow for other reasons, DNS-SD may be a sufficient alternative to CoRE-RD. It is used
for example in Thread <eref target="https://en.wikipedia.org/wiki/Thread_(network_protocol)"/> for this purpose
and the only multicast based coordination is the one to establish network wide parameters,
such as the address(es) of DNS-SD server(s).</t>

<t>"Building Power-Efficient Constrained Application Protocol (CoAP) Devices for Cellular Networks"  <xref target="RFC9178"/>
discusses sleepy devices, especially the use of CoAP PubSub <xref target="I-D.ietf-core-coap-pubsub"/> as a
mechanism to build proxies for sleepy devices. "Sensor Measurement Lists (SenML)", Standardized
proxy infrastructures are best built with standard data models, such as "Sensor Measurement Lists" (SenML)
<xref target="RFC8428"/> for sensors, likely the largest number of sleepy devices, especially in LLN.</t>

<t>"Reducing Energy Consumption of Router Advertisements", <xref target="RFC7772"/> eliminates/reduces the
energy impact for sleepy nodes of the ubiquitous IPv6 "Neighbor Discovery" (ND) protocol by
giving recommends for replacing multicast "Router Advertisement" (RA) messages with so-called
directed unicast versions, therefore not waking up sleepy nodes (with an IP multicast RA message).
This was already allowed in ND <xref target="RFC4861"/>, but not recommended as the default. Note that
<xref target="RFC7772"/> does not provide all the energy related optimizations of ND as developed by 
6LoWPAN through <xref target="RFC6775"/>. <xref target="I-D.chakrabarti-nordmark-energy-aware-nd"/> proposes generalizations
for those applications for to all IPv6 links, but was not further pursued by the IETF so far.</t>

</section>
</section>
<section anchor="lack-of-power-benchmarking-proposals"><name>(Lack of) Power Benchmarking Proposals</name>

<t><xref target="I-D.petrescu-v6ops-ipv6-power-ipv4"/> presented some measurement results of the power
consumption when using IPv6 vs IPv4 with a focus on mobile devices. Such
measurements are not backed with formal benchmarking methodologies so that solid and
reliable references are set to compare and interpret data.</t>

<t><eref target="https://www.ietf.org/proceedings/103/slides/slides-103-saag-iot-benchmarking-00"/>
presented a benchmark example but with a focus on power cost of encryption.</t>

</section>
</section>
<section anchor="energy-management-networks"><name>Energy Management Networks</name>

<t>Use of IETF protocol networks in networks that operate power
consumption and production is another broad area of digitization.</t>

<section anchor="smart-grid"><name>Smart Grid</name>

<t>"Smart Grid" is the most well-known instance of such energy management networks.
According to <eref target="https://en.wikipedia.org/wiki/Smart_grid"/>, the term covers
aspects mostly centered around intelligent measured and controlled
consumption of energy. This includes "Advanced Metering Infrastructure" / "Smart Meters",
remote controllable "distribution boards", "circuit breakers",
"load control" and "smart appliances". Use cases for the "Smart Grid"
include for example timed and measured operations of home devices such as
washers or charging cars, when energy consumption is below average.</t>

<t>The 2011 "Internet Protocols for the Smart Grid" <xref target="RFC6272"/> is a quite comprehensive
(66 page) overview of all IETF protocols considered to be necessary or beneficial
for Smart Grid networks. This document was written in response to interest by
the (not-yet-smart grid) community in utilizing the IETF TCP/IP technologies to
evolve previously non-TCP/IP network, and the risk that unnecessary reinvention of
the wheel/protocols would be done by that community instead of reusing what
was already well specified by the IETF.</t>

<t>Most of the overview in this document is not specific to networks used for Smart
Grid applications but just summarized in the document for the above described
outreach and education to the community.  The aspects most specific to Smart Grids
is the back in 2011 still somewhat in its infancy adaptation of IPv6 network
technologies to LLN networks (see <xref target="LLN"/> below): smart meters, circuit breakers,
load measurement devices, car chargers and so on - all those devices would
most likely be connected to the network via a low-power radio networks, which
ideally would utilize IPv6 directly. Support for LLN networks with IPv6 has
well improved in IETF specifications in the past decade.</t>

</section>
<section anchor="syncro-phasor-networks"><name>Syncro Phasor Networks</name>

<t>Power output of multiple power plants/generators into the same power grid needs to be synchronized
by power levels based on consumption and power phase (50/60Hz depending on
continent) to avoid that energy created out-of-phase is not only wasted, but would
actually burn out power lines or create permanent damage in power generators. When generators
go out-of-sync, they have to be emergency switched off, resulting in (rolling-)blackouts,
worsening the conditions beyond its likely root-cause such as a single overloaded
limited region.</t>

<t>Syncro Phasor Networks are networks whose goal it is to support synchronization of
power generators across a power grid, ultimately also permitting to build larger
and more resilient power grids. "Power Measurement Units" (PMU) are their core
sensoring elements. Since about 2012? these networks have started to
move from traditional SCADA towards more TCP/IP based networking and application technologies 
"to improve power system reliability and visibility through wide area measurement and control, 
by fostering the use and capabilities of synchrophasor technology" (www.naspi.org).</t>

<t>With their fast control loop reaction time and measurement requirements, they also
benefit from reliable, fast propagation of PMU data as well as stricter clock synchronization
than most Smart Grid applications. For example, transmission lines expand under heat that
s caused by electrical load and/or environmental temperature by as much as 30% (between coldest
and hottest or highest-load times), impacting the necessary phase relationship of power generation
on either end (speed of light propagation speed based on effective length of contracted/expanded wire).</t>

<t>The length of transmission wires can be measured from
data sent across the transmission lines and measuring their propagation latency with the help of
accurate clock synchronization between sender and receiver(s), using for example network-based
clock synchronization protocols. The IETF "Network Time Protocol version 4" (NTPv4), <xref target="RFC5905"/>
is one option for this. The IEEE PTP protocol is often preferred though because it specifies
better how measurements can be integrated at the hardware level of Ethernet interfaces, thus
allowing easier to achieve higher accuracy, such as Maximum Time Interval (MTIE) errors of
less than 1 msec. See for example <xref target="NASPICLOCK"/>.</t>

<t>The "North American Syncro Phasor Initiative" (NASPI), https://www.naspi.org is an example
organization in support of syncro phasor networking. It is an ongoing project by
the USA "Department of Energy" (DoE).</t>

</section>
</section>
<section anchor="limited-energy-management-for-networks"><name>(Limited) Energy Management for Networks</name>

<section anchor="metrics"><name>Metrics</name>

<t>A 2010-2013 draft <xref target="I-D.manral-bmwg-power-usage"/>, which was not adopted
discussed and proposed metrics for power consumption that where intended
to be used for benchmarking.</t>

<t>The later work in <xref target="EMAN"/> referred instead to other metrics for
measuring power consumption from other SDOs.</t>

<t>A 2011-2012 draft <xref target="I-D.jennings-energy-pricing"/>, which was not adopted,
discusses and proposes a data model to communicate time-varying cost of
energy in support of enabling time-shifting of network attached or
managed equipment consumption of power.</t>

</section>
<section anchor="EMAN"><name>EMAN WG</name>

<t>While the IETF did specify a few MIBs with aspects related to of power management,
it was only with the formation of the "Energy Management" (EMAN) WG
which ran from 2010 to 2015 and released 7 RFC,
that the IETF produced a comprehensive set of MIB based standards for
managing energy/power for network equipment and associated devices 
and integrated prior scattered power management related work
in the IETF.</t>

<t>EMAN produced (solely) a set of data/information models
(MIBs). It does not introduce any new protocol/stacks nor does it
address "questions regarding Smart Grid, electricity producers, and distributors" (from <xref target="RFC7603"/>).</t>

<t><xref target="I-D.claise-power-management-arch"/> describes
the initial EMAN architecture as envisioned by some of the core contributors to the WG.
It was rewritten in EMAN as the "Energy Management Framework" <xref target="RFC7326"/>.
"Requirements for Energy Management" are defined in <xref target="RFC6988"/>.</t>

<t>According to <xref target="RFC7326"/>, "the (EMAN) framework presents a physical reference model and
information model.  The information model consists of an Energy
Management Domain as a set of Energy Objects.  Each Energy Object can
be attributed with identity, classification, and context.  Energy
Objects can be monitored and controlled with respect to power, Power
State, energy, demand, Power Attributes, and battery.  Additionally,
the framework models relationships and capabilities between Energy Objects."</t>

<t>One category of use-cases of particular interest to network equipment vendors was and is
the management of "Power over Ethernet" via the EMAN framework,
measuring and controlling ethernet connected devices through their PoE 
supplied power. Besides industrial, surveillance cameras and office equipment,
such as WiFi access points and phones, PoE is also positioned as a new
approach for replacing most in-building automation components including
security control for doors/windows, as well as environmental controls and lighting
through the use of an in-ceiling, PoE enabled IP/ethernet infrastructure.</t>

<t>EMAN produced version 4 of the "Entity MIB" (ENTITY-MIB) <xref target="RFC6933"/>, primarily
to introduce globally unique UUIDs for physical entities that allows to better 
link across different entities, such as a PoE port on an ethernet switch and
the device connected to that switch port.</t>

<t>The "Monitoring and Control MIB for Power and Energy" <xref target="RFC7460"></xref> specifies
a MIB for monitoring for Power State and energy consumption of networked.
The document discusses the link with other MIBs such as
the ENTITY-MIB, the ENTITY-SENSOR-MIB <xref target="RFC3433"/> for which it is 
amending missing accuracy information to meet IEC power monitoring
requirements, the "Power Ethernet MIB" (POWER-ETHERNET-MIB) <xref target="RFC3621"/>
to manage PoE, and the pre-existing IETF MIB for Uninterruptable Power Supplies (UPS) (UPS-MIB) 
<xref target="RFC1628"/>, allowing for example to build control systems that manage shutdowns
of devices in case of power failure based on UPS battery capacity and device consumptions/priorities.
Similarly, the EMAN "Definition of Managed Objects for Battery Monitoring" <xref target="RFC7577"/>
defines objects to support battery monitoring in managed devices.</t>

<t>The pre-existing IETF "Entity State MIB" (ENTITY-STATE-MIB) <xref target="RFC4268"/> allows to
specify the operational state of entities specified via the ENTITY-MIB respective
to their power consumption and operational capabilities (e.g.: "coldStandby",
"hotStandby", "ready" etc.). Devices can also act as proxies to provide a MIB
interfaces for monitoring and control of power for other devices, that may use
other protocols, such as in case of a home gateway interfacing with various
vendor specific protocols of home equipment.</t>

<t>The EMAN "Energy Object Context MIB" <xref target="RFC7461"/> defines the
ENERGY-OBJECT-CONTEXT-MIB and IANA-ENERGY-RELATION-MIB, both of which serve to
"address device identification, context information, and the energy relationships
between devices" according to <xref target="RFC7461"/>.</t>

<t>To automatically discover and negotiate PoE power consumption
between switch and client, non-IETF technologies, such as IEEE "Link Layer Discovery Protocol" (LLDP)
 and proprietary MIBs for it, such as LLDP-EXT-MED-MIB can be used.</t>

<t>Finally, the "Energy Management (EMAN) Applicability Statement" <xref target="RFC7603"/>
provides an overview of EMAN with a user/operator 
perspective, also reviewing a range of typical scenarios it can
support as well as how it could/can link
to a variety of pre-existing, non-IETF standards relevant for power management.
Such intended applicability includes home, core, and DC networks.</t>

<t>There are currently no YANG equivalent modules. Such modules would not only
be designed to echo the EMAN MIBs but would also allow to control dedicated
 power optimization engines instead of relying upon static and frozen vendor-specific optimization.</t>

</section>
</section>
<section anchor="powerawareness-in-forwarding-and-routing-protocols"><name>Powerawareness in Forwarding and Routing Protocols</name>

<section anchor="PANET"><name>Power Aware Networks (PANET)</name>

<t>In 2013/2014, some drafts proposed how networks themselves,
specifically those of Internet Service Providers (ISP) could become
"power aware" to the extent that its power consumption could be regulated
(or self-regulate) based on the current required performance of the
network and/or available power, by reducing excess (or too power expensive)
network capacity through switching-off/low-powering components such as 
redundant routers, linecards, interfaces or links, or reducing power
consumption by reducing bitrates on links.</t>

<t>The 2013 "Power-Aware Networks (PANET): Problem Statement" <xref target="I-D.zhang-panet-problem-statement"/>
gives an overview of this concept, and so does "Power-aware Routing and Traffic Engineering: Requirements, Approaches, and Issues", <xref target="I-D.zhang-greennet"/> from the same year.</t>

<t>The 2014 <xref target="I-D.retana-rtgwg-eacp"/> exemplifies
the concept and discusses key challenges such as the reduced resilience against errors when
redundant components are switched off, the risk of increased stretch (path length) and
therefore latency under partial network component shutdown or downspeeding, as well
as the idea of saving energy through (periodic) microsleeps such as possible with
"Energy Efficient Ethernet" <eref target="https://en.wikipedia.org/wiki/Energy-Efficient_Ethernet"/>
links. The 2013 draft "Reducing Power Consumption using BGP with power source data",
<xref target="I-D.mjsraman-panet-inter-as-power-source"/> proposed BGP attributes to allow calculation
of power efficient (or for example green) paths.</t>

<t>One core market driver for this work where rolling blackouts that especially
affected India at the time of these drafts, raising the desire to be for
example reducing the total power consumption of a network in times of such
energy emergencies.</t>

<t>While there was technical interest in the IETF, the market significance for
the vendors mostly present in the IETF was considered as not to be important
enough. Likewise, traditional routers, unlike for example todays standard PC
hardware designs do exhibit little power savings upon shutdown of components
such as line-cards or interfaces.</t>

<t>In addition, an SDN / controller-based solution where relatively in
their infancy back in 2013/2014, and technologies that would allow for SDN controller to
have resilient (self-healing) connectivity such as described in <xref target="RFC8368"/>/<xref target="RFC8994"/>
was also not available, making the risk of severely impacting network
reliability one of the key factors for this PANET work to not proceed so far.</t>

</section>
<section anchor="sdn-based-semantic-forwarding"><name>SDN-based Semantic Forwarding</name>

<t>Recently, <xref target="I-D.boucadair-irtf-sdn-and-semantic-routing"/> provided the following
feature as an examples of capabilities that can be offered by appropriate control
of forwarding elements:</t>

<t>Energy-efficient Forwarding:  An important effort was made in the
past to optimize the energy consumption of network elements.
However, such optimization is node-specific and no standard means
to optimize the energy consumption at the scale of the network
have been defined.  For example, many nodes (also, service cards)
are deployed as backups.</t>

<t>A controller-based approach can be implemented so that the route
selection process optimizes the overall energy consumption of a
path.  Such a process takes into account the current load, avoids
waking nodes/cards for handling "sparse" traffic (i.e., a minor
portion of the total traffic), considers node-specific data (e.g.,
<xref target="RFC7460"/>), etc.  This off-line Semantic Routing approach will
transition specific cards/nodes to "idle" and wake them as
appropriate, etc., without breaking service objectives.  Moreover,
such an approach will have to maintain an up-to-date topology even
if a node is in an "idle" state (such nodes may be removed from
adjacency tables if they don't participate in routing
advertisements).</t>

</section>
<section anchor="misc"><name>Misc</name>

<t>The non-adopted, expired 2013 draft <xref target="I-D.okamoto-ccamp-midori-gmpls-extension-reqs"/>
discusses power awareness in routing in conjunction with Traffic
Engineering (tunnels), specifically in the context of Generalized MPLS (GMPLS),
e.g.: varous L2 technologies such as switched optical fiber networks. It primarily
claims the issue that the existing management objects are not sufficient to
express energy management related aspects, and thus do not allow to build
energy conscious policies into PCE for such GMPLS networks.</t>

<t>The non-adopted 2013 "Requirements for an Energy-Efficient Network System",
<xref target="I-D.suzuki-eens-requirements"/> proposes a signaling of network capacity towards
DC, for example based on load or network energy management in support of 
appropriate performance control (such as VM migration) the DC - or vice versa
(DC load-based traffic engineering in the network to support that DC load).</t>

<t>The non-adopted 2013 "Building power optimal Multicast Trees" <xref target="I-D.mjsraman-rtgwg-pim-power"/>
proposes that (PIM based) IP Multicast routing could perform local routing choices
in the case of "Equal Cost MultiPath" (ECMP) "Reverse Path Forwarding" (RPF)
alternatives based on the energy that would be consumed in the router, such as when
one ECMP alternative would use a more power efficient linecard or when one ECMP choice was
on the same linecard as the interfaces to which the packets would need to be routed
(and therefore avoiding to forward the packet across separate ingress and egress linecards).</t>

</section>
</section>
<section anchor="gaps"><name>Gaps</name>

<t>The 2013 "Towards an Energy-Efficient Internet" <xref target="I-D.winter-energy-efficient-internet"/>
summarizes some of the same work items as this document (as written back in 2013) and
lists additional more non-adopted drafts. It also identifies three areas of gaps, that
it suggests the IETF to work on: "Load-adaptive Resource Management",
"Energy-efficient Protocol Design" and "Energy-efficiency Metrics and Standard Benchmarking Methodologies".</t>

<t>Some aspects for those areas of gaps where partially tackled by later work in the IETF, 
but broadly speaking, most of those areas remain open to a wide range of possible further IETF/IRTF work.</t>

</section>
<section anchor="summary"><name>Summary</name>

<t>TBD</t>

</section>
<section anchor="changelog"><name>Changelog</name>

<t>[RFC-Editor: this section to be removed in final document.]</t>

<t>The master for this document is hosted at <eref target="http://github.com/toerless/energy"/>. Please
submit Issues and/or Pull-requests for proposed changes or join the team of authors and edit yourself.</t>

<t>00: Initial version</t>

<t>01: Added Co-author  (Mohamed Boucadair) - long list of typo fixes, editorial improvements in abstract, introduction and other chapters. Added section on satellite networks, devices with batteries, power benchmarking and SDN-based forwarding semantics.</t>

</section>


  </middle>

  <back>



    <references title='Informative References'>





<reference anchor='RFC768' target='https://www.rfc-editor.org/info/rfc768'>
<front>
<title>User Datagram Protocol</title>
<author fullname='J. Postel' initials='J.' surname='Postel'><organization/></author>
<date month='August' year='1980'/>
</front>
<seriesInfo name='STD' value='6'/>
<seriesInfo name='RFC' value='768'/>
<seriesInfo name='DOI' value='10.17487/RFC0768'/>
</reference>



<reference anchor='RFC791' target='https://www.rfc-editor.org/info/rfc791'>
<front>
<title>Internet Protocol</title>
<author fullname='J. Postel' initials='J.' surname='Postel'><organization/></author>
<date month='September' year='1981'/>
</front>
<seriesInfo name='STD' value='5'/>
<seriesInfo name='RFC' value='791'/>
<seriesInfo name='DOI' value='10.17487/RFC0791'/>
</reference>



<reference anchor='RFC793' target='https://www.rfc-editor.org/info/rfc793'>
<front>
<title>Transmission Control Protocol</title>
<author fullname='J. Postel' initials='J.' surname='Postel'><organization/></author>
<date month='September' year='1981'/>
</front>
<seriesInfo name='STD' value='7'/>
<seriesInfo name='RFC' value='793'/>
<seriesInfo name='DOI' value='10.17487/RFC0793'/>
</reference>



<reference anchor='RFC822' target='https://www.rfc-editor.org/info/rfc822'>
<front>
<title>STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES</title>
<author fullname='D. Crocker' initials='D.' surname='Crocker'><organization/></author>
<date month='August' year='1982'/>
<abstract><t>This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet.  Some of RFC 733's features failed to gain adequate acceptance.  In order to simplify the standard and the software that follows it, these features have been removed.  A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced.  Obsoletes RFC 733, NIC 41952.</t></abstract>
</front>
<seriesInfo name='STD' value='11'/>
<seriesInfo name='RFC' value='822'/>
<seriesInfo name='DOI' value='10.17487/RFC0822'/>
</reference>



<reference anchor='RFC1112' target='https://www.rfc-editor.org/info/rfc1112'>
<front>
<title>Host extensions for IP multicasting</title>
<author fullname='S.E. Deering' initials='S.E.' surname='Deering'><organization/></author>
<date month='August' year='1989'/>
<abstract><t>This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting.  Recommended procedure for IP multicasting in the Internet.  This RFC obsoletes RFCs 998 and 1054.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='STD' value='5'/>
<seriesInfo name='RFC' value='1112'/>
<seriesInfo name='DOI' value='10.17487/RFC1112'/>
</reference>



<reference anchor='RFC1142' target='https://www.rfc-editor.org/info/rfc1142'>
<front>
<title>OSI IS-IS Intra-domain Routing Protocol</title>
<author fullname='D. Oran' initials='D.' role='editor' surname='Oran'><organization/></author>
<date month='February' year='1990'/>
<abstract><t>This RFC is a republication of ISO DP 10589 as a service to the Internet community.  This is not an Internet standard.</t></abstract>
</front>
<seriesInfo name='RFC' value='1142'/>
<seriesInfo name='DOI' value='10.17487/RFC1142'/>
</reference>



<reference anchor='RFC1628' target='https://www.rfc-editor.org/info/rfc1628'>
<front>
<title>UPS Management Information Base</title>
<author fullname='J. Case' initials='J.' role='editor' surname='Case'><organization/></author>
<date month='May' year='1994'/>
<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 objects for managing uninterruptible power supply (UPS) systems.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='1628'/>
<seriesInfo name='DOI' value='10.17487/RFC1628'/>
</reference>



<reference anchor='RFC1866' target='https://www.rfc-editor.org/info/rfc1866'>
<front>
<title>Hypertext Markup Language - 2.0</title>
<author fullname='T. Berners-Lee' initials='T.' surname='Berners-Lee'><organization/></author>
<author fullname='D. Connolly' initials='D.' surname='Connolly'><organization/></author>
<date month='November' year='1995'/>
<abstract><t>This document defines a HTML 2.0 (to distinguish it from the previous informal specifications).  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='1866'/>
<seriesInfo name='DOI' value='10.17487/RFC1866'/>
</reference>



<reference anchor='RFC1883' target='https://www.rfc-editor.org/info/rfc1883'>
<front>
<title>Internet Protocol, Version 6 (IPv6) Specification</title>
<author fullname='S. Deering' initials='S.' surname='Deering'><organization/></author>
<author fullname='R. Hinden' initials='R.' surname='Hinden'><organization/></author>
<date month='December' year='1995'/>
<abstract><t>This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='1883'/>
<seriesInfo name='DOI' value='10.17487/RFC1883'/>
</reference>



<reference anchor='RFC2086' target='https://www.rfc-editor.org/info/rfc2086'>
<front>
<title>IMAP4 ACL extension</title>
<author fullname='J. Myers' initials='J.' surname='Myers'><organization/></author>
<date month='January' year='1997'/>
<abstract><t>The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2086'/>
<seriesInfo name='DOI' value='10.17487/RFC2086'/>
</reference>



<reference anchor='RFC2212' target='https://www.rfc-editor.org/info/rfc2212'>
<front>
<title>Specification of Guaranteed Quality of Service</title>
<author fullname='S. Shenker' initials='S.' surname='Shenker'><organization/></author>
<author fullname='C. Partridge' initials='C.' surname='Partridge'><organization/></author>
<author fullname='R. Guerin' initials='R.' surname='Guerin'><organization/></author>
<date month='September' year='1997'/>
<abstract><t>This memo describes the network element behavior required to deliver a guaranteed service (guaranteed delay and bandwidth) in the Internet. [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2212'/>
<seriesInfo name='DOI' value='10.17487/RFC2212'/>
</reference>



<reference anchor='RFC2246' target='https://www.rfc-editor.org/info/rfc2246'>
<front>
<title>The TLS Protocol Version 1.0</title>
<author fullname='T. Dierks' initials='T.' surname='Dierks'><organization/></author>
<author fullname='C. Allen' initials='C.' surname='Allen'><organization/></author>
<date month='January' year='1999'/>
<abstract><t>This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.</t></abstract>
</front>
<seriesInfo name='RFC' value='2246'/>
<seriesInfo name='DOI' value='10.17487/RFC2246'/>
</reference>



<reference anchor='RFC2328' target='https://www.rfc-editor.org/info/rfc2328'>
<front>
<title>OSPF Version 2</title>
<author fullname='J. Moy' initials='J.' surname='Moy'><organization/></author>
<date month='April' year='1998'/>
<abstract><t>This memo documents version 2 of the OSPF protocol.  OSPF is a link- state routing protocol.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='STD' value='54'/>
<seriesInfo name='RFC' value='2328'/>
<seriesInfo name='DOI' value='10.17487/RFC2328'/>
</reference>



<reference anchor='RFC2475' target='https://www.rfc-editor.org/info/rfc2475'>
<front>
<title>An Architecture for Differentiated Services</title>
<author fullname='S. Blake' initials='S.' surname='Blake'><organization/></author>
<author fullname='D. Black' initials='D.' surname='Black'><organization/></author>
<author fullname='M. Carlson' initials='M.' surname='Carlson'><organization/></author>
<author fullname='E. Davies' initials='E.' surname='Davies'><organization/></author>
<author fullname='Z. Wang' initials='Z.' surname='Wang'><organization/></author>
<author fullname='W. Weiss' initials='W.' surname='Weiss'><organization/></author>
<date month='December' year='1998'/>
<abstract><t>This document defines an architecture for implementing scalable service differentiation in the Internet.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='2475'/>
<seriesInfo name='DOI' value='10.17487/RFC2475'/>
</reference>



<reference anchor='RFC2543' target='https://www.rfc-editor.org/info/rfc2543'>
<front>
<title>SIP: Session Initiation Protocol</title>
<author fullname='M. Handley' initials='M.' surname='Handley'><organization/></author>
<author fullname='H. Schulzrinne' initials='H.' surname='Schulzrinne'><organization/></author>
<author fullname='E. Schooler' initials='E.' surname='Schooler'><organization/></author>
<author fullname='J. Rosenberg' initials='J.' surname='Rosenberg'><organization/></author>
<date month='March' year='1999'/>
<abstract><t>The Session Initiation Protocol (SIP) is an application-layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2543'/>
<seriesInfo name='DOI' value='10.17487/RFC2543'/>
</reference>



<reference anchor='RFC3433' target='https://www.rfc-editor.org/info/rfc3433'>
<front>
<title>Entity Sensor Management Information Base</title>
<author fullname='A. Bierman' initials='A.' surname='Bierman'><organization/></author>
<author fullname='D. Romascanu' initials='D.' surname='Romascanu'><organization/></author>
<author fullname='K.C. Norseth' initials='K.C.' surname='Norseth'><organization/></author>
<date month='December' year='2002'/>
<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 for extending the Entity MIB (RFC 2737) to provide generalized access to information related to physical sensors, which are often found in networking equipment (such as chassis temperature, fan RPM, power supply voltage).  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3433'/>
<seriesInfo name='DOI' value='10.17487/RFC3433'/>
</reference>



<reference anchor='RFC3550' target='https://www.rfc-editor.org/info/rfc3550'>
<front>
<title>RTP: A Transport Protocol for Real-Time Applications</title>
<author fullname='H. Schulzrinne' initials='H.' surname='Schulzrinne'><organization/></author>
<author fullname='S. Casner' initials='S.' surname='Casner'><organization/></author>
<author fullname='R. Frederick' initials='R.' surname='Frederick'><organization/></author>
<author fullname='V. Jacobson' initials='V.' surname='Jacobson'><organization/></author>
<date month='July' year='2003'/>
<abstract><t>This memorandum describes RTP, the real-time transport protocol.  RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services.  RTP does not address resource reservation and does not guarantee quality-of- service for real-time services.  The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality.  RTP and RTCP are designed to be independent of the underlying transport and network layers.  The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes.  There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='STD' value='64'/>
<seriesInfo name='RFC' value='3550'/>
<seriesInfo name='DOI' value='10.17487/RFC3550'/>
</reference>



<reference anchor='RFC3621' target='https://www.rfc-editor.org/info/rfc3621'>
<front>
<title>Power Ethernet MIB</title>
<author fullname='A. Berger' initials='A.' surname='Berger'><organization/></author>
<author fullname='D. Romascanu' initials='D.' surname='Romascanu'><organization/></author>
<date month='December' year='2003'/>
<abstract><t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.  This document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing Power Sourcing Equipment (PSE).</t></abstract>
</front>
<seriesInfo name='RFC' value='3621'/>
<seriesInfo name='DOI' value='10.17487/RFC3621'/>
</reference>



<reference anchor='RFC3948' target='https://www.rfc-editor.org/info/rfc3948'>
<front>
<title>UDP Encapsulation of IPsec ESP Packets</title>
<author fullname='A. Huttunen' initials='A.' surname='Huttunen'><organization/></author>
<author fullname='B. Swander' initials='B.' surname='Swander'><organization/></author>
<author fullname='V. Volpe' initials='V.' surname='Volpe'><organization/></author>
<author fullname='L. DiBurro' initials='L.' surname='DiBurro'><organization/></author>
<author fullname='M. Stenberg' initials='M.' surname='Stenberg'><organization/></author>
<date month='January' year='2005'/>
<abstract><t>This protocol specification defines methods to encapsulate and decapsulate IP Encapsulating Security Payload (ESP) packets inside UDP packets for traversing Network Address Translators.  ESP encapsulation, as defined in this document, can be used in both IPv4 and IPv6 scenarios.  Whenever negotiated, encapsulation is used with Internet Key Exchange (IKE).  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3948'/>
<seriesInfo name='DOI' value='10.17487/RFC3948'/>
</reference>



<reference anchor='RFC3977' target='https://www.rfc-editor.org/info/rfc3977'>
<front>
<title>Network News Transfer Protocol (NNTP)</title>
<author fullname='C. Feather' initials='C.' surname='Feather'><organization/></author>
<date month='October' year='2006'/>
<abstract><t>The Network News Transfer Protocol (NNTP) has been in use in the Internet for a decade, and remains one of the most popular protocols (by volume) in use today.  This document is a replacement for RFC 977, and officially updates the protocol specification.  It clarifies some vagueness in RFC 977, includes some new base functionality, and provides a specific mechanism to add standardized extensions to NNTP.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3977'/>
<seriesInfo name='DOI' value='10.17487/RFC3977'/>
</reference>



<reference anchor='RFC4268' target='https://www.rfc-editor.org/info/rfc4268'>
<front>
<title>Entity State MIB</title>
<author fullname='S. Chisholm' initials='S.' surname='Chisholm'><organization/></author>
<author fullname='D. Perkins' initials='D.' surname='Perkins'><organization/></author>
<date month='November' year='2005'/>
<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 extensions to the Entity MIB to provide information about the state of physical entities.</t><t>In addition, this memo defines a set of Textual Conventions to represent various states of an entity.  The intent is that these Textual Conventions will be imported and used in MIB modules that would otherwise define their own representations.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4268'/>
<seriesInfo name='DOI' value='10.17487/RFC4268'/>
</reference>



<reference anchor='RFC4271' target='https://www.rfc-editor.org/info/rfc4271'>
<front>
<title>A Border Gateway Protocol 4 (BGP-4)</title>
<author fullname='Y. Rekhter' initials='Y.' role='editor' surname='Rekhter'><organization/></author>
<author fullname='T. Li' initials='T.' role='editor' surname='Li'><organization/></author>
<author fullname='S. Hares' initials='S.' role='editor' surname='Hares'><organization/></author>
<date month='January' year='2006'/>
<abstract><t>This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol.</t><t>The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems.  This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced.</t><t>BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR).  These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network &quot;class&quot; within BGP.  BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths.</t><t>This document obsoletes RFC 1771.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4271'/>
<seriesInfo name='DOI' value='10.17487/RFC4271'/>
</reference>



<reference anchor='RFC4607' target='https://www.rfc-editor.org/info/rfc4607'>
<front>
<title>Source-Specific Multicast for IP</title>
<author fullname='H. Holbrook' initials='H.' surname='Holbrook'><organization/></author>
<author fullname='B. Cain' initials='B.' surname='Cain'><organization/></author>
<date month='August' year='2006'/>
<abstract><t>IP version 4 (IPv4) addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are designated as source-specific multicast (SSM) destination addresses and are reserved for use by source-specific applications and protocols.  For IP version 6 (IPv6), the address prefix FF3x::/32 is reserved for source-specific multicast use.  This document defines an extension to the Internet network service that applies to datagrams sent to SSM addresses and defines the host and router requirements to support this extension.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4607'/>
<seriesInfo name='DOI' value='10.17487/RFC4607'/>
</reference>



<reference anchor='RFC4861' target='https://www.rfc-editor.org/info/rfc4861'>
<front>
<title>Neighbor Discovery for IP version 6 (IPv6)</title>
<author fullname='T. Narten' initials='T.' surname='Narten'><organization/></author>
<author fullname='E. Nordmark' initials='E.' surname='Nordmark'><organization/></author>
<author fullname='W. Simpson' initials='W.' surname='Simpson'><organization/></author>
<author fullname='H. Soliman' initials='H.' surname='Soliman'><organization/></author>
<date month='September' year='2007'/>
<abstract><t>This document specifies the Neighbor Discovery protocol for IP Version 6.  IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4861'/>
<seriesInfo name='DOI' value='10.17487/RFC4861'/>
</reference>



<reference anchor='RFC4944' target='https://www.rfc-editor.org/info/rfc4944'>
<front>
<title>Transmission of IPv6 Packets over IEEE 802.15.4 Networks</title>
<author fullname='G. Montenegro' initials='G.' surname='Montenegro'><organization/></author>
<author fullname='N. Kushalnagar' initials='N.' surname='Kushalnagar'><organization/></author>
<author fullname='J. Hui' initials='J.' surname='Hui'><organization/></author>
<author fullname='D. Culler' initials='D.' surname='Culler'><organization/></author>
<date month='September' year='2007'/>
<abstract><t>This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='4944'/>
<seriesInfo name='DOI' value='10.17487/RFC4944'/>
</reference>



<reference anchor='RFC4949' target='https://www.rfc-editor.org/info/rfc4949'>
<front>
<title>Internet Security Glossary, Version 2</title>
<author fullname='R. Shirey' initials='R.' surname='Shirey'><organization/></author>
<date month='August' year='2007'/>
<abstract><t>This Glossary provides definitions, abbreviations, and explanations of terminology for information system security. The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026). The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='FYI' value='36'/>
<seriesInfo name='RFC' value='4949'/>
<seriesInfo name='DOI' value='10.17487/RFC4949'/>
</reference>



<reference anchor='RFC5548' target='https://www.rfc-editor.org/info/rfc5548'>
<front>
<title>Routing Requirements for Urban Low-Power and Lossy Networks</title>
<author fullname='M. Dohler' initials='M.' role='editor' surname='Dohler'><organization/></author>
<author fullname='T. Watteyne' initials='T.' role='editor' surname='Watteyne'><organization/></author>
<author fullname='T. Winter' initials='T.' role='editor' surname='Winter'><organization/></author>
<author fullname='D. Barthel' initials='D.' role='editor' surname='Barthel'><organization/></author>
<date month='May' year='2009'/>
<abstract><t>The application-specific routing requirements for Urban Low-Power and Lossy Networks (U-LLNs) are presented in this document.  In the near future, sensing and actuating nodes will be placed outdoors in urban environments so as to improve people's living conditions as well as to monitor compliance with increasingly strict environmental laws. These field nodes are expected to measure and report a wide gamut of data (for example, the data required by applications that perform smart-metering or that monitor meteorological, pollution, and allergy conditions).  The majority of these nodes are expected to communicate wirelessly over a variety of links such as IEEE 802.15.4, low-power IEEE 802.11, or IEEE 802.15.1 (Bluetooth), which given the limited radio range and the large number of nodes requires the use of suitable routing protocols.  The design of such protocols will be mainly impacted by the limited resources of the nodes (memory, processing power, battery, etc.) and the particularities of the outdoor urban application scenarios.  As such, for a wireless solution for Routing Over Low-Power and Lossy (ROLL) networks to be useful, the protocol(s) ought to be energy-efficient, scalable, and autonomous.  This documents aims to specify a set of IPv6 routing requirements reflecting these and further U-LLNs' tailored characteristics.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='5548'/>
<seriesInfo name='DOI' value='10.17487/RFC5548'/>
</reference>



<reference anchor='RFC5673' target='https://www.rfc-editor.org/info/rfc5673'>
<front>
<title>Industrial Routing Requirements in Low-Power and Lossy Networks</title>
<author fullname='K. Pister' initials='K.' role='editor' surname='Pister'><organization/></author>
<author fullname='P. Thubert' initials='P.' role='editor' surname='Thubert'><organization/></author>
<author fullname='S. Dwars' initials='S.' surname='Dwars'><organization/></author>
<author fullname='T. Phinney' initials='T.' surname='Phinney'><organization/></author>
<date month='October' year='2009'/>
<abstract><t>The wide deployment of lower-cost wireless devices will significantly improve the productivity and safety of industrial plants while increasing the efficiency of plant workers by extending the information set available about the plant operations.  The aim of this document is to analyze the functional requirements for a routing protocol used in industrial Low-power and Lossy Networks (LLNs) of field devices.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='5673'/>
<seriesInfo name='DOI' value='10.17487/RFC5673'/>
</reference>



<reference anchor='RFC5826' target='https://www.rfc-editor.org/info/rfc5826'>
<front>
<title>Home Automation Routing Requirements in Low-Power and Lossy Networks</title>
<author fullname='A. Brandt' initials='A.' surname='Brandt'><organization/></author>
<author fullname='J. Buron' initials='J.' surname='Buron'><organization/></author>
<author fullname='G. Porcu' initials='G.' surname='Porcu'><organization/></author>
<date month='April' year='2010'/>
<abstract><t>This document presents requirements specific to home control and automation applications for Routing Over Low power and Lossy (ROLL) networks.  In the near future, many homes will contain high numbers of wireless devices for a wide set of purposes.  Examples include actuators (relay, light dimmer, heating valve), sensors (wall switch, water leak, blood pressure), and advanced controllers (radio-frequency-based AV remote control, central server for light and heat control).  Because such devices only cover a limited radio range, routing is often required.  The aim of this document is to specify the routing requirements for networks comprising such constrained devices in a home-control and automation environment.  This document is not an Internet Standards Track  specification; it is published for informational purposes.</t></abstract>
</front>
<seriesInfo name='RFC' value='5826'/>
<seriesInfo name='DOI' value='10.17487/RFC5826'/>
</reference>



<reference anchor='RFC5867' target='https://www.rfc-editor.org/info/rfc5867'>
<front>
<title>Building Automation Routing Requirements in Low-Power and Lossy Networks</title>
<author fullname='J. Martocci' initials='J.' role='editor' surname='Martocci'><organization/></author>
<author fullname='P. De Mil' initials='P.' surname='De Mil'><organization/></author>
<author fullname='N. Riou' initials='N.' surname='Riou'><organization/></author>
<author fullname='W. Vermeylen' initials='W.' surname='Vermeylen'><organization/></author>
<date month='June' year='2010'/>
<abstract><t>The Routing Over Low-Power and Lossy (ROLL) networks Working Group has been chartered to work on routing solutions for Low-Power and Lossy Networks (LLNs) in various markets: industrial, commercial (building), home, and urban networks.  Pursuant to this effort, this document defines the IPv6 routing requirements for building automation.  This  document is not an Internet Standards Track specification; it is published for informational purposes.</t></abstract>
</front>
<seriesInfo name='RFC' value='5867'/>
<seriesInfo name='DOI' value='10.17487/RFC5867'/>
</reference>



<reference anchor='RFC5905' target='https://www.rfc-editor.org/info/rfc5905'>
<front>
<title>Network Time Protocol Version 4: Protocol and Algorithms Specification</title>
<author fullname='D. Mills' initials='D.' surname='Mills'><organization/></author>
<author fullname='J. Martin' initials='J.' role='editor' surname='Martin'><organization/></author>
<author fullname='J. Burbank' initials='J.' surname='Burbank'><organization/></author>
<author fullname='W. Kasch' initials='W.' surname='Kasch'><organization/></author>
<date month='June' year='2010'/>
<abstract><t>The Network Time Protocol (NTP) is widely used to synchronize computer clocks in the Internet.  This document describes NTP version 4 (NTPv4), which is backwards compatible with NTP version 3 (NTPv3), described in RFC 1305, as well as previous versions of the protocol. NTPv4 includes a modified protocol header to accommodate the Internet Protocol version 6 address family.  NTPv4 includes fundamental improvements in the mitigation and discipline algorithms that extend the potential accuracy to the tens of microseconds with modern workstations and fast LANs.  It includes a dynamic server discovery scheme, so that in many cases, specific server configuration is not required.  It corrects certain errors in the NTPv3 design and implementation and includes an optional extension mechanism.   [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5905'/>
<seriesInfo name='DOI' value='10.17487/RFC5905'/>
</reference>



<reference anchor='RFC6206' target='https://www.rfc-editor.org/info/rfc6206'>
<front>
<title>The Trickle Algorithm</title>
<author fullname='P. Levis' initials='P.' surname='Levis'><organization/></author>
<author fullname='T. Clausen' initials='T.' surname='Clausen'><organization/></author>
<author fullname='J. Hui' initials='J.' surname='Hui'><organization/></author>
<author fullname='O. Gnawali' initials='O.' surname='Gnawali'><organization/></author>
<author fullname='J. Ko' initials='J.' surname='Ko'><organization/></author>
<date month='March' year='2011'/>
<abstract><t>The Trickle algorithm allows nodes in a lossy shared medium (e.g., low-power and lossy networks) to exchange information in a highly robust, energy efficient, simple, and scalable manner.  Dynamically adjusting transmission windows allows Trickle to spread new information on the scale of link-layer transmission times while sending only a few messages per hour when information does not change.  A simple suppression mechanism and transmission point selection allow Trickle's communication rate to scale logarithmically with density.  This document describes the Trickle algorithm and considerations in its use.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='6206'/>
<seriesInfo name='DOI' value='10.17487/RFC6206'/>
</reference>



<reference anchor='RFC6272' target='https://www.rfc-editor.org/info/rfc6272'>
<front>
<title>Internet Protocols for the Smart Grid</title>
<author fullname='F. Baker' initials='F.' surname='Baker'><organization/></author>
<author fullname='D. Meyer' initials='D.' surname='Meyer'><organization/></author>
<date month='June' year='2011'/>
<abstract><t>This note identifies the key infrastructure protocols of the Internet Protocol Suite for use in the Smart Grid.  The target audience is those people seeking guidance on how to construct an appropriate Internet Protocol Suite profile for the Smart Grid.  In practice, such a profile would consist of selecting what is needed for Smart Grid deployment from the picture presented here.  This document is  not an Internet Standards Track specification; it is published for  informational purposes.</t></abstract>
</front>
<seriesInfo name='RFC' value='6272'/>
<seriesInfo name='DOI' value='10.17487/RFC6272'/>
</reference>



<reference anchor='RFC6282' target='https://www.rfc-editor.org/info/rfc6282'>
<front>
<title>Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks</title>
<author fullname='J. Hui' initials='J.' role='editor' surname='Hui'><organization/></author>
<author fullname='P. Thubert' initials='P.' surname='Thubert'><organization/></author>
<date month='September' year='2011'/>
<abstract><t>This document updates RFC 4944, &quot;Transmission of IPv6 Packets over IEEE 802.15.4 Networks&quot;.  This document specifies an IPv6 header compression format for IPv6 packet delivery in Low Power Wireless Personal Area Networks (6LoWPANs).  The compression format relies on shared context to allow compression of arbitrary prefixes.  How the information is maintained in that shared context is out of scope. This document specifies compression of multicast addresses and a framework for compressing next headers.  UDP header compression is specified within this framework.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='6282'/>
<seriesInfo name='DOI' value='10.17487/RFC6282'/>
</reference>



<reference anchor='RFC6550' target='https://www.rfc-editor.org/info/rfc6550'>
<front>
<title>RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks</title>
<author fullname='T. Winter' initials='T.' role='editor' surname='Winter'><organization/></author>
<author fullname='P. Thubert' initials='P.' role='editor' surname='Thubert'><organization/></author>
<author fullname='A. Brandt' initials='A.' surname='Brandt'><organization/></author>
<author fullname='J. Hui' initials='J.' surname='Hui'><organization/></author>
<author fullname='R. Kelsey' initials='R.' surname='Kelsey'><organization/></author>
<author fullname='P. Levis' initials='P.' surname='Levis'><organization/></author>
<author fullname='K. Pister' initials='K.' surname='Pister'><organization/></author>
<author fullname='R. Struik' initials='R.' surname='Struik'><organization/></author>
<author fullname='JP. Vasseur' initials='JP.' surname='Vasseur'><organization/></author>
<author fullname='R. Alexander' initials='R.' surname='Alexander'><organization/></author>
<date month='March' year='2012'/>
<abstract><t>Low-Power and Lossy Networks (LLNs) are a class of network in which both the routers and their interconnect are constrained.  LLN routers typically operate with constraints on processing power, memory, and energy (battery power).  Their interconnects are characterized by high loss rates, low data rates, and instability.  LLNs are comprised of anything from a few dozen to thousands of routers.  Supported traffic flows include point-to-point (between devices inside the LLN), point-to-multipoint (from a central control point to a subset of devices inside the LLN), and multipoint-to-point (from devices inside the LLN towards a central control point).  This document specifies the IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL), which provides a mechanism whereby multipoint-to-point traffic from devices inside the LLN towards a central control point as well as point-to-multipoint traffic from the central control point to the devices inside the LLN are supported.  Support for point-to-point traffic is also available.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='6550'/>
<seriesInfo name='DOI' value='10.17487/RFC6550'/>
</reference>



<reference anchor='RFC6690' target='https://www.rfc-editor.org/info/rfc6690'>
<front>
<title>Constrained RESTful Environments (CoRE) Link Format</title>
<author fullname='Z. Shelby' initials='Z.' surname='Shelby'><organization/></author>
<date month='August' year='2012'/>
<abstract><t>This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes, and other relationships between links.  Based on the HTTP Link Header field defined in RFC 5988, the Constrained RESTful Environments (CoRE) Link Format is carried as a payload and is assigned an Internet media type.  &quot;RESTful&quot; refers to the Representational State Transfer (REST) architecture.  A well-known URI is defined as a default entry point for requesting the links hosted by a server.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='6690'/>
<seriesInfo name='DOI' value='10.17487/RFC6690'/>
</reference>



<reference anchor='RFC6763' target='https://www.rfc-editor.org/info/rfc6763'>
<front>
<title>DNS-Based Service Discovery</title>
<author fullname='S. Cheshire' initials='S.' surname='Cheshire'><organization/></author>
<author fullname='M. Krochmal' initials='M.' surname='Krochmal'><organization/></author>
<date month='February' year='2013'/>
<abstract><t>This document specifies how DNS resource records are named and structured to facilitate service discovery.  Given a type of service that a client is looking for, and a domain in which the client is looking for that service, this mechanism allows clients to discover a list of named instances of that desired service, using standard DNS queries. This mechanism is referred to as DNS-based Service Discovery, or DNS-SD.</t></abstract>
</front>
<seriesInfo name='RFC' value='6763'/>
<seriesInfo name='DOI' value='10.17487/RFC6763'/>
</reference>



<reference anchor='RFC6775' target='https://www.rfc-editor.org/info/rfc6775'>
<front>
<title>Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)</title>
<author fullname='Z. Shelby' initials='Z.' role='editor' surname='Shelby'><organization/></author>
<author fullname='S. Chakrabarti' initials='S.' surname='Chakrabarti'><organization/></author>
<author fullname='E. Nordmark' initials='E.' surname='Nordmark'><organization/></author>
<author fullname='C. Bormann' initials='C.' surname='Bormann'><organization/></author>
<date month='November' year='2012'/>
<abstract><t>The IETF work in IPv6 over Low-power Wireless Personal Area Network (6LoWPAN) defines 6LoWPANs such as IEEE 802.15.4.  This and other similar link technologies have limited or no usage of multicast signaling due to energy conservation.  In addition, the wireless network may not strictly follow the traditional concept of IP subnets and IP links.  IPv6 Neighbor Discovery was not designed for non- transitive wireless links, as its reliance on the traditional IPv6 link concept and its heavy use of multicast make it inefficient and sometimes impractical in a low-power and lossy network.  This document describes simple optimizations to IPv6 Neighbor Discovery, its addressing mechanisms, and duplicate address detection for Low- power Wireless Personal Area Networks and similar networks.  The document thus updates RFC 4944 to specify the use of the optimizations defined here.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='6775'/>
<seriesInfo name='DOI' value='10.17487/RFC6775'/>
</reference>



<reference anchor='RFC6887' target='https://www.rfc-editor.org/info/rfc6887'>
<front>
<title>Port Control Protocol (PCP)</title>
<author fullname='D. Wing' initials='D.' role='editor' surname='Wing'><organization/></author>
<author fullname='S. Cheshire' initials='S.' surname='Cheshire'><organization/></author>
<author fullname='M. Boucadair' initials='M.' surname='Boucadair'><organization/></author>
<author fullname='R. Penno' initials='R.' surname='Penno'><organization/></author>
<author fullname='P. Selkirk' initials='P.' surname='Selkirk'><organization/></author>
<date month='April' year='2013'/>
<abstract><t>The Port Control Protocol allows an IPv6 or IPv4 host to control how incoming IPv6 or IPv4 packets are translated and forwarded by a Network Address Translator (NAT) or simple firewall, and also allows a host to optimize its outgoing NAT keepalive messages.</t></abstract>
</front>
<seriesInfo name='RFC' value='6887'/>
<seriesInfo name='DOI' value='10.17487/RFC6887'/>
</reference>



<reference anchor='RFC6933' target='https://www.rfc-editor.org/info/rfc6933'>
<front>
<title>Entity MIB (Version 4)</title>
<author fullname='A. Bierman' initials='A.' surname='Bierman'><organization/></author>
<author fullname='D. Romascanu' initials='D.' surname='Romascanu'><organization/></author>
<author fullname='J. Quittek' initials='J.' surname='Quittek'><organization/></author>
<author fullname='M. Chandramouli' initials='M.' surname='Chandramouli'><organization/></author>
<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='RFC6988' target='https://www.rfc-editor.org/info/rfc6988'>
<front>
<title>Requirements for Energy Management</title>
<author fullname='J. Quittek' initials='J.' role='editor' surname='Quittek'><organization/></author>
<author fullname='M. Chandramouli' initials='M.' surname='Chandramouli'><organization/></author>
<author fullname='R. Winter' initials='R.' surname='Winter'><organization/></author>
<author fullname='T. Dietz' initials='T.' surname='Dietz'><organization/></author>
<author fullname='B. Claise' initials='B.' surname='Claise'><organization/></author>
<date month='September' year='2013'/>
<abstract><t>This document defines requirements for standards specifications for Energy Management.  The requirements defined in this document are concerned with monitoring functions as well as control functions. Monitoring functions include identifying energy-managed devices and their components, as well as monitoring their Power States, Power Inlets, Power Outlets, actual power, Power Attributes, received energy, provided energy, and contained batteries.  Control functions include such functions as controlling power supply and Power State of energy-managed devices and their components.</t><t>This document does not specify the features that must be implemented by compliant implementations but rather lists features that must be supported by standards for Energy Management.</t></abstract>
</front>
<seriesInfo name='RFC' value='6988'/>
<seriesInfo name='DOI' value='10.17487/RFC6988'/>
</reference>



<reference anchor='RFC7030' target='https://www.rfc-editor.org/info/rfc7030'>
<front>
<title>Enrollment over Secure Transport</title>
<author fullname='M. Pritikin' initials='M.' role='editor' surname='Pritikin'><organization/></author>
<author fullname='P. Yee' initials='P.' role='editor' surname='Yee'><organization/></author>
<author fullname='D. Harkins' initials='D.' role='editor' surname='Harkins'><organization/></author>
<date month='October' year='2013'/>
<abstract><t>This document profiles certificate enrollment for clients using Certificate Management over CMS (CMC) messages over a secure transport.  This profile, called Enrollment over Secure Transport (EST), describes a simple, yet functional, certificate management protocol targeting Public Key Infrastructure (PKI) clients that need to acquire client certificates and associated Certification Authority (CA) certificates.  It also supports client-generated public/private key pairs as well as key pairs generated by the CA.</t></abstract>
</front>
<seriesInfo name='RFC' value='7030'/>
<seriesInfo name='DOI' value='10.17487/RFC7030'/>
</reference>



<reference anchor='RFC7102' target='https://www.rfc-editor.org/info/rfc7102'>
<front>
<title>Terms Used in Routing for Low-Power and Lossy Networks</title>
<author fullname='JP. Vasseur' initials='JP.' surname='Vasseur'><organization/></author>
<date month='January' year='2014'/>
<abstract><t>This document provides a glossary of terminology used in routing requirements and solutions for networks referred to as Low-Power and Lossy Networks (LLNs).  An LLN is typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links.  There is a wide scope of application areas for LLNs, including industrial monitoring, building automation (e.g., heating, ventilation, air conditioning, lighting, access control, fire), connected home, health care, environmental monitoring, urban sensor networks, energy management, assets tracking, and refrigeration.</t></abstract>
</front>
<seriesInfo name='RFC' value='7102'/>
<seriesInfo name='DOI' value='10.17487/RFC7102'/>
</reference>



<reference anchor='RFC7326' target='https://www.rfc-editor.org/info/rfc7326'>
<front>
<title>Energy Management Framework</title>
<author fullname='J. Parello' initials='J.' surname='Parello'><organization/></author>
<author fullname='B. Claise' initials='B.' surname='Claise'><organization/></author>
<author fullname='B. Schoening' initials='B.' surname='Schoening'><organization/></author>
<author fullname='J. Quittek' initials='J.' surname='Quittek'><organization/></author>
<date month='September' year='2014'/>
<abstract><t>This document defines a framework for Energy Management (EMAN) for devices and device components within, or connected to, communication networks.  The framework presents a physical reference model and information model.  The information model consists of an Energy Management Domain as a set of Energy Objects.  Each Energy Object can be attributed with identity, classification, and context. Energy Objects can be monitored and controlled with respect to power, Power State, energy, demand, Power Attributes, and battery. Additionally, the framework models relationships and capabilities between Energy Objects.</t></abstract>
</front>
<seriesInfo name='RFC' value='7326'/>
<seriesInfo name='DOI' value='10.17487/RFC7326'/>
</reference>



<reference anchor='RFC7460' target='https://www.rfc-editor.org/info/rfc7460'>
<front>
<title>Monitoring and Control MIB for Power and Energy</title>
<author fullname='M. Chandramouli' initials='M.' surname='Chandramouli'><organization/></author>
<author fullname='B. Claise' initials='B.' surname='Claise'><organization/></author>
<author fullname='B. Schoening' initials='B.' surname='Schoening'><organization/></author>
<author fullname='J. Quittek' initials='J.' surname='Quittek'><organization/></author>
<author fullname='T. Dietz' initials='T.' surname='Dietz'><organization/></author>
<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='RFC7461' target='https://www.rfc-editor.org/info/rfc7461'>
<front>
<title>Energy Object Context MIB</title>
<author fullname='J. Parello' initials='J.' surname='Parello'><organization/></author>
<author fullname='B. Claise' initials='B.' surname='Claise'><organization/></author>
<author fullname='M. Chandramouli' initials='M.' surname='Chandramouli'><organization/></author>
<date month='March' year='2015'/>
<abstract><t>This document defines a subset of a Management Information Base (MIB) for energy management of devices.  The module addresses device identification, context information, and the energy relationships between devices.</t></abstract>
</front>
<seriesInfo name='RFC' value='7461'/>
<seriesInfo name='DOI' value='10.17487/RFC7461'/>
</reference>



<reference anchor='RFC7577' target='https://www.rfc-editor.org/info/rfc7577'>
<front>
<title>Definition of Managed Objects for Battery Monitoring</title>
<author fullname='J. Quittek' initials='J.' surname='Quittek'><organization/></author>
<author fullname='R. Winter' initials='R.' surname='Winter'><organization/></author>
<author fullname='T. Dietz' initials='T.' surname='Dietz'><organization/></author>
<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='RFC7603' target='https://www.rfc-editor.org/info/rfc7603'>
<front>
<title>Energy Management (EMAN) Applicability Statement</title>
<author fullname='B. Schoening' initials='B.' surname='Schoening'><organization/></author>
<author fullname='M. Chandramouli' initials='M.' surname='Chandramouli'><organization/></author>
<author fullname='B. Nordman' initials='B.' surname='Nordman'><organization/></author>
<date month='August' year='2015'/>
<abstract><t>The objective of Energy Management (EMAN) is to provide an energy management framework for networked devices.  This document presents the applicability of the EMAN information model in a variety of scenarios with cases and target devices. These use cases are useful for identifying requirements for the framework and MIBs.  Further, we describe the relationship of the EMAN framework to other relevant energy monitoring standards and architectures.</t></abstract>
</front>
<seriesInfo name='RFC' value='7603'/>
<seriesInfo name='DOI' value='10.17487/RFC7603'/>
</reference>



<reference anchor='RFC7641' target='https://www.rfc-editor.org/info/rfc7641'>
<front>
<title>Observing Resources in the Constrained Application Protocol (CoAP)</title>
<author fullname='K. Hartke' initials='K.' surname='Hartke'><organization/></author>
<date month='September' year='2015'/>
<abstract><t>The Constrained Application Protocol (CoAP) is a RESTful application protocol for constrained nodes and networks.  The state of a resource on a CoAP server can change over time.  This document specifies a simple protocol extension for CoAP that enables CoAP clients to &quot;observe&quot; resources, i.e., to retrieve a representation of a resource and keep this representation updated by the server over a period of time.  The protocol follows a best-effort approach for sending new representations to clients and provides eventual consistency between the state observed by each client and the actual resource state at the server.</t></abstract>
</front>
<seriesInfo name='RFC' value='7641'/>
<seriesInfo name='DOI' value='10.17487/RFC7641'/>
</reference>



<reference anchor='RFC7733' target='https://www.rfc-editor.org/info/rfc7733'>
<front>
<title>Applicability Statement: The Use of the Routing Protocol for Low-Power and Lossy Networks (RPL) Protocol Suite in Home Automation and Building Control</title>
<author fullname='A. Brandt' initials='A.' surname='Brandt'><organization/></author>
<author fullname='E. Baccelli' initials='E.' surname='Baccelli'><organization/></author>
<author fullname='R. Cragie' initials='R.' surname='Cragie'><organization/></author>
<author fullname='P. van der Stok' initials='P.' surname='van der Stok'><organization/></author>
<date month='February' year='2016'/>
<abstract><t>The purpose of this document is to provide guidance in the selection and use of protocols from the Routing Protocol for Low-Power and Lossy Networks (RPL) protocol suite to implement the features required for control in building and home environments.</t></abstract>
</front>
<seriesInfo name='RFC' value='7733'/>
<seriesInfo name='DOI' value='10.17487/RFC7733'/>
</reference>



<reference anchor='RFC7772' target='https://www.rfc-editor.org/info/rfc7772'>
<front>
<title>Reducing Energy Consumption of Router Advertisements</title>
<author fullname='A. Yourtchenko' initials='A.' surname='Yourtchenko'><organization/></author>
<author fullname='L. Colitti' initials='L.' surname='Colitti'><organization/></author>
<date month='February' year='2016'/>
<abstract><t>Frequent Router Advertisement messages can severely impact host power consumption.  This document recommends operational practices to avoid such impact.</t></abstract>
</front>
<seriesInfo name='BCP' value='202'/>
<seriesInfo name='RFC' value='7772'/>
<seriesInfo name='DOI' value='10.17487/RFC7772'/>
</reference>



<reference anchor='RFC7849' target='https://www.rfc-editor.org/info/rfc7849'>
<front>
<title>An IPv6 Profile for 3GPP Mobile Devices</title>
<author fullname='D. Binet' initials='D.' surname='Binet'><organization/></author>
<author fullname='M. Boucadair' initials='M.' surname='Boucadair'><organization/></author>
<author fullname='A. Vizdal' initials='A.' surname='Vizdal'><organization/></author>
<author fullname='G. Chen' initials='G.' surname='Chen'><organization/></author>
<author fullname='N. Heatley' initials='N.' surname='Heatley'><organization/></author>
<author fullname='R. Chandler' initials='R.' surname='Chandler'><organization/></author>
<author fullname='D. Michaud' initials='D.' surname='Michaud'><organization/></author>
<author fullname='D. Lopez' initials='D.' surname='Lopez'><organization/></author>
<author fullname='W. Haeffner' initials='W.' surname='Haeffner'><organization/></author>
<date month='May' year='2016'/>
<abstract><t>This document defines a profile that is a superset of the connection to IPv6 cellular networks defined in the IPv6 for Third Generation Partnership Project (3GPP) Cellular Hosts document.  This document defines a profile that is a superset of the connections to IPv6 cellular networks defined in &quot;IPv6 for Third Generation Partnership Project (3GPP) Cellular Hosts&quot; (RFC 7066).</t><t>Both mobile hosts and mobile devices with the capability to share their 3GPP mobile connectivity are in scope.</t></abstract>
</front>
<seriesInfo name='RFC' value='7849'/>
<seriesInfo name='DOI' value='10.17487/RFC7849'/>
</reference>



<reference anchor='RFC8036' target='https://www.rfc-editor.org/info/rfc8036'>
<front>
<title>Applicability Statement for the Routing Protocol for Low-Power and Lossy Networks (RPL) in Advanced Metering Infrastructure (AMI) Networks</title>
<author fullname='N. Cam-Winget' initials='N.' role='editor' surname='Cam-Winget'><organization/></author>
<author fullname='J. Hui' initials='J.' surname='Hui'><organization/></author>
<author fullname='D. Popa' initials='D.' surname='Popa'><organization/></author>
<date month='January' year='2017'/>
<abstract><t>This document discusses the applicability of the Routing Protocol for Low-Power and Lossy Networks (RPL) in Advanced Metering Infrastructure (AMI) networks.</t></abstract>
</front>
<seriesInfo name='RFC' value='8036'/>
<seriesInfo name='DOI' value='10.17487/RFC8036'/>
</reference>



<reference anchor='RFC8352' target='https://www.rfc-editor.org/info/rfc8352'>
<front>
<title>Energy-Efficient Features of Internet of Things Protocols</title>
<author fullname='C. Gomez' initials='C.' surname='Gomez'><organization/></author>
<author fullname='M. Kovatsch' initials='M.' surname='Kovatsch'><organization/></author>
<author fullname='H. Tian' initials='H.' surname='Tian'><organization/></author>
<author fullname='Z. Cao' initials='Z.' role='editor' surname='Cao'><organization/></author>
<date month='April' year='2018'/>
<abstract><t>This document describes the challenges for energy-efficient protocol operation on constrained devices and the current practices used to overcome those challenges.  It summarizes the main link-layer techniques used for energy-efficient networking, and it highlights the impact of such techniques on the upper-layer protocols so that they can together achieve an energy-efficient behavior.  The document also provides an overview of energy-efficient mechanisms available at each layer of the IETF protocol suite specified for constrained-node networks.</t></abstract>
</front>
<seriesInfo name='RFC' value='8352'/>
<seriesInfo name='DOI' value='10.17487/RFC8352'/>
</reference>



<reference anchor='RFC8368' target='https://www.rfc-editor.org/info/rfc8368'>
<front>
<title>Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)</title>
<author fullname='T. Eckert' initials='T.' role='editor' surname='Eckert'><organization/></author>
<author fullname='M. Behringer' initials='M.' surname='Behringer'><organization/></author>
<date month='May' year='2018'/>
<abstract><t>Operations, Administration, and Maintenance (OAM), as per BCP 161, for data networks is often subject to the problem of circular dependencies when relying on connectivity provided by the network to be managed for the OAM purposes.</t><t>Provisioning while bringing up devices and networks tends to be more difficult to automate than service provisioning later on.  Changes in core network functions impacting reachability cannot be automated because of ongoing connectivity requirements for the OAM equipment itself, and widely used OAM protocols are not secure enough to be carried across the network without security concerns.</t><t>This document describes how to integrate OAM processes with an autonomic control plane in order to provide stable and secure connectivity for those OAM processes.  This connectivity is not subject to the aforementioned circular dependencies.</t></abstract>
</front>
<seriesInfo name='RFC' value='8368'/>
<seriesInfo name='DOI' value='10.17487/RFC8368'/>
</reference>



<reference anchor='RFC8428' target='https://www.rfc-editor.org/info/rfc8428'>
<front>
<title>Sensor Measurement Lists (SenML)</title>
<author fullname='C. Jennings' initials='C.' surname='Jennings'><organization/></author>
<author fullname='Z. Shelby' initials='Z.' surname='Shelby'><organization/></author>
<author fullname='J. Arkko' initials='J.' surname='Arkko'><organization/></author>
<author fullname='A. Keranen' initials='A.' surname='Keranen'><organization/></author>
<author fullname='C. Bormann' initials='C.' surname='Bormann'><organization/></author>
<date month='August' year='2018'/>
<abstract><t>This specification defines a format for representing simple sensor measurements and device parameters in Sensor Measurement Lists (SenML).  Representations are defined in JavaScript Object Notation (JSON), Concise Binary Object Representation (CBOR), Extensible Markup Language (XML), and Efficient XML Interchange (EXI), which share the common SenML data model.  A simple sensor, such as a temperature sensor, could use one of these media types in protocols such as HTTP or the Constrained Application Protocol (CoAP) to transport the measurements of the sensor or to be configured.</t></abstract>
</front>
<seriesInfo name='RFC' value='8428'/>
<seriesInfo name='DOI' value='10.17487/RFC8428'/>
</reference>



<reference anchor='RFC8575' target='https://www.rfc-editor.org/info/rfc8575'>
<front>
<title>YANG Data Model for the Precision Time Protocol (PTP)</title>
<author fullname='Y. Jiang' initials='Y.' role='editor' surname='Jiang'><organization/></author>
<author fullname='X. Liu' initials='X.' surname='Liu'><organization/></author>
<author fullname='J. Xu' initials='J.' surname='Xu'><organization/></author>
<author fullname='R. Cummings' initials='R.' role='editor' surname='Cummings'><organization/></author>
<date month='May' year='2019'/>
<abstract><t>This document defines a YANG data model for the configuration of devices and clocks using the Precision Time Protocol (PTP) as specified in IEEE Std 1588-2008.  It also defines the retrieval of the configuration information, the data sets and the running states of PTP clocks.  The YANG module in this document conforms to the Network Management Datastore Architecture (NMDA).</t></abstract>
</front>
<seriesInfo name='RFC' value='8575'/>
<seriesInfo name='DOI' value='10.17487/RFC8575'/>
</reference>



<reference anchor='RFC8613' target='https://www.rfc-editor.org/info/rfc8613'>
<front>
<title>Object Security for Constrained RESTful Environments (OSCORE)</title>
<author fullname='G. Selander' initials='G.' surname='Selander'><organization/></author>
<author fullname='J. Mattsson' initials='J.' surname='Mattsson'><organization/></author>
<author fullname='F. Palombini' initials='F.' surname='Palombini'><organization/></author>
<author fullname='L. Seitz' initials='L.' surname='Seitz'><organization/></author>
<date month='July' year='2019'/>
<abstract><t>This document defines Object Security for Constrained RESTful Environments (OSCORE), a method for application-layer protection of the Constrained Application Protocol (CoAP), using CBOR Object Signing and Encryption (COSE).  OSCORE provides end-to-end protection between endpoints communicating using CoAP or CoAP-mappable HTTP. OSCORE is designed for constrained nodes and networks supporting a range of proxy operations, including translation between different transport protocols.</t><t>Although an optional functionality of CoAP, OSCORE alters CoAP options processing and IANA registration.  Therefore, this document updates RFC 7252.</t></abstract>
</front>
<seriesInfo name='RFC' value='8613'/>
<seriesInfo name='DOI' value='10.17487/RFC8613'/>
</reference>



<reference anchor='RFC8724' target='https://www.rfc-editor.org/info/rfc8724'>
<front>
<title>SCHC: Generic Framework for Static Context Header Compression and Fragmentation</title>
<author fullname='A. Minaburo' initials='A.' surname='Minaburo'><organization/></author>
<author fullname='L. Toutain' initials='L.' surname='Toutain'><organization/></author>
<author fullname='C. Gomez' initials='C.' surname='Gomez'><organization/></author>
<author fullname='D. Barthel' initials='D.' surname='Barthel'><organization/></author>
<author fullname='JC. Zuniga' initials='JC.' surname='Zuniga'><organization/></author>
<date month='April' year='2020'/>
<abstract><t>This document defines the Static Context Header Compression and fragmentation (SCHC) framework, which provides both a header compression mechanism and an optional fragmentation mechanism. SCHC has been designed with Low-Power Wide Area Networks (LPWANs) in mind.</t><t>SCHC compression is based on a common static context stored both in the LPWAN device and in the network infrastructure side. This document defines a generic header compression mechanism and its application to compress IPv6/UDP headers.</t><t>This document also specifies an optional fragmentation and reassembly mechanism. It can be used to support the IPv6 MTU requirement over the LPWAN technologies. Fragmentation is needed for IPv6 datagrams that, after SCHC compression or when such compression was not possible, still exceed the Layer 2 maximum payload size.</t><t>The SCHC header compression and fragmentation mechanisms are independent of the specific LPWAN technology over which they are used. This document defines generic functionalities and offers flexibility with regard to parameter settings and mechanism choices. This document standardizes the exchange over the LPWAN between two SCHC entities. Settings and choices specific to a technology or a product are expected to be grouped into profiles, which are specified in other documents. Data models for the context and profiles are out of scope.</t></abstract>
</front>
<seriesInfo name='RFC' value='8724'/>
<seriesInfo name='DOI' value='10.17487/RFC8724'/>
</reference>



<reference anchor='RFC8815' target='https://www.rfc-editor.org/info/rfc8815'>
<front>
<title>Deprecating Any-Source Multicast (ASM) for Interdomain Multicast</title>
<author fullname='M. Abrahamsson' initials='M.' surname='Abrahamsson'><organization/></author>
<author fullname='T. Chown' initials='T.' surname='Chown'><organization/></author>
<author fullname='L. Giuliano' initials='L.' surname='Giuliano'><organization/></author>
<author fullname='T. Eckert' initials='T.' surname='Eckert'><organization/></author>
<date month='August' year='2020'/>
<abstract><t>This document recommends deprecation of the use of Any-Source Multicast (ASM) for interdomain multicast. It recommends the use of Source-Specific Multicast (SSM) for interdomain multicast applications and recommends that hosts and routers in these deployments fully support SSM.  The recommendations in this document do not preclude the continued use of ASM within a single organization or domain and are especially easy to adopt in existing deployments of intradomain ASM using PIM Sparse Mode (PIM-SM).</t></abstract>
</front>
<seriesInfo name='BCP' value='229'/>
<seriesInfo name='RFC' value='8815'/>
<seriesInfo name='DOI' value='10.17487/RFC8815'/>
</reference>



<reference anchor='RFC8824' target='https://www.rfc-editor.org/info/rfc8824'>
<front>
<title>Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)</title>
<author fullname='A. Minaburo' initials='A.' surname='Minaburo'><organization/></author>
<author fullname='L. Toutain' initials='L.' surname='Toutain'><organization/></author>
<author fullname='R. Andreasen' initials='R.' surname='Andreasen'><organization/></author>
<date month='June' year='2021'/>
<abstract><t>This document defines how to compress Constrained Application Protocol (CoAP) headers using the Static Context Header Compression and fragmentation (SCHC) framework. SCHC defines a header compression mechanism adapted for Constrained Devices. SCHC uses a static description of the header to reduce the header's redundancy and size. While RFC 8724 describes the SCHC compression and fragmentation framework, and its application for IPv6/UDP headers, this document applies SCHC to CoAP headers. The CoAP header structure differs from IPv6 and UDP, since CoAP uses a flexible header with a variable number of options, themselves of variable length. The CoAP message format is asymmetric: the request messages have a header format different from the format in the response messages. This specification gives guidance on applying SCHC to flexible headers and how to leverage the asymmetry for more efficient compression Rules.</t></abstract>
</front>
<seriesInfo name='RFC' value='8824'/>
<seriesInfo name='DOI' value='10.17487/RFC8824'/>
</reference>



<reference anchor='RFC8994' target='https://www.rfc-editor.org/info/rfc8994'>
<front>
<title>An Autonomic Control Plane (ACP)</title>
<author fullname='T. Eckert' initials='T.' role='editor' surname='Eckert'><organization/></author>
<author fullname='M. Behringer' initials='M.' role='editor' surname='Behringer'><organization/></author>
<author fullname='S. Bjarnason' initials='S.' surname='Bjarnason'><organization/></author>
<date month='May' year='2021'/>
<abstract><t>Autonomic functions need a control plane to communicate, which depends on some addressing and routing.  This Autonomic Control Plane should ideally be self-managing and be as independent as possible of configuration.  This document defines such a plane and calls it the &quot;Autonomic Control Plane&quot;, with the primary use as a control plane for autonomic functions.  It also serves as a &quot;virtual out-of-band channel&quot; for Operations, Administration, and Management (OAM) communications over a network that provides automatically configured, hop-by-hop authenticated and encrypted communications via automatically configured IPv6 even when the network is not configured or is misconfigured.</t></abstract>
</front>
<seriesInfo name='RFC' value='8994'/>
<seriesInfo name='DOI' value='10.17487/RFC8994'/>
</reference>



<reference anchor='RFC9008' target='https://www.rfc-editor.org/info/rfc9008'>
<front>
<title>Using RPI Option Type, Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data Plane</title>
<author fullname='M.I. Robles' initials='M.I.' surname='Robles'><organization/></author>
<author fullname='M. Richardson' initials='M.' surname='Richardson'><organization/></author>
<author fullname='P. Thubert' initials='P.' surname='Thubert'><organization/></author>
<date month='April' year='2021'/>
<abstract><t>This document looks at different data flows through Low-Power and Lossy Networks (LLN) where RPL (IPv6 Routing Protocol for Low-Power and Lossy Networks) is used to establish routing. The document enumerates the cases where RPL Packet Information (RPI) Option Type (RFC 6553), RPL Source Route Header (RFC 6554), and IPv6-in-IPv6 encapsulation are required in the data plane. This analysis provides the basis upon which to design efficient compression of these headers. This document updates RFC 6553 by adding a change to the RPI Option Type. Additionally, this document updates RFC 6550 by defining a flag in the DODAG Information Object (DIO) Configuration option to indicate this change and updates RFC 8138 as well to consider the new Option Type when the RPL Option is decompressed.</t></abstract>
</front>
<seriesInfo name='RFC' value='9008'/>
<seriesInfo name='DOI' value='10.17487/RFC9008'/>
</reference>



<reference anchor='RFC9010' target='https://www.rfc-editor.org/info/rfc9010'>
<front>
<title>Routing for RPL (Routing Protocol for Low-Power and Lossy Networks) Leaves</title>
<author fullname='P. Thubert' initials='P.' role='editor' surname='Thubert'><organization/></author>
<author fullname='M. Richardson' initials='M.' surname='Richardson'><organization/></author>
<date month='April' year='2021'/>
<abstract><t>This specification provides a mechanism for a host that implements a routing-agnostic interface based on IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery to obtain reachability services across a network that leverages RFC 6550 for its routing operations. It updates RFCs 6550, 6775, and 8505.</t></abstract>
</front>
<seriesInfo name='RFC' value='9010'/>
<seriesInfo name='DOI' value='10.17487/RFC9010'/>
</reference>



<reference anchor='RFC9011' target='https://www.rfc-editor.org/info/rfc9011'>
<front>
<title>Static Context Header Compression and Fragmentation (SCHC) over LoRaWAN</title>
<author fullname='O. Gimenez' initials='O.' role='editor' surname='Gimenez'><organization/></author>
<author fullname='I. Petrov' initials='I.' role='editor' surname='Petrov'><organization/></author>
<date month='April' year='2021'/>
<abstract><t>The Static Context Header Compression and fragmentation (SCHC) specification (RFC 8724) describes generic header compression and fragmentation techniques for Low-Power Wide Area Network (LPWAN) technologies. SCHC is a generic mechanism designed for great flexibility so that it can be adapted for any of the LPWAN technologies.</t><t>This document defines a profile of SCHC (RFC 8724) for use in LoRaWAN networks and provides elements such as efficient parameterization and modes of operation.</t></abstract>
</front>
<seriesInfo name='RFC' value='9011'/>
<seriesInfo name='DOI' value='10.17487/RFC9011'/>
</reference>



<reference anchor='RFC9119' target='https://www.rfc-editor.org/info/rfc9119'>
<front>
<title>Multicast Considerations over IEEE 802 Wireless Media</title>
<author fullname='C. Perkins' initials='C.' surname='Perkins'><organization/></author>
<author fullname='M. McBride' initials='M.' surname='McBride'><organization/></author>
<author fullname='D. Stanley' initials='D.' surname='Stanley'><organization/></author>
<author fullname='W. Kumari' initials='W.' surname='Kumari'><organization/></author>
<author fullname='JC. Zúñiga' initials='JC.' surname='Zúñiga'><organization/></author>
<date month='October' year='2021'/>
<abstract><t>Well-known issues with multicast have prevented the deployment of multicast in 802.11 (Wi-Fi) and other local-area wireless environments. This document describes the known limitations of wireless (primarily 802.11) Layer 2 multicast.  Also described are certain multicast enhancement features that have been specified by the IETF and by IEEE 802 for wireless media, as well as some operational choices that can be made to improve the performance of the network.  Finally, some recommendations are provided about the usage and combination of these features and operational choices.</t></abstract>
</front>
<seriesInfo name='RFC' value='9119'/>
<seriesInfo name='DOI' value='10.17487/RFC9119'/>
</reference>



<reference anchor='RFC9148' target='https://www.rfc-editor.org/info/rfc9148'>
<front>
<title>EST-coaps: Enrollment over Secure Transport with the Secure Constrained Application Protocol</title>
<author fullname='P. van der Stok' initials='P.' surname='van der Stok'><organization/></author>
<author fullname='P. Kampanakis' initials='P.' surname='Kampanakis'><organization/></author>
<author fullname='M. Richardson' initials='M.' surname='Richardson'><organization/></author>
<author fullname='S. Raza' initials='S.' surname='Raza'><organization/></author>
<date month='April' year='2022'/>
<abstract><t>Enrollment over Secure Transport (EST) is used as a certificate provisioning protocol over HTTPS. Low-resource devices often use the lightweight Constrained Application Protocol (CoAP) for message exchanges. This document defines how to transport EST payloads over secure CoAP (EST-coaps), which allows constrained devices to use existing EST functionality for provisioning certificates.</t></abstract>
</front>
<seriesInfo name='RFC' value='9148'/>
<seriesInfo name='DOI' value='10.17487/RFC9148'/>
</reference>



<reference anchor='RFC9176' target='https://www.rfc-editor.org/info/rfc9176'>
<front>
<title>Constrained RESTful Environments (CoRE) Resource Directory</title>
<author fullname='C. Amsüss' initials='C.' role='editor' surname='Amsüss'><organization/></author>
<author fullname='Z. Shelby' initials='Z.' surname='Shelby'><organization/></author>
<author fullname='M. Koster' initials='M.' surname='Koster'><organization/></author>
<author fullname='C. Bormann' initials='C.' surname='Bormann'><organization/></author>
<author fullname='P. van der Stok' initials='P.' surname='van der Stok'><organization/></author>
<date month='April' year='2022'/>
<abstract><t>In many Internet of Things (IoT) applications, direct discovery of resources is not practical due to sleeping nodes or networks where multicast traffic is inefficient. These problems can be solved by employing an entity called a Resource Directory (RD), which contains information about resources held on other servers, allowing lookups to be performed for those resources. The input to an RD is composed of links, and the output is composed of links constructed from the information stored in the RD. This document specifies the web interfaces that an RD supports for web servers to discover the RD and to register, maintain, look up, and remove information on resources. Furthermore, new target attributes useful in conjunction with an RD are defined.</t></abstract>
</front>
<seriesInfo name='RFC' value='9176'/>
<seriesInfo name='DOI' value='10.17487/RFC9176'/>
</reference>



<reference anchor='RFC9178' target='https://www.rfc-editor.org/info/rfc9178'>
<front>
<title>Building Power-Efficient Constrained Application Protocol (CoAP) Devices for Cellular Networks</title>
<author fullname='J. Arkko' initials='J.' surname='Arkko'><organization/></author>
<author fullname='A. Eriksson' initials='A.' surname='Eriksson'><organization/></author>
<author fullname='A. Keränen' initials='A.' surname='Keränen'><organization/></author>
<date month='May' year='2022'/>
<abstract><t>This memo discusses the use of the Constrained Application Protocol (CoAP) in building sensors and other devices that employ cellular networks as a communications medium. Building communicating devices that employ these networks is obviously well known, but this memo focuses specifically on techniques necessary to minimize power consumption.</t></abstract>
</front>
<seriesInfo name='RFC' value='9178'/>
<seriesInfo name='DOI' value='10.17487/RFC9178'/>
</reference>


<reference anchor='I-D.ajunior-energy-awareness-00'>
   <front>
      <title>Energy-awareness metrics global applicability guidelines</title>
      <author fullname='Antonio Junior' initials='A.' surname='Junior'>
         </author>
      <author fullname='Rute C. Sofia' initials='R. C.' surname='Sofia'>
         </author>
      <date day='16' month='October' year='2012'/>
      <abstract>
	 <t>   This document describes a new set of energy-awareness metrics which
   have been devised to be applicable to any multihop routing protocol,
   including the Routing for Low Power and Lossy Networks (RPL)
   protocol.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-ajunior-energy-awareness-00'/>
   <format target='https://www.ietf.org/archive/id/draft-ajunior-energy-awareness-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.claise-power-management-arch'>
   <front>
      <title>Power Management Architecture</title>
      <author fullname='Benoit Claise'>
	 </author>
      <author fullname='John Parello'>
	 </author>
      <author fullname='Brad Schoening'>
	 </author>
      <date day='22' month='October' year='2010'/>
      <abstract>
	 <t>This document defines the power management architecture.  




































  &lt;Claise, et. Al&gt;

  Expires April 20, 2011



[page 2] 



  Internet-Draft
 &lt;Power Management Archictecure&gt;
Octobre 2010
	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-claise-power-management-arch-02'/>
   <format target='https://www.ietf.org/archive/id/draft-claise-power-management-arch-02.txt' type='TXT'/>
</reference>


<reference anchor='I-D.bormann-core-roadmap-05'>
   <front>
      <title>CoRE Roadmap and Implementation Guide</title>
      <author fullname='Carsten Bormann' initials='C.' surname='Bormann'>
         </author>
      <date day='21' month='October' year='2013'/>
      <abstract>
	 <t>   The CoRE set of protocols, in particular the CoAP protocol, is
   defined in draft-ietf-core-coap in conjunction with a number of
   specifications that are currently nearing completion.  There are also
   several dozen more individual Internet-Drafts in various states of
   development, with various levels of WG review and interest.

   Today, this is simply a bewildering array of documents.  Beyond the
   main four documents, it is hard to find relevant information and
   assess the status of proposals.  At the level of Internet-Drafts, the
   IETF has only adoption as a WG document to assign status - too crude
   an instrument to assess the level of development and standing for
   anyone who does not follow the daily proceedings of the WG.

   With a more long-term perspective, as additional drafts mature and
   existing specifications enter various levels of spec maintenance, the
   entirety of these specifications may become harder to understand,
   pose specific implementation problems, or be simply inconsistent.

   The present guide aims to provide a roadmap to these documents as
   well as provide specific advice how to use these specifications in
   combination.  In certain cases, it may provide clarifications or even
   corrections to the specifications referenced.

   This guide is intended as a continued work-in-progress, i.e. a long-
   lived Internet-Draft, to be updated whenever new information becomes
   available and new consensus on how to handle issues is formed.
   Similar to the ROHC implementation guide, RFC 4815, it might be
   published as an RFC at some future time later in the acceptance curve
   of the specifications.

   This document does not describe a new protocol or attempt to set a
   new standard of any kind - it mostly describes good practice in using
   the existing specifications, but it may also document emerging
   consensus where a correction needs to be made.

   (TODO: The present version does not completely cover the new
   Internet-Drafts submitted concurrently with it; it is to be updated
   by the start of IETF88.)

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-bormann-core-roadmap-05'/>
   <format target='https://www.ietf.org/archive/id/draft-bormann-core-roadmap-05.txt' type='TXT'/>
</reference>


<reference anchor='I-D.castellani-core-alive'>
   <front>
      <title>CoAP Alive Message</title>
      <author fullname='Angelo P. Castellani'>
	 </author>
      <author fullname='Salvatore Loreto'>
	 </author>
      <date day='29' month='March' year='2012'/>
      <abstract>
	 <t>   In the context of a Constrained RESTful Environment (CoRE), hosts
   could frequently be energy-constrained and be turned off the vast
   majority of time for energy-saving purposes.

   In the case of a CoAP server, while it is offline, it is neither
   available to serve requests.  Clients desiring to access its
   resources have no way to understand when they will find it up again.

   This specification provides a simple new message that gives to a CoAP
   server the ability to signal its current availability in the network.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-castellani-core-alive-00'/>
   <format target='https://www.ietf.org/archive/id/draft-castellani-core-alive-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.chakrabarti-nordmark-energy-aware-nd'>
   <front>
      <title>Energy Aware IPv6 Neighbor Discovery Optimizations</title>
      <author fullname='Samita Chakrabarti'>
	 </author>
      <author fullname='Erik Nordmark'>
	 </author>
      <author fullname='Margaret Wasserman'>
	 </author>
      <date day='12' month='March' year='2012'/>
      <abstract>
	 <t>   IPv6 Neighbor Discovery (RFC 4861) protocol has been designed for
   neighbor&#39;s address resolution, unreachability detection, address
   autoconfiguration, router advertisement and solicitation.  With the
   progress of Internet adoption on various industries including home,
   wireless and machine-to-machine communications, there is a desire for
   optimizing legacy IPv6 Neighbor Discovery protocol to be more
   efficient in terms of number of signaling messages in the network.
   Efficient IPv6 Neighbor Discovery is useful for energy-efficient
   networks and as well for overlay networks such as VLANs with large
   number of nodes.  This document describes a method of optimizations
   by reducing periodic multicast messages, frequent Neighbor
   Solicitation messages and discusses interoperability with legacy IPv6
   nodes.  It also addresses the ND denial of service issues by
   introducing node Registration procedure.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-chakrabarti-nordmark-energy-aware-nd-02'/>
   <format target='https://www.ietf.org/archive/id/draft-chakrabarti-nordmark-energy-aware-nd-02.txt' type='TXT'/>
</reference>


<reference anchor='I-D.zhang-greennet'>
   <front>
      <title>Power-aware Routing and Traffic Engineering: Requirements, Approaches, and Issues</title>
      <author fullname='Beichuan Zhang'>
	 </author>
      <author fullname='Junxiao Shi'>
	 </author>
      <author fullname='Jie Dong'>
	 </author>
      <author fullname='Mingui Zhang'>
	 </author>
      <date day='10' month='January' year='2013'/>
      <abstract>
	 <t>   Energy consumption of network infrastructures is rising fast.  There
   are emerging needs for power-aware routing and traffic engineering,
   which adjust routing paths to help reduce power consumption network-
   wide.  This document gives a high-level analysis on the basic
   requirements, approaches, and potential issues in power-aware routing
   and traffic engineering.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-zhang-greennet-01'/>
   <format target='https://www.ietf.org/archive/id/draft-zhang-greennet-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.fossati-core-monitor-option'>
   <front>
      <title>Monitor Option for CoAP</title>
      <author fullname='Thomas Fossati'>
	 </author>
      <author fullname='Pierpaolo Giacomin'>
	 </author>
      <author fullname='Salvatore Loreto'>
	 </author>
      <date day='9' month='July' year='2012'/>
      <abstract>
	 <t>   This memo defines Monitor, an additional Option for the Constrained
   Application Protocol (CoAP) especially targeted at sleepy sensors.

   The Monitor Option complements the typical Observe pattern, enabling
   the tracking of a resource hosted by a node sleeping most of the
   time, by taking care of establishing and maintaining an Observe
   relationship with the (sleepy) origin on behalf of the (sleepy)
   client.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-fossati-core-monitor-option-00'/>
   <format target='https://www.ietf.org/archive/id/draft-fossati-core-monitor-option-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.fossati-core-publish-option'>
   <front>
      <title>Publish Option for CoAP</title>
      <author fullname='Thomas Fossati'>
	 </author>
      <author fullname='Pierpaolo Giacomin'>
	 </author>
      <author fullname='Salvatore Loreto'>
	 </author>
      <date day='6' month='January' year='2014'/>
      <abstract>
	 <t>   This memo defines the Publish Option for the Constrained Application
   Protocol (CoAP).  The Publish Option is used by a CoAP Endpoint to
   control the authority delegation of one of its resources to another
   Endpoint.  All the phases of the authority delegation process (setup,
   renewal, cancellation) are controlled by a simple RESTful protocol.

   This memo also introduces the &#39;proxies&#39; Web Linking relation type, to
   be used by a CoAP Proxy to explicitly advertise the resources that it
   can serve - either from its cache, or by forwarding the Client&#39;s
   request upstream.

   The Publish Option and the &#39;proxies&#39; relation provide the building
   blocks for a comprehensive, in-protocol, solution to the sleepy/
   intermittent Endpoint use case.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-fossati-core-publish-option-03'/>
   <format target='https://www.ietf.org/archive/id/draft-fossati-core-publish-option-03.txt' type='TXT'/>
</reference>


<reference anchor='I-D.giacomin-core-sleepy-option'>
   <front>
      <title>Sleepy Option for CoAP</title>
      <author fullname='Thomas Fossati'>
	 </author>
      <author fullname='Pierpaolo Giacomin'>
	 </author>
      <author fullname='Salvatore Loreto'>
	 </author>
      <author fullname='Mirko Rossini'>
	 </author>
      <date day='29' month='February' year='2012'/>
      <abstract>
	 <t>   This memo defines a framework for allowing asynchronous communication
   between sleepy sensors mediated by a supporting Proxy node.  The
   Proxy acts as a store-and-forward agent that handles requests on
   behalf of a sleepy client, and buffers responses coming from the
   target origin until the requesting client wakes up and get the
   computation results.

   A new CoAP option, Sleepy, is defined to initiate and control the
   asynchronous exchange.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-giacomin-core-sleepy-option-00'/>
   <format target='https://www.ietf.org/archive/id/draft-giacomin-core-sleepy-option-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.ietf-core-coap-pubsub'>
   <front>
      <title>Publish-Subscribe Broker for the Constrained Application Protocol (CoAP)</title>
      <author fullname='Michael Koster'>
	 <organization>SmartThings</organization>
      </author>
      <author fullname='Ari Keranen'>
	 <organization>Ericsson</organization>
      </author>
      <author fullname='Jaime Jimenez'>
	 <organization>Ericsson</organization>
      </author>
      <date day='4' month='May' year='2022'/>
      <abstract>
	 <t>   The Constrained Application Protocol (CoAP), and related extensions
   are intended to support machine-to-machine communication in systems
   where one or more nodes are resource constrained, in particular for
   low power wireless sensor networks.  This document defines a publish-
   subscribe Broker for CoAP that extends the capabilities of CoAP for
   supporting nodes with long breaks in connectivity and/or up-time.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-ietf-core-coap-pubsub-10'/>
   <format target='https://www.ietf.org/archive/id/draft-ietf-core-coap-pubsub-10.txt' type='TXT'/>
</reference>


<reference anchor='I-D.ietf-dnssd-srp'>
   <front>
      <title>Service Registration Protocol for DNS-Based Service Discovery</title>
      <author fullname='Ted Lemon'>
	 <organization>Apple Inc.</organization>
      </author>
      <author fullname='Stuart Cheshire'>
	 <organization>Apple Inc.</organization>
      </author>
      <date day='24' month='April' year='2022'/>
      <abstract>
	 <t>   The Service Registration Protocol for DNS-Based Service Discovery
   uses the standard DNS Update mechanism to enable DNS-Based Service
   Discovery using only unicast packets.  This makes it possible to
   deploy DNS Service Discovery without multicast, which greatly
   improves scalability and improves performance on networks where
   multicast service is not an optimal choice, particularly 802.11
   (Wi-Fi) and 802.15.4 (IoT) networks.  DNS-SD Service registration
   uses public keys and SIG(0) to allow services to defend their
   registrations against attack.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-ietf-dnssd-srp-13'/>
   <format target='https://www.ietf.org/archive/id/draft-ietf-dnssd-srp-13.txt' type='TXT'/>
</reference>


<reference anchor='I-D.jennings-energy-pricing'>
   <front>
      <title>Communication of Energy Price Information</title>
      <author fullname='Cullen Jennings'>
	 </author>
      <author fullname='Bruce Nordman'>
	 </author>
      <date day='10' month='July' year='2011'/>
      <abstract>
	 <t>   This specification defines media types for representing the future
   price of energy in JSON.  It also defines a way for a client device,
   such as a car, refrigerator, air conditioner, water heater, or
   display to discover a web server that can provide the future price
   for local electrical energy.  This will allow the client device to
   make intelligent decisions about when to use energy, and enable price
   distribution when the building is off-grid.  It enables obtaining
   price from a local or non-local price server.

   This draft is an early skeleton of a draft to start discussion around
   this idea.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-jennings-energy-pricing-01'/>
   <format target='https://www.ietf.org/archive/id/draft-jennings-energy-pricing-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.manral-bmwg-power-usage'>
   <front>
      <title>Benchmarking Power usage of networking devices</title>
      <author fullname='Vishwas Manral'>
	 </author>
      <author fullname='Puneet Sharma'>
	 </author>
      <author fullname='Sujata Banerjee'>
	 </author>
      <author fullname='Yang Ping'>
	 </author>
      <date day='12' month='March' year='2013'/>
      <abstract>
	 <t>   With the rapid growth of networks around the globe there is an ever
   increasing need to improve the energy efficiency of network devices.
   Operators are begining to seek more information of power consumption
   in the network, have no standard mechanism to measure, report and
   compare power usage of different networking equipment under different
   network configuration and conditions.

   This document provides suggestions for measuring power usage of live
   networks under different traffic loads and various switch router
   configuration settings.  It provides a benchmarking suite which can
   be employed for any networking device .

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-manral-bmwg-power-usage-04'/>
   <format target='https://www.ietf.org/archive/id/draft-manral-bmwg-power-usage-04.txt' type='TXT'/>
</reference>


<reference anchor='I-D.mjsraman-panet-inter-as-power-source'>
   <front>
      <title>Reducing Power Consumption using BGP with power source data</title>
      <author fullname='Shankar Raman'>
	 </author>
      <author fullname='Balaji Venkat Venkataswami'>
	 </author>
      <author fullname='Gaurav Raina'>
	 </author>
      <author fullname='Kamakoti Veezhinathan'>
	 </author>
      <date day='25' month='January' year='2013'/>
      <abstract>
	 <t>   In this paper, we propose a framework to reduce the aggregate power
   consumption of the Internet using a collaborative approach between
   Autonomous Systems (AS). We identify the low-power paths among the AS
   and then use Traffic Engineering (TE) techniques to route the packets
   along the paths. Such low-power paths can be identified by using the
   consumed-power-to-available-bandwidth (PWR) ratio as an additional
   constraint in the Constrained Shortest Path First (CSPF) algorithm.
   For re-routing the data traffic through these low-power paths, the
   Inter-AS Traffic Engineered Label Switched Path (TE-LSP) that spans
   multiple AS can be used. Extensions to the Border Gateway Protocol
   (BGP) can be used to disseminate the PWR ratio metric among the AS
   thereby creating a collaborative approach to reduce the power
   consumption. Since calculating the low-power paths can be
   computationally intensive, a graph-labeling heuristic is also
   proposed. This heuristic reduces the computational complexity but may
   provide a sub-optimal low-power path. The feasibility of our
   approaches is illustrated by applying our algorithm to a subset of
   the Internet. The techniques proposed in this paper for the Inter-AS
   power reduction require minimal modifications to the existing
   features of the Internet. The proposed techniques can be extended to
   other levels of Internet hierarchy, such as Intra-AS paths, through
   suitable modifications. The addition to this draft is that the power
   source of the Autonomous system is broken down to a ratio called PWR-
   SOURCE Ratio and used in the arrival of the metric to be used for
   this purpose.



	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-mjsraman-panet-inter-as-power-source-00'/>
   <format target='https://www.ietf.org/archive/id/draft-mjsraman-panet-inter-as-power-source-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.mjsraman-rtgwg-pim-power'>
   <front>
      <title>Building power optimal Multicast Trees</title>
      <author fullname='Shankar Raman'>
	 </author>
      <author fullname='Balaji Venkat Venkataswami'>
	 </author>
      <author fullname='Gaurav Raina'>
	 </author>
      <author fullname='Vasan Srini'>
	 </author>
      <date day='27' month='March' year='2012'/>
      <abstract>
	 <t>   Power consumption in multicast replication operations is an area of
   concern and choosing suitable replication points that can decrease
   power consumption overall assumes importance. Multicast replication
   capacity is an attribute of every line card of major routers and
   multi-layer switches that support multicast in the core of an
   Internet Service Provider (ISP) or an enterprise network.

   Currently multicast replication points on Point-to-Multipoint
   Multicast Distribution trees consume power while delivering multiple
   output streams of data from a given input stream. The multicast
   distribution trees are constructed without any regard for a proper
   placement of the replication points and consequent optimal power
   consumption at these points.

   This results in overloading certain routers while under-utilizing
   others. An optimal usage of these replication resources could reduce
   power consumption on these routers bringing power consumption to
   optimality. In this paper, we propose a mechanism by which Multicast
   Distribution Trees are constructed for carrying multicast traffic
   across multiple routers within a given network. We propose that these
   Multicast Distribution Trees be built by using the information
   pertaining to power-replication capacity ratio available with fine
   grained components such as multicast capable line-cards of routers
   and multi-layer switches deployed within a network.


	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-mjsraman-rtgwg-pim-power-02'/>
   <format target='https://www.ietf.org/archive/id/draft-mjsraman-rtgwg-pim-power-02.txt' type='TXT'/>
</reference>


<reference anchor='I-D.okamoto-ccamp-midori-gmpls-extension-reqs'>
   <front>
      <title>Requirements of GMPLS Extensions for Energy Efficient Traffic Engineering</title>
      <author fullname='Satoru Okamoto'>
	 </author>
      <date day='14' month='March' year='2013'/>
      <abstract>
	 <t>       This document discusses some of extensions required in existing GMPLS
       OSPF routing protocol, RSVP signaling protocol, and LMP to support
       the energy efficient traffic engineering technology.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-okamoto-ccamp-midori-gmpls-extension-reqs-02'/>
   <format target='https://www.ietf.org/archive/id/draft-okamoto-ccamp-midori-gmpls-extension-reqs-02.txt' type='TXT'/>
</reference>


<reference anchor='I-D.rahman-core-sleepy-nodes-do-we-need'>
   <front>
      <title>Sleepy Devices: Do we need to Support them in CORE?</title>
      <author fullname='Akbar Rahman'>
	 </author>
      <date day='11' month='February' year='2014'/>
      <abstract>
	 <t>   This document summarizes the discussion in the CORE WG related to the
   question of whether support of sleepy devices is required for the
   CoAP protocol, CORE Link Format, CORE Resource Directory, etc.  The
   only goal of this document is to trigger discussions in the CORE WG
   so that all relevant considerations for sleeping devices are taken
   into account.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-rahman-core-sleepy-nodes-do-we-need-01'/>
   <format target='https://www.ietf.org/archive/id/draft-rahman-core-sleepy-nodes-do-we-need-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.rahman-core-sleepy-problem-statement'>
   <front>
      <title>Sleepy Devices in CoAP - Problem Statement</title>
      <author fullname='Akbar Rahman'>
	 </author>
      <author fullname='Thomas Fossati'>
	 </author>
      <author fullname='Salvatore Loreto'>
	 </author>
      <author fullname='Matthieu Vial'>
	 </author>
      <date day='21' month='October' year='2012'/>
      <abstract>
	 <t>   This document analyzes the COAP protocol issues related to sleeping
   devices.  The only goal of this document is to trigger discussions in
   the CORE WG so that all relevant considerations for sleeping devices
   are taken into account when designing CoAP.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-rahman-core-sleepy-problem-statement-01'/>
   <format target='https://www.ietf.org/archive/id/draft-rahman-core-sleepy-problem-statement-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.rahman-core-sleepy'>
   <front>
      <title>Enhanced Sleepy Node Support for CoAP</title>
      <author fullname='Akbar Rahman'>
	 </author>
      <date day='11' month='February' year='2014'/>
      <abstract>
	 <t>   CoAP is a specialized web transfer protocol for constrained devices.
   These devices typically have some combination of limited battery
   power, small memory footprint and low throughput links.  It is
   expected that in CoAP networks there will be a certain portion of
   devices that are &quot;sleepy&quot; and which may occasionally go into a sleep
   mode (i.e. go into a low power state to conserve power) and
   temporarily suspend CoAP protocol communication.  This document
   proposes a minimal and efficient mechanism building on the Resource
   Directory (RD) functionality to enhance sleepy node support in CoAP
   networks.  The RD functionality may be incorporated as part of a CoAP
   Proxy.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-rahman-core-sleepy-05'/>
   <format target='https://www.ietf.org/archive/id/draft-rahman-core-sleepy-05.txt' type='TXT'/>
</reference>


<reference anchor='I-D.retana-rtgwg-eacp'>
   <front>
      <title>A Framework and Requirements for Energy Aware Control Planes</title>
      <author fullname='Alvaro Retana'>
	 </author>
      <author fullname='Russ White'>
	 </author>
      <author fullname='Manuel Paul'>
	 </author>
      <date day='24' month='October' year='2014'/>
      <abstract>
	 <t>   There has been, for several years, a rising concern over the energy
   usage of large scale networks.  This concern is strongly focused on
   campus, data center, and other highly concentrated deployments of
   network infrastructure.  Given the steadily increasing demand for
   higher network speeds, always-on service models, and ubiquitous
   network coverage, it is also of growing importance for
   telecommunication networks both local and wide area in scope.  One of
   the issues in moving forward to reduce energy usage is to ensure that
   the network can still meet the performance specifications required to
   support the applications running over it.

   This document provides an overview of the various areas of concern in
   the interaction between network performance and efforts at energy
   aware control planes, as a guide for those working on modifying
   current control planes or designing new control planes to improve the
   energy efficiency of high density, highly complex, network
   deployments.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-retana-rtgwg-eacp-03'/>
   <format target='https://www.ietf.org/archive/id/draft-retana-rtgwg-eacp-03.txt' type='TXT'/>
</reference>


<reference anchor='I-D.suzuki-eens-requirements'>
   <front>
      <title>Requirements for an Energy-Efficient Network System</title>
      <author fullname='Toshiaki Suzuki'>
	 </author>
      <author fullname='Toshiaki Tarui'>
	 </author>
      <date day='15' month='October' year='2012'/>
      <abstract>
	 <t>   Requirements concerning an energy-efficient network system such as a
   cloud system are presented.  Specifically, a large-scale cloud
   system, which is composed of multiple data centers (DCs) and a wide
   area network (WAN) to connect these DCs, is focused on.  The problems
   needed to be overcome in order to make the system energy efficient
   are presented.  The requirements that must be satisfied in order to
   solve these problems are also presented.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-suzuki-eens-requirements-00'/>
   <format target='https://www.ietf.org/archive/id/draft-suzuki-eens-requirements-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.vial-core-mirror-proxy'>
   <front>
      <title>CoRE Mirror Server</title>
      <author fullname='Matthieu Vial'>
	 </author>
      <date day='13' month='July' year='2012'/>
      <abstract>
	 <t>   The Constrained RESTful Environments (CoRE) working group aims at
   realizing the REpresentational State Transfer (REST) architecture in
   a suitable form for the most constrained nodes.  Thanks to the
   Constrained Application Protocol (CoAP), REST is now applicable to
   constrained networks.  However the most energy-constrained devices
   may enter sleep mode and disconnect their network link during several
   minutes to save energy, hence preventing them from acting as
   traditional web servers.  This document describes how a sleeping
   device can store resource representations in an entity called Mirror
   Server and participate in a constrained RESTful environment.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-vial-core-mirror-proxy-01'/>
   <format target='https://www.ietf.org/archive/id/draft-vial-core-mirror-proxy-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.vial-core-mirror-server'>
   <front>
      <title>CoRE Mirror Server</title>
      <author fullname='Matthieu Vial'>
	 </author>
      <date day='10' month='April' year='2013'/>
      <abstract>
	 <t>   The Constrained RESTful Environments (CoRE) working group aims at
   realizing the REpresentational State Transfer (REST) architecture in
   a suitable form for the most constrained nodes.  Thanks to the
   Constrained Application Protocol (CoAP), REST is now applicable to
   constrained networks.  However the most energy-constrained devices
   may enter sleep mode and disconnect their network link during several
   minutes to save energy, hence preventing them from acting as
   traditional web servers.  This document describes how a sleeping
   device can store resource representations in an entity called Mirror
   Server and participate in a constrained RESTful environment.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-vial-core-mirror-server-01'/>
   <format target='https://www.ietf.org/archive/id/draft-vial-core-mirror-server-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.wang-roll-energy-optimization-scheme'>
   <front>
      <title>An energy optimization routing scheme for LLSs</title>
      <author fullname='Hao Wang'>
	 </author>
      <author fullname='Min Wei'>
	 </author>
      <author fullname='Shuaiyong Li'>
	 </author>
      <author fullname='Qingqing Huang'>
	 </author>
      <author fullname='Ping Wang'>
	 </author>
      <author fullname='Chaomei Wang'>
	 </author>
      <date day='21' month='February' year='2017'/>
      <abstract>
	 <t>   Low-Power and Lossy Networks (LLNs) are composed of devices that
   have constraints on processing power, memory, and energy (battery
   power). It is obvious that conserving energy is especially important
   in the LLNs. This document is aimed at proposing an efficient and
   effective scheme to optimize the energy in the process of seeking
   the DAG root node.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-wang-roll-energy-optimization-scheme-00'/>
   <format target='https://www.ietf.org/archive/id/draft-wang-roll-energy-optimization-scheme-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.winter-energy-efficient-internet'>
   <front>
      <title>Towards an Energy-Efficient Internet</title>
      <author fullname='Rolf Winter'>
	 </author>
      <author fullname='Sangjin Jeong'>
	 </author>
      <author fullname='JinHyeock Choi'>
	 </author>
      <date day='22' month='October' year='2012'/>
      <abstract>
	 <t>   Climate change and cost drives all sectors of industry and society as
   a whole towards more energy-efficient technology, products and life
   styles.  The collection of Internet infrastructure and the attached
   devices are a large user of electrical energy and therefore of course
   are no exception regarding this trend.  This memo attempts to
   identify obstacles and more importantly technology options for an
   energy-efficient Internet with a focus on the protocols that are the
   product of the IETF.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-winter-energy-efficient-internet-01'/>
   <format target='https://www.ietf.org/archive/id/draft-winter-energy-efficient-internet-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.zhang-panet-problem-statement'>
   <front>
      <title>Power-Aware Networks (PANET): Problem Statement</title>
      <author fullname='Beichuan Zhang'>
	 </author>
      <author fullname='Junxiao Shi'>
	 </author>
      <author fullname='Jie Dong'>
	 </author>
      <author fullname='Mingui Zhang'>
	 </author>
      <author fullname='Mohamed Boucadair'>
	 </author>
      <date day='15' month='October' year='2013'/>
      <abstract>
	 <t>   Energy consumption of network infrastructures is growing fast due to
   exponential growth of data traffic and the deployment of increasingly
   powerful equipment.  There are emerging needs for power-aware routing
   and traffic engineering, which adapt routing paths to traffic load in
   order to reduce energy consumption network-wide.  This document
   outlines the design space and problem areas for potential IETF work.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-zhang-panet-problem-statement-03'/>
   <format target='https://www.ietf.org/archive/id/draft-zhang-panet-problem-statement-03.txt' type='TXT'/>
</reference>


<reference anchor='I-D.boucadair-irtf-sdn-and-semantic-routing'>
   <front>
      <title>Considerations for the use of SDN in Semantic Routing Networks</title>
      <author fullname='Mohamed Boucadair'>
	 <organization>Orange</organization>
      </author>
      <author fullname='Dirk Trossen'>
	 <organization>Huawei</organization>
      </author>
      <author fullname='Adrian Farrel'>
	 <organization>Old Dog Consulting</organization>
      </author>
      <date day='31' month='May' year='2022'/>
      <abstract>
	 <t>   The forwarding of packets in today&#39;s networks has long evolved beyond
   ensuring mere reachability of the receiving endpoint.  Instead, other
   &#39;purposes&#39; of communication, e.g., ensuring quality of service of
   delivery, ensuring protection against path failures through utilizing
   more than one, and others, are realized by many extensions to the
   original reachability purpose of IP routing.

   Semantic Routing defines an approach to realizing such extended
   purposes beyond reachability by instead making routing and forwarding
   decisions based, not only on the destination IP address, but on other
   information carried in an IP packet.  The intent is to facilitate
   enhanced routing decisions based on this information in order to
   provide differentiated forwarding paths for specific packet flows.

   Software Defined Networking (SDN) places control of network elements
   (including all or some of their forwarding decisions) within external
   software components called controllers and orchestrators.  This
   approach differs from conventional approaches that solely rely upon
   distributed routing protocols for the delivery of advanced
   connectivity services.  By doing so, SDN aims to enable network
   elements to be simplified while still performing forwarding function.

   This document examines the applicability of SDN techniques to
   Semantic Routing and provides considerations for the development of
   Semantic Routing solutions in the context of SDN.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-boucadair-irtf-sdn-and-semantic-routing-01'/>
   <format target='https://www.ietf.org/archive/id/draft-boucadair-irtf-sdn-and-semantic-routing-01.txt' type='TXT'/>
</reference>


<reference anchor='I-D.petrescu-v6ops-ipv6-power-ipv4'>
   <front>
      <title>Power Consumption of IPv6 vs IPv4 in Smartphone</title>
      <author fullname='Alexandre Petrescu'>
	 </author>
      <author fullname='Siwar Ben Hadj Said'>
	 </author>
      <author fullname='Olivier Philippot'>
	 </author>
      <author fullname='Thomas Vincent'>
	 </author>
      <date day='13' month='March' year='2017'/>
      <abstract>
	 <t>   This draft documents preliminary results of measuring the power
   consumption of using IPv6 vs using IPv4 on typical applications on a
   smartphone.  The smartphone is connected on a 4G cellular network
   with either an IPv6 connection, or with an IPv4 connection, but not
   both simultaneously.

   The preliminary results expose a roughly 5% increase in power
   consumption on IPv6.  More experiments are planned as future work
   that may confirm or infirm these figures.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-petrescu-v6ops-ipv6-power-ipv4-00'/>
   <format target='https://www.ietf.org/archive/id/draft-petrescu-v6ops-ipv6-power-ipv4-00.txt' type='TXT'/>
</reference>


<reference anchor='I-D.lhan-problems-requirements-satellite-net'>
   <front>
      <title>Problems and Requirements of Satellite Constellation for Internet</title>
      <author fullname='Lin Han'>
	 <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <author fullname='Richard Li'>
	 <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <author fullname='Alvaro Retana'>
	 <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <author fullname='Meiling Chen'>
	 <organization>China Mobile</organization>
      </author>
      <author fullname='Li Su'>
	 <organization>China Mobile</organization>
      </author>
      <author fullname='Tianji Jiang'>
	 <organization>China Mobile</organization>
      </author>
      <author fullname='Ning Wang'>
	 <organization>University of Surrey</organization>
      </author>
      <date day='6' month='July' year='2022'/>
      <abstract>
	 <t>   This document presents the detailed analysis about the problems and
   requirements of satellite constellation used for Internet.  It starts
   from the satellite orbit basics, coverage calculation, then it
   estimates the time constraints for the communications between
   satellite and ground-station, also between satellites.  How to use
   satellite constellation for Internet is discussed in detail including
   the satellite relay and satellite networking.  The problems and
   requirements of using traditional network technology for satellite
   network integrating with Internet are finally outlined.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-lhan-problems-requirements-satellite-net-03'/>
   <format target='https://www.ietf.org/archive/id/draft-lhan-problems-requirements-satellite-net-03.txt' type='TXT'/>
</reference>


<reference anchor="VC2014" target="https://www.sciencedirect.com/science/article/pii/S0140366414000620">
  <front>
    <title>Comparison of the energy, carbon and time costs of videoconferencing and in-person meetings</title>
    <author initials="D." surname="Ong" fullname="Dennis Ong">
      <organization></organization>
    </author>
    <author initials="T." surname="Moors" fullname="Tim Moors">
      <organization></organization>
    </author>
    <author initials="V." surname="Sivaraman" fullname="Vijay Sivaraman">
      <organization></organization>
    </author>
    <date year="2014"/>
  </front>
  <seriesInfo name="DOI" value="10.1016/j.comcom.2014.02.009"/>
</reference>
<reference anchor="NASPICLOCK" target="https://www.naspi.org/sites/default/files/reference_documents/tstf_electric_power_system_report_pnnl_26331_march_2017_0.pdf">
  <front>
    <title>Time Synchronization in the Electric Power System</title>
    <author initials="N. T. S. T." surname="Force" fullname="NASPI Time Synchronization Task Force">
      <organization></organization>
    </author>
    <date year="2017" month="March"/>
  </front>
</reference>


    </references>



  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA7W9bXPbSJce/L1/BYpTScgKQUqyLcn+ksiSxqOsZSuWZib7
JFsukARJjEiAC4CSNVP+7znXeelukPTMVqqe1OYemQQb/XL6vJ/rpGnqptWs
KBfvkm07T8+da4t2lb9Lbq4ffk6ycpZcl3m9eEnS5KJMPj/l9VORP7tsMqnz
p3dJzl+mlX0+q6Zltqafz+ps3qb59DGv27TIaWgaK919vGnrPFu/S4pylm9y
+p+yddOszRdV/YJP55UrNvW7pK23TXtydPT26MTRj2ior9mqKuk9L3njNsU7
lyRJW03l3/I3jdgu3yVv8M+mqulN88Z/37ysO/+eVus1vVw/cNm2XVY1Rk3x
Lf6fLOuhyutV3jTJNa/MvqwrbFk+K9qqts+qmvb05227rfPnvEge8umyrFbV
osib5Nf7C3sMW5C375KTk5Oj5JLmUGer5Prbpqa3PGcv9ti0aGlH7rOyzZLL
VVZn/otqRq++vEjevjl6cxQ+3dJI9IvoTfk6K1a0l23+36fNaJ5tR7N8f4W3
1ZL+O0veV9tpNsuK7no+11m5yLuT+pKXpeximM+rN0dH+5P5mX49zXfms5YX
jib2wv9e8UtGdCbOgQbqddYWTzmO48vPl2en5/bX22P/1yv96/zkRP86Pj4O
f772f56e2M+Pz09P/Z/nNsDJ0bl9enLiRzg5ee0/feVHOHl99sb+fPPaRnj1
+pX/882bI/vz9MRm++rt63P/59mZ/vn6xC/s9cmZPfv69Mg/cH7qP337+nX4
863++eaNH/fN6ZnN4c35yan/89QGe/P2yKZ+enJ06v88O/F/nvs/wypOT9/6
P89OX/k//T6cnp/bK07f+n04fXvuD+3olY1wdnxkrzh75Sd5RksOf/oTfuM3
6uz06JX/87V/4My/7ezMr+Ls3O/O+dEre8X5qzcn/k+/6+ev/cGev/ELok33
tHV2Yrt+fn7sHzgPn759a3++PTo6938eH4U/bb5vj4/f+j/9ub09PjsNf9Kn
9PdPxL7WeZLXdVUTT0we62w9q57L5HmZl0lZtcm2IQaepEdHyTKv+Z7cpFej
7I9tWVS1Md3sOavpz6ah52hcfWi6yoomTzfVc16n66zMFjkYYZrV06UNNMEN
LMt0WtV5WlfZbJ1tUiEfHiJr2ny1yspCnshWeln5y2VG851kdVukZVXTT+vH
zozScmbP/rmke58uiB8SQ2nt03nVNHT/Zex1VYLHptWmLary4COb7WRVNMud
RxZFRvyk0EU0qzzfvOw8wlKKv55WtEAap9lOOl/OyqaZpU29sU//oJnS1je2
ok1dTCFL9WvaNeLm6WT9vNAd3ja0wf7rPxo6yqxMNxmtNy3Klp7IGn20qbb1
dP/Zul1gtGItj9n31WO2rtoqnU6z9SZdF7OqLtLFerOiuX1r87KhhaZ1/u+N
/aDOlhgu3o6SWHeTzqr0mU4lz2d/8+imriarfJ2SLG6ZYH78rP8mJ7md6fzz
bOo3sdn+uX0sUjr1BjPcFnUusli/fypoD+X0C9wBvPzbyw+/bUi3CPvyDJIi
8bzyuged+br4M8PJp810Se/yz8oJ6IP5fE6HibvAH0cUKXQqh/bDjfDiLC1q
Ip1mVrIG1JDUK9tiSnPathGpbHLSA5rpNn06rTZNWmyeTpUO6M/X9tRqCWqR
V3Y3K6ULQJewaHF0LfON30iWHfNPSR8Spa53Wa03WV00VZlU86Rd5qrBDZNp
Vk/oU2h8tEE5Ce2mbfDQUzHLq2lVzom1lKBufoZu0iavMc6a1BfcgR6/KGhO
+H9et1Dl4gr3pUk+l4sfPPBQrEkDqermB9//VvyRvST3xVPGt4G/ndHKSX+i
tfI/6fxJxYLeYLO4+nzzLjk+Gh0fHZ+O/4BeQf83wg9GRycj0ipli7J6AUVs
2bab5t14/Pz8PGpAAFPS6+p82uKHY/1kDIY2XeXjTVGM72kkEi4ki16T1kPi
FLv/6eL+7uby4+fLf+mcwAP29v6lnC5rYmVChmDqOIrrFb2FOEhyh4Onp4iv
rv92V3VX+F2Hh37Imsfk56pWtUv26hbcHTt29sOVl1mzKUak840boqlmPMtJ
YVy143lB6u+YdGemhvwrKfxbJsBx27Tzr7ku4SvT7teGl/C1zjekgH/dlOXq
68npq1fHX9eYwVfM4OvRaDObO5emaZJNSBvOpq1zD0sik3W+rhKidlBgQ1SX
mN0Asnyu6seESBDqIamrkxdSUPHwpmron89FuyxKh11lQ6bOV7RyIu1KCR5E
PKZfsLR5l3jhOEyCEKRLUZHiWq1oaFfns+2Ut5ReTp832/XG/ml3CBejIUsl
K8psUtBlpNc0SdHGr7cpjXSRtoEJ/f1cF6Sdl3hsma829CwtJtmW82xNo2U1
L4tH4NVPtm3imDnlDUYnMipo0kpNy2qTY6QaAp607DpP7Fk8olxOZ+Zo14un
ooVxInvnJzqkJRG1YCGwz4r5C3jAIts0ygieaMRikYEJuKZabbErDZ7PNjiP
uqAXjOSASS7NVrlzPyU32Fjd0d2doK0l+ij+xFywznaZtcmSBpzQWYUzprXh
yD0JuJ2Jj2++0DYnd3xVt2QzreiI6DCmIKMmPAJli+f7TAyU/utu7q/1M1pf
eIy1rxnt0mxLJhrpBuuigVgVW7dxPM1naGBEyPRTsk9nST8fLUbDZJVNH0Ep
6wor3K6HyQSKVNJM6ZQGTAv8O/r/xNqKaosJbeguNXSOz0mWLEinKmU7pnQT
5NgicuaX088dKXQ0q3nB9EDfqzlNBztKkns+ycSemQqPmFW009AjM6I+omoM
q7vssoTtrxUxiW9VWa1fmOoKJtctToG+5h1vssccK5zkNEhNEyThJ3fAdUxf
LJH0M9Drlgz+GtNRi18WQQNj5Ty91eolaYpFyf8oW4eX5d9Iw1nluPGTHKS4
JklFjJCE//Mo5hzbZssDMLNq7O618WQmneGTHDSCo8dZ86kmIBXao6Ej+qg2
nvAwUkl2fdOOEn4j/R8ziwzLkO/hU6hAr7hbU9w+4UWeZdKDjifXHdHeGUYG
KdFipxntOPaellU9N7zHujLddd5R9o8w66Ofk7JMAgUSfVWUPIfnZUFEYFsc
9uMlecYd13tJBnlyzQ/JIWynU+KO8+3K8Ro6u/hc0L1ZZk+ygJo3kI9yu4G8
aYSBFKS502BMwyOwAHUs3WdP7H66KHeZQvwOHq8p6ORpMniV0v2UFRrl7HR8
RV6PK1o70dUKWht7DoTq6FPHtw57jKvNhLMt/VYYHY5oIvS00RHPXl/X8GRt
IkJZLtxC+Rq7KDYbGWAtCwgVi3QbAjt9/H3J0/DXr+UrhMk7u/x8hbMpe1Bw
f/M8+euvroj5/p3vIDP4GenYxarB9v6UXBUL2nHRA5yL/0XPNdO6mPC+0sbU
Wdmom0UEGt1+HDd9P6+rNU2uxI1gx9cM4+AYIYpI1cRxYkuwCzKH+AEczxZK
dXhyBHVEzy0jRdZeRrvZkIZBEhhzmsl06WDFSMM1qOYkHIcODIi51eo5e6HH
eVqeHCCY+S2X9GcBBhMzjc5jm1j5yp9UdNFr3JqGzBZ80i3EB/3BG0H3H0uD
44qPTiQJKd75gvRRERjGv4UK/RXE/oJIIxFZlNPVFr7XhIwXDEmfr4o/+W3R
nL0S07sv+INbPPuAQ4NaldzVZPhNq1Uv6d/fPtwNiULEEfb9+2DoFmRobJgX
ETEKw2+iF4XBP8kJJZ9yYi0HR//0yY8OvxUNnyjzz1a4S3DW4ZaTMMhbUZOi
t+pBEtPdFiv6GmrOxqwQmcIvLyTNH8hePfz+Xx7wfscTgJuOKF80LuZNZDQM
vMSOxyJt95G24CMZbVvS7Hig24+6EDgB98eBHKmzWYEJg/8NjR5lJUuS3FVJ
DKBHR8haUbbqDRMjzB70rFJ+2xNRjYUviw0TwD4Nvktu5uDrYGwzr00yBwJP
xpj8OqZ6VdeJ5Zf5nPW91p5yOZQEslUqkmm4OxBaZT4kPkQHjos2oRsHvjWl
+a2I0RGnI1GczYY7dwADzmrWOZjws/IFutUipTWqgWwTaORGFjKQkFYbvg3a
4xqqPE2KWFtOL5xvy6nsET0+nq/yb4UwtCEYHh2E/2dDioDpEjgoVsVpIJio
dFLErGlqMxLkyxYq83ax3Dmvliwi+jTZF1187rG2wcSo9r5jwbYqHnP6guUb
vl1h+5tWxH0xkf3aFQFJRqJ/0bCo5l8R56AF0eUN+thQVSlHx5ytGlEBllnN
8gkqWFFuKiKlhM3yl0Mie0wUPApnKGoZs0moVdV6UpSep7NG8LysaA7ExEQd
neWbVfVCW7nRWyY7QjppncnZePVFRbBfdd7sL1r32cWbT9PjWek2+oVOigVv
I1goNqk7EhELvRZTxHcHNo9n41QN5nMVU8Gm9I5Van+UkXrPIwpzfri8G9/c
mRQz3ZTnGU+xO7UZXbJVtYEG55R7bTJ6ak526Yx0NNiqxVwubHCw7JmM/74t
nrIVmzswarHBrEOKOjNKPotYUilCpzLEAb7wHP0mikZoKrjNl7SwpCX2h/fg
7wMzMGVSN1iVTz8VF9RAk4+8Rluft0PD/sJvBPoF201xY4UgsnbnuTnNdsZ6
x1rUlI4aSCqvXNV7GgGGIj1AiqGKwnfJA4nazbIqX/jaswI3zRrcpYOUyO/W
dTKRBDo/oDgm/UjrqFnr8R8MYrndJJttzdSsSouJseAkMK3Ctp4mShtDRyQU
LzqOUUsZKVIj93OQ/cO/oSDTs54qGBetbUxn6ao25GKn3rAGzr/3UtX1729M
qCOGdUCmwt7Ms6ZYganTBaJJyLZN1K2g8/MOU2ZYvFyeW0r6GPGLZEJj8L0t
HZ1DUdV+6hFDNmmREe+pFmyH6Tp77N+6IvubF3NL217QFn0jef5wdTuIdoBO
KufJehpnUeqCeCuEdughus2YQ8QeNsuXBsIgXWUvMCNoN4iWH/WfkcYbz3sk
pPrAF2X6SIS+tvnhUVouKQobUPQnYh81nc2KnU3CsfWSLIkOPSkdGmZdzXLi
lGtl2pOXcMjRvDyNO+JtfT7Zs7fH0NZYO7p7OtVPEfU8cN5tFZl7bPttWBPj
Tezc7IlQGoJRTizeiMyNDrHeZI4YUc0bKSJG55twzIFubzA1wc08R2ZhWzPR
sN44YycTeIN/ZpT8vixiNTnccbFJq1YcR3hgXtSQObW/hEWtVr9dxjLHykmH
F/btmMc8k5LHz5i4lMM5tOl8ZV/UD8QcvATDXFY45VXOXHRbm+p9/PbtEbFS
tjLyGWyoCVn1j/BHvojmJQIgrGlCH7B9yZvgZbj4KyMyLspYUuHB+bbmsWK6
dXzY++er9HxdztK2IoVvJkYinnPuolX/Rs0TiNSzYcIa6JYV3bJ6HiaFmJgr
KGfPOatoEBCygamafmwClTAGZ16HyMOrifFBruHirkgTiDy0CdzIZHBMkWWB
VefrSTUrwjARFwwmxaV6dSMmSJqAMsGztwfuhLpi9P6tijX0qnym7O/bBvE1
IjWsbFlthtESk7BEb/m752q7moF9agRHvGgkUQo2iGmIdPKCkfD5M2mEsUjT
lyQXX/7nUJ050NYfc3Y82f1EeAm2Ka6kI86cw79LNKwH6+XxFwlDJRfRRjai
O5ERvASt5/RCOgn8V8Q8NrLAcIkGsbwVZ6PuHGZ0Cu9J+tM4H2j7QOJ9ff/A
2WEk/fcf7CyQB4HDiJgzbVbuORVYZykXBMufk8pY1V3+1aXO4ENzNkXoAXkr
y0FwmmY/R7hE1NtvdLdq+6JJ6LSmj7Cb7lh+mTtfly3SmuPPU9XCoQU6mIti
0rBnny4B22CLrQQFJLxo+nbEU4juy3wqOoftpAwLGtCsGqLBstpUnRFnWZsF
/ign/nNNVlfFLoiiLKsnetC5Puk46c3dIDBcNR6gYM6KmfpZVnBBE/mDfHtz
GQgkYQORCJY4h7c+YEwF3RFHP2DnbbbZrLwXot5y9Fx4cdF6Q0bjHn5Owkvl
LIxx0uo3KyU9vWmeQ7F66rDPEDkstr2ODXcar0dUXhFCYu/Q9NhpN8sRFMLA
NbjZluwlssrwLq/2+uF0CS54M2CRi1KIX3jTvSgTnRALSb4wWKQfCbYgb/tG
g2vsLGVrDDvq8m/T1RaaD3uYSUi0xtdtFbR+aGD8TrK8W9sqWtw0L2B58wya
NqxLXm6emX2mn5fT+mUjDsTflypDm4w2aYKcE1B0sA819IETFv0wmFbeSQFH
tjKLcGMbyEXhcZUTxbgjuJhz5IdmpeZ+JB5Nf4zY/UemgPt8SmK3fYG6+PHe
NN6T16ffv7NTQV0VOxzfZCay9MoF/VnmYudYfE9Zrt/LcYfCSeSTqCjW23WS
zcyd5JgCzGhjl/2KY2q7dEzyvF5s2WMDXwzbxXLjRIcFg4qUq0OqqThM1KZd
cVg5VtL0xEkg0jiL3KtlJAEufsBYRVcwMSNnvu9XkXAULpqQgldjiavMhbzZ
ROUMAyVc1/eH9xsMg2HyG1IP+A5cEUfrDVTc0Q15gouVloQQ1NhL0SaHT7mN
WQff2JeNendIC4fZ17IzIeyX21Hlr1XCs86tM/d2wc7g/p0qC8eRyGblVnQJ
e0o1YLWC49jWTgiBFSk1DPjGLfCA9+awE42HXiIOrzbYGIq3BifIOsjIwJoZ
G/iUzqvVzG18hKXr6mnMKyHXzsweUq8/w5G7rRs6EOK/i6L0jrLLi7vr/8WP
fsYfiG/qbg3Dlr6kswJu8uhUeNpEhik7osTJ6TVKYm1IK8H92JYSyLQfSoS9
s1FwnhWxA/CPLce3zS3Lkoklj/f6sMMgWYuHFlyRyHEgN4EVo3u6yUJ0efsp
b0UZEsNB5CWkGZsENOqMeCdIPETRaIPXRaPye+da8UqT3kWjWRpbBAqYUyEK
eEvkQuzp4uF2MExcUO2IiIhO9Li9DaK0kbOEUGPiHMZEfE1j12bHlKSf9HCp
Er5qPDLftt7QyZ1mO2PnS9rMVn06ZIsPgvoKtTyFYoAIVF6D55G+PqVBwN7o
eyL9cvoiVFU9p38UHK5kOsg4VklCrxKDiSwyJDfC2k/N2k+9ta/GfqAInqe/
XmwyNVWq+sdVrAhJmqQ7YFgrs98JhdLZvUTKvTk1Utwx8WXMthyCh+iYkoKa
xlc/gybtRD6NvM20d1peMrJzvKTlvb96lyD7DiPPC3Wr+YSbIb1phnjSI5lX
zWg0kLQDBJ3YdlixmDroPQhuJnbpsLJhhAK6/nSXwvsM3Q3pEsIUaElu5xR1
t1asqVWRbg89eFGzBnpvas3vH4iibz493F9/+W3QIU3wepJuRPxtDtNXFNzN
VnjPLuWYcvNUZCa6j0/INkjFJKnUobYuxOFDd4gjA3KZkTtCi51nUARpk0ly
tyuOe0473lB4LaoqWVSYHqtN+UyiKFA+s6IMKi3xUiJk9kaIik4zAZsBLRiX
hHRKhdv0n/xN4nw60i9+IdkoTgiQnrprvToIN6+kN0DYIQdLjMRMQ9i1xdjC
OyTs9+bsDW2LzlI4GB2CWYrNkk1PMX5ExpiKY7RRlPOaFIp6y7agMyYGIYMJ
3FQPmvczI05bFxwOZetolCgPvSIRj3137kouCKbCxoOqwAfNYzYDliAqqHyf
QDCcCUEckjMaQJr9cLXfkyKbXkOOtgPnDU8lE7HElOzUbH9m1z9yJl7iEJnu
lDpi2G3ReiJVhTkVFQ8OnAoZGqzBDSOtVT12CGTQm3bU13BBrkz3KQ5ckqub
n3+WW8LzdbN8bgQnBP8aJ6uXjym6wJlAJwUBw3LhO4AsZySzRNwsunY7QsB1
1VXWVHRSkazHlnghZIqr3/OKcxQs3aUbU9mhpqHrSKS59wH7iyHG4K9X3nN5
eg7PZQiVf3m40xD0mzdH6qm5v7kz+U1/Okf/wzskmUFVyyp0HMeguXmHX+TO
CTr6D+bfxLqnST82bOWCd7zQtpE+hcBiAuxvPDk6OvI5EmviNXSTxjn2dFOD
iQW3Hp+La6tZxkpdna8rtgX49rKHUWwhZg/0YjXqx/cw7Pf96P2b+6tPYaLB
CgzuhqGzaC4RIpQ30SFhr1rgo4kI5YkVoWzTesMkr8lkwFekmYEwzRsl0u2C
Juk4SahCCZEFsDB8S/Y0MpUW42hA/6b/NmAek/wibIQdxYfCWz7bBXFmL/NQ
W0USBP+Yc/7UOrNfdQMZ7G0WTQRbGYJC7HKhA6Lz5IQwDIAZ/PgVOGBaO+In
fA016qTxD/+cRLFxGCYIcAAolmp+HAIyfcQeVaUEopkNPV6G0JzrrGPMBKLX
N15eBh0fjgjOCqpALeV2PcFWRzNylmtIpKSDDKJR4AOqOS8N9kBGbLbd4p7F
rnzZ3ChDy1wQZDd4Y60Tv8HzKj0swwAZSbxQCyFrPkAnfpZnnHqmO0RD9RtJ
omnzb+1AatCMCJpOKhFPtCGFjcP59BWrrMg4pddMSRqN3DVuoNQwykO4mTme
efhN89D/ZmwWBPyzq9+uEve/6X+fmnsb7d/6nUT0NRESmUVFVtKWxpnoqWia
Yz+NlCeR4nVWyjB7mqXH50dv3xy/OT8lU6cbgwqHna1B4J3DVllvcc4DdMip
SpYR5cJuaMiQqJ9UvMdGzzBy4O4G0HwYB5qYf/+qqh41mQQsUtNREj3FA3d/
neMODkUTU8pQ+e2VaXPPHVgO7jQnUjf5am6CNSvJzmy2eSdQ9WwOMR1lhtKO
GWcYwz0H72DRPLLLkTYButKmkwpiFn+wyIfQzxCJIRNKyJt9OfVapT7Nc0o3
BleMtH/ikC/mb+UkbxJgiww7x060njF8WgISd3vDKChlHOtQPlwTOUymrHhm
jaMdX8sd0/wPCVjI5VUbKNYlQprjsyb1mreXNpfNsksWdiQTri4Hyv+Cef6P
gW9L7VEhbPsQOVRg8VZsgnmGQ8SXdn4d54iOOHor4T4YczCwfOaBDyKHFBHH
TkjSR7c1F8bAh5vhEGjcHp1pNU/p/7DLPU2DVC2rD/O4XAxMJ/fRch3pxT1l
q60mj8JSY4/d8dFo9OqIDW8wWBFYnRoeYzUcGI4TCBcVqfzyUtdnq5aVcSm5
Zj1QKwYkMjFfQdkR7xcK2vxrugt+IWHcYSQuvnHGpOM0C6YIkXzRpkEHpPXC
IIFEfcw5kiBzcVEgR7UnMTaEYMQltooyRgO5070pZ82BNAVOzutY9DbZMe+7
w74POxvIWhcZgFMVBVUrsq1EIcAqm1R1nO3KxzwYWoWJz9dmPVF9tYu6em6X
Ei9oOnoAiNDkd+6DBTs+/qHnZbIyYbWWNieWXf0i111/6ky9e8KxFHrD+Odx
CEwnHe372scr8kayhIJ6o4ShW+9s60G0E9R8fOAMQlQwqFkgNyR4byJ22rEp
OHKff4NXJfgG9BaLJRJyKuhGReHagRAKGE5csbMbJOG4KH62nRTEQVquuJAY
nc/P2U3r4vg6sfIV22V07E9wiZY5r7fJtH7hQII8ey1/sFLNTJdtJqFG/J9L
EdhCr3d22Ih76Oz8DzHwVkWKpKUk95Bgn6pW9PH7bn3SXz/tZJOT9dR9QiP4
frtxpSR/mCUpV6myDzZLnm0POAViJrb0rGB34BIXnWQANjBscZBw7n3+UpUW
XKEHpE4n3/H3DncLrCQFUJ3xNe9y23FLddM7qzglzKHm65ldIbYOX83FUQvE
brDO/NuSVFGjJZQbQ1Xxqw/XMeQt7lEBYoSLVTVBanxWr9VxwC563CjSNPHR
SuI8dJ5iijbGnIn9lMz3vJpUw3TL18bjyirKg+wsmjme91RI9vDOLophhojv
M5Ei6To+45eMrqHkjnqSVd2IqZ72hyurOLJN95yIj+sZ5mZxmqil+SNfDuEk
oGWAYCyhJ0yGlCK9qHTuNw+71reIaO96Qw1WYwFy1BQhSp7nxrZZWGcWl9St
h1yxmjEomEMHfzSzWb++KJAGiS9zDrW2krb4c+XDyHYHV9UWFV1L4jswYZ37
4slLHwn3pQ/mtpEw4DMRcD3AfREfimUbx4JYB6DLQxJGSijMxkFmYlZ3n0Ao
xW4GfFoIjYzhQGBOqcFMdjhuS87NGSWXPP091cxbyFknWhVMBSaNhwQHgVCu
TGMkXAfbuKqymZjKFpjKbZNELbAXePnMBS/1jLFCfMg9vDB7ImODd7Xe3V+N
iUBJGjLzkWOzEJgeLE0uWkmYI1gxfkT7xtELCBIeyaewY1u4UjLX07667HzI
d68vX7Go6/jXuFyCtxbUzu7B/kKNpXY64pgzZGx31yZmDanXEGOQVHWzl5J+
Kze8LwyVgzLrgn3wzFwwv1Wl9RcSrtz6LM393VMm5vPf+7BBwC9MfH9+eKB1
TR8nkHomxQdSAMZ194lG8ubZhOvOKp/4wnbXmqQQ5iQOLTr5CtESnu0yXiZN
dyzrQAY537db48UaB+XAXabRuXX2R1WzT2AekVE4IthLqGK0BPTnrGnNsc+c
nccaRuTCzrVIbWTljea70nBRzkzcSzHZ4kin0lkgkGMMmnhyKRfej/NzJf5/
J0HPodATfw97YFWsQ/1cBg+/+QS4bJlvBFHSqKzGghUAhAEdfPz9O3NoFBJj
r6VoQvyFqqPTyw6oD10Tqh9BM+2YGxyecN7osJDDpS43kJfICyHvSPGBrcpi
QamjEjNLCr5Z02bScSyz2TmovjF6hdQxeNIutEhGsB3USd3Jd9/KzkeSJgqo
O6lVQqWaMsiqzha5EN4vRBkcMIBK7dx1h2DivFU4JmwUGLmXQ1WE7deoS4fP
QBKlOINJOCDGYnnG5fJEDVm5UFO5Aclbir5PCo3qkLk2/KURP6spyuprMwFL
nHxJN2/VCJ+x8Rzra0j0gnNi2u7OY5RcWPl9LbJiuvSHoCtNu9eRU7fNYetY
Q8h18rY104xUJC2NZ/VPWAbK0yVdMUok947VyHYZJUlPZNV/5rPpcf1MsNTZ
4izBCubiuNbq064fPw51uHCv4GtjtkHfYz3saXvepHB70ITGdGRgzOOTo5Oj
8dEJ//crzwZTSX9HDuUmg1f2kvMbWGdN76pW8rkAdfD9u9AVShmmpETAfMys
4nXnI45iZLJNUkno4xgKa2CeLGS0W6YKp1F0DJDdkgOYz3MxXbRKsmGHKAhq
p1QQAVfv3uMDKVEg2BfMIVS3v0tQGDhgbsqqIHQr1qT31sM1LCXHHnbWqYs7
XKkFxSkjlaFh4SOZT1HCA5tXUsKBSHuN0DEH9IZhpyTPr0ROGucSALRIivMl
Ff6Yo8mcnyDaWEhhteSPQJa8QDCNbDsrqrEErqzQMl6WLUexK1YcL9CcQzsS
zxA1sInPbt/T2URkmZej5+Kx2OSzImNQDvxrfAsxTLMOmSIs3LgsP64N8OXB
7ArLlAiQbKe32yRzd/I+nP1cQgwY3st/tac3DKxQbMTf4XFgYKJ4pW32pHID
Ibm9+Ncwin0dIArNild5ImWj6o2Q3FoeVfSsRmtccIKRzhVlBrL64++IJwoG
s8DRNVFFnwV1s9YPQGyE7rYTQwmWDvvQNAGcOc9Yq68tyP6cixov+UXJr42o
od1Ek12di0nWFdgV9lGJd58l797+4MSlBIMt3lUxz1OWF0yQQ3w/Bk8VuuLS
KWIYCBr8I2nFD8f3IpGcQ1WNwjTlypuecvFl/NuX/QmL0+7k6Pg4upjVxudU
9r7k2SrlMp/LTuUwEc7v1+9TWusz8eyml/S/PFzSJwPObBCPQ4XMG5YkzifZ
ZFaxxrGkdeRo0YIOjYoj9lUjhYm0kZYLtX3GAS7BkvhJDT1OS5qFYNkFwzlP
WGi6Q7pWLDaMQteXRTOtkt/zSf7NfL/Fj+6s6EzD5P+ruPpW8BzgfONvd14G
ykxu6f5dT5eV2vKLqpqFtKGGqRAB1MiB4EvVf8yw2SbSUqkQk9lxwkvJi8u4
+L+ZbpvGg3vsuBmikB4nTQU0Kk5LNxbT1nRvVonCgTiu4DHXugZ+ph0gKyuZ
lgpsjYxMzPus5l9Re/fMridm6LK9RNd44qNDslmytoq11App0geOsRO39J5w
y5vwbBOR/TT4gGTRbGdEqReIl2lGB0xny7ruCulxZ2INl9wmTfYsalELtwXI
EEYGq6aYnXKyQCED48+XVV2VWXJJu8v5/Lixb4eiukb6brdsQY+Mc7ylRKGu
lsUE4SNxVsqnuaHYeEgFiEYI1twyrlF8gXDFamVZqZu8Ur8jS07+2VLCcrMI
yiC6mvu8siWrSDaGTDwJbWV86cTv6kkPE2w1f1n95xVHYcQVDaHJ8YQnkUvZ
Abbsmci+iE9jb/ra8rKRUaFhGOFrzkst6DNTVssOWGqGKhXdhQlpF7nXsH6I
2aanpQXHq/wbl/D7hKJkFRf7ylPil/LX0CcJQsHGWciK58nl55MkN2SkqMq5
mrsDoaqhpi+Hi8rpV+IoOuzfllvOtWSs+LbKN51e7h94xZdcffCjAoR+PO1B
IrE/8CQZM3ZQ7nlo6Yz++kvA9pB5B4WdmW8UOswOnpEcAmsA+/Sa8RXxHFrm
6WI8GCF/1ip+sOmNwI81YhFIYBzXDGpNxhHHioWTL+5nDMBxQKhQWt2b3dQK
2GDDSTIl/XX2n3it5T444Ag4ZXufPUiZD2eYaLFmAL+ygxNTbQrIxVxD7sgM
zjnzD1TV4acSJEdQUn2LsqJoQY152ey9lhL5xHl0hqTE6VY0adr5p6o+uAvv
/Abtph9yGv4CbnDFaS1WIZRn0YP5Vrm90gE/v92M4DYWeI5hkhX+66Wp91MB
FoJ0ZSWsmdbQWINwBW2zf4gWRv9ccFmk0Aaz0zCoU39pRkqxJOmYHhLp5WTC
BluUC2nt7qvzAueWWXJOV66GO5mV8a0OzlxQbqz8YHIc6gCGgqZGq49Oct6b
LeeWJSvIW8Ak5E4q7mB4Ss4wabGZB0D0bgAFuKR/I3PW55T5xeDeqvx/ZSwC
s9vJPshKF+bYdRxkLXH3OX07msEYGM/JIl3k5Vea1ddH+PLok+2CiPMxX9bR
p/y/z0X9uC0XX6NHxuwquCkVEO/l3QH9TBwEuvl72hZDsHRi8EG1KrlUwplr
ZleZ+hFchCUKgHssYVngXraswe55lHF/fDWTWcSSlBZiLBY8k9Q1lo9BZxHP
UdYctoAkE01C8zi/cFt2JsyX+yCFRhE7YaXx9QS/jUaNUcs+RzCymOe9gbN8
8hVUP/2UfCQ7UcA8scaPNPSLfyDpf/z4aZD89RP957tzf/toVkfVMx7DzZcX
IWIPuKJKy4v4SuL8aN4kMUhCYfSNln+FY40e4TPh8dS4FhXUSirE+lDQRS4Z
yvVxfO0iV57HauHfTQApWHu0TSWtZVYzaKQ55+hnfclvFUQP1TYGiUS2gLRL
Z0EyoZpKDMRHhTAHRESy9YQ9MxYr1lH338ezgvq2Nmf8c644ZLwehwS/Iv+z
4ooOdt2bh9NGY3dKDomk0RfdkJnuiL28oVnCaUVkc5+zy12Mt98/6Alh3pwL
imA9V9NxxnFsVUjoFisOKdxEL96xZP4Mx2WuPiEjOC1QYDXS0oBXb+DjWggg
nugoMaLqDxQnQwjtgnn5u6+uVA+OsjHcmF0PlMAL0GXLkcT7EEXXoxdLvEQ8
9UbhQzXezHOG6uYYOUDPolnrtoqK7mMBBqNomo4WHiwZPJFZXy2+oyERR7YA
XcgS+94080Uoik0gMTEZqNGyAJRTggpouvqGCXH4lbqSWHm2QKdc1RCy1KQ/
UmscUVJRzWiMzjPtttRxuLqNnaHqzgVV83T7zWBoW+qrBNfm6uQixyrkustl
RokzvweAYMWTYknuxGPleBMgOR0iowh3kIjE6KkTGTFmHEo/P54cRn25ub6+
Ts6PTkbHb0avJdTQXxnrGjiSkZxqFiUQvV9tc7LtiB2AxSlz7r//eE278Xvx
c5H0w5jHgoBydX2Z/PrxGlR4o770Tw8+GSeLSzaGpCfIzcWl8wBcuMH5t6Jp
+/ls8E5qaE8/fv797uITfSchyR4DrbAJGJgvP9H/3ZZxxwoxjX6B9xq3H/SS
/imtmtgeHFx0RArCdnJ09AanCEuDV+Lv2mnA3OSKREF5QQn2325osrehbvIi
EtuMCb5nMw6ZCCTD29dvv38fxveGNWBGlfHoEOBTg+5N09+jrQT93q2rmQeg
bRTzheTzhNNGGgm2Jf1PVwP92RmKXzoAJ68S3xuE9xCIvY5UA01f561mduN9
wmxk284Ab0CrxG2tto47vdh8eN0dtDPq+d14jdUwrrptx888KSmWwnBIqRB4
yP0B0/dsUO8Ma5vU+2R7cuX3pKN4+HcYnaWiQvwDhRF9faywQaC1aH/xOVNx
ShuvteEf735Xqr5n9wCIT9y3OxRub57laedlRM08BtPyMoskxGucGZtAyMGR
GwLHrFzDcMeNO3ysvmSYzD85r/Ectk+1BLhozZ/bGDrm2QkOTv9xHv0DLTo0
REeX+uHm/vKX7upf7a0e/3zAc2vWRubdI0ZJ72lL57fc34EzvwOZof7i957c
opAQw1+l96uqhaZxSRKPlKLkl2qzAVVr6TBmYXnFTvWFZqcmd6cWN68PCf19
/DQXEpt8EiV7I/g+WrEatw5oaJIitet8ohkXKo6RmKBCCiLpwJvZxI8tFr8Z
VkuDRY480/2nw/E0T/v6RdOvUq/44u5BxxCW6w9IE4uhPghsIkfs5omyZb53
kAhFlIMc1LhjPlZ/ObndVbo6mVdVXCbFGluoh/PRggDEy3WA9JnEJnZ/mnR+
mnjwBGG3OwOL5FtnrE9yKYw4BGMGGnCp2QfdCu5UnrKkY9ZJEtFpVdyOOofD
+PL540c+DZWqX6rtQ1F+QLDmw+CAaJWQjyIIfe4KymADlYGN4AU4Ite5Q42e
/dF5cvIqUUBMhpqG/tyGB6MUPoF35zBGjEYBMu999Lxo3xDrvUu29SQr3wmv
QMMlMI6oFlY+Pz17hc/FSb1tK9ljQa5FPyYNqfkEyPCMDnB+esZMKLkPRZ6W
KW5mMkfap3CeOM0RFbK3LfWISkytXjYcWBVt7d1Hk7RcVmk8xFDeJb0XvBke
ulwyrUKqruFJK7xcJ1KEe+LVC7xcjNdutAgERSYOk5CGb9WJ4Rur8JkNXdK7
6Hx/7xuvcHrRr8Ho/+d9cLsWOW+Df/6e42o0tV9wjhfhjLCK93Z2iiamghRt
qOR03Y8m6iNB/68TpBldzJ6wwbPkFrydL2cnwSXpX9zeDMIJC+mhBRaTFXZK
r6smxNWI6Ks2zyyN2LsxMTrBIcmfHEHCX/W0bO7/TFuyLcdHJ3gzzT9yWYlN
NC8WW7HAtaTdkIGbuHC5L7JikMS8O2AAul/L+IuaTAK2HtksCvVM+WwRqlG9
Ix67QRMzA5P1xb08R+c9hUnvKthd6ecangeATXCXGPrjYvoyBQTYhzrbLHG7
rj5fXXwQFoyUKAhUy7jyUG9ORJOHVGPlhSx/cHC7V/ZdR6NGpzGiuDhdvbNF
7NWwX8YhI8t2A8h93clwpv3sgUQeasCdEemvALrbLtdePz1iFiZlLfGbd99j
NrJPhNFLBDXkzxdrEGAQjjgEpPIh5wHH5TIGofMHY6Obe8Mq2pDPps6wOvd9
HwDdMQ35I0xhyHnxaSu5dUzBe2M4jCbKcYiRC1e5AErOcr/3x0f+QkH9oI//
ofUa7Zv21mg06bX1ikNwvob9I8MBV1xDP5hpdCkiqI5xw00GzPCvAm5xyFui
NS81iV6a//QuSp83HtsVttHSH0uZwH3TG+r6/iNdtWihrppwVvBMTFO+Buxp
5GXkAtyhdLdTo6W7PF3RRnmgPb7VYIu+B4w3yeMJNEmc78r+NO6YhXq1gtUa
X84krVvEymWsjyi7zqdKHMDzwI5gEQpNF3lKcAvgZWk7dU5FazA+XE+DwDE7
kRw3ZxOcPSlS1d+Scfq+i18rfvIIcibAoPNdHh+4xwzfgvUwghTPzbuRYx1b
lL3d67VfnxXgNxgSl2WzY9wXruozVMd6R7CBB958uBsEU67j5xUVI2Rq3dzf
3Cs6//HrE8Vn+3x/97MCYbw6Ya3LyxJBzauQ/1QbomK1c1goeT8kObqFfuFq
OQmDC9S792kHBCvjY9IdIBQIqEX59u1ry/O83LU1+BxDmKB/J76YPaZtTnP/
UlbERRXj5DNDgjGVjGMrmlYsxu+qo8uuOgp1p4hEfGXSFGVShJV2MCjRXoiz
ITRn1LPW7sBCqBvzPNiAlQcO10sYDc25Q4IMGoMGSM18vDG8RBkqCPWsbZEd
yrOJtM2RNFUCrtTQ71UwXwy2bsn23FRp0BzvxATZz+5fQt83jt2vXGGCCu1Y
NGi+uc2zH6DffJmEOVR+v/lw2Gj9iJHS32XAGxxLcEZ/2BZcEEM3afVcLNhS
VRyYyAvYMegYYkMtA81wbLaTP2jLh0I/tNWahVZKh7uQEcftGuT9zBFAQ24/
L7voTFKSheNd4V0Yc1BqmFjnKNxXl81m8Jepc6OtaJsZZAk9cgSoT5PmMCQb
GjjHANoWu6KxyyKOj8/O2W/mlXO+W4AJ0onHl/EiShMN6LOX1cXdILnKJToM
5nCZr1ZoHxZ0Wg+b+OWaX47feLP34u7OD9unf/zQ9I3n8uX6/gHFttflU1FX
XBsEpom8jR9bvMdHyckxtPRhN61IUsjipnOszf3T2ntOFy863unbYAdqIUMD
JO3I2GNFXsOv3rJBlxZff6Hvc3lY11ADrcD4MZgZpB5e3ol3/uHjfedzgHWy
rCJ1Gf0sUL7O7Xkk5yhrGxc9vtyuGVoD3ccU5YOrJOTJod9oGyL/pqkl1pgz
fvce2Ja1sOnDKKR1DoYBt5X1l05TkxDc9HGYgQvebRbnfO8gti0hQf1mjIYX
lcKESu06X2r9etRlB0ZpOFIXLCjJerbfSvJjSm9I4fofW5RJWsBrcJ4u/7Zj
THVQElzvM/MQD6gqd+Sfafnz/eXnLwjLyNU9PX5l2VKKQGbQlD75AteL2Nze
LtjZiRuMU9KG+8p6o/NzMcwM3QUQ2J5qxwmcEcAVm7y4DayuIUgw1RJaSAUu
ONA0QkYIYV3ZXMxIGuhuYET9IdaFA5iNc6yci2qDD+mWpBmatZ34v/q3J7eD
naTPoYuSHDi3RvuLRa10EmmX49MLWYejv4OtHSPnMue3Wkk4e5qWS5F2YOYT
7AXytJoohHZ/fSnU0Ke/fsjyLrbwZLXGeTC7C25tGgc0YlraoSHiMwPXydqP
kNA4LNYNLkgk2ROqvxVFmfzofIadJoNMApL0yBCLHilVYCzAA+4PoA/TDeAm
0mYmHsNPyMq4/EJGpKfUO3L0CmZkZ+Wc2WB2HubL4BsLuBReIrXcQfgW4fh4
xderVbEBL6MzIaLv40QUlvwxf/G4lRJW5+izAv023HQzRAbUtHAdmyI2HL7c
X3RGlhpTGBvRfOlLKzmOmzX4DlHV3F1firce44lNtZYESBZoAold5zNtitWL
gNoUs5090Swxu1s4cJYFhUJIb+AVHolDfx/sh0KzgGl+DEhw0N8kCsC99VyW
k0MTdFFn3fWaLEJLSo4LGbpVaKjv5ZwFb8d2dhrxV9a8ogDJSJp4dp7TFEaS
zWghWHa6BnJAxQlzQ/SFFF0yXbT5G2Lwxb9vuR6d+5Sq5TZQxd6KoFCIyPkY
fv0dkC1xCvxHm1OD7UsnWcbGACdyDLYeragfFEANVfNN9vs97ey3HocpbUyE
7znzCLgL7hblgDutQXS92szuNYMMPuecyqBiQLeQZOvMCpR9+QyMFG5lO6m+
8TEWpSAuQ5Rua2kdOF0V2uUzYfAoFIvQXtORPOb5JluJOOXTbDh1hDOVRPP2
PfNKS6FKccEZWV1a1jTcpVJsprZylu7iM652IboagfxRHUNUvPPzMzoMpT0+
i06oEFBay4qzPyQ9mBekkETSQoM9AGZPBbB3f3hy1XCzEBkcuX+xlSfyvyrK
5Sbw3Y5Td0TBNLZt8sSMj00Ficf5VRdfv1xf/p+fTvCIcNRzpCl4bFPS6WA6
qwQ0lBVBNtKOUbZvRNTTvJ5wyhMdKI4q3ZmrCFVOkS2l5MhzX1bHfIYi/ygr
LasGO+YO7VhCDy8NGy8S18ucBBdOQjt63otQ4saoDEV+LSgxjdB/H4CPvrpR
ATHFMa+LDDVw8kSnGrLb/lWe3S2OlCw9yUMWR1APaI734rv2YwHF+v52wGaL
pXRHUlI1pRh/la9nxpHOUKTXrc9jx6U2SWYb8vaOTAWOxdxcfwnLit7kcxel
8a4v0bFKRNXh0EV9hqwe8eRyDnWd5wE7UjTN8IZO8pIWeWcaurQOZJ0OuYjf
baV3sJNya7TQk0YdUd72S1ymH6AXgxc9a30aJhAFGKmdN83F5NQ3d3tRWuPV
FGaacRUDhoLHczDyjkZxyjEyV8sOPqF0jpZ01+MU20dbaYBTtrKV3Js37qks
qd4xsA4C2AGgcp194/4IUscT6smaSEFg75Dvp4JvSdln51uiANtEgfMWXnYf
3DFcJW6/xCuzzn7c1gWVB4fAD6p1/qxln6wNS3GT6UoRSDV4qncHRcDf/cu7
X0lVXxbI5P9Ir3wugKpZlIqksQefMURNciCtKWd75TmaKKGLOOnhgks8yUPD
bfHXGhiYM7WTFY0mQkEW433NV9ZOijMatxvSzGYCDqOKEDvtrFBdwfM6OcNI
2NDdHWtrgAewg73jAoa21Q3auZFyxzBjZZMZlPXEOlIYqLomje8k3EtP6QDW
wKTkT9naFHhCIHEfJT1GSOdR02iVA5roJp1SGnW0KQ+K0qmHscbr7B5xiePO
dgt0qiSy1xkD5UZXIbQfCtg/TlqsmfDh7UZRWhT1UoeAELR3R8KfrbGXPcdx
8Ef3Qyo1KqTY5FRYjZR7i7IpxL7fSLW9MbjPofL7OI2UVZR4Hp3b3mGBniBY
lHjYHoN46uJ/+uY/UW/5PqNIgUd6nsnlWR55M0Ih0pQkyYH0R2N5yR0nQF+s
FB/LoLnW0oDas8iBQYp413+wmXbBUp2920Nh7KYcW5ql+lvCzdfwkYqhrKg5
f8r3TCPaxKWTqpRRR6Azgk03DZwXLJZlgHRWgB3OLPkp/ud351hfCD/1zZuw
bhVWya6wYhWWa3EmLyFtOLjBXOeVnFQTzG6fGW99h2qPiEU3uaT9FD/iMMoB
ZQNeI5sjlc5hzh39USo1a7jWDKMRc/aQxlrziWmTkOPSE99Oq6hmpPB6Qbsr
XqEaV1DzmePI5nsYHO+FMVWnWK3SbPbEkKxiTwAd05Ti0Cja4oRKVwHYjO2F
5h0dUTbgcG1I0DYcFpuqLZxNVtMN9HG2ngOis+lFDv2sJHnbb6Q4U+Silt2e
g4nv4qoGgDSs776KqLM/6c7VzFLM7sDELD0Y/VmyWvqLRaSoWLew+Wn+rN5E
rZKijpwRmAIxqNVKMUTbeCaW0h6/to0GgdjoT2X6cQaeDjAzblAisx3byZLf
yIYvb52T1EbDPOzEbBC3AuWiaKun0TYO/g6EsD1SJXWLA6CgzABLFtsNGVna
5bvZVGWgp+h8OFtsuqwkx6DSV/hz1ZanloVkjavsJnod2Ex5ljwdQEH9JjOQ
tMg0Zvr0nLXXrMh+eun5nAn5N9JV0L7ZqOKZTkybRhqBdGi8D1R435ZzYC2l
GTVxGKSBj0oxdoLCAkUBwQj/WBU2rnigO0LPP2n2SNB4vPu7nHWCxJ5bdMSi
3csO/7MFMMNoOupH1XRmYYntqVc2uBmoFKN2HfAConF0GoFodCyqnlpjviQt
NsvuySzT3PXTozNOqQ+eTcmAj0xIgdDg6x5r+4qfqHpfQISKVh6YPkf9GtHc
YQ2L3tOX4uWcozT0wUBNiH1xT7r9/e2ucRqUYEFOk77CrORwRmIaglRyoBYM
E86aWJt4TG4GpJNp5j3fyszJgJV5C+4WqX6sOo99rhM0m5jT43dWmPaP22J4
CqLyWmR1+iI9LWWaVnBzfvxGQyUB5Yo1o2jimO3epiASoU1GEOUTIK+uD/On
yAHgLzyvgrXCv356JhL67pz6sY/hVWHJHLPrHxSDJX3J0yG9YKDZ0NHb2N/r
8JZR8vsOeOteqSK3SbJ00WZHWmb8OywI4vJXzytemLGkW+7LuH+veYH3HpX7
/uFiYFlHYtHbSbOuYzqcuxBAwztRn/sXd2iZzN2Qt8gljv0QevulWbu0bm+k
PzaYaCw92EmrbS8lUUJYIgsmkquSniFvVsWdD6l36wGNSlil/p+fGQaULvzt
ze1npB6SnlPiYnGZQQs8wyk660hamMzzAIavQWL2OBAqPERaaEYqCWZSkIqt
0CYcKzezHjeZPW3eFXNxNzTnPq8q8qrExTiMccn5H9CgOD90JEL6pmWwV6GC
w+2ZvQNIQs07uQOdG/lUZK5jgEuTNeEe1rXAu+d3KN1bB8Wa+3dJ8qQoANeW
No9LgASdTLyyUZ3H7vor+cSMFz0XCzaw6DRJ+pNKUuc6n7OnJEBcRGlWln4W
tbEvY7dlbLlBz47tF8hQrrffT1KKAuBRhk9sEnqHtOL+BXeFZgZxFxrEvXHG
rSbNVG0+qSpu8Kb6tY1jzmQ2RLnqmMN/jqEJBMYHmIOcnCyGUxIZtERVMwB+
zNCPu82Ju0hJs3rP9xiPM/1/BQiGesY+JmFy6nCCvKYFqI8rLlvtuMFDWxw/
jtMaPk+rbJzz69qlMYLdxCw2IRtGiWCXhdU0SwxmwrDGSHWr8xRXdp1t0iMS
H+8klMkYDlmDiFwUL2wiEnITdRaJ92S6VOXGG2qxfkwkxN2GZIABFvNNx1Hh
dXb6+vj7d5eXSykIkLIRfTcHTOjU2f8SkzHS9zg12M+Ad2+NOi/uqlJZFA/4
GoYmPDLsv5OjY0AzamJVnbP2ENMkmjhJ0bNFCPY/2d8gJ5OjRWMv4za/zDmZ
FhmGGoYnJ5ZCynOX33hxHbemL4FwnDv4D2coDxDLWsm366KuqzrlJNtaStgO
PsDngswo+R4YB3SA8giHb5tlKrktYZBFkXFmgzwlK9h7CHwKYbhSB+NISXhR
nS1pKZ0RVMlIfV1HGGz/6b/7LuXdTGdV+oywYj77wfqI9xXEBfzUR8mnwCEP
pQD7no2fS0XrIrXU6zSwp6p150hNqYwSroQ4D4AXuZ2MWnZPKxSVVsyr/hnk
wl9/dRw3vCesln1XV5GLoC7+Ma0MKW5frge+GE7rFqoarZHxVfrFqm7fHp9x
vciNtbDY4xZisi0K9iCb00YDZPppwDxHKp/JNmRxsz7Nqg7uEKlpnZHNrAtK
iNixslGZjCtty2Dbsw1/UfoD28n60YWZb6139elea29NQfYltr3kL3x7f/Xd
amNPXxELo8sw4U1lCRcbhD0b4guvud5JKcSjf/86JlrSEObprGyaWdrUG2z7
fcCoKcUfBQnHIXMA37cxW9as24CsYrj39GZx2YpLywAPSfa8AMVyz2YYJrJ4
wx7PYsjww5tq9jiXosUbQ7N5WCIX7x9LduWxr32d/FeTigNJm9E0/m2NuI3v
fSEm5Y7rs6Pc6WlzY7UqgcBkXhccAqhoCzUWQTVh57KkqPYBjQfUadkW4bV9
Tuf9/zvPNInTWl0wf/Se+Gj+Dk9RbsAC/247ud9OYhJjpojkJHB+IiREdomm
nIfRYFLBwlicF3nn1vvkAyL6Ek28bolstlpV+ZHV8j59c/tx0BvCuPJuCSe6
wR4OM/c5xekxvKtojwa+yb4Aq4L1zcF/9OKevVmL3V6faNIVrBw0dR/6EGCU
2x+irH+zqwX7kXDiX3Kt1VGoictusOqLBEsvZoAgKxoxCHpDqw08Qxzdg3A0
Y4n2GmqplL5IluYeozU0ydCuhkvCDkAE9AQ3wbtvJy9uIS7EKGlhzr5362kU
LlHv0ApQIHoxCM72bvzEzazwzZi7mjidXFYw8B9w+r66nbuB0C8X9sKB2iNx
B1frLU8n8+lKHVrnp8cQjuZd96uVRJKW8VLmGb1gxO1wxAcZn4z3dBkusgGv
71RldYuN6GRoCtyn20OAviROIRZ8jCbCWRiZ9rTMHsmyhcQibaaeIRetUzOW
lrO4XsyXpWuaWeib2WnjOhcIU0yeaUSjmAybmMkCTckllkqqSxesRzolS8ZJ
/yMAt6v5QMNO7/NyusQ0tbxHvDtO9a5N3tKdnm7Tp9Nq06TF5ulUyk/w52te
CbzE2ELWodbRFRZlOiAY7ea9WQ6Fx/B44hvwWmMWUsKRcNU820meUSHBykVv
Cn0+EIqP5Pk6A25YtD5Jf/IYNZoFRZpgwU5hR+RQaB8SD7MrPp427vUpcpkb
u9IX4GmMGBkjx4ExszBULRQ42uPjo1fjZoU0XP1PSp+kTZYt0qJq03iqXFfo
wu5mYSGhidm23dsrM3fFZqGfIGmzkJYbxuFus5LuIJ+Rr0N2TuusO1l1HYgy
/zdvmmGG7R9rwLExiW1xCnY5+UziGHBYs6FoeW3yoS5mxJfDP3om9Xdb+cVd
QFmY6K1ehwUG3+gFt6BR1KV/0l745V8X9HLwH18fJH5Sp+5Jq9mfcgcYHJIY
qyCN1apY4P1KphJz0IyxFWNvdaSM9djpeml6/1QU3kvGiW4UP0GCyXnkd3kX
k3Mvdr8nkwpJ7STDetOinm6Bt0pH8ig/76Edgv26x9PuNfwG5khs8/dGXJUf
avFYAY8OTEOjebcUr1jrPvhNESIynsvgCnrLTTlwxN+WHCVldEJNwc3qrru9
k/HDKYeIa2QAelrkoZj3WDrac3b+XUgp0wXEBKdF0SxDuKLh37eSpBpVa7j+
6SmpmiTNOqBrzKS7qal75XXBn42sGd8Kldl/mEZU2Md0YXAezPOf66JtOTNY
A4eNlJEyKUL7euEIa5+uXvqSt6mcISjalx20rAYFuGUvL7Q3UCdBrK1c/lSt
nvK4YTY8Rd324FGcs2gehVVsI/99nRflk/htDUCYzjFfjSNYf0t9nkHLn6jz
Op6zL+epcxEfSPBysTLBkTdLg+0IQ6KG21BaFU7OAFD8JmuA2DuK25DmEdK2
+LAcH1ZHYPuIsgB9xnmR/gVGdzuAGw79dRkPjotSiI0a3rVEhG0fRglHpGNe
1JlsoKPGKf/UXhtyFSS07tPjpEMutPmMsYQCNo2BaBlqwg5ZdOBAkj6ZtHR7
gID5Xa7h4F0itKcWWbLLdNCwLZt1VAevsdNNl2tvqWGMW5ekqsdVTWAYTDYu
zguc+A7oISPD7ER4LrKomnY/j4fBUma5BHOYJK1HIu+G1VdCHQluxc5esGzm
h5dgZCBJjSowMXR7GXoPvmQ0eLRuweJJ7l9IlFfJHY1U1VGtsShx2iLOfEwc
05ZEvBVAlMeaxwQ3uW+1wjUd8tRCmE3U2IreRkpuyWbeRLPYJGAQ9cTdE/ry
yiXAXftvjsanR7/82elJC6nXFvCsDyKUfFCfsXFuszzDetBqV4ayVlDwDUib
L9V8+cB9nupkW0srSp0sYPVZavCYCM6RWsDEla1Ra1aYshQ2B7UseRl94BaV
zQVbIm0RDJOSyylQFcJRXsUGBVua7ziS+5DD0OkGE7LOHtE6euhCg0i51b47
pBap4DIamnxFPFxCJmYyZ1b0xU1oUNE4c5Z7BD8da1SHaaYLPSve7EVFmrKk
6UVYFIEKjBG43R0LyVSBkoYJlo4+Z9acDXuvSZneEyENrZzEQWpuvVlIsksY
CU4JIfDYNfArcT+4Bu5ufx1YUnBRMyK6E78AXpSvDPhEqrIFRxBxhP+mbmK/
B1Kv41vTOIDJanQTbEFThu8vL64ufFcSnvOhFrgGzR+3rOlmWvcEhR58wGJ0
3J0rEesjlPk9FY1V/ZnJGcD0YnYZ6ZbDxHGv6Eb1RfMeCVLNRoYvxPug57sR
+ghZV7S3MGFKEi0FVOJB1ABIy6x8uciqqjYMXyoLLdZ5rOGpHRjKgPQGcV6h
lXHxTpvlNZThYSBnCy9/6KjFdRShRQreDjfVq0is7RCrNAlnaRApVLGM7rbc
7IaqhXnk3zac08LI7NwLjf0LsXef/dc1562zEPOoyN47z32Q1qznAsVp8iJ5
cXKNXx39p6RvoEWk/HCBJt65BChgwyAEDHLdtCmPz83CB0P1KdkBB/VKOKa0
cac1LosoUyLujlcaZAOgSvokhJhxSbVtZ/PlK8/y8/k8l8aYK99wlEkhg5Ad
y46xBY4OSdr72j/Z2eNnbvJuiRlmETD4NB91nKsZ5XbHBxQoLVQmxZM3YEQP
Lo2KQbCxbDrdsvV6kHY8jFST89FrdRDnRjD6lOGKB9vGajKkddXhUUMLEGmb
CPHfU66ccI8k70u2jILX8Pw93D29tiLrN28RNnSaxVSFYjDorjbu9XVy93AX
jHifBuyrLjUi5iPxRRtqxpymqHFHrNjJokcFC2MhqCyaROqj6JJRQAd93foa
aA2R883fkulsgWh0OBccIMSD8yePQS9nM40wWG4184T3iA24J7pV/duHm+tB
kiMcyhWnK+lKSrM8TtZNPiXOn3ct0L/++nRxf3dz+fHz5b94kKfeJ5J1y+Ri
DYQ0+nFXagrwICgeR4Ff01HEjh7PJbvpXK7TsqCbmNHIG5TvBrlhURc00CkX
lWaacGm+WnO/3l8AqgwRsbW2YROfDiDJqmsGJEn6H0URGBzw98w7yiNyxbiF
CP19wfATKUNecQBVPZqkNNXZKp2snxfq+dvCgxuAJMwByTDF7Ds2CEB1BAmu
k/QqEWt7H7c+6s5jAOlup0Im9o4ZZ+EGZgYA89df17cXMDs8lZul6PGQokm4
wDj2p8MiSX5yf/WZ6xHZaML2nHS254+8hBLXmJN3Q+PTv3+4PcMo6BPtD6ej
+9iI+hq1zFg8J+kT8XepP2br1UcXOqTlky/4J8T/55bK6qHwDFoHW8CEwcgH
xYbpY8ctxTsjvjnsLbAb/vqJdzluOialeIVhdyGUOyeL+vbmvRWKqI0ahdO9
VAq+uqHT7iCi6RvPDrkpFg/fI2uifkyKcVVk1yOE7eOjRBC23xh2Qs7SjCFd
h86nwpvPRtJRs8PIHLQmK8gwcAghJsyF2RrPTZr3Kgi27HvYY9YOQ+cDs1+d
eZWVuQoeQTPlJCmf9Rq5Nm032SjvopzxYfm19JtqlaNiKLNlgNTG+8C0ro8z
k2xsHznxObpoIM8N60ywjLkXAXdilseL1lCAkh4XlbBBQ/aIVtIFTWzoNSdo
tzrT2hDRzFlZcWdATYbi1KOjV9+/D0YWnZiusqLJlS2FnUmzerpE8Mdy/pxk
azGErBAyniAeKcia3FYCyjbnEpKGxqEMpbapIK2UfkbmSfj9A6dRgGDrPPLG
yfjND0g1+RmhaRyZ4Wi+OuGMjN6XHZS3fe7dk/wiBWY2ZLLTt+fnLMx2HNx+
7GHSY0+gXJG5vd9CN2y8LV8aVmJ93EMZEYIie3Sinqe9z8XP2UjIhy6gLMBF
i7/SipsmkKJ1X2EIGlJhkmu4vjqfQvNAAwi6CVK4pBEewRwAQAoRAumF5kYZ
eoMo/wZMeJ2HvsKrnJJFtOeal7F3U5eHEi5zjPk69O0JZ8AYmumXyYVNUAlZ
ExxpChce3mL1wi1zo3OQu9dR2pt9e8100p396klSE8TEAqBD3PXGYPK40Ngn
8HrXcPBkRlzJ0ijZiwpOJLcm4jc0mlrjnBJkOl7PA3ox5ft1DSMJG+8wc0nT
D4N/zthghFNO2vxddZ04j5Mg4ih5n8Ob3kQAO9AV66e8QN4aEohoCrWuQ1oR
hoWGjJADGdgskTV5Fa+2Zp4kogtNNWbaJS7oyJasK9DqTuBduw8eQoKOEkt9
JqnzYDZmUnMhQEVnMSZFeVY9N50mCV3TUn9jZbNkvXFfkD2sd+3hRjbMiuuL
sDiDArm5izGL4vDSniTxdkkki3EDIRchhD893Dz8a0r/MMixt68YNtuj8DkJ
UahAkcZNgOJjzJLk119vrlRDNIbEN7ywdnaasxbqaJwUtYuVGKC/7VfDyGGG
JYuaVLKebksWx53vyKq1VDuO48w/hyHMcrgVFmIUrrjRrCRgEQFB2ZT0/w2m
/Pr06N8icyvzz6/DcOHnzHAkFLAf6gp6HarUHuLoQre0greJGZtotaybWYiN
764/Ogl36r/vrz/df/6CjxVY5TWDYXOXJQEaZIvFZWt18rKBjv1QK64jJYAr
nNOW31xfmjrjl+z23ETGbbwxKUR29/n36y/p9cMv118+XT9ExPbq9ASJyXgJ
My2ceAhH7eHe+23/tWTOWG83nK9u+y5Mp0n6v97dD/h/5V2SX3J8KpCl3p7d
AR0VJ6cHVWEHnxKxzq5Zbls0E+S248b9AAulvdFUhcyKFfuNzAPzK4NNdRPw
tcLBCNc3WhyzDsk3YeTuySpcoVH3MDBrsiXnrBcJLd2qPWCSEmt6r+8KtG6K
y5uzM+SwsTpCskZ/E/mPbZoRXaOpvb7E0jnkLu0fj7EWuQAdBnP/cPFwHZ38
65PTc49eDQ+uGSIc4bMYc2bgNmwnKVsJMUIvxfxNMCUAsV6fAbxvLLKUiV7S
EduMSvQu6cG5x8lzkxcE2ZdV6/+V9Dhm2SOWNB2R8m0ZhB7oANljghb5TUNu
PpsJ++KCk2WXjURyNyIpnyDqw2xKl4yJ6rq1wk0HC9eIM5Ng/ULhgW0GHpFG
66adaBUhLhmivBbv94JZCUHosqv/XYoqJ0QgxPcamWGJER+y7a4/XX/58K/p
5/f/4/ryIb38/Onh+n8xe+BduLn4dJHqI1+uP1483Hz+JNxuUrURcCong4KE
embJ6L0ygCtTMVW9jPlbYDZxdpmpdM40ON31HoNR7SjsvKwRN1PrABJ3M7FL
0vXglcpVqO1WuHj/pRdtvgoZEXtByY1iEuGI2XnY+whp8ZFrsUObIg8qijaH
V3cD5/0XVgrFQgXUBQR23+KHnk35JK6v+DRU/YZfhxb6s2A1Dn9kLqnV8oPG
C73YLnR6K8SBFmVkMElpohS9th7LbaWJojubXfGhXDYpGxFsSg+VqOgYAScR
cg9WibG6SEGD35RbdG5XszEWC9nrGCA86rQR87voVIJXAX6KJ62t3bP9FWTM
9xLsNtjw+UO4YEO2YIU0ry7jWtEHD0KiCEEC/vGvF58+xG2eyTzZriztzv6l
EXGLy7pJF2YtR9d6L2WYLnzEVnmaVR4be/KNEZyutgNfn5cLvuid3A8BDthu
EKZouXSdC7vr6k+ifeE86UE4eXaTspj3OP5gbj8HzB8MtNvMQxymaumxvzt0
8bi7IF0ErT/5j+9a0X38aizNtdihEMpSxCMKQoly6qxmfeg6lfmS5FBFLYl3
63/p9Tf3dwPfwhnthF1PQcIxz565LBiaXqJYHF8+1D9Uc2/qfCENgV1f8Drm
qX00CMoIO0gUXkr1t5nVkltiHnhz1IcD4TEPHGO29URhstg2/MYWWZ9TXq1w
GJ0f2BE38GN55cesHeF2iLOTzTf2qR2K2WiGl/ElhxfSXcPMBXpoyFGlqfQU
i2RqVVu+LRt6Os39vMd4EdY6MpFYFfczCS0lRLFNDxPROxwsCqq6bA7+rj8B
bJyieWp7qOrKaQfHcqcJqGFvbBSFgq4fu+t0GkwjntrxwIPC31zzreMtfJd8
6ejnF2r9mqvjhgumfDsJmSn3rBZ8SF8szGknLzmnI+uGvLaKMBIjZZbW7eJ5
kebZdIPU+m85wBPZUtJECUZaUj+hmjgoEY0KeeOaD+upYPkF8GMuMvARCx1x
pXaghohWOPW3k9fhE9toY4nN1rn6gmnq9Mo+2nFovHNgFqVmy1ssUqLJVtMU
QPn1pd4sSNgLQObBRrKHvRPA6cKQmxShHVpjUb0MfStGH5BJBvMY6flhZ3yZ
M8SiM7kbql2Cc+efMmXlp6FQ5qv9lOjRMMWM7iVwEiouhJfGBRcSWX3/4U7k
taZHSFUbnNY9Kwhc/9HUGeoH5TbwdU2zRn3B8ouQaD/jIb3/sNFkemLAUb8V
5zXkAIsPLhRbdkzRA227oq43BrAWzNlZzeA0vr4pwigx15dPAdLEp4D7m3Fs
HQ4ZMqUzC65ySsVOaSOayRaNRf+5mt4SkhCMsMl6btR6iKt9js/KvMdZkRQO
X/dsQSZLcxJsTh/50Trc1qNXehdjFI6QS2Ogvr5kV/Bq+E6b61HTqdUv3cGR
xGuiLFqNqcmSDfyzpdkKYlwA6YsTeDyb35ZIrNqx2GfZS8CxTO4unY9qK94T
Cszzb8sCuHakZrU+x04uYKOKiL++84iTeJ8jJEzKIgb3OwgZwYAxEGSw1OT+
6lMyDn7pOtW4k5WtKlmxifGUc0mTExPVcjijdE9TRNhA6eRvcuBV9bKVlg/i
1eHFsIY4RSqkaPVZIVjm2Yqhha3vx1MMkR/wWnwPlVcw08dRPxXN2W0Ue9LU
gmGEFe3ZLfft5XX63BfLSI0TpyKsBEgFAQxowpVkISsXs62sNAgVGp0qGdoB
3e976yIQtENU6k9ZXzZxN6m202yWFXVa1O08bWZlSjudWgeCVEGYhSFBaZtp
aFO9R26eZxaKCjkEfA073gTJhBYDqmJnp5TObsQMy0LeP5hZhGFp2XDvnFOG
HXhcWNi7JLkow30CH4Rxg0NaZzPDuHUbhbbwGAuRyXvYOxmy8dwvdGeeoPMx
nXSUfE70nOVBZxfciHArGXrX/QferLxT+i91QYaFlCdiiHMkbZR0M8HWHOeU
OjbQ5jCA7+HiDpwwBUUmYfiF6SPQbJElsHdffZjA0meswUoeYJiZzMGdXMAO
03bofqmNT1dH6vPh3c4cBBOth021zI/RMn5aB0M81tyRWTaUbFzUW/DNkz4v
UwtwJ6TPSevzXkO6SwObQpXEfjHKRwCdWhclMXTFWLVdF7Gjzw6GnonvHjUn
PwiEtzNXyNH37/QLeMUSKYAgkk/BQcOl9Fqr7fJzQRoSp4oVlr+mOC9YytiX
uPeK2SrvKfbfo+DqwRceXSV59dB3qeV8dQa2MLBD9k4xhFeS3JIagNOx+FLZ
nZNPGuaOrQI7SBIjbatUwMhJT2HEO0bJKVgoCxBBIs/qhMWD2Q+gJFbVjbKf
J0ugy2Z/kFThBvfgpzTGXBIvZ1X5X9pkp2Gecif6VVzjKt2NkltSskVTh5PC
slhgkLGxt5cvVD1ma7KX0+mUrlO6LkiyF+mCiL5J2fxE/AhQ8k2n/jmyVs0a
t5Zj0tnhD4MMZ71QDRQXGShJv0WdyQr5eR0DWtUI89cRXX4IvYATRpzuf8B/
BkMnzton1HE1P2xpHyyCjSAWz4tJjMKF7IkQ8EKOwlo1dsaM9zfeu7vjGKt6
0T1AQqjURwHON25JfqDMzXJBNNPGPJFb1lo6SG8cmIjbNE8Fy1uh14VL3F1e
B4h53pwdx1FMDGrT7uUv+AyAqIre0h3vOSDitflm++f2sUiJKXfbDMSlshkr
j6xxxJIluAEkM9tdXXY7wHlnBSfQxhk5e7vYzaWKeUHHqWEuK9+g+bdbYn6L
WnFmcbZXl0mKdzGfQNQ0c336DFNQuWDsM49IeAdDPgqlSLdFGWDwwyPw4AWR
Bw3dZ3wF9gOZL415E7wJJQb3pliL9SSeVOtnSe/t393cyjYOuoBvdkXFa2QY
gqtqqto2f7es4O22BCULIPSuAZFLtl+jEGd3JLkQ4bm8vRuAmLBpeYJPIwWF
+xr/PIixf5uuN8qbwV6tnXhAEV+CJZZA8FGzBwCKI97egcTQwp/Gd9LdNRDN
ZZRwRJTxzHUYWTiUJ2vmzK4P/wMz44OjCbiZHISQEiAFmhRHa4CI58nPBG4x
uBdYemsoQfW+aBiLkDdIHRWuLwDJHFeWP73zS7JIP2SbJnZZPWjhw6Fbba5J
o6xnMcfzHU1TrHRxDfi6uKaTbcVbpJCfDFTa7FTl9aPSx9i+EXeLoMjFvWQE
qCBcFDGgmUez3RH1LeEOAVxcwYr3gjZAImPIS2y2C4BLNMEkxWlxE/nyXdL7
iIvNNXOgGg/EE+VuDc3LEmnePt/7ik1MrbbdeYyEuCbp8teGwNEt3L+NC9vR
ze6eG5Vr3mWEKhCvTk1I9UXB15yhOTCbFN3U2mDLuwlrQrRcQKFvRCOKu9WF
txAPh55TbfJS+qNy8YqPqXgXlCEX4AXjmy+w9rnXIxHhPVPJC3yn76/wwSW3
dqNlOvd/kEyRXs8Q63wnVNKo7qwXRTUimsOcm70aEY3+TQh7LTD53jSMSz+X
VaMZ7uIAezceL0jz2E5GZNWP2yqvGf5bSBz4D3ecVkp0PVkTuYg71Pzdd9vV
KlWcbc1vMb+U9Kpjb8Afle50m2drVue5kZZeUlpn8kJUBcub9ubo6J3mpvtq
Afrw+B0yzXKkoqTy6yTp31ZL7obx3ozUAcmmDrRZ+7IhrlF8Y4wU3lAMGyMg
shI6abjOY+gzeEL4mw+Q1rKBh2Wkk7DjgBru+/yEEstZ3NxnYs19hspiO7gN
TPjeJI/sWrOwSS35v3KDU8757AAA

-->

</rfc>