Observations on "Link" in MANET/Autoconf and Other Contexts
draft-templin-manet-autoconf-link-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2006-08-28 | ||
| 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
Mobile Ad-hoc Networks (MANETs) comprise MANET routers, and connect to other networks via one or more MANET border routers. MANET routers communicate over semi-broadcast links which present interesting considerations for the classical IP model that are subject matter for this document. In particular, the term "link" requires careful examination in MANET/Autoconf and other contexts.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)