Internet DRAFT - draft-omar-rrp

draft-omar-rrp



Internet Engineering Task Force                            Khaled Omar
Internet-Draft                                              The Road                                       
Intended status: Standard Track                             
Expires: April 20, 2021		      	               October 20, 2020
                                                                                              


                     Regional Routing Protocol (RRP)
                             Specification
                           draft-omar-rrp-01

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 April 20, 2021.



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 Regional Routing Protocol, sometimes referred to as
   KHALED Routing Protocol (KRP).




Table of Contents

   1. Introduction..................................................1
   2. Regional Routing Protocol (RRP)...............................1
   3. RRP Forwarding Mechanism......................................2
   3. Security Considerations.......................................4
   4. Acknowledgments...............................................4
   5. Authors' Addresses............................................4
   6. IANA Considerations...........................................4
   7. References....................................................4
   8. Full Copyright Statement......................................4





Khaled Omar             Internet-Draft                   [Page 1]

RFC              Regional Routing Protocol (RRP)      October 20, 2020




This contribution has been withdrawn.





Security Considerations



Acknowledgments

   The authors would like to thank B. Raveendran for the useful inputs and
   discussions about RRP.


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



IANA Considerations




References




Full Copyright Statement

   Copyright (C) IETF (2020).  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.