Numbering Exchange Protocol (NEP) Specification
draft-omar-nep-05

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Khaled Omar  , Luís Câmara 
Last updated 2018-01-26
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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 (IETF)                    Khaled Omar
Internet-Draft                                             The Road
Intended status: Experimental                                  L. Camara
Expires: July 30, 2018                                  January 26, 2018
                                                       

                     Numbering Exchange Protocol (NEP)
                             Specification
                           draft-omar-nep-05

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 July 30, 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
   (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
   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.

Abstract

   This document specifies the Numbering Exchange Protocol (NEP), a
   routing protocol that combines three metrics: delay, bandwidth and
   number of hops.

Omar & Camara          Expires July 30, 2018                    [Page 1]
Internet-Draft    Numbering Exchange Protocol (NEP)         January 2018

Table of Contents

   1. Introduction ....................................................2
   2. Numbering Exchange Protocol (NEP) ...............................3
   3. NEP Loop Prevention .............................................5
   4. Subnet Advertisement ............................................6
   5. IANA Considerations .............................................7
   6. Security Considerations .........................................7
   7. References ......................................................7
   7.1. Normative References ..........................................8
   7.2. Informative References ........................................8
   8. Authors' Addresses ..............................................8
   Appendix A. NEP Advertisement Format ...............................8
   A.1. NEP Header ....................................................8
   A.2. Topology Advertisement ........................................9
   A.3. Subnet Advertisements ........................................10
   A.3.1. IPv4 Subnet Advertisements .................................10
   A.3.2. IPv6 Subnet Advertisements .................................10

1.  Introduction

   The Numbering Exchange Protocol (NEP) is an Interior Gateway
   Protocol (IGP), delivering IP packets between routers in the same
   Autonomous System (AS).

   Many routing protocols, such as RIP, OSPF, IS-IS, and EIGRP, use
   normally one or even zero metrics each:

      a. RIP uses only the number of hops.
      b. OSPF uses only the cost (bandwidth).
      c. IS-IS uses only a default metric of 10 for all links.
      d. EIGRP uses the least bandwidth and delay.

   NEP differs from other IGPs as it chooses its best path based on a
   composite metric of:

      a. Highest total bandwidth (for faster transmission).
      b. Number of hops (for less processing).
      c. Lowest total delay (for faster delivery).

   NEP uses a numbering method between routers that provides a fast
   topology exchange and learning process, and builds a routing table
   shorter than those that other IGPs build.

   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
   BCP 14 [RFC2119, RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Omar & Camara          Expires July 30, 2018                    [Page 2]
Internet-Draft    Numbering Exchange Protocol (NEP)         January 2018

2. Numbering Exchange Protocol (NEP)

   The following figure shows 6 interconnected routers within an AS as
Show full document text