Mobile Ad-hoc Networks (manet) Internet Drafts
| Dynamic MANET On-demand (DYMO) Routing | |||||||||||||||||
|
The Dynamic MANET On-demand (DYMO) routing protocol is intended for use by mobile routers in wireless, multihop networks. DYMO determines unicast routes among DYMO routers within the network in an on-demand fashion, offering improved convergence in dynamic topologies. | ||||||||||||||||
| Simplified Multicast Forwarding for MANET | |||||||||||||||||
|
This document describes a Simplified Multicast Forwarding (SMF) mechanism that provides basic IP multicast forwarding suitable for wireless mesh and mobile ad hoc network (MANET) use. SMF specifies techniques for multicast duplicate packet detection (DPD) to assist the forwarding process. SMF also specifies DPD maintenance and checking operations for with both IPv4 and IPv6. SMF takes advantage of reduced relay sets for efficient MANET multicast data distribution within a mesh topology. The document describes interactions with other protocols and multiple deployment approaches. Algorithms for selecting reduced relay sets and related discussion are provided in the Appendices. Basic issues relating to the operation of multicast MANET border routers are discussed but ongoing work remains in this area beyond the scope of this document. | ||||||||||||||||
| The Optimized Link State Routing Protocol version 2 | |||||||||||||||||
|
This document describes version 2 of the Optimized Link State Routing (OLSRv2) protocol. The protocol embodies an optimization of the classical link state algorithm tailored to the requirements of a Mobile Ad hoc NETwork (MANET). The key optimization in OLSRv2 is that of multipoint relays (MPRs), providing an efficient mechanism for network-wide broadcast of link state information (i.e. reducing the cost of performing a network- wide link state broadcast). A secondary optimization is that OLSRv2 employs partial link state information; each node maintains information about all destinations, but only a subset of links. Consequently, only selected nodes flood link state advertisements (thus reducing the number of network-wide link state broadcasts) and these advertisements contain only a subset of links (thus reducing the size of network-wide link state broadcasts). The partial link state information thus obtained still allows each OLSRv2 node to at all times maintain optimal (in terms of number of hops) routes to all destinations in the network. OLSRv2 imposes minimum requirements on the network by not requiring sequenced or reliable transmission of control traffic. Furthermore, the only interaction between OLSRv2 and the IP stack is routing table management. OLSRv2 is particularly suitable for large and dense networks as the technique of MPRs works best in this context. | ||||||||||||||||
| Generalized MANET Packet/Message Format | |||||||||||||||||
|
This document specifies a packet format capable of carrying multiple messages that may be used by mobile ad hoc network routing protocols. | ||||||||||||||||
| MANET Neighborhood Discovery Protocol (NHDP) | |||||||||||||||||
|
This document describes a 1-hop and symmetric 2-hop neighborhood discovery protocol (NHDP) for mobile ad hoc networks (MANETs). | ||||||||||||||||
| IANA Allocations for MANET Protocols | |||||||||||||||||
|
This document enumerates several common IANA allocations for use by MANET protocols. The following well-known numbers are required: a UDP port number, an IP protocol number, and a link-local multicast group address. | ||||||||||||||||
| Representing multi-value time in MANETs | |||||||||||||||||
|
This document describes a general and flexible TLV (type-length-value structure) for representing time using the generalized MANET packet/ message format. It defines two message and two address block TLVs for representing validity and interval times for MANET routing protocols. | ||||||||||||||||
| Definition of Managed Objects for the DYMO Manet Routing Protocol | |||||||||||||||||
|
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring aspects of the DYMO routing process. The DYMO MIB also reports state information, performance metrics, and notifications. In addition to configuration, this additional state and performance information is useful to management stations troubleshooting routing problems. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Mobile Ad-hoc Networks (manet)
In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:
Additional MANET Page
Last Modified: 2008-04-23
Additional information is available at tools.ietf.org/wg/manet
Chair(s):
Routing Area Director(s):
Routing Area Advisor:
Mailing Lists:
General Discussion: manet@ietf.orgTo Subscribe: manet-request@ietf.org
In Body: subscribe manet
Archive: http://www.ietf.org/mail-archive/web/manet/index.html
Description of Working Group:
The purpose of the MANET working group is to standardize IP routingprotocol functionality suitable for wireless routing application within
both static and dynamic topologies with increased dynamics due to node
motion or other factors.
Approaches are intended to be relatively lightweight in nature,
suitable
for multiple hardware and wireless environments, and address scenarios
where MANETs are deployed at the edges of an IP infrastructure. Hybrid
mesh infrastructures (e.g., a mixture of fixed and mobile routers)
should also be supported by MANET specifications and management
features.
Using mature components from previous work on experimental reactive and
proactive protocols, the WG will develop two Standards track routing
protocol specifications:
- Reactive MANET Protocol (RMP)
- Proactive MANET Protocol (PMP)
If significant commonality between RMRP and PMRP protocol modules is
observed, the WG may decide to go with a converged approach. Both IPv4
and IPv6 will be supported. Routing security requirements and issues
will also be addressed.
The MANET WG will also develop a scoped forwarding protocol that can
efficiently flood data packets to all participating MANET nodes. The
primary purpose of this mechanism is a simplified best effort multicast
forwarding function. The use of this protocol is intended to be applied
ONLY within MANET routing areas and the WG effort will be limited to
routing layer design issues.
The MANET WG will pay attention to the OSPF-MANET protocol work within
the OSPF WG and IRTF work that is addressing research topics related to
MANET environments.
Goals and Milestones:
| Done | Post as an informational Internet-Drafts a discussion of mobile ad-hoc networking and issues. | |
| Done | Agenda bashing, discussion of charter and of mobile ad hoc networking draft. | |
| Done | Discuss proposed protocols and issues. Redefine charter. | |
| Done | Publish Informational RFC on manet design considerations | |
| Done | Review the WG Charter and update | |
| Done | Submit AODV specification to IESG for publication as Experimental RFC | |
| Done | Develop I-D for potential common manet encapsulation protocol approach | |
| Done | Submit initial I-D(s) of candidate proposed routing protocols and design frameworks | |
| Done | Promote implementation, revision, and testing of initial proposed I-D(s) | |
| Done | Explore basic performance and implementation issues of initial approaches | |
| Done | Explore proposed proactive protocol design commonalities | |
| Done | Submit DSR specification to IESG for publication as Experimental RFC | |
| Done | Submit OLSR specification to IESG for publication as Experimental RFC | |
| Done | Submit TBRPF specification to IESG for publication as Experimental RFC | |
| Done | Develop a further focused problem statement and address an approach for a common engineering work effort | |
| Done | Reevaluate the WG's potential based on the problem statement consensus | |
| Done | Submit initial ID of RMP for WG review | |
| Done | Submit initial ID of PMP for WG review | |
| Done | Submit inital ID of generalized MANET flooding approach | |
| Done | Revise WG documents and review | |
| Done | Document initial implementation progress and experience Revise documents based upon implementation experience | |
| Done | Submit initial WG ID on Neighborhood Discovery (NHDP) | |
| Dec 2006 | Submit PacketBB to IESG | |
| Dec 2006 | Submit initial WG ID on MIB for NHDP, DYMO, OLSRv2 | |
| Apr 2007 | Submit NHDP to IESG | |
| Apr 2007 | Submit DYMO to IESG | |
| Apr 2007 | Submit OLSRv2 to IESG | |
| Apr 2007 | Submit SMF to IESG |
Internet-Drafts:
Dynamic MANET On-demand (DYMO) Routing (80640 bytes)Simplified Multicast Forwarding for MANET (134584 bytes)
The Optimized Link State Routing Protocol version 2 (145280 bytes)
Generalized MANET Packet/Message Format (142203 bytes)
MANET Neighborhood Discovery Protocol (NHDP) (113207 bytes)
IANA Allocations for MANET Protocols (11661 bytes)
Representing multi-value time in MANETs (24908 bytes)
Definition of Managed Objects for the DYMO Manet Routing Protocol (62536 bytes)
Request For Comments:
Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation Considerations (RFC 2501) (28912 bytes)Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) (90356 bytes)
Optimized Link State Routing Protocol (RFC 3626) (161265 bytes)
Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) (RFC 3684) (107963 bytes)
The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4 (RFC 4728) (265706 bytes)
Jitter considerations in Mobile Ad Hoc Networks (MANETs) (RFC 5148) (26379 bytes)
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
