draft-omar-nep-00 Khaled Omar
Internet-Draft The Road
Intended status: Standard Track
Expires: December 12, 2017 June 12, 2017
Numbering Exchange Protocol (NEP)
Specification
draft-omar-nep-00
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 December 12, 2017.
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. 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 Numbering Exchange Protocol (NEP).
Table of Contents
1. Introduction..................................................1
2. Numbering Exchange Protocol (NEP).............................1
3. Security Considerations.......................................3
4. Acknowledgments...............................................3
5. Author Address................................................3
6. References....................................................3
7. Full Copyright Statement......................................3
Khaled Omar Internet-Draft [Page 1]
RFC Numbering Exchange Protocol (NEP) June 12, 2017
1. Introduction
- Numbering Exchange Protocol (NEP) is an Interior Gateway Protocol (IGP)
that delivers IP packets between routers in the same Autonomous System (AS).
- NEP 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.
2. Numbering Exchange Protocol (NEP)
- The following figure shows 6 interconnected routers within an AS as follows:
21, 500, 5
11, 2000, 10 41, 1000, 20
21, 500, 5 62, 6000, 90
<--- 34 * 31 --->
----------------------* 3 *----------------------
| 20 | * 10 |
| 1000 | |32 2000 |
| v | |
| | |
| | 5 |
21, 3000, 40 | ^ | 500 |
51, 100, 200 ^ | | | | ^
61, 5000, 70 | | | | | | 21, 1000, 10
| | 31,51,61 11,31,51 |23 31,41,51 31,51 |13 | 51, 3000, 10
* 64 <-- 46 * 42 --> <-- 24 * 21 --> <-- 12 *
* 6 *--------------* 4 *-------------------* 2 *-------------------* 1 *
* 70 * 40 | * 10 * | 21, 1000, 10
5000 45| 3000 | |25 1000 |15 | 31, 2000, 10
| | v | | v 42, 3000, 30
21, 3000, 40 | | | 40 |
31, 1000, 20 v | ^ | 2000 |
61, 5000, 70 | | | |
| | | |
| 200 |52 10 |
| 100 * 3000 |
----------------------* 5 *----------------------
<--- 54 * 51 --->
11, 3000, 10 21, 2000, 40
21, 2000, 40 41, 100, 200
62, 5100, 270
- Each link has two numeric values:
Upper value represents the link delay.
Lower value represents the link bandwidth.
- Each router interface has a number called CUIN assigned to it and is
a combination of the local and remote NEP routers' ULRNs as follows:
xy
Where x represents the local NEP router ULRN.
y represents the remote neighbor NEP Router ULRN.
- Each NEP router advertises the topology information as follows:
rh, b, d
Where r represents the NEP router ULRN.
h represents the number of hops to reach that ULRN.
b represents the link bandwidth.
d represents the link delay.
Khaled Omar Internet-Draft [Page 2]
RFC Numbering Exchange Protocol (NEP) June 12, 2017
- Each router within an Autonomous System (AS) must be configured with
a unique number called Unique Local Router Number (ULRN).
* Unique Local Router Number (ULRN): 8-bit decimal number that uniquely
identifies a router within an AS.
- Each router advertises its ULRN first to its neighboring NEP router.
- Each router assigns the interface connected to the neighboring NEP router
with a composite number called Composite Unique Interface Number (CUIN).
* Composite Unique Interface Number (CUIN): 16-bit decimal number that uniquely
identifies a router interface within
an AS.
- Each router advertises all the interconnected ULRNs, total bandwidth,
number of hops, and total delay to the neighboring NEP router.
- Each NEP router calculates the best path to each ULRN using the following values:
a. Total bandwidth.
b. Number of hops.
c. Total delay.
- The best NEP path from the NEP router to every ULRN from the collected advertised
information has the following:
a. Highest total bandwidth.
b. Lowest number of hops that corresponds to the highest total bandwidth.
c. Lowest total delay.
- The NEP metric is calculated using the following formula:
*****************************************
* (Total-BW * Total-Delay) *
* Metric = --------------------------- *
* No. of Hops *
*****************************************
- The best metric has the lowest value.
- Each NEP router sends an Echo message of each of its interface to the neighboring
NEP router, the time taken by the message to be sent and received over the link
divided by 2 determines the link delay.
- The Echo message is sent by every NEP router every 10 seconds (by default).
- The link delay value is updated every 10 seconds on every advertised message that
contains the 3 values that can be used to determine the best path from the NEP router
to every ULRN.
Khaled Omar Internet-Draft [Page 3]
RFC Numbering Exchange Protocol (NEP) June 12, 2017
Expires: 12-12-2017
Security Considerations
Acknowledgments
Author Address
Khaled Omar Ibrahim Omar
The Road
6th of October City, Giza
Egypt
Phone: +2 01003620284
E-mail: eng.khaled.omar@hotmail.com
National ID No.: 28611262102992
References
Full Copyright Statement
Copyright (C) IETF (2017). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked.
This document and the information contained herein is provided on
THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.