Topology Refresh Protocol (TRP)
draft-peterlau-manet-topology-refresh-00

Document Type Active Internet-Draft (individual)
Last updated 2017-01-03
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)
Mobile Ad hoc Networks Working Group                              P. Lau
Internet-Draft                                 The University of Memphis
Intended status: Experimental                           December 31,2016
Expires: July 3, 2017

                  Topology Refresh Protocol (TRP)
             draft-peterlau-manet-topology-refresh-00

Abstract

   The topology refresh protocol is intended for use in mobile social
   networks where user nodes announce their presence when they move into
   contact with the network, see all existing users, know when old users
   have left the network and new ones join the network, and communicate
   with each other over optimal paths established on the fly.  TRP is a
   very lightweight protocol but does require user nodes periodically
   broadcast their ids along with some personal information to the
   network.  These broadcasts serve the dual purpose of announcing
   users' presence in the social network and establishing a complete
   topology of end-to-end optimal paths.  Individual user controls her
   "radius of users" based on the number of hops and physical distance
   between her and the others.  User nodes independently choose their
   ids and dynamically resolve any duplicated ones.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF). Note that other groups may also distribute
   working documents as Internet-Drafts. The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.
   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."

   This Internet-Draft will expire on July 3, 2017.

Copyright Notice

   Copyright (c) 2016 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Applicability Statement . . . . . . . . . . . . . . . . . . .   3
   6.  Generic Message Formats . . . . . . . . . . . . . . . . . . .   4
   7.  Forwarding Table Entry  . . . . . . . . . . . . . . . . . . .   6
   8.  Type 2 Control Messages . . . . . . . . . . . . . . . . . . .   6
     8.1. Generating Type 2 Control Messages . . . . . . . . . . . .   6
     8.2. Processing Type 2 Control Messages . . . . . . . . . . . .   7
     8.3. Transmitting Type 2 Control Messages . . . . . . . . . . .   8
   9.  Resolving Duplicated Node Identifications (Id's)  . . . . . .   8
   10. Generating Type 8 and 9 User Messages . . . . . . . . . . . .   8
   11. Generating of Type 10 Acknowledgement Messages  . . . . . . .   9
   12. Processing of Transit Type 8 and 9 Messages . . . . . . . . .   9
   13. Transmitting Type 8 and 9 Messages  . . . . . . . . . . . . .   9
   14. IANA Consideration  . . . . . . . . . . . . . . . . . . . . .  10
   15. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   16. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     16.1. Normative References  . . . . . . . . . . . . . . . . . .  10
     16.2. Informative References  . . . . . . . . . . . . . . . . .  10

1. Introduction

   The intended application of this memo is nearby mobile social network 
   in which users would like to know who are nearby and socialize with 
   them on the fly.  The delay performance study, carried out in 
   [WTS2015], demonstrates the adequacy of TRP for mobile social network 
   application.  Existing protocols and methods were not conceived to 
   support such an application.  The delay sensitive nature of the 
   application renders the methods and protocols like [Epidemic] 
   [Abhijeet] [RFC6693] designed for delay-tolerant mobile ad-hoc 
   network inapplicable.  The expected frequent path breaks and numerous 
Show full document text