On Lightweight and Embedded IP Programming Interfaces

Document Type Expired Internet-Draft (individual)
Last updated 2012-09-06 (latest revision 2012-03-05)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document takes a look at various aspects of Application Programming Interfaces (APIs) used in embedded sensors and controller applications such as IP Smart Objects and IP based Wireless Sensor Networks. These devices may be interconnected via many different types of media, including 802.15.4 (lowpans), power line control (PLC), RS485, but the common characteristic is that the devices have extremely limited code space and memory space for both the stack and application. Just as there is no one single API for IP networking stacks today (though the "Berkeley sockets" might be considered de- facto standard) there is not likely to be a single standard in the embedded space, but there can be some common understanding about facilities that can and should be provided to the application developer.


Carl Williams (carlw@mcsr-labs.org)
Geoffrey Mulligan (geoff@proto6.com)

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