Internet DRAFT - draft-ahn-manet-multipath-requirement

draft-ahn-manet-multipath-requirement



MANET Working Group                                         Sanghyun Ahn 
Internet Draft                                       University of Seoul
Expires: June 13, 2016                                 December 22, 2015 

                                     
           Requirements on Multipath Routing Protocols for MANET
               draft-ahn-manet-multipath-requirement-00.txt 

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.  This document may not be modified,
   and derivative works of it may not be created, except to format it
   for publication as an RFC or to translate it into languages other
   than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on June 13, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (http://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.







Ahn                      Expires June 13, 2016                  [Page 1]

Internet-Draft Requirements on Multipath Routing Protocols December 2015


Abstract

   This document describes the requirements on the protocols providing
   multiple routes between a given source and destination node pair
   in a mobile ad hoc network (MANET). For this, the conditions to be
   considered in defining a MANET multipath routing protocol are
   listed.


Table of Contents

   1.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  ? 
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Requirements on MANET Multipath Routing Protocols. . . . . . .  3
   4.  Other Considerations . . . . . . . . . . . . . . . . . . . . .  4
   References . . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .  4


































Ahn                      Expires June 13, 2016                  [Page 2]

Internet-Draft Requirements on Multipath Routing Protocols December 2015


1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   
2.  Introduction

   The mobile ad hoc network (MANET) is composed of a number of mobile
   nodes which can communicate with each other through multiple
   wireless links without the help of a wired infrastructure.
   Therefore, in the MANET, the route connectivity tends to be very
   unstable. This route unstability can be mitigated by providing more
   than one route to a source and destination node pair. In recent
   years, there have been intensive studies done on multipath routing
   protocols for the MANET [1]. Also, multipath routing protocols may
   have the advantage of providing load balancing by distributing data
   traffic to a number of routes. On the other hand, it may incur more
   control message overhead to set up multiple routes.

   In this draft, we define the requirements on MANET multipath
   routing protocols.


3.  Requirements on MANET Multipath Routing Protocols

   MANET multipath routing protocols MAY consider the following
   conditions:

   - the number of routes for a given pair of source and destination
     nodes
   - the disjointness of the routes between a source and destination
     node pair
   - the control message overhead for establishing a given number of
     routes
   - the base MANET unicast routing protocol, such as AODV [2] or DSR
     [3], on which the multipath routing protocol is defined
   - the degree of changes on the base MANET unicast routing protocol

   With considering the above-mentioned conditions, a MANET multipath
   routing protocol SHOULD satisfy the following requirements:









Ahn                      Expires June 13, 2016                  [Page 3]

Internet-Draft Requirements on Multipath Routing Protocols December 2015


   - The control message overhead incurred by a MANET multipath routing
     protocol SHOULD NOT overwhelm the data traffic in the network.
     Or, more definitively, it SHOULD NOT exceed a certain portion of
     the total amount of the network traffic. The latter is more
     definitive, but achieving this may not be feasible.
   - The modifications and/or extensions on the base MANET unicast
     routing protocol SHOULD NOT hinder the operation of the base MANET
     unicast routing protocol.
   - The number of routes provided for a given source and destination
     node pair SHOULD be controlled adaptively so that the multiple
     routes do not increase the amount of routing information
     maintained in a router unnecessarily.
 
  
4.  Other Considerations

   TBD


References

   [1] M. Tarique, K. E. Tepe, S. Abidi and S. Erfani, "Survey of
       Multipath Routing Protocols for Mobile Ad Hoc Networks," Journal
       of Network and Computer Applications, November 2009.
   [2] C. Perkins, E. Belding-Royer and S. Das, "Ad hoc On-Demand
       Distance Vector (AODV) Routing," RFC 3561, July 2003.
   [3] D. Johnson, Y. Hu and D. Maltz, "The Dynamic Source Routing
       Protocol," RFC 4728, February 2007.
              

Author's Address

   Sanghyun Ahn 
   University of Seoul 
   90, Cheonnong-dong, Tongdaemun-gu 
   Seoul 130-743
   Korea 
   Email: ahn@uos.ac.kr













Ahn                      Expires June 13, 2016                  [Page 4]