Node Potential Oriented Multi-NextHop Routing Protocol
draft-lanzhangwang-rtgwg-npmnrp-02

Document Type Active Internet-Draft (individual)
Last updated 2016-10-19
Replaces draft-ietf-rtgwg-npmnrp
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)
Network Working Group                                           J.L. Lan
Internet-Draft                                                J.H. Zhang
Intended status: Informational                                    B.Wang
Expires: April 21, 2017                                         W.F. Liu
                                                                 Y.J. Bu
         National Digital Switching System Engineering and Technological
                                              Research Center, P.R.China
                                                                   X. Li
                      BEIJING UNIVERSITY OF POSTS AND TELECOMMUNICATIONS
                                                         October 20, 2016

         Node Potential Oriented Multi-NextHop Routing Protocol
                       draft-lanzhangwang-rtgwg-npmnrp-02

Abstract

   The Node Potential Oriented Multi-Nexthop Routing Protocol (NP-MNRP)
   bases on the idea of "hop-by-hop routing forwarding, multi-backup
   next hop" and combines with the phenomena that water flows from
   higher place to lower.  NP-MNRP defines a metric named as node
   potential, which is based on hop count and the actual link bandwidth,
   and calculates multiple next-hops through the potential difference
   between the nodes.

Requirements Language

   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 RFC 2119 [RFC2119].

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 April 21, 2017.

 

Bu, et al              Expires April 21, 2017                [Page 1]
Internet Draft        The NPMNRP Routing Protocol        October 20, 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.  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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3. Protocol operation  . . . . . . . . . . . . . . . . . . . . . .  5
     3.1. LFBs Network prefix information advertisement . . . . . . .  5
     3.2. Neighbor Node Discovery and Adjacency establishment . . . .  7
     3.3. Calculation of node potential value . . . . . . . . . . . .  8
     3.4. network event sensing . . . . . . . . . . . . . . . . . . . 10
     3.5. Update of the node potential  . . . . . . . . . . . . . . . 12
   4. Routing information base  . . . . . . . . . . . . . . . . . . . 14
   5. NP-MNRP packets format  . . . . . . . . . . . . . . . . . . . . 15
     5.1. Encapsulation of NP-MNRP packets  . . . . . . . . . . . . . 15
     5.2. Packet format . . . . . . . . . . . . . . . . . . . . . . . 15
   6. Informative References  . . . . . . . . . . . . . . . . . . . . 24
   7. Author's Address  . . . . . . . . . . . . . . . . . . . . . . . 24

1. Introduction

   The inspiration of this routing protocol comes from the natural water
   flow, which is a phenomenon of potential energy driven. Water flows
   through all feasible channels from high potential site to low
   potential site. If in every router all feasible next-hops for one
   certain destination can be found, then all the packets to that
   destination can be transferred in many paths.

   This routing protocol obeys the Internet philosophy of "hop-by-hop
   routing paradigm" and enhances it with "multiple feasible next-hops".
Show full document text