< draft-omar-nep-00.txt   draft-omar-nep-01.txt >
draft-omar-nep-00 Khaled Omar draft-omar-nep-01 Khaled Omar
Internet-Draft The Road Internet-Draft The Road
Intended status: Standard Track Intended status: Standard Track
Expires: December 12, 2017 June 12, 2017 Expires: June 6, 2018 December 6, 2017
Numbering Exchange Protocol (NEP) Numbering Exchange Protocol (NEP)
Specification Specification
draft-omar-nep-00 draft-omar-nep-01
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the provisions This Internet-Draft is submitted in full conformance with the provisions
of BCP 78 and BCP 79. of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF). Note that other groups may also distribute working documents Force (IETF). Note that other groups may also distribute working documents
as Internet-Drafts. The list of current Internet-Drafts is at as Internet-Drafts. The list of current Internet-Drafts is at
http://datatracker.ietf.org/drafts/current/. http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and 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. 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 It is inappropriate to use Internet-Drafts as reference material or to cite
them other than as "work in progress." them other than as "work in progress."
This Internet-Draft will expire on December 12, 2017. This Internet-Draft will expire on June 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the document Copyright (c) 2017 IETF Trust and the persons identified as the document
authors. All rights reserved. authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions 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 Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect
on the date of publication of this document. Please review these documents on the date of publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect to this carefully, as they describe your rights and restrictions with respect to this
skipping to change at page 1, line 50 skipping to change at page 1, line 50
BSD License. BSD License.
Abstract Abstract
This document specifies Numbering Exchange Protocol (NEP). This document specifies Numbering Exchange Protocol (NEP).
Table of Contents Table of Contents
1. Introduction..................................................1 1. Introduction..................................................1
2. Numbering Exchange Protocol (NEP).............................1 2. Numbering Exchange Protocol (NEP).............................1
3. Security Considerations.......................................3 3. NEP Loop Prevention...........................................3
4. Acknowledgments...............................................3 4. Security Considerations.......................................4
5. Author Address................................................3 5. Acknowledgments...............................................4
6. References....................................................3 6. Author Address................................................4
7. Full Copyright Statement......................................3 7. References....................................................4
8. Full Copyright Statement......................................4
RFC Numbering Exchange Protocol (NEP) June 12, 2017 RFC Numbering Exchange Protocol (NEP) December 6, 2017
1. Introduction 1. Introduction
- Numbering Exchange Protocol (NEP) is an Interior Gateway Protocol (IGP) - Numbering Exchange Protocol (NEP) is an Interior Gateway Protocol (IGP)
that delivers IP packets between routers in the same Autonomous System (AS). that delivers IP packets between routers in the same Autonomous System (AS).
- NEP chooses its best path based on a composite metric of: - NEP chooses its best path based on a composite metric of:
a. Highest total bandwidth (for faster transmission). a. Highest total bandwidth (for faster transmission).
b. Number of hops (for less processing). b. Number of hops (for less processing).
c. Lowest total delay (for faster delivery). c. Lowest total delay (for faster delivery).
- NEP uses a numbering method between routers that provides a fast topology - NEP uses a numbering method between routers that provides a fast topology
exchange and learning process. exchange and learning process.
2. Numbering Exchange Protocol (NEP) 2. Numbering Exchange Protocol (NEP)
- The following figure shows 6 interconnected routers within an AS as follows: - The following figure shows 6 interconnected routers within an AS as follows:
21, 500, 5 22, 2500, 15
11, 2000, 10 41, 1000, 20 12, 3000, 30 31, 2000, 10
21, 500, 5 62, 6000, 90 22, 1500, 25 42, 3000, 30
<--- 34 * 31 ---> 31, 1000, 20 63, 8000, 100
<----- * ----->
----------------------* 3 *---------------------- ----------------------* 3 *----------------------
| 20 | * 10 | | 20 | * 10 |
| 1000 | |32 2000 | | 1000 | | 2000 |
| v | | | v | |
| | | | | |
| | 5 | 22, 4000, 60 | | 5 |
21, 3000, 40 | ^ | 500 | 41, 1000, 20 | ^ | 500 |
51, 100, 200 ^ | | | | ^ 52, 1100, 220 ^ | | | | ^ 11, 2000, 10
61, 5000, 70 | | | | | | 21, 1000, 10 62, 6000, 90 | | | | | | 22, 3000, 20
| | 31,51,61 11,31,51 |23 31,41,51 31,51 |13 | 51, 3000, 10 | | 32,41,52,62 12,21,32 | 31,41,51 31,51 | | 52, 5000, 20
* 64 <-- 46 * 42 --> <-- 24 * 21 --> <-- 12 * * <---- * ----> <---- * ----> <---- *
* 6 *--------------* 4 *-------------------* 2 *-------------------* 1 * * 6 *--------------* 4 *-------------------* 2 *-------------------* 1 *
* 70 * 40 | * 10 * | 21, 1000, 10 * 70 * 40 | * 10 * | 11, 3000, 10
5000 45| 3000 | |25 1000 |15 | 31, 2000, 10 5000 | 3000 | | 1000 | | 22, 4000, 20
| | v | | v 42, 3000, 30 | | v | | v 32, 5000, 20
21, 3000, 40 | | | 40 | 22, 3100, 240 | | | 40 | 43, 6000, 40
31, 1000, 20 v | ^ | 2000 | 32, 1100, 220 v | ^ | 2000 | 64, 11000, 110
61, 5000, 70 | | | | 41, 100, 200 | | | |
| | | | 62, 5100, 270 | | | |
| 200 |52 10 | | 200 | 10 |
| 100 * 3000 | | 100 * 3000 |
----------------------* 5 *---------------------- ----------------------* 5 *----------------------
<--- 54 * 51 ---> <---- * ---->
11, 3000, 10 21, 2000, 40 12, 3100, 210 22, 5000, 50
21, 2000, 40 41, 100, 200 22, 2100, 240 42, 3100, 210
62, 5100, 270 51, 100, 200 51, 3000, 10
63, 8100, 280
- Each link has two numeric values: - Each link has two numeric values:
Upper value represents the link delay. Upper value represents the link delay.
Lower value represents the link bandwidth. 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: - Each NEP router advertises the topology information as follows:
rh, b, d rh, b, d
Where r represents the NEP router ULRN. Where r represents the NEP router RID.
h represents the number of hops to reach that ULRN. h represents the number of hops to reach that router.
b represents the link bandwidth. b represents the link bandwidth.
d represents the link delay. d represents the link delay.
RFC Numbering Exchange Protocol (NEP) June 12, 2017 RFC Numbering Exchange Protocol (NEP) December 6, 2017
- Each router within an Autonomous System (AS) must be configured with - Each router within an Autonomous System (AS) must be configured with
a unique number called Unique Local Router Number (ULRN). a unique number called Router ID (RID).
* 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. * RID: 32-bit decimal number that uniquely identifies a router within an AS.
- Each router assigns the interface connected to the neighboring NEP router The RID has the following format: Y.Y.Y.Y
with a composite number called Composite Unique Interface Number (CUIN).
* Composite Unique Interface Number (CUIN): 16-bit decimal number that uniquely - Each router advertises its RID first to its neighboring routers using Hello messages.
identifies a router interface within
an AS.
- Each router advertises all the interconnected ULRNs, total bandwidth, - Each router advertises all the interconnected RIDs, total bandwidth, number of hops,
number of hops, and total delay to the neighboring NEP router. and total delay to the neighboring router.
- Each NEP router calculates the best path to each ULRN using the following values: - Each router calculates the best path to each router using the following values:
a. Total bandwidth. a. Total bandwidth.
b. Number of hops. b. Number of hops.
c. Total delay. c. Total delay.
- The best NEP path from the NEP router to every ULRN from the collected advertised - The best NEP path from the local router to every other router from the collected advertised
information has the following: information has the following:
a. Highest total bandwidth. a. Highest total bandwidth.
b. Lowest number of hops that corresponds to the highest total bandwidth. b. Lowest number of hops that corresponds to the highest total bandwidth.
c. Lowest total delay. c. Lowest total delay.
- The NEP metric is calculated using the following formula: - The NEP metric is calculated using the following formula:
***************************************** ****************************************************
* (Total-BW * Total-Delay) * * (No. of Hops * Total-Delay) *
* Metric = --------------------------- * * Metric = [-----------------------------] x 10^7 *
* No. of Hops * * Total-BW *
***************************************** ****************************************************
- The best metric has the lowest value. - The best metric has the lowest value.
- Each NEP router sends an Echo message of each of its interface to the neighboring - 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 router, the time taken by the message to be sent and received over the link
divided by 2 determines the link delay. divided by 2 determines the link delay.
- The Echo message is sent by every NEP router every 10 seconds (by default). - The Echo message is sent by every router every 10 seconds (by default).
- The link delay value is updated every 10 seconds on every advertised message that - 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 contains the 3 values that can be used to determine the best path from the NEP router
to every ULRN. to other routers.
RFC Numbering Exchange Protocol (NEP) June 12, 2017 RFC Numbering Exchange Protocol (NEP) December 6, 2017
Expires: 12-12-2017
NEP Loop Prevention:
- NEP uses a loop free mechanism by discarding the advertised topology information that has
a higher metric than the existing stored entry for the same RID to prevent looping.
- When an NEP router receives an advertised topology information to a specific router, it
checks its own topology table, if there is no entry listed for that RID contained in the
advertised message, it adds it to its own topology table.
- If more than one message received to the same RID, the NEP router calculates the metric for
each one of them and store the one with the lowest metric for that router.
For example:
a) Router 1 will have 3 messages to the destination router 4 as follows:
2: 42, 4000, 50 ==> Metric = 250,000 (discarded)
3: 42, 3000, 30 ==> Metric = 200,000 (added)
5: 42, 3100, 210 ==> Metric = 1,354,839 (discarded)
The message from router 3 has the lowest metric to the destination router 4 so this route
through router 3 will be added to the routing table and other routes will be discarded.
b) Router 1 will have 3 messages to the destination router 6 as follows:
2: 63, 9000, 120 ==> Metric = 400,000 (discarded)
3: 63, 8000, 100 ==> Metric = 375,000 (added)
5: 63, 8100, 280 ==> Metric = 1,037,037 (discarded)
The message from router 2 has the lowest metric to the destination router 6 so this route
through router 2 will be added to the routing table and other routes will be discarded.
Router 1 Routing Table:
***************************************************************
* Destination Router * Metric * Next-hop Router *
***************************************************************
* 2 * 100,000 * 2 *
***************************************************************
* 3 * 50,000 * 3 *
***************************************************************
* 4 * 200,000 * 3 *
***************************************************************
* 5 * 33,333.33 * 5 *
***************************************************************
* 6 * 375,000 * 3 *
***************************************************************
Note:- - In case of two or more equal metrics for the same destination, the routes are added to the
routing table and traffic is balanced between these routes.
RFC Numbering Exchange Protocol (NEP) December 6, 2017
Expires: 6-2-2018
Security Considerations Security Considerations
Acknowledgments Acknowledgments
Author Address Author Address
Khaled Omar Ibrahim Omar Khaled Omar Ibrahim Omar
The Road The Road
6th of October City, Giza 6th of October City, Giza
 End of changes. 26 change blocks. 
68 lines changed or deleted 110 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/