Manet = Munchkins?

Jim Whitehead (ejw@ics.uci.edu)
Thu, 12 Jun 1997 11:08:20 -0700


Probably not, but perhaps of interest.

- Jim

>To: IETF-Announce@ietf.org
>cc: all-ietf@ietf.org
>Subject: WG ACTION: Mobile Ad-hoc Networks (manet)
>Date: Thu, 12 Jun 1997 12:21:44 -0400
>Sender:ietf-announce-request@ietf.org
>From: Cynthia Clark <cclark@ietf.org>
>
>
>A new working group has been formed in the Routing Area
>of the IETF. For additional information, contact the Area Directors
>or the WG Chair.
>
>Mobile Ad-hoc Networks (manet)
>------------------------------
>
> Chair(s):
> Scott Corson <corson@isr.umd.edu>
> Joseph Macker <macker@itd.nrl.navy.mil>
>
> Routing Area Director(s):
> Joel Halpern <jhalpern@newbridge.com>
>
> Mailing lists:
> General Discussion:manet@itd.nrl.navy.mil
> To Subscribe: majordomo@itd.nrl.navy.mil
> In Body: subscribe manet
> Archive:
>
>Description of Working Group:
>
>A "mobile ad-hoc network" is an autonomous system of mobile routers (and
>associated hosts) connected by wireless links--the union of which form an
>arbitrary graph. The routers are free to move randomly and organize
>themselves arbitrarily; thus, the network's wireless topology may change
>rapidly and unpredictably. Such a network may operate in a standalone
>fashion, or may be connected to the larger Internet.
>
>The focus of the working group will be to standardize an intra-domain
>unicast routing protocol which efficiently reacts to topological changes
>while maintaining effective routing. The goal is to support networks
>scaling up to hundreds of routers. If this proves successful, future work
>may include development of other protocols to support additional routing
>functionality.
>
>The working group will examine the security issues around this protocol.
>They will consider the intended usage environments, and the threats that
>are (or are not) meaningful within that environment.
>
>
> Goals and Milestones:
>
> Jul 97 Post as an informational Internet-Drafts a discussion of mobile
> ad-hoc networking and issues.
>
> Aug 97 Obtain early performance results for the protocols
>
> Dec 97 Implement the various protocols and test
>
> Apr 98 Reach consensus on a mobile, ad-hoc unicast routing protocol.
>
> Jul 98 Document mobile ad-hoc routing protocol and submit to the IESG
> as a proposed standard, including security threat analysis.
>