idnits 2.17.1 draft-omar-krp-02.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 108 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 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 99 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 (September 24, 2017) is 2400 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 draft-omar-krp-02 Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standard Track 4 Expires: March 24, 2018 September 24, 2017 6 KHALED Routing Protocol (KRP) 7 Specification 8 draft-omar-krp-02 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 March 24, 2018. 27 Copyright Notice 29 Copyright (c) 2017 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), sometimes referred to as 44 Regional Routing Protocol (RRP). 46 Table of Contents 48 1. Introduction..................................................1 49 2. KHALED Routing Protocol (KRP).................................1 50 3. KRP Forwarding Mechanism......................................2 51 4. Security Considerations.......................................4 52 5. Acknowledgments...............................................4 53 6. Author Address................................................4 54 7. IANA Considerations...........................................4 55 8. References....................................................4 56 9. Full Copyright Statement......................................4 58 RFC KHALED Routing Protocol (KRP) September 24, 2017 60 1. Introduction 62 - KHALED Routing Protocol (KRP) is an Exterior Gateway Protocol (EGP) that 63 introduces a new way of routing IP packets from the source to the destination 64 through different Autonomous Systems (ASs). 65 - The Internet will be subdivided into logical regions or by the physical 66 location of continents. 67 - The routing process that KHALED Routing Protocol (KRP) uses is based on the 68 KRP Region Number (RN), the KRP Autonomous System Number (ASN), Best Path Algorithm 69 (AS Path) and the efforts made by the IGP within each AS. 70 - The major difference between KRP and BGP is that KRP does not uses a large table 71 with hundreds of thousands of entries (BGP Table) stored within each Internet router, 72 instead of that, it uses a smarter way of routing based on the KRP RN, KRP ASN 73 stored within each IP address, Best Path Algorithm (AS Path) and the efforts already 74 being done by each IGP within an AS. 76 ************************** ************************************* 77 * * * * 78 * * * * 79 * * ********** 3 * 80 * 1 * ********* * * 81 * * * * * *** * 82 * * * * * * *** * 83 *** * * * * * * * 84 * * * * * * * *************** 85 * * ****** 4 * * * * * 86 ********** * * * * * * 87 ***** * * * * * 88 * * * * * * 89 * * * * * 5 * 90 * * * * * * 91 * 2 * * * * * 92 * * * * * 93 * * ***************** 94 * * 95 * * 96 * 98 Globe Subdivision Into 5 Logical Regions. 100 2. KHALED Routing Protocol (KRP) 102 - KRP uses new terms that can be defined as follows: 104 * Region Number (RN): 106 - The 1st hex digit of the 2nd group of an IPv6 address determines on which RN this IPv6 107 address is located. 108 - The 1st octet of an IPv4 address determines on which RN this IPv4 address is located. 109 - The table that will be used listing the Region Number (RN), the corresponding IPv6 110 2nd group 1st hex digits and the IPv4 1st octet pool of numbers is called the 111 Region Number Table (RNT) and is stored on every KRP router and is as follows: 113 ********************************************************************************************** 114 * Region Number * 1st Hex Digit of the 2nd IPv6 Group * 1st IPv4 Octet Decimal Digits * 115 ********************************************************************************************** 116 * 1 * 0 - 5 - A - F * ARIN Pool * 117 ********************************************************************************************** 118 * 2 * 1 - 6 - B * LACNIC Pool * 119 ********************************************************************************************** 120 * 3 * 2 - 7 - C * RIPE NCC/APNIC Pool * 121 ********************************************************************************************** 122 * 4 * 3 - 8 - D * AFRINIC Pool * 123 ********************************************************************************************** 124 * 5 * 4 - 9 - E * APNIC Pool * 125 ********************************************************************************************** 127 RFC KHALED Routing Protocol (KRP) September 24, 2017 129 * Regional Boarder Router (RBR) ==> A router in a region that has 130 at least one interface connected 131 to a router's interface in another 132 region. 134 * Regional Router (RR) ==> - A router in a region and has all interfaces 135 connected to other routers in the same 136 region. 138 - A router in a local AS that has at least 139 one interface connected to a different AS. 141 * Local KRP AS Router (LKAR) ==> A router in an AS that has all interfaces 142 connected to other routers in the same AS. 144 - Each RBR and RR is configured with a Region Number (RN) that identifies 145 in which region that router is located. 146 - All RBRs and RRs interfaces will be assigned by default to the configured 147 Region Number (RN). 149 - The two connected KRP routers exchange their RNs: 151 1) If they are the same, the two KRP routers are RRs. 152 2) If they are different, the two KRP routers are RBRs. 154 - The two connected KRP routers exchange their KRP ASNs: 156 1) If they are the same, the two KRP routers are LKARs. 157 2) If they are different, the two KRP routers are RRs. 159 Note: 161 - For ISPs and Enterprises, the RN and KRP ASN are configured 162 manually on every KRP router. 164 - For Enterprises, the RN and KRP ASN must be stored on every 165 assigned GUA (in case of IPv6) and on every public IP address 166 (in case of IPv4). 168 3. KRP Forwarding Mechanism 170 - The KRP ASN is represented as follows: 172 a) The 2nd two groups of an IPv6 address are represented as follows: 174 xxxx|yyyy|yyyy|yyyy:yyyy|yyyy|yyyy|yyyy Binary Format 176 XYYY.YYYY Hexadecimal Format 178 where X hex digit is associated with a specific Region Number (RN). 179 and XYYY.YYYY hex digits represents the KRP Autonomous System Number (ASN). 181 b) All octets of an IPv4 address is represented as follows: 183 xxxxxxxx.yyyyyyyy.yyyyyyyy.yyyyyyyy Binary Format 185 XXYY.YYYY Hexadecimal Format 187 where XX hex digits are associated with a specific Region Number (RN). 188 and XXYY.YYYY hex digits represents the KRP Autonomous System Number (ASN). 190 Note:- - The Region Number (RN) is unique for every region. 191 - The KRP ASN must be unique for every AS. 192 - For IPv4, the 4 octets are represented in decimal in the IPv4 address 193 itself, but the KRP ASN is represented in 8 hexadecimal digits. 195 - There are 3 types of tables, 2 RBR messages and 1 RR message that KRP uses for 196 forwarding a packet: 198 a) KRP router Regional Table (RT): 200 - Each RBR and RR creates its own Regional Table (RT). 201 - The Regional Table (RT) is as follows: 203 ********************************************************************** 204 * Local RN * Remote RN * Traffic Class * Local KRP ASN * RBR KRP ASN * 205 ********************************************************************** 206 * * * * * * 207 ********************************************************************** 209 RFC KHALED Routing Protocol (KRP) September 24, 2017 211 b) KRP router Forwarding Table (FT): 213 *************************************************************************** 214 * Local * Remote * RBR * Best * Output * Next-hop * 215 * KRP ASN * KRP ASN * KRP ASN * AS Path * Interface * IP Address * 216 *************************************************************************** 217 * * * * * * * 218 *************************************************************************** 220 c) KRP router IGP Routing Table (IRT): 222 ********************************************************************* 223 * Prefix (Subnet) * Metric * Output Interface * Next-hop IP Address * 224 ********************************************************************* 225 * * * * * 226 ********************************************************************* 228 - RBR Advertised Message Information for the local region's KRP ASN is as follows: 230 ************************************************************ 231 * Remote RN * Traffic Class * No. of Hops * RBR IP Address * 232 ************************************************************ 233 * * * * * 234 ************************************************************ 236 - RBR Advertised Message Information for the remote region's RBR is as follows: 238 *********************************************************** 239 * Local * Remote * Traffic * Number * Time-out * RBR * 240 * RN * RN * Class * of Hops * Value * KRP ASN * 241 *********************************************************** 242 * * * * * * * 243 *********************************************************** 245 - RR Advertised Message Information is as follows: 247 *************************************************** 248 * Local * Remote * Local * RBR * RR * 249 * RN * RN * KRP ASN * KRP ASN * IP Address * 250 *************************************************** 251 * * * * * * 252 *************************************************** 254 RFC KHALED Routing Protocol (KRP) September 24, 2017 255 Expires: 24-3-2018 257 Security Considerations 259 Acknowledgments 261 The author would like to thank Lee Howard and B. Raveendran for the useful 262 inputs and discussions about KRP. 264 Author Address 266 Khaled Omar Ibrahim Omar 267 The Road 268 6th of October City, Giza 269 Egypt 271 Phone: +2 01003620284 272 E-mail: eng.khaled.omar@hotmail.com 273 National ID No.: 28611262102992 275 IANA Considerations 277 References 279 Full Copyright Statement 281 Copyright (C) IETF (2017). All Rights Reserved. 283 This document and translations of it may be copied and furnished to 284 others, and derivative works that comment on or otherwise explain it 285 or assist in its implementation may be prepared, copied, published 286 and distributed, in whole or in part, without restriction of any 287 kind, provided that the above copyright notice and this paragraph are 288 included on all such copies and derivative works. However, this 289 document itself may not be modified in any way, such as by removing 290 the copyright notice or references, except as needed for the purpose of 291 developing Internet standards in which case the procedures for 292 copyrights defined in the Internet Standards process must be 293 followed, or as required to translate it into languages other than 294 English. 296 The limited permissions granted above are perpetual and will not be 297 revoked. 299 This document and the information contained herein is provided on 300 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 301 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 302 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 303 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 304 PURPOSE.