draft-eckert-ietf-and-energy-overview-05.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.36 (Ruby 3.1.3) -->


<!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-05" 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="July" day="09"/>

    
    
    

    <abstract>


<?line 211?>

<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>

<t>This document captures work until 12/2022, at which time the
"IAB workshop on Environmental Impact of Internet Applications and Systems"
(https://www.iab.org/activities/workshops/e-impact/) creaeted new interest and
work in the topic.</t>



    </abstract>



  </front>

  <middle>


<?line 227?>

<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>

<t>This document captures work until 12/2022, at which time the
"IAB workshop on Environmental Impact of Internet Applications and Systems"
(https://www.iab.org/activities/workshops/e-impact/) creaeted new interest and
work in the topic.</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="analysis-of-routing-protocol-inefficiencies"><name>Analysis of routing protocol (in)efficiencies</name>

<t>At the beginning of much of the following IETF efforts was an understanding and
analysis that prior protocols for routing and subnet management where not able to
ideally support evolving network and device models: - lower compute performance due to
low energy (batteries, energy recovery), bitrates especially on radio links, and
lower memory footprint.</t>

<t>The two documents from 2008/2009 that capture this analysis/understanding ar
and <xref target="I-D.levis-roll-overview-protocols"/> and <xref target="I-D.ietf-roll-protocols-survey"/>.
The overall challenges also very much related to energy of IPv6 over wireless
are captured in <xref target="I-D.thubert-6man-ipv6-over-wireless"/>, which is ongoing work.</t>

</section>
<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>

<t>05: Added pointers on analysis and limit scope of dociument to 12/2022.</t>

</section>


  </middle>

  <back>



    <references title='Informative References'>



<reference anchor="RFC768">
  <front>
    <title>User Datagram Protocol</title>
    <author fullname="J. Postel" initials="J." surname="Postel"/>
    <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">
  <front>
    <title>Internet Protocol</title>
    <author fullname="J. Postel" initials="J." surname="Postel"/>
    <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">
  <front>
    <title>Transmission Control Protocol</title>
    <author fullname="J. Postel" initials="J." surname="Postel"/>
    <date month="September" year="1981"/>
  </front>
  <seriesInfo name="RFC" value="793"/>
  <seriesInfo name="DOI" value="10.17487/RFC0793"/>
</reference>

<reference anchor="RFC822">
  <front>
    <title>STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES</title>
    <author fullname="D. Crocker" initials="D." surname="Crocker"/>
    <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">
  <front>
    <title>Host extensions for IP multicasting</title>
    <author fullname="S.E. Deering" initials="S.E." surname="Deering"/>
    <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">
  <front>
    <title>OSI IS-IS Intra-domain Routing Protocol</title>
    <author fullname="D. Oran" initials="D." role="editor" surname="Oran"/>
    <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">
  <front>
    <title>UPS Management Information Base</title>
    <author fullname="J. Case" initials="J." role="editor" surname="Case"/>
    <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">
  <front>
    <title>Hypertext Markup Language - 2.0</title>
    <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
    <author fullname="D. Connolly" initials="D." surname="Connolly"/>
    <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">
  <front>
    <title>Internet Protocol, Version 6 (IPv6) Specification</title>
    <author fullname="S. Deering" initials="S." surname="Deering"/>
    <author fullname="R. Hinden" initials="R." surname="Hinden"/>
    <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">
  <front>
    <title>IMAP4 ACL extension</title>
    <author fullname="J. Myers" initials="J." surname="Myers"/>
    <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">
  <front>
    <title>Specification of Guaranteed Quality of Service</title>
    <author fullname="S. Shenker" initials="S." surname="Shenker"/>
    <author fullname="C. Partridge" initials="C." surname="Partridge"/>
    <author fullname="R. Guerin" initials="R." surname="Guerin"/>
    <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">
  <front>
    <title>The TLS Protocol Version 1.0</title>
    <author fullname="T. Dierks" initials="T." surname="Dierks"/>
    <author fullname="C. Allen" initials="C." surname="Allen"/>
    <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">
  <front>
    <title>OSPF Version 2</title>
    <author fullname="J. Moy" initials="J." surname="Moy"/>
    <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">
  <front>
    <title>Internet Protocol, Version 6 (IPv6) Specification</title>
    <author fullname="S. Deering" initials="S." surname="Deering"/>
    <author fullname="R. Hinden" initials="R." surname="Hinden"/>
    <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">
  <front>
    <title>An Architecture for Differentiated Services</title>
    <author fullname="S. Blake" initials="S." surname="Blake"/>
    <author fullname="D. Black" initials="D." surname="Black"/>
    <author fullname="M. Carlson" initials="M." surname="Carlson"/>
    <author fullname="E. Davies" initials="E." surname="Davies"/>
    <author fullname="Z. Wang" initials="Z." surname="Wang"/>
    <author fullname="W. Weiss" initials="W." surname="Weiss"/>
    <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">
  <front>
    <title>SIP: Session Initiation Protocol</title>
    <author fullname="M. Handley" initials="M." surname="Handley"/>
    <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
    <author fullname="E. Schooler" initials="E." surname="Schooler"/>
    <author fullname="J. Rosenberg" initials="J." surname="Rosenberg"/>
    <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">
  <front>
    <title>Internet Message Format</title>
    <author fullname="P. Resnick" initials="P." role="editor" surname="Resnick"/>
    <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 "electronic mail" messages. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="2822"/>
  <seriesInfo name="DOI" value="10.17487/RFC2822"/>
</reference>

<reference anchor="RFC2854">
  <front>
    <title>The 'text/html' Media Type</title>
    <author fullname="D. Connolly" initials="D." surname="Connolly"/>
    <author fullname="L. Masinter" initials="L." surname="Masinter"/>
    <date month="June" year="2000"/>
    <abstract>
      <t>This document summarizes the history of HTML development, and defines the "text/html" 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">
  <front>
    <title>SIP: Session Initiation Protocol</title>
    <author fullname="J. Rosenberg" initials="J." surname="Rosenberg"/>
    <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
    <author fullname="G. Camarillo" initials="G." surname="Camarillo"/>
    <author fullname="A. Johnston" initials="A." surname="Johnston"/>
    <author fullname="J. Peterson" initials="J." surname="Peterson"/>
    <author fullname="R. Sparks" initials="R." surname="Sparks"/>
    <author fullname="M. Handley" initials="M." surname="Handley"/>
    <author fullname="E. Schooler" initials="E." surname="Schooler"/>
    <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">
  <front>
    <title>Entity Sensor Management Information Base</title>
    <author fullname="A. Bierman" initials="A." surname="Bierman"/>
    <author fullname="D. Romascanu" initials="D." surname="Romascanu"/>
    <author fullname="K.C. Norseth" initials="K.C." surname="Norseth"/>
    <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">
  <front>
    <title>RTP: A Transport Protocol for Real-Time Applications</title>
    <author fullname="H. Schulzrinne" initials="H." surname="Schulzrinne"/>
    <author fullname="S. Casner" initials="S." surname="Casner"/>
    <author fullname="R. Frederick" initials="R." surname="Frederick"/>
    <author fullname="V. Jacobson" initials="V." surname="Jacobson"/>
    <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">
  <front>
    <title>Power Ethernet MIB</title>
    <author fullname="A. Berger" initials="A." surname="Berger"/>
    <author fullname="D. Romascanu" initials="D." surname="Romascanu"/>
    <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">
  <front>
    <title>UDP Encapsulation of IPsec ESP Packets</title>
    <author fullname="A. Huttunen" initials="A." surname="Huttunen"/>
    <author fullname="B. Swander" initials="B." surname="Swander"/>
    <author fullname="V. Volpe" initials="V." surname="Volpe"/>
    <author fullname="L. DiBurro" initials="L." surname="DiBurro"/>
    <author fullname="M. Stenberg" initials="M." surname="Stenberg"/>
    <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">
  <front>
    <title>Network News Transfer Protocol (NNTP)</title>
    <author fullname="C. Feather" initials="C." surname="Feather"/>
    <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">
  <front>
    <title>Entity State MIB</title>
    <author fullname="S. Chisholm" initials="S." surname="Chisholm"/>
    <author fullname="D. Perkins" initials="D." surname="Perkins"/>
    <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">
  <front>
    <title>A Border Gateway Protocol 4 (BGP-4)</title>
    <author fullname="Y. Rekhter" initials="Y." role="editor" surname="Rekhter"/>
    <author fullname="T. Li" initials="T." role="editor" surname="Li"/>
    <author fullname="S. Hares" initials="S." role="editor" surname="Hares"/>
    <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 "class" 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">
  <front>
    <title>The Transport Layer Security (TLS) Protocol Version 1.1</title>
    <author fullname="T. Dierks" initials="T." surname="Dierks"/>
    <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
    <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">
  <front>
    <title>Source-Specific Multicast for IP</title>
    <author fullname="H. Holbrook" initials="H." surname="Holbrook"/>
    <author fullname="B. Cain" initials="B." surname="Cain"/>
    <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">
  <front>
    <title>Neighbor Discovery for IP version 6 (IPv6)</title>
    <author fullname="T. Narten" initials="T." surname="Narten"/>
    <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
    <author fullname="W. Simpson" initials="W." surname="Simpson"/>
    <author fullname="H. Soliman" initials="H." surname="Soliman"/>
    <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">
  <front>
    <title>Transmission of IPv6 Packets over IEEE 802.15.4 Networks</title>
    <author fullname="G. Montenegro" initials="G." surname="Montenegro"/>
    <author fullname="N. Kushalnagar" initials="N." surname="Kushalnagar"/>
    <author fullname="J. Hui" initials="J." surname="Hui"/>
    <author fullname="D. Culler" initials="D." surname="Culler"/>
    <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">
  <front>
    <title>Internet Security Glossary, Version 2</title>
    <author fullname="R. Shirey" initials="R." surname="Shirey"/>
    <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">
  <front>
    <title>The Transport Layer Security (TLS) Protocol Version 1.2</title>
    <author fullname="T. Dierks" initials="T." surname="Dierks"/>
    <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
    <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">
  <front>
    <title>Internet Message Format</title>
    <author fullname="P. Resnick" initials="P." role="editor" surname="Resnick"/>
    <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 "electronic mail" messages. This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", 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">
  <front>
    <title>Routing Requirements for Urban Low-Power and Lossy Networks</title>
    <author fullname="M. Dohler" initials="M." role="editor" surname="Dohler"/>
    <author fullname="T. Watteyne" initials="T." role="editor" surname="Watteyne"/>
    <author fullname="T. Winter" initials="T." role="editor" surname="Winter"/>
    <author fullname="D. Barthel" initials="D." role="editor" surname="Barthel"/>
    <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">
  <front>
    <title>Industrial Routing Requirements in Low-Power and Lossy Networks</title>
    <author fullname="K. Pister" initials="K." role="editor" surname="Pister"/>
    <author fullname="P. Thubert" initials="P." role="editor" surname="Thubert"/>
    <author fullname="S. Dwars" initials="S." surname="Dwars"/>
    <author fullname="T. Phinney" initials="T." surname="Phinney"/>
    <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">
  <front>
    <title>Home Automation Routing Requirements in Low-Power and Lossy Networks</title>
    <author fullname="A. Brandt" initials="A." surname="Brandt"/>
    <author fullname="J. Buron" initials="J." surname="Buron"/>
    <author fullname="G. Porcu" initials="G." surname="Porcu"/>
    <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">
  <front>
    <title>Building Automation Routing Requirements in Low-Power and Lossy Networks</title>
    <author fullname="J. Martocci" initials="J." role="editor" surname="Martocci"/>
    <author fullname="P. De Mil" initials="P." surname="De Mil"/>
    <author fullname="N. Riou" initials="N." surname="Riou"/>
    <author fullname="W. Vermeylen" initials="W." surname="Vermeylen"/>
    <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">
  <front>
    <title>Network Time Protocol Version 4: Protocol and Algorithms Specification</title>
    <author fullname="D. Mills" initials="D." surname="Mills"/>
    <author fullname="J. Martin" initials="J." role="editor" surname="Martin"/>
    <author fullname="J. Burbank" initials="J." surname="Burbank"/>
    <author fullname="W. Kasch" initials="W." surname="Kasch"/>
    <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">
  <front>
    <title>The Trickle Algorithm</title>
    <author fullname="P. Levis" initials="P." surname="Levis"/>
    <author fullname="T. Clausen" initials="T." surname="Clausen"/>
    <author fullname="J. Hui" initials="J." surname="Hui"/>
    <author fullname="O. Gnawali" initials="O." surname="Gnawali"/>
    <author fullname="J. Ko" initials="J." surname="Ko"/>
    <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">
  <front>
    <title>Internet Protocols for the Smart Grid</title>
    <author fullname="F. Baker" initials="F." surname="Baker"/>
    <author fullname="D. Meyer" initials="D." surname="Meyer"/>
    <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">
  <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"/>
    <author fullname="P. Thubert" initials="P." surname="Thubert"/>
    <date month="September" year="2011"/>
    <abstract>
      <t>This document updates RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks". 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">
  <front>
    <title>RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks</title>
    <author fullname="T. Winter" initials="T." role="editor" surname="Winter"/>
    <author fullname="P. Thubert" initials="P." role="editor" surname="Thubert"/>
    <author fullname="A. Brandt" initials="A." surname="Brandt"/>
    <author fullname="J. Hui" initials="J." surname="Hui"/>
    <author fullname="R. Kelsey" initials="R." surname="Kelsey"/>
    <author fullname="P. Levis" initials="P." surname="Levis"/>
    <author fullname="K. Pister" initials="K." surname="Pister"/>
    <author fullname="R. Struik" initials="R." surname="Struik"/>
    <author fullname="JP. Vasseur" initials="JP." surname="Vasseur"/>
    <author fullname="R. Alexander" initials="R." surname="Alexander"/>
    <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">
  <front>
    <title>Constrained RESTful Environments (CoRE) Link Format</title>
    <author fullname="Z. Shelby" initials="Z." surname="Shelby"/>
    <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. "RESTful" 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">
  <front>
    <title>DNS-Based Service Discovery</title>
    <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
    <author fullname="M. Krochmal" initials="M." surname="Krochmal"/>
    <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">
  <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"/>
    <author fullname="S. Chakrabarti" initials="S." surname="Chakrabarti"/>
    <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
    <author fullname="C. Bormann" initials="C." surname="Bormann"/>
    <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">
  <front>
    <title>Port Control Protocol (PCP)</title>
    <author fullname="D. Wing" initials="D." role="editor" surname="Wing"/>
    <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
    <author fullname="M. Boucadair" initials="M." surname="Boucadair"/>
    <author fullname="R. Penno" initials="R." surname="Penno"/>
    <author fullname="P. Selkirk" initials="P." surname="Selkirk"/>
    <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">
  <front>
    <title>Entity MIB (Version 4)</title>
    <author fullname="A. Bierman" initials="A." surname="Bierman"/>
    <author fullname="D. Romascanu" initials="D." surname="Romascanu"/>
    <author fullname="J. Quittek" initials="J." surname="Quittek"/>
    <author fullname="M. Chandramouli" initials="M." surname="Chandramouli"/>
    <date month="May" year="2013"/>
    <abstract>
      <t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single Simple Network Management Protocol (SNMP) agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of the Entity MIB module published as RFC 4133.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6933"/>
  <seriesInfo name="DOI" value="10.17487/RFC6933"/>
</reference>

<reference anchor="RFC6988">
  <front>
    <title>Requirements for Energy Management</title>
    <author fullname="J. Quittek" initials="J." role="editor" surname="Quittek"/>
    <author fullname="M. Chandramouli" initials="M." surname="Chandramouli"/>
    <author fullname="R. Winter" initials="R." surname="Winter"/>
    <author fullname="T. Dietz" initials="T." surname="Dietz"/>
    <author fullname="B. Claise" initials="B." surname="Claise"/>
    <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">
  <front>
    <title>Enrollment over Secure Transport</title>
    <author fullname="M. Pritikin" initials="M." role="editor" surname="Pritikin"/>
    <author fullname="P. Yee" initials="P." role="editor" surname="Yee"/>
    <author fullname="D. Harkins" initials="D." role="editor" surname="Harkins"/>
    <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">
  <front>
    <title>Terms Used in Routing for Low-Power and Lossy Networks</title>
    <author fullname="JP. Vasseur" initials="JP." surname="Vasseur"/>
    <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">
  <front>
    <title>Energy Management Framework</title>
    <author fullname="J. Parello" initials="J." surname="Parello"/>
    <author fullname="B. Claise" initials="B." surname="Claise"/>
    <author fullname="B. Schoening" initials="B." surname="Schoening"/>
    <author fullname="J. Quittek" initials="J." surname="Quittek"/>
    <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">
  <front>
    <title>Monitoring and Control MIB for Power and Energy</title>
    <author fullname="M. Chandramouli" initials="M." surname="Chandramouli"/>
    <author fullname="B. Claise" initials="B." surname="Claise"/>
    <author fullname="B. Schoening" initials="B." surname="Schoening"/>
    <author fullname="J. Quittek" initials="J." surname="Quittek"/>
    <author fullname="T. Dietz" initials="T." surname="Dietz"/>
    <date month="March" year="2015"/>
    <abstract>
      <t>This document defines a subset of the Management Information Base (MIB) for power and energy monitoring of devices.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7460"/>
  <seriesInfo name="DOI" value="10.17487/RFC7460"/>
</reference>

<reference anchor="RFC7461">
  <front>
    <title>Energy Object Context MIB</title>
    <author fullname="J. Parello" initials="J." surname="Parello"/>
    <author fullname="B. Claise" initials="B." surname="Claise"/>
    <author fullname="M. Chandramouli" initials="M." surname="Chandramouli"/>
    <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">
  <front>
    <title>Definition of Managed Objects for Battery Monitoring</title>
    <author fullname="J. Quittek" initials="J." surname="Quittek"/>
    <author fullname="R. Winter" initials="R." surname="Winter"/>
    <author fullname="T. Dietz" initials="T." surname="Dietz"/>
    <date month="July" year="2015"/>
    <abstract>
      <t>This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines managed objects that provide information on the status of batteries in managed devices.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7577"/>
  <seriesInfo name="DOI" value="10.17487/RFC7577"/>
</reference>

<reference anchor="RFC7603">
  <front>
    <title>Energy Management (EMAN) Applicability Statement</title>
    <author fullname="B. Schoening" initials="B." surname="Schoening"/>
    <author fullname="M. Chandramouli" initials="M." surname="Chandramouli"/>
    <author fullname="B. Nordman" initials="B." surname="Nordman"/>
    <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">
  <front>
    <title>Observing Resources in the Constrained Application Protocol (CoAP)</title>
    <author fullname="K. Hartke" initials="K." surname="Hartke"/>
    <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 "observe" 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">
  <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"/>
    <author fullname="E. Baccelli" initials="E." surname="Baccelli"/>
    <author fullname="R. Cragie" initials="R." surname="Cragie"/>
    <author fullname="P. van der Stok" initials="P." surname="van der Stok"/>
    <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">
  <front>
    <title>Reducing Energy Consumption of Router Advertisements</title>
    <author fullname="A. Yourtchenko" initials="A." surname="Yourtchenko"/>
    <author fullname="L. Colitti" initials="L." surname="Colitti"/>
    <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">
  <front>
    <title>An IPv6 Profile for 3GPP Mobile Devices</title>
    <author fullname="D. Binet" initials="D." surname="Binet"/>
    <author fullname="M. Boucadair" initials="M." surname="Boucadair"/>
    <author fullname="A. Vizdal" initials="A." surname="Vizdal"/>
    <author fullname="G. Chen" initials="G." surname="Chen"/>
    <author fullname="N. Heatley" initials="N." surname="Heatley"/>
    <author fullname="R. Chandler" initials="R." surname="Chandler"/>
    <author fullname="D. Michaud" initials="D." surname="Michaud"/>
    <author fullname="D. Lopez" initials="D." surname="Lopez"/>
    <author fullname="W. Haeffner" initials="W." surname="Haeffner"/>
    <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 "IPv6 for Third Generation Partnership Project (3GPP) Cellular Hosts" (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">
  <front>
    <title>Internet Protocol, Version 6 (IPv6) Specification</title>
    <author fullname="S. Deering" initials="S." surname="Deering"/>
    <author fullname="R. Hinden" initials="R." surname="Hinden"/>
    <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">
  <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"/>
    <author fullname="J. Hui" initials="J." surname="Hui"/>
    <author fullname="D. Popa" initials="D." surname="Popa"/>
    <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">
  <front>
    <title>Energy-Efficient Features of Internet of Things Protocols</title>
    <author fullname="C. Gomez" initials="C." surname="Gomez"/>
    <author fullname="M. Kovatsch" initials="M." surname="Kovatsch"/>
    <author fullname="H. Tian" initials="H." surname="Tian"/>
    <author fullname="Z. Cao" initials="Z." role="editor" surname="Cao"/>
    <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">
  <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"/>
    <author fullname="M. Behringer" initials="M." surname="Behringer"/>
    <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">
  <front>
    <title>Sensor Measurement Lists (SenML)</title>
    <author fullname="C. Jennings" initials="C." surname="Jennings"/>
    <author fullname="Z. Shelby" initials="Z." surname="Shelby"/>
    <author fullname="J. Arkko" initials="J." surname="Arkko"/>
    <author fullname="A. Keranen" initials="A." surname="Keranen"/>
    <author fullname="C. Bormann" initials="C." surname="Bormann"/>
    <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">
  <front>
    <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
    <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
    <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">
  <front>
    <title>YANG Data Model for the Precision Time Protocol (PTP)</title>
    <author fullname="Y. Jiang" initials="Y." role="editor" surname="Jiang"/>
    <author fullname="X. Liu" initials="X." surname="Liu"/>
    <author fullname="J. Xu" initials="J." surname="Xu"/>
    <author fullname="R. Cummings" initials="R." role="editor" surname="Cummings"/>
    <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">
  <front>
    <title>Object Security for Constrained RESTful Environments (OSCORE)</title>
    <author fullname="G. Selander" initials="G." surname="Selander"/>
    <author fullname="J. Mattsson" initials="J." surname="Mattsson"/>
    <author fullname="F. Palombini" initials="F." surname="Palombini"/>
    <author fullname="L. Seitz" initials="L." surname="Seitz"/>
    <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">
  <front>
    <title>SCHC: Generic Framework for Static Context Header Compression and Fragmentation</title>
    <author fullname="A. Minaburo" initials="A." surname="Minaburo"/>
    <author fullname="L. Toutain" initials="L." surname="Toutain"/>
    <author fullname="C. Gomez" initials="C." surname="Gomez"/>
    <author fullname="D. Barthel" initials="D." surname="Barthel"/>
    <author fullname="JC. Zuniga" initials="JC." surname="Zuniga"/>
    <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">
  <front>
    <title>Deprecating Any-Source Multicast (ASM) for Interdomain Multicast</title>
    <author fullname="M. Abrahamsson" initials="M." surname="Abrahamsson"/>
    <author fullname="T. Chown" initials="T." surname="Chown"/>
    <author fullname="L. Giuliano" initials="L." surname="Giuliano"/>
    <author fullname="T. Eckert" initials="T." surname="Eckert"/>
    <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">
  <front>
    <title>Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)</title>
    <author fullname="A. Minaburo" initials="A." surname="Minaburo"/>
    <author fullname="L. Toutain" initials="L." surname="Toutain"/>
    <author fullname="R. Andreasen" initials="R." surname="Andreasen"/>
    <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">
  <front>
    <title>An Autonomic Control Plane (ACP)</title>
    <author fullname="T. Eckert" initials="T." role="editor" surname="Eckert"/>
    <author fullname="M. Behringer" initials="M." role="editor" surname="Behringer"/>
    <author fullname="S. Bjarnason" initials="S." surname="Bjarnason"/>
    <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 "Autonomic Control Plane", with the primary use as a control plane for autonomic functions. It also serves as a "virtual out-of-band channel" 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">
  <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"/>
    <author fullname="M. Richardson" initials="M." surname="Richardson"/>
    <author fullname="P. Thubert" initials="P." surname="Thubert"/>
    <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">
  <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"/>
    <author fullname="M. Richardson" initials="M." surname="Richardson"/>
    <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">
  <front>
    <title>Static Context Header Compression and Fragmentation (SCHC) over LoRaWAN</title>
    <author fullname="O. Gimenez" initials="O." role="editor" surname="Gimenez"/>
    <author fullname="I. Petrov" initials="I." role="editor" surname="Petrov"/>
    <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">
  <front>
    <title>Multicast Considerations over IEEE 802 Wireless Media</title>
    <author fullname="C. Perkins" initials="C." surname="Perkins"/>
    <author fullname="M. McBride" initials="M." surname="McBride"/>
    <author fullname="D. Stanley" initials="D." surname="Stanley"/>
    <author fullname="W. Kumari" initials="W." surname="Kumari"/>
    <author fullname="JC. Zúñiga" initials="JC." surname="Zúñiga"/>
    <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">
  <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"/>
    <author fullname="P. Kampanakis" initials="P." surname="Kampanakis"/>
    <author fullname="M. Richardson" initials="M." surname="Richardson"/>
    <author fullname="S. Raza" initials="S." surname="Raza"/>
    <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">
  <front>
    <title>Constrained RESTful Environments (CoRE) Resource Directory</title>
    <author fullname="C. Amsüss" initials="C." role="editor" surname="Amsüss"/>
    <author fullname="Z. Shelby" initials="Z." surname="Shelby"/>
    <author fullname="M. Koster" initials="M." surname="Koster"/>
    <author fullname="C. Bormann" initials="C." surname="Bormann"/>
    <author fullname="P. van der Stok" initials="P." surname="van der Stok"/>
    <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">
  <front>
    <title>Building Power-Efficient Constrained Application Protocol (CoAP) Devices for Cellular Networks</title>
    <author fullname="J. Arkko" initials="J." surname="Arkko"/>
    <author fullname="A. Eriksson" initials="A." surname="Eriksson"/>
    <author fullname="A. Keränen" initials="A." surname="Keränen"/>
    <date month="May" year="2022"/>
    <abstract>
      <t>This memo discusses the use of the Constrained Application Protocol (CoAP) in building sensors and other devices that employ cellular networks as a communications medium. Building communicating devices that employ these networks is obviously well known, but this memo focuses specifically on techniques necessary to minimize power consumption.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9178"/>
  <seriesInfo name="DOI" value="10.17487/RFC9178"/>
</reference>


<reference anchor="I-D.ajunior-energy-awareness-00">
   <front>
      <title>Energy-awareness metrics global applicability guidelines</title>
      <author fullname="Antonio Junior" initials="A." surname="Junior">
         <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">
   <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">
   <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">
   <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">
   <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&#x27;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">
   <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">
   <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">
   <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 &#x27;proxies&#x27; 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&#x27;s
   request upstream.

   The Publish Option and the &#x27;proxies&#x27; 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">
   <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">
   <front>
      <title>A publish-subscribe architecture for the Constrained Application Protocol (CoAP)</title>
      <author fullname="Michael Koster" initials="M." surname="Koster">
         <organization>Unaffiliated</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="13" month="March" year="2023"/>
      <abstract>
	 <t>   This document describes a publish-subscribe architecture for CoAP
   that extends the capabilities of CoAP for supporting nodes with long
   breaks in connectivity and/or up-time.  The Constrained Application
   Protocol (CoAP) is used by CoAP clients both to publish and to
   subscribe via a known topic resource.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-core-coap-pubsub-12"/>
   
</reference>


<reference anchor="I-D.ietf-dnssd-srp">
   <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="7" month="July" 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 IEEE 802.11
   (Wi-Fi) and IEEE 802.15.4 networks.  DNS-SD Service registration uses
   public keys and SIG(0) to allow services to defend their
   registrations.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dnssd-srp-21"/>
   
</reference>


<reference anchor="I-D.jennings-energy-pricing">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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">
   <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&#x27;s networks has long evolved beyond
   ensuring mere reachability of the receiving endpoint.  Instead, other
   &#x27;purposes&#x27; 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">
   <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">
   <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="Meiling Chen" initials="M." surname="Chen">
         <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="5" month="July" 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-05"/>
   
</reference>


<reference anchor="I-D.ietf-tcpm-rfc793bis">
   <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">
   <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="I-D.ietf-roll-protocols-survey">
   <front>
      <title>Overview of Existing Routing Protocols for Low Power and Lossy Networks</title>
      <author fullname="Arsalan Tavakoli" initials="A." surname="Tavakoli">
         <organization>UC Berkeley</organization>
      </author>
      <author fullname="Stephen Dawson-Haggerty" initials="S." surname="Dawson-Haggerty">
         <organization>UC Berkeley</organization>
      </author>
      <date day="24" month="April" year="2009"/>
      <abstract>
	 <t>   Low-power wireless devices, such as sensors, actuators and smart    objects, present difficult constraints: very limited memory, little
   processing power, and long sleep periods.  As most of these devices
   are battery-powered, energy efficiency is critically important.
   Wireless link qualities can vary significantly over time, requiring
   protocols to make agile decisions yet minimize topology change energy
   costs.  Routing over such low power and lossy networks introduces
   requirements that existing routing protocols may not fully address.
   Using existing application requirements documents, this document
   derives a minimal and not exhaustive set of criteria for routing in
   low-power and lossy networks.  It provides a brief survey of the
   strengths and weaknesses of existing protocols with respect to these
   criteria.  From this survey it examines whether existing and mature
   IETF protocols can be used without modification in these networks, or
   whether further work is necessary.  It concludes that no existing
   IETF protocol meets the requirements of this domain.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-roll-protocols-survey-07"/>
   
</reference>


<reference anchor="I-D.levis-roll-overview-protocols">
   <front>
      <title>Overview of Existing Routing Protocols for Low Power and Lossy Networks</title>
      <author fullname="JP Vasseur" initials="V." surname="Jp">
         <organization>Cisco Systems</organization>
      </author>
      <date day="12" month="February" year="2008"/>
      <abstract>
	 <t>Networks of low power wireless devices introduce novel IP routing
   issues.  Low-power wireless devices, such as sensors, actuators and
   smart objects, have difficult constraints: very limited memory,
   little processing power, and long sleep periods.  As most of these
   devices are battery-powered, energy efficiency is critically
important.  Wireless link qualities can vary significantly over time,
   requiring protocols to make agile decisions yet minimize topology
   change energy costs.  Such low power and lossy networks (L2Ns) have
   routing requirements that existing mesh protocols only partially
   address.  This document provides a brief survey of the strengths and
   weaknesses of existing protocols with respect to L2Ns.  It provides
   guidance on how lessons from existing and prior efforts can be
   leveraged in future protocol design.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-levis-roll-overview-protocols-00"/>
   
</reference>


<reference anchor="I-D.thubert-6man-ipv6-over-wireless">
   <front>
      <title>Architecture and Framework for IPv6 over Non-Broadcast Access</title>
      <author fullname="Pascal Thubert" initials="P." surname="Thubert">
         <organization>Cisco Systems, Inc</organization>
      </author>
      <author fullname="Michael Richardson" initials="M." surname="Richardson">
         <organization>Sandelman Software Works</organization>
      </author>
      <date day="8" month="March" year="2023"/>
      <abstract>
	 <t>   This document presents an architecture for IPv6 access networks that
   decouples the network-layer concepts of Links, Interface, and Subnets
   from the link-layer concepts of links, ports, and broadcast domains,
   and limits the reliance on link-layer broadcasts.  This architecture
   is suitable for IPv6 over any network, including non-broadcast
   networks.  A study of the issues with ND-Classic over wireless media
   is presented, and a framework to solve those issues within the new
   architecture is proposed.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-thubert-6man-ipv6-over-wireless-15"/>
   
</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:
H4sIAAAAAAAAA+W9W3PbyJcn+I5PgWDF7JIxBKmbJdkv07Iku9Rt2VpLLk/v
TIcDJEESZRBgA6BklsPffc/vXDITpFTVsRH7tBM9/6JFMJF58tyvSZJE02qW
l4s38aadJ+dR1OZtkb2JL8r402NWP+bZU1zN4+syqxfbpM6KtM1m8fV8XtVt
/JS3y7yM22UW31w/vIujdDKps8c38i/5jVsmmlXTMl3R2rM6nbdJNv2e1W2S
Z/TetJwlmbyi0seTg1dR09ZZunoT5+UsW2f0P2UbTWkDi6re4q/zKsrX9Zu4
rTdNe3Rw8PrgKKIf0Wrf0qIq6VXbrInW+ZsojuO2msq/5TOt2C7fxK/wz4YO
U2fzxn3fbFedf0+r1Ypern+I0k27rGqsmuBb/D852UOV1UXWNPE1H86+rCuA
NJvlbVXb36qaYP5u027q7CnL44dsuiyrolrkWRN/ub+wxwCCrH0THx0dHcSX
tIc6LeLrH+ua3vKUbu2xad4SRO7Tsk3jyyKtU/dFNaNXX17Er18dvDrwf93Q
SvSL4E3ZKs0LgmWb/cu0Gc3TzWiW7Z/wtlrSf2fx22ozTWdpXv/jGT/VabnI
uhv9nJWlQNbv8fjVwcH+Bt/Rr6fZzh5XsonRxDbxLxW/ZET3tL/lu7SZEtAe
lptJcCe8t8u8mVbx/bZps1UzjG/K6WgX8Cev4ouiyLJ4RhfzqV7R/ybx27tD
Qrdh/HaTF6Ce+GrnIqr1Mk+JiNp8XRX5zkkPTo9encS3n768v/l4/w8nXi8Z
j3v//fg4Pnl9Fh8dx0en8fFJbwckhMx8vH+Z4kgMiH1I/Gs2nxOmESJvPIYw
ID7+cXN1c/FfQI8/aQkisHYEuv2XBf4oLwM11qu0zR8zEMbnd5dnp+f26fWh
+3Ssn86PjvTT4eGh/3jiPp4e2c8Pz09P3cdzW+Do4Nz+enTkVjg6OnF/PXYr
0B8P3MezV/bx1YlbzG/n6PzViX48Pjq1jR+fHNuzx69e2WLHp0fugdcn5+7j
2Zl+PDlyQDg5OrNnT47dJmlj7tlz97aT1ycn/uNr/fjKn+3Vsdvvq1fuxa9O
z2yTr86P3LPnp/aKV68P7PCnRwen7uPZkft47j76Y56evnYfz06P3UcHydPz
c3vF6WsHqNPX5w4DDo5thbPDA3vF2bHb5Jm/Ifro0OWVg+TZ6cGx+3jiHjhz
bzs7c6c4O3cwOyc6tY8Hx/a28+NXR+6ju6HzkyP/0YH6/JU7Jl2QQ9+zI7uh
8/ND98C5/+vr1/bx9cHBuft4eOA/2ileHx6+dh/dbb4+PDv1H+mv9Pk3klWr
LM7quqpJAMbf63Q1q57K+GmZlXFZtfGmAT9KDg7iZVYzKd4kV6P0z02ZV7UJ
2fQprelj0ySAjj4zLdK8yZJ19ZTVySot00UGoZek9XRp60xA42WZTKs6S+oq
na3SdSI4xUukxEmLIi1zeSItlB3wl8uUtjtJ6zZPyqqmn9bfOxtKypk9+9eS
+HmyIBZMgqK1v86rpiEOI2uvqhKyJqnWbV6Vzz6y3kyI+S53HlnkKXGsXA/R
EG9fb3ceYaWEv55WdEBap9lMOl/OyqaZJU29tr/+STslyDd2onWdT6FX6dcE
NZLcyWT1tFAIbxoCsPv6z4ZuMi2TdUrnTfKypSfSRh9tqk093X+2bhdYLV/J
Y/Z99T1dVW2VTKfpap2s8llV58litS5obz/arGzooKTJ/WdjP6jTJZYLwVGS
oGqSWZU80a1k2exvHl3X1aTIVgnpXS0jzMvPum8yEiGp7j9Lpw6Izeavzfc8
oVtvsMNNXmeid+n3jznBUG4/Bwng5T+2L37bkCrp4fIElCI1pXCqJt35Kv8r
xc0nzXRJ73LPyg3ogyTz6DJBC/znACMFT+XSXgSEU1OSvCbUaWYlK7wNiVRS
EKa0p00boMo6I9WjmW6Sx9Nq3ST5+vFU8YA+nthTxRLYIq/sAishAiAizFtc
XdvB2na6XiX1fEpieJI7qNJVr2iLWbr5IW9bgY6Tp3yeP4ervBLDkV5PmnRF
iEUKxWPmLqLIHvNGHnHqvHvWHlKFJTkFkvBr8Sy9lYwM4kzClu4/HR68On+d
3GfTikB2Teqlkikp8WKp9G5wJ6QO5nRs0tyhy5GCHz/35xz6M6E1qS1lDLBn
YJZOdanKOPsxxZVmse03pu+IqWbgtrQH4qNTfhC2D1s+nQfpH485a4T4ip4v
M34cJyKONcvij1n7VNXf43vAZZrFfTpjfH5ydjwQlc7bFnGgv6kCx2cqeaek
0X6qF8RpBX/57fcwfdJ6pn8b8q+JCMimwBl1UYLY/ade/AbQHd9cX8YM4jck
KI+GsQA6VkAP44/V4yjGVyPcxx+kdR2edMF/Wa3WaZ03tAcyFHFsoZphPE3r
Cf2V9kQPrwCOpm3wEIEoI5CVc5JQJbgkP0MceZ3VWGdFmjd46TMQ2QPJFfgu
aebl4oUHHvIVWS1V3bzw/R/5n+k2vs8fU+aq/O2McIZsLjrrCyC8+nTzhuA2
Ojw4PB3/CQ2Y/m+EH4wIVGSJCojSegEbYtm26+bNePz09DRqwEimhJY1YQZ+
ONa/jCEYp0U2Xuf5+J5WInWFFJ0TsopIVwP0P17c391cfvh0+W+dG3gAbO+3
5XRZVw4d1Cy/LugtJIniO9CxWjp/C1WFCr/r+aUf0uZ7/K6q1UgRWN1CSwDE
zl48eZk263xE5sa4Id7UjGcZGZlFO57nRB1jsrcZG7Jvs2q6YUY2bpt2/i3T
I3xjVvRNKPlbna3JaP+2Lsvi29Hp8fHhtxV28A07+HYwWs/mgNjbT18+Xl1f
fftw8XD98fLfu4h7QQhaTDfFpmHiKZUwZ1mRbkfxzciRKu2A9wOgEp4XDIbn
cHMfjPHn0YdRfFlv/gpgdfj69eHf4RUj1uHB6/Hh+egUHxzdXl9f92jnD2Qi
NikzFqKnktiCZ2APy6yqt3E//qMqNtjC8RkZtk2zwYuVx+zeTp5l2Y91QZJz
hI98R3YLY9lBlCRJnE7IKqb3RtHDkmhula0q5XhkFadE/4HHiCFH9IydZbN4
so2FPa6rhv4pnqPIeY7MsUR8W7gHOMKYfsEq4JvYKazD2GumQzDYlsQMLR3V
2WwjnJleTn9vNqu1/dMYErhMsyH5nJfpJCcJSa+hW23D19uWRnpIgwPdfPxU
5y0pUHhsmRVrepYOE2/Kebqi1dLahELa8vGH8WTTxhHrDFmD9YFAtG0lzmW1
zrBWDb07XhH4Y3sWj2Qdn1uE+34krkyg3vG7DelQRHw4Clxk+XwLlrpI143y
1UdaMV+k4KkR4e9GEIeeT9e4kRoicu+803QN51QjN7mhdYv48Gh8dHBEYgIn
XOb0UmbstJGod3Pxlh9t6FhAyuvyMSeugbVIVt2QkJi2uIwbVaHii/W6yKep
boY2qn6YXtQP2UaeThgh/fnH9ppmnCU5LzwexNM6SzMAuSQEdHCkdSM+gMKr
rdb5dCToTKrxrMii6Dfsqa4Uf3bhQIhErCX/yyDB17sk4E0IMz1G0z0CwR3C
RzuXNL75TEgV3zGX3xRpXRBCEupNQTSNfwTmHt/NE+lw9N/o5v5a/0Yg8o+x
/TcjiMw2BF4yT1Z5A81evKtNJFgIG5DIln5albQp8DmSc3lFPI/A1QDy/Wy0
GA3jIp1+x/WsKpx6syLkhX0XN1PC0gFjB69F/99WIH5OrLkhPH6K03hBpl4p
IBKUbQJq5t3QbyMyMmmb85yJgb5Xdy7d6iiO7xmNY3tGcINugpaCaZsS8RFR
Y1kFe5TGzPkKYmk/qrJabYXm6P42jZ4XF9Ck3zMcbpLREjWOPlMGMIo6nlcc
j0xGoNGmnNGjqe1Qz0Ar49S8u6LYxk2+KPkfYEcR3pf9ILOryIZgeRPWL1ek
95A8IJPkaRSyzk2z4TVY9DXGfNpwP5POG+IMaANswPXbPuTGY6ARK32EO9Xa
ISWWJIogWhjF/Gr6P2abKY5UqZ66ImuagAoam7Kqy1zZSWJ6MOJddle0d+rK
4CZpRVfIB8R+6Wk6IaEHIK5n1Dtg8LKvnqUA/Z6MeToMGEqRl7wJYTGpP6mD
zTZ+omM64mNiEBLOZqP4mn8g97OZTklszDdFxEfqQPcpJxJbpo9ynpoBy7e8
Wc8YgZmv5iVxHUIxoPb/z7jkbxbEuU8fOUh0Ue7yyhCeDLuG3gXAA6xK/VM2
EVS8EwrnBGu6sopeRRRWqE3zqPQHODHv0Z0J/WxKhwVGkaSkYbtGTiIETW5i
AyA+3Y7QWOQ5knzNOh271DZ0y6wrqLpJvMHL1e9fl7wTx4paZijYf2Rc0OkZ
cehXEC6XTtmlDhaXZfHPn10l5NcvZlSsAMwy+qJoAPvf4qt8QVcpC0VR+C9E
I6Z1PmGgE8igEHodkLZCpAG8p+/ndbWiPZcJQM7BqRkWAkJDW1G1F6ACdGQT
4QO4vA2cIf7JEdR/vdV0UmT2NoJyQxo9KWnY1Ez2C/IUTSwHkEh/Gkbg0czR
i6d0S4/ztlTfEd2N33JJH0mlqYdxh7F6G7Oj6CnuZo+q4dDLohUtnC4YD1pI
XvrA8CC2gQMifMEXK0K4pctfkBUohGZiTtDUMSiAGYgcaFJ5OS02bPVnCS9J
fy/yv+gPz+yc2VDvHmiZkdlET7M6D3MmvlNfQi/u398+3A0JVSRUQigSVRN6
I9MuSQX+4oi/0acQEvj1azCMFnW1WTNPJ5w2zuF2FOzB7JuP2VPz/CY+fnSb
QFCDlo9VoqYFqBJRH7BHkrBZK4p38Fa9d5Jim7xowe1aML15sIXft6QxPWQ/
2uff//sD3h/JYQ/OTwkMosMzUyebfjB0alG4GFmj3wkGH9JysSFjgVe6/aAn
QTiJFtrQw9Msmwk87bKhuNQm17BX+WHDZKvRIQID0Sch5yO0bbhioMvNQvJc
kuZUlcR3eoQbrJWnRU90E+B9D5xXf9sTdQmAWuZrxqx95H4T38yhLYKrzpw9
w7wPghBr8uuYqNS+I0lbZnO2N1p7KsqgpNXZtCKlAqQJZaEkzBTJBX8iETTY
5ZT2VxCLJR5L8iadDXeICwvOatb5mKLScgt9d5HQGdVvahtohOBzWUhQsfXf
eutlBWOSNkUcNaMXztXXluLx8bzIfuTCMIdgqIQA7p+bJrWPiPXaPyLgBhuG
tCi8T3RtJDJomzPSqpYtDLjNYrlzd+2yxl/jfX2BcS/U/hiRVVJHrE0U+feM
vmClAt8WuIqmFZUrnwjsdqVQnJL6tYC0oxXYp1jhcMQfvHqsii2RHO2jaEQN
W6Y1S0loxHm5rgitYva4bZ/TmcaEvyN/n3nrODLU3Go1yUsnP1gpe1oSwwHn
FNNglq2LakugdL5c4Z1ESOaSNBVSdQF36o4xoIdWOEch8Gl7vCsFozvoJF8w
GMGnAaTuSrlTm/DdM8Dj3URilsi9iilnW3rD5o1Xurz5xSuKBLi5G9/efbg3
iWnGAm803GN3bzOiuKJaQ8GLlPWtU3pqTvrXLJtCy4nzuVDvC4INmsV/bvLH
tGB7VBzHqsiLYjWKP4nwU1lF1zLEDW55jw6K0xSObDOKbL/QBFtinXgPPj+z
g0kmP1UIqwXgthJ55dukMJ/Rzud85R7A8AkDgcGyE9CsYETa7jyHRKMZKzkr
0Yk6CinZHUKr97QCLHl6ACoq7Z0w/1rE7pv4geQ6Eim2TP6sTk7TBjT1LEby
FvS4jCwe35/TZPuBolND0/KazyBUEsheIUsBWK16kolC77oyFcZugDZK8KGb
EswXtcqQpgx0t1H07r+gIYGGVbV7rGDotQaYztFVQ8nEn3DD5g//3knmqH9/
Y4oBsihInDZdeSo6w9Hp4b7IJtiTkp42eQEZQDRG+xOITtQLplt3YTfmaQwJ
3nZC2iGxlHhCazBplxFdUV7V7lQBzzbhkhJ7qha4IQNBj73bV2Qu8Tlv6UZy
gt4P0hYerm4HAXCgd/FmHRWw5I28NMwFreghonfsIeAg6+W2gbxIinQLe4eg
Qdj+Xf8Z6N/hvkeCzOBKd8R+iRTc/vDoXQ29Yg2c/0gMpqZrK9g7KkxdyWhJ
KOqwbC3LrMJlEJEiZrpSvj7Z+vsP9uXQP7q5i/t8s2evD6EMsu5193iqf0V2
zguogAwcRQXVaQ8OsEJbBSY62+trVgIB4KjDFyaCoJztIE6LgDoMfQGLeI4s
hJqBLBLKXPsc1Sai9+6BwPHfiKyuGaFYZZ2xvxScxT0zir8u8yLzYPKsQfwI
VSt+QTwwz2uIrNrRbl6rB8douMxwclI9hflHzJqeSF/kZ0zaysU9dyFM6Vt1
8zH/L8FulxUwoMiYB29q0/oPX78+aMQQymYw9iZ1ln6Hb30rOpxID3+kCf2B
DWSGgdMAxPceYHhehmIOD843Na8VonTEd+2vN9brVVS/LmdJWyX0H28LRNFF
q5dd8wZC7S5mXXbDKnNZPQ3jXIzhAqrdU8YKHqSLwC9RG5WttBJW68xpIJm8
mv4DdgmhCJouSI8Iog0x4ktk6kzh78Gps9WkmuV+mYB38gHMIXupQYqAez5c
Gvc8e328xyHpZCOyfn/+fCFuD/tDPG5Kv0W+guqWzZR9/lgjy4PQEcdfVuth
AIfYw8H5N6KnalPMwH41j0A8pySscjbvaYlkssVK+PsTIsyBtNSXxBef/6+h
+rtgHHzP2L9oNMzR9rphso2IsyMuTiiz1dt/X5DlQWKpiT8T+MnOxmkuNX7+
yEmVHQ3ts+RMxBfBpTSixZHNvwTZZLQvulX8V/QNXEqOt8aaceFsUVt1BzH8
jb4lLYSWeU9ABrX09fWDyC417r99b3eKTD9caiACCKSZk39g0KXQGoA0J921
qrucsIvoJnhI+7cdQhHJWjkNEqlo83OEZEXPlmCeftHEdKfT7zDmItpvXjkv
rp1bFAbOlpqqQQB9NIIVK5YWh7yIotg0XGwkWpZ3shEC/uTzHhoHSlkWuKLZ
pYSrZbWuOivO0jb1vFYw411NkqTSlI6yeqQHo6gPh9bN3cAzb7VjoOrO8pl6
l+B6JvCvgOa9uSwEnMh1IRL1EgB0hhDsOq/F4u4H7NVPQzdsveFcL+Hreets
Kg0Iuj0JX5bb8Dkhm3WhuKcU2TrXBxTlCHCG+GL1wGn7zpUuyrcINDG9EAuA
C3OWIVqKhWuwxg2ZbmQg4l1OAXfL6REi75TBOSQAg6BgOl1m5s/LZt7BkJex
7o/lLxMQzuwWhpXKt9AX02gA5OfQPjvRQYh9BvUgyn5Miw1YJIciSBa1Jj7s
fAQZ6ID8+nnetgZE1i9yuAp4M03rT6xpNep62pct1+W03q7Fo/p1qZK6SQl8
E6ROAte9EavxM9y9aKikAOnenFeFRK7xEU/NDaSvcMkqEq29Ix+ZqQRiJ3O7
Up9EIIVNg+15F9kHxo37bErCvd1CYf1wb+o4aVq/fonLDHnG3j94FPwD+a1e
jJi0Rs57uaCPZSbmmUXJlY878I475EC6BsmffLVZxelMEofSImL8MFuToz0F
x6V3kZ40iXqxYa8T/EmSkMXk6dznoVb3nL68jUSpZlO84EyXUDtUJGCHHWl4
M0vsIHlx8QIfFi3FZJegwb4/SKKaoErBDqdbEwuaC86zZc3BAcXlSOOthO4F
h4UeSaksOSNT/jBQGUpk8wiXJB2JY5lNBm97G7IXpurtWp1RZBHAOm3Z9+HB
FO2YFdeqLbD+rxt2NsrO4u6dKjDHgfhnZVo0F3tKNW612YPAZbQTdGHNTY0U
pr0FHnDOJ/b/8dJLZASpPTiGoq/hHDIrUjL2XKbdx2ReFbNo7SJTXc9UYz4U
IUAzwQjyn+Cz3tQNGc3Eoxd56fx6lxd31/+TH/2EDwiNK7SGHqTbZJbDWRzc
Cm+bsC9hv5n4Z50KK0F3ySksJQxuPxRPdgdQ8PXlob/yzw2nhphHmaUXSyfn
pGK/RrwS5zL4I2HhQAiA0xyQdsgvuspaIgPRmMRQEZkKiccmCK06Iy4KzPZR
VwIwqbUq45WaPMrQbuLeRaP5Yhv405lnIXB8S+hCjOri4XYwjCOvJhISEZ7o
dTubR3EDrFF56+Hr84OmQ5yhI7Zj1dIvelfQJP5gdwAW/gMZh71hJJTMds3O
lwTLVh1QTIROE4YZkEB3QGwuq8HpyD6Y0iJgajOOGJTTrSBV9ZT8mXN8m9Eg
5eA2yb9K7DMyAGG+wvGQmOMhcYa9+h08QvA+HXWxidZUiaooV6GuJGn/0TM2
vrL4ncg5Xd02sBPMv5KAxMStMttwbhL881PSYpOQ8lNo25EIqpGz0XYvy0lI
9uqzj+Tnz52MPJJUDHOEX9jUKFgAPeus8A4v9iCxkmHIANT9eJfAH65ZfUr3
tO1o56YUIgUrbFVgtUEdXtSsiN6bOvP1PSHtzceH++vPfww66AepTHKL8LvN
YE6LnrveCHvZxQ7TZB7z1OT0IaJ6iZgmlbr2Vrn4l4hMOFYh9IpsIzrsPIU+
SJAkmdwWHPWddtyzcIRUVbyo2o4PBrYq6aBpXnrNltglISs7OERTp52Ak+C+
jRFC7iTCUPqPjlo4eZc0h99J6olfA+il/mOnBsLvLNkvEGNI+BSbMtXQfm0R
Q/8OUUxenb0isOguhUnRJZhh2SzZUhUrSMSIKS+GG3k5r0lVqDdsE0bGpyBH
sIGb6kGz4mYbGJocBWYzCeYRs8krEt6AexRdCRFgK2xDqOr7rDXN1sASSAX9
TjCGA4kb9rlwYnbc9/T7ltTWRAppB5GzQBVPNFSsq4iZ/8TRCGTSbMMInoJK
nDvsCmkdkqp2nIjyBp9Qhbwd1s2GgYqqDkKEVuhFO7qqJ5Ar02ryZ4jk6ubd
O6ES3m40y+aGcOoBxM0q8TFG57gTaJtA4EoyZOIZSnM4d8hzrIDsdhh9lO6m
xzgMDMQ5QOLkjKmkDuQVZ2hYEtTD5d3Ya/k72DSMOlJn7lzOjjDEJvxy5Ryl
p+dwc/oMgc8Pd+ocf/XKPKL3N3cmouljFNH/MIQkcaxqWTkOAyu0N+dDDLw/
Xvt+Yf9NqFWahGP7Vgi84/Q2QLrMCYtOsAvz6ODgwCWIrIjXECWNM8B0XYOJ
eVch30vUVrOU9bY6W1Ws5TP1stNy7SoYELlU2358D/t+323fv7m/+ug36k0+
73UYRhZrJkSEfiZqIuxUC8E0AaI8sq6TrltncmQ1GQMZ51YvgZjmvOo/vL1C
EtQ2jjhXrEK9r0XUsHxLZjXS1xbjYEH3pv8xYB4T/y5shH71MXuyiNalD9S4
XB9EwZ3MQ/E3SRD8Y050DN+khXe6cRN2YIu2AVD68BR7XuiC6D45TRALII73
8itwwXR2hGuYDDX+peEW95zE1XEZJghwAahjbl4ORpnOYY+q4gHRzCYcH0Nw
LuqcY8wIouQbHi+FGg8HhOSwAVvKzWoCUAc7iiwZlVBJFxkEq8AVVHOyIlT+
lLhsuwGdhdEBAW6QuWb+BjINnD3WCRfheZUelv+AdCw+qAW1NUOhE8nLUs5A
VAjRUv1GMofa7Ec7kKpsQ4ImzKOSjTaklHGCAX3FailylOk1UxJGo+gaFChN
FuQhUGaGZx7+0OKEv1mbBQH/7OqPqzj6X/S/j829rfYfnfTEZkWIRJZPnpYE
0rDsJRFtcuy2kfAmEq6Y0pSw2eMsOTw/eP3q8NX5KVkz3ZCXv+x0BQTvXLbK
eou4PoOHnKBliWCRh4ZGKAn7ScX73ugdBp7c3XidiwxxsZi9v6iq75rqAhap
yTKx3uL+fqJVBhociiammKHyW4PmchYJZOwdBzTNZQZNVsxNsKYlmZLNJuvE
vp7M+6WrzFCPOOOcdPji4P7Lm++sUxAQoCutO8kpZtR7o3sI/QzRHTKTBL3Z
S1OvVOrTPqdEMSCxsnoiDrk1tyuXQJAAW6SAHHvMesbwUZFWrba9YRDnMo71
XBpgE/hEpqx4pk1EEF8JjWlGisQ3hHjVzgl1CZ/7+aRp3+b0JeCy6XXJwo5k
wtXlQPmft8D/MQRvyUYqhA0Ogc8EVm3FZpZjOIR8SefXYe7siAMkEkGEwfa9
hKmpjMTFrH3OSsQeR1JHNzVX4cF3m3IydRn36E6reUL/Byj3NAdUtaw+TOBy
MTCd3AXndaVt9JgWG82ohaXGvrjDg9Ho+ICNazBYEVidgkFjNRw0DtImyZ4h
lV9eGvXZcmVlXHrCsB6o9TQSoJgXUHbEwYUqbPea7oG3A1R4BYwkCinOmHSY
8MEYIZIvABqXVBRwYMLxkn7POKAge4mCiI5qT2JsCMKI16sI0mU9uhPdlLPm
mawITh3sWO222THDPQLcO3mnonWRAThVUVC1IttKlI4U6aSqw1RfvmZJrByz
RSguzob1RPXCLurqqV1K2KDp6AFAQpPfmQsS7Dj0h46XycmE1VpSn1h29VbI
XX8aTYNgINHj0P88jIXppgO4r1ycImskbcmrN4oYCvrIQA+knaAi6j3nN6K+
Rc0CoRDvoQnYacem4GSA7Ac8J943oFQslggQSVI4iKKC+O9AEAUMJ6xo242I
cBgVP9tMcuIgLdfjSKjOZQrt5plxzJ5YecF2GV37I7yeZcbnbVKtcHmmToId
ky+cVDP2Bcwk1Ij/c6UKW+j1DoQNuSUz8wUWmbcqUiQLJr6HBPtYtaKP33fr
937+tpNLT9ZT9wnNCnDgBklJNjRLUm6twG7WNH4yGHBWxUxs6VnOLr8lCJ1k
AADoQewknJVRSQ4/vSbk7mJ0WkoJZ22inpHExttsW5UWa6FVpRws2/EDD3er
Fq3Aiqm25qtpO76sbpZqFWa0RSikfGL/iR3ely4giIFQDoCT/ViS/moIiMYa
0G8cyDwN+/TLPdRBfHEhoX068Uq9Dey6BxmSeoo/FRL2QeV57opa+dIKdFYI
dasa9l62MsZYVkE6Z+fQzCade0MSortQHEqSq8NkVZmYGAgCXKLHcW8if8JJ
rv2YmyFqEph2iIQ+xI/QAQt45O7ZvY50JaVfutmbh12jXCS388ihmK+x8DmK
0RBDzzLj5izDU4tNKnAhbqz4EHrnMIIrmrmvO18QOYMiIHv2fSMkvfJd5YLM
ZpcW1WYW30+XxI5g2UbRZ4dAijWejPrgeWuJ+z0hlX4AMhLXiqVFh/LZKmY2
LQkeKSsx0wepk2ndfQJBlKC4sERQZAy/AjNQjV6yH3JTchrQSLe/p7E5wznt
xKm8BcGo8RDjIhDOlW2MhBkBjEWVzsSCtpAUYaYASbQFe4ET21wFVM+4u5cL
yPsXpo9kgzBU6134ajQEutOQeZJcmwW/9GJpc8FJ/B7BofEjghsHLiBfeCWX
dw+wcOEY8R8B12Xnj0xdffmKJWDH7cY1IQxaYDt7DfsLtqFIPrbTEUeZIXu7
YJuYlaTeRCxC0jaabUv6sRBxXxgtB2RWOfvmmX9gg0WlVSYSqdy4ZNF98Cmf
cpn6fdgmYAkm1j89PNDBpt8nkIYm3QdSH8hNZGIN4s3TCRcpVi4vhu2xFUkn
7EkcXXT1FSIlvNtleEza7ljOgVx3JrhPUiyWxe8lBEqQ+J2sL01lSv+savYV
zAM8sjtqxJBC/avlyj+lTWsef+beyAFthwHCsNct0CdZq6MNFxoryphRO/Em
MA6ULd0GmgIZEya+WwrJu3XeVRIYiCTgOZTdlvwALIUiX4GIPQ7+/GnuAq74
Z6ogbBqV1Vha0KBjji4/RhoD2DSK8AFvKfEQX6Lq73QZz6gWXfOqH/SV3DFF
OHQROYPEwhGXemKPYiI0BMUDpQh2LMsGxZBKTDDfHkbQJ2LRzI5D9ZsBTlJ2
4fA71/oeRZSZQjrIzt8I9AN5EwTUIynLQg2fssmqTheZYB9QLf6csdaxjaLr
DtKEebLwWtgqsIAvm6GqyRyLEKWFPQqSTcVpTsIIsRiLNSlcjdCqUQ3pBohv
FQUuDTWoa+fOCttGvLCmRqsnzuQsMfQl0R+yYQOjZ2DrRqzVIStM8gp39zOK
L6yJRS2ig2uO7UL00MnCkSd+zxnl5tiNWGXI9BgGpWlKWpG2mGA1UVgImjxI
FmSQ3+4csIGNM4rjngiv/4OvqceVP96iZ8u0BGuYi4Nbi5W7/v4wJBJ5IoNP
jtkIfY/zsEfuaY3iSxSmjenywKhRx3wwPuB65oNvvBtsJfmKnMt1Cu/tJac6
sJqa3FWtpHmh/8qvX4JiKL6YklYBMzO1ouGdP3G0IxUwSaGli3doexDzeCHR
3pJWOKOiY6jsFknAzJ6LiaOlpA07ToFaOwWSCMw6NyBfSImyyL700xPlHuWQ
A2aurBtC2WLlee88XHxTcoxi55x6uOdrzKBJSeIdhJHkPvncB7bCpOYEQfca
EWYO+wV1pZIVWCJPjdMK0MhLTBOtfTzkqDPnKoh65lNeLQ/EoyUfEPwj3czy
aiwBLisvDY9lx9EeMAXHFTRF0a7EMUeNf+Jvt2/pbgK0zMrRU/49X6NrF5ez
41/jW4hl2rVPGmFZx1lRYcmCK6Jml1mqSIAMPKVvk9Tdzbuw91MJkWBNqP67
Pb3mlh35WvwirjkVrBKnxc0eVYYgdLcXJwOvdEGyZ7BCU/JVuEi1rLotJBeX
lxXNq9GyHFxhoIUF+YKsDzkicWjBPWFwd01QjGjR37T1fcyaDRF3JKEu2D7s
bNPEcmY9Yy1St2j8UyaKveQaxV8aUUy7WSe7ShgjbZQDKuzMkjAAi+E9+ODK
pfyDrdwin2cJiw7GyCG+H4OpCmJxtRdxDEQX/hG3wodDwogl7VBVJb9NoXnT
Wi4+j//4vL9h8e4dHRweBqRZrV1aZe9zlhYJlx9ddgqmCXO+ZpOEzvpETLvp
xf3PD5dfr98OOAVCXBMV0nBYlEQu4ya1WjsOOq0Cj4wWk2j4HEGyGvlMpJq0
XMjuMhNABUviKDX0Oq3kFoRlXw0nQOGgyQ7qWn3bMIhxS1tlOkn2w5zE+UtE
KwrUMP6/Ky4ilm4g8NLxtzsvA2bGt0SA19NlpdHYRVXNYtc9rGEsRKQ1cBq4
6u6XOTZbSVrC5YM3O956KbeJUm6R0Ew3TeP6xOw4aILYH2dQ+R55iDU4HtPW
RDdFrJ1lIq4eMh+8RoimnfZ6VvktheQaQpmYm1oNwrx2Lpld78swSvdyXcON
j54TzpLDla+kTkmzQ3CNnQCnc5lbgoXjm0gBSLzfRw7NdkeQo4HAmqZ+wJi2
XOyulB53NtZwtXCTPola1MKPASyEzcFaKjanjMwjyMD482VVV2UaXxJwOf0f
BPt6KEpsoPp2qxz0xjjxWyoa6mqZTxBmEqem/DWzXkiu4wREIwRrZjnXqNZA
WKMoLEF1nVXqn2TJyT9bSvhuFjRwCChzn1W2ZCIJXMjikxBYyjQn/lmHedhg
qxnM6mevOFojLmsITY47PIpYSp/hyo6H7Iv4JPS6rywzG5kXGq4RthY5oQWF
Zspq2TNWm3VnC0hhQtpF5jSsFxtJ6m1ppXSR/eBGBC7xKC7CKmV5ShxVjgpd
MiEUbNyFnHgeX346ijMr8QrKs6t59ExIa6iZzJ5OOU1LPEfP+8GFyLmOjRXf
VtlmpLT9gvd8ySUJL1Ul9MNtD2KJEYIlyZqhx3LPKUt39POndABFhh4Udua9
QYgxffaO5BJYAdjH15RJxDFo2WcUds0R9Gel4gWgN9LGrxGLQALoIDNoNSlH
JiuWTa4tATcmHfs+G4qre7ubWl0cbDhJuqRPZ/+Nz1rudywdodvf3t8epCqI
M1G0TtS3ULOLE/1em89KaB5ZwplM2iCs6rBTCaYjeKnORjlRcKDGvG72Xkud
fOR8O2vDxWlZtGmC/GNVPwuFNw5Au1mKnJG/gF9ce5DnhQ/5WcBgvlFmr3jA
z2/WI/iRpcnIME5z9/XS1PupdGWCcGUdrJnWUFi9bAVus7OIDkb/XHBJpuAG
s1O/aKQOVBRYSDKPqSGBWk4mrLdFuYbXaF/dGLi31JJ4umLV02RahlTtvbvA
3FD3weY4uoHmD5onrS47SX9vNpyDFhcQt+jvkEVSoAfDU3KLq7D/r3MDaNdd
+jcybF3umTsM6FbF/7GxCOxuJ0shLSO/x67jIG2Ju8/p29EMtsB4TibpIiu/
0a6+fYdnj/6yWRByfs+WdfBX/t+nvP6+KRffgkfG7Cq4KbXV4vbNM+qZOAgU
+HvKFjeS6cTqvWZVctVEZK6ZXV3qpT4XllAA7rGEYQG6bFmB3fMwg35cPZNZ
xJK85oMuFi+TFDeWj15nEc9R2jxvAEnGmoTwcX+eWnY2zMT9LIYGQTphpSF5
gt8Gq4aN3z51e5nF99ZWxtdQcc+NtNiqFmW1tc6eJJt6YD4FZEy4goFJRspf
qRUbbGXqMXwoTOrkmAdKfQlB1XcOVIEfpfZ6NWTzKqxi51Jm3ZQE2ifgYUFl
t1eA+FJJ9yGrKQ3bEaDTA4tDc2tItQrnnXK6c/OGlB4rPRMHYBCO02oKBOUM
7foTtLOUzj4ujCZ+2MEQVWs102qgiEITSmd5JaVLjE6RvBHt72oo3lWLMHer
aRicJexaOLI6eXRwcD7GpCQThNy9UFODFIrjHQDXkXRt+MfO7q6/w993iQe1
PwSuekdeyvh9hs9+V2AIIfSbYJXTWsWzQaZH0Xzz/0KDeQQRnG1alYuKK/2k
xyOh9Ae6KmmajTN9IGrZOpyP+x8+fBzEP3+j//yKon98lGyOtA5KxFxrS1dD
h5yV4HJF2IAzERrQhZLuhZesFb88wwoeYW7D66nXSGwrKxwSs1ob1XJdXKaP
4+socFK7/kn8O0FT149Z72GZ1txU2NzO9LO+ZHhLdx3VowexBHExIIG4DGk7
1VSifS4Aij0g9peuJuxztMQHXXX/fbwrGCYrizo9ZdqGkM8Tgfjz7K+K65Y4
RmW+e1uNHYUZdC2NMypAZgoRe3lDu4Q7ljDiPmNsFYb09b3eEPbN2dBIVzH8
4U4/zlyWPASc2BcxEEo4l6k56iKu93YpSd4bhypC9d5ibA0R2UJaZYr2Hfbc
fsEksA7S3eZ8IdmBK7pGRWtr5bTrW5WmHSRGMqSxPwSpIsGLJTAo4SjD8KF6
JVyL9bRNw34cehfNSsEqxqcLeFnjWtPhtfRmyT1lmd3W4hQdEnKkC+6lykfs
O5+DK8PSjh8S/ZWFGi2McUx3aG+YECcs1EfKZqHF9IVUfXRe015JYY8Ik/Jq
Rmt0nmk3pa7DJZzs5tdABbCat9tHN0MFqSuFXZkXnyt5K1/tIcQMecvvQcO+
/FFb7O6kHsj1xuiu9hwaBX1HCUkMnzrhP1MzfFnzh6Pn2yyhRX18fnA0Onw1
OpEgWr8w1jWIjPkGKXRvi03WVqh0BItTtaP/9sM1QeNr/i6P+37NQ2k5dHV9
GX/5cA0svNEo0ccHTosJ65XQtVGIFvTm+uGBeLMfedP2s9ngjZSGn3749PXu
4iN9J5Kz54WM57v8RP+rneCOrTxa/QLvNX4/6MX9UzowcTw4bel2Sid5X+EC
YT7zIRyZnfq+w1xxKxIOzQb+FpbxHiyjyVbUULOQmcRmHAeUfgCvT15z7NyT
jJOofdciBSxq0CUy/T2mg9HvI9J4XHtuG55ASueEk6MaUWLi/sergf7sDJVf
nY5Bx+HQFYIhGpxHpO9q7QaDmjmNi3Ow58ggg14VO1127Bx3StN8eV0I2h31
HDROcBqeYGLgeMebkkpBLIfEIWkJu79g8pa9RDvLGpB6Hw0mVw4mHW3avcPw
LBEl4h8wjPDrQwUAAdcC+OLvjMUJAV5bHny4+6pYfc8+LyCfhCR2MNzePMuS
zssIm3kNxuVlGgiHE9wZ2/XINBMKQbBByNCTtzGGD9XnFJv5p4AMngP4VEFA
2MFiFI01rzg7OvGdLM6Df2Cmmsadiagfbu4vf++e/njv9PjnA57j6Tycwxhc
MUrWT1u6v+U+BM4cBNKwYaxDtyDOya3mkvuiarmtEQk70ofi36v1GlitpfHY
hSXVR6oqNDtF5zvF5ln9nLzfb2MYNS59z2UQs4uN6dEqNbkdRUObFIFdZxPN
KlJJjNQblU+QRs+8mf1WoRnugGGFZDjkyDHdf7och/ME18+aZJg4nRe0B/VC
WK67IM2qh+YgXUw5DD2PlS0z3UEi5EECvtfgDvlaHXGKzVAckW0V1giysuaL
QV0EzPfgFqtwqPG23Z/GnZ/GfaMSYbc7C4vQw8wqunw2J8XLHTLQwM5zndVR
LsKSzizpoMd7qMnhMj5/+vCBb0MF6udq85CX7xGAfD94RrRKGFOt6k9dQemt
oNKzEbwAVxR1aKjRuz84x2RT7U/L7fahOrf+wSBRVaZhcGgubLICNO99cLxo
3xTrvYk39SQt32g/nFcn52AcQSG4/P307Bh/l8jLpq0ExtJRB2M11cx1ab7+
GV3g/PSMmVB87yucrUzCfD+cPjKFRzDSXGdBewPpXThVzMuGZ05FoL37YJKW
a4qNh9gUDMltB2+G2zmTdEKfcm6t5LWVYyf6CTpx6gVeriMZOhFQIBRZN4xC
mpKgnjk3Co/vbBjFvYvO9/duVB7nz33xnqx/hkO0a2gzGNzz9xwrpq39jnu8
8HeEU7i5vdqbTwUpponK7UYvbdRFN//fbpB2dDF7BIBn8S14OxNnJ2sr7l/c
3gz8DQvqYXwpoxUgpeSqSZ810lRUkWeWRuzdmBjd4JDkT4bA9xe9Ldv7P+OW
gOXw4Ahvpv0Hflgxh+b5YiPGt/ZzsKbdnV4tfZEVgzjk3b6nZvSlDL+oyRpg
w5EtIl/Ml80WvhTbRZcADdpY6JhL95J5I+f+jntX3uRKPtVwOqCbCs9jow8X
0+0UbfDe1+l6Ceq6+nR18V5YMPL8IFAtkdC1RYxENDk3IysvZPSDgxtd2Xcd
jRqjYQnjwrKLDojYoWG/DOOgls2prr9w/uOIrhtKTY2mf4T6BXpgt8uV008P
mIVJTVf45t33mHnssruUiKCG/LW1ISnWEhWXgFRV5PHguqKUOzG6i9n1C1s5
J1yA6gerMzcTB71ppj4nyvyyPhcrs2FaeG/YC6YJ8nbCVqBFJg1aZ5mD/eGB
IyioH+o3/JtZuQQ3nTnTaGZ36xQHH1Hw8CPDASSu8UzsNCCKoE/NuOGxI2bz
V76LuE/GozMvtVRExuz1Ltysk87EEQO0TDRVJnDf9IZ6vv/KHFSdN4HU95mY
pkwG7GTkY2TStUbxbqdAUaE8LQhQrtkkUzXYopva40zycANNHCZ0syuNZ5yi
WDNntcbV8smkK7FyudFNkDLq0n+eaWYDiOAQ2p4xcJKACuBgaTtFfnlrbaq4
mAzZEOw/inicrjRHlApt/S0Zp2+7vaIl+BP0VPJTCZiWx8/QMfcuwnm4Qxrv
zXmQQx1blL1d8tovTvStZ7j9NMvmSKanImBivU3rHcEGHnjz/m7gTbmOi1dU
DB9tubm/uY+0HfThydFz7aBfmOr669eAVYxP93fvtGXM8RGraE7wgMzpVUgA
rK0FabVzs2gO8ZyY6ZbEejqMJBFExjQ437dv52ZMT6Z8+JoZNT9fvz6xTOfL
XcOEL90Hyvp34rjZ4/DmXHcvZa1d9DYOhFjPJNPfOLqoKfZiKRcdxbfoaN+d
uirxqclYpUnuT9pp2opJbZwPpFnTjg93FxasXpubwhasXM9/pdhgaY7VSDPd
sL2GdJcIAcNHlKW8BpC2LfKjeTeBajqS4XTosjZ0sArnWUma9ZKNv6kirDno
iWOyP969hL5vInbTctEVijtDOaLFF7bPvu+D6AqHzPvy9eb98xbuB6yUfJUF
b3At3mn9fpNzjRiRXfGUL9is1Y5JgcuwY/1xMxo1IzTFt9lM/iSQD11cVUNd
pQye9aFNHrsi72f2ARyK9isT8s4mJV0+hApDYayRSR1VwvQapbMZnGvqCeHJ
YtyODCO2pGulZo1iSbZKcI++g2Hosnbt418fnp2zk81p8kxb6KelGw+JMZih
5vX1/mV1cTeIrzLJjwBzuMyKAqMZvQLsWod+vuaX4zfORr64u3PL9ukfL9rJ
4V4+X98/oCw9GPwGDovMpZfN48OD+OgQKv2wm1gnOZRhnJRVv386ey/Sw4tC
ePraG41a1NOgjX1gGbLWrwkIzgzCdCZXjKTvizJ/rqGmGqAbljVkQu7t5Z14
8R8+3Hf+jh62LNhIt8YsGoSBeX6XZN2lbRMFjy83K25Cg1GO2g+HK4bkyaED
tC3hJnvb3PXw3Xtt6Wx0VR8WJJ1zMPSdjVnZ6Qwn8kFQF68ZRN4VzrKf6Q4y
3lJy1MnGvSGDwjDf06DOltrpIZiuBQvWX2nkzS1J+7ffSvZvQm/ggPfYolHT
SnumpuKT2HQsr04/kaj3iXmI6zMsNPLPuPzp/vLTZ4RvhHRPD48tX1B79Vmf
Vpd+BPIiNrcHBbs78ZlxUuZwX7NvdH9R2JCJaAEItqcHcgZz0AqO7WNQA+t2
iChMtW4cUoFrbjSRlnvpsGJt/mikzXQBGGC/j4nhAmbjDCfnOnPvcLolaYZZ
l0fuU//26Hawk/U8jII0H84u0/GEwUisWEZduQRbVvjoszfMw4bSzPmtfBie
oablsrydIQ8xYIFMxSYItd1fXwo29OnTiyzvYgO3V2ucB7u74FnZYfQjxKUd
HCI+M4g6ZStBz0COoXUjERJxdojqqCIv45fuZxiOaxUUkLRfbkbq2gZLOhF4
wP0zTbmJAkjbxKhllUtwKrLmLr+QFekpdaUcHMPm7JycMyDMKMR+uU3NAv6H
baDDRxC+ub8+PvF1UeRr8LJLpNbEfdyI9vH/nm1dF1cJv3OUWptdNzzQ2IcR
1A6JOgZIaGV8vr/orCxV17BMgv3Sl1aFH05KcZPeqnl0fSmufawnBthKUoBZ
oEmv+Dqb6XC7XtDSUMccsNuaJWYXhIPI8gBRFuyswdz1rNHfe/sh1zx42h93
4XjWOSUKwD3JVwJ1q7KVPguCRNH1isxHS8sPK3m6dZioeOfcBmf0diCNYC1r
XkE0Rdvxd57TJF6SzZhA2p0uytGXSJgbQjWk6JLpokMfEavP/3OTuXnPauYN
VLG3MkAU5XLehjt/px2dZoGR9EjULm+ScINJY4DCuFCwfZlIzl1kwIkink4Q
nKjvFUCNazMlO3hPO/DW6zCljZHwrSXSRdEtCmJ35vLoeXWI5Qm343zKOOVB
xYCCkGTrzEr2Xf0YjBQeEz6pfvA15qW0H4co3dQyW3Ra5DolOeY2a6iWIljT
lXzPsnVaiDjl22w4xYQzmkTzdrMyS0u1SkDgPHBAEgwbnnMrNlNbRZYW4zKz
dpvZNdIcS3UMUfHOz89giQvu8V104opoOresOEtE8gL5QNq8S6bXsLvA7Ck/
A8FdnpAaKAthxFH0b3byWP5XRblQAtN2mOIjCqaxbZMnZnysK0g8zsO6+Pb5
+vJ//3aER4SjniOnwXUBJp0OprNKQOtHJD3AdMqbwY2QeprVE06NogvFVSU7
exWhyknipdTcOe7L6pjL0eUfpaVl3wBi0XMQi+nhpXWRDMT1MiPBhZvQyb/3
IpR4ujL35b+WfkqN4H8frVFdga+2jhUvvg7GY8oInugUBD9J0w8ToPzsbnmw
ZPNJJr54jXroe3ovjm63Flq6398O2GyxooZASqqmFDYqZvJMOSzqq1S7Bars
5dRh82xD8txFDtzcXH/2OVFhkq/lOMrgclejZrW4qsOVKdo5fH2vncq4iqDO
Mt9lVTRN/4ZOkpM2PEg1zmlTAzsjxRHs28js9UhaDmD8pUy2CSoXtmHTCt+k
1Lvc09ala6LFBo8tYKBFITr1zTeflzafOYGZZlzFWqjB+TYYOa+kePC4h13L
3kDBdA6tdM8TaRcsnT0DTtkKKHnAdzicXoodOoOwy7CV6yr9wTNCpJLNF1Q2
gYLA3iE3gAjfkrLPzrdY280TBs5buORdJMg6kPHsMz6ZDeXkSUiovXmuFUi1
yp607pm1YSnvM10paOcOnurcQUEb/P7l3RdS1Zc5alk+0CufcvSfzUvtLbPX
UGaIsnyPWlNODcsyjDCbEPxJD0fKC983Y5CP5FvbvMjUTlY0mqBduBjvKyZZ
uynOfNysSTObSb8kVYTYaWetGrTNZCe3GNkdCt2xzsl4ADvYuy50m7fCWbs3
Uu64IV/ZpNb0fWJTWWzEgJZN7JSclBme8Z1LXDkB37LN7HCIQOI+SI4MZgIE
k+dVDmhWnAwQatTRpjyok1MfaLyR0RHX+O6AW5oMSylHnXJL6YAU/MQu3w4r
kvmGJnwY3CjLDEJk6hAQhHbuSPizg9HoHcex90f3fco1agTZ5NQmMwnPBWZT
iH2/gWp7Y41xh8rvw3RTVlHCfXSovcMCHUKwKHGdrKzrWbdTrpuWJZ1iGNX7
3FgNPNLxTC5QdD1qg8Zcmr8kCZPuaix/ueME6IuV4gIftNda5tQ7Fjmw/jrO
9e9tpt22wpG92zWD2U1NtpxM9bd4ytdYk4qhNK852cpNLCTcBNFJXdaoI9C/
gmjdoFuH8olYltqDn8wSbTnFaSi/TYN//ooi1hc853HTznBuFVbxrrBiFbbR
cfMuvdi7waLwHZKB481ul0Fv47hq1ySOKLkkeIofcRgkjLIBr2HQkUpnv+eO
/ii1yjVca9bNFHt2zb+16hnbJiHHxVdu/lxezUjhdYJ2V7xCNa6g5jPH4X5a
vimU88KYqpMXRZLOHrl5sdgT6CNrSrEf+G5BRcUrX+DE9kLzhq4oHXBs1ydy
Wy8i26odnE1W0w30cbaefe9z04siDICTJG8HSHGmCKGW3YmfsRvArAYA9zzc
eRVhZ3/S3auZpdjdMxuzXGIMK0prGcgXoKJ2hYbNT/tn9SYYFxaMyg26iRCD
KgrtttuGO7HU9/C1bbAIxEZ/KtsP0/V0gZlxgxIZ8AAnS35DGybeOiOpjRGT
gMRMltJXcVsAq7vRgSeOBnyMH3mVCmLfRVN2gCOL7Yb0Lb5q9PesSo9Pwf1w
atl0WUlCQqWvcPeqBWqWsmTD24wSnQ5spjxLnk4XTf0mtb6BgWnM+Ok4a68p
yH7a9lyChfwbuS0YvW5Y8UQ3piNbDUE6ON7H/AQ3E3dg4+C5VejQSwMXleLm
IdoYKwgIBp3CVWHjygiiEXr+UVNNvMbj3N/lrBMkdtyiIxaNLjv8zw7ADKPp
qB9V09mFZcEnTtngUbxSjt11wEsXmYPToItMx6LqqTXmijJDs+yezDJNdD89
OOP8e+/ZlHT5wECUHjJM7qG2rzWMqvf5nmjByT3T56hfI5o7rGHRe/pSvp9x
lIb+MFATYl/ck25/f7trnHolWFoJysBvVnI4fTHxQSq5UAuGCWdVbVEoZ4ZW
P9PUeb6VmZMBK/uWHnSk+rHqPHaJUdBsQk6P31kB2z+CxTqKiMrrCmG3MgZW
tmmFOeeHrzRU4vu8sWYUbBy73QMKIhGmCtxZM7uuD/O3wAFwZwTPOqGWG7hE
xZ+/PRE2/YoidWkfwsHCQjrk3C/Wj/UlwYd0hIGmUQdvZt9v9DVP3uWj+OtO
++K9+kYeIWaJps2O6Ez5dyY7vzjGsWUuk2x4quk+kfO7OaFTdnv/cDGwhCWx
7+3eWfNxRaYX0vDzTpTp/sVdMxB5OdkgDTn0SigvYG8a6SLMVWWMPVhqKEvY
ZatTYyVtQhgkiymSspKsIW9WNZ4Rr3fr+nuVsFHdPz9xn1wi/9ub20/IWiSt
pwSZcYVCi3afUwykkowy2eczva+tZ2yPw6LCUWQCbaCgYCc5Kdza6Ycj52bk
g67Z7+YcMxd3Q3P186kCH0tYx8M9YBkfoU9xaulIRPZNy92QBQ2en5Tu3EES
eN7JJOjQ52OeRh1zXCq6hZfYtA/nrN9Bdmcr5Csebid5l6IOXFvGPcgA6Tqp
+GiDEpHd81eKlGbL6MXQgpE43GlfZINMs3TzQyqZV2wCgEwl6yfZQDnmyBPy
WxrpAUgP+pxRVrKaTk1hUAuiPou9ojI1cKy8wDplNqLcs+bN9jT7Ln1H8FKY
tyog+3XLJkNtagDHWFhj0Mypn7+pAhFF+nefIxr0tglS0SxFzzMijmU4b21o
sMK8CM02qA7caGM/NyuI+weJTaEl7Pzw2vDTe2k0IYrHVCHcD2RuNVeoarNJ
VfGURzUrbB3zobP9zUXZHPWMuCeJtO9Cs1FO4BZ7MQ7seCKfGTr9zCpkS2UE
b6n41qDB3lVEZvYUhWtMrwxd/WxQU+gA6toLq3o73n8/N8utE2mdoyNK9knw
69qlcbzdfDS2nBtuD8OYZSXfQgkT7qiADL86S8CbVuk6OSCp+UYiuNy8JW0Q
iAzCpE2AQtFEfWTiNJouVadz9mloFhAK8TgyWQCzrKsfuo7K7LPTk8Nfv6Ks
XErRhJTW6Ls5TkS3zm6nEI2Rtcjp024HDL0VauF47FJlwUs01rG+4iPr+nl0
cIierJpPVmesNIU4iSlvUhNugZH9v+wDKJLN0aEBy2G37aq2Z+WG9LC3OfkW
yg2P/w4P1/HmujKRyDVm+Js7lAeINxfy7Sqv66pOOBG5ljK/Zx/ge0FCmHyP
5iZ0gfIIR62bZSIpPX6RRZ5yQoc8JSfYewhsEtHHUhfjAJF/UZ0u0V0iXEFN
psTVvvjF9p/+u+8ShmYyq5InRFOz2QvnI96XExdwWx8RC3Uc8rk0aTe49VOp
XfpIGze2yWZktepcqenSQZ6ZIOczXcuinaxj9sprDzptKKBqtxdDP392/FUM
E1ZBf6mHLAp63PxjNh0y+z5fD1zBoNZ2VDUGpeOr5LNVJr8+POOamhubcbPH
LcRSXeTsODdflcYF9a9++gEyGE2Gc18amBGs04GGSCHtrGzWrNe2xHwXQKWy
rsw1hEuDXRcXpbuwnWQnPZi5FHtXH++1PtnsAleG3It/4tv7q19WP3x6TCyM
iGHCQGUJF9rBPVviM5+53smkxKN//zrfEWZWNs0saeo1wH7vm1OV4oaDhONM
AYzAaEO2rMnGvqWSTcCgN4unWjx51uiUZM8W3Wv3TKVhLIe3IQRpODvgeaCa
G4LL9ULA0G4elkhB/MeyZnnsW183/82k4kCyhbTUYVMjXOWG44gl7chEPL4d
LVZvmycvVjEEJvM67wdB1Z+vQ/GqCfvUJTO3j56YaD0vYBFe2+cs5v+v02vj
MJs38oae0olLYtjhKcoNWODfbSb3m0mIYswUkZMFzk+IhIA24VTkuowwquBg
LM7zrEP1LueCkL7ElL9bQpuNVp5+YPujT9/cfhj0hrAinTcmEt1grwE7D0LG
7XFbZ9Eerekuu0CsUtiu5sUX9+zNWhB4cqS5ZjDn6Be0hkU+g5IGH1z+G6jm
7D7DjX/OtJ5pfywpV2FLjPhiht6DeSOWT29o9ZNnSB9wPUqasQS5rVuxlAdJ
cuoeo7Uusn6eFZfNPdNGoSe9JZzXerKNFuI5DXI1uOuXG3rmiaj33AlQRHsx
8DGGbtgomllxoDF3teU6Kbxg4C9w+r5627vx388X9sKB2iPhhGeWR5LA8PFK
/Xjnp4cQjhZUcKeV/JmW28nMU3rBiOdlies1vBnn4LOG6DZ7YadyrVuQRTdD
W0ibsPXvNo60DYWFysNeFCPTnpbpdzLhIbFIm6lnSMHr1NUl5SysqXOl+5pd
5wfrduY8z6V1MTbPOKLBW+6XmsoBTckllkqqS7eXkYxSl0Sb/gd02q/mA422
vc3K6RLb1BIocWSZHb7OWqLp6SZ5PK3WjZjiYn/TxxM+CZzjACHrUKuAhEWZ
9g2edtP9LHXE9Tl5ZAo40VCNWPYxdxZgO8kxKuSVRcGb/MQfZCAE8nyVomFg
cD7J+nItfDT5izTBnH3hEaFDrhOJXHttcWa14TBgkcs8+Zm+AE/jVrFhy0gw
ZhaGqoWigf748OB43BTwJuh/EvpL0qTpIsmrNgm3yrWXkYdu6g/ipxxu2j1Y
mbkrNgv9BLmquczeMQ536xsBOhdoFGkteieZsNPBzX1moFlLtf1r9b1+TGJb
eIZ9ay6BOmw0rklgdLw2fl/nM+LL/h89k/q7sz7DMcEsTJSqg06H3iV8wcOo
tCnVP2kv/PJvC3o5+I8rixKfcKSOWOtrMOVZULgkMVaBGkWRL/B+RVMJtWii
XMGtyTpSxqZtdb00vX8qnO/F41gBxU+QYIrcyAd5F6NzL4w6xJMKufwkw3rT
vJ5u0GiZruS7/LyHOSj26x5vu9fwG5gjsc3fG3HnAl+CyAp4cGEaEc66FYj5
SuHggCJIZDyXG1AolZtyEBF/W3JwmNuSauZxWnejDB1XG2daIpyTohnWIvMF
z4dxz3X0veu0y+Q8/wDhtHCcZQgXcvznRnJzgyKVqH96SqomSbNOTzpm0t2M
3L2qQu+5R7KQm5XM7N9vI6hn7PokwfOf6rxtOSFa46WNlNoyKkL72nJguU+k
l2yzNpE7BEa7aouW1SDfZ93JCx0S1smLa6uIe4JyPPQRuQCaqqMPu5QeF97N
m+/CKjZBpKLO8vJRHNTWOZzuMSvGwTgPy/ieQcufqJc+3LOrYqozER/Ia4tC
ZYIDjpb92xGGhA23vqLM35w1iXFA1ri484i3PrvFZ6vxZUV8WR2B7QLp0uE3
TAd1LzC822lKEmEAN7fL41ocYqPW6F4C4QaHUcyB+JAXdTbr8aiJlH/qkB0h
BckocFmBMkIb2nzK/ZZ8/x5rNGadJXbQotMyJe6TSUvUgz6hvwZvYsE6tcXi
XXaDoY3prKM0OF2daFwI3nLhuKFfnKgGBxXJWAUjTBQmQk4yK8H1KShmIcJn
kQblw/uJS9xKRvvhCjLa+FSGgxWUQhHxDsUOFFgq88NLsDAgowZOGA26E0ud
715SOFyDfulUFN9vSYhX8R2tVNVBcbWobzom0rxLHMSXzMMCfdPHmrgFB7mb
rsRFLPLUQthMMNqO3kbqbckG3kTT9iRUEIzL3hP38sol+jn3Xx2MTw9+/6sz
rhryrs3hUx8EczGAd8bAeQL7DOfBFG5ZygbBwSsgg/5U5+ULd4m5k00tU2p1
sxikwfKC10T8kRQCRq50heK63NQkDxwU72Rl8IdoUdleABIZhGLNOrl+BGUw
HNbWpqlgSPMdF3IfEhja3GBCdtl3TJUfRn4MrNCzmwGrVTkgQxsgURH3lmCJ
GcupVbnx3CmUcM4iS7aCh451qedxptuTV/zYi4p0ZMlLDDp1eCwwFhDtQsxn
j3lMGsY4OgYd2nhGwF6zUJ0PQqbZRRIBqXnAbi7ZPX4luCMEwUOnwBfie3AK
3N1+GVgWdF7zEIRIPAJ4UVZYWxgpQ5cui4gg/A91EDsYSIGSG0YVocuuBnDB
FjRH+v7y4urCzSHiPT83HdvabYdDqrqp5T0ZPAE+YNE5HskXi93h6xof88bK
HM3Y9K0GQ3YZaJXDOOIx8o1qiuY3kj4+a1k+F7+D3u9a8MOnmRFsYbyUJFRy
KMODYOaX1pW5+piiqtbc11UOmq+yULdTC9DXPSkFcSKl1a0xpM3mGsryMI3T
hZM8dNXiNAp6aUo3Ip6qWZFA20HWSHLvIQ0CVSqUzt2xu91ovDCP7Meak3h4
GAOPP2TPQujXZ891zYn6LMRcu2jnl+fJZyvWcNHjarKVREAh4+OD/xb3raUT
qT1ckYp3LtEyseGuC9zXvmkTXh8ARnco8SbZBXvFSjgm+zNwxmUeZIOEszFL
61GBRi59EkLMuKS8uAN8+cqx/Gw+z2Q4buGGDjMqpBCyY4EY294855tVbv9k
B8Z4xOeemC3AXbn5qsPk1CCZPbwgj2m+FCvcvLWNdF23USIJNpZOpxu2W5/F
Hddkq8n46rUcitM/uDeXjRLwVo0VociwuudX9VN/ZGoqxH9PuXLMU9GcF9mS
Jk7g83u4ezyxqvJXrxEwjDRtq/LVb9Babd3r6/ju4c6b7y7v2ZWZaizMxeDz
1hfJRZqTxzPwQveKXhVsi4W0odGsWRc/l1wCuujr1hV9a3CcKX9DRrOFoGnl
XLokIRKcPbqxE3I306DpzK0m1zCM2HR7JKrq3z7cXA/iDIFQLrEtZDAx7fIw
XjXZlDh/1rU9f/78eHF/d3P54dPlv7kWWL2PJOuW8cUK/ePox12pKW0ZgfG4
CvyariJ08Tgu2c1fizpTSropGY28QfmulxsWb8HMLG3MT3fIvQjUjvtyf4FG
boiFrXTyonhz0LCtuuYOLHH/gygCg2c8PfOO8gi9Etb2LY8OwoQKbrqRcFcw
jp+qQ5M0pzotksnqadFNvLEKHPM/cidndh1bl0T1A0nrK5lRJMb2fnZMMJXL
2sdHO3VBoXPM2AvPLbS2Nz9/Xt9ekNURO1Q3Q9G1jAo2EXnusb8dlkvyk/ur
T1yFyTYTwHPUAc+fGc/zaMzHu6b16d8vgmcYxHwC+HASvguNqKtRi6vFcZI8
EpOXqms2Xl1woYNfLveCf0JCYG4JvK5boDUUAggYO7jfQ75mJNnxSjFkxDUH
2KJjxc/fGMrhrEEpQMytvRkiuXMyqG9v3lp5jJqoQTTdiSbvqhtGOhVI1H1j
3D41xcLhe7hNJIBNcTcZgXrQhPzwIJYm5K+sY0TGIo273g4jVwBgLhvJ40qf
70dCZ1KJ6FpiCDJhL8zbeG8ywVv7hAvcPYxZRfRzIcyIjcyprBxWujA0U86R
crm+gWfToMk2ebcRHF+WO0u/qYoMdVKpHQOoNt7v3Rv1cWeSg+4CJy4zOUap
OeZUmnQZ86QGHsguj+et9T6Ke1xKw1YNGSVaP+jVsaFTn6Di6k5raxpnvsqK
B4JqLhRnHh0c//o1GFlwYlqkeZMpW/KQSdJ6ukTsx3IbI0nW4i67gsh4ghil
NB/loRvQuDlnktQ0jmQotk2lv0zpdmTuhK/vOYsCCFtngTNO1m9eQNX4HSLT
uDJrNXp8xAkZvc87jfD2WXhP0ou0d7X1Yzt9fX7OEm3Hv+3WHsY9dgQKiczt
/Ra5YQtuuW1Yk3VhD2VEiIns4Yk6nvb+Lm7ORiI+RIBygCg4/JXWGTUeFW3q
EjfeIT0mvobnq/NXqB8Yj0GUIOVaGuCRTgtoC0OIQMqh+VKGzirKfqBtvu5D
X+H0Tkki2vPMy9q7OdpDiZZF3BbX5hcN6TII7Wb6ZXxhG1RE1vxG2sKFa+pR
bHlUdnAPQnsdzb3ZN9pMMd2BV09ymiAmFmi1xNOurDkgl1e7RGXnGfaOzIAr
WRaljJxCMQFvM+A3tJqa5JwRZIpez7UxY8x35xoGEjaEMHNJUxK9k87YYNDK
nVT6u+o6jlx3CBFH8dusySVrz9oKQWGsH7McaWvIH6It1HoOGUHqD+oTQp7J
NGeJrLmreLXN8CURnWtKNeMuccGIDMq6Aq7uxN116uhzzbKDvFKXSBq5Fj5m
V3P5Q0V3MSZteVY9NZ05El37Un9jxcJkwvHUlL12+Dq7kQyZgquqcDhrgHJz
F3ZqCqNLe5LEGSeBLAYFQi5CCH98uHn494T+YY3WXh9zZ3HXezCSCIUKFBnY
hgaE3Kkl/vLl5ko1RGNITOG5jbHUlDVfPRRJKb+Yir47uv1qGHjNcGRRk0pW
1u3I4r1zg5g1gXvHe5y657CEmQ+3wkIMw7W1NisJOIRvMm2a+v8CUz45PfiP
wOZK3fMrv5z/OTMciQTsR7q8XofavIcwuNCtIWEwMWMTrZZ1M4uwMe26q5No
p/77/vrj/afP+LO2kznhfuE8g0raK7LZEqUr9fSylQ54qCnXkRJovZwRyG+u
L02dcUeO9nxFxm2cRSlIdvfp6/Xn5Prh9+vPH68fAmQ7Pj1CXjJewkwLN+6j
UXujARzYv5TMGevNmtPVDe7CdJq4/+XufsD/K++S9JLDU2nU6ozanVar4ul0
rWTYy6dIrLtrlpsWQ0SbiDuQCfdDMyydiagqZJoX7DwyN8wXbrHVzb8PZ/MF
6NGMWYdkShhF92QakhgotkPPrMmgnLNeJLh0q/aASUqc6a2+y+O6KS6vzs6Q
wsbqCMka/U3gRLZtBnidl7EZHZbNIbS0fz3GWoQAOgzm/uHi4Tq4+ZOj03PX
4BtuXDNEOMBnIebUWvqwnaRsxYcInRRzlGBKAEK9LgF431hkKRO8pCO2uRfT
m7gHDx/nzk22iLEvq9b9K+5xyLJHLGk6IuXbEghdewckj0mPzB8acXPJTIBL
5D0tu2wkkLsBSrn8UBdrU7zkTrBRt0K66XQANuRMJVa/0A7KtgPXh0erxSPR
KnxY0gd5LdzvBLMiguBlV/+7FFVOkECQ7wSJYbEhH5Ltrj9ef37/78mnt/96
ffmQXH76+HD9P5k9MBRuLj5eJPrI5+sPFw83nz4Kt5tUbdAulnNBgUI9s2SU
rqytl6mYql6G/M0zmzC5zFS6yDQ4hXqPW3DtKOx8rBGPmuu0Ye4mYpek68E1
lalQ2y1wcU5MJ9pc7TUC9tIbOAhM+CtmD2LvA6TFB65A95OcXCtVDHi8uhtE
zn9hJV8sVIBdaFLvpiDRswnfxPUV34aq3/Dr0EHfSYfK4UvmklotL8ym6IV2
YeQrtcpOQgajlOZJ0WvrsVArbRSz64zEh0JsUjUiHTldg0jtCeK7Q0LuwSox
VhcoaHCe8mjeTTEb47CQvRH3UA+GkYT8LrgV71WAn+JRK4r3bH9treYmLXZn
kLj0IRDYkC1YQc2ry7BC9sG1XtG+SNLy5N8vPr4Px7uTebIpLOvO/qVhcQvO
RpNucznCrcpLGcYLF7ZVnmb11sae3OyISE/b6fCflQsm9E7qh7RL2KwRq2i5
YJ/L2evqL8J94TzJsx332Vcq+d0XNusA3O2db3WElXYHnojbVE099nr7SSd3
F6SMYEAqf/ilheyHx2MZQMYeBV+WIi5RYEqQU2el+sOo05BAUh2qYBb5btkz
vf7m/m6gs9tn2zJdyW9Jp1rICJCXZJdTKzhhRzSwWTjHl3vIRy7h0ILd4lSc
x+EwNPwNiCy9twJjJ+pruqoW0SGCMwWSDzSpq2TXGcebOIdRH2e7SnOzOa6S
8LDKSFq72ihNi/YO3VRZvTbXNqdy6Rvox0E8IdgaN6tFGowS8ktwkABLyg1d
Gz/oDA07n0OInmHEMJKWFhp1Ifpy0zVYjkpjgP2LQZcl24ZlJpnFybNIlzrB
oxfg8R4+vrG69y7LhO/sL4A9wZja9rkCrkhnZZY741ate8la+3g0lbj+dBt8
OEc4eOBBb+GaKZix5E38uaPrX+i5zG1yw7VXbnqH7JTn3kuHTVdgzXks24wz
mxUgJ1ZcRiKpTJO6XTwtkiydrpGl/yND+0m2ujTzgntVqc9RzSVUmwbFz2H5
iI2wsIQF+EQXKXiSxaK4uh2PERcv29Dg5yziTqKIy5EjwBLLrjP1K9PW6ZV9
TD/RAOrArFNNvLfgpoSnrTzKjzXQlzoTI2aPApkaa0lEdg6FSA+GZKegX6SN
cFU3Qt8K+Adk3sHURqa/h4wrDYeIjUyG+8IZ7yj6p6Rb+amvuflmPyV8tK5s
hvcShPHFG0KFYe2GhGrfvr8T2a/5FlIgBwd4z2oLV382dYpSRKEGVmaTtFG/
svzC5+zPeEnni2w0L594eTDeJnLath8s0K/qjpXIGD3QKTfqxuMW4NK1d1Zz
ex9XKhV0eTE3mssp0kwq3zk55WA9nDtklqcWreUcjZ0qSYztzRtLJ+AOBJbh
FHJ+x4hb1yTs2Rp3NwiTuRZSFiw32wJWljcl3U1dFElLelvX/9O5K4PQhhCN
tUV21b/S8Ydp2tyYmpmtPu5OJ068JkjI1ficHNnap7a0W+m559schhlB2qNv
SCSITK0d63+Wbn0n0PjuMnJhcu2YhVr17McyR2dAUtlal7QnBNioUuPIdx6K
LKM7iNGE5Sjo2xuB0kXH2kiDpcb3Vx/jsfdx19pKzVXAKlqxufKYcXVUJCqD
pYMGmaOm07Cx00kF5SCu6niFViLi1f7FsKw458rnfPXR0ChZZmnBzZltcspj
OGTAd7xxU2iOYfKPg4k0mv7baPdO68g3DLptO3bLY5L5nC6ZxpJbw0ysoO0C
pIL0Hmg8SbKQFcJsK6syQrFHp+CGIOBa1+kcBq9oouh/yrq3ibtJtZmmszSv
k7xu50kzKxOCdGIzHBJVb4QhQf+baZhUPVHRPEstrOWTEpgMO54JSaoWY6xi
x6lU4a7FpEt9CQGYWdAF1BSuN1GkDNvzOH+wN3F8UXp6Ah+EfoVLWqUz6xIc
rbUdiGvXEJjPz3s6fXpf9DvRzCNiM4wnHYOBM0dnmdf/pQWFp0puXhz9F96s
vFPGXXXbNAsqT8So56jcKO6mlq04ZiolccDNoeuNJgpwJExBu7lwJ4fpd/QD
RsbBHr26kIPl49iImsw3smY0B3eKfPc11ZbdURuX+Y5c6uehnUYQTHQeNvtS
t0bLHeg6XdhZl7LWulU6G0p6L0o3votRgIKnqQXLY9LnZMh8ryHdpcl6TlXv
56NshLZdq7wkhq5dag3qInb02cHQMfHdq+ZECmmCHplb5eDXL/oFPGyx1FIQ
yifgoJ4ondZqUIZhEHHuWW4JcdobB0cZu2r5Xj4rsp52T/wunQnhVw9ISV49
dEOBOQGejR5rF8meLm6CFse3pAbgdixWVXb35LKQeUCuNG4kiZG0VSLt3ElP
4Z6B3FkoZ6EsPQ1ieVY3LN7Qvu9vYgXiqCB6tIy8dPYnSRXIAHaP0xpzyeSc
VeX/2cY78wmVO9GvwnJZmQ8V35KSLZo67ETLiEGyJds5e7lH1fd0RaZ3Mp0S
OSWrnCR7niwI6ZuEB9EhFoVm/E2nlFqHgoWGvZmEMhvjT2u6znqhGihRYKDE
/RYlKwUS/jq2uKoR5vsjvHzvRy/H3LO7/x7/IbtPHL+PKAlr4g9HXVHpuoU6
i2AtPZ/n+STsY4ZMDB88Q77DSjV27rrvKN65zsN4rXrkXa8FX/SPWp4fPAH+
mYo5yyvRrB3zam5Ya+n0yuMgRzgVeyrd0LV5vXCJu8tr36SfgbPjhAqRQW3a
vVwIl00QFORb/uQ9B1ecNt9s/tp8zxNiyt1BDWHVbcrKI2scoWRx8RRN9Y6u
Lrsz9Jy7hDNyw+yePSh287JCXhC6FZz7y83D/uOWmN+i1k69uNuryzjBu5hP
IAKbRn36G7agcsHYZxag8E4X/iAsI8MtZYHBi1fg+iAE3jjM73HF3A9kvjTm
TXAmlBjc63wl1pN4ZW18KL23f3dzK2AcdNvkGYmKE8u6MBbVVLVt/m5ZwXNu
yU4WjOhdo8kw2X6NtoW7I8mFaNHl7d0AyASgZTH+GigoPEb63SDsntx0/WHO
DHZq7cT1JnHVXGIJeH83ewCgOOLtne4aWknUuMHFuwai+cVijq5yR3hdRg4O
5clmZ7Prw/3AzHgfCELnUQ5oSE2RtuoUp61vss+bn0nDSu9eYOmtYQnV+4Jl
LNreIBdVuL60mOYYtXz0Hj52tb5P103osnrQSornqNq8nIZZT2KOZzuapljp
4hpwJXZNJ3OLQaRNU7nVa7NT4NcPqihD+0bcLdJ5L5zGIz0PPKGIAc08mu2O
YPILz1jgag1WvBcEAImyIcex2SzQp6LxJiluCxutyjdx7wMIm8vvgDWup0+Q
BzY0L0ugebsE8is2MbVwd+cxEuKa8MtfWzOPbg+A27BGHvMAOVHYcjiDBgXh
6dSEVF8U3NYpZjGzSdFN0/W2fDRhTYiOi2bya9GIwnl//i3Ew6HnVOuslHG0
XA3j4jPOBWVNEPCC8c1nWPs8LZOQ8GKKmnHa0oLFAfAxRXN9HOgd1I+3KEkU
BZW9r+z0ZB+n3Feu03jiS56qR/CJov+NjA4e51rVbwS9GlW6lcJUlaLNz3ko
r2Hf6D+EIlYyocDZlGH56bJqNNdePGdvxuMFqSybyWharcZtldXceV1oAz0o
7ji3lQhisiI8Ez+qucXvNkWRaItzTbIxh5aMCWQ3wp+VXlGbpSu2A9TlLbWo
tOqW0BEmO4Hi4OCNZsm7ugX64+EbpLtlyIdJ5Ndx3L+tljyI5K1ZtwMSap32
au12Tewm/8F9WhigWDZsN8na66ThipOhSyPyMXi+eTrLGq6ZkW7CrgP6uxux
5Is9Z+FcpYnNVRoqb+70jmCKcbZ8YBCbaQ7sODh6Q2puyUVVpCHiIJiRSOJu
CF4iiWZa/OBZiyi9+pjse+qARyYyhGCf9kZqZXRwDPjSE/9KVB0/ADCbmsuj
3E/ooZM38R/asd3Nicx/bMCGUl4fibzW1IXb3OhEuaDxhThQqwnSh4GH9AhC
xWpoStzcZk1z/lnKhUs8qcRWQYz34JVhhJ6+kRystNg2uaWuAWGbaSV9hYkI
cqECghM3/js6GkX/D2yXKEC8+wAA

-->

</rfc>