Sloppy Topology Updates for ad-hoc Routing Protocols (STURP)
draft-lou-manet-sturp-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhe Lou , Luigi Iannone , Dirk Trossen , Zhaochen Shi | ||
| Last updated | 2024-12-29 (Latest revision 2024-06-27) | ||
| 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 memo describes an approach to updating topologies in typical MANET-like environments, relying on what is termed 'sloppy updates' in the remainder of this document. Key to the approach is that updates are only initiated if existing communication relations may be effect by non-synchronized topology information, otherwise using the topology information as it exists. This 'sloppy' nature of the approach reduces the needed updates and the associated communication for them, thus increases efficiency as well as performance from a user perspective.
Authors
Zhe Lou
Luigi Iannone
Dirk Trossen
Zhaochen Shi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)