Why Reactive Protocols are Ill-Suited for LLNs
draft-tripathi-roll-reactive-applicability-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Joydeep Tripathi , Jaudelice C. de Oliveira , C. Chauvenet, JP Vasseur | ||
| Last updated | 2014-07-21 (Latest revision 2014-01-06) | ||
| 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
This document describes serious issues and shortcomings regarding the use of reactive routing protocols in low power and lossy networks (LLNs). Routing requirements for various LLN deployments are discussed in order to judge how reactive routing may or may not adhere to the necessary criteria.
Authors
Joydeep Tripathi
Jaudelice C. de Oliveira
C. Chauvenet
JP Vasseur
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)