Khaled Routing Protocol (KRP) ID Submission.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jasmine,

 

Please upload the 2nd ID attached.

 

Looking for an advanced discussion to take this ID forward.

 

Best Regards,

 

Khaled Omar

ÿþdraft-omar-intarea-krp-00                              Khaled Omar

Internet-Draft                                           The Road                                       

Intended status: Standard Track

Expires: September 30, 2017		              March 30, 2017                                       





                     KHALED Routing Protocol (KRP)

                             Specification

                       draft-omar-intarea-krp-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 September 30, 2017.







Copyright Notice



   Copyright (c) 2016 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 KHALED Routing Protocol (KRP).









Table of Contents



   1. Introduction..................................................1

   2. KHALED Routing Protocol (KRP).................................1

   3. KRP Forwarding Mechanism......................................2

   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              KHALED Routing Protocol (KRP)        March 30, 2017





1.  Introduction





    - KHALED Routing Protocol (KRP) is an Exterior Gateway Protocol (EGP) that

      introduces a new way of routing IP packets from the source to the destination

      through different Autonomous Systems (ASs).

    - The Internet will be subdivided into logical regions or by the physical

      location of continents.

    - The routing process that KHALED Routing Protocol (KRP) uses is based on the

      KRP Region Number (RN), the KRP Autonomous System Number (ASN), Best Path Algorithm

      (AS Path) and the efforts made by the IGP within each AS.

    - The major difference between KRP and BGP is that KRP does not uses a large table

      with hundreds of thousands of entries (BGP Table) stored within each Internet router,

      instead of that, it uses a smarter way of routing based on the KRP RN,  KRP ASN

      stored within each IP address, Best Path Algorithm (AS Path) and the efforts already

      being done by each IGP within an AS.









2. KHALED Routing Protocol (KRP)





    - KRP uses new terms that can be defined as follows:





    * Region Number (RN):



   - 3-bits represented in one decimal digit.

   - 8 RNs can be used to represent 8 different Regions (from 0 to 7).

   - The 1st hex digit of the 1st group of an IPv6 address determines on which RN this IPv6

     address is located..

   - The 1st octet of an IPv4 address determines on which RN this IPv4 address is located.

   - The table that will be used listing the Region Number (RN), the corresponding IPv6

     1st hex digits and the IPv4 1st octet pool of numbers is called the Region Number Table

     (RNT) and is stored on every KRP router and is as follows:





           **************************************************************

           *  Region Number  *  1st IPv6 hex digits  *  1st IPv4 Octets * 

           **************************************************************  

           *        1        *       1 - 6 - B       *     ARIN Pool    *        

           **************************************************************  

           *        2        *       2 - 7 - C       *   RIPE NCC Pool  *        

           **************************************************************  

           *        3        *       3 - 8 - D       *   AFRINIC Pool   *        

           **************************************************************  

           *        4        *       4 - 9 - E       *    APNIC Pool    *        

           **************************************************************  

           *        5        *       5 - A           *   LACNIC Pool    *        

           **************************************************************







    * Regional Boarder Router (RBR) ==> A router in a region that has

                                        at least one interface connected

                                        to a router's interface in another

                                        region.





    * Regional Router (RR) ==> A router in a region and has all interfaces

                               connected to other routers in the same

                               region.





   - Each RBR and RR is configured with a Region Number (RN) that identifies

     in which region that router is located. 

   - All RBRs and RRs interfaces will be assigned by default to the configured

     Region Number (RN).

   - The two connected KRP routers exchange their RNs: 



       1) If they are the same, the two KRP routers are RRs.

       2) If they are different, the two KRP routers are RBRs.



   











Khaled Omar             Internet-Draft                   [Page 2]



RFC               KHALED Routing Protocol (KRP)        March 30, 2017









3. KRP Forwarding Mechanism







   - KRP requires the IPv6 and IPv4 assignment must follow these requirements:



     a) The 1st two groups of an IPv6 address is represented as follows:



                   yyyy|yyyy|yyyy|yyyy:yyyy|yyyy|yyyy|yyyy

                                  

                                  YYYY:YYYY



       where YYYY:YYYY hex digits represents the KRP Autonomous System Number (ASN).







     b) The 1st two octets of an IPv4 address is represented as follows:



                             yyyyyyyy.yyyyyyyy



                                   YY.YY



      where YY.YY hex digits represents the KRP Autonomous System Number (ASN).



     Note:- - The KRP ASN must be unique for every AS.







    - There are 3 types of tables and 1 RBR message that the KRP uses for forwarding a packet:





     a) KRP router Regional Table (RT):





     **********************************************************************

     * Local RN * Remote RN * Traffic Class * Local KRP ASN * RBR KRP ASN * 

     **********************************************************************  

     *          *           *               *               *             *

     **********************************************************************





    - Each RBR and RR creates its own Regional Table (RT).

    - The Regional Table (RT) is as follows:





      Note:- - Each RBR broadcasts the full learned RT first, then the new learned 

               Remote RN.

             - Each RBR broadcasts the RT out of all its interfaces except the interface

               where it learned about the remote RN.







    b) KRP router Forwarding Table (FT):





     ***************************************************************************

     *   Local  *   Remote  *    RBR    *    Best   *   Output   *   Next-hop  *

     *  KRP ASN *  KRP ASN  *  KRP ASN  *  AS Path  *  Interface *  IP Address *

     ***************************************************************************  

     *          *           *           *           *            *             *

     ***************************************************************************







    c) KRP router IGP Routing Table (IRT):





     *************************************************************

     * Prefix (Subnet) * Metric * Output Interface * Next-hop IP * 

     ************************************************************* 

     *                 *        *                  *             *      

     *************************************************************

   





   - RBR Advertised Message Information for the local region is as follows:





     *******************************************************

     * Remote RN * Metric * Output Interface * Next-hop IP * 

     ******************************************************* 

     *           *        *                  *             *      

     *******************************************************







   - RBR Advertised Message Information for the remote region is as follows:





     ***********************************************************

     * Local * Remote * Traffic * Number  * Time-out *   RBR   *

     *  RN   *   RN   *  Class  * of Hops *  Value   * KRP ASN *

     *********************************************************** 

     *          *           *                  *               *      

     ***********************************************************







    d) RBR Regional Table (RRT):





     ******************************************************

     * Local RN * Remote RN * Traffic Class * RBR KRP ASN * 

     ******************************************************  

     *          *           *               *             *

     ******************************************************











Khaled Omar             Internet-Draft                   [Page 3]



RFC              KHALED Routing Protocol (KRP)        March 30, 2017

Expires: 30-9-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 (2016).  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.


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]