DSR Extensions for the Resolution of Cached Route Reply Implosion
draft-ahn-manet-dsr-crri-02

Document Type Active Internet-Draft (individual)
Last updated 2017-11-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MANET Working Group                                         Sanghyun Ahn 
Internet Draft                                       University of Seoul
Expires: May 23, 2018                                  November 30, 2017 

                                     
   DSR Extensions for the Resolution of Cached Route Reply Implosion
                   draft-ahn-manet-dsr-crri-02.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 May 23, 2018.

Copyright Notice

   Copyright (c) 2017 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 May 23, 2018                   [Page 1]

Internet-Draft DSR Extensions for the Resolution of Cached November 2017

Abstract

   In DSR, a node can generate a route reply in response to a received
   route request if it has a fresh route to the destination in its
   route cache. However, this can incur the cached route reply
   implosion problem and DSR just tries to mitigate this problem
   by reducing the possibility of cached route reply collisions.
   This document describes how DSR can be extended for the resolution
   of the cached route reply problem. 

Table of Contents

   1.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  3 
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Extensions on DSR Route Request Option . . . . . . . . . . . .  3
   4.  Operations Related to C Flag . . . . . . . . . . . . . . . . .  5
   5.  Other Considerations . . . . . . . . . . . . . . . . . . . . .  6
   References . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .  6  

Ahn                     Expires May 23, 2018                    [Page 2]

Internet-Draft DSR Extensions for the Resolution of Cached November 2017

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 DSR protocol [1] works based on the source routing mechanism
   and support multiple routes between a source and destination node
   pair by maintaining several routes in the route cache at the source.
   However, in DSR, the route reply storm problem can happen
   because of route replies generated by intermediate nodes with fresh
   routes to the destination in their own route caches (i.e., cached
   route replies). DSR tries to solve this route reply storm problem
   by reducing the possibility of route reply collisions with adding
   a short jitter delay before the broadcast of a route reply.
   However, DSR does not try to resolve the cause of the route reply
   storm problem.

   The main reason of the route reply storm is uncontrolled
   generation of route replies at intermediate nodes, i.e., cached
   route replies. Therefore, a mechanism to control the generation of
   route replies at intermediate nodes is required for the effective
   operation of DSR. However,for the support of multipath routing,
   too tight restriction (control) on route reply generation may not be
   desirable. Therefore, when controlling the generation of route
   replies, both of these aspects need to be considered. In this draft,
   we describe how DSR Options header has to be extended to support
   the control of generation route replies.

3.  Extensions on DSR Route Request Option
Show full document text