Dynamic MultiPath Routing Protocol
draft-pfeifer-rtgwg-dmpr-00

Document Type Active Internet-Draft (individual)
Last updated 2019-02-11
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Internet Engineering Task Force                          H. Pfeifer, Ed.
Internet-Draft                                              ProtocolLabs
Intended status: Informational                                S. Widmann
Expires: August 15, 2019          University for Applied Sciences Munich
                                                       February 11, 2019

                   Dynamic MultiPath Routing Protocol
                      draft-pfeifer-rtgwg-dmpr-00

Abstract

   Dynamic MultiPath Routing (DMPR) is a loop free path vector routing
   protocol with built-in support for policy based multipath routing.
   It has been designed from scratch to work at both low and high
   bandwidth networks - even with high packet loss.  The objective was
   to keep routing overhead low and ensure a deterministic upper limit.
   DMPR can be used to manage huge networks with a similar feature set
   as BGPv4 except for the concept of autonomous systems.

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 https://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 August 15, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Pfeifer & Widmann        Expires August 15, 2019                [Page 1]
Internet-Draft          Dynamic MultiPath Routing          February 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Organization of this Document . . . . . . . . . . . . . .   4
     1.4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.5.  Distinction from other Routing Protocols  . . . . . . . .   5
   2.  Data Structures . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Message Information Base  . . . . . . . . . . . . . . . .   5
     2.2.  Routing Data  . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Routing Table . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Behavior  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Neighbor Detection  . . . . . . . . . . . . . . . . . . .   6
     3.2.  Detection of a Lost Neighbor  . . . . . . . . . . . . . .   6
     3.3.  Interface Handling  . . . . . . . . . . . . . . . . . . .   6
     3.4.  Message Handling  . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Policies  . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.6.  Link Attributes . . . . . . . . . . . . . . . . . . . . .   7
     3.7.  Route Selection . . . . . . . . . . . . . . . . . . . . .   7
     3.8.  Routing Data Calculation  . . . . . . . . . . . . . . . .   8
     3.9.  Network Retraction  . . . . . . . . . . . . . . . . . . .   8
   4.  Protocol Parameters . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Core Configuration  . . . . . . . . . . . . . . . . . . .   9
     4.2.  Path Metric Profiles  . . . . . . . . . . . . . . . . . .   9
     4.3.  Interfaces  . . . . . . . . . . . . . . . . . . . . . . .   9
   5.  Message Format  . . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  Header  . . . . . . . . . . . . . . . . . . . . . . . . .  10
       5.1.1.  Preamble  . . . . . . . . . . . . . . . . . . . . . .  10
       5.1.2.  Extension Header  . . . . . . . . . . . . . . . . . .  11
       5.1.3.  Payload . . . . . . . . . . . . . . . . . . . . . . .  11
         5.1.3.1.  Payload: keep-alive . . . . . . . . . . . . . . .  11
         5.1.3.2.  Payload: uncompressed JSON  . . . . . . . . . . .  12
         5.1.3.3.  Payload: compressed JSON  . . . . . . . . . . . .  12
         5.1.3.4.  Payload: Fragmentation  . . . . . . . . . . . . .  12
     5.2.  JSON Payload  . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text