draft-eckert-ietf-and-energy-overview-04.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-04" category="info" submissionType="independent" tocDepth="5" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="IETF Energy Overview">An Overview of Energy-related Effort within the IETF</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" role="editor">
      <organization>Orange</organization>
      <address>
        <postal>
          <city>Rennes</city>
          <code>35000</code>
          <country>France</country>
        </postal>
        <email>mohamed.boucadair@orange.com</email>
      </address>
    </author>
    <author initials="P." surname="Thubert" fullname="Pascal Thubert">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <street>45 Allee des Ormes - BP1200, Building D</street>
          <city>Sophia Antipolis</city>
          <code>06254 MOUGINS</code>
          <country>France</country>
        </postal>
        <phone>+33 497 23 26 34</phone>
        <email>pthubert@cisco.com</email>
      </address>
    </author>
    <author initials="J." surname="Tentsura" fullname="Jeff Tentsura">
      <organization>NVIDIA</organization>
      <address>
        <postal>
          <country>USA</country>
        </postal>
        <email>jefftant.ietf@gmail.com</email>
      </address>
    </author>

    <date year="2023" month="March" day="12"/>

    
    
    

    <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 that 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 for various reasons (e.g., lack of momentum, broad scope).</t>

<t>There are various aspects how a given work relates to energy that are
classified into categories.  Such a classification does not attempt to propose
a formal taxonomy, but 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 specific draft version,
as opposed to the newest. This is contrary to the common practice in IETF documents to
refer to the newest version. This appraoch is meant to allow readers to better understand
the historic timeline in which a specific technology was proposed or 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 or other alternatives are the
broadest and most unspecific category. In this memo such an energy saving simply refers
to energy savings in some unit of electricity, such as kWh and does not take other
aspects of energy optimization 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, the 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"/> 
obsoleted by <xref target="RFC2822"/>, <xref target="RFC5322"/>),
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"/> uperceeded by various later version
of HTML, see <xref target="RFC2854"/>).</t>

<t>Conventionally, 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, usability, 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 IP/MPLS 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-iconic-example-telephony"><name>An Iconic 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"/> superceeded by <xref target="RFC3261"/> 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"/> superceeded by <xref target="RFC2460"/> and <xref target="RFC8200"/>) 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 1990s 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 "Transmission Control Protocol"
(TCP, <xref target="RFC793"/> and successors, e.g. <xref target="I-D.ietf-tcpm-rfc793bis"/>). 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="global-vs-restricted-connectivity-the-internet-routing-architectures"><name>Global vs Restricted Connectivity: The 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.</t>

<t>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. Such approaches resulted not only in higher cost of those services but also (likely) 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"/>
<xref target="RFC4346"/>, <xref target="RFC5246"/>, <xref target="RFC8446"/>). 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
(e.g., realtime vs. non-realtime) which previously used 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 1980s 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 1980s, it was proven in <xref target="BOUNDED_LATENCY"/>
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 INTSERV versus standard (so-called Best-Effort)
Internet traffic, the INTSERV model was already recognized in the 1990s 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 (e.g., ore depletion required for building hardware).
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, 
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="optimize-generated-heat"><name>Optimize Generated Heat</name>

<t>The majority of energy in cloud DCs 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, DCs 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 DCs 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 DCs, can be recovered when it is coupled to heating systems
ranging in size all the way from individual familys home through larger buildings (hotels, for example) all the
way to district heating systems. A provider of such a 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 1980s 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 2000s, 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 (LLNs) 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 INT 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"/> superceeded by <xref target="ISO10589-Second-Edition"/>)
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 in Wireless Networks</name>

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

<t>(a) Unnecessary wake-up of power constrained Wi-Fi 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 Wi-Fi unicast packets.</t>

<t><xref target="I-D.desmouceaux-ipv6-mcast-wifi-power-usage"/> focuses on IPv6-related concerns of multicast traffic in large  wireless network. This document provides as set of statistics and the induced device power consumption of such flows.</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"/>): 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="some-metrics"><name>Some 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="power-awareness-in-forwarding-and-routing-protocols"><name>Power-Awareness 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 dynamically
regulate their power consumption based on the required performance, for
example by switching off or low-powering non-needed components
(links, nodes, linecards) or changing speeds on links, or reducing clock-rates
of processing elements, and/or routing traffic to utilize as few components
as will support the required performance. The authors called this "Power Aware Networks" (PANET),
 even though no awareness of actual power consumption is required in this approach.</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="acknowledgments"><name>Acknowledgments</name>

<t>Thanks for Fred Baker for his review and suggestions.</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>

<t>02: Minor text edits (med), add pointer to additional draft (med), Added co-author pascal (tte),</t>

<t>03: Aded Jeff Tentsura as co-author</t>

