idnits 2.17.1 draft-omar-krp-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack an IETF Trust Provisions of 28 Dec 2009, Section 6.b Copyright Notice. 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 1 longer page, the longest (page 1) being 82 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 17 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- The document date (October 20, 2020) is 1284 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: 5 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standard Track 4 Expires: April 20, 2020 October 20, 2020 6 KHALED Routing Protocol (KRP) 7 Specification 8 draft-omar-krp-07 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 April 20, 2021. 27 Copyright Notice 29 Copyright (c) 2020 IETF Trust and the person identified as the document 30 author. 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) Choosing a better path (using the AS Weight) 52 c) Enhancing the QoS (using the information separation). 54 KRP sometimes referred to as Regional Routing Protocol (RRP). 56 Table of Contents 58 1. Introduction..................................................1 59 2. KHALED Routing Protocol (KRP).................................1 60 3. KRP Forwarding Mechanism......................................2 61 4. Information Separation........................................4 62 5. Autonomous System Weight (ASW)................................4 63 6. Security Considerations.......................................5 64 7. Acknowledgments...............................................5 65 8. Author Address................................................5 66 9. IANA Considerations...........................................5 67 10. References...................................................5 68 11. Full Copyright Statement.....................................5 70 RFC KHALED Routing Protocol (KRP) October 20, 2020 72 This contribution has been withdrawn. 74 Security Considerations 76 Acknowledgments 78 The author would like to thank Lee Howard and B. Raveendran for the useful 79 inputs and discussions about KRP. 81 Author Address 83 Khaled Omar Ibrahim Omar 84 The Road 85 6th of October City, Giza 86 Egypt 88 Phone: +2 01003620284 89 E-mail: eng.khaled.omar@hotmail.com 90 National ID No.: 28611262102992 92 IANA Considerations 94 TBD 96 References 98 TBD 100 Full Copyright Statement 102 Copyright (C) IETF (2020). All Rights Reserved. 104 This document and translations of it may be copied and furnished to 105 others, and derivative works that comment on or otherwise explain it 106 or assist in its implementation may be prepared, copied, published 107 and distributed, in whole or in part, without restriction of any 108 kind, provided that the above copyright notice and this paragraph are 109 included on all such copies and derivative works. However, this 110 document itself may not be modified in any way, such as by removing 111 the copyright notice or references, except as needed for the purpose of 112 developing Internet standards in which case the procedures for 113 copyrights defined in the Internet Standards process must be 114 followed, or as required to translate it into languages other than 115 English. 117 The limited permissions granted above are perpetual and will not be 118 revoked. 120 This document and the information contained herein is provided on 121 THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, 122 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 123 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 124 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 125 PURPOSE.