idnits 2.17.1 draft-omar-krp-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 4 longer pages, the longest (page 3) being 109 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 5 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 108 instances of too long lines in the document, the longest one being 27 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. == There is 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- The document date (January 31, 2018) is 2277 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force (IETF) Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standard Track 4 Expires: July 31, 2018 January 31, 2018 6 KHALED Routing Protocol (KRP) 7 Specification 8 draft-omar-krp-05 10 Status of this Memo 12 This Internet-Draft is submitted in full conformance with the provisions 13 of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF). Note that other groups may also distribute working documents 17 as Internet-Drafts. The list of current Internet-Drafts is at 18 http://datatracker.ietf.org/drafts/current/. 20 Internet-Drafts are draft documents valid for a maximum of six months and 21 may be updated, replaced, or obsoleted by other documents at any time. 22 It is inappropriate to use Internet-Drafts as reference material or to cite 23 them other than as "work in progress." 25 This Internet-Draft will expire on July 31, 2018. 27 Copyright Notice 29 Copyright (c) 2018 IETF Trust and the persons identified as the document 30 authors. All rights reserved. 32 This document is subject to BCP 78 and the IETF Trust's Legal Provisions 33 Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect 34 on the date of publication of this document. Please review these documents 35 carefully, as they describe your rights and restrictions with respect to this 36 document. Code Components extracted from this document must include 37 Simplified BSD License text as described in Section 4.e of the Trust Legal 38 Provisions and are provided without warranty as described in the Simplified 39 BSD License. 41 Abstract 43 This document specifies KHALED Routing Protocol (KRP), an Exterior Gateway 44 Protocol (EGP) that introduces a new way of routing IP packets from 45 the source to the destination through different Autonomous Systems (ASs). 47 The enhancements that KRP adds are: 49 a) Decreasing the BGP routing table (using the regions concept). 50 b) Enhancing the routing function (using the stored information). 51 c) Enhancing the QoS (using the information separation). 53 KRP sometimes referred to as Regional Routing Protocol (RRP). 55 Table of Contents 57 1. Introduction..................................................1 58 2. KHALED Routing Protocol (KRP).................................1 59 3. KRP Forwarding Mechanism......................................2 60 4. Information Separation........................................4 61 5. Security Considerations.......................................5 62 6. Acknowledgments...............................................5 63 7. Author Address................................................5 64 8. IANA Considerations...........................................5 65 9. References....................................................5 66 10. Full Copyright Statement.....................................5 68 RFC KHALED Routing Protocol (KRP) January 31, 2018 70 1. Introduction 72 - KHALED Routing Protocol (KRP) is an Exterior Gateway Protocol (EGP) that 73 introduces a new way of routing IP packets from the source to the destination 74 through different Autonomous Systems (ASs). 75 - The enhancements that KRP adds are: 77 a) Decreasing the BGP routing table. 78 b) Enhancing the routing function. 79 c) Enhancing the QoS. 81 - KRP shrinks the BGP routing table by more than 80%. 82 - KRP makes separate links for different traffic class to enhance the QoS. 83 - KRP is considered a replacement to BGP. 84 - The Internet will be subdivided into logical regions or by the physical 85 location of continents. 86 - The routing process that KHALED Routing Protocol (KRP) uses is based on the 87 KRP Region Number (RN), the KRP Autonomous System Number (ASN), Best Path Algorithm 88 (AS Path) and the efforts made by the IGP within each AS. 89 - The major difference between KRP and BGP is that KRP does not uses a large table 90 with hundreds of thousands of entries (BGP Table) stored within each Internet router, 91 instead of that, it uses a smarter way of routing based on the KRP RN, KRP ASN 92 stored within each IP address, Best Path Algorithm (AS Path) and the efforts already 93 being done by each IGP within an AS. 95 ************************** ************************************* 96 * * * * 97 * * * * 98 * * ********** 3 * 99 * 1 * ********* * * 100 * * * * * *** * 101 * * * * * * *** * 102 *** * * * * * * * 103 * * * * * * * *************** 104 * * ****** 4 * * * * * 105 ********** * * * * * * 106 ***** * * * * * 107 * * * * * * 108 * * * * * 5 * 109 * * * * * * 110 * 2 * * * * * 111 * * * * * 112 * * ***************** 113 * * 114 * * 115 * 117 Globe Subdivision Into 5 Logical Regions. 119 2. KHALED Routing Protocol (KRP) 121 - KRP uses new terms that can be defined as follows: 123 * Region Number (RN): 125 - The 1st hex digit of the 2nd group of an IPv6 address determines on which RN this IPv6 126 address is located. 127 - The 1st octet of an IPv4 address determines on which RN this IPv4 address is located. 128 - The table that will be used listing the Region Number (RN), the corresponding IPv6 129 2nd group 1st hex digits and the IPv4 1st octet pool of numbers is called the 130 Region Number Table (RNT) and is stored on every KRP router and is as follows: 132 ********************************************************************************************** 133 * Region Number * 1st Hex Digit of the 2nd IPv6 Group * 1st IPv4 Octet Decimal Digits * 134 ********************************************************************************************** 135 * 1 * 0 - 5 - A - F * ARIN Pool * 136 ********************************************************************************************** 137 * 2 * 1 - 6 - B * LACNIC Pool * 138 ********************************************************************************************** 139 * 3 * 2 - 7 - C * RIPE NCC/APNIC Pool * 140 ********************************************************************************************** 141 * 4 * 3 - 8 - D * AFRINIC Pool * 142 ********************************************************************************************** 143 * 5 * 4 - 9 - E * APNIC Pool * 144 ********************************************************************************************** 146 RFC KHALED Routing Protocol (KRP) January 31, 2018 148 * Regional Boarder Router (RBR) ==> A router in a region that has 149 at least one interface connected 150 to a router's interface in another 151 region. 153 * Regional Router (RR) ==> - A router in a region and has all interfaces 154 connected to other routers in the same 155 region. 157 - A router in a local AS that has at least 158 one interface connected to a different AS. 160 * Local KRP AS Router (LKAR) ==> A router in an AS that has all interfaces 161 connected to other routers in the same AS. 163 - Each RBR and RR is configured with a Region Number (RN) that identifies 164 in which region that router is located. 165 - All RBRs and RRs interfaces will be assigned by default to the configured 166 Region Number (RN). 168 - The two connected KRP routers exchange their RNs: 170 1) If they are the same, the two KRP routers are RRs. 171 2) If they are different, the two KRP routers are RBRs. 173 - The two connected KRP routers exchange their KRP ASNs: 175 1) If they are the same, the two KRP routers are LKARs. 176 2) If they are different, the two KRP routers are RRs. 178 Note: 180 - For ISPs and Enterprises, the RN and KRP ASN are configured 181 manually on every KRP router. 183 - For Enterprises, the RN and KRP ASN must be stored on every 184 assigned GUA (in case of IPv6) and on every public IP address 185 (in case of IPv4). 187 3. KRP Forwarding Mechanism 189 - The KRP ASN is represented as follows: 191 a) The 2nd two groups of an IPv6 address are represented as follows: 193 xxxx|yyyy|yyyy|yyyy:yyyy|yyyy|yyyy|yyyy Binary Format 195 XYYY.YYYY Hexadecimal Format 197 where X hex digit is associated with a specific Region Number (RN). 198 and XYYY.YYYY hex digits represents the KRP Autonomous System Number (ASN). 200 b) All octets of an IPv4 address is represented as follows: 202 xxxxxxxx.yyyyyyyy.yyyyyyyy.yyyyyyyy Binary Format 204 XXYY.YYYY Hexadecimal Format 206 where XX hex digits are associated with a specific Region Number (RN). 207 and XXYY.YYYY hex digits represents the KRP Autonomous System Number (ASN). 209 Note:- - The Region Number (RN) is unique for every region. 210 - The KRP ASN must be unique for every AS. 211 - For IPv4, the 4 octets are represented in decimal in the IPv4 address 212 itself, but the KRP ASN is represented in 8 hexadecimal digits. 213 - For IPv4, Enterprises can be assigned more than one KRP ASN. 215 - There are 3 types of tables, 2 RBR messages and 1 RR message that KRP uses for 216 forwarding a packet: 218 a) KRP router Regional Table (RT): 220 - Each RBR and RR creates its own Regional Table (RT). 221 - The Regional Table (RT) is as follows: 223 ********************************************************************** 224 * Local RN * Remote RN * Traffic Class * Local KRP ASN * RBR KRP ASN * 225 ********************************************************************** 226 * * * * * * 227 ********************************************************************** 229 RFC KHALED Routing Protocol (KRP) January 31, 2018 231 b) KRP router Forwarding Table (FT): 233 ************************************************************************** 234 * Local * Remote * RBR * Best * Output * Next-hop * 235 * KRP ASN * KRP ASN * KRP ASN * AS Path * Interface * IP Address * 236 ************************************************************************** 237 * * * * * * * 238 ************************************************************************** 240 c) KRP router IGP Routing Table (IRT): 242 ********************************************************************* 243 * Prefix (Subnet) * Metric * Output Interface * Next-hop IP Address * 244 ********************************************************************* 245 * * * * * 246 ********************************************************************* 248 - RBR Advertised Message Information for the local region's KRP ASN is as follows: 250 ************************************************************ 251 * Remote RN * Traffic Class * No. of Hops * RBR IP Address * 252 ************************************************************ 253 * * * * * 254 ************************************************************ 256 - RBR Advertised Message Information for the remote region's RBR is as follows: 258 *********************************************************** 259 * Local * Remote * Traffic * Number * Time-out * RBR * 260 * RN * RN * Class * of Hops * Value * KRP ASN * 261 *********************************************************** 262 * * * * * * * 263 *********************************************************** 265 - RR Advertised Message Information is as follows: 267 ************************************************************** 268 * Local * Remote * Local * RBR * Traffic * RR * 269 * RN * RN * KRP ASN * KRP ASN * Class * IP Address * 270 ************************************************************** 271 * * * * * * * 272 ************************************************************** 274 RFC KHALED Routing Protocol (KRP) January 31, 2018 276 4. Information Separation 278 Each RR and RBR is responsible for forwarding a specific traffic class. 279 They can have multiple interfaces connected to other routers and each 280 interface is dedicated to a specific traffic class or they can be completely 281 assigned to handle a specific traffic class. 283 This will make the information (data, voice, and video) traffic be 284 separated through the routing process within each region and between 285 different regions. 287 For example, When a host has a packet to be forwarded, it sends the packet 288 to the default gateway (router). 289 This router can be an LKAR or RR. 290 If that router is an LKAR, it checks the KRP Forwarding Table and send the 291 packet to the appropriate RR based on the matching entry with a specific 292 traffic class value. 293 When the packet reaches the local AS RR, it check the KRP FT and forward 294 the packet to the appropriate RR or RBR that is responsible for handling 295 this specific traffic class as advertised by each RR and RBR within each 296 region. 297 Eventually, the packet will reach the appropriate RR (if the destination is 298 within the same region) or RBR (if the destination is within a different region) 299 that is responsible for handling that specific traffic class. 301 By doing so, the information with different traffic classes will have a separate 302 dedicated routing paths from the source to the destination. 304 RFC KHALED Routing Protocol (KRP) January 31, 2018 305 Expires: 7-31-2018 307 Security Considerations 309 Acknowledgments 311 The author would like to thank Lee Howard and B. Raveendran for the useful 312 inputs and discussions about KRP. 314 Author Address 316 Khaled Omar Ibrahim Omar 317 The Road 318 6th of October City, Giza 319 Egypt 321 Phone: +2 01003620284 322 E-mail: eng.khaled.omar@hotmail.com 323 National ID No.: 28611262102992 325 IANA Considerations 327 TBD 329 References 331 TBD 333 Full Copyright Statement 335 Copyright (C) IETF (2018). All Rights Reserved. 337 This document and translations of it may be copied and furnished to 338 others, and derivative works that comment on or otherwise explain it 339 or assist in its implementation may be prepared, copied, published 340 and distributed, in whole or in part, without restriction of any 341 kind, provided that the above copyright notice and this paragraph are 342 included on all such copies and derivative works. However, this 343 document itself may not be modified in any way, such as by removing 344 the copyright notice or references, except as needed for the purpose of 345 developing Internet standards in which case the procedures for 346 copyrights defined in the Internet Standards process must be 347 followed, or as required to translate it into languages other than 348 English. 350 The limited permissions granted above are perpetual and will not be 351 revoked. 353 This document and the information contained herein is provided on 354 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 355 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 356 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 357 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 358 PURPOSE.