<t>04: Various textual fixups, added new versions of RFC for references using obsoleted RFCs, so that both original and latest are referenced.</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='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='RFC2460' target='https://www.rfc-editor.org/info/rfc2460'>
<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='1998'/>
<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='2460'/>
<seriesInfo name='DOI' value='10.17487/RFC2460'/>
</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='RFC2822' target='https://www.rfc-editor.org/info/rfc2822'>
<front>
<title>Internet Message Format</title>
<author fullname='P. Resnick' initials='P.' role='editor' surname='Resnick'><organization/></author>
<date month='April' year='2001'/>
<abstract><t>This document specifies a syntax for text messages that are sent between computer users, within the framework of &quot;electronic mail&quot; messages. [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='2822'/>
<seriesInfo name='DOI' value='10.17487/RFC2822'/>
</reference>



<reference anchor='RFC2854' target='https://www.rfc-editor.org/info/rfc2854'>
<front>
<title>The 'text/html' Media Type</title>
<author fullname='D. Connolly' initials='D.' surname='Connolly'><organization/></author>
<author fullname='L. Masinter' initials='L.' surname='Masinter'><organization/></author>
<date month='June' year='2000'/>
<abstract><t>This document summarizes the history of HTML development, and defines the &quot;text/html&quot; MIME type by pointing to the relevant W3C recommendations.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='2854'/>
<seriesInfo name='DOI' value='10.17487/RFC2854'/>
</reference>



<reference anchor='RFC3261' target='https://www.rfc-editor.org/info/rfc3261'>
<front>
<title>SIP: Session Initiation Protocol</title>
<author fullname='J. Rosenberg' initials='J.' surname='Rosenberg'><organization/></author>
<author fullname='H. Schulzrinne' initials='H.' surname='Schulzrinne'><organization/></author>
<author fullname='G. Camarillo' initials='G.' surname='Camarillo'><organization/></author>
<author fullname='A. Johnston' initials='A.' surname='Johnston'><organization/></author>
<author fullname='J. Peterson' initials='J.' surname='Peterson'><organization/></author>
<author fullname='R. Sparks' initials='R.' surname='Sparks'><organization/></author>
<author fullname='M. Handley' initials='M.' surname='Handley'><organization/></author>
<author fullname='E. Schooler' initials='E.' surname='Schooler'><organization/></author>
<date month='June' year='2002'/>
<abstract><t>This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants.  These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='3261'/>
<seriesInfo name='DOI' value='10.17487/RFC3261'/>
</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='RFC4346' target='https://www.rfc-editor.org/info/rfc4346'>
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.1</title>
<author fullname='T. Dierks' initials='T.' surname='Dierks'><organization/></author>
<author fullname='E. Rescorla' initials='E.' surname='Rescorla'><organization/></author>
<date month='April' year='2006'/>
<abstract><t>This document specifies Version 1.1 of the Transport Layer Security (TLS) protocol.  The TLS protocol provides communications security 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='4346'/>
<seriesInfo name='DOI' value='10.17487/RFC4346'/>
</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='RFC5246' target='https://www.rfc-editor.org/info/rfc5246'>
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.2</title>
<author fullname='T. Dierks' initials='T.' surname='Dierks'><organization/></author>
<author fullname='E. Rescorla' initials='E.' surname='Rescorla'><organization/></author>
<date month='August' year='2008'/>
<abstract><t>This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol.  The TLS protocol provides communications security over the Internet.  The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5246'/>
<seriesInfo name='DOI' value='10.17487/RFC5246'/>
</reference>



<reference anchor='RFC5322' target='https://www.rfc-editor.org/info/rfc5322'>
<front>
<title>Internet Message Format</title>
<author fullname='P. Resnick' initials='P.' role='editor' surname='Resnick'><organization/></author>
<date month='October' year='2008'/>
<abstract><t>This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of &quot;electronic mail&quot; messages.  This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, &quot;Standard for the Format of ARPA Internet Text Messages&quot;, updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs.  [STANDARDS-TRACK]</t></abstract>
</front>
<seriesInfo name='RFC' value='5322'/>
<seriesInfo name='DOI' value='10.17487/RFC5322'/>
</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='RFC8200' target='https://www.rfc-editor.org/info/rfc8200'>
<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='July' year='2017'/>
<abstract><t>This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.</t></abstract>
</front>
<seriesInfo name='STD' value='86'/>
<seriesInfo name='RFC' value='8200'/>
<seriesInfo name='DOI' value='10.17487/RFC8200'/>
</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='RFC8446' target='https://www.rfc-editor.org/info/rfc8446'>
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
<author fullname='E. Rescorla' initials='E.' surname='Rescorla'><organization/></author>
<date month='August' year='2018'/>
<abstract><t>This document specifies version 1.3 of the Transport Layer Security (TLS) protocol.  TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t><t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961.  This document also specifies new requirements for TLS 1.2 implementations.</t></abstract>
</front>
<seriesInfo name='RFC' value='8446'/>
<seriesInfo name='DOI' value='10.17487/RFC8446'/>
</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' target='https://datatracker.ietf.org/doc/html/draft-ajunior-energy-awareness-00'>
   <front>
      <title>Energy-awareness metrics global applicability guidelines</title>
      <author fullname='Antonio Junior' initials='A.' surname='Junior'>
         <organization>SITI, University Lusofona</organization>
      </author>
      <author fullname='Rute C. Sofia' initials='R. C.' surname='Sofia'>
         <organization>SITI, University Lusofona</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.claise-power-management-arch' target='https://datatracker.ietf.org/doc/html/draft-claise-power-management-arch-02'>
   <front>
      <title>Power Management Architecture</title>
      <author fullname='Benoît Claise' initials='B.' surname='Claise'>
         <organization>Cisco Systems</organization>
      </author>
      <author fullname='John Parello' initials='J.' surname='Parello'>
         <organization>Cisco Systems</organization>
      </author>
      <author fullname='Brad Schoening' initials='B.' surname='Schoening'>
         <organization>Cisco Systems</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.bormann-core-roadmap-05' target='https://datatracker.ietf.org/doc/html/draft-bormann-core-roadmap-05'>
   <front>
      <title>CoRE Roadmap and Implementation Guide</title>
      <author fullname='Carsten Bormann' initials='C.' surname='Bormann'>
         <organization>Universitaet Bremen TZI</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.castellani-core-alive' target='https://datatracker.ietf.org/doc/html/draft-castellani-core-alive-00'>
   <front>
      <title>CoAP Alive Message</title>
      <author fullname='Angelo P. Castellani' initials='A. P.' surname='Castellani'>
         <organization>University of Padova</organization>
      </author>
      <author fullname='Salvatore Loreto' initials='S.' surname='Loreto'>
         <organization>Ericsson</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.chakrabarti-nordmark-energy-aware-nd' target='https://datatracker.ietf.org/doc/html/draft-chakrabarti-nordmark-energy-aware-nd-02'>
   <front>
      <title>Energy Aware IPv6 Neighbor Discovery Optimizations</title>
      <author fullname='Samita Chakrabarti' initials='S.' surname='Chakrabarti'>
         <organization>Ericsson</organization>
      </author>
      <author fullname='Erik Nordmark' initials='E.' surname='Nordmark'>
         <organization>Cisco Systems</organization>
      </author>
      <author fullname='Margaret Cullen' initials='M.' surname='Cullen'>
         <organization>Painless Security</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.zhang-greennet' target='https://datatracker.ietf.org/doc/html/draft-zhang-greennet-01'>
   <front>
      <title>Power-aware Routing and Traffic Engineering: Requirements, Approaches, and Issues</title>
      <author fullname='Beichuan Zhang' initials='B.' surname='Zhang'>
         <organization>The University of Arizona</organization>
      </author>
      <author fullname='Junxiao Shi' initials='J.' surname='Shi'>
         <organization>The University of Arizona</organization>
      </author>
      <author fullname='Jie Dong' initials='J.' surname='Dong'>
         <organization>Huawei</organization>
      </author>
      <author fullname='Mingui Zhang' initials='M.' surname='Zhang'>
         <organization>Huawei</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.fossati-core-monitor-option' target='https://datatracker.ietf.org/doc/html/draft-fossati-core-monitor-option-00'>
   <front>
      <title>Monitor Option for CoAP</title>
      <author fullname='Thomas Fossati' initials='T.' surname='Fossati'>
         <organization>KoanLogic</organization>
      </author>
      <author fullname='Pierpaolo Giacomin' initials='P.' surname='Giacomin'>
         <organization>Freelance</organization>
      </author>
      <author fullname='Salvatore Loreto' initials='S.' surname='Loreto'>
         <organization>Ericsson</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.fossati-core-publish-option' target='https://datatracker.ietf.org/doc/html/draft-fossati-core-publish-option-03'>
   <front>
      <title>Publish Option for CoAP</title>
      <author fullname='Thomas Fossati' initials='T.' surname='Fossati'>
         <organization>Alcatel-Lucent</organization>
      </author>
      <author fullname='Pierpaolo Giacomin' initials='P.' surname='Giacomin'>
         <organization>Freelance</organization>
      </author>
      <author fullname='Salvatore Loreto' initials='S.' surname='Loreto'>
         <organization>Ericsson</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.giacomin-core-sleepy-option' target='https://datatracker.ietf.org/doc/html/draft-giacomin-core-sleepy-option-00'>
   <front>
      <title>Sleepy Option for CoAP</title>
      <author fullname='Thomas Fossati' initials='T.' surname='Fossati'>
         <organization>KoanLogic</organization>
      </author>
      <author fullname='Pierpaolo Giacomin' initials='P.' surname='Giacomin'>
         <organization>Freelance</organization>
      </author>
      <author fullname='Salvatore Loreto' initials='S.' surname='Loreto'>
         <organization>Ericsson</organization>
      </author>
      <author fullname='Mirko Rossini' initials='M.' surname='Rossini'>
         <organization>CS Dept. University of Bologna</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.ietf-core-coap-pubsub' target='https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-pubsub-11'>
   <front>
      <title>Publish-Subscribe Broker for the Constrained Application Protocol (CoAP)</title>
      <author fullname='Michael Koster' initials='M.' surname='Koster'>
         <organization>SmartThings</organization>
      </author>
      <author fullname='Ari Keränen' initials='A.' surname='Keränen'>
         <organization>Ericsson</organization>
      </author>
      <author fullname='Jaime Jimenez' initials='J.' surname='Jimenez'>
         <organization>Ericsson</organization>
      </author>
      <date day='7' month='November' 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-11'/>
   
</reference>


<reference anchor='I-D.ietf-dnssd-srp' target='https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-srp-18'>
   <front>
      <title>Service Registration Protocol for DNS-Based Service Discovery</title>
      <author fullname='Ted Lemon' initials='T.' surname='Lemon'>
         <organization>Apple Inc.</organization>
      </author>
      <author fullname='Stuart Cheshire' initials='S.' surname='Cheshire'>
         <organization>Apple Inc.</organization>
      </author>
      <date day='9' month='January' year='2023'/>
      <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-18'/>
   
</reference>


<reference anchor='I-D.jennings-energy-pricing' target='https://datatracker.ietf.org/doc/html/draft-jennings-energy-pricing-01'>
   <front>
      <title>Communication of Energy Price Information</title>
      <author fullname='Cullen Fluffy Jennings' initials='C. F.' surname='Jennings'>
         <organization>Cisco</organization>
      </author>
      <author fullname='Bruce Nordman' initials='B.' surname='Nordman'>
         <organization>Lawrence Berkeley National</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.manral-bmwg-power-usage' target='https://datatracker.ietf.org/doc/html/draft-manral-bmwg-power-usage-04'>
   <front>
      <title>Benchmarking Power usage of networking devices</title>
      <author fullname='Vishwas Manral' initials='V.' surname='Manral'>
         <organization>HP</organization>
      </author>
      <author fullname='Puneet Sharma' initials='P.' surname='Sharma'>
         <organization>HP</organization>
      </author>
      <author fullname='Sujata Banerjee' initials='S.' surname='Banerjee'>
         <organization>HP</organization>
      </author>
      <author fullname='Yang Ping' initials='Y.' surname='Ping'>
         <organization>H3C</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.mjsraman-panet-inter-as-power-source' target='https://datatracker.ietf.org/doc/html/draft-mjsraman-panet-inter-as-power-source-00'>
   <front>
      <title>Reducing Power Consumption using BGP with power source data</title>
      <author fullname='Shankar Raman' initials='S.' surname='Raman'>
         <organization>IIT Madras</organization>
      </author>
      <author fullname='Balaji Venkat Venkataswami' initials='B. V.' surname='Venkataswami'>
         <organization>IIT Madras</organization>
      </author>
      <author fullname='Gaurav Raina' initials='G.' surname='Raina'>
         <organization>IIT Madras</organization>
      </author>
      <author fullname='Kamakoti Veezhinathan' initials='K.' surname='Veezhinathan'>
         <organization>IIT Madras</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.mjsraman-rtgwg-pim-power' target='https://datatracker.ietf.org/doc/html/draft-mjsraman-rtgwg-pim-power-02'>
   <front>
      <title>Building power optimal Multicast Trees</title>
      <author fullname='Shankar Raman' initials='S.' surname='Raman'>
         <organization>I.I.T Madras</organization>
      </author>
      <author fullname='Balaji Venkat Venkataswami' initials='B. V.' surname='Venkataswami'>
         <organization>I.I.T Madras</organization>
      </author>
      <author fullname='Gaurav Raina' initials='G.' surname='Raina'>
         <organization>I.I.T Madras</organization>
      </author>
      <author fullname='Vasan Srini' initials='V.' surname='Srini'>
         <organization>I.I.T Madras</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.okamoto-ccamp-midori-gmpls-extension-reqs' target='https://datatracker.ietf.org/doc/html/draft-okamoto-ccamp-midori-gmpls-extension-reqs-02'>
   <front>
      <title>Requirements of GMPLS Extensions for Energy Efficient Traffic Engineering</title>
      <author fullname='Satoru Okamoto' initials='S.' surname='Okamoto'>
         <organization>Keio University</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.rahman-core-sleepy-nodes-do-we-need' target='https://datatracker.ietf.org/doc/html/draft-rahman-core-sleepy-nodes-do-we-need-01'>
   <front>
      <title>Sleepy Devices: Do we need to Support them in CORE?</title>
      <author fullname='Akbar Rahman' initials='A.' surname='Rahman'>
         <organization>InterDigital Communications</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.rahman-core-sleepy-problem-statement' target='https://datatracker.ietf.org/doc/html/draft-rahman-core-sleepy-problem-statement-01'>
   <front>
      <title>Sleepy Devices in CoAP - Problem Statement</title>
      <author fullname='Akbar Rahman' initials='A.' surname='Rahman'>
         <organization>InterDigital Communications</organization>
      </author>
      <author fullname='Thomas Fossati' initials='T.' surname='Fossati'>
         <organization>KoanLogic</organization>
      </author>
      <author fullname='Salvatore Loreto' initials='S.' surname='Loreto'>
         <organization>Ericsson</organization>
      </author>
      <author fullname='Matthieu Vial' initials='M.' surname='Vial'>
         <organization>Schneider-Electric</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.rahman-core-sleepy' target='https://datatracker.ietf.org/doc/html/draft-rahman-core-sleepy-05'>
   <front>
      <title>Enhanced Sleepy Node Support for CoAP</title>
      <author fullname='Akbar Rahman' initials='A.' surname='Rahman'>
         <organization>InterDigital Communications</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.retana-rtgwg-eacp' target='https://datatracker.ietf.org/doc/html/draft-retana-rtgwg-eacp-06'>
   <front>
      <title>A Framework for Energy Aware Control Planes</title>
      <author fullname='Alvaro Retana' initials='A.' surname='Retana'>
         <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <author fullname='Russ White' initials='R.' surname='White'>
         <organization>Akamai Technologies</organization>
      </author>
      <author fullname='Manuel Paul' initials='M.' surname='Paul'>
         <organization>Deutsche Telekom AG</organization>
      </author>
      <date day='22' month='February' year='2023'/>
      <abstract>
	 <t>   Energy is a primary constraint in large-scale network design,
   particularly in cloud-scale data center fabrics.  While compute and
   storage clearly consume the largest amounts of energy in large-scale
   networks, the optics and electronics used in transporting data also
   contribute to energy usage and heat generation.

   This document provides an overview of 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 ones to improve the energy efficiency
   of high density, highly complex, network deployments.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-retana-rtgwg-eacp-06'/>
   
</reference>


<reference anchor='I-D.suzuki-eens-requirements' target='https://datatracker.ietf.org/doc/html/draft-suzuki-eens-requirements-00'>
   <front>
      <title>Requirements for an Energy-Efficient Network System</title>
      <author fullname='Toshiaki Suzuki' initials='T.' surname='Suzuki'>
         <organization>Hitachi, Ltd.</organization>
      </author>
      <author fullname='Toshiaki Tarui' initials='T.' surname='Tarui'>
         <organization>Hitachi, Ltd.</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.vial-core-mirror-proxy' target='https://datatracker.ietf.org/doc/html/draft-vial-core-mirror-proxy-01'>
   <front>
      <title>CoRE Mirror Server</title>
      <author fullname='Matthieu Vial' initials='M.' surname='Vial'>
         <organization>Schneider-Electric</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.vial-core-mirror-server' target='https://datatracker.ietf.org/doc/html/draft-vial-core-mirror-server-01'>
   <front>
      <title>CoRE Mirror Server</title>
      <author fullname='Matthieu Vial' initials='M.' surname='Vial'>
         <organization>Schneider-Electric</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.wang-roll-energy-optimization-scheme' target='https://datatracker.ietf.org/doc/html/draft-wang-roll-energy-optimization-scheme-00'>
   <front>
      <title>An energy optimization routing scheme for LLSs</title>
      <author fullname='Hao Wang' initials='H.' surname='Wang'>
         <organization>Chongqing University of</organization>
      </author>
      <author fullname='Min Wei' initials='M.' surname='Wei'>
         <organization>Chongqing University of</organization>
      </author>
      <author fullname='ShuaiYong Li' initials='S.' surname='Li'>
         <organization>Chongqing University of</organization>
      </author>
      <author fullname='QingQing Huang' initials='Q.' surname='Huang'>
         <organization>Chongqing University of</organization>
      </author>
      <author fullname='Ping Wang' initials='P.' surname='Wang'>
         <organization>Chongqing University of</organization>
      </author>
      <author fullname='Chaomei Wang' initials='C.' surname='Wang'>
         <organization>Chongqing University of</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.winter-energy-efficient-internet' target='https://datatracker.ietf.org/doc/html/draft-winter-energy-efficient-internet-01'>
   <front>
      <title>Towards an Energy-Efficient Internet</title>
      <author fullname='Rolf Winter' initials='R.' surname='Winter'>
         <organization>HSA</organization>
      </author>
      <author fullname='Sangjin Jeong' initials='S.' surname='Jeong'>
         <organization>ETRI</organization>
      </author>
      <author fullname='JinHyeock Choi' initials='J.' surname='Choi'>
         <organization>Samsung AIT</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.zhang-panet-problem-statement' target='https://datatracker.ietf.org/doc/html/draft-zhang-panet-problem-statement-03'>
   <front>
      <title>Power-Aware Networks (PANET): Problem Statement</title>
      <author fullname='Beichuan Zhang' initials='B.' surname='Zhang'>
         <organization>Univ. of Arizona</organization>
      </author>
      <author fullname='Junxiao Shi' initials='J.' surname='Shi'>
         <organization>Univ. of Arizona</organization>
      </author>
      <author fullname='Jie Dong' initials='J.' surname='Dong'>
         <organization>Huawei</organization>
      </author>
      <author fullname='Mingui Zhang' initials='M.' surname='Zhang'>
         <organization>Huawei</organization>
      </author>
      <author fullname='Mohamed Boucadair' initials='M.' surname='Boucadair'>
         <organization>France Telecom</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.boucadair-irtf-sdn-and-semantic-routing' target='https://datatracker.ietf.org/doc/html/draft-boucadair-irtf-sdn-and-semantic-routing-01'>
   <front>
      <title>Considerations for the use of SDN in Semantic Routing Networks</title>
      <author fullname='Mohamed Boucadair' initials='M.' surname='Boucadair'>
         <organization>Orange</organization>
      </author>
      <author fullname='Dirk Trossen' initials='D.' surname='Trossen'>
         <organization>Huawei</organization>
      </author>
      <author fullname='Adrian Farrel' initials='A.' surname='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'/>
   
</reference>


<reference anchor='I-D.petrescu-v6ops-ipv6-power-ipv4' target='https://datatracker.ietf.org/doc/html/draft-petrescu-v6ops-ipv6-power-ipv4-00'>
   <front>
      <title>Power Consumption of IPv6 vs IPv4 in Smartphone</title>
      <author fullname='Alexandre Petrescu' initials='A.' surname='Petrescu'>
         <organization>CEA, LIST</organization>
      </author>
      <author fullname='Siwar Ben Hadj Saïd' initials='S. B. H.' surname='Saïd'>
         </author>
      <author fullname='Olivier Philippot' initials='O.' surname='Philippot'>
         <organization>Greenspector</organization>
      </author>
      <author fullname='Thomas Vincent' initials='T.' surname='Vincent'>
         <organization>Greenspector</organization>
      </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'/>
   
</reference>


<reference anchor='I-D.lhan-problems-requirements-satellite-net' target='https://datatracker.ietf.org/doc/html/draft-lhan-problems-requirements-satellite-net-04'>
   <front>
      <title>Problems and Requirements of Satellite Constellation for Internet</title>
      <author fullname='Lin Han' initials='L.' surname='Han'>
         <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <author fullname='Richard Li' initials='R.' surname='Li'>
         <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <author fullname='Alvaro Retana' initials='A.' surname='Retana'>
         <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <author fullname='chenmeiling' initials='' surname='chenmeiling'>
         <organization>China Mobile</organization>
      </author>
      <author fullname='Li Su' initials='L.' surname='Su'>
         <organization>China Mobile</organization>
      </author>
      <author fullname='Tianji Jiang' initials='T.' surname='Jiang'>
         <organization>China Mobile</organization>
      </author>
      <author fullname='Ning Wang' initials='N.' surname='Wang'>
         <organization>University of Surrey</organization>
      </author>
      <date day='4' month='January' year='2023'/>
      <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-04'/>
   
</reference>


<reference anchor='I-D.ietf-tcpm-rfc793bis' target='https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-rfc793bis-28'>
   <front>
      <title>Transmission Control Protocol (TCP)</title>
      <author fullname='Wesley Eddy' initials='W.' surname='Eddy'>
         <organization>MTI Systems</organization>
      </author>
      <date day='7' month='March' year='2022'/>
      <abstract>
	 <t>This document specifies the Transmission Control Protocol (TCP).  TCP is an important transport-layer protocol in the Internet protocol stack, and it has continuously evolved over decades of use and growth of the Internet.  Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion.  This document collects and brings those changes together with the protocol specification from RFC 793.  This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793.  It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements.  It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN-RECEIVED state.  The TCP header control bits from RFC 793 have also been updated based on RFC 3168.
	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-ietf-tcpm-rfc793bis-28'/>
   
</reference>


<reference anchor='I-D.desmouceaux-ipv6-mcast-wifi-power-usage' target='https://datatracker.ietf.org/doc/html/draft-desmouceaux-ipv6-mcast-wifi-power-usage-01'>
   <front>
      <title>Power consumption due to IPv6 multicast on WiFi devices</title>
      <author fullname='Yoann Desmouceaux' initials='Y.' surname='Desmouceaux'>
         <organization>Cisco</organization>
      </author>
      <date day='1' month='August' year='2014'/>
      <abstract>
	 <t>   IPv6 networks make a consequent use of multicast for several
   purposes, including mandatory functions such as Neighbor Discovery.
   Although this use of multicast does not create real difficulties on
   wired networks, it can become painful on wireless ones, notably in
   terms of power consumption.  There might be little effect on home
   networks, however, such effects become more important on large-scale
   networks.  This memo provides statistics about the multicast traffic
   rate in a large IPv6 wireless network and the induced device power
   consumption, in response to a call emitted at IETF 89.

	 </t>
      </abstract>
   </front>
   <seriesInfo name='Internet-Draft' value='draft-desmouceaux-ipv6-mcast-wifi-power-usage-01'/>
   
</reference>


<reference anchor="ISO10589-Second-Edition" >
  <front>
    <title>Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)</title>
    <author initials="I. O. for" surname="Standardization," fullname="International Organization for Standardization,">
      <organization></organization>
    </author>
    <date year="n.d."/>
  </front>
  <seriesInfo name="ISO" value="ISO/IEC 10589:2002, Second Edition, Nov. 2002."/>
</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>
<reference anchor="BOUNDED_LATENCY" target="https://ieeexplore.ieee.org/document/61109">
  <front>
    <title>A calculus for network delay. I. Network elements in isolation</title>
    <author initials="R.L." surname="Cruz" fullname="R.L. Cruz">
      <organization></organization>
    </author>
    <date year="1991"/>
  </front>
  <seriesInfo name="DOI" value="10.1109/18.61109"/>
  <seriesInfo name="IEEE" value="Transactions on Information Theory ( Volume: 37, Issue: 1)"/>
</reference>


    </references>



  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA7W9a3PbSJcm+B2/AsGK2SVjCFI3S7K/TMuS7FK3ZWstuWp6
ZzocIAmSKIMAGwAlqxz+73Oec8lMkFS5YyN2ouctmQQTmSfP/ZokSTStZnm5
eBNv2nlyHkVt3hbZm/iijD89ZvVjnj3F1Ty+LrN68ZzUWZG22Sy+ns+ruo2f
8naZl3G7zOKb64d3cZROJnX2+Eb+Jb9xy0SzalqmK1p7VqfzNsmm37K6TfKM
3puWsySTV1T6eHJwEjVtnaWrN3FezrJ1Rv9TttGUNrCo6md8Oq+ifF2/idt6
07RHBwevD44i+hGt9jUtqpJe9Zw10Tp/E8Vx3FZT+bf8TSu2yzfxK/yzocPU
2bxx3zfPq86/p9VqRS/XD6J00y6rGqsm+Bb/T072UGV1kTVNfM2Hsy/rCiDN
Znlb1fZZVRPM323aTZ09ZXn8kE2XZVVUizxr4i/3F/YYQJC1b+Kjo6OD+JL2
UKdFfP19XdNbntJne2yatwSR+7Rs0/iySOvUfVHN6NWXF/HrVwevDvynG1qJ
fhG8KVuleUGwbLN/mTajeboZzbLdE95WS/rvLH5bbabpLM3rX57xU52Wi6y7
0c9ZWQpk/R6PXx0c7G7wHf16mm3tcSWbGE1sE/9S8UtGdE+7W75LmykB7WG5
mQR3wnu7zJtpFd8/N222aobxTTkdbQP+5FV8URRZFs/oYj7VK/rfJH57d0jo
NozfbvIC1BNfbV1EtV7mKRFRm6+rIt866cHp0auT+PbTl/c3H+9/ceL1kvG4
99+Pj+OT12fx0XF8dBofn/S2QELIzMf7lymOxIDYhcS/ZvM5YRoh8sZjCAPi
4x83VzcX/wX0+IuWIAJrR6Dbf1ngQ3kZqLFepW3+mIEwPr+7PDs9t79eH7q/
jvWv86Mj/evw8ND/eeL+PD2ynx+en566P89tgaODc/v06MitcHR04j49divQ
hwfuz7NX9uerE7eY387R+asT/fP46NQ2fnxybM8ev3plix2fHrkHXp+cuz/P
zvTPkyMHhJOjM3v25Nhtkjbmnj13bzt5fXLi/3ytf77yZ3t17Pb76pV78avT
M9vkq/Mj9+z5qb3i1esDO/zp0cGp+/PsyP157v70xzw9fe3+PDs9dn86SJ6e
n9srTl87QJ2+PncYcHBsK5wdHtgrzo7dJs/8DdGfDl1eOUienR4cuz9P3ANn
7m1nZ+4UZ+cOZudEp/bnwbG97fz41ZH7093Q+cmR/9OB+vyVOyZdkEPfsyO7
ofPzQ/fAuf/09Wv78/XBwbn78/DA/2mneH14+Nr96W7z9eHZqf+TPqW/fyNZ
tcrirK6rmgRg/K1OV7PqqYyfllkZl1Ubbxrwo+TgIF5mNZPiTXI1Sv/alHlV
m5BNn9Ka/myaBNCJ9KFpkeZNlqyrp6xOVmmZLjJIvSStp0tbaAIiL8tkWtVZ
UlfpbJWuE0EqXiIlVloUaZnLE2mh/IC/XKa030lat3lSVjX9tP7W2VFSzuzZ
v5fE0JMF8WCSFK19Oq+ahliMrL2qSgibpFq3eVXufWS9mRD3XW49sshTYlm5
HqIh5r5+3nqEtRL+elrRAWmdZjPpfDkrm2aWNPXaPv2Ldkqgb+xE6zqfQrHS
rwlqJLqTyeppoRDeNARg9/VfDV1lWibrlM6b5GVLT6SNPtpUm3q6+2zdLrBa
vpLH7PvqW7qq2iqZTtPVOlnls6rOk8VqXdDevrdZ2dBBSZX7z8Z+UKdLLBeC
oyRJ1SSzKnmiW8my2T88uq6rSZGtElK8WkaYl59132QkQ1Ldf5ZOHRCbzd+b
b3lCt95gh5u8zkTx0u8fc4Kh3H4OGsDLvz+/+G1DuqSHyxNQivSUwumadOer
/O8UN5800yW9yz0rN6APktCjywQt8McBRgqeyqW9CAinpyR5TajTzErWeBuS
qaQhTGlPmzZAlXVGukcz3SSPp9W6SfL146niAf15Yk8VS2CLvLILrIQIgIgw
b3F1bQdr2+l6ldTzKcnhSe6gSle9oi1m6ea7vG0FOk6e8nnexVU8f//p8ODV
+evkPptWdIhr0viUcEivFuOhdwMokYaW00ZImYZ6RTp3vO/jHCotIRppEmUM
QGTgX06bqMo4+z4FkLOYDkuKe1XE9B3xuQwMkPZArG3KD8IcYWOk8yD94zFn
JQ1f0fNlxo9DTyceMsvij1n7VNXf4ntYHtMs7tMZ4/OTs+OBaFle3Y8DlUp1
Kj5TyTslJfNTvSDeJxjFb7+HNZLWM/1syL8mtCQ1H2fURQli95968RtAd3xz
fRkziN+Q7DoaxgLoWAE9jD9Wj6MYX41wH3+QInR40gX/ZbVap3Xe0B7IdsOx
BY+H8TStJ/Qp7YkeXgEcTdvgIQJRRiAr5yQ0SvAtfoZ45Dqrsc6KlGFwtz0Q
2QHJFTghKcvl4oUHHvIVGRJV3bzw/R/5X+lzfJ8/pszn+NsZ4QyZQXTWF0B4
9enmDcFtdHhweDr+C0op/d8IPxgRqMg4FBCl9QJq/bJt182b8fjp6WnUgLSn
hJY1YQZ+ONZPxhBV0yIbr/N8fE8rkQZBuscJGSqkPgH6Hy/u724uP3y6/LfO
DTwAtvfP5XRZVw4d1FK+LugtJBviO1CWGh//CFWFCr9r/9IPafMtflfVajcI
rG4htwGxsxdPXqbNOh+RBTBuiFs041lGdl/Rjuc5UceYTGDGhuwrme4bZi3j
tmnnXzM9wldmDl+Fkr/W2Zrs6K/rsiy+Hp0eHx9+XWEHX7GDrwej9WwOiL39
9OXj1fXV1w8XD9cfL/+9i7gXhKDFdFNsGiaeUglzlhXp8yi+GTlSpR3wfgBU
wvOCwbAPN3fBGH8efRjFl/Xm7wBWh69fH/4TXjFiHR68Hh+ej07xh6Pb6+vr
Hu38gay2JmXGQvRUElvwDOxhmVX1c9yP/6iKDbZwfEa2ZtNs8GLlMdu3k2dZ
9n1dkCwb4U++I7uFsewgSpIkTidkqNJ7o+hhSTS3ylaVcjwyVFOi/8CJw5Aj
esbOyISfPMfCHtdVQ/8UZ07knDnm6yG+LdwDHGFMv2Cl7E3sdMhh7HXFIRhs
SzKWlo7qbLYRzkwvp8+bzWpt/zSGBC7TbEhi5mU6yUlm0WvoVtvw9balkR7S
4EA3Hz/VeUsqDR5bZsWanqXDxJtynq5otbQ2oZC2fPxhPNm0ccRSPGuwPhCI
tq3EuazWGdaqoQnHKwJ/bM/ikazjBotw34/ElQnUW66wIR2KiA9Hgdcqnz+D
pS7SdaN89ZFWzBcpeGpE+LsRxKHn0zVupIaIHMkVkwI3K7Io+g2ypq4Uptuw
IOASueV/Yy+4Zz7ykhac0G35W6az4dIdEkRbGx/ffCZAx3fM+TZFWhd0SXQd
UyBS4x+BVcL7fSJNg/4b3dxf62d0Pv8YmykzgtJsQ+KRlOhV3kD/FCdgE8nN
wFQhVKafViVtCrRPvD+viA/UWdoANP1stBgN4yKdfgP+rCqcerOiC4UVEjdT
urkBYwivRf/fViAeR+yqobt9itN4QQZJKSCSa2wCDOfd0G8jMoVom/OcEYS+
V68j3fQoju/5amN7ZipUPqtoKVhgKSEkITqWVbBHaczcoCAy/16V1epZ8JDu
b9PoeXEBTfotw+EmGS1R4+gzJYpR1HEQ4nhk2AB/N+WMHk1th3oGWhmn5t0V
xXPc5IuS/wESjfC+7DsZB0U2BBuYsM61Il2AeCQpzk+jkJ1smg2vweKgMYJs
w/1MOm+IM6ANsAHXb/uQG4+BRqwIEe5Ua4eUWLLMnogqRjG/mv6PWUmKI1Wq
u63I5iOggu6mrP4xp3LSiR6MeJfdFe2dujIoLK3oCvmA2C89TSck9ADE9Yx6
BwxedikzZ6Tfk8lJh4H2VOQlb+JpmTNCuJM62DzHT3RMR3xMDELC2WwUX/MP
5H420ymx0vmmiPhIHeg+5URiy/RRzlMzYPmWN+sZIzDzmpysYVqMUXsEbqH+
9/v0kf37F+U2/wjfwes1OaEEbQavUoqYsiqpYoCuNaf30zEqAgZhXaG676Pi
JH0aMT0C6mAEjFOb0kHGsJSEOXiOoZgwS+Ov2AAQUrcjeBd5KpWvWfazN2RD
J2eZomoJ0Yvnv9/+XPJOHHm2TGTYf2ScwcmjOLQIhfLTKXtDQfZZFv/40RVW
P38y8bKgmJFRmxcNYP9bfJUv6DpkoSgK/wVH8rTOJwx0AhkUB68r0FYIXYAL
9P28rla05zIByDmuMMNCuGRINVWPACpARzYRPoDL28CM9U+OoCbqraZkOtrb
CMoNaX4kzLGpmewXKCsSOweQSM4OI/At5nLFU/pMj/O2VC6KjOe3XNKfJPrq
YdxhNt4W6SgEKoCyR5WE9LJoRQunC8aDFtKI/mB4ECnhgPA888WKYCKDN1uQ
tSDyx1i/oKkjWoAZiBxI3LycFhu2DrOEl6TPi/xv+mDPzpk0e/dAy4zUa3qa
1T6ovfGd2py9uH9/+3A3JFQRLzehSFRN6I1ZK0oXf3HE3+hT8Ob+/DkYRgsy
gNfM5winRa40fkfBHkwP/pg9Nfs38fGj2wT80bR8rFImLUCVcNiDZZDUyVpR
0IK36r0TZ9/kRQuFtq3WZkzKFn5/Ji3iIfve7n//7w94fySHPTg/JTCIrseM
jmy/wdCpCuFiZLV8Ixh8IIt/Q0olr3T7QU+CSAAttKGHp1k2E3jaZUOY18br
I9qr/LBhslXHPoGB6JOQ8xFaGUx26DezkDyXpE1UJfGdHuEGa29p0RN5Dbzv
QR/U3/ZEhQCglvmaMWsXucmon0ODAledOb2XeR+EA9bk1zFRqR1A0qfM5qyX
tvZUlEFxIRO1IkEL0oQALQkziTsRJsITRAQNdjml/RXEYonHkoqQzoZbxIUF
ZzXrQUxRafkMHXCR0BnV42UbaITgc1lIULH133otdwWjgzZFHDWjF87VJ5Pi
8fG8yL7nwjCHYKiEAO6fmya1PxGms39EwA02IGhReCno2khk0DZnpGksWyj6
m8Vy6+5aMorp03hXhjLuhRoRI7I68yKWsEX+LaMvWNDi2wJX0bSihuQTgd22
FIpTUkkWkHa0AvueKhyO+INXGVXZI5KjfRSNqCbLtGYpCS0xL9cVoVXMnpnn
fXrEmPB35O8zbx1HhupXrSZ56eQHKypPS2I44JyiLs8ysiWfCZTmGhOIkM5c
m+vK1CrVBdypOwqyHlrhHIXAp+3xrhSM7qCTfMFgBJ8GkLorEeLQa7FFfLcH
eLybSFR1uVcxb2xLb1jld1cZmCS8okiAm7vx7d2He5OYpkDzRsM9dvc2I4or
qjVUy0hZ3zqlp+ZkTs+yKbScOJ8L9b4g2KBZ/Ocmf0wLttHEwajKrShWo/iT
CD+VVXQtQ9zgM+/RQXGawuFphoLtl/TBuCXWiffg7z07mGTyU4WwasVuK5FX
SE0K8xntfM6n6gEM3yEQGCw7Ac0KRqTt1nPIEZmxkrMSnaijkJIuLrR6TyvA
uqUHoKLS3gnzr0XsvokfSK4jBv7M5M/q5DRtQFN7MZK3oMdlZPH4vk+T7QeK
Tg1Ny2s+g1BJIB1+UzNWq55kotC7OEyFsRugjRJ86KYE80WtMqQpA91tFL37
L2hIoGFV7R4rGD+tAaZzdNVQMrGxb9gk4N87yRz1729MMUAAnMRp05WnojMc
nR7uimyCPSnpaZMXkAFEY7Q/gehEvSW6dRcwYZ7GkOBtJ6QdEkuJJ7QGk3YZ
0RXlVe1OFfBsEy4psadqgRsyEPTYC3qVP+Z8zlu6kZyg9520hYer20EAHOhd
vFlHBSx5Iy8Nc0EreojoHXsIOMh6+dxAXiRF+gx7h6BB2P5N/xno3+G+R4LM
4Ep3xH6JFNz+8OhdDb1iDZz/SAympmsr2IsmTF3JaEko6rBsLcuswmUQuSBm
ulK+Pnn29x/sy6F/dHMX9/lmz14fQhlk3evu8VQ/RWLFC6iA5AlFBdVpDw6w
QlsFZivbsGtWAgHgqMMXJoKgHKgWQz6gDkNfwCKeI35cM5BFQpkLmOORRPTe
ZA4cxI3I6poRilXWGfvVwFncM6P4z2VeZB5MnjWIbV214ivDA/O8hsiqHe3m
tXo1jIbLDCcn1VOYf8Ss6Yn0RX7GpK1c3L4LYUp/VtcX8/8S7HZZAQOKjHnw
pjat//D164NGDKFsBmNvUmfpN/hgn0WHE+nhjzShD9hAZhg4DUB8tAGG52Uo
5vDgfFPzWiFKR3zX/npjvV5F9etylrRVQv/xtkAUXbR62TVvINTuYtZlN6wy
l9XTMM7FGC6g2j1lrOBBugj8ErVR2UorYbXOnAaSyavpP2CXEIqg6YL0iMAr
HSMOQabOFNl2OHW2mlSz3C8T8E4+gDkpL9WZHXDPh0vjnmevj3c4JJ1sRNbv
jx8vRFxhf4gXSum3yFdQ3bKZss/va8TnCR1x/GW1HgZwiD0cnH8jeqo2xQzs
VyPA4k0kYZWzeU9LJJNnrITPnxCJDKSlviS++Pz/DNWNBePgW8Y+N6NhjsrW
DZNtRJwd8VNCmWe9/fcFWR4klpr4M4Gf7Gyc5lLjrI+cD9fR0D5LtDu+CC6l
ES2ObP4lyCajfdGt4r+ib+BScrw11li5s0Vt1S3E8Df6lrQQWuY9ARnU0tfX
DyK71Lj/9r3dKZK0cKmBCCCQZk7+gUGXQmsA0px016rucsIuopvgIe3fdghF
JGvlNEiBoc3PEboTPVuCPvpFE9OdTr/BmItov3nlPJt2blEYOM9lqgYB9NEI
VqxYWhwaIYpi03CxkahK3olaB/zJx8cbB0pZFriiiYGEq2W1rjorztI29bxW
MONdTZKk0tB/WT3Sg1HUh0Pr5m7gmbfaMVB1Z/lMvUtwxxL4V0Dz3lwWAk7k
uhCJegkUOUMIdp3XYnH3A/Z0p+t14Zwp9YazdISv562zqTRw5PYkfFluw+cO
bNaF4p5SZOtcH1CUI8AZ4ovVA6ftO/eyKN8i0MT0gn8cLsxZhqgaFq7BGjdk
upGBiHc5Bdwtp0eIvFMG55CgBIJH6XSZmT8vm3kHQ17Guj+Wv0xAOLNbGFYq
30JfTKMBkJ9DwOxYBiH2GdSDKPs+LTZgkeyeJ1nUmviw8xFkoAPy6+d52xoQ
Wb/I4SrgzTStP7GmX6jraVe2XJfT+nktHtU/lyqpm5TAN0HWG3DdG7EaU8Ld
i4ZKCpDuzXlVSOQaH/HU3ED6CpesItHaO/KRmUogdjK3K/VJBFLYNNied5F9
YNy4z6Yk3NtnKKwf7k0dJ03r509xmSFF1PsHj4J/IDXRixGT1khXLhf0Z5mJ
eWbRVOXjDrzjDjmQrkHyJ19tVnE6kwSTtIgYP8zW5AhIwfHLbaQnTaJebNjr
BH+SJO4weTr3eajV7dOXnyNRqtkULzgjItQOFQnYYUca3swSAEheXLzAh0VL
MdklaLDrD5JIH6hSsMPp1sSC5oLzbFlzcEBxOdIYJKF7wdkzj6RUlpxLJx8M
VIYS2TzCJUlH4vhek8Hb3obshan6ea3OKLIIYJ227PvwYIq2zIpr1RZY/9cN
Oxtla3H3ThWY40D8szItmos9pRq32uxBMC/aCrqw5qZGCtPeAg845xP7/3jp
JTJH1B4cQ9HXcA6ZFSkZey4j62Myr4pZtHaRqa5nqjEfihCgmWAE+U/wWW/q
hoxm4tGLvHR+vcuLu+v/yY9+wh8IFyu0hh6kz8ksh7M4uBXeNmFfwn4z8c86
FVYC0ZJ7Vkpo2H4onuwOoODry0N/5V8bTiEwjzJLL5ZOzknFfo14Jc5l8EfC
woEQAIf+kZ7GL7rKWiID0ZjEUBGZConHJgitOiMuCsz2kUgCMKm1KuOVmjzK
0G7i3kWjeUUb+NOZZyGYekvoQozq4uF2MIwjryYSEhGe6HU7m0dxA6xReevh
6/ODpkOcoSO2Y9XSL3pX0CT+YHcAFv4DmWm9YSSUzHbN1pcEy1YdUEyEThOG
GZBAd0BsLqvB6cg+mNIiYGozjhiU02dBquop+SvnmC+jQcoBX5J/ldhnZADC
fIXjITHHQ+IMe/U7eITgfTrqYhOtqRJVUa5CXUkytqM9Nr6y+K1oMl3dc2An
mH8lAYmJW2W24RwW+OenpMUmIeWn0LYjEVQjZ6NtX5aTkOzVZx/Jjx9bmVsk
qRjmCL+wqVGwANrrrPAOL/YgsZJhyADU/XiXwB+u2V9K97TtaOumFCIFK2xV
YLVBHV7UrIjemzrz53tC2puPD/fXn/8YdNAPUpnkFuF3m8GcFj13vRH2so0d
psk85qnJ6UNE9RIxTSp17a1y8S8RmXCsQugVGTh02HkKfZAgSTK5LTjqO+24
Z+EIqap4UbUdHwxsVdJB07z0mi2xS0JWdnCIpk47ASfBfRsjhNxJhKH0Hx21
cJInaQ6/k9QTvwbQS/3HTg2E31kyQiDGkBgoNmWqof3aIob+HaKYvDp7RWDR
XQqToksww7JZsqUqVpCIEVNeDDfycl6TqlBv2CaMjE9BjmADN9WDZk/NNjA0
OQrMZhLMI2aTVyS8AfcouhIiwFbYhlDVd681zdbAEkgF/U4whgOJG/a5cAJv
3Pf0+5bU1kRqIAeRs0AVTzRUrKuImf/E0QhklzyHETwFlTh32BXSOiRV7TgR
5Q0+oQq5LKybDQMVVR2ECK3Qi7Z0VU8gV6bV5HuI5Orm3TuhEt5uNMvmhnDq
AcTNKvExRue4E2ibQGAYMEwDKKrgfBrPsQKy22L0UVcRZWVENxWIc4DEyRlT
SR3IK87QsMSgh8u7sdfyt7BpGHWkzty5nB1hiE345co5Sk/P4eb0GQKfH+7U
Of7qlXlE72/uTETTn1FE/8MQkmSqqmXlOAys0N6cDzHw/njt+4X9N6FWaRKO
7Vsh8I7T2wDpMicsOsEuzKODgwOXILIiXkOUNM4A03UNJuZdhXwvUVvNUtbb
6mxVsZbP1MtOy7XLdEfkUm378T3s+123ff/m/uqj36g3+bzXYRhZrJkQEfqZ
qImwUy0E0wSI8si6TrpuncmR1WQMZJyDuwRimvOq//D2CklQz3HE+VMVSjUt
ooblWzKrkdK1GAcLujf9jwHzmPh3YSP0q4/Zk0W0Ln2gxuX6IAruZB7qdkmC
4B9zomP4Ji28042bsANbtA2A0oen2PNCF0T3yalzWABxvJdfgQumsyNcw2So
8S8Nt7jnJK6OyzBBgAtACWrzcjDKdA57VBUPiGY24fgYgnNR5xxjRhAl3/B4
KdR4OCA4J6oCtpSb1QSgDnYUWYImoZIuMghWgSuo5gQ+qPwpcdl2AzoLowMC
3CBzzfwNZBo4e6wTLsLzKj0s/wHpWHxQC2prhkInkpelnJWnEKKl+o1kDrXZ
93YgBbWGBE2YRyUbbUgp4wQD+orVUuTt0mumJIxG0TUoUOrj5SFQZoZnHv7Q
JPZ/WJsFAf/s6o+rOPpf9L+Pzb2t9h/9TnXEihCJLJ88LQmkYXlEItrk2G0j
4U0kXFmjKWGzx1lyeH7w+tXhq/NTsma6IS9/2ekKCN65bJX1FnHdg4ecoGWJ
YJGHhkYoCftJxfvW6B0GntzteJ2LDHFRkb2/qKpvmuoCFqnJMrHe4u5+olUG
GhyKJqaYofJbg+ZyFglk7BwHNM3p6E1WzE2wpiWZks0m68S+nsz7pavMUEk2
4zxt+OLg/subb6xTEBCgK607ySlm1Hujewj9DNEdMpMEvdlLU69U6tM+p0Qx
ILGyeiIO+WxuV06VJwG2SAE59pj1jOGjcqlaPfeGQZzLONa+NMAm8IlMWfFM
m4ggvhIa04wUiW8I8aqdE+oSPvfzSVOhzelLwGXT65KFHcmEq8uB8j9vgf8y
BG/JRiqEDQ6BzwRWbcVmlmM4hHxJ59dh7uyIAyQSQYTB9q2EqamMxMWsfc5K
xB5HUkc3NVdrwXebcoJxGffoTqt5Qv8HKPc0B1S1rD5M4HIxMJ3cBed1pefo
MS02mlELS419cYcHo9HxARvXYLAisDqFZcZqOGgcpE2SPUMqv7w06rPlysq4
tPNgPVDrLiRAMS+g7IiDC/Wz7jXdAz8PUAkUMJIopDhj0mHCB2OESL4AaFxm
UMCBCcdL+i3jgILsJQoiOqo9ibEhCCNeryJIl/XoTnRTzpo9WRGcOtix2m2z
Y4Z7BLh38k5F6yIDcKqioGpFtpUopyjSSVWHqb58zZJYOWaLUFycDeuJ6oVd
1NVTu5SwQdPRA4CEJr8zFyTYcugPHS+TkwmrtaQ+sezqZyF3/Wk0DYKBRI9D
//MwFqabDuC+cnGKrJG0Ja/eKGIo6CMDPZB2gsqZ95zfiJoPNQuEQryHJmCn
HZuCkwGy7/CceN+AUrFYIkAkSeEgigrivwNBFDCcsPJpOyLCYVT8bDPJiYO0
XKMioTqXKbSdZ8Yxe2LlBdtldO2P8HqWGZ+3SbXqY0/tADsmXzipZuwLmEmo
Ef/n6g220OstCBtyS2bmCywyb1WkSBZMfA8J9rFqRR+/79Z5/fhtK5eerKfu
E5oV4MANkpJsaJakXBTPbtY0fjIYcFbFTGzpWc4uvyUInWQAAOhB7CSclRZJ
Dj+9JuTuYnRaSglnbaLujcTG2+y5Ki3WQqtKiVS25Qceble3WdERU23NV9N2
fFndLNUqzGiLUHD3xP4TO7wvXUAQA6EcACf7viT91RAQLRGg3ziQeRr26Zc7
qIP44kJC+3TilXob2HUPMiT1FB8VEvZBhXLuih/50grUxIe6VQ17L1sZYyyr
IJ2zc2hmk869IQnRXSgOJcnVYbKqTEwMBAEuW+O4N5E/4STXfszNEDUJTDtE
Qh/iR2heBDxy9+xeR7qS0i/d7M3DtlEuktt55FDg1lj4HAVaiKFnmXFzluGp
xSYVuBA3VpAHvXMYwRXN3NedL4icQRGQPfuKf0mvfFe5ILPZpUW1mcX30yWx
I1i2UfTZIZBijSejPnjeWuJ+T0ilH4CMxLViadGhfLaKmU1LgkfKSsz0Qepk
WnefQBAlKLgrERQZw6/ADFSjl+yH3JScBjTS7e9obM5wTjtxKm9BMGo8xLgI
hHNlGyNhRgBjUaUzsaAtJEWYKUASbcFe4MQ2VwHVM27M5ALy/oXpI9kgDNV6
G74aDYHuNGSeJNdmwS+9WNpccBK/R3Bo/IjgxoELyBdeyeXdAyxchkr8R8B1
2fmQqasvX7EE7LjduCaEQQtsZ69hf8E2FMnHdjriKDNkbxdsE7OS1JuIRUja
RrPnkn4sRNwXRssBmVXOvnnmH9hgUWmViUQqNy5ZdBd8yqdcpn4ftglYgon1
Tw8PdLDptwmkoUn3gdTMcfuPWIN483TChXuVy4the2xF0gl7EkcXXX2FSAnv
dhkek7Y7lnMg150J7pMUi2XxewmBEiR+J+tLU5nSv6qafQXzAI/sjhoxpFAT
arnyT2nTmsefuTdyQNthgDDsdQv0SdbqaMOFxooyZtROvAmMA2VLt4F2LsaE
ie+WQvJunXeVBAYiCXgOZbclPwBLochXIGKPgz9+mLuAK8OZKgibRmU1luYh
6HWiy4+RxgA2jWJtwFtKPMSXqPo7XcYe1aJrXvWDloBbpgiHLiJnkFg44lJP
7FFMhIageKAUwY5l2aAYUokJ5tuICPpELJrZcah+M8BJyi4cfuda36OIMlNI
B9n5G4F+IG+CgHokZVmo4VM2WdXpIhPsA6rFnzPWOp6j6LqDNGGeLLwWtgos
4MtmqGoyxyJEaWGPgmRTcZqTMEIsxmJNOuRF6LKnhnQDxLeKApeGGtR6cwX+
cyNeWFOj1RNncpYY+pLoD9mwgdEzsHUj1uqQFSZ5hdv7GcUX1uygFtHBdbh2
IXroZOHIE7/njHJz7EasMmR6DIPSNCWtSFsRsJooLATNACQLMshvdw7YwMYZ
xXFPhNf/xdfU48ofb9GzZVqCNczFwa0FvF1/fxgSiTyRwSfHbIS+x3nYI/e0
RvElCtPGdHlg1OOjg6OD8cER//cr7wZbSf5EzuU6hff2klMdWE1N7qpW0rzQ
p+PnT0ExFF9MSauAmZla0fDWRxztSAVMUmjp4h3aRsI8Xki0t6QVzqjoGCrb
RRIws+di4mgpacOOU6DWVoEkArPODcgXUqIssi+t0ES5RznkgJkr64ZQtlh5
3jkPF9+UHKPYOqcebn+NGTQpSbyDMJLcJ5/7wFaY1Jwg6F4jwsxhv6CuVLIC
S+SpcVoBWjCJaaK1j4ccdeZcBVHPfMqr5YF4tOQDgn+km1lejSXAZeWl4bHs
ONorpOC4gqYo2pU45qjxT3x2+5buJkDLrBw95d/yNbo7cbcS/Gt8C7FMu/ZJ
IyzrOCsqLFlwRdTsMksVCZCBp/Rtkrq7eRf2fiohEqxZ0X+3p9fcxiJfi1/E
NTGCVeK0uNmjyhCE7nbiZOCVLki2Bys0JV+Fi1TLqttCcnF5WdG8Gi3LwRUG
WliQL8j6kCMShxbcOwR31wTFiBb9TVvf76rZEHFHEuqC7cPONk0sZ9Yz1iJ1
i8Y/ZaLYS65R/KURxbSbdbKthDHSRjmgws4sCQOwGN6BD65cyj/Yyi3yeZaw
6GCMHOL7MZiqIBZXexHHQHThl7gVPhwSRixph6oq+W0KzZvWcvF5/Mfn3Q2L
d+/o4PAwIM1q7dIqe5+ztEi4/OiyUzBNmPNnNknorE/EtJte3P/8cPnn9dsB
p0CIa6JCGg6Lkshl3KRWa8dBp1XgkdFiEg2fI0hWI5+JVJOWC9ldZgKoYEkc
pYZep5XcgrDsq+EEKBw02UJdq28bBjFu6YhLJ8m+m5M4f4loRYEaxv9vxUXE
0iEDXjr+dutlwMz4lgjwerqsNBq7qKpZ7LpMNYyFiLQGTgNX3f0yx2YrSUu4
fPBmy1sv5TZRyi0SmummaVzvlC0HTRD74wwq30sNsQbHY9qa6KaItdtKxNVD
5oPXCNG004bNKr+lkFxDKBNzU6tBmNfOJbPtfRlG6U6ua7jx0T7hLDlc+Urq
lDQ7BNfYCXA6l7klWDi+iRSAxPt95NBsdwQ5GgisaeoHjGnLxe5K6XFnYw1X
Czfpk6hFLfwYwELYHKylYnPKyDyCDIw/X1Z1VabxJQGX0/9BsK+HosQGqm+3
ykFvjBO/paKhrpb5BGEmcWrKp5n1B3IdJyAaIVgzy7lGtQbCGkVhCarrrFL/
JEtO/tlSwnezoIFDQJm7rLIlE0ngQhafhMBSpjnxzzrMwwZbzWBWP3vF0Rpx
WUNoctzhUcRSuocrOx6yK+KT0Ou+ssxsZF5ouEbYWuSEFhSaKatle6w26+IV
kMKEtIvMaVgvNhzU29JK6SL7zo0IXOJRXIRVyvKUOKocFbpkQijYuAs58Ty+
/HQUZ1biFZRnV/NoT0hrqJnMnk45TUs8R/v94ELkXMfGim+rbDNS2n7Be77k
koSXqhL64bYHscQIwZJkzdBjueOUpTv68UM6RSJDDwo7894gxJjuvSO5BFYA
dvE1ZRJxDFr2GYVdcwT9Wal4AeiNtHtrxCKQADrIDFpNypHJimWTa0vADSzH
vs+G4urO7qZWFwcbTpIu6a+z/8ZnLXc7W47QFW7nswepCuJMFK0T9W3F7OJE
v9cmpRKaR5ZwJkMSCKs67FSC6QheqrNRThQcqDGvm73XUicfOd/OWlNxWhZt
miD/WNV7ofDGAWg7S5Ez8hfwi2v76LzwIT8LGMw3yuwVD/j5zXoEP7I0GRnG
ae6+Xpp6P5WuTBCurIM10xoKq5etwG12FtHB6J8LLskU3GB26heN1IGKAgtJ
5jE1JFDLyYT1tijX8BrtqxsD95ZaEk9XrHqaTMuQqr13F5gb6j7YHEc30PxB
86TVZSfp782Gc9DiAuIW/R2ySAr0YHhKbnEV9ol1bgDtzkr/Roatyz1zhwHd
qvg/NhaB3W1lKaRl5PfYdRykLXH3OX07msEWGM/JJF1k5Vfa1ddv8OzRJ5sF
Iee3bFkHn/L/PuX1t025+Bo8MmZXwU2p7Qef3+xRz8RBoMDfUba4kUwnVu81
q5KrJiJzzWzrUi/1ubCEAnCPJQwL0GXLCuyOhxn04+qZzCKW5DUfdLF4maS4
sXz0Oot4jtJmvwEkGWsSwsf9eWrZ2jAT914MDYJ0wkpD8gS/DVYNG7996vYy
i++trYyvofrtt/gDmYnSiRZn/EBLP7sH4v6HDx8H8Y/f6D8/o+iXj5KCltZB
PY3rjecKjhDgr9NZXmnBEVMmrpG2T4KDBBVestY6MH+7wSN8NbyemtiiiFqV
hdgg2umSi4gyfRxfR4FHzzWb4d9N0Laxdk1OFcOWac2dOs1HRz/rSzqstCJR
pWMQS8QLfcDpSkg0VFMJjbhoEfaAQEm6mrCDxqLEuuru+3hX0OJW5qJ/yrRn
G58nQj5gnv1dcZEHO/TN0WmrsVclg2DSoIwCZKYQsZc3tEv4rgh77jP2wosJ
9+d7vSHsm1NHEdvnsjpOUA5tCwna4sQ+45tQwvmXzKsRcXGsy9/wrguUXKmr
C+MZSE9ZSF9BUVXCRrYv6E/WlrXbycyxAPWouq4ua+t7s+2Ikg4HRHMZcn4f
grh68GKJoojv3jB8qCac61uctmnYvEDvolkpWEVTd9EB63xpCo/WKSy5KSVz
wFo8SENCjnQBvJAj9p2B5mpWtD2ChMpkoUarCFBXWUsIR98wIUZfqEOJdWgL
gAqp+lCm5giSdhMRJuXVjNboPNNuSl2H693YJ6peXWA1b7eP1m8KUlc3uDKX
J5c9Vj41XogZhdH8HnQ3yx+1R+dWnFauN0Yrqn1oFDRpJCQxfOrESown+xrQ
D0f7e9Kg73N8fnA0Onw1OpGIQ78w1jWISFRyZlqQb/S22GRk4hE7AItTHt1/
++GaoPFn/i6P+37NQ+nPcnV9GX/5cA0svFGX+scHziEIizvQ4k6IFvTmmoeB
eLPvedP2s9ngjdTRnn749OfdxUf6ToKUPe4Aw0ag57v8RP9PO8Edq8S0+gXe
a/x+0Iv7p3Rg4njwcNHtaDO5o4ODV7hA2Bp8CEdmp75xKZcnSvsZVGb/Iyzj
HVhGk2eR2WZOMInNOGgixdOvT15zoNGTDOvA3O7G9ZMAixp0iUx/jyk49Pto
Vc1cf1/rSE4SesKZJI1E3uL+x6uB/uwMZTKd9irH4SQDgiE6JEekHGiiO4Oa
OY1zCrOZbZBBYf9WSxI7x53SNF9eF4J2Rz0HjROchscCGDje8aakrArLIctC
+mfuLpi8ZZN6a1kDUu+jweTKwaSjerh3GJ4lokT8AsMIvz5UABBwLYAvPmcs
TgjwWh/+4e5Pxep7dhAA+cR/u4Xh9uZZlnReRtjMazAuL9NAOJzgztgIQlqO
UAg8s0KGnryNMXyoPqfYzK+813gO4FMFAT5ac+g2Vul/dnTiy/7Pg39gdpAG
6YioH27uL3/vnv545/T45wOe45EXnPAVXDHqe09bur/lLgTOHARS666J3zt0
C4JC3JcruS+qlnvAkLAjfSj+vVqvgdVaR4xdWAZypKpCs1Whu1WZm9X75P1u
z7eocblOLt2S/RFMj1bWxrX7DW1SBHadTTQFQyUx8hRUPkEa7XkzG/mhzeKA
YVU3OOTIMd1fXY7DeYLrZ83ISpzOC9qDeiEs112QpiBDc5CWjxyzm8fKlpnu
IBHyIFvZa3CHfK2OOHnuYlIczasqLKhiZc1XzrlwgW9YzBWDiJJxcGL7p3Hn
p3HfqETY7dbCIvQwCIYun4tmxCUYMlDf63vu2lAjt54lHbNOkoiR1s9taXK4
jM+fPnzg21CB+rnaPOTle0Rr3g/2iFaJ+WjPoU9dQemtoNKzEbwAVxR1aKjR
uz84xwQ/bebJ/bqhOrf+wSCrT9rpcxwj7EgBNO99cLxo1xTrvYk39SQt32jz
kFcn52AcQdWsfH56dozPxU29aSuBsbQfwfg4jam5nEj/jC5wfnrGTCi+9+Wg
llNuhjLH2qdwn0SaGCpobyC9C0f1eNmw51QE2rsPJmm5ANN4iLXRl0Rg8Gb4
6DLJvfL5udZ3W/vedUJFoBOnXuDl2tO9Ey4CQpF1wyik8Vt1Y7iJT3xnwyju
XXS+v3cToTjZ6Is3+38Nh2jb0GYwuOfvObBGW/sd93jh7wincPMptZGZClJM
zZPbjV7aqAsF/X/dIO3oYvYIAM/iW/B2Js5Oikvcv7i9GfgbFtTDmD5GK0BK
yVUz5GrE9FWRZ5ZG7N2YGN3gkORPhijhF70t2/uvcUvAcnhwhDfT/gOnlZhD
83yxEeNbi9+tw3GnsUVfZMUgDnm3b0AYfSnDL2qyBthwZIvIVz5ls4WvW3Wu
eECDNma2JeuLO5mPkfMVxr0rb3Iln2o4HdB6gocc0R8X0+cpeoa9r9P1EtR1
9enq4r2wYCRFQaBa1pXrIReJaHJN2Fh5IaMfHNzoyr7raNQYgUgYF+aod0DE
Dg37ZRg0stQ3jAmoO0nPBM8eUOShRoc0Qv0CDYPb5crppwfMwqQAJnzz9nvM
PHapMEpEUEP+frYpC9Y/EpeAvD4kPeC6opTb1rmLsdXNs2G1b8hpUz9Ynbmh
GmjkMfUJJIxhyHpxiSuZTajBe8PGGU2Q5BD2TSwy6WY5yxzsDw8cQUH90PaE
/zATkuCmQysaTYNtneLg3a8efmQ4gMQ1+IOdBkQRNPUYNzyjwWz+yrdc9plL
dOal5tXL7KrehRsM0RnPYICWwX3KBO6b3lDP918Z96fN+ZEnPBPTlMmAnYx8
jExafCjebVVzKZSnBQHKdeZjqgZbdGM/nEkebqCJw+xXdqXxKD9UtuWs1rjC
JxmVI1YudwUJ8utcrsSezh+ACA6hvewCJwmoAA6WtlMRlbfW04crbxA6Zv9R
xFMjpZOclLPqb8k4fdttrCue8qABjW/hzrQ83kPH3OgF5+F2Urw350EOdWxR
9rbJa7eSy/fp4F69LJsjGUmI+j9rBFlvCTbwwJv3dwNvynVcvKJi+FStm/ub
+0h75x6eHO3rnfvCqMSfPwesYny6v3un/TWOj1hFc4IHZE6vQrZUbf0aq62b
RSX9PjHTrR/0dBhJ1Fx62jvft+99ZUxPRiL4AgM1P1+/PrG00Mttw4Qv3UcV
+nfiuNnh8OZcdy9lrV30Nk5VswYzpr9xKEbzkcVSLjqKb9HRvjtFKOJTkxk0
k9yftNPhEqOeOHlCU0wdH+4uLFi9NjeFLVi5BulKscHSnGkknUfDXgRSih8C
ho8oS3kNIG1bJJPybgLVdCTTrdCSauhg5W0d63O3ZONvqghrDnrimOyPdy+h
75uI3bRcoYJKuFCOaKa67bPvm8a5Kgvzvvx5836/hfsBKyV/yoI3uBbvtH6/
ybmghsiueMoXbNZqe5nAZdix/rhzh5oRmg/ZbCZ/EciHgj8Eas1ZK2Wao8+f
4xkV8n5mH8ChaDeNO+9sUnKLQ6gwFMYcvBrGOteB6TVKZzM419QT0lYEZu7d
hHlE0uJPU+ywJFsluEff7i10Wbte2xj8zE42p8kzbaH5kG48JMaLIKnUd7e9
rC7uBvFVJsFkMIfLrCgw280rwK7P4udrfjl+42zki7s7t2yf/vGinRzu5fP1
/QNqeK/Lx7yuuLYIHBZpHi+bx4cH8dEhVPphNwtJEs7CmYCs+v3q7L1IDy8K
4elrbzRqBUSDnt+BZchav0ZrnRmEUTauckPfF2X+XEONy6J1kHWvQaLi5Z14
8R8+3Hc+R8NPFmykW2NwB6riediRpCilbRMFjy83K+7YgVlw2jyEyyvkyaED
tC3hxuXaeOHw3Ts9vGzOTx8WJJ1zMPRtYFnZ6Uxy8UFQF68ZRN4VzrKf6Q4y
3vIX1MnGjfSCKhpfAF5nSy2LD0YRwYL1Vxp5c0typO23kiqZ0BsSxAnGFo2a
VtpgMhWfxKZjeXWaL0S9T8xDXFNWoZFf4/Kn+8tPnxG+EdI9PTy25CptbGZN
LV2uBsiL2NwOFOzuxGfGGWzDXc2+0f1FYfcaogUg2I4eyOmeQd8sto9BDazb
IaIw1SJbSAUuUNCsQ248woq1+aORY9AFYID9PiaGC5iNM5yci3K9w+mWpBmG
5R25v/q3R7eDrRTRYRTkRHAqjs5yC+YHxTIXyGUjssJHf3vDPOy+y5zfai3h
GWparmHa6ogfAxZI62qCUNv99aVgQ5/+epHlXWzg9mqN82B3FzyANox+hLi0
hUPEZwZRJ8c/aLDGMbRuJEIizg5RHVXkZfzS/QzDeY+CApIjyZ0bXY9V6Y4B
HnC/p4MxUQBpm5hfqnIJTkXW3OUXsiI9pa6Ug2PYnJ2TcwaEGYXYL/f0WMD/
8Bzo8BGEb+6vj098XRT5GryM7oSQvo8b0abn37Jn1/JSwu8cpdbOwA1PRPVh
BLVDoo4BEloZn+8vOitLiSosk2C/9KWVLIdjJdxYrGoeXV+Kax/riQG2knxJ
FmjSWLvOZjoJrBf0f9Oe8Oy2ZonZBeEgsqQp1FA6azB3DT70995+yDVpmPbH
LQv2OqdEAbi3yfFyc/S3IEgUXa/IfLQc5rDsoVu0hvJgzm1wRm8H0gjWsuYV
RFO0d3nnOc14JNmMcY3dUYwcfYmEuSFUQ4oumS46IQ+x+vw/N5kbGKtm3kAV
e6uZQgUj522483d6d4kHoSDpkahd3iThBpPGAIXZimD7MuaXW26AE0Xcyj04
Ud8rgBrXZkp28J524K3XYUobI+FbzlBCZ4boFtWDW0NM9Lw68e+Eexc+ZZzy
oGJAQUiydWb1za7YBkYKzxmeVN/5GvNSejVDlG5qGcQ4LXIdsxpzTyqUlhCs
6Uq+Zdk6LUSc8m02nGLCGU2iebvBgqWlWiUgcO7OLoN3Gh4KKjZTW0WWFuMy
s7Y7fzXSSUh1DFHxzs/PYIkL7vFddOKK6NC1rDhLRLKJ+UDa6UhGfbC7wOwp
3zDeXZ6QGigLYcRR9G928lj+V0W5UALTdpjiIwqmsW2TJ2Z8rCtIPM7Duvj6
+fryf/92hEeEo54jp8G1TCWdDqazSkBr3iINk3QklsGNkHqa1RNOjaILxVUl
W3sVocoZtaUUKDnuy+qYS2jkH6WlZd8AYtE+iMX08NJa7gXiepmR4MJN6JjU
exFKPIqWm5hfS/OZRvC/jz6SrhpS+2yKF1+niDFlBE90qiefpEOCCVB+druW
UrL5JG1ZvEY9NIm8F0e3Wwv9r+9vB2y2WAZ4ICVVUwq7ujJ5phwW9SV93Wo+
9nLqtGq2IXlIHQdubq4/+5yo4E0ux1EmH7uCHitcVB0Oo+5nSAESty+nXNdZ
5ltSiqbp39BJctLq8FTjnDZirTOTGMG+jQxvjqQ+G7MCZQxIkOb9HFb4+46O
3uWeti5dE/0IuMc7Ay0K0alvvvm8tGG2Ccw04yrWbwrOt8HIeSXFg8cNv1r2
Bgqmc2ile55IWwbpoA5wylZAydOQw+nWkhnemRpchn0vV+l3HqggZT+++qwJ
FAT2DrlpLfiWlH12vsXam5swcN7CJe8iQdauiQdF8clsgiGPjUGhwr6+CdUq
e9IiUdaGpRbKdKWg9zV4qnMHBT3D+5d3X0hVX+ZI/P9Ar3zK0awzL7URx073
jSFqmD1qTTk1LMsw7wkj3kkPR8oL37cbfy7OXesxFpnayYpGE/RWFuN9xSRr
N8WZj5s1aWYzaS6jihA77ayuXXvydXKLkd2h0B3rUIEHsIOd60JrbqsytHsj
5Y67l5VNah2yJzbCwvqxa475Vn6+TPH2bR4Yldwt24ADhwgk7oPkyKCBejCm
W+WAZsXJtJVGHW3Kg4K062Go8UZGR1wQuQVu6cgqee91yv13O6PkjdJ976BI
hsGZ8GFwo4YtCJGpQ0AQ2rkj4c8O5kh3HMfeH933KdcoqGKTUztyJDxElU0h
9v0Gqu2NdREdKr8P001ZRQn30aH2Dgt0CMGixLX9sRZR3baibrSQtNVgVO9z
FyrwSMczuZrLNfQMuhhp/pIkTLqrsfzljhOgL1aKC3zQXmsZ6u1Y5MCakTjX
v7eZtnuwRvZu1zljOzXZcjLV3+IpX2NNKobSvOZkKzfejXATRCdFLKOOQP8T
ROumgjqUT8Sy1IblZJZofx5OQ/ltGvzzZxSxvuA5jxsNhXOrsIq3hRWrsI3O
5nbpxd4NFoXvkAwcb3a7DHqbXVS7jlpEySXBU/yIwyBhlA14DYOOVDr7PXf0
RynsrOFas9aP2LPrlKwlotg2CTmuVHHDuvJqRgqvE7Tb4hWqcQU1nzkONx/y
HXScF8ZUnbwoknT2yJ1exZ5A001Tiv10bAsqKl75xmhsLzRv6IrSAcd2fSK3
NW6xrdrB2WQ13UAfZ+vZN4o2vSjCtCxJ8naAFGeKEGrZHY8Yu2m1agBwg7it
VxF29ifdvZpZit3t2ZjlEmOyS1rL9LIAFbWFLmx+2j+rN8FspWCuaNB6gRhU
UWhr0jbciaW+h69tg0UgNvpT2X6YrqcLzIwblMiABzhZ8hvaMPHWGUltzOMD
JGaylL6Ka6it7kanQzga8DF+5FUqiH3LQdkBjiy2G9K3dLR5s65Kj0/B/XBq
2XRZSUJCpa9w96qDWy1lySZdGSU6HdhMeZY8nZaD+k1qTdYC05jx03HWXlOQ
/fTccwkW8m/ktmBOtWHFE92Yzrc0BOngeB/N5t0A0YHNzua+ikMvDVxUijst
aBehICAYtFVWhY0rI4hG6PlHTTXxGo9zf5ezTpDYcYuOWDS67PA/OwAzjKaj
flRNZxeWBZ84ZYPnlkrtatcBLy03Dk6Dlhsdi6qn1pirYAvNsnsyyzTR/fTg
jPPvvWdT0uUDA1EabjC5h9q+9l9Uvc83kApO7pk+R/0a0dxhDYve05da54yj
NPTBQE2IXXFPuv397bZx6pVg6bsm05FZyeH0xcQHqeRCLRgmnFW1RaGcGfqi
TFPn+VZmTgas7FsadpHqx6rz2CVGQbMJOT1+ZwVsvwSLtV8Qldciq9NnmZkp
27TCnPPDVxoq8U2xWDMKNo7d7gAFkQhTBe6s81fXh/lb4AC4M4JnnVDLDVyi
4o/fngibfkaRurQP4WBhIR1y7hfrx/qS4EM6wkDTqIM3s+83+jNP3uWj+M+t
Xq879Y08b8kSTZst0Zny70x2fnGM45m5TLLhEZC7RM7v5oRO2e39w8XAEpbE
vrd7Z83HNLroQroj3oky3b+4awYiLycbpCGHXgnlBTKiXgbWNzLzGyw1lCXs
stURm5I2IQySxRRJWUnWkDerGs+I17t1zZBK2Kjun5+4qSiR/+3N7SdkLZLW
U4LMuEKhRW/EKab3SEaZ7HNPo2BrsNnjsKhwFBnXGSgo2ElOCre2ReHIuRn5
oGv2uznHzMXd0Fz9fKrAxxLW8XDDTMZH6FOcWjoSkX3TcutYQYP9Y6WdO0gC
z1uZBB36fMzTqGOOy7A24SU2GsE567eQ3dkK+YongUnepagD15ZxDzJAuk4q
PtqgRGT7/JUipdkyejG0YCQOd9oX2SDTLN18T/L142myYhMAZCpZP8kGyjFH
npDf0kjDNHrQ54yyktV0agqDWhD1WewUlamBY+UF1lawEeWeNW+2p9l36dsn
l8K8VQHZrVs2GWot1jnGwhqDZk79+E0ViCjSz32OaNAIJEhFsxQ9z4g4luG8
taHBCvMiNNugOnBXgt3crCDuHyQ2hZaw88Nrd0TvpdGEKJ7pg3A/kLnVXKGq
zSZVxSPx1KywdcyHzvY3F2Vz1DPiBg7S6widGTmBW+zFOLDjiXxmaIsyw8D0
NiN4S8W3Bg12riIys6coXBdvZejqZ4OaQgdQ115Y1dvx/vshQ26dSOscHVGy
T4Jf1y6N423no7Hl3HAvDcYsK/kWSphwN2hk+NVZAt60StfJAUnNNxLB5U4X
aYNAZBAmbQIUiibqIxOn0XSpOp2zT0OzgFCIZzfJAhj8W33XdVRmn52eHP78
GWXlUoompLRG381xIrp1djuFaIysRU6fdjtg6K1QC8czaioLXqILiTVhHlmL
xKODQzSw1HyyOmOlKcRJjMSSmnALjOx+sgugSDaXlwzLYbdHpfay5O7dsLc5
+RbKDc9KDg/X8ea6MpGIUyZ/cYfyAPHmQr5d5XVd1QknItdS5rf3Ab4XJITJ
9+gEQRcoj3DUulkmktLjF1nkKSd0yFNygp2HwCYRfSx1MQ4Q+RfV6ZKO0llB
TabE1b74xXaf/qfvEoZmMquSJ0RTs9kL5yPelxMXcFsfEQt1HHJfmrSbcvmp
1JZmpI0b22Qzslp1rtR06SDPTJBzT4unaCvrmL3y2rBLGwqo2u3F0I8fHX8V
w4RV0J/qIYuChiC/zKZDZt/n64ErGNTajqrGVGl8lXy2yuTXh2dcU3NjA0F2
uIVYqoucHefmq9K4oH7qW8Ujg9FkODLd2YxgnQ40RAppZ2WzZr22Jea7ACqV
dWUIHFwa7Lq4KN2FbSU76cHMpdi7+niv9clmF7gy5F78A9/eX/20+uHTY2Jh
RAwTBipLuNAO7tkSn/nM9VYmJR7959cx0pIqNE9mZdPMkqZeA+z3vpNPKW44
SDjOFMC8gDZky5ps7PvP2LgAerN4qsWTZ10hSfY8o9Xnjqk0jOXw1rE9DRut
7wequSG4XC8EDO3mYYkUxF+WNctjX/u6+a8mFQeSLaSlDpsa4So3SUQsaUcm
4vHtaLF62zymroohMJnXeT8Iqv58HYpXTdinLpm5fTQQRJ9uAYvw2j5nMf//
nV4bh9m8kTf0lE5cEsMWT1FuwAL/bjO530xCFGOmiJwscH5CJAS0Caci12WE
UQUHY3GeZx2qdzkXhPQlRqLdEtpstPL0A9sfffrm9sOgN4QV6bwxkegGO92q
eWosbo974Ir2aB1K2QVilcJ2NS++uGdv1oLAkyPNNYM5R7+gNSzyGZQ0+ODy
P0A1Z/cZbvxzpvVMuzMcuQpbYsQXMzRqyxuxfHpDq588Q/qA61HSjCXIba1d
pTxIklN3GK213PTDf7hsbk8bhZ70lnBe68lztBDPaZCrMeeQg02I8kTU23cC
FNFeDHyMoRs2imZWHGjMXW25TgovGPgLnL6v3vZu/Pfzhb1woPZIOA6X5ZEk
MHy8Uj/e+ekhhKMFFdxpJX+m5XYy85ReMOLhQuJ6DW/GOfise7Q1qt+qXOsW
ZNHN0BZ4sLnrk/ocR9qGwkLlYS+KkWlPy/QbmfCQWKTN1DOk4HXq6pJyFtbU
udJ9za7zU0g7Q3Hn0ucVm2cc0eAtN5dM5YCm5BJLJdWl28tI5k5Lok3/A9qS
V/OBRtveZuV0iW1qCZQ4sswOX2ct0fR0kzyeVutGTHGxv+nPEz4JnOMAIetQ
q4CERZn2DZ620/0sdcT1OXlkCjjRUI1Y9jF3FmA7yTEq5JVFwZv8eBRkIATy
fJWiu1pwPsn6ci18NPmLNMGcfeERoUOu41tcL2JxZrXh5FSRyzwml74AT+O+
mmF/PTBmFoaqhaLb+Pjw4HjcFPAm6H8S+iRp0nSR5FWbhFvl2svIQzf1B/Ej
4TbtDqzM3BWbhX6CXNVcBpUYh7tNS6JBviPnAo0irUXvJBN2Ori5vxlo1lJt
91p9rx+T2BaeYd+aS6AOuzJrEhgdr43f1/mM+LL/R8+k/vZgxHCmKgsTpeqV
P6B3CV/w5B5tSvUr7YVf/nVBLwf/cWVR4hOO1BFrfQ2mPDgHlyTGKlCjKPIF
3q9oKqEWTZQruDVZR8rYaKKul6b3q8L5XjyOFVD8BAmmyPXHl3cxOvfCqEM8
qZDLTzKsN83r6QZdaelKvsnPexgaYb/u8bZ7Db+BORLb/L0Rdy7wJYisgAcX
phHhrFuBmK8UDg4ogkTGc7kBhVK5KQcR8bclB4e5h6NmHqd1N8rQcbVxpiXC
OSmaYS0yX/B8GPdc+9M7n0mnBwgRTgvHWYZwIcd/biQ3NyhSifqnp6RqkjTr
9KRjJt3NyN2pKvSeeyQLucGyzP79NoJ6xq5PEjz/qc7blhOiNV7aSKktoyK0
r2cOLPeJ9JLnrE3kDoHRrtqiZTXIN6V28kInKnXy4toqyh6r4jELx4/DU9Qd
th6Ed/Pmm7CKTRCpqLO8fBQHtbVZpnvMinEw+8AyvmfQ8ifqpQ/37KqY6kzE
B/LaolCZ4ICjZf92hCFhw62vKPM3Z01iHJA1Lu484q3PbvHZanxZEV9WR2C7
QLq0Qw3TQd0LDO+2mpJEmFbM7fK4FofYqHUFl0C4wWEUcyA+5EWdzXo8aiLl
nzqRREhBMgpcVqDMG4Y2n3K/Jd+/xxqNWWeJLbTotEyJ+2TSEvWgT+jPwZtY
sE5tsXib3WDCXTrrKA1OVycaF4K3XDhu6BcnqsFVjWcVjDBRmAg5cZPkfQqK
WYjwWaRB+fBu4hK3kpllEq9iZLRZkwwHKyiFIuIdih0osFTmh5dgYUBGDZww
GnTHOzrfvaRwuG7m0qkovn8mIV7Fd7RSVQfF1aK+6Uw98y5xEF8yDws0mR5r
4hYc5G4UDRexyFMLYTPBHDB6G6m3JRt4E03bk1BBMFt4R9zLK5doftt/dTA+
Pfj9785sX8i7NodPfRAMEQDeGQPncdUznAcji2Upm5oFr4BMRVOdly/cJeZO
NrWM9NTNYuoAywteE/FHUggYudIViutyU5M8cFC8k5XBB9Gisr0AJDI1wpp1
cv0IymA4rK1NU8GQ5lsu5D4kMLS5wYTssm8YwT2M/MxMoWc3MFOrckCG1m2/
Iu4twRIzllOrcuMhPSjhnEWWbAUPHetS+3Gm25NX/NiLinRkyUsMOnV4LDAW
EG1DzGePeUwaxjg6psLZLDvAXrNQnQ9CRn9FEgGpeRppLtk9fiW4IwTBQ6fA
F+J7cArc3X4ZWBZ0XnPH+Eg8AnhRVlhbGClDly6LiCD8D3UQOxhIgZKb3BOh
y64GcMEWNEf6/vLi6sINbeE97xslbKMLwok+3dTynnTpBx+w6BzPL4vF7vB1
jY95Y2WOZmz6VoMhuwy0ymEc8cztRjVF8xtJH5+1LJ+L30Hvdy344dPMCLYw
XkoSKjmU4UEwIEnrylx9TFFVa+7rKgfNV1mo26kF6OuelII4kdLq1hjSZnMN
ZXmYxunCSR66anEaBb00pRsRjyCsSKBtIasMW2dpEKhSoXTuzijtRuOFeWTf
15zEw53reVYcexZCvz57rmtO1Gch5tpFO788j4lasYaLHleTZ0kEFDI+Pvhv
cd9aOpHawxWpeOcSLRMb7rrATcCbNuH1eej6YKjeJLtgr1gJx2R/Bs64zINs
kHCQYGk9KtDIpU9CiBmXlBd3gC9fOZafzeeZTBIt3IRWRoUUQnYsEGPbm4ci
ywxx92QHxnjE556YLcBdufmqw+TUIJk9vCCPab4UK9y8tY10XbdRIgk2lk6n
G7Zb9+KOa7LVZHz1Wg7F6R/cm8v6rnurxopQZLLX/lX9iBQZMQnx31OuHPMI
KedFtqSJE/j8Hu4eT6yq/NVrBAwjTduqfPUbtFZb9/o6vnu48+a7y3t2ZaYa
C3Mx+Lz1RXKR5uTxwLDQvaJXBdtiIW1oNGvWxc8ll4Au+rp1Rd8aHGfK35DR
bCFoTIqXLkmIBGePrke/3M00aDpzq8k1DCM23R6Jqvq3DzfXgzhDIJRLbAuZ
4kq7PIxXTTYlzp91bc8fPz5e3N/dXH74dPlvrgVW7yPJumV8sUL/OPpxV2pK
W0ZgPK4Cv6arCF08jkt289eizkiHbkpGI29QvuvlhsVbMGCoXFSaTMO9CNSO
+3J/gUZuiIWtdEydeHPQsK265g4scf+DKAKDPZ6eeUd5/E1Hst/ynBX64IKb
biTcFYzjp+rQJM2pTotksnpadBNvrALH/I/cyZldx9YlUf1A0vpKBrqIsb2b
HROMMLL28dFWXVDoHDP2wkPerO3Njx/XtxdkdcQO1c1QdC2jgk1Ennvsbofl
kvzk/uoTV2GyzQTwHHXA81dWQpNrzMe7pvXp3y+CZxjEfAL4cBK+C42oq1GL
q8VxkjwSk5eqazZeXXChg18u94J/QkJgbgm8rlugNRQCCBg7uN9DvmYk2fJK
MWTENQfYomPFj98YyuFgNilAzK29GSK5czKob2/eWnmMmqhBNN2JJu+qG0Y6
QkXUfWPcPjXFwuE7uE0kgE1xNxmBetCE/PAglibkr6xjRMYijbveDiNXAGAu
G8njSvf3I6EzqUR0LTEEmbAX5m28Nxl3rH3CBe4exqwi+rkQZsRG5lRWDitd
GJop50i5XN/As2nQZJu82wiOL8udpd9URYY6qdSOAVQb7/bujfq4M8lBd4ET
l5kco9QcQ/1Muox5UgNPr5bH89Z6H8U9LqVhq4aMEq0f9OrY0KlPUHF1p7U1
jTNfZcXTEzUXijOPDo5//hyMLDgxLdK8yZQtecgkaT1dIvZjuY2RJGtxl11B
ZDxBjFKaj/LQDWjcnDNJahpHMhTbptJfpnQ7MnfCn+85iwIIW2eBM07Wb15A
1fgdItO4Mms1enzECRm9z1uN8HZZeE/Si7R3tfVjO319fs4Sbcu/7dYexj12
BAqJzO39FrlhC2753LAm68IeyogQE9nBE3U87Xwubs5GIj5EgHKAKDj8ldYZ
NR4VbUQNN94hPSa+huer8ynUD4zHIEqQci0N8EinBbSFIUQg5dB8KUNnFWXf
0TZf96GvcHqnJBHteOZl7e0c7aFEyyJuizt0Ixxn6Kw00y/jC9ugIrLmN9IW
LlxTj+KZ5woH9yC019Hcm12jzRTTLXj1JKcJYmKBVks8GsiaA3J5tUtUdp5h
78gMuJJlUbITFZxIqCbgN7SamuScEWSKXs+1MWPMd+caBhI2hDBzSVMSvZPO
2GDQyp1U+rvqOo5cdwgRR/HbrMkla8/aCkFhrB+zHGlryB+iLdR6DpnX6A/q
E0L2ZJqzRNbcVbzaBp6SiM41pZpxl7hgRAZlXQFXt+LuOqJxX7PsIK/UJZJG
roWP2dVc/lDRXYxJW55VT01njkTXvtTfWLEwmXA8NWWnHb4OuiNDpuCqKhzO
GqDc3IWdmsLo0o4kccZJIItBgZCLEMIfH24e/j2hf1ijtdfH3Fnc9R6MJEKh
AkWmW6EBIXdqib98ublSDdEYElN4bjP/NGXNVw9FUsovpqLvjm6/GgZeMxxZ
1KSSlXU7snjv3NRaTeDe8h6n7jksYebDrbAQw3Btrc1KAg7hm0ybpv6/wJRP
Tg/+I7C5Uvf8yi/nf84MRyIBu5Eur9ehNu8hDC50a0gYTMzYRKtl3cwibEy7
7uok2qn/vr/+eP/pMz7WdjIn3C+cZ1BJe0U2W6J0pZ5ettIBDzXlOlICrZcz
AvnN9aWpM+7I0Y6vyLiNsygFye4+/Xn9Obl++P3688frhwDZjk+PkJeMlzDT
wo37aNTOaAAH9i8lc8Z6s+Z0dYO7MJ0m7n+5ux/w/8q7JL3k8FQatTqjdqvV
qng6XSsZ9vIpEuvumuWmxcRFns1u3A/NsHSAnKqQaV6w88jcMF+4xVY3/14r
OQxx3TTKMeuQTAmj6J5MwwLTzIeeWZNBOWe9SHDpVu0Bk5Q401t9l8d1U1xe
nZ0hhY3VEZI1+pvAiWzbDPA6L2MzOiybQ2hp93qMtQgBdBjM/cPFw3Vw8ydH
p+euwTfcuGaIcIDPQsyptfRhO0nZig8ROinmKMGUAIR6XQLwrrHIUiZ4SUds
cy+mN3EPHj7OnZs8I8a+rFr3r7jHIcsesaTpiJRvSyB07R2QPCY9Mr9rxM0l
MwEukfe0bLORQO4GKOXyQ12sTfGSO8FG3QrpptMB2JAzlVj9Qjso2w5cHx6t
Fo9Eq/BhSR/ktXC/E8yKCIKXXf3vUlQ5QQJBvhMkhsWGfEi2u/54/fn9vyef
3v7r9eVDcvnp48P1/2T2wFC4ufh4kegjn68/XDzcfPoo3G5StUG7WM4FBQr1
zJJRurK2XqZiqnoZ8jfPbMLkMlPpItPgFOo9bsG1pbDzsUY8aq7ThrmbiF2S
rgfXVKZCbbvAxTkxnWhztdcI2Etv4CAw4a+YPYi9D5AWH7gC3U9ycq1UMeDx
6m4QOf+FlXyxUAF2oUm9m4JEzyZ8E9dXfBuqfsOvQwd9Jx0qhy+ZS2q1vDCb
ohfahZGv1Co7CRmMUponRa+tx0KttFHMrjMSHwqxSdWIdOR0DSK1J4jvDgm5
B6vEWF2goMF5ynNMN8VsjMNC9kbcQz0YRhLyu+BWvFcBfopHrSjesf21tZqb
tNidQeLSh0BgQ7ZgBTWvLsMK2QfXekX7IknLk3+/+Pg+nIVN5smmsKw7+5eG
xS04G026zeUItyovZRgvXNhWeZrVWxt7crMjIj1tp8N/Vi6Y0DupH9IuYbNG
rKLlgn0uZ6+rvwn3hfMkezvus69U8rsvbNYBuNs73+oIK20PPBG3qZp67PX2
k07uLkgZwYBU/uOnFrIfHo9lABl7FHxZirhEgSlBTp2V6g+jTkMCSXWogsHN
22XP9Pqb+7uBDrqePZfpSn5LOtVCRoC8JLucWsEJO6KBzawGHrYU95CPXMKh
BbvFqTiPw2Fo+AyILL23AmMn6mu6qhbRIYIzBZIPNKmrZNcZx5s4h1EfZ7tK
c7M5rpLwsMpIWrvaKE2L9g7dVFm9Ntc2p3LpG+jHQTwh2Bo3q0UajBLyS3CQ
AEvKDV0bP+gMDTv3IUTPMGIYSUsLjboQfbnpGixHpTHA7sWgy5JtwzKTzOLk
WaRLneDRC/B4Bx/fWN17l2XCd/Y3wJ5gTG27r4Ar0lmZ5da4VetestY+HkTK
7PrTbfDhHOHggQe9hWumYMaSN/Hnjq5/oecyt8kN11656R2yUx4SLh02XYE1
57E8Z5zZrAA5seIyEkllmtTt4mmRZOl0jSz97xnaT7LVpZkX3KtKfY5qLqHa
NCh+DstHbISFJSzAJ7pIwZMsFsXV7XiMuHjZhgY/ZxF3EkVcjhwBllh2nalf
mbZOr+xj+okGUAdmnWrivQU3JTxt5VF+rIG+1JkYMXsUyNRYSyKycyhEejAk
OwX9Im2Eq7oR+lbAPyDzDqY2Mv09ZFxpOERsZDLcF854R9Gvkm7lp77m5qv9
lPDRurIZ3ksQxhdvCBWGtRsSqn37/k5kv+ZbSIEcHOA9qy1c/dXUKUoRhRpY
mU3SRv3K8gufsz/jJZ0vstG8fOLlwXibyGnbfrBAv6o7ViJj9ECn3Kgbj1uA
S9feWc3tfVypVNDlxdxoLqdIM6l85+SUg/Vw7pBZnlq0lnM0tqokMbY3byyd
gDsQWIZTyPkdI25dk7C9Ne5uECZzLaQsWG62Bawsb0q6m7ookpb0tq7/p3NX
BqENIRpri+yqf6XjD9O0uTE1M1t93J1OnHhNkJCr8Tk5srVPbWm30nPPtzkM
M4K0R9+QSBCZWlvW/yx99p1A47vLyIXJtWMWatWz78scnQFJZWtd0p4QYKNK
jSPfeSiyjO4gRhOWo6BvbwRKFx1rIw2WGt9ffYzH3sddays1VwGraMXmymPG
1VGRqAyWDhpkjppOw8ZOJxWUg7iq4xVaiYhX+xfDsuKcK5/z1UdDo2SZpQU3
Z7bJKY/hkAHf8cZNoTmGyT8OJtJo+m+j3TutI98w6Lbt2C2PSeZzumQaS24N
M7GCtguQCtJ7oPEkyUJWCLOtrMoIxR6dghuCgGtdp3MYvKKJov8p694m7ibV
ZprO0rxO8rqdJ82sTAjSic1wSFS9EYYE/W+mYVL1REXzLLWwlk9KYDLseCYk
qVqMsYodp1KFuxaTLvUlBGBmQRdQU7jeRJEybM/j/MHexPFF6ekJfBD6FS5p
lc6sS3C01nYgrl1DYD7v93T69L7od6KZR8RmGE86BgNnjs4yr/9LCwpPldy8
OPovvFl5p4y76rZpFlSeiFHPUblR3E0tW3HMVErigJtD1xtNFOBImIJ2c+FO
DtNv6AeMjIMdenUhB8vHsRE1mW9kzWgO7hT57muqLbujNi7zHbnU+6GdRhBM
dB42+1K3Rssd6Dpd2FmXsta6VTobSnovSje+iVGAgqepBctj0udkyHyvId2l
yXpOVe/no2yEtl2rvCSGrl1qDeoidvTZwdAx8e2r5kQKaYIemVvl4OdP+gU8
bLHUUhDKJ+Cgniid1mpQhmEQce5Zbglx2hsHRxm7avlePiuynnZP/CadCeFX
D0hJXj10Q4E5AZ6NHmsXyZ4uboIWx7ekBuB2LFZVdvfkspB5QK40biSJkbRV
Iu3cSU/hnoHcWShnoSw9DWJ5Vjcs3tC+729iBeKoIHq0jLx09hdJFcgAdo/T
GnPJ5JxV5f/dxlvzCZU70a/CclmZDxXfkpItmjrsRMuIQbIl2zk7uUfVt3RF
pncynRI5JaucJHueLAjpm4QH0SEWhWb8TaeUWoeChYa9mYQyG+Mva7rOeqEa
KFFgoMT9FiUrBRL+Ora4qhHm+yO8fO9HL8fcs7v/Hv8hu08cv48oCWviD0dd
Uem6hTqLYC09n+f5JOxjhkwMHzxDvsNKNXbuuu8o3rnOw3iteuRdrwVf9I9a
nu88AX5PxZzllWjWjnk1N6y1dHrlcZAjnIo9lW7o2rxeuMTd5bVv0s/A2XJC
hcigNu1OLoTLJggK8i1/8p6DK06bbzZ/b77lCTHl7qCGsOo2ZeWRNY5Qsrh4
iqZ6R1eX3Rl6zl3CGblhds8OFLt5WSEvCN0Kzv3l5mH/cUvMb1Frp17c7dVl
nOBdzCcQgU2jPn2GLahcMPaZBSi81YU/CMvIcEtZYPDiFbg+CIE3DvN7XDH3
A5kvjXkTnAklBvc6X4n1JF5ZGx9K7+3f3dwKGAfdNnlGouLEsi6MRTVVbZu/
W1bwnFuykwUjetdoMky2X6Nt4e5IciFadHl7NwAyAWhZjE8DBYXHSL8bhN2T
m64/zJnBTq2duN4krppLLAHv72YPABRHvL3TXUMriRo3uHjbQDS/WMzRVe4I
r8vIwaE82exsdn24H5gZ7wNB6DzKAQ2pKdJWneK09U32efMzaVjp3QssvTUs
oXpfsIxF2xvkogrXlxbTHKOWP72Hj12t79N1E7qsHrSSYh9Vm5fTMOtJzPFs
S9MUK11cA67ErulkbjGItGkqt3pttgr8+kEVZWjfiLtFOu+F03ik54EnFDGg
mUez3RFMfuEZC1ytwYr3ggAgUTbkODabBfpUNN4kxW1ho1X5Ju59AGFz+R2w
xvX0CfLAhuZlCTRvl0B+xSamFu5uPUZCXBN++Wtr5tHtAXAb1shjHiAnClsO
Z9CgIDydmpDqi4LbOsUsZjYpumm63paPJqwJ0XHRTH4tGlE478+/hXg49Jxq
nZUyjparYVx8xrmgrAkCXjC++Qxrn6dlEhJeTFEzTltasDgAPqZoro8DvYP6
8RYliaKgsveVnZ7s45T7ynUaT3zJU/UIPlH0v5HRweNcq/qNoFejSrdSmKpS
tPk5D+U17Bv9h1DESiYUOJsyLD9dVo3m2ovn7M14vCCVZTMZTavVuK2ymjuv
C22gB8Ud57YSQUxWhGfiRzW3+N2mKBJtca5JNubQkjGB7Eb4q9IrarN0xXaA
urylFpVWfSZ0hMlOoDg4eKNZ8q5ugT48fIN0twz5MIn8Oo77t9WSB5G8Net2
QEKt016tfV4Tu8m/c58WBiiWDdtNsvY6abjiZOjSiHwMnm+ezrKGa2akm7Dr
gP7uRiz5Ys9ZOFdpYnOVhsqbO70jmGKcLR8YxGaaAzsOjt6QmltyURVpiDgI
ZiSSuBuCl0iimRY/eNYiSq8+JvueOuCRiQwh2Ke9kVoZHRwDvvTEvxJVxw8A
zKbm8ij3E3ro5E38h3Zsd3Mi8+8bsKGU10cirzV14TY3OlEuaHwhDtRqgvRh
4CE9glCxGpoSN7dZ05x/lnLhEk8qsVVmo+j/ANFUDUZb9gAA

-->

</rfc>