Skip to main content

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

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Hudson Ayers , P Levis
Last updated 2022-01-27 (Latest revision 2021-02-11)
Replaces draft-hudson-ayers
RFC stream Independent Submission
Intended RFC status Informational
Formats
Stream ISE state In ISE Review
Revised I-D Needed
Consensus boilerplate Unknown
Document shepherd Eliot Lear
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to rfc-ise@rfc-editor.org

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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.

Authors

Hudson Ayers
P Levis

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)