Design Considerations for Low Power Internet Protocols
draft-ayers-low-power-interop-01

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Replaces draft-hudson-ayers
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Independent Submission                                          H. Ayers
Internet-Draft                                                  P. Levis
Intended status: Informational                       Stanford University
Expires: January 14, 2021                                  July 13, 2020

         Design Considerations for Low Power Internet Protocols
                    draft-ayers-low-power-interop-01

Abstract

   Low-power wireless networks provide IPv6 connectivity through
   6LoWPAN, a set of standards to aggressively compress IPv6 packets
   over small maximum transfer unit (MTU) links such as 802.15.4.

   The entire purpose of IP was to interconnect different networks, but
   we find that different 6LoWPAN implementations fail to reliably
   communicate with one another.  These failures are due to stacks
   implementing different subsets of the standard out of concern for
   code size.  We argue that this failure stems from 6LoWPAN's design,
   not implementation, and is due to applying traditional Internet
   protocol design principles to low-power networks.

   We propose three design principles for Internet protocols on low-
   power networks, designed to prevent similar failures in the future.
   These principles are based around the importance of providing
   flexible tradeoffs between code size and energy efficiency.  We apply
   these principles to 6LoWPAN and show that the modified protocol
   provides a wide range of implementation strategies while allowing
   implementations with different strategies to reliably communicate.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 14, 2021.

Ayers & Levis           Expires January 14, 2021                [Page 1]
Internet-Draft                 Design-Low                      July 2020

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  6LoWPAN Today . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Traditional Principles: Not Low-Power . . . . . . . . . . . .  10
   5.  Three Principles  . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Principle 1: Capability Spectrum  . . . . . . . . . . . .  10
     5.2.  Principle 2: Capability Discovery . . . . . . . . . . . .  11
     5.3.  Principle 3: Explicit and Finite Bounds . . . . . . . . .  12
   6.  A Principled 6LoWPAN  . . . . . . . . . . . . . . . . . . . .  12
     6.1.  Principle 1: Capability Spectrum  . . . . . . . . . . . .  13
     6.2.  Principle 2: Capability Discovery . . . . . . . . . . . .  16
     6.3.  Principle 3: Provide Reasonable Bounds  . . . . . . . . .  16
   7.  Evaluation  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     7.1.  Implementations . . . . . . . . . . . . . . . . . . . . .  17
     7.2.  Compile-Time Costs  . . . . . . . . . . . . . . . . . . .  18
     7.3.  Run-time Performance  . . . . . . . . . . . . . . . . . .  20
   8.  Discussion and Conclusions  . . . . . . . . . . . . . . . . .  21
   9.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .  22
     9.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .  22
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  22
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  22
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  22
     12.2.  Informative References . . . . . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  25

1.  Introduction
Show full document text