Painless Class 1 Devices Programming
draft-hahm-lwig-painless-constrained-programming-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Oliver Hahm , Emmanuel Baccelli , Kaspar Schleiser | ||
| Last updated | 2013-09-12 (Latest revision 2013-03-11) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In order to fit the constraints of Class 0 devices (offering much less than 10KiB of RAM and 100KiB of ROM) there are no alternatives to implementing IP protocols in special software environments, which impose programming paradigms that make implementation of protocol specifications significantly more complex. However, our experience implementing RFC 4944 and RFC 6282, TCP and UDP on Class 1 devices (offering approximately 10KiB of RAM and 100KiB of ROM) shows that there are alternatives concerning software environments in which to implement IP protocols, which avoid such complexity by providing a more developer-friendly environment. This draft shares this experience.
Authors
Oliver Hahm
Emmanuel Baccelli
Kaspar Schleiser
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)