<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC4861 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4861.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- used by XSLT processors -->
<!-- OPTIONS, known as processing instructions (PIs) go here. -->
<!-- For a complete list and description of PIs,
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable PIs that most I-Ds might want to use. -->
<?rfc strict="yes" ?> <!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC): -->
<?rfc toc="yes"?> <!-- generate a ToC -->
<?rfc tocdepth="2"?> <!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references: -->
<?rfc symrefs="yes"?> <!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?> <!-- sort the reference entries alphabetically -->
<!-- control vertical white space: 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?> <!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?> <!-- keep one blank line between list items -->
<!-- end of popular PIs -->
<rfc category="bcp" docName="draft-ietf-v6ops-reducing-ra-energy-consumption-00" ipr="trust200902">
  <front>
    <title abbrev="Reducing RA energy consumption">Reducing energy consumption of Router Advertisements</title>
    <author fullname="Andrew Yourtchenko" initials="A" surname="Yourtchenko">
      <organization>cisco</organization>
      <address>
        <postal>
      <street>7a de Kleetlaan</street>
      <city>Diegem</city>
      <region>1831</region>
<!-- <code/> -->
      <country>Belgium</country>
        </postal>
      <phone>+32 2 704 5494</phone>
<!-- <facsimile/> -->
      <email>ayourtch@cisco.com</email>
<!-- <uri/> -->
      </address>
    </author>
    <author fullname="Lorenzo Colitti" initials="L" surname="Colitti">
      <organization>Google</organization>
      <address>
        <postal>
          <street>Roppongi 6-10-1</street>
          <city>Minato</city>
          <region>Tokyo</region>
          <code>106-6126</code>
          <country>JP</country>
        </postal>
<!-- <phone/> -->
<!-- <facsimile/> -->
      <email>lorenzo@google.com</email>
<!-- <uri/> -->
      </address>
    </author>
    <date year="2015" />
    <area>General</area>
    <workgroup>IPv6 Operations</workgroup>
    <keyword>Neighbour Discovery</keyword>
    <keyword>IPv6</keyword>
    <abstract>
      <t>Frequent Router Advertisement messages can severely impact host power consumption. This document recommends operational practices to avoid such impact.
      </t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction">
      <t>Routing information is communicated to IPv6 hosts by Router Advertisement messages. If these messages are too frequent, they can severely impact power consumption on battery-powered hosts.</t>
      <t>
          The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
          "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
          this document are to be interpreted as described in
          <xref target="RFC2119"/>.
      </t>
    </section>
    <section title="Problem scenarios">
      <section title="Solicited multicast RAs on large networks">
        <t>On links with a large number of battery-powered devices, sending solicited Router Advertisements multicast can severely impact host power consumption. This is because every time a device joins the network, all devices on the network receive a multicast Router Advertisement. In the worst case, if devices are continually joining and leaving the network, and the network is large enough, then all devices on the network will receive solicited Router Advertisements at the maximum rate specified by section 6.2.6 of <xref target="RFC4861"/>, which is one every 3 seconds.</t>
      </section>
      <section title="Frequent periodic Router Advertisements">
        <t>Some networks send periodic multicast Router Advertisements (e.g., once every few seconds). This may be due to a desire to ensure that hosts always have access to up-to-date router information.</t>
      </section>
    </section>

    <section title="Consequences">
      <t>Observed reactions to frequent Router Advertisement messages by battery-powered devices include:</t>
      <t><list style="symbols">
        <t>Some hosts simply experience bad battery life on these networks and otherwise operate normally. This is frustrating for users of these networks.</t>
        <t>Some hosts react by dropping all Router Advertisement messages when in power saving mode on any network, e.g., <eref target="https://code.google.com/p/android/issues/detail?id=32662"/>. This causes devices to lose connectivity when in power-saving mode, potentially disrupting background network communications, because the device is no longer able to send packets or acknowledge received traffic.</t>
        <t>Some hosts react by dropping *all* IPv6 packets when in power saving mode, <eref target="http://www.gossamer-threads.com/lists/nsp/ipv6/54641"/>. This disrupts network communications.</t>
        </list></t>
        <t>Compounding the problem, when dealing with devices that drop Router Advertisements when in power saving mode, some network administrators work around the problem by sending RAs even more frequently. This causes devices to engage in even more aggressive filtering.</t>
    </section>


    <section title="Recommendations">
      <t><list style="numbers">
        <t>Router manufacturers SHOULD allow network administrators to configure the routers to respond to with unicast Router Advertisements to Router Solicitations if:
        <list style="symbols">
          <t>The Router Solicitation's source address is not the unspecified address, and:</t>
          <t>The solicitation contains a valid Source Link-Layer Address option.</t>
        </list></t>
        <t>Networks that serve large numbers (tens or hundreds) of battery-powered devices SHOULD enable this behaviour.</t>
        <t>Networks that serve battery-powered devices SHOULD NOT send multicast RAs too frequently (e.g., more than one every 5-10 minutes for current battery-powered devices) unless the information in the RA packet has substantially changed. If there is a desire to ensure that hosts pick up configuration changes quickly, those networks MAY send frequent Router Advertisements for a limited period of time (e.g., not more than one minute) immediately after a configuration change.</t>
      </list></t>
      <t>No protocol changes are required. Responding to Router Solicitations with unicast Router Advertisements is already allowed by section 6.2.6 of <xref target="RFC4861"/>, and Router Advertisement intervals are already configurable by the administrator to a wide range of values.</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>The authors wish to thank Steven Barth, Erik Kline, Erik Nordmark, Alexandru Petrescu, and Mark Smith for feedback and helpful suggestions.
      </t>
    </section>
    <section anchor="IANA" title="IANA Considerations">
      <t>
None.
      </t>
    </section>
    <section anchor="Security" title="Security Considerations">
      <t>None.</t>
    </section>
  </middle>
  <back>
    <references title="Normative References">
      &RFC2119;
      &RFC4861;
    </references>
  </back>
</rfc>